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#35812 - pacman should print replaces with "pacman -Sup"
Attached to Project:
Pacman
Opened by lieven moors (lievenmoors) - Sunday, 16 June 2013, 10:00 GMT
Last edited by Allan McRae (Allan) - Thursday, 05 May 2016, 03:53 GMT
Opened by lieven moors (lievenmoors) - Sunday, 16 June 2013, 10:00 GMT
Last edited by Allan McRae (Allan) - Thursday, 05 May 2016, 03:53 GMT
|
DetailsI use the command "pacman -Sup" to get the updates for a computer without internet. But it doesn't deal with replaces. I heard --noconfirm is implied when you use the "--print". So in my opinion it would make sense that "pacman -Sup" would print out _all_ the packages that would have been downloaded with "pacman -Syu --noconfirm" (assuming the database files are up-to-date). That would mean it would print out replaces and new dependencies of those as well.
|
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 05 May 2016, 03:53 GMT
Reason for closing: Implemented
Additional comments about closing: git commit 3ed57be4
Thursday, 05 May 2016, 03:53 GMT
Reason for closing: Implemented
Additional comments about closing: git commit 3ed57be4
when running in --print mode? Wouldn't that overide the alpm defaults for all other events? Also, I would be interested
to know where or how those alpm default values would be set...
Sorry, I'm not at all familiar with the pacman codebase, so any help would be appreciated.