I am planning to downgrade bison in unstable by uploading an older bison package with a higher epoch number. This approach seems to be the path of least resistance, unless the release team wants to get involved.
Felipe, is it really necessary to downgrade the unstable version all the way back to 2.4? Testing has bison 1:2.5.dfsg-2.1, which was uploaded about a year ago and not affected by #689700. Unless anyone objects, I will bump the version number of bison 1:2.5.dfsg-2.1 to 2:2.5.dfsg-3 and upload it to unstable tomorrow. Note that this downgrade is a temporary measure intended to accommodate the special circumstances of the freeze. Once wheezy is released and the freeze lifted, I will again upload the latest version of bison. The broken packages will have to support the new behavior (or alternatively convince bison upstream that they new behavior is broken). On Wed, Oct 31, 2012 at 7:03 AM, Felipe Sateler <fsate...@gmail.com> wrote: > Dear release team, > > I'd like to point you to this bug in bison. Certain new features of > Bison 2.6 have caused incompatibilities with 2.4. This has resulted in > at least one package failing to build. > > I have set the severity to serious, because it causes other packages > to FTBFS. Please advise with how to proceed for packages that > build-depend on bison (eg, see #689988). > > > Saludos, > Felipe Sateler -- Chuan-kai Lin http://sites.google.com/site/chklin/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
