Johannes Graumann wrote: > The current un-installability of git-core: > Unpacking git-core (from .../git-core_1%3a1.5.3.6-1_amd64.deb) ... > dpkg: error processing > /var/cache/apt/archives/git-core_1%3a1.5.3.6-1_amd64.deb (--unpack): > trying to overwrite `/usr/share/perl5/Error.pm', which is also in package > liberror-perl > Errors were encountered while processing: > /var/cache/apt/archives/git-core_1%3a1.5.3.6-1_amd64.deb > > results in apt being stuck in the pre-action handle of etckeeper without any > error indication. > etckeeper should test whether git works properly and leave it to the user > whether to live without > git's functionality or abort apt/aptitude all together in case of failure.
I ran 6 upgrades of machines using etckeeper yesterday, encountered the git upgrade bug on all of them, and did not see any hang or other bad behavior from etckeeper. I don't see how the git bug could keep git from working properly, or how, if git doesn't work properly, etckeeper's pre-apt hook could be "stuck". The hook runs git commit exactly once, if it fails, it display an error message and then allows you to continue. Please show me how this bug causes git-commit to fail, and explain what etckeeper is doing when it's "stuck" (process tree would probably suffice). -- see shy jo
signature.asc
Description: Digital signature
