Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#43334 - show originating repository name in pacman -Q -i

Attached to Project: Pacman
Opened by Ido Rosen (idorosen) - Monday, 05 January 2015, 02:14 GMT
Last edited by Allan McRae (Allan) - Sunday, 04 December 2022, 08:11 GMT
Task Type Feature Request
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.2.0
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:
pacman -Q -i <pkgname> does not show the repository that the package was installed from, whereas pacman -S -i <pkgname> does show the repository that it'd be synced from. This is a feature request to help make managing custom / on-site repositories easier.

Steps to Reproduce:
pacman -Q -i rsync
pacman -S -i rsync
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 04 December 2022, 08:11 GMT
Reason for closing:  Won't implement
Additional comments about closing:  Various options are available to achieve the intended outcomes.
Comment by Allan McRae (Allan) - Monday, 05 January 2015, 02:26 GMT
If I install a package while it is in [testing] and then it gets moved to [core], which repository should it report?
Comment by Ido Rosen (idorosen) - Monday, 05 January 2015, 02:54 GMT
Good motivating example, another one might be [community] -> [extra] (pkgver/pkgrel may have remained the same while the PKGBUILD changes). In your example, I think -Q should report testing, -S should report core (since it's displaying info for the package in the repo db, not in the installed pkgs db).
Comment by Allan McRae (Allan) - Monday, 05 January 2015, 03:22 GMT
But then if I "pacman -S <pkg>" again, it will now report [core]. Exactly the same package and files, different metadata.
Comment by Allan McRae (Allan) - Monday, 05 January 2015, 03:23 GMT
Perhaps if you gave an example of what you are trying to achieve, I can understand what information is needed.
Comment by Ido Rosen (idorosen) - Monday, 05 January 2015, 03:28 GMT
I have multiple repositories that can provide the same package with the same pkgver/pkgrel, and need to know (e.g. in a puppet module, in my cfg mgmt, etc.) what the installed version is. This is especially important when migrating a host from production<->staging repositories, for example. It's really exactly as described: I want to know where the installed package came from, not just what it's name and version are. The packages might differ between the repositories (locally applied patches, remotely differing PKGBUILDs but same pkgver/pkgrels, etc.). The installed package metadata should carry the repository name that it was downloaded/installed from when cached in the pacman local db, since it carries pretty much everything else already.
Comment by Ido Rosen (idorosen) - Monday, 05 January 2015, 03:30 GMT
For context: I have production (frozen-in-time with security and performance patches only, 6 monthly update cycle), staging (testing for production-next), and upstream mirror (aka archlinux) package repositories/dbs. This is for a deployment of a bunch of ArchLinux-based machines for which just following Arch repos directly would be hazardous to uptime.
Comment by Allan McRae (Allan) - Monday, 05 January 2015, 03:57 GMT
I think that you should be using a different version to signify different package versions. You could also use the "packager" field if that was not suitable.

I am fairly sure we have rejected a similar request before. I'll leave this open, but it is very low on the priority list.
Comment by Ido Rosen (idorosen) - Monday, 05 January 2015, 04:04 GMT
If I did it myself and submitted a patch, would that make it more likely to happen sooner? (I won't have time for about a month to do this myself, it's on my low priority wishlist.)
Comment by Allan McRae (Allan) - Monday, 05 January 2015, 04:06 GMT
Yes - but I'd strongly advise discussion of the feature on the pacman-dev mailing list first to judge whether it would be accepted.

I'd also suggest that it is only shown as additional information in -Qii output.

Loading...