Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1

View: New views

4 Messages — Rating Filter: Alert me

	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Luk Claes :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bálint Réczey wrote: > 2009/10/30 Luk Claes <luk@...>: >> Bálint Réczey wrote: >> >>> It seems, that the automatic migration to testing cannot take place >>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>> bug [2]. >>> >>> Package fails to build on alpha [3], BTW. >> This was a bug in the BTS handling of release arches to create the lists >> of RC bugs for britney which has been solved in the mean time. So >> closing this bug. >> >> Cheers >> >> Luk >> > > Can I expect it to go in soon? > It still could not enter testing. Which is because there is a new RC bug because of a security issue. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Bálint Réczey :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 2009/11/1 Luk Claes <luk@...>: > Bálint Réczey wrote: >> 2009/10/30 Luk Claes <luk@...>: >>> Bálint Réczey wrote: >>> >>>> It seems, that the automatic migration to testing cannot take place >>>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>>> bug [2]. >>>> >>>> Package fails to build on alpha [3], BTW. >>> This was a bug in the BTS handling of release arches to create the lists >>> of RC bugs for britney which has been solved in the mean time. So >>> closing this bug. >>> >>> Cheers >>> >>> Luk >>> >> >> Can I expect it to go in soon? >> It still could not enter testing. > > Which is because there is a new RC bug because of a security issue. > > Cheers > > Luk > Hi, I've fixed the new bug, and http://release.debian.org/migration/testing.pl?package=wireshark shows correctly that migration is blocked by build failures, but http://qa.debian.org/excuses.php?package=wireshark still lists #547704 as a blocker bug, incorrectly. I guess this bug should be reopened and moved to qa.debian.org. Or should I open a different bug? Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Luk Claes :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bálint Réczey wrote: > 2009/11/1 Luk Claes <luk@...>: >> Bálint Réczey wrote: >>> 2009/10/30 Luk Claes <luk@...>: >>>> Bálint Réczey wrote: >>>> >>>>> It seems, that the automatic migration to testing cannot take place >>>>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>>>> bug [2]. >>>>> >>>>> Package fails to build on alpha [3], BTW. >>>> This was a bug in the BTS handling of release arches to create the lists >>>> of RC bugs for britney which has been solved in the mean time. So >>>> closing this bug. >>>> >>>> Cheers >>>> >>>> Luk >>>> >>> Can I expect it to go in soon? >>> It still could not enter testing. >> Which is because there is a new RC bug because of a security issue. >> >> Cheers >> >> Luk >> > > Hi, > I've fixed the new bug, and > http://release.debian.org/migration/testing.pl?package=wireshark > shows correctly that migration is blocked by build failures, but > http://qa.debian.org/excuses.php?package=wireshark still lists > #547704 as a blocker bug, incorrectly. > I guess this bug should be reopened and moved to qa.debian.org. Or > should I open a different bug? No, the reason qa mentions that #547704 is still a blocker is because of the build failures there are still binaries in unstable affected by that bug. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Adam D. Barratt-29 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sun, 2009-11-08 at 13:54 +0100, Bálint Réczey wrote: > 2009/11/1 Luk Claes <luk@...>: > I've fixed the new bug, and > http://release.debian.org/migration/testing.pl?package=wireshark > shows correctly that migration is blocked by build failures, but > http://qa.debian.org/excuses.php?package=wireshark still lists > #547704 as a blocker bug, incorrectly. > I guess this bug should be reopened and moved to qa.debian.org. Or > should I open a different bug? That's not a bug, and it's not incorrect (although that's not an unreasonable assumption). #547704 /is/ a blocker until the missing builds are available, as the version of the package currently in unstable is affected by the bug. This is an artefact of the way in which the BTS considers whether a bug affects a particular suite; the bug is not fixed in unstable until all architectures have the fix available (with a couple of exceptions for non-release architectures). Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...

	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Luk Claes :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bálint Réczey wrote: > 2009/10/30 Luk Claes <luk@...>: >> Bálint Réczey wrote: >> >>> It seems, that the automatic migration to testing cannot take place >>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>> bug [2]. >>> >>> Package fails to build on alpha [3], BTW. >> This was a bug in the BTS handling of release arches to create the lists >> of RC bugs for britney which has been solved in the mean time. So >> closing this bug. >> >> Cheers >> >> Luk >> > > Can I expect it to go in soon? > It still could not enter testing. Which is because there is a new RC bug because of a security issue. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Bálint Réczey :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message 2009/11/1 Luk Claes <luk@...>: > Bálint Réczey wrote: >> 2009/10/30 Luk Claes <luk@...>: >>> Bálint Réczey wrote: >>> >>>> It seems, that the automatic migration to testing cannot take place >>>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>>> bug [2]. >>>> >>>> Package fails to build on alpha [3], BTW. >>> This was a bug in the BTS handling of release arches to create the lists >>> of RC bugs for britney which has been solved in the mean time. So >>> closing this bug. >>> >>> Cheers >>> >>> Luk >>> >> >> Can I expect it to go in soon? >> It still could not enter testing. > > Which is because there is a new RC bug because of a security issue. > > Cheers > > Luk > Hi, I've fixed the new bug, and http://release.debian.org/migration/testing.pl?package=wireshark shows correctly that migration is blocked by build failures, but http://qa.debian.org/excuses.php?package=wireshark still lists #547704 as a blocker bug, incorrectly. I guess this bug should be reopened and moved to qa.debian.org. Or should I open a different bug? Cheers, Balint -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Luk Claes :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message Bálint Réczey wrote: > 2009/11/1 Luk Claes <luk@...>: >> Bálint Réczey wrote: >>> 2009/10/30 Luk Claes <luk@...>: >>>> Bálint Réczey wrote: >>>> >>>>> It seems, that the automatic migration to testing cannot take place >>>>> for wireshark 1.2.2-2 because #547704 [1] is falsely identified a new >>>>> bug [2]. >>>>> >>>>> Package fails to build on alpha [3], BTW. >>>> This was a bug in the BTS handling of release arches to create the lists >>>> of RC bugs for britney which has been solved in the mean time. So >>>> closing this bug. >>>> >>>> Cheers >>>> >>>> Luk >>>> >>> Can I expect it to go in soon? >>> It still could not enter testing. >> Which is because there is a new RC bug because of a security issue. >> >> Cheers >> >> Luk >> > > Hi, > I've fixed the new bug, and > http://release.debian.org/migration/testing.pl?package=wireshark > shows correctly that migration is blocked by build failures, but > http://qa.debian.org/excuses.php?package=wireshark still lists > #547704 as a blocker bug, incorrectly. > I guess this bug should be reopened and moved to qa.debian.org. Or > should I open a different bug? No, the reason qa mentions that #547704 is still a blocker is because of the build failures there are still binaries in unstable affected by that bug. Cheers Luk -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...
	Bug#552727: wireshark 1.2.2-2 cannot enter testing because a bug already closed in 1.2.2-1 by Adam D. Barratt-29 :: Rate this Message: Reply to Author \| View Threaded \| Show Only this Message On Sun, 2009-11-08 at 13:54 +0100, Bálint Réczey wrote: > 2009/11/1 Luk Claes <luk@...>: > I've fixed the new bug, and > http://release.debian.org/migration/testing.pl?package=wireshark > shows correctly that migration is blocked by build failures, but > http://qa.debian.org/excuses.php?package=wireshark still lists > #547704 as a blocker bug, incorrectly. > I guess this bug should be reopened and moved to qa.debian.org. Or > should I open a different bug? That's not a bug, and it's not incorrect (although that's not an unreasonable assumption). #547704 /is/ a blocker until the missing builds are available, as the version of the package currently in unstable is affected by the bug. This is an artefact of the way in which the BTS considers whether a bug affects a particular suite; the bug is not fixed in unstable until all architectures have the fix available (with a couple of exceptions for non-release architectures). Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@...