Kevin O'Gorman
Kevin O'Gorman
No CI failures so this is most likely dev machine specific. Closing.
Leaving open - work is ongoing on automating provisioning of Qubes setups for test purposes, which aligns with the approach in this issue.
Recent user feedback indicates that this is still a point of confusion. To be addressed with printing improvements.
I don't recall one - I think the big issue for me with that would be deviation from stock Qubes.
In terms of the f39 update, it's pretty straightforward and I'd be inclined to do a 4.1 point release to cover it (with absolutely nothing else in scope, branching off...
Ongoing and planned work on provisioning improvements will catch the stragglers here. Leaving open for now.
I think for that last point there would be some unavoidable Salt additions. At the very least we need to install our release pubkey and set up the repo. It...
Do we use `qubes-dom0-update` for prod installs? By current docs the initial install is also via `dnf`.
If we had a key+repo-config-only rpm (ideall,y that was available via a regular qubes dom0 repo) then you could probably install *that* via `dnf` and then you'd be home free...
Flagging for @deeplow's attention - if possible we should update the list of non-dom0 target VMs after any potential dom0 chnages, maybe using VM tags instead of an explicit list.