GNU bug report logs - #36637
Package buffer should show where (which archive) a package is installed from

Previous Next

To reply to this bug, email your comments to 36637 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: bug-gnu-emacs <at> gnu.org
Subject: Package buffer should show where (which archive) a package is
 installed from
Date: Sat, 13 Jul 2019 14:14:21 +0200

It would be good if there was an indication in the "*Packages*" buffer of where
(what archive) you have installed a package from.

I have added both MELPA and MELPA Stable to `package-archives':

    (add-to-list 'package-archives
                 '("melpa" . "https://melpa.org/packages/") t)
    (add-to-list 'package-archives
                 '("melpa-stable" . "https://stable.melpa.org/packages/") t)

I sometimes install packages from gnu (ELPA), sometimes from melpa and sometimes
from melpa-stable.

The package "ivy" is available from all three archives.  After installing the
package from gnu, when I run M-x package-list-packages, I see in the "*Package*"
buffer the following two entries (although not next to each other):

  ivy                20190709.740  available  melpa      Incremental
Vertical completYon
  ivy                0.11.0        installed             Incremental
Vertical completYon

From this, I can figure out that I have not installed it from melpa (its status
is "available").  But I cannot easily know if I installed it from gnu or from
melpa-stable, or if it's available from only one or from both of them.

In this case, the versions on melpa-stable and gnu matches.  (Or, at least, the
version number does.)  But this just happens to be the case here.  Often, the
package does not even exist on gnu, and I wouldn't know that from the above.

It would be good if the second of the above two lines would be this instead:

  ivy                0.11.0        installed  gnu        Incremental
Vertical completYon

It would be even better if the describe-package buffer would also would show the
same information.

Thanks,
Stefan Kangas

Message #14 received at 36637 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Kangas <stefan <at> marxist.se>
Cc: 27601 <at> debbugs.gnu.org, 36637 <at> debbugs.gnu.org
Subject: Re: bug#27601: 25.2; Repository is not shown in the *Packages*
 buffer for installed packages
Date: Wed, 11 Aug 2021 16:54:33 +0200

Stefan Kangas <stefan <at> marxist.se> writes:

> The package "ivy" is available from all three archives.  After installing the
> package from gnu, when I run M-x package-list-packages, I see in the "*Package*"
> buffer the following two entries (although not next to each other):
>
>   ivy                20190709.740  available  melpa      Incremental
> Vertical completYon
>   ivy                0.11.0        installed             Incremental
> Vertical completYon

I guess the problem here is that we apparently don't save the archive in
`package-alist' when packages are installed?  Is there any particular
reason for that?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #17 received at 36637 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 27601 <at> debbugs.gnu.org, 36637 <at> debbugs.gnu.org
Subject: Re: bug#27601: 25.2; Repository is not shown in the *Packages* buffer
 for installed packages
Date: Tue, 24 Aug 2021 16:33:23 +0200

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> I guess the problem here is that we apparently don't save the archive in
> `package-alist' when packages are installed?  Is there any particular
> reason for that?

Yes, this is basically the problem.  AFAICT, there is no particular
reason for this, so it should mostly just be a matter of implementing
it.

I didn't consider recording it in package-alist, but I suppose it
could make sense.  I'd hope we can find a clean and preferably
backwards-compatible way of doing it.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.