etckeeper uses bzr by default but installs git by default
Bug #321809 reported by
Thierry Carrez
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| etckeeper (Ubuntu) |
Fix Released
|
Low
|
Thierry Carrez | ||
Bug Description
Binary package hint: etckeeper
Since 0.25ubuntu1 etckeeper has VCS=bzr enabled by default.
However running "apt-get install etckeeper" still pulls git-core rather than bzr (if none are installed).
Fix (in debian/control):
Depend on "bzr (>= 1.4~) | git-core (>= 1:1.5.4) | mercurial" rather than "git-core (>= 1:1.5.4) | mercurial | bzr (>= 1.4~)"
| Changed in etckeeper: | |
| assignee: | nobody → tcarrez |
| importance: | Undecided → Low |
| status: | New → In Progress |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in etckeeper: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
This bug was fixed in the package etckeeper - 0.28ubuntu1
---------------
etckeeper (0.28ubuntu1) jaunty; urgency=low
* Merge from debian unstable. Remaining changes:
* etckeeper.conf: Default to bzr
* debian/control: Default to bzr as well (LP: #321809)
etckeeper (0.28) unstable; urgency=low
* Support darcs. Thanks to Gian Piero Carrubba. Closes: #510032
etckeeper (0.27) unstable; urgency=low
* Use SUDO_USER as the committer if set. Closes: #498739
(Thierry Carrez)
* bzr: Avoid use of etckeeper pre-commit on Trees not on the
filesystem. (Jelmer Vernooij)
etckeeper (0.26) unstable; urgency=low
* Add Japanese debconf translation. Closes: #512869
* Prevent git from removing a directory when the last file in it
has been removed, but the directory is left existing and empty,
by touching a flag file before calling git rm. Closes: 513006
-- Thierry Carrez <email address hidden> Fri, 13 Feb 2009 13:58:42 +0000