Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upBetter way to track dom0 updates #2742
Comments
andrewdavidwong
added
C: core
enhancement
P: major
labels
Apr 10, 2017
andrewdavidwong
added this to the Release 4.1 milestone
Apr 10, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Apr 10, 2017
Contributor
The same (long since fixed!) un-muting bug has come up at least 6 times that I'm aware of:
- #2550
- #2117
- #2291
- #2321
- https://groups.google.com/forum/#!msg/qubes-users/53TYf5GYkqY/ZU8i5v6JAwAJ
- https://groups.google.com/d/topic/qubes-users/2-IeWlS9Rdg/discussion
Attempted discussion about general fix:
|
The same (long since fixed!) un-muting bug has come up at least 6 times that I'm aware of:
Attempted discussion about general fix: |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
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.
|
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
changed the title from
Dom0 update meta-package
to
Better way to track dom0 updates
Apr 10, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
@jpouellet: Updated the title. Thanks! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
jpouellet
Apr 24, 2017
Contributor
It's possible that whatever solution ends up being identified in #2572 might also solve this issue.
|
It's possible that whatever solution ends up being identified in #2572 might also solve this issue. |
andrewdavidwong commentedApr 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: