| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fail in other locales.
Bug report:
> + egrep -q '[^-a-z_]'
> + echo 'etckeeper: invalid command init'
Strangely, I cannot reproduce this problem when using the
LANG=et_EE.UTF-8 locale. I guess our egreps are somehow behaving
differently, even though a-z is not a character class that should be
affected by locale AFAIK.
I'll go ahead and set LANG=C when calling things that use character
classes.
|
|
|
|
|
|
etckeeper out to the caller. This is to avoid making apt give up because git is misconfigured and cannot commit, or similar. Closes: #760011"
This reverts commit 1b70e83dddcafbcbea84fc55a6396e4876a9a0c4.
This approach breaks the AVOID_COMMIT_BEFORE_INSTALL feature.
|
|
|
|
to the caller. This is to avoid making apt give up because git is misconfigured and cannot commit, or similar. Closes: #760011
I absoltely do not want etckeeper to dive into the rats nest of making git
be able to commit reliably. git commit has about a dozen failure modes, and
it's up to the admin to avoid breaking their system by not giving it a
hostname, or writing a broken ~/.gitconfig, or not giving uid 0 a user
name, etc.
I considered making only apt.conf's etckeeper calls be guarded with ||
true, but this would also need to be done for the other package managers
that can call etckeeper. And it's better to let etckeeper
indicate which script failed, rather than seeing an error message and apt
continuing without an indication of why git commit was being called then.
|
|
traversal etc issues.
|
|
Apparently fails with netbsd's shell. Unsure if that shell is POSIX.
|
|
CWD does not have to be /etc when using etckeeper..
|
|
|
|
|
|
A new variable is introduced that will cause etckeeper to push to a
configuration-defined remote.
|
|
|
|
|
|
|
|
avoid daily noise. (gulikoza)
|
|
as of version 1.7.4p4, so it is not necessary for etckeeper to work around its behavior anymore. (sudo also allows disabling that for those who enjoy using guns around feet.) Closes: #583899
|
|
|
|
scripts that re-exec etckeeper are guaranteed to find it.
|
|
run by etckeeper do not drop root-owned files in user home directory when sudo etckeeper is run. Closes: #583581
|
|
|
|
Some etckeeper scripts run 'etckeeper unclean' and other subcommands.
If -d was specified, those subcommands would run on /etc, rather
than the -d directory. Use an env var to propigate the directory to the
subcommands.
|
|
|
|
to configure etckeeper to abort an installation if there are uncommitted changes in /etc. Closes: #478754
|
|
(Note that bzr does not support etckeeper's pre-commit hook.)
|
|
* Pass other patameters on from etckeeper to the .d scripts.
* Stop using run-parts for various reasons.
* Split out a commit.d that contains committing code that's used by
both the pre-install.d and post-install.d scripts.
* Split out an unclean.d that tests if the WC contains uncommitted
changes.
* Add preinst code to remove old post-install.d scripts.
|
|
|
|
Significantly refactored
|
|
in etckeeper.conf.
* Only install apt hooks if apt is used.
* Only add backup conffile exclusion to gitignore if dpkg is used.
* Rename pre/post-apt.d to pre/post-install.d to allow the same directories
to be used for other package managers.
* Use the name of the highlevel package manager in commit messages.
|
|
|
|
|
|
|
|
When etckeeper commit something it use a default message that can be
configured, but not easily edited on a case by case basis.
To make this possible, and to give other way to customize commit, I
add a configuration file that contain for now only one option:
GIT_COMMIT_OPTION that can contain option given to git commit when run
by etckeeper
|
|
|
|
|
|
Default to cding to /etc, but allow the user to specify another directory
to operate on.
|
|
|
|
|
|
|
|
Store the toplevel directory of the repo in the pre-commit hook, and cd to
there. This is not ideal, but good enough.
|
|
|
|
|
|
|
