Welcome to the Pacman bug collection. 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 reproduceable test case whenever possible.
Tasklist

FS#8244 - No hint what package failed after -Syu when integrity check failed for one of these

Attached to Project: Pacman
Opened by Gerhard Brauer (GerBra) - Sunday, 07 October 2007, 08:59 GMT-5
Last edited by Dan McGee (toofishes) - Thursday, 08 November 2007, 23:33 GMT-5
Task Type Bug Report
Category Output
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture All
Severity Low
Priority Normal
Reported Version 3.0.6
Due in Version 3.1.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

[root@myhost ~]# LANG=C pacman -Suv
Root : /
DBPath : var/lib/pacman/
CacheDir : var/cache/pacman/pkg/
Targets : None
:: Starting full system upgrade...
resolving dependencies... done.
looking for inter-conflicts... done.

Targets: hwdetect-0.8-10 imagemagick-6.3.6.0-1 irssi-0.8.12-1 jre-6u3-1 kernel26-2.6.22.9-1 less-408-1 libpcap-0.9.8-1 libtheora-1.0beta1-1
pcre-7.4-1 ppp-2.4.4-5 sane-1.0.18-8 stalonetray-0.7.3-1 udev-115-2 unrar-3.7.8-1 vi-7.1.135-1 vim-7.1.135-1 wireshark-0.99.6-5

Total Package Size: 86.08 MB

Proceed with installation? [Y/n]
checking package integrity... done.
error: error while reading package: Unrecognized archive format: Invalid or incomplete multibyte or wide character
error: failed to commit transaction (libarchive error)

pacman does not say on **which** package the failure happened.
with strace i could see that on above situation it was the wireshark package.

This task depends upon

View Dependency Graph

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Thursday, 08 November 2007, 23:33 GMT-5
Reason for closing:  Fixed
Additional comments about closing:  Fixed in git
Comment by Aaron Griffin (phrakture) - Monday, 08 October 2007, 19:25 GMT-5
This one looks easy enough - just add some %s magic.

Adding to the release roadmap
Comment by Dan McGee (toofishes) - Monday, 08 October 2007, 22:26 GMT-5
Should be fixed in GIT, it was an easy addition to the error messages.

See commit 087b8df781fb...

Loading...