Use SOURCE_DATE_EPOCH in version timestamps #2943
Merged
Conversation
This file contains 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
|
The current |
gioele
force-pushed
the
debian-reproducible-buildtimestamps
branch
from
e800e78
to
28120fb
Compare
|
I updated the PR with the necessary changes for Mac OS X. Now Travis is happy again. |
To allow package to build reproducibly use SOURCE_DATE_EPOCH as mentioned in <https://reproducible-builds.org/specs/source-date-epoch/>.
gioele
force-pushed
the
debian-reproducible-buildtimestamps
branch
from
28120fb
to
102978a
Compare
|
Okay. |
Omnikron13
pushed a commit
to Omnikron13/fontforge
that referenced
this pull request
May 31, 2022
…ldtimestamps Use SOURCE_DATE_EPOCH in version timestamps
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR pushes upstream a patch carried by Debian since long time. It is safe to apply, does not interfere with the normal packaging workflow and make Fontforge a good citizen. :)
This is unrelated to issues #2490 and #2711: those issues are about timestamps in generated font files, this is PR has to do with the packaging of Fontforge itself.
Commit message: