Thierry, You're right that the behavior doesn't really make sense. And I can't explain it. To have the /etc working tree "out of date" would imply that etckeeper somehow made a revision to the repository that didn't come from /etc. I'm not sure how that would happen. In particular, I'm not sure that it's correct to blame daily autocommits.
Here's the history: - I have been running etckeeper v0.18 since my initial install of Intrepid. It did pre/post-commits on every apt run and never complained about an out-of-date working tree. - On 26 Feb, I installed v0.30ubuntu2 using prevu (i.e., I created an Intrepid binary from the Jaunty source package) in order to use daily autocommits. The installation added a few comments to my etckeeper.conf, but doesn't seem to have otherwise changed my configuration. Daily autocommits were enabled by default. - After the upgrade, I began to regularly get errors about an out-of-date working tree when I ran apt, with conflicts centered on the files in the cups and resolvconf/run directories (as shown above). According to my etckeeper logs, /etc/.bzrignore never had rules to ignore cups/subscriptions.conf or resolvconf/run, so I'm not sure why they suddenly became a problem. - I don't know if the daily autocommit itself ever had a problem with an out-of-date working tree. The result of the cron job doesn't seem to get logged. - Since I removed/ignored cups and resolvconf/run (as described above), I have not had any more "out-of-date" errors. -- Daily autocommits lead to frequent conflicts https://bugs.launchpad.net/bugs/340726 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
