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

Fedora 36 template #7342

Closed
7 tasks done
marmarek opened this issue Mar 12, 2022 · 6 comments · Fixed by QubesOS/qubes-posts#98
Closed
7 tasks done

Fedora 36 template #7342

marmarek opened this issue Mar 12, 2022 · 6 comments · Fixed by QubesOS/qubes-posts#98
Labels
C: Fedora P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.

Comments

@marmarek
Copy link
Member

marmarek commented Mar 12, 2022

The problem you're addressing (if any)
Fedora 36 is going out soon.

Describe the solution you'd like
We should have a Fedora 36 template.

Where is the value to a user, and who might that user be?
Users of the Fedora template who prefer to upgrade their templates by reinstalling will have a new template to upgrade to.

Tasks:

  • build all packages
  • build the template
  • add to relevant qubes-builder/example-configs (including templates.conf)
  • document
  • upload to testing repo
  • migrate to stable repo
  • announce

If any issue affects Fedora 36 template (build failures, things that worked fine before etc), please add reference to this issue too.

@marmarek marmarek added T: enhancement P: default Priority: default. Default priority for new issues, to be replaced given sufficient information. labels Mar 12, 2022
marmarek added a commit to QubesOS/qubes-release-configs that referenced this issue Mar 12, 2022
@andrewdavidwong andrewdavidwong changed the title Fedoea 36 template Fedora 36 template Mar 12, 2022
@andrewdavidwong andrewdavidwong added this to the Release 4.1 updates milestone Mar 12, 2022
@lubellier
Copy link

Fedora-36 switches to systemd-250 (source: https://src.fedoraproject.org/rpms/systemd).
So like ArchLinux, Fedora-36 should have the problem with the new predictable network interface names (xen_netfront: eth0 vs enX0), see #7284.

@marmarek
Copy link
Member Author

Fc36 packages for R4.1 are already built into current-testing repository. But above linked issues are not solved yet.

@marmarek
Copy link
Member Author

BTW, currently I do not plan backporting F36-related changes to R4.0. F35 is supported past EOL of R4.0, so there won't be any support gap.

marmarek added a commit to marmarek/qubes-linux-yum that referenced this issue Apr 3, 2022
marmarek added a commit to QubesOS/qubes-continuous-integration that referenced this issue May 26, 2022
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
wireless-tools package is removed in F36:
https://fedoraproject.org/wiki/Changes/RemoveWirelessExtensions

Drop it from the list - templates that still has something that
implicitly depend on it, will have it pulled in via dependency.

QubesOS/qubes-issues#7342
marmarek added a commit to marmarek/qubes-builder-rpm that referenced this issue May 26, 2022
marmarek added a commit to QubesOS/qubes-release-configs that referenced this issue May 27, 2022
@marmarek
Copy link
Member Author

The fedora-36 template (and other flavors too) is available in template-itl-testing repository for Qubes 4.1.

@andrewdavidwong
Copy link
Member

The fedora-36 template (and other flavors too) is available in template-itl-testing repository for Qubes 4.1.

Announced on the tester forum:

https://forum.qubes-os.org/t/fedora-36-templates-available-for-testing/11722

@marmarek
Copy link
Member Author

marmarek commented Jun 9, 2022

openqa test results all green: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.1&build=20220527-4.1-fedora-36&groupid=7
this doesn't happen often

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: Fedora P: default Priority: default. Default priority for new issues, to be replaced given sufficient information.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants