-
Notifications
You must be signed in to change notification settings - Fork 43
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
Use Fedora 34 in sys-* VMs #735
Comments
Great opportunity to tackle #702. |
Still in progress upstream, see QubesOS/qubes-issues#6568. We can and should pull the template in from the "testing" repository to evaluate how it'll work. |
I can enable the the qube template test repos (maybe this sprint but would be interested in doing this for the next sprint) and test the fedora-34 template with our updater. i think the fedora-35 template will also be accessible, so worth testing with that too to put us much further away from the next eol. |
Sounds wonderful, @creviera. In the interest of clarity, I see the testing steps we can do on this issue immediately as:
If you run into any errors, document them here and we'll investigate. Any blockers for our needs will need to be reported upstream, but let's confer amongst ourselves first. |
I was able to follow @conorsch's steps above and do basic client testing that included: I'll check to see if we run into any issues with the |
Oh, never mind about testing |
Good news, upstream's already published the F34 RPM in the prod repo for Qubes 4.0.4. We're now unblocked to migrate and release the change. Let's get an RPM up with changes and try to ship next week, to stay ahead of the EOL date. @creviera if you've got a branch lying around, mind opening a PR? |
It'll soon be that time again. We're still running Fedora 33 (#691), which goes EOL on 2021-11-30: https://endoflife.date/fedora Unfortunately, it looks like there's no
qubes-template-fedora-34
RPM available in the dom0 repos for 4.0 yet. Lets investigate upstream and try to get a sense of timeline.The text was updated successfully, but these errors were encountered: