Please merge 1.18.10-1 into disco
Bug #1815612 reported by
Karl Stenerud
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| etckeeper (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
tracking bug
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in etckeeper (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package etckeeper - 1.18.10-1ubuntu1
---------------
etckeeper (1.18.10-1ubuntu1) disco; urgency=medium
* Merge with Debian unstable (LP: #1815612). Remaining changes:
- Use C.UTF-8 for LANG for consistent unicode support
etckeeper (1.18.10-1) unstable; urgency=medium
* New upstream release
* update debhelper and standards version, no change
etckeeper (1.18.10) unstable; urgency=medium
* Avoid post-install failing when ps is from busybox or another
version not supporting procps-specific options.
* Use ps --no-headers rather than problimatic -h option.
etckeeper (1.18.9) unstable; urgency=medium
* When run during a package installation, include in the commit
message the command line that caused etckeeper to run.
Thanks, Laszlo Gombos
etckeeper (1.18.8-1) unstable; urgency=medium
* New upstream release (Closes: #850679)
* Revert port to py3, requires bzrlib to port first (Closes: #906000)
* update standards version, no change
etckeeper (1.18.8) unstable; urgency=medium
* Work around git commit's lack of robustness, by providing
reasonable default values for GIT_COMMITTER_EMAIL etc.
This was already done as part of the su/sudo handling,
and is now always done.
* Don't hardcode the master branch when pushing to PUSH_REMOTE.
Instead, let git push whatever branches it is configured to
push to that remote.
-- Karl Stenerud <email address hidden> Wed, 13 Feb 2019 12:17:24 +0100