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#7694 - -Ql on package doesn't work

Attached to Project: Pacman
Opened by Stefan O. (hybrid) - Saturday, 28 July 2007, 09:46 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 03 August 2007, 20:15 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture i686
Severity Very Low
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
pacman -Ql foo.pkg.tar.gz gives a "error: package "foo.pkg.tar.gz" not found.

Own interpretation:
It seems like, pacman only checks in the database.

Please tell me if I'm wrong, but "This can be run against the local package database or can be used on individual .tar.gz packages. [man pacman about -Q]" I would interpret as if it pacman should be able to perform a -Ql (for example) on a not installed package.
If I'm getting this wrong and that's not supported by pacman, please see it as a feature request. I sometimes want to see, what files a package contains and what directories it uses _before_ I install it.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 03 August 2007, 20:15 GMT
Reason for closing:  Won't implement
Comment by Dan McGee (toofishes) - Saturday, 28 July 2007, 12:37 GMT
Have you taken a look at the '-p' option? I think that is what you are missing.

pacman -Qlp foo.pkg.tar.gz
Comment by Stefan O. (hybrid) - Monday, 30 July 2007, 14:10 GMT
whoops, yeah, you're right, -p helps.
Even though I guess it would be nice if pacman could autodetect that (imo a check whether a path before the packagename has been entered and/or if the entered package name has a .pkg.tar.gz in the end would be enough to determine whether -p should be used or not. Or a construct like: -Qlp || -Ql )

But all that is definately not important at all, since -p works fine.
Comment by Aaron Griffin (phrakture) - Friday, 03 August 2007, 20:15 GMT
Checking the extension has quite a few problems. Considering it's generic and could be changed at build time to "foo" what happens if a package name legitimately ends with "foo"? If we check for an existing file, what happens if there's a file named "coreutils" in the current directory when -Ql'ing for coreutils.

This is exactly what the -p option is for, so I'm going to close this with a "Won't Implement" for now. We can revisit later - I'd suggest opening an Feature Request ticket for your request there.

Loading...