FS#18827 - Failures in upgrading packages should be directed to pacman.log

Attached to Project: Pacman
Opened by Vlad George (DonVla) - Thursday, 25 March 2010, 11:56 GMT
Task Type Feature Request
Category Output
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Summary and Info:
Problems with package upgrades, like file conflicts, should be logged to pacman.log.

BTW: a more verbose pacman.log would be nice.
For now only very general messages like:
"> starting full system upgrade
> synchronizing package lists"
are stated.
"...
checking package integrity...
(8/8) checking for file conflicts 100%
error: failed to commit transaction (conflicting files)
cups: /etc/cups/printers.conf exists in filesystem
cups: /etc/cups/subscriptions.conf exists in filesystem
Errors occurred, no packages were upgraded."
There is actually a file conflict problem, but the log file didn't show anything.
This task depends upon

Comment by Allan McRae (Allan) - Saturday, 09 February 2013, 04:47 GMT
Related to more verbose logging requested in FS#28475 - needs something like a VerboseLog option to be added.

Loading...