From: "Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 63757@debbugs.gnu.org
Subject: bug#63757: 29.0.91 order of package paths changed: random old versions of packages in load-path
Date: Tue, 30 May 2023 01:44:11 +1000 [thread overview]
Message-ID: <CAKOwOe45eCkB=gKUCgMH3LoCJy1KrTijhOFk2WauDEJAH8ySAw@mail.gmail.com> (raw)
In-Reply-To: <jwvpm6ji8cb.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3869 bytes --]
> Can you show how `package-alist` changes for `-go-mode` for you?
To reproduce the case we need emacs 29.0.91 and
~/.emacs.d/elpa/go-mode-20170726.555/...
~/.emacs.d/elpa/go-mode-20220114.2239/...
Run `emacs -Q` and `M-x package-initialize`.
After that `package-alist` contains
(go-mode #s(package-desc :name go-mode :version
(20170726 555)
:summary "Major mode for the Go programming
language" :reqs nil :kind nil :archive nil :dir
"/home/eab/.emacs.d/elpa/go-mode-20170726.555" :extras
((:keywords "languages" "go")
(:url . "https://github.com/dominikh/go-mode.el
")
(:commit .
"99b06da201afb91e8db0c525c0f3c3590fd92fa6"))
:signed nil)
#s(package-desc :name go-mode :version
(20220114 2239)
:summary "Major mode for the Go programming
language" :reqs
((emacs
(26 1)))
:kind nil :archive nil :dir
"/home/eab/.emacs.d/elpa/go-mode-20220114.2239" :extras
((:url . "https://github.com/dominikh/go-mode.el
")
(:keywords "languages" "go")
(:maintainer "The go-mode Authors")
(:authors
("The go-mode Authors"))
(:commit .
"fa2693278637f56759480d2bf203bb8aad107230"))
:signed nil))
and `load-path` contains
"/home/eab/.emacs.d/elpa/go-mode-20170726.555"
On Mon, May 29, 2023 at 11:25 PM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >> In your commit 04c4c578, package directories became NOSORT due to
> (fourth t
> >> argument)
> >> (directory-files dir)
> >> replaced by
> >> (directory-files dir t "^[^.]" t)
> >>
> >> It affects package-alist forming.
>
> Can you show how `package-alist` changes for `-go-mode` for you?
>
> >> For example, there are old and new
> >> versions of a package in my elpa directory:
> >>
> >> go-mode-20170726.555
> >> go-mode-20220114.2239
> >>
> >> After (package-initialize)
> >> in emacs 28 (require 'go-mode) gives 2022 version, e.g. the latest
> version
> >> of a package in most cases, directory-files default sorting works.
> >> In emacs 29.0.91 I get old 2017
>
> That shouldn't be the case (unless you specifically asked for it via
> something like `package-pinned-packages`).
>
> >> version because of NOSORT unpredictable version order in
> >> package-alist and hence random paths in load-path
>
> In its, this shouldn't make a difference, because it just changes the
> order in which we consult the `<PKG>-pkg.el` descriptors to populate
> `package-alist` whereas the *activation* of the `go-mode` package is the
> one that should choose the one with the higher version number.
>
> > No, this is not a feature but I think it might have uncovered a bug.
> > Relying on the ordering of file names (which IIRC is lexiographic not
> > numeric) is not a robust way to decide what packages should be preferred
> > when loading descriptors. Could you submit a bug report to
> > bug-gnu-emacs@gnu.org so that this issue can be discussed with the other
> > maintainers?
>
> Barring bugs, `package-alist` can be filled in any order (so the `nosort`
> option shouldn't make a difference): we apply the proper sorting
> (i.e. newest version at the front) in `package-process-define-package`.
>
>
> Stefan
>
>
--
__________________________
С уважением,
Бойков Евгений Алексеевич
сот. 8-924-202-25-65
e-mail: artscan@list.ru
[-- Attachment #2: Type: text/html, Size: 5275 bytes --]
next prev parent reply other threads:[~2023-05-29 15:44 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 16:30 bug#63757: 29.0.91 order of package paths changed: random old versions of packages in load-path Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 11:09 ` Eli Zaretskii
2023-05-29 14:24 ` Philip Kaludercic
2023-06-03 10:19 ` Philip Kaludercic
2023-06-03 10:38 ` Eli Zaretskii
2023-06-03 11:50 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 12:53 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 13:33 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 14:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 4:46 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 5:37 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 5:41 ` Eli Zaretskii
2023-06-04 7:47 ` Philip Kaludercic
2023-06-04 8:03 ` Eli Zaretskii
2023-06-04 9:19 ` Philip Kaludercic
2023-06-04 10:14 ` Eli Zaretskii
2023-06-04 11:39 ` Philip Kaludercic
2023-06-04 12:08 ` Eli Zaretskii
2023-06-04 12:12 ` Philip Kaludercic
2023-06-04 12:19 ` Eli Zaretskii
2023-06-04 12:32 ` Philip Kaludercic
2023-06-04 12:46 ` Eli Zaretskii
2023-06-04 13:21 ` Philip Kaludercic
2023-06-04 14:03 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:24 ` Philip Kaludercic
2023-06-04 14:30 ` Eli Zaretskii
2023-06-04 14:47 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:55 ` Eli Zaretskii
2023-06-04 16:36 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 15:12 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 15:20 ` Eli Zaretskii
2023-06-04 15:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 16:15 ` Philip Kaludercic
2023-06-04 16:30 ` Eli Zaretskii
2023-06-04 16:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 17:37 ` Philip Kaludercic
2023-06-04 18:32 ` Eli Zaretskii
2023-06-04 16:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 18:40 ` Philip Kaludercic
2023-06-04 19:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-05 7:55 ` Philip Kaludercic
2023-06-05 14:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-07 15:36 ` Eli Zaretskii
2023-06-07 18:38 ` Philip Kaludercic
2023-06-07 19:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-08 9:26 ` Eli Zaretskii
2023-06-04 16:28 ` Eli Zaretskii
2023-06-04 15:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:54 ` Eli Zaretskii
2023-06-04 15:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 12:14 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 7:52 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 8:06 ` Eli Zaretskii
2023-06-04 8:43 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 8:54 ` Eli Zaretskii
2023-06-04 9:10 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 9:17 ` Philip Kaludercic
2023-06-04 10:16 ` Eli Zaretskii
2023-06-04 9:52 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-04 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 13:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-29 15:44 ` Евгений Бойков via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-05-30 2:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-03 8:37 ` Eli Zaretskii
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='CAKOwOe45eCkB=gKUCgMH3LoCJy1KrTijhOFk2WauDEJAH8ySAw@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=63757@debbugs.gnu.org \
--cc=artscan@list.ru \
--cc=monnier@iro.umontreal.ca \
/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).