You are not logged in.
Pacman -Syu downloaded the following packages but hangs at "checking package integrity"
[root@n6re ~]# pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
Targets (20): apr-1.3.9-1 db-4.8.24-1 apr-util-1.3.9-3 python-2.6.3-1
dbus-python-0.83.0-2.1 gavl-1.1.1-2 perl-5.10.1-3
groff-1.20.1-3 heimdal-1.2.1-7 libical-0.44-1 libmtp-0.3.7-1.1
libsasl-2.1.23-2 pam-1.0.4-2 qt-4.5.3-2 rdesktop-1.6.0-3
redland-1.0.9-4 soprano-2.3.1-1 subversion-1.6.5-5
system-config-printer-common-1.1.13-1 vorbis-tools-1.2.0-4
Total Download Size: 0.00 MB
Total Installed Size: 286.37 MB
Proceed with installation? [Y/n] y
checking package integrity...
This printout resulted after canceling the download and restarting pacman -Syu. Thus the same failure occurs after the original download failure of the same type.
What causes this failure mode?
Last edited by lilsirecho (2009-10-04 22:19:44)
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
After ten minutes the cause for the "hang" was corrupted python download.
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
No wait, this looks like a bug. This shouldn't happen, because pacman should warn you about corrupted download. Why should it "hang"? I've faced this as well, but couldn't pinpoint the exact situation. So far, it seems random.
edit: ok nevermind, i forgot new pacman has yet to roll out.
Last edited by schivmeister (2009-10-05 20:52:13)
I need real, proper pen and paper for this.
Offline
Mine took a whole 10 minutes to spit out...:
checking package integrity...
:: File go-openoffice-3.1.1.3-1-x86_64.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n]
... today.
I guess, this shouldn't happen... but then again, I guess, I really really shouldn't have the machine hibernate while pacman is downloading .
Offline
Mine took a whole 10 minutes to spit out...:
checking package integrity... :: File go-openoffice-3.1.1.3-1-x86_64.pkg.tar.gz is corrupted. Do you want to delete it? [Y/n]
... today.
I guess, this shouldn't happen... but then again, I guess, I really really shouldn't have the machine hibernate while pacman is downloading .
No it should not happen, this is the same bug.
I guess either when you suspended or resumed, your network was down at some point, so libfetch returned -1 and triggered the infamous pacman bug.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
Wow, this hit me too... Rebooted just for kicks & had to fsck, possibly unrelated. Anyway, got a wild hair & moved /var/cache/pacman/pkg to /var/cache/pacman/OLD_pkg & re-ran pacman -Syu, things are going great now. So I figured there must be something rotten in the old pkg directory. I checked & found out the old one was 182G, what the crap! so then I did:
du -h /var/cache/pacman/OLD_pkg/* | sort -h
and the winner is:
177G /var/cache/pacman/OLD_pkg/kdegames-kblocks-4.3.2-1-x86_64.pkg.tar.gz
Good grief! So I imagine that file was corrupted in some fashion, anyway it's heading to /dev/null... Maybe other folks can check for stuff like that too?
OK I waited to make sure pacman ran OK, things look cool.
VincentV
Somewhere in J-Pop Heaven...
Offline