-
Notifications
You must be signed in to change notification settings - Fork 39
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
Packages in dom0 are not being updated #646
Labels
Projects
Comments
Tested an upgrade from 0.5.1 clean install to 0.5.2, confirmed the update logic is restored. Log messages below to illustrate. full launcher.log, included before and after upgrade
To make a bit clearer, here are the specific differences verifying upgrade functionality: Before
After
The "No updates available for dom0" message in the "After" logs shows that the function executed properly:
|
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discovered during post-release testing of 0.5.1 today (#643). The graphical updater has stopped running
qubes-dom0-update
as part of its standard logic, so new RPMs, such as 0.5.1, are not being installed automatically. The upstreamqubes-update-gui
tool is unaffected, and continues to work properly.The problem was introduced in 0.5.0, via the template consolidation PR, specifically this line: https://github.com/freedomofpress/securedrop-workstation/pull/619/files#diff-d0118b9cd7e4fe0ee2bfa80461f1aa3329be6f49d0b29c5874fde88ad7e1e1f0R179
Although the call to
Updater.apply_updates()
properly passes indom0
as a target, the generator returned by that function is never iterated over, so the logic in the function never executes. Compare with the call to the same function lower down, where the results are iterated over: https://github.com/freedomofpress/securedrop-workstation/pull/619/files#diff-d0118b9cd7e4fe0ee2bfa80461f1aa3329be6f49d0b29c5874fde88ad7e1e1f0R197-R201Let's modify that logic to ensure that dom0 packages are updated as a first step. In order for this change to land, we'll need to release a 0.5.2, and once it's available, instruct pilot participants to run
sudo qubes-dom0-update
manually to pull down the latest. Thereafter, a new invocation of the GUI updater will work as expected.The text was updated successfully, but these errors were encountered: