-
-
Notifications
You must be signed in to change notification settings - Fork 48
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
Migrate templates from rpmdb to qvm-template #7436
Comments
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
|
Automated announcement from builder-github The package
|
QubesOS/qubes-issues#7436 is expected to fully resolve. Switching to running qvm-template manually resolves the issue in the meantime. Because anon-whonix also calls the Salt state, removing it for now (we run it mainly to ensure that Whonix is up-to-date, which won't be an issue until the next Debian stable release).
QubesOS/qubes-issues#7436 is expected to fully resolve. Switching to running qvm-template manually resolves the issue in the meantime. Because anon-whonix also calls the Salt state, removing it for now (we run it mainly to ensure that Whonix is up-to-date, which won't be an issue until the next Debian stable release).
Automated announcement from builder-github The package
|
Automated announcement from builder-github The package
|
Automated announcement from builder-github The component
Or update dom0 via Qubes Manager. |
How to file a helpful issue
Qubes OS release
R4.1
Brief summary
After in-place upgrade, templates previously installed cannot be managed with qvm-template
Steps to reproduce
qvm-template info <name-of-template>
Expected behavior
Shows info about installed template.
Actual behavior
Originally reported at freedomofpress/securedrop-workstation#751 (comment)
The text was updated successfully, but these errors were encountered: