From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Terje Larsen Newsgroups: gmane.emacs.bugs Subject: bug#37976: 27.0.50; Dependency reversal of seq-subseq and cl-subseq causes regression when using seq from ELPA Date: Wed, 13 Nov 2019 12:30:28 +0100 Message-ID: <878sok9for.fsf@gmail.com> References: <87o8xz3ljd.fsf@gmail.com> <87h83k2e0i.fsf@web.de> <87h83exny5.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="132341"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Michael Heerdegen , 37976@debbugs.gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Nov 13 12:31:22 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iUqrp-000YFi-IC for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Nov 2019 12:31:21 +0100 Original-Received: from localhost ([::1]:43122 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iUqrm-0005qe-N4 for geb-bug-gnu-emacs@m.gmane.org; Wed, 13 Nov 2019 06:31:19 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58392) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iUqrX-0005of-TG for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 06:31:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iUqrW-0003pX-N2 for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 06:31:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:50048) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iUqrW-0003pM-JR for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 06:31:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iUqrW-0001uv-F0 for bug-gnu-emacs@gnu.org; Wed, 13 Nov 2019 06:31:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Terje Larsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Nov 2019 11:31:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37976 X-GNU-PR-Package: emacs Original-Received: via spool by 37976-submit@debbugs.gnu.org id=B37976.15736446527353 (code B ref 37976); Wed, 13 Nov 2019 11:31:02 +0000 Original-Received: (at 37976) by debbugs.gnu.org; 13 Nov 2019 11:30:52 +0000 Original-Received: from localhost ([127.0.0.1]:58869 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iUqrM-0001uX-Hm for submit@debbugs.gnu.org; Wed, 13 Nov 2019 06:30:52 -0500 Original-Received: from mail-lj1-f181.google.com ([209.85.208.181]:46031) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iUqrJ-0001uI-0Q for 37976@debbugs.gnu.org; Wed, 13 Nov 2019 06:30:51 -0500 Original-Received: by mail-lj1-f181.google.com with SMTP id n21so2123707ljg.12 for <37976@debbugs.gnu.org>; Wed, 13 Nov 2019 03:30:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=bL7Q+qxQdMJZVC1qqtbqjaEV/fB/IR5dLJe/ls75HH8=; b=M6Cm3p7kvy7nBrxmfwxg7Kvwi/JL8LC//DP/hIsm91djFhgmSFnaYYlClyJTAgb25a 0cXkqwUPfmFgbZ4gOnMz7Lp9wBDT2X7XZrypbOUEX2CfPE4fg7nrmNa+lSY3eCOC5RJR x3GfkBVwM5n0oAZxikHAihbPuDYNyR1rThS1BHIo6W0siVVBkXdpNZfvIHaIRunSHBXr PfNiGRXd66/1BUMpQJdlK3NlWpFXK6LnHMl/1WwbTXc3i7psTQ0lt5WtqdB1fmH9PXYc JO9W3MjVfwhV3kD+7CLxMjKp4EYQs7cGcQS6Gb3/cVtxjZimZTmy7YAUx2aZEOkO5ngF eB4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=bL7Q+qxQdMJZVC1qqtbqjaEV/fB/IR5dLJe/ls75HH8=; b=OjMQMd64harHX2dYuPnf9RePlXXKBX+UB9FScun5QhkFO7fIO+M/17llTsU72bSkAn ajXjRtClnIDuZnM7ypG5QNS/oJAoK5zN17qYG7Rf4nZFg/6TMglMs2cghayCi3XTVceq aoDK+LO2zr1ov/yT9qOYf81Who9AMTvRcDVxeIoKUQpyC5cLnssd1GQiwH7AUcOkp9CJ mr8D5f2Eo3k/ItavzYlY9dATnBKGvtBN9wVU9qJQjlieshVMTHV/uvaNt/6IFAYNZQmz QTPDXiVriylKOyRh7Y0kQFy7gkApNiM7O/bPTfnuCZBBa/6GupxUCDE/MIdELXT9zdmI b/gg== X-Gm-Message-State: APjAAAUvJEGzJG7rBHvrdfRxyn3FOzLd2w5nyXvqFGgpIVL0mrT6iknP +NUAo9PtK3EDBAn6GA09TQ6UPdLWBTU= X-Google-Smtp-Source: APXvYqxH4UkflJbxL2Ugp9N5JYMwkT7A4nM8GoqFSE9BOZVrduyBZ149U3Nw2DKbiZa9gGNgUYjKTQ== X-Received: by 2002:a2e:7607:: with SMTP id r7mr2283183ljc.37.1573644642447; Wed, 13 Nov 2019 03:30:42 -0800 (PST) Original-Received: from beetle ([212.85.78.250]) by smtp.gmail.com with ESMTPSA id g14sm937387lfj.17.2019.11.13.03.30.40 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 13 Nov 2019 03:30:41 -0800 (PST) In-Reply-To: (Stefan Monnier's message of "Tue, 12 Nov 2019 17:26:41 -0500") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:171489 Archived-At: Stefan Monnier writes: >>> What ended up happening now is that Emacs is using the new builtin cl-s= ubseq >>> from cl-extra. > > This new cl-subseq only exists in Emacs's `master`, right? > So they're running Emacs `master`. > Yes, as mentioned, this is Emacs from `master`, since commit `0e4dd67aae8b1= 0032317a29a6bd99d2d4a64c897`. >>> 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`? > I am sorry to have written MELPA, but I meant ELPA. I think you can reproduce this by installing `seq` from ELPA via package-install, which Emacs clearly marks as an older version, so that would be questionable. But is it that unlikely that you somehow would have the `seq` from ELPA on your `load-path`? >>> 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")? > In ELPA there are not that many packages that depend on seq, but there is for example `beacon` which depends on `(seq "2.14")`. In MELPA there is a lot, for example `org-drill` which also depends on `(seq "2.14")`. However I think `seq` won't be pulled from ELPA for these since the dependency is already satisfied by the built-in version. I am using NixOS and I think this issue comes from nix and how it resolves packages. Nix will resolve Emacs package dependencies on a system level and make sure all of them are added to your `load-path` when launching Emacs. The unfortunate thing is that if a package depends on `seq`, it pulls the one from ELPA since it doesn't know about the built-in package in Emacs. I will raise this issue on the nixpkgs instead, as it is less likely that non-nix users will have the ELPA `seq` on their `load-path`. > > Stefan "=C2=A1=C2=BFwhy on earth would you put `seq` on MELPA?!" No-one put seq on MELPA, it was ELPA all-along, once again sorry for that mistake. Thank you for your reply and if you don't think anything needs to be done on Emacs/ELPA side, feel free to close this issue.