From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 37976@debbugs.gnu.org, Terje Larsen <terlar@gmail.com>
Subject: bug#37976: 27.0.50; Dependency reversal of seq-subseq and cl-subseq causes regression when using seq from ELPA
Date: Tue, 12 Nov 2019 17:26:41 -0500 [thread overview]
Message-ID: <jwva790ka3y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87h83exny5.fsf@web.de> (Michael Heerdegen's message of "Fri, 08 Nov 2019 18:44:34 +0100")
>> What ended up happening now is that Emacs is using the new builtin cl-subseq
>> from cl-extra.
This new cl-subseq only exists in Emacs's `master`, right?
So they're running Emacs `master`.
>> But using seq-subseq from MELPA which causes an infinite
>> loop as they depend on eachother.
Why would they use "seq-subseq from MELPA" when they have the latest
seq.el built into their Emacs `master`?
>> What is the recommended way to solve this issue? I am not controlling
>> using seq from MELPA since I am using a package that pulls in seq from
>> MELPA as a dependency. For now I am considering to patch the seq in
>> MELPA.
Could we have some more data, such as which package (name and version)
pulls which version of `seq` (and how does it say "from MELPA")?
Stefan "¡¿why on earth would you put `seq` on MELPA?!"
next prev parent reply other threads:[~2019-11-12 22:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 10:15 bug#37976: 27.0.50; Dependency reversal of seq-subseq and cl-subseq causes regression when using seq from ELPA Terje Larsen
2019-11-04 9:21 ` Michael Heerdegen
2019-11-05 6:14 ` Terje Larsen
2019-11-08 17:44 ` Michael Heerdegen
2019-11-12 22:26 ` Stefan Monnier [this message]
2019-11-13 11:30 ` Terje Larsen
2019-11-13 13:42 ` Stefan Monnier
2019-11-15 19:20 ` John Wiegley
2019-11-15 19:56 ` Stefan Monnier
2020-08-25 23:32 ` 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=jwva790ka3y.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=37976@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=terlar@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).