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

Builds fail for EOS distributions (for example focal) #6561

Closed
1 of 2 tasks
SteeManMI opened this issue May 8, 2024 · 3 comments
Closed
1 of 2 tasks

Builds fail for EOS distributions (for example focal) #6561

SteeManMI opened this issue May 8, 2024 · 3 comments
Assignees
Labels
Discussion Issue is being discussed. Undetermined.

Comments

@SteeManMI
Copy link
Contributor

What happened?

This was reported in the forums: https://forum.armbian.com/topic/34923-csc-armbian-for-rk322x-tv-box-boards/page/86/#comment-190270

The build framework still shows eos distributions (currently it shows buster, focal, kinetic, lunar as eos) but if you choose them, the build fails as the build system tries to pull things from apt.armbian.com for the distribution which no longer exists.

So I would suggest either filtering out the eos distributions from the build framework ui, or remove the eos distributions from the config/distributions directory completely. Or I guess we could also restore the eos distribution content on apt.armbian.com.

Looking for feedback on which way this should be fixed.

How to reproduce?

performed a build for focal

Branch

main (main development branch)

On which host OS are you running the build script and observing this problem?

Other

Are you building on Windows WSL2?

  • Yes, my Ubuntu/Debian/OtherOS is running on WSL2

Relevant log URL

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
Copy link

github-actions bot commented May 8, 2024

Jira ticket: AR-2131

@EvilOlaf EvilOlaf added the Discussion Issue is being discussed. Undetermined. label May 9, 2024
@EvilOlaf
Copy link
Member

EvilOlaf commented May 9, 2024

I'd vote for removing eos userspaces from framework, at least disable the code necessary to show them even in EXPERT mode.
Restoring apt repo for those is possible too but why should we allow resources to be wasted?

@igorpecovnik
Copy link
Member

Now all are present, but EOS are not updating. Errors should be gone on all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion Issue is being discussed. Undetermined.
Development

No branches or pull requests

3 participants