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#49255 - [pacman] Files aren't registered properly when installation aborts due to full disk
Attached to Project:
Pacman
Opened by mirh (mirh) - Saturday, 07 May 2016, 18:34 GMT
Last edited by Allan McRae (Allan) - Sunday, 08 May 2016, 09:06 GMT
Opened by mirh (mirh) - Saturday, 07 May 2016, 18:34 GMT
Last edited by Allan McRae (Allan) - Sunday, 08 May 2016, 09:06 GMT
|
DetailsSummary and Info:
I was installing from the aur installer mathematica, which as you might know is a quite big software suite (more than 7GB). I forget to previously check for free space and I end up with "can't write" errors, or something along that. I removed it, and expanded a bit the root partition. When I proceeded to reinstall it, I got errors due to old files from previous attempt (log attached). This shouldn't have happened (and I don't think -R is to blame). I wonder if it couldn't be related to Steps to Reproduce: 1) Install a package bigger than available free space (wait for errors to spawn) 2) Pacman -R package 3) Free additional space (so there's enough) 4) Install the thing again 
mathematicalog
(4.5 KiB)
|
This task depends upon
Closed by Allan McRae (Allan)
Sunday, 08 May 2016, 09:06 GMT
Reason for closing: Not a bug
Additional comments about closing: Use CheckSpace.
Sunday, 08 May 2016, 09:06 GMT
Reason for closing: Not a bug
Additional comments about closing: Use CheckSpace.
Besides, I'm not complaining about pacman not realizing it could have never completed the task (that could deserve another ticket perhaps?)
.. but more about pacman failing to fully remove the package.
When you filled the filesystem, pacman could not not store the list of files for that package. There is no way for it to remove the files in that state.