Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.

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) - Friday, 12 February 2016, 13:55 GMT
Task Type Bug Report
Category Output
Status Assigned
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.3
Due in Version 5.1.0
Due Date Undecided
Percent Complete 0%
Votes 0
Private No


When pacman aborts part way through a transation, it print this message, but some packages have been upgraded...
This task depends upon

Comment by Carl Schaefer (crs) - Sunday, 08 June 2014, 21:54 GMT
this bug is still present in 4.1.2-6

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.
Comment by Allan McRae (Allan) - Sunday, 08 June 2014, 21:59 GMT
All file conflicts are fixed in the git version.