Your message dated Thu, 09 Dec 2010 19:36:22 +0100 with message-id <4D0121A6.1060303@debian.org> and subject line Re: Bug#603781: unblock: superiotool has caused the Debian Bug report #603781, regarding unblock: superiotool 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 603781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=603781 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Cc: uwe@debian.org
- Subject: unblock: superiotool
- From: Matt Taggart <taggart@debian.org>
- Date: Tue, 16 Nov 2010 22:44:53 -0800
- Message-id: <20101117064453.C5B56D6D2F@taggart.lackof.org>
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 taggart@debian.org
--- End Message ---
--- Begin Message ---
- To: Matt Taggart <taggart@debian.org>, 603781-done@bugs.debian.org
- Subject: Re: Bug#603781: unblock: superiotool
- From: Mehdi Dogguy <mehdi@debian.org>
- Date: Thu, 09 Dec 2010 19:36:22 +0100
- Message-id: <4D0121A6.1060303@debian.org>
- In-reply-to: <20101124082442.5297BD7108@taggart.lackof.org>
- References: <20101117064453.C5B56D6D2F@taggart.lackof.org> <20101117082024.GA30602@thrall.0x539.de> <20101124082442.5297BD7108@taggart.lackof.org>
On 24/11/2010 09:24, Matt Taggart wrote: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.Unblocked. Regards, -- Mehdi Dogguy مهدي الدڤي mehdi@{dogguy.org,debian.org}
--- End Message ---