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#7162 - Pacman should delete corrupt packages or at least say what was corrupt
Attached to Project:
Pacman
Opened by Xilon (Xilon) - Monday, 14 May 2007, 16:06 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 14 May 2007, 18:42 GMT
Opened by Xilon (Xilon) - Monday, 14 May 2007, 16:06 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 14 May 2007, 18:42 GMT
|
DetailsWhen a package is corrupt and you try to install it pacman only notifies you that _a_ package is corrupt. In my opinion pacman should either automatically remove the package (who needs a corrupt package?) or prompt the user what to do with it. The very least it could do is tell you which package was corrupt so you can manually delete it instead of doing a pacman -Scc or something.
Attatched is a log of pacman trying to update the system. I had problems downloading the abiword package, I guess that's what got corrupt. as you can see pacman isn't being very suggestive as to what was corrupt. |
This task depends upon
pacman.log
As for 2nd variant - see http://bugs.archlinux.org/task/7151 and http://bugs.archlinux.org/task/7155