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-26 still used for sys- VMs #189

Closed
conorsch opened this issue Nov 6, 2018 · 2 comments · Fixed by #248
Closed

Fedora-26 still used for sys- VMs #189

conorsch opened this issue Nov 6, 2018 · 2 comments · Fixed by #248
Labels
provisioning salt Involves Salt-based configuration management stretch goal

Comments

@conorsch
Copy link
Contributor

conorsch commented Nov 6, 2018

On a clean install, the current config logic will leave the core sys-* VMs based on fedora-26, which has been EOL'd. We should explicitly reassign a dependency on the latest Fedora VM (currently fedora-28) for those machines.

There may be existing Qubes-maintained Salt logic we can reuse in /srv/formulas/base/virtual-machines-formula/qvm.

Related to #111, #181, #186.

@conorsch conorsch added provisioning salt Involves Salt-based configuration management labels Nov 6, 2018
@kushaldas
Copy link
Contributor

The current latest available version of Fedora in Qubes is Fedora 29.

@conorsch
Copy link
Contributor Author

We're right to close this issue given changes in #248, but we'll certainly be revisiting the issue of updating EOL templates for the sys-* VMs once fedora-30 is standard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
provisioning salt Involves Salt-based configuration management stretch goal
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants