make \ not act as an escape character while parsing ignore file

Use "read -r" to parse the ignore file.
update-ignore, uninit: Fix parsing of ignore files containing '\'
replace shebang => null line in yum-etckeeper.py.

The yum-etckeeper.py is not executable.
But it has a shebang.  So rpmlint is warning.
So Fedora executes "sed -i -e 1d" in etcleeper.spec.
http://pkgs.fedoraproject.org/cgit/etckeeper.git/tree/etckeeper.spec
Upstream should not worry downstreams.
The etckeeper-bzr/__INIT__.py has same problem too.
So I will modify it in other patch.

	modified:   yum-etckeeper.py
replace shebang => null line in __init__.py.

The __init__.py is not executable.
But it has a shebang.  So rpmlint is warning.
So Fedora executes "sed -i -e 1d" in etcleeper.spec.
http://pkgs.fedoraproject.org/cgit/etckeeper.git/tree/etckeeper.spec
Upstream should not worry downstreams.
Please see also:
https://github.com/joeyh/etckeeper/pull/15

	modified:   Makefile
	modified:   etckeeper-bzr/__init__.py
prep release
prep
Avoid propigating nonzero exit status of any command called by etckeeper out 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.
prep release
better status output
Revert "Avoid propigating nonzero exit status of any command called by 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.
Use debconf for prompting when post-install commit fails, as was already done for pre-install commit. This avoids propigating errors to apt when eg, git is misconfigured and cannot commit. Closes: #760011
let's not use debconf to display a possibly minor warning
prep release
Avoid propigating nonzero exit status of any command called by etckeeper out 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.
better status output
Revert "Avoid propigating nonzero exit status of any command called by 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.
prep release
Allow etckeeper to track multiple directories