unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: No Wayman <iarchivedmywholelife@gmail.com>
Cc: 62893@debbugs.gnu.org
Subject: bug#62893: 30.0.50; ELPA recipes with broken :url property values
Date: Tue, 18 Apr 2023 06:13:53 +0000	[thread overview]
Message-ID: <87sfcx3efy.fsf@posteo.net> (raw)
In-Reply-To: <875y9vw6xb.fsf@gmail.com> (No Wayman's message of "Sun, 16 Apr 2023 22:53:12 -0400")

No Wayman <iarchivedmywholelife@gmail.com> writes:

> In elpa-packages, is there a reason why we keep the :url property for
> packages for which
> the upstream no longer exists? e.g. any package :url pointing to
> "http://www.dr-quibit.org/git/predictive.git"?
>
> I ask because I'm writing GNU/NonGNU ELPA support for Elpaca.
> I'd like to avoid hard-coding an exception for that URL when
> generating package recipes.
> Would a patch changing those :url values to nil be accepted?
> If so, should the old URL be preserved in a comment above each
> package?

Elpa-admin.el fails with a message from "git fetch", which makes sense
if a repository is temporarily not available.  What I think would make
sense here would be to first check what repositories are failing and
then consider if setting the :url to nil would make sense or if it has
just moved somewhere else.

E.g. in this case it seems that there has been an issue with the hosting
provider, and Toby has been (very) slowly porting his packages over to
Gitlab: https://dr-qubit.org/undo-tree.html#orgffcc37e.





  reply	other threads:[~2023-04-18  6:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-17  2:53 bug#62893: 30.0.50; ELPA recipes with broken :url property values No Wayman
2023-04-18  6:13 ` Philip Kaludercic [this message]
2023-09-05 16:34   ` Stefan Kangas
2023-09-05 19:42     ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfcx3efy.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=62893@debbugs.gnu.org \
    --cc=iarchivedmywholelife@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).