Bug#603781: unblock: superiotool
FWIW it *is* in the tag database: superiotool | 0.0+r3844-1 | testing | source, amd64, armel, i386, kfr= eebsd-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, i3= 86, kfreebsd-amd64, kfreebsd-i386 So you do want a removal from unstable of that binNMU. Fixed with the closing of #603962. -- Matt Taggart tagg...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603781: unblock: superiotool
On Tue, 2010-11-16 at 22:44 -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. [...] Assuming it builds on ia64, this version should have been in testing anyway, and allowing it in now represents very little risk. Could someone kick w-b and if it builds please consider unblocking? Packages-arch-specific says: %superiotool: !hppa !ia64 !m68k !mips !mipsel !powerpc !sh4 !sparc# sys/io.h i.e. the package isn't intended to build on ia64. The out-of-date ia64 binaries need removing from unstable, otherwise the package won't be able to migrate even if it is unblocked. w-b should probably also be updated to forget that superiotool ever had binaries on ia64 but that's orthogonal to getting unstable tidied up. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#603781: unblock: superiotool
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 signature.asc Description: Digital signature
Bug#603781: unblock: superiotool
Package: release.debian.org 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. The package currently has no bugs. It's a utility for determining what super i/o chipset your system has, mostly useful for coreboot development. The newer version is able to recognize more chipsets, the version currently in squeeze (0.0+r3844-1) was uploaded in Dec 2008 and is not so useful. Assuming it builds on ia64, this version should have been in testing anyway, and allowing it in now represents very little risk. Could someone kick w-b and if it builds please consider unblocking? Thanks, -- Matt Taggart tagg...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
