emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#53004: closed (NonGNU ELPA: paredit only available in -devel archive


From: GNU bug Tracking System
Subject: bug#53004: closed (NonGNU ELPA: paredit only available in -devel archive)
Date: Wed, 05 Jan 2022 16:55:02 +0000

Your message dated Wed, 5 Jan 2022 08:54:48 -0800
with message-id 
<CADwFkmn_=3c2Zc2=trttMzW0iCaq6Lg+C551mmZJARN=916ONg@mail.gmail.com>
and subject line Re: bug#53004: NonGNU ELPA: paredit only available in -devel 
archive
has caused the debbugs.gnu.org bug report #53004,
regarding NonGNU ELPA: paredit only available in -devel archive
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53004: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=53004
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: NonGNU ELPA: paredit only available in -devel archive Date: Tue, 4 Jan 2022 09:10:05 -0500
In elpa-packages, we have:

    ("paredit"          :url "https://mumble.net/~campbell/git/paredit.git";
     :ignored-files ("check.sh" "genhtml.sh" "test.el"))

But I can't find it on:

    http://elpa.nongnu.org/nongnu/

However, it is available here:

    https://elpa.nongnu.org/nongnu-devel/

I guess this has to do with the version number, which is "25beta".  I'm
not sure why it is a beta, as I've been using it for 10+ years with no
issues whatsoever.

Perhaps we should gently ask the developer to bump it to some non-beta
version number, or alternatively accept that as a full release in this
case?



--- End Message ---
--- Begin Message --- Subject: Re: bug#53004: NonGNU ELPA: paredit only available in -devel archive Date: Wed, 5 Jan 2022 08:54:48 -0800 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux)
Sean Whitton <spwhitton@spwhitton.name> writes:

> I was in touch with upstream recently about a bug.  I think that 25
> might be forthcoming.  So perhaps wait and see a bit?

I think I've misunderstood the development model. Basically, it is
briefly changed from e.g. version 25-beta to version 25 when it is
released, and then it is changed to 26-beta. So if you're running from
current master, it will always be such a "beta" version.

In this case, we could tag up an old commit and build a package from
that, but I don't think it's worth it. Let's just wait for version 26.

I'm therefore closing this bug report.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]