Your message dated Thu, 15 May 2008 12:12:16 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#481310: etckeeper: Etckeeper upgrade breaks bzr
has caused the Debian Bug report #481310,
regarding etckeeper: Etckeeper upgrade breaks bzr
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
481310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=481310
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: etckeeper
Version: 0.15
Severity: critical
Justification: breaks unrelated software
Etckeeper upgrade removes (old) bzr, which is not even enabled in the etckeeper
config file. Etckeeper must detect incompatible bzr version in runtime, not
remove completely unrelated packages.
I had to upgrade bzr to unstable version, which is not even a release, but some
rc!
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (750, 'testing'), (700, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-ovz4 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages etckeeper depends on:
ii bzr 1.5~rc1-1 easy to use distributed version co
ii debconf [debconf-2.0] 1.5.21 Debian configuration management sy
ii git-core 1:1.5.5.1-1 fast, scalable, distributed revisi
ii mercurial 1.0-4 Scalable distributed version contr
etckeeper recommends no packages.
-- debconf information:
* etckeeper/unclean: true
etckeeper/commit_failed:
--- End Message ---
--- Begin Message ---
Mikhail Gusarov wrote:
> Etckeeper upgrade removes (old) bzr, which is not even enabled in the
> etckeeper
> config file. Etckeeper must detect incompatible bzr version in runtime, not
> remove completely unrelated packages.
>
> I had to upgrade bzr to unstable version, which is not even a release, but
> some
> rc!
etckeeper conflicts with old versions of bzr because it will break if
used with them.
Since the new bzr has not yet reached testing, apt might decide to
pgrade etckeeper and remove the old bzr to satisfy its conflict. But it
will tell you it's going to do that, and you can avoid the problem by
putting etckeeper on hold until the new bzr reaches testing.
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
