[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: Re: Bug#659294: [libarchive-discuss] Fwd: Bug#659294: libarchive: FTBFS on various architectures (hurd, mipsel, s390, s390x)



Mail to debian-mipsel bounced, so forwarding to debian-mips.

~ Andres
---------- Forwarded message ----------
From: "Andres Mejia" <amejia004@gmail.com>
Date: Feb 22, 2012 10:10 AM
Subject: Re: Bug#659294: [libarchive-discuss] Fwd: Bug#659294: libarchive: FTBFS on various architectures (hurd, mipsel, s390, s390x)
To: <659294@bugs.debian.org>, <libarchive-discuss@googlegroups.com>, <debian-s390@lists.debian.org>, <debian-mipsel@lists.debian.org>

On Feb 22, 2012 12:45 AM, "Tim Kientzle" <tim@kientzle.com> wrote:
>
>
> On Feb 21, 2012, at 3:40 AM, Pino Toscano wrote:
>
> > Hi,
> >
> > (greetings from your favourite Hurd porter)
> >
> > Alle lunedì 13 febbraio 2012, Tim Kientzle ha scritto:
> >> So on hurd, I see a couple of interesting failures for bsdtar:
> >> [...]
> >
> > Actually, libarchive is pretty fine on Hurd, as it was after I fixed
> > libarchove 3.0.2 (and in 3.0.3 there are no changes leading to issues).
> >
> > The problem is that the test suite run (just like the whole package
> > build) is done within fakeroot (which means fakeroot-tcp), triggering
> > Debian's #534879.
>
> Thanks, Pino.
>
> Libarchive's test suite does a lot of file operations, including
> a lot of cross-checks of file modes, ownership, and other
> properties.
>
> The races described in #534789 would likely manifest
> as essentially random failures in libarchive's test suite.
>
> Tim
>

Ok, resolved the issue on hurd. Now that leaves the issues on mipsel and s390x which don't seem random.

~ Andres


Reply to: