-
Notifications
You must be signed in to change notification settings - Fork 48
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
Automatically redirect RISC-V users to riscv.eessi.io
in init script + initial RISC-V support for archdetect
#583
Automatically redirect RISC-V users to riscv.eessi.io
in init script + initial RISC-V support for archdetect
#583
Conversation
Instance
|
Instance
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
@bedroge I'm waiting ages for both the bot and GitHub Actions, guess we have some GitHub issues |
@ocaisa Looks good now? |
@bedroge it's missing the updates to the |
Which updates do you mean? It does contain the (almost empty) spec file for RISC-V? |
In the report from the bot I only see
|
Ah, you mean the tarball. Yes, you're right, I just checked the tarball itself and it doesn't contain it... let me check. edit: found it, it has to be added to install_scripts.sh. |
bot: build repo:eessi.io-2023.06-software arch:x86_64/generic |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
Tested on my Visionfive 2:
And this is what archdetect reports: