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

Explain that the reproduction process is only important for GuestOS. #999

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

DFINITYManu
Copy link
Contributor

No description provided.

@DFINITYManu DFINITYManu marked this pull request as ready for review October 9, 2024 07:46
@DFINITYManu DFINITYManu requested a review from a team as a code owner October 9, 2024 07:46
Copy link
Contributor

@LittleChimera LittleChimera left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we probably want to hold this off until we have proper changes in place

@@ -23,7 +23,7 @@ def _verify_release_instructions(version):
sudo apt-get install -y curl && curl --proto '=https' --tlsv1.2 -sSLO https://raw.githubusercontent.com/dfinity/ic/{version}/ci/tools/repro-check.sh && chmod +x repro-check.sh && ./repro-check.sh -c {version}
```

The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal.
The two SHA256 sums printed above from a) the downloaded CDN image and b) the locally built image, must be identical, and must match the SHA256 from the payload of the NNS proposal. The verification process will also attempt to reproduce HostOS and SetupOS — these results are for advisory purposes only, as this proposal only elects a GuestOS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have been discussing submitting both the HostOS and GuestOS proposal together on a weekly basis, so let's wait with merging this PR until we decide what to do on that matter.

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.

3 participants