GNU bug report logs - #76953
Latest elpa track-changes 1.3 uses incf which does not exist in Emacs < 31

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 76953 in the body.
You can then email your comments to 76953 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ship Mints <shipmints <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Latest elpa track-changes 1.3 uses incf which does not exist in Emacs
 < 31
Date: Tue, 11 Mar 2025 14:53:29 -0400

[Message part 1 (text/plain, inline)]

Second package released a couple of days that refers to future features.

track-changes says:

;; Package-Requires: ((emacs "24"))

Is there an ELPA infrastructure testing regime, across at least a couple of
supported Emacs releases, that these packages should be passing?  I guess,
like my little ELPA package, it's author's honor.

-Stephane

[Message part 2 (text/html, inline)]

Message #8 received at 76953 <at> debbugs.gnu.org (full text, mbox):

From: Ship Mints <shipmints <at> gmail.com>
To: 76953 <at> debbugs.gnu.org
Subject: Re: bug#76953: Latest elpa track-changes 1.3 uses incf which does not
 exist in Emacs < 31
Date: Tue, 11 Mar 2025 14:57:18 -0400

[Message part 1 (text/plain, inline)]

For track-changes, I guess either add incf to compat and release both, or
use cl-incf?

On Tue, Mar 11, 2025 at 2:55 PM Ship Mints <shipmints <at> gmail.com> wrote:

> Second package released a couple of days that refers to future features.
>
> track-changes says:
>
> ;; Package-Requires: ((emacs "24"))
>
> Is there an ELPA infrastructure testing regime, across at least a couple
> of supported Emacs releases, that these packages should be passing?  I
> guess, like my little ELPA package, it's author's honor.
>
> -Stephane
>

[Message part 2 (text/html, inline)]

Message #13 received at 76953-done <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Ship Mints <shipmints <at> gmail.com>, 76953-done <at> debbugs.gnu.org
Cc: Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#76953: Latest elpa track-changes 1.3 uses incf which does not
 exist in Emacs < 31
Date: Tue, 11 Mar 2025 17:18:25 -0700

Ship Mints <shipmints <at> gmail.com> writes:

> Second package released a couple of days that refers to future features.
>
> track-changes says:
>
> ;; Package-Requires: ((emacs "24"))
>
> Is there an ELPA infrastructure testing regime, across at least a couple of
> supported Emacs releases, that these packages should be passing?  I guess,
> like my little ELPA package, it's author's honor.

Thanks for the bug report.

This should now be fixed, and I've bumped the version of track-changes
accordingly, so it should be released on GNU ELPA within 24 hours.

Message #16 received at 76953 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Ship Mints <shipmints <at> gmail.com>
Cc: 76953 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>
Subject: Re: bug#76953: Latest elpa track-changes 1.3 uses incf which does
 not exist in Emacs < 31
Date: Tue, 11 Mar 2025 22:05:22 -0400

>> Second package released a couple of days that refers to future features.
>>
>> track-changes says:
>>
>> ;; Package-Requires: ((emacs "24"))

"Package-Requires:" does not intend to mean that the package is
guaranteed to work with that release.  Instead it's intended to mean
something more like "it's guaranteed not to work with an older release".

>> Is there an ELPA infrastructure testing regime,

AFAIC, the burden of testing on older releases falls on users of those
older releases.
[ And indeed, when the "older" release is the latest release, it usually
  doesn't take long, as bug#76953 seems to show.  ]

> This should now be fixed, and I've bumped the version of track-changes
> accordingly, so it should be released on GNU ELPA within 24 hours.

Thanks,


        Stefan

Message #19 received at 76953 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>, Ship Mints <shipmints <at> gmail.com>
Cc: 76953 <at> debbugs.gnu.org
Subject: Re: bug#76953: Latest elpa track-changes 1.3 uses incf which does not
 exist in Emacs < 31
Date: Wed, 12 Mar 2025 02:27:04 +0000

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

> AFAIC, the burden of testing on older releases falls on users of those
> older releases.
> [ And indeed, when the "older" release is the latest release, it usually
>   doesn't take long, as bug#76953 seems to show.  ]

It would be useful to have some automated testing of :core packages on
older versions of Emacs.  AFAIK, we don't currently have anything of the
sort, though you can always say

    EMACS=/usr/local/bin/emacs-29.4 make check -C test track-changes-tests

That would presumably need to be given a more convenient interface or
people won't really do it, however.

Perhaps some interested party could teach ERT a couple of new tricks
here.

Message #22 received at 76953 <at> debbugs.gnu.org (full text, mbox):

From: Ship Mints <shipmints <at> gmail.com>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 76953 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>
Subject: Re: bug#76953: Latest elpa track-changes 1.3 uses incf which does not
 exist in Emacs < 31
Date: Tue, 11 Mar 2025 22:51:36 -0400

[Message part 1 (text/plain, inline)]

On Tue, Mar 11, 2025 at 10:05 PM Stefan Monnier <monnier <at> iro.umontreal.ca>
wrote:

> >> Second package released a couple of days that refers to future features.
> >>
> >> track-changes says:
> >>
> >> ;; Package-Requires: ((emacs "24"))
>
> "Package-Requires:" does not intend to mean that the package is
> guaranteed to work with that release.  Instead it's intended to mean
> something more like "it's guaranteed not to work with an older release".
>
> >> Is there an ELPA infrastructure testing regime,
>
> AFAIC, the burden of testing on older releases falls on users of those
> older releases.
>

I'm on 30.1 these days.  Not so old.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.