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#35524 - Negative Download Size

Attached to Project: Pacman
Opened by JWC (jwcxz) - Wednesday, 29 May 2013, 06:03 GMT
Last edited by Allan McRae (Allan) - Wednesday, 29 May 2013, 08:07 GMT
Task Type Bug Report
Category Output
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Recently, I upgraded a system that had not been upgraded recently. There were an enormous amount of updates (upwards of 800 packages). The result of running pacman -Syu was a negative download size! It ended up downloading all the packages and updating just fine. I have not been able to reproduce this type of failure since then.


Steps to Reproduce:
Unknown, other than to upgrade a very large amount of packages, possibly (i.e. I haven't been able to confirm that this is indeed the root cause).
   pacman-download-wtf.png (5.9 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 29 May 2013, 08:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  Was fixed in 4.1.1
Comment by Allan McRae (Allan) - Wednesday, 29 May 2013, 06:10 GMT
What pacman version were you using?
Comment by JWC (jwcxz) - Wednesday, 29 May 2013, 06:31 GMT
Oh shoot, I missed the pacman upgrade line. The version of pacman used on that operation was 4.1.0-2. Was the problem resolved between then and 4.1.1-1?

Edit: I'm betting that https://projects.archlinux.org/pacman.git/commit/?id=b5a7734a7ecdd35f64f33eeed5252423ca005fd2 was the culprit, which has since been fixed by the 4.1.1 release.

Loading...