etckeeper with git breaks package upgrades that touch /etc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
etckeeper (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I tried to upgrade Ubuntu 12.04 Precise system to 14.04 Trusty (alpha) with "do-release-upgrade -d". I had etckeeper installed and configured to use Git. The upgrade failed at the very end, because etckeepers DPkg::Post-Invoke hook failed. The reason was that git user.name and user.email were not configured, but this was not an issue before the upgrade (i.e. apt/dpkg worked just fine).
It would be nice, if this kind of configuration issue was detected before the upgrade.
<pre>
Running mktexlsr. This may take some time... done.
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/
*** Please tell me who you are.
Run
git config --global user.email "<email address hidden>"
git config --global user.name "Your Name"
to set your account's default identity.
Omit --global to set the identity only in this repository.
fatal: unable to auto-detect email address (got 'root@untamo.
Error in function:
A fatal error occurred
Please report this as a bug and include the files
/var/log/
your report. The upgrade has aborted.
Your original sources.list was saved in
/etc/apt/
SystemError: E:Problem executing scripts DPkg::Post-Invoke 'if [ -x
/usr/bin/etckeeper ]; then etckeeper post-install; fi', E:Sub-process
returned an error code
No pending crash reports. Try --help for more information.
Could not install the upgrades
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Upgrade complete
The upgrade has completed but there were errors during the upgrade
process.
To continue please press [ENTER]
</pre>
description: | updated |
summary: |
- etckeeper with git breaks upgrade from Precise to Trusty + etckeeper with git breaks package upgrades that touch /etc |
Hmm.. forget it. The upgrade went fine after all. Only the changes in etc had to be committed manually.
I mark this as Invalid, since the problem can be avoided by changing the configuration.