From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) (→Owner) |
Churchyard (talk | contribs) |
||
Line 32: | Line 32: | ||
<!-- [[Category:SystemWideChange]] --> | <!-- [[Category:SystemWideChange]] --> | ||
* Targeted release: [https://docs.fedoraproject.org/en-US/releases/ | * Targeted release: [https://docs.fedoraproject.org/en-US/releases/f38/ Fedora Linux 38] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page |
Revision as of 20:22, 8 November 2022
Reproducible builds: Clamp build mtimes to $SOURCE_DATE_EPOCH
Summary
The %clamp_mtime_to_source_date_epoch
RPM macro will be set to 1
. When an RPM package is built, mtimes of packaged files will be clamped to $SOURCE_DATE_EPOCH
which is already set to the date of the latest %changelog
entry. As a result, more RPM packages will be reproducible: The actual modification time of files that are e.g. modified in the %prep
section will not be reflected in the RPM package.
Owner
- Name: Miro Hrončok, Zbigniew Jędrzejewski-Szmek
- Email: mhroncok at redhat.com, zbyszek at in.waw.pl
Current status
- Targeted release: Fedora Linux 38
- Last updated: 2022-11-08
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Objectives:
Upgrade/compatibility impact
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)