Package: etckeeper
Version: 0.50
Severity: normal
Hi Joey,
Using current unstable etckeeper on lenny.
Suppose my /root/.hgrc lists a extension which is not available. In my
case it was
hg-prompt.prompt =
Then hg complains when it runs, of course. However, this doesn't
actually affect anything. However, etckeeper seems to see this as a
problem, and pops up a screen saying the commit failed to happen, when
in fact there is no problem. I assume it is looking at some exit
status to determine whether there is a problem? I think this is a bug.
You may disagree, in which case, feel free to close it. Thanks for
your work on etckeeper, and Happy Christmas and New Year!
Regards, Faheem
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500, 'stable'), (50, 'unstable'), (50, 'testing'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages etckeeper depends on:
ii debconf [debconf-2. 1.5.24 Debian configuration management sy
ii git-core 1:1.5.6.5-3+lenny3.2 fast, scalable, distributed revisi
ii mercurial 1.7.2-1 scalable distributed version contr
Versions of packages etckeeper recommends:
ii cron 3.0pl1-105 management of regular background p
Versions of packages etckeeper suggests:
ii sudo 1.6.9p17-3 Provide limited super user privile
-- debconf information:
* etckeeper/commit_failed:
etckeeper/purge: true
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
