From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.bugs Subject: bug#71356: use-package doesn't load org from elpa Date: Thu, 06 Jun 2024 06:15:44 +0000 Message-ID: <87ed9abnqn.fsf@posteo.net> References: <86plsvk57o.fsf@gnu.org> <86ed9aip6z.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6882"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71356@debbugs.gnu.org, acorallo@gnu.org, Pedro Andres Aranda Gutierrez To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 06 08:25:09 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sF6Yd-0001ZB-Fr for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 06 Jun 2024 08:25:07 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sF6YL-0000tF-EO; Thu, 06 Jun 2024 02:24:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sF6YK-0000ss-2h for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 02:24:48 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sF6YJ-0001Ba-QO for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 02:24:47 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sF6YY-00016X-6f for bug-gnu-emacs@gnu.org; Thu, 06 Jun 2024 02:25:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Philip Kaludercic Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 06 Jun 2024 06:25:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71356 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 71356-submit@debbugs.gnu.org id=B71356.17176550654140 (code B ref 71356); Thu, 06 Jun 2024 06:25:02 +0000 Original-Received: (at 71356) by debbugs.gnu.org; 6 Jun 2024 06:24:25 +0000 Original-Received: from localhost ([127.0.0.1]:41724 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sF6Xx-00014f-05 for submit@debbugs.gnu.org; Thu, 06 Jun 2024 02:24:25 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]:51087) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sF6Xu-00014C-0A for 71356@debbugs.gnu.org; Thu, 06 Jun 2024 02:24:22 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id E077E240027 for <71356@debbugs.gnu.org>; Thu, 6 Jun 2024 08:15:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1717654545; bh=Vs1HndreLsWF8RielJK2JtaFL4Sg5mBZ5r+xkANlXCY=; h=From:To:Cc:Subject:OpenPGP:Date:Message-ID:MIME-Version: Content-Type:From; b=FAjSfThfqF5diqXPrWyrdlfP64hqC26zRD4m5mHMOzCLKqFjPgs+okZ+lgUjxmsON qLgr9hZAoB6GTA7JEVq5T9YSToFc83MTMQT8HVNEE2SJxkI7C16r8Fvgq1l8E3tUrb qULoH2if9JpBnalirbxRZ5S55qfWullyt9CIPAYTP7PV7wqb/hT/lktxsxhFSCIM6f GAOJ+r4mMTp5aVTn159wKBIN9Q/fRGloLZ/lj9JOLHSlRKzFYTi06F1OTxXnMZq5Hq sujuOIL6XMzyF3Wecn6ZRKS4gHzSYQgUqLXEvGEZz8Z5zvUkh10aFFp/kL/eyw/apJ RQexF2QQVUcvw== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4VvvG85hJdz9rxG; Thu, 6 Jun 2024 08:15:44 +0200 (CEST) In-Reply-To: <86ed9aip6z.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 06 Jun 2024 09:02:28 +0300") OpenPGP: id=7126E1DE2F0CE35C770BED01F2C3CC513DB89F66; url="https://keys.openpgp.org/vks/v1/by-fingerprint/7126E1DE2F0CE35C770BED01F2C3CC513DB89F66"; preference=signencrypt X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:286659 Archived-At: Eli Zaretskii writes: >> From: Pedro Andres Aranda Gutierrez >> Date: Thu, 6 Jun 2024 07:46:31 +0200 >> Cc: Eli Zaretskii , Philip Kaludercic , 71356@debbugs.gnu.org >> >> Andrea is right. Reading through all the documentation, I implied >> that use-package would upgrade built-in packages if I pinned them to an archive >> and I :ensure'd them. >> >> Use case: want to upgrade org from the 9.6.x version packaged with master to the >> 9.7.x version available in elpa. >> >> Maybe this is more a FR and if so, we could move this to the list and have an informed >> discussion there. > > I'd like to hear from Philip. If use-package just uses package.el, > then the behavior is expected. Sorry for the delayed response; I don't think that has to be expected. While use-package can utilise package.el for package management, my impression is that it is at liberty to be more flexible/declarative. > Do you have package-install-upgrade-built-in set non-nil? If not, can > you set it non-nil and try the recipe again? I have tried it out myself, and it doesn't appear to do anything. The issue looks like that `package-installed-p' doesn't respect package-install-upgrade-built-in or :pin. > As for a feature request: what exactly is the feature requested here? > Are you saying that use-package should automatically upgrade built-in > packages? If so, I don't think this will fly, since it would mean > inconsistencies with package-install. IIUC the feature would be that if a use-package form has a :pin gnu argument, then this is an indication that we want to install the package from GNU ELPA, disregarding the fact that Emacs already has a built-in version of the same package. Sort of a package-local version of `package-install-upgrade-built-in'. I am not familiar with the use-package code, but it seems like we could implement this generally in package-install, by checking `package-pinned-packages'. -- Philip Kaludercic on peregrine