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#12778 - [pacman 3.2.2-1] pacman-optimize fails with pacman-cage
Attached to Project:
Pacman
Opened by solsTiCe (zebul666) - Tuesday, 13 January 2009, 14:54 GMT
Last edited by Dan McGee (toofishes) - Sunday, 04 October 2009, 14:12 GMT
Opened by solsTiCe (zebul666) - Tuesday, 13 January 2009, 14:54 GMT
Last edited by Dan McGee (toofishes) - Sunday, 04 October 2009, 14:12 GMT
|
DetailsSummary and Info:
when i try to run pacman-optimize while pacman-cage is running, pacman-optimize fail with this error ==> MD5sum'ing the old database... ==> Tar'ing up /var/lib/pacman... ==> Making and MD5sum'ing the new database... ==> Syncing database to disk... ==> Checking integrity... ==> Rotating database into place... mv: cannot move `/var/lib/pacman' to `/var/lib/pacman.old': Device or resource busy chmod: failed to get attributes of `/var/lib/pacman.old': No such file or directory chown: failed to get attributes of `/var/lib/pacman.old': No such file or directory ==> ERROR: New database substitution failed. Check for /var/lib/pacman, /var/lib/pacman.old, and /var/lib/pacman.new directories. Steps to Reproduce: use pacman-cage and then pacman-optimize. it was working nice with previous version of pacman. if i uncage pacman db (with pacman-uncage), pacman-optimize work again. i know that pacman-cage is not even available on aur so it is not supported _at ALL_ i use the version from http://repo.archlinux.fr/i686/pacman-cage/ but may be that bug might worth to look into. still no 3.2.2 version of pacman in here ? at the left |
This task depends upon
Closed by Dan McGee (toofishes)
Sunday, 04 October 2009, 14:12 GMT
Reason for closing: Won't fix
Additional comments about closing: See comments. Thanks for doing some bug day sweeping of these.
Sunday, 04 October 2009, 14:12 GMT
Reason for closing: Won't fix
Additional comments about closing: See comments. Thanks for doing some bug day sweeping of these.
I don't understand why you would want to use both. pacman-optimize tries to move all the files into a contiguous block on your hard drive. With pacman-cage, they are already in a loopbacked filesystem in a small contiguous file.
The reason this is failing is that we are trying to move the mount point that pacman-cage creates. I guess changing:
mv "$dbroot" "$dbroot.old" || fail=1
mv "$dbroot.new" "$dbroot" || fail=1
to
mv "$dbroot/*" "$dbroot.old" || fail=1
mv "$dbroot.new/*" "$dbroot" || fail=1
and cleaning up the left over $dbroot.new later would fix this but it seems pointless.
yes. i did not thought about that. but now that you mention it, i realise that's almost stupid.
i began to use pacman-cage once and continue to use pacman-optimizse as before. but i can see some difference after a pacman-optimise even with pacman-cage.
i think i'll stop to use one of them.