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

Package 'firmware-linux' has no installation candidate #398

Closed
Penlect opened this issue Feb 24, 2023 · 0 comments · Fixed by #399
Closed

Package 'firmware-linux' has no installation candidate #398

Penlect opened this issue Feb 24, 2023 · 0 comments · Fixed by #399

Comments

@Penlect
Copy link

Penlect commented Feb 24, 2023

The readme file contains a Simple example for new users to get started.

It currently fails with the following error message:

2023/02/24 15:20:00 apt | Package firmware-linux is not available, but is referred to by another package.
2023/02/24 15:20:00 apt | This may mean that the package is missing, has been obsoleted, or
2023/02/24 15:20:00 apt | is only available from another source
2023/02/24 15:20:00 apt | 
2023/02/24 15:20:00 apt | E: Package 'firmware-linux' has no installation candidate
2023/02/24 15:20:00 Action `apt` failed at stage Run, error: exit status 100

This is related to https://lists.debian.org/debian-devel-announce/2022/10/msg00001.html which implies that the firmware-linux package has moved to the non-free-firmware component. The fix should therefore be to add it to the components like this:

actions:
  - action: debootstrap
    suite: bookworm
    components:
      - main
      - non-free-firmware
bors bot added a commit that referenced this issue Feb 24, 2023
399: Include non-free-firmware component in Simple example r=obbardc a=Penlect

Fixes #398

Co-authored-by: Daniel Andersson <daniel.andersson@qrtech.se>
@bors bors bot closed this as completed in f4ff783 Feb 24, 2023
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.

1 participant