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

Better way to track dom0 updates #2742

Open
andrewdavidwong opened this Issue Apr 10, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@andrewdavidwong
Member

andrewdavidwong commented Apr 10, 2017

Problem

If a bug is fixed by patching the Qubes installer, that fix is not always available to existing Qubes installations, even if they are fully updated. This can happen when the fix entails changing the list of packages that are installed by the Qubes installer, e.g., by adding a new package to that list. (Re)installing Qubes will result in having the new package (and, therefore, the fix), but merely updating an existing installation will not. Existing installations remain broken despite being fully updated.

Proposed Solution

Create a meta-package that tracks the list of packages installed by the Qubes installer, and enable the update system to use this meta-package so that existing installations, once updated, will have the same packages as fresh installations.


This problem and the proposed solution were identified and presented by @jpouellet:

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Apr 10, 2017

Contributor

Also, I think the title should be something like "Better way to track dom0 updates". The proposed meta-package(s) is not necessarily the best (or even a correct) solution, just the first thing that came to mind.

Contributor

jpouellet commented Apr 10, 2017

Also, I think the title should be something like "Better way to track dom0 updates". The proposed meta-package(s) is not necessarily the best (or even a correct) solution, just the first thing that came to mind.

@andrewdavidwong andrewdavidwong changed the title from Dom0 update meta-package to Better way to track dom0 updates Apr 10, 2017

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Apr 10, 2017

Member

@jpouellet: Updated the title. Thanks!

Member

andrewdavidwong commented Apr 10, 2017

@jpouellet: Updated the title. Thanks!

@jpouellet

This comment has been minimized.

Show comment
Hide comment
@jpouellet

jpouellet Apr 24, 2017

Contributor

It's possible that whatever solution ends up being identified in #2572 might also solve this issue.

Contributor

jpouellet commented Apr 24, 2017

It's possible that whatever solution ends up being identified in #2572 might also solve this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment