Re: binNMU ruby1.8 (was Re: Bug#420325: xapian-bindings: FTBFS: declaration of 'int) eaccess(const char*, int) throw ()' throws different exceptions
On Thu, Jun 14, 2007 at 05:05:33PM +0000, Olly Betts wrote:
> On 2007-04-21, Steve Langasek <firstname.lastname@example.org> wrote:
> > On Sat, Apr 21, 2007 at 07:41:00PM +0200, Adeodato Simó wrote:
> >> ruby1.8_1.8.6-1, rebuild against latest libc6-dev to drop eaccess from missing.h, 1, alpha amd64 arm hppa i386 ia64 m68k mips mipsel powerpc s390 sparc
> > Scheduled, with dep-wait set on libc6-dev 2.5 as I assume that's the version
> > providing the eaccess prototype.
> Short version: The dep-wait didn't work for mips and mipsel for some
> reason, so can you binNMU ruby1.8 on mips and mipsel again?
Well, it "worked", but a dep-wait on libc6-dev has a race condition anyway
because libc6-dev is not a build-dependency of these packages so the
clearing of the dep-wait does not guarantee that the version in question is
available in the buildd chroot.
So yes, new binNMUs scheduled.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.