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#33076 - Misleading message: "Errors occurred, no packages were upgraded"
Attached to Project:
Pacman
Opened by Allan McRae (Allan) - Thursday, 13 December 2012, 11:03 GMT
Last edited by Allan McRae (Allan) - Tuesday, 29 December 2020, 13:37 GMT
Opened by Allan McRae (Allan) - Thursday, 13 December 2012, 11:03 GMT
Last edited by Allan McRae (Allan) - Tuesday, 29 December 2020, 13:37 GMT
|
DetailsWhen pacman aborts part way through a transation, it print this message, but some packages have been upgraded...
|
This task depends upon
steps to reproduce:
change /usr/local/share/man to be a real directory and then upgrade "filesystem". You're likely to see:
warning: /etc/passwd installed as /etc/passwd.pacnew
warning: /etc/group installed as /etc/group.pacnew
error: extract: not overwriting dir with file /usr/local/share/man
error: problem occurred while upgrading filesystem
error: could not commit transaction
error: failed to commit transaction (transaction aborted)
Errors occurred, no packages were upgraded.
The last two lines are wrong: the upgrade of "filesystem" did in fact take place, and pacman may have upgraded other packages before "filesystem".
At least those messages should be changed to be accurate, but also this particular problem could be avoided if pacman would check for it during the "checking for file conflicts" phase.