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.
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.
FS#16292 - Searching in the desired repository
Attached to Project:
Pacman
Opened by Laszlo Papp (djszapi) - Sunday, 20 September 2009, 20:59 GMT
Last edited by Allan McRae (Allan) - Monday, 21 September 2009, 11:07 GMT
Opened by Laszlo Papp (djszapi) - Sunday, 20 September 2009, 20:59 GMT
Last edited by Allan McRae (Allan) - Monday, 21 September 2009, 11:07 GMT
|
DetailsHello!
It would be great if pacman could handle search session in the desired repository. Example usage: 1. pacman -Ss --repo core -> it gives back the available packages from core. 2. pacman -Qs --repo extra -> it gives back the installed packages from extra Implementation: 1. Maybe the first is simplier because we know the database/repo name 2. It's hard because I can't find anywhere where it stores the original repo Thanks in advance! |
This task depends upon
Closed by Allan McRae (Allan)
Monday, 21 September 2009, 11:07 GMT
Reason for closing: Not a bug
Additional comments about closing: Use "-Sl"
Monday, 21 September 2009, 11:07 GMT
Reason for closing: Not a bug
Additional comments about closing: Use "-Sl"
pacman -Ss kernel26 | grep -A1 "^repo/"
2) what does the original repo matter? e.g. I install a package from [testing] and it is then moved to [extra]. Which repo is it from?
pacman -Ss | grep ^community | sed -e 's/community\///g' -e 's/\ .*//g'
pacman -Ss | grep ^core | sed -e 's/^[^/]*\/\([^[:space:]]*\)[[:space:]].*$/\1/'
^^ it would be better with this to get just the packagename, like in case of implemented -Qt option e.g, you get there the package names too. But with this long command ,it's not so easy with one exact option :)
@Dan: Yeah, you're right with -Qs, maybe it can't be solved well.
pacman -Sl core
pacman -Sql core
paclist core (from pacman-contrib)