public inbox for
 help / color / mirror / Atom feed
From: Christian Franke <>
Subject: [ITP] etckeeper 1.18.17-1
Date: Tue, 28 Jun 2022 12:58:23 +0200	[thread overview]
Message-ID: <> (raw)

I would like to contribute etckeeper.

category: Utils
requires: bash coreutils grep sed
sdesc: "Store /etc in git or mercurial"
ldesc: "Etckeeper is a tool to let /etc be stored in git or
mercurial.  It hooks into Cygwin Setup to automatically commit changes
made to /etc during package upgrades.  It tracks file metadata
(permissions, owner, group) that version control systems do not
normally support."

Package for review:
wget -r -nH --cut-dirs=2 \ \ \ 
\ \

Tested with git. Only a few tests were done with hg.

Baazar is not fully supported yet as the pre-commit hook Python module 
is not included. The "bzr" command now fails on Cygwin as it still 
requires python2.7. Debian/Ubuntu moved to brz (breeze).

The current Cygwin Setup cannot automatically run the hook for 
'etckeeper pre-install'. A related patch is here:

As a workaround for now, 'etckeeper pre-install' could be run manually 
before starting setup. If not run, the 'etckeeper post-install' hook 
then also commits any pending changes done before setup, the "Package 
changes:" list in the log message is always empty and "Packages with 
configuration changes:" will not appear. The remaining functionality is 
not affected.


             reply	other threads:[~2022-06-28 10:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 10:58 Christian Franke [this message]
2022-06-28 17:41 ` Adam Dinwoodie
2022-06-28 21:09   ` Christian Franke
2022-06-29  7:55     ` Christian Franke
2022-06-29  8:12       ` Adam Dinwoodie
2022-07-02 13:02         ` Jon Turney
2022-07-02 13:26         ` Christian Franke
2022-07-02 12:34 ` Jon Turney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).