Your message dated Mon, 28 May 2007 16:44:14 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Bug#421291: trying to overwrite
`/usr/share/doc/gcj-4.1-base/README'
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gij-4.1
Version: 4.1.2-4
Severity: serious
Hi,
I'm getting this error:
Unpacking gcj-4.1 (from .../gcj-4.1_4.1.2-4_amd64.deb) ...
Selecting previously deselected package libgcj7-0.
Unpacking libgcj7-0 (from .../libgcj7-0_4.1.1-20_amd64.deb) ...
dpkg: error processing
/home/buildd/build/chroot-unstable/var/cache/apt/archives/libgcj7-0_4.1.1-20_amd64.deb
(--unpack):
trying to overwrite `/usr/share/doc/gcj-4.1-base/README', which is also in
package gij-4.1
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Kurt
--- End Message ---
--- Begin Message ---
Version: 1.13.2
On Mon, 2007-05-28 at 14:21:06 +0200, Kurt Roeckx wrote:
> On Fri, May 25, 2007 at 01:50:33AM +0300, Guillem Jover wrote:
> > tag 421291 unreproducible
> > thanks
> >
> > > > http://buildd.debian.org/fetch.cgi?pkg=commons-daemon;ver=1.0.2%7Esvn20061127-5;arch=amd64;stamp=1177691051
> > > > http://buildd.debian.org/fetch.cgi?pkg=antlr;ver=2.7.6-8;arch=amd64;stamp=1177691078
> > > > http://buildd.debian.org/fetch.cgi?pkg=kdebindings;ver=4%3A3.5.6-2;arch=amd64;stamp=1177691156
> >
> > Also all build failures occur on the same buildd, maybe a local
> > problem? Strange that this didn't happen on other buildds.
>
> I might be a little more active in following up on failed build logs
> than most of the other arches.
>
> Anyway, afaik, the dpkg used it those from the host system, not from the
> chroot. So that would still be 1.10.28 from sarge.
Ah that explains it! This was fixed in dpkg 1.13.2 (bugs #164595,
#184635, #277890), so please upgrade the host systems.
regards,
guillem
--- End Message ---
