Pacman

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.
Tasklist

FS#34388 - Package Integrety frequently fails on upgrade

Attached to Project: Pacman
Opened by thayne (ender4) - Wednesday, 20 March 2013, 20:08 GMT
Last edited by Allan McRae (Allan) - Tuesday, 16 July 2013, 00:08 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version 4.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

When updating using pacman -Syu during the past few weeks, I have frequently gotten the errors:

(17/17) checking package integrity [#########################################] 100%
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.


For one thing this doesn't tell me which package is invalid or corrupted. And it always seems to fail on the last package. Interestingly, I know at least twice it has said 17/17, and I can't remember how many packages it was the other times it has happened. Also, if I then run pacman again with --ignore <package-name> then it installs all the packages fine, and it doesn't seem to matter which package I tell it to ignore. I am really confused as to why this is happening.

Steps to Reproduce:

Run pacman -Syu, although it doesn't always happen, and I haven't figured out under what conditions it occurs.

I suspect that it may have something to do with the 17/17 packages thing, but I'm not sure.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 16 July 2013, 00:08 GMT
Reason for closing:  Works for me
Additional comments about closing:  Can not replicate.
Comment by Allan McRae (Allan) - Wednesday, 20 March 2013, 22:03 GMT
Have you run a memcheck on your system?
Comment by Daniel Wallace (gtmanfred) - Wednesday, 20 March 2013, 22:12 GMT
which mirror are you using? if it is us.leaseweb.net there is a bug report about them, lots of people come to #archlinux with this problem (usually about the signatures though)
Comment by thayne (ender4) - Thursday, 21 March 2013, 01:43 GMT
@Allan

what do you mean by memcheck?

@Daniel

the first few lines of my mirrorlist are:

Server = http://archlinux.supsec.org/$repo/os/$arch
Server = http://archlinux.surlyjake.com/archlinux/$repo/os/$arch
Server = http://cake.lib.fit.edu/archlinux/$repo/os/$arch
Server = http://mirrors.cat.pdx.edu/archlinux/$repo/os/$arch
Comment by Allan McRae (Allan) - Monday, 15 July 2013, 05:30 GMT
Because you can just --ignore any package and the upgrade will work, I suspect your computer has a memory issue. memcheck will test that.
Comment by thayne (ender4) - Monday, 15 July 2013, 20:02 GMT
I haven't had the problem since March. I still don't really know what caused it.

Loading...