Closing this one as invalid since OP cannot reproduce it anymore.
Daniel: please reopen it if you can reproduce it :)
** Changed in: etckeeper (Ubuntu)
Status: Incomplete => Invalid
--
bzr: ERROR: no changes to commit.
https://bugs.launchpad.net/bugs/344492
You received this bug notificat
Christian: your issue is bug 221383, which was fixed in Jaunty. You can work
around it in hardy by adding to your etckeeper.conf:
BZR_COMMIT_OPTIONS="--unchanged"
--
bzr: ERROR: no changes to commit.
https://bugs.launchpad.net/bugs/344492
You received this bug notification because you are a memb
Thierry Carrez wrote:
> Christian: it works here. What version of etckeeper / bzr are you
> running ?
>
>
For etckeeper, the one in hardy: 0.14ubuntu2. For bazaar, the one in the
bzr PPA, which is right now 1.16.1-1~bazaar1~hardy1
--
bzr: ERROR: no changes to commit.
https://bugs.launchpad.ne
Christian: it works here. What version of etckeeper / bzr are you
running ?
--
bzr: ERROR: no changes to commit.
https://bugs.launchpad.net/bugs/344492
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
The following patch is at least a workaround for this problem (if not a
clean solution).
** Attachment added: "Change /etc/apt/apt.conf.d/05etckeeper to ignore
etckeeper exit codes."
http://launchpadlibrarian.net/28974972/workaround.patch
--
bzr: ERROR: no changes to commit.
https://bugs.la
I'm getting this bug too. To reproduce, just install a package that does
not change any files in /etc.
The cause of the problem is etckeeper does a bzr commit after every
package install, and bazaar exits with a non-zero exit code (an a
"pointless commit" error) when there is nothing to commit. Th
Daniel: Yes, that would be useful. Add some logging to unclean.d/50test
(something like echo "$(date -R) : $(bzr status)" >> /var/log/etckeeper-
bzrstatus) so that next time it happens, you can see which files are
reported different (if any)...
--
bzr: ERROR: no changes to commit.
https://bugs.la
Thierry, yes, it looks strange (just like bug 221383), but I don't think
anything has been deleted/changed between calling "etckeeper unclean" and
"etckeeper commit" - or at least that's very unlikely.
IIRC, I've just done a standard "apt-get upgrade".
I cannot reproduce it.
Maybe it would be us
I can't reproduce this. If etckeeper unclean returns correctly (and from
your description, it does) everything should work...
Can you reproduce it or was it a transient error ? There could be some
condition if some file in /etc was deleted between the calls to
etckeeper unclean and etckeeper comm
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/24019410/Dependencies.txt
--
bzr: ERROR: no changes to commit.
https://bugs.launchpad.net/bugs/344492
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
10 matches
Mail list logo
