Package: etckeeper
Version: 0.27
Severity: normal
When the 05uncommitted-changes script detects an unclean /etc, and the
commit fails, it then enters as infinite loop of calling '$0 fail-debconf',
which displays a message (by email, in our case), then goes and tries
again.
This means that any noninteractive run that fails to automatically
commit to /etc will result in an infinite loop; for the moment I worked
around that by explicitly exiting in the fail-debconf stanza.
It would be ideal to detect this situation so that email reporting from
debconf doesn't loop forever. :/
Regards,
Daniel
-- System Information:
Debian Release: 4.0
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages etckeeper depends on:
ii debconf [debc 1.5.11etch2 Debian configuration management sy
ii git-core 1:1.5.6.5-3+lenny2~bpo40+1 fast, scalable, distributed revisi
etckeeper recommends no packages.
-- debconf information:
etckeeper/commit_failed:
--
✣ Daniel Pittman ✉ [email protected] ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
Looking for work? Love Perl? In Melbourne, Australia? Let me know.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]