Package: etckeeper
Version: 1.18.7-1
Severity: normal

Dear Maintainer,

Some time ago I disabled daily autocommits for my /etc/ directory:

  commit 1e123419c83f254aa27b831f8b268a8f575211dc
  Author: Martin Schwenke <mar...@meltin.net>
  Date:   Tue Sep 8 10:51:19 2015 +1000

      etckeeper: Be less automatic

  diff --git a/etckeeper/etckeeper.conf b/etckeeper/etckeeper.conf
  index 2aec35e..fd9cfb8 100644
  --- a/etckeeper/etckeeper.conf
  +++ b/etckeeper/etckeeper.conf
  @@ -18,7 +18,7 @@ DARCS_COMMIT_OPTIONS="-a"

   # Uncomment to avoid etckeeper committing existing changes
   # to /etc automatically once per day.
  -#AVOID_DAILY_AUTOCOMMITS=1
  +AVOID_DAILY_AUTOCOMMITS=1

   # Uncomment the following to avoid special file warning
   # (the option is enabled automatically by cronjob regardless).
   @@ -27,7 +27,7 @@ DARCS_COMMIT_OPTIONS="-a"
   # Uncomment to avoid etckeeper committing existing changes to 
   # /etc before installation. It will cancel the installation,
   # so you can commit the changes by hand.
  -#AVOID_COMMIT_BEFORE_INSTALL=1
  +AVOID_COMMIT_BEFORE_INSTALL=1

   # The high-level package manager that's being used.
   # (apt, pacman-g2, yum, dnf, zypper etc)

This has worked until recently.

Now I see daily autocommits again.  When I check /var/log/syslog I
see:

  Dec 18 16:06:26 rover systemd[1]: Starting Autocommit of changes in /etc 
directory...
  Dec 18 16:06:27 rover systemd[1]: Started Autocommit of changes in /etc 
directory.

It appears that a systemd job is active:

  $ systemctl list-units | grep etckeeper
  etckeeper.timer                                                               
            loaded active waiting   Daily autocommit of changes in /etc 
directory                              

However, the comment in /etc/etckeeper/etckeeper.conf.dpkg-dist says:

  # Etckeeper includes both a cron job and a systemd timer, which each
  # can commit exiting changes to /etc automatically once per day.
  # To enable the systemd timer, run: systemctl enable etckeeper.timer
  # The cron job is enabled by default; to disable it, uncomment this next line.
  #AVOID_DAILY_AUTOCOMMITS=1

I certainly haven't enabled the the systemd timer.

Note that I don't seem to be able to disable the systemd timer:

  root@rover:/etc# systemctl disable etckeeper.timer
  root@rover:/etc# systemctl list-units | grep etckeeper
  etckeeper.timer                                                               
            loaded active waiting   Daily autocommit of changes in /etc 
directory               

Clearly, I'm not smart enough to use something as excellent as
systemd.  ;-)

I think that, as documented, the systemd job should not be enabled by
default.

Alternatively, /etc/etckeeper/daily could be modified to honour
AVOID_DAILY_AUTOCOMMITS=1.  Then it would not matter if the systemd
job is active and is immortal.  In that case a Linux user with over 20
years experience would still be able to disable the daily autocommit
in an expected way.  ;-)

Thanks...

peace & happiness,
martin


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (990, 'stable'), (500, 'stable-updates'), (300, 
'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages etckeeper depends on:
ii  debconf [debconf-2.0]  1.5.65
ii  git                    1:2.15.1-1

Versions of packages etckeeper recommends:
ii  cron [cron-daemon]  3.0pl1-128.1

Versions of packages etckeeper suggests:
ii  sudo  1.8.21p2-2

-- Configuration Files:
/etc/etckeeper/etckeeper.conf changed:
VCS="git"
GIT_COMMIT_OPTIONS=""
HG_COMMIT_OPTIONS=""
BZR_COMMIT_OPTIONS=""
DARCS_COMMIT_OPTIONS="-a"
AVOID_DAILY_AUTOCOMMITS=1
AVOID_COMMIT_BEFORE_INSTALL=1
HIGHLEVEL_PACKAGE_MANAGER=apt
LOWLEVEL_PACKAGE_MANAGER=dpkg
PUSH_REMOTE=""


-- debconf information:
  etckeeper/purge: true

Reply via email to