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#65431 - pacman does not see an update if the newer version of the package is in the new repo
Attached to Project:
Pacman
Opened by Alex (__AlexL__) - Sunday, 09 February 2020, 09:01 GMT
Last edited by Allan McRae (Allan) - Sunday, 09 February 2020, 10:46 GMT
Opened by Alex (__AlexL__) - Sunday, 09 February 2020, 09:01 GMT
Last edited by Allan McRae (Allan) - Sunday, 09 February 2020, 10:46 GMT
|
DetailsSummary and Info:
pacman does not see an update if the newer version of the package is in the new repo. For example: now I have autoconf-2.69-6 installed. core has autoconf-2.69-6 extra has autoconf-2.69-7 But pacman -Syu updates nothing. Steps to Reproduce: have autoconf-2.69-6 installed execute pacman -Syu |
This task depends upon
You should probably file a bug against core instead.
If these packages have the same versions the user must be asked about his/her preference and if there is the one with higher version then this one must be treated as a update.
You just don't want fixing this.