On Tue, Nov 16, 2010 at 10:44:53PM -0800, Matt Taggart wrote: > I discovered that the version of superiotool in unstable was blocked from > entering testing due to not being built on ia64 (according to > grep-excuses). But looking at > > https://buildd.debian.org/pkg.cgi?pkg=superiotool > > lists it as being uploaded (although the "Last State Change" date is > weird). However the ia64 version of r5050 isn't in the pool either. I think > wanna-build is confused and this prevented the ia64 buildd from building it > and thus it was blocked for a long time from entering testing. FWIW it *is* in the tag database: superiotool | 0.0+r3844-1 | testing | source, amd64, armel, i386, kfreebsd-amd64, kfreebsd-i386 superiotool | 0.0+r3844-1 | unstable | source superiotool | 0.0+r3844-1+b2 | testing | ia64 superiotool | 0.0+r3844-1+b2 | unstable | ia64 superiotool | 0.0+r5050-1 | unstable | source, alpha, amd64, armel, i386, kfreebsd-amd64, kfreebsd-i386 So you do want a removal from unstable of that binNMU. Kind regards Philipp Kern
Attachment:
signature.asc
Description: Digital signature