Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

initrd: reproducible build #48

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

simone-weiss
Copy link
Collaborator

Changes

Set timestamp to SOURCE_DATE_EPOCH for initrd cpio content. When one exports SOURCE_DATE_EPOCH before calling the initrd generator twice for the same initrd, the built image is binary identical.

Dependencies:

(Provide list of pull requests with dependencies with this pull request)

Tests results

WIP need to implement reproducibility test.

<!-- add Robot test CLI logs here. -->

Developer Checklist:

  • Test: Changes are tested
  • Doc: Documentation has been updated
  • Git: Informative git commit message(s)
  • Issue: If a related GitHub issue exists, linking is done

Checklists for documentation

  • Grammar: the content is grammatically correct
    (spelling, grammar, formatting, US English is used)
  • Comprehensibility/Unambiguousness: the content is easy readable, clear to understand
  • Correctness and consistency: the content is technically correct and consistent,
    no contradictions, no double descriptions
  • Terminology: technical terms are clear and they are used correctly and documented in the glossary
  • Level of detail: the content matches the detail level necessary for the reviewed object

Reviewer checklist:

  • Review: Changes are reviewed
  • Review: Tested by the reviewer

Checklists for documentation

  • Grammar: the content is grammatically correct
    (spelling, grammar, formatting, US English is used)
  • Comprehensibility/Unambiguousness: the content is easy readable, clear to understand
  • Correctness and consistency: the content is technically correct and consistent,
    no contradictions, no double descriptions
  • Terminology: technical terms are clear and they are used correctly and documented in the glossary
  • Level of detail: the content matches the detail level necessary for the reviewed object

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant