GNU bug report logs -
#53004
NonGNU ELPA: paredit only available in -devel archive
Previous Next
Reported by: Stefan Kangas <stefan <at> marxist.se>
Date: Tue, 4 Jan 2022 14:11:01 UTC
Severity: minor
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53004 in the body.
You can then email your comments to 53004 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53004
; Package
emacs
.
(Tue, 04 Jan 2022 14:11:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Stefan Kangas <stefan <at> marxist.se>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Tue, 04 Jan 2022 14:11:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53004
; Package
emacs
.
(Tue, 04 Jan 2022 19:31:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 53004 <at> debbugs.gnu.org (full text, mbox):
Hello Stefan,
On Tue 04 Jan 2022 at 09:10AM -05, Stefan Kangas wrote:
> 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?
I was in touch with upstream recently about a bug. I think that 25
might be forthcoming. So perhaps wait and see a bit?
--
Sean Whitton
Severity set to 'minor' from 'normal'
Request was from
Stefan Kangas <stefan <at> marxist.se>
to
control <at> debbugs.gnu.org
.
(Wed, 05 Jan 2022 16:55:02 GMT)
Full text and
rfc822 format available.
Reply sent
to
Stefan Kangas <stefan <at> marxist.se>
:
You have taken responsibility.
(Wed, 05 Jan 2022 16:55:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Stefan Kangas <stefan <at> marxist.se>
:
bug acknowledged by developer.
(Wed, 05 Jan 2022 16:55:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 53004-done <at> debbugs.gnu.org (full text, mbox):
Sean Whitton <spwhitton <at> 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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53004
; Package
emacs
.
(Thu, 06 Jan 2022 06:41:01 GMT)
Full text and
rfc822 format available.
Message #18 received at 53004 <at> debbugs.gnu.org (full text, mbox):
On Wed 05 Jan 2022 at 08:54am -08, Stefan Kangas wrote:
> Sean Whitton <spwhitton <at> 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.
Just to confirm, you meant version 25, right?
--
Sean Whitton
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53004
; Package
emacs
.
(Thu, 06 Jan 2022 08:06:01 GMT)
Full text and
rfc822 format available.
Message #21 received at 53004 <at> debbugs.gnu.org (full text, mbox):
Sean Whitton <spwhitton <at> spwhitton.name> writes:
>> 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.
>
> Just to confirm, you meant version 25, right?
Yes, that was a typo.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 03 Feb 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 83 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.