Your message dated Thu, 29 Nov 2018 20:16:47 -0800 with message-id <CAJjFYLa7kPmbFH+4-z=e1Faq-SvWMQW=qpowsp7hrmdcxzo...@mail.gmail.com> and subject line Closing #301075 has caused the Debian Bug report #301075, regarding Stale dangling yacc alternatives from byacc to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 301075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=301075 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bison Version: 1.875d-1 Severity: serious Synopsis: installation of bison does not properly install the yacc alternatives symlinks - see below. > I think I ran into this a few months back. It had to do with > alternatives -- very odd. Odd indeed. I found a stale yacc alternatives file for bison (byacc) on kullervo, that might have prevented proper alternatives installation. > /usr/bin/yacc needs to point to /etc/alternatives/yacc > /etc/alternatives/yacc needs to point to /usr/bin/bison.yacc Which should be taken care of by bison's postinstall script. > It seems like I had to do something like > update-alternatives --auto yacc Which constitutes a bug in bison. This section of bison.postinst if [ $1 != "upgrade" ] ; then update-alternatives --install /usr/bin/yacc yacc /usr/bin/bison.yacc 100 \ --slave /usr/share/man/man1/yacc.1.gz yaccman /usr/share/man/man1/bison.1.gz fi doesn't work at all. Funny enough, after a single invocation of update-alternatives --auto, it does. Hence, adding that to the postinst seems like a good idea. Bug filed. Michael
--- End Message ---
--- Begin Message ---This bug applies to a version of bison that is now over 13 years old. Even though I did not come up with a comprehensive solution, everyone who had experienced the problem would have worked around it manually over a decade ago. Versions of bison 2.0-1 and on cannot cause the dangling alternative, so it is likely that no Debian users have personally experienced this bug in the past 10 years. So I am marking it as done. Chuan-kai Lin
--- End Message ---
