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

Fix Riscv recipe #79

Closed
rvagg opened this issue May 4, 2023 · 5 comments · Fixed by #80
Closed

Fix Riscv recipe #79

rvagg opened this issue May 4, 2023 · 5 comments · Fixed by #80
Assignees

Comments

@rvagg
Copy link
Member

rvagg commented May 4, 2023

From #78 (comment)

It needs to be either fixed or removed from here. Any pushes to the main branch here will result in a broken deploy and therefore non-update of the server's copy of this repo until this is addressed.

@rvagg rvagg assigned sxa May 4, 2023
@sxa
Copy link
Member

sxa commented May 15, 2023

Thanks for disabling it for now (I've been on vacation for the last two weeks) - it's a redirect issue as a result of a name change - switching it to ci.adoptium.net instead of ci.adoptopenjdk.net will fix it although there's another issue around with an alternate option for this so I'll hold off on implementing that for a few days.

@sxa
Copy link
Member

sxa commented May 17, 2023

FYI I've rebuilt and it's up including RISC_V at https://unofficial-builds.nodejs.org/download/release/v20.2.0/

@rvagg
Copy link
Member Author

rvagg commented May 17, 2023

uh, probably shouldn't have rebuilt, it causes problems for the docker-node folks to have a changed SHASUMs; something we ought to put in the README, or figure out with them

@sxa
Copy link
Member

sxa commented May 17, 2023

I have backups - I'll restore all but riscv64 ... Noted for future

@sxa
Copy link
Member

sxa commented May 17, 2023

Of course, if we manage to get fully reproducible builds working that wouldn't be a problem ;-)

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 a pull request may close this issue.

2 participants