Package: etckeeper
Version: 0.41
Severity: normal

It is possible that etckeeper commits accidentally during apt run between 
commit prior to apt run and commit after apt run.
This violates the distinction between administrator's und apt's changes.
I discovered this because I tried to derive an pristine (without my changes) 
tree of /etc this way:

#!/bin/bash
set -e
set -x
PRISTINE_BRANCH=/home/pristine_etc
rm -r $PRISTINE_BRANCH
bzr branch -r1 /etc $PRISTINE_BRANCH
cd /etc
APTS_REVISIONS="$(bzr log --forward\
                --message='^committing changes in /etc after apt run'\
                  |grep '^revno: '|cut -d ' ' -f 2)"
cd $PRISTINE_BRANCH
for AR in $APTS_REVISIONS
do
    bzr merge -r$((AR - 1))..$AR /etc
    bzr commit -m $AR
done

For avoiding this problem I included this into my etckeeper.conf:

AVOID_DAILY_AUTOCOMMITS=1

It's the opposite of the default configuration.


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages etckeeper depends on:
ii  bzr                           2.0.3-1    easy to use distributed version co
ii  debconf [debconf-2.0]         1.5.28     Debian configuration management sy

Versions of packages etckeeper recommends:
ii  cron                          3.0pl1-106 process scheduling daemon

etckeeper suggests no packages.

-- debconf information:
  etckeeper/commit_failed:
  etckeeper/purge: true



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to