unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Fri, 08 Nov 2019 18:44:34 +0100	[thread overview]
Message-ID: <87h83exny5.fsf@web.de> (raw)
In-Reply-To: <CAGoWm-YGqBxZ9Wq+aHE9XAeRcn=QKVH751GjpD-X=r2_NeAPwA@mail.gmail.com> (Terje Larsen's message of "Tue, 5 Nov 2019 07:14:26 +0100")

Hi Stefan,

is this issue on your radar?

Terje Larsen <terlar@gmail.com> writes:

> I meant the seq package provided by GNU ELPA repository. Guess I
> slipped on the keyboard there. My Emacs selects the seq25.el from
> ELPA.

His original report:

> Since the commit 0e4dd67aae8b10032317a29a6bd99d2d4a64c897 there is a
> regression for people using seq from MELPA.

> The dependency was reversed so cl-subseq is using seq-subseq, but before
> seq-subseq was using cl-subseq.

> What ended up happening now is that Emacs is using the new builtin cl-subseq
> from cl-extra. But using seq-subseq from MELPA which causes an infinite
> loop as they depend on eachother.

> 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.


TIA,

Michael.





  reply	other threads:[~2019-11-08 17:44 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 [this message]
2019-11-12 22:26       ` Stefan Monnier
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=87h83exny5.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=37976@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).