On Sat, Oct 13, 2012 at 05:18:48PM -0700, Chuan-kai Lin wrote: > On Sat, Oct 13, 2012 at 3:35 PM, Felipe Sateler <fsate...@debian.org> wrote: > > This causes unrelated packages to break. Please revert this change > > until wheezy is released, since it makes fixing bugs in testing harder > > than necessary for pacakges build-depending on bison.
Hello Felipe, Could you provide example of such packages for the record ? I found the problem with the pari package, but it is not normally build with g++ so it does not affect Debian, hence the severity. > Do you happen to know what is the correct procedure to revert the > introduction of a new upstream release? > Is it something that the release team can handle through a bug to > release.debian.org? Hello Chuan-kai Did you report the bug upstream ? Maybe they could provide a fix. The only way to revert to an older upstream release is to reupload the old upstream release with a larger version number, either by raising the epoch field of by playing game like 2.6.2.really.2.5.0. It is generally not recommended to upload new upstream version during the freeze especially if they hae a large number of reverse dependencies or build-dependencies. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
