severity 383971 important thanks Yes, this is a bug in bison when upgrading from the previous version (which shipped /usr/bin/yacc by mistake) to the current version (which no longer ships /usr/bin/yacc, but doesn't take appropriate steps to reinstate the alternative-controlled version). This is not a release-critical bug, because only upgrades from 1:2.3.dfsg-1 to 1:2.3.dfsg-2 are affected; it would still be highly desirable for the bison package to clean up after the mess it made so that buildd maintainers and others don't have to take care of it themselves when upgrading from -1...
-- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
