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.
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.
FS#43586 - "invalid or corrupted package" - pacman should explicitly say what package is corrupted
Attached to Project:
Pacman
Opened by Damian Nowak (Nowaker) - Tuesday, 27 January 2015, 16:10 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 11 October 2019, 19:45 GMT
Opened by Damian Nowak (Nowaker) - Tuesday, 27 January 2015, 16:10 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 11 October 2019, 19:45 GMT
|
DetailsTotal Installed Size: 1044.97 MiB
Net Upgrade Size: 237.14 MiB :: Proceed with installation? [Y/n] (328/328) checking keys in keyring [####################################################] 100% (328/328) checking package integrity [####################################################] 100% error: failed to commit transaction (invalid or corrupted package) Errors occurred, no packages were upgraded. I probably can use --debug and find which package is corrupted, but that's extremely sub-optimal. pacman should explicitly say what package(s) are corrupted. |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Friday, 11 October 2019, 19:45 GMT
Reason for closing: Fixed
Additional comments about closing: https://git.archlinux.org/pacman.git/com mit/?id=192d6166e9cb2a8f26d7256690e0158b d5a5d226
Friday, 11 October 2019, 19:45 GMT
Reason for closing: Fixed
Additional comments about closing: https://git.archlinux.org/pacman.git/com mit/?id=192d6166e9cb2a8f26d7256690e0158b d5a5d226