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#44942 - Pacman miserably handles ENOSPC
Attached to Project:
Pacman
Opened by Alexandre Bique (babali) - Tuesday, 12 May 2015, 09:51 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 12 May 2015, 17:46 GMT
Opened by Alexandre Bique (babali) - Tuesday, 12 May 2015, 09:51 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 12 May 2015, 17:46 GMT
|
DetailsHi,
It seems that pacman do not handle well a full disk. A friend did install go from pacman, and the installation went wrong with tons of errors like: error: could not extract usr/lib/go/src/go/doc/testdata/error2.2.golden (Write to restore size failed) And then pacman considered go successfully installed but it was not! She had to remove go with pacman -R and then cleanup the files by hand on the disk to really uninstall go. Thanks for having a look! |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 12 May 2015, 17:46 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#37402
Tuesday, 12 May 2015, 17:46 GMT
Reason for closing: Duplicate
Additional comments about closing:
What filesystem was the install using?
Was the CheckSpace option enabled in pacman.conf?
Sorry it is not very detailed :/
If there are not enough information to start checking some execution path, then we can close the bug.
Thanks!