Am Sun, 28 Apr 2013 17:24:26 +0100 schrieb "Adam D. Barratt" <[email protected]>:
> On Sun, 2013-04-28 at 18:18 +0200, Christian Hammers wrote: > > Am Sun, 28 Apr 2013 17:00:59 +0100 > > schrieb "Adam D. Barratt" <[email protected]>: > > > The version information also indicates that the problem applies > > > to the version of quagga in unstable. If that's correct, please > > > fix it in unstable; if not, please add an appropriate fixed > > > version. > > > > We've 0.99.22 in unstable (and 0.99.22.1 with a fix coming soon) and > > 0.99.21 in testing. At this stage of the freeze, I'd rather prefer a > > fixed 0.99.21 than the 0.99.22 to be released. > > I wasn't suggesting that we ship 0.99.22 in wheezy, I was asking > whether the package in unstable contains the fix. Looking at the > code, the answer is "yes, it does", which makes your answer that it's > "coming soon" slightly confusing. :-( Sorry, came to my mind as well and I've already send a mail to control@bugs to mark the 0.99.22 version as fixed. > Please go ahead with the upload. Please also fix the version > information for the bug to indicate that it doesn't apply to the > package in unstable. OK, thanks! bye, -christian- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
