Transferring conffiles between packages (Re: Bug#564254: conflicting /etc/bash_completion)
- To: email@example.com
- Cc: Kurt Roeckx <firstname.lastname@example.org>, David Paleino <email@example.com>, Sven Joachim <firstname.lastname@example.org>, Julien Cristau <email@example.com>, firstname.lastname@example.org
- Subject: Transferring conffiles between packages (Re: Bug#564254: conflicting /etc/bash_completion)
- From: Jonathan Nieder <email@example.com>
- Date: Tue, 2 Nov 2010 15:14:36 -0500
- Message-id: <20101102201436.GA6756@burratino>
- In-reply-to: <20100108203329.GA12684@roeckx.be>
- References: <20100108183234.GA11082@roeckx.be> <20100108194745.GN20626@radis.liafa.jussieu.fr> <firstname.lastname@example.org> <email@example.com> <20100108203329.GA12684@roeckx.be>
Hi Guillem et al,
Sorry to revive this old thread.
On 2010-01-08, Kurt Roeckx wrote:
> I got this on the buildd:
> Unpacking bash-completion (from .../bash-completion_1%3a1.1-3_all.deb) ...
> dpkg: error processing /home/buildd/build/chroot-unstable/var/cache/apt/archives/bash-completion_1%3a1.1-3_all.deb
> (--unpack): trying to overwrite `/etc/bash_completion', which is also in package bash
> On the system:
> excelsior:~# ls -l /etc/bash_completion
> -rw-r--r-- 1 root root 215907 Jul 5 2006 /etc/bash_completion
> excelsior:~# dpkg --search /etc/bash_completion
> bash: /etc/bash_completion
> This is with bash 4.0-7.
The message is in tarobject(). I think dpkg 1.13.14~19 (Improve
processing of disappearing conffiles, 2006-02-10) was supposed to deal
with this case:
If the file to be unpacked is (1) a conffile in the new package and
(2) a regular file rather than a symlink or directory, and some
installed conffile with the same inode is obsolete, then let the
Checking on snapshot.debian.org, I see that /etc/bash_completion was
indeed a conffile in bash-completion 1:1.1-3.
Any idea what could have gone wrong?
Kurt Roeckx wrote:
> At some point in time the chroot had the version from oldstable
> or older, just like all my chroots and main systems. And I have
> upgraded from that version. I never installed bash-completion.
> But now some pacakge build-depends on that for some strange reason,
> and I get that error.