when possible, suppress build paths in Bison-generated files - #349
Closed
Smattr wants to merge 3 commits into
Closed
when possible, suppress build paths in Bison-generated files#349Smattr wants to merge 3 commits into
Smattr wants to merge 3 commits into
Conversation
Build paths in Bison-generated files has been a barrier to reproducible builds, pointed out by Debian Developers many times over the past years. It has never seemed worth fixing this because a bug in Flex made the build not reproducible anyway.¹ In my mind, I actually incorrectly conflated the Flex bug as the _root cause_ of the Bison problem due to this situation having persisted for so long. The Flex bug has now been fixed in Flex commit cff048484c75ba2f434b69caa8df1c2bbe12d366. Though this has not yet made it into a Flex release, it seems a good time to fix our interactions with Bison such that we should automatically acquire reproducible builds when the Flex fix propagates to Debian. ¹ Compounding the confusing situation, the Flex bug was closed without the underlying issue being fixed. It was later reposted as a new issue. Github: westes/flex#268 Github: westes/flex#463 Github: westes/flex#704 Reported-by: Phil Wyett <philip.wyett@kathenas.org> Reported-by: Simon Quigley <tsimonq2@debian.org> Reported-by: Tobias Frost <tobi@debian.org> Thanks-to: Javier Maestro <jjmaestro@ieee.org> Thanks-to: Joshua Watt <JPEWhacker@gmail.com>
Smattr
force-pushed
the
smattr/62800585-eefe-4e31-a6bb-ee11c7407d87
branch
from
August 31, 2026 00:57
a713c90 to
64ab0b3
Compare
Smattr
added a commit
that referenced
this pull request
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Build paths in Bison-generated files has been a barrier to reproducible builds, pointed out by Debian Developers many times over the past years. It has never seemed worth fixing this because a bug in Flex made the build not reproducible anyway. In my mind, I actually incorrectly conflated the Flex bug as the root cause of the Bison problem due to this situation having persisted for so long.
The Flex bug has now been fixed in Flex commit
cff048484c75ba2f434b69caa8df1c2bbe12d366. Though this has not yet made it into a Flex release, it seems a good time to fix our interactions with Bison such that we should automatically acquire reproducible builds when the Flex fix propagates to Debian.