Bug 474358 - bison-2.4 breaks existing code
bison-2.4 breaks existing code
Product: Fedora
Classification: Fedora
Component: graphviz (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Patrick Laughton
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-03 09:27 EST by John Ellson
Modified: 2010-06-28 06:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 06:53:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fix for this problem. (595 bytes, patch)
2008-12-08 07:10 EST, Petr Machata
no flags Details | Diff

  None (edit)
Description John Ellson 2008-12-03 09:27:31 EST
Description of problem:
bison-2.4 breaks graphviz builds.
Same problem has also been reported elsewhere for libIDL, see;

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.  extract sources from graphviz-2.20.3-1.fc11.src.rpm
2.  ./configure; make distclean  # to clear bison products from upstream tarball
3.  ./configure; make
Actual results:
bison -y -dv ../../lib/common/htmlparse.y
../../lib/common/htmlparse.y:473.11-12: $$ for the midrule at $3 of `table' has no declared type

Expected results:
No regressions

Additional info:
Comment 1 Petr Machata 2008-12-08 07:10:09 EST
Created attachment 326117 [details]
Fix for this problem.

As analysed in the bug that you reference, and documented in following link, the bug that you are seeing is in fact a bug in grammar.

Replacing the mid-rule reference $$ with $<tbl>$ fixes the problem.
Comment 2 Petr Machata 2008-12-08 07:11:42 EST
Reassigning to graphviz, since that's where the bug is.
Comment 3 John Ellson 2008-12-20 10:49:48 EST
This is fixed in graphviz upstream sources.

Doesn't affect distro build which use tar.gz sources since the problem occurs during generation of the source package.
Comment 4 Bug Zapper 2009-06-09 06:05:54 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 5 Patrick Laughton 2010-01-26 10:31:56 EST
John, are you saying this is NOTABUG for Fedora?
Comment 6 Bug Zapper 2010-04-27 08:27:04 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 7 Bug Zapper 2010-06-28 06:53:26 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.