On Fri, Jun 29, 2012 at 07:58:59PM +0200, Goswin von Brederlow wrote: > my only concern with the patch was that it breaks other sources > providing plugins for libao. As Ron mentioned on irc there are none such > sources in debian so this is of no concern.
What I said doesn't mean there is no concern, it just means that all the things which you said would need doing - without so much as a casual look at the source or what was really needed - were completely irrelevant here. > I checked the Ubuntu bugs for libao and they are not reproducable and > all concern earlier versions of libao (although that needed some > confident guessing) and do not apply to the mutiarch version. A few hours before the freeze is not the time to be indulging in blind guessing games and Works For Me assertions. cf. http://bash.org/?950581 Your first round of guessing what was needed here was wrong, and this round of guessing is based on equally little real and clear evidence. There is a word for certainty based on things you don't really know the full details of, but 'confidence' isn't the one that best describes it. > I would opt for including the patch before the freeze. If it breaks > something unexpected then there will be enough time during the freeze to > fix or revert it. It is only a freeze, not a release yet. The whole point of the freeze is to *fix* the remaining RC bugs so that we can release - not to cram in last minute untested things that introduce as many more of them as possible right before the 'deadline'. You're months too late for "if it breaks something unexpected" speculation. That you left reporting the remaining ia32-libs deps until the last day is bad enough, I don't see any good reason to make it unnecessarily worse. There are plenty of other m-a issues that you should be working on fixing before the wheezy+1 cycle begins without adding extra busywork to that. Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
