-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Qubes-Whonix 16 for Qubes R4.0 #6891
Comments
That will fail the code signing check I believe. |
Demi Marie Obenour:
> * Waiting for [Whonix 16 qubes-mgmt-salt-dom0-virtual-machines#40](QubesOS/qubes-mgmt-salt-dom0-virtual-machines#40) to be merged at Qubes.
>
> * Edit was made using github web interface. I hope that's OK for minor edits?
That will fail the code signing check I believe.
Could have been. Was also wondering about that. Very glad that
minor/trivial changes are still being accepted through github web interface.
|
Known issue: Default Qubes appmenu is empty. - Maybe fixed in next build. |
It looks like sys-whonix based on whonix-gw-16 doesn't work as dom0 updatevm (DNF not configured to get DNS over tor?):
|
I was just told in #1778 (comment) that Qubes-Whonix 16 is already in the stable repo, which is quite surprising, as I saw no indication of that here. The link about the staged rollout doesn't provide any details about how exactly the staged rollout for Qubes-Whonix 16 works, and it's unclear to me at what point in the staged rollout we should publish Qubes announcements for these new templates. I guess you should just let me know when, @adrelanos. |
Right. Generally plan: stage 1: stage 2: stage 3: Specifically this time: Waiting for some fixes to be tested (default Qubes appmenu) and migrating to stable before starting stage 2. Current stable templates probably soon the be replaced with these ones:
Yes, thank you! :) |
Created #6913 for it. |
I would like to suggest moving all of these...
to stable. @marmarek No big changes were introduced. Just small bugfixes. Testing completed. (Could also wait the minimum time but I doubt someone else would test and report and blocking bugs before that.) Once that's done, I'll write an announcement in the usual Whonix place. |
Next: I'd suggest to wait a few days before announcing on Qubes news. But if there was a draft, I'd of course have a look. |
May I ask why? Users have only one month to upgrade, and each day we wait is one fewer day they have.
Opened QubesOS/qubes-posts#84. Please review when you get a chance. |
Staged rollout.
Right, well. No problem. I wouldn't start the counter until "fully released". The spirit isn't to be overly strict about it. Arguably (?) according to https://www.whonix.org/wiki/About#Support_Schedule we previously said we'd post a deprecation notice at https://forums.whonix.org/c/news which might be a good idea for clarification anyhow. The deadline doesn't mean:
Just that the more time passes, release upgrades can become increasingly difficult that it becomes infeasible to troubleshoot and that questions "how do I x,y, z on deprecated version x" become more confusing for other readers and harder to answer since fewer and fewer people are using it.
Looks perfect! |
Ok, but some users become a bit confused when they see an announcement from the Whonix Project that Whonix 16 has been released with no similar announcement from the Qubes OS Project. Example (see replies):
Ok, that's good. It's unclear to me what the official release date is with a staged rollout.
No, those are not the concerns. Rather, the concern is that there are no more security patches for EOL releases, so users definitely want to upgrade from Whonix 15 before it reaches EOL. If they're too slow or too late, they may be vulnerable to unpatched security bugs in their Whonix qubes.
Thanks! Since it's been a couple days, I'll go ahead and publish it now. |
@adrelanos, could you let me know when Whonix 15 has officially reached EOL so that I can make another announcement and update https://www.qubes-os.org/doc/supported-releases/#templates? |
I see. Well, since this release seems to not cause many upgrade troubles anyhow...
Posted deprecation notice just now. https://forums.whonix.org/t/whonix-15-deprecation-notice-all-users-should-upgrade-to-whonix-16/12473
I see. Seems like there are many ways to define "supported". Will keep this in mind.
Does https://forums.whonix.org/t/whonix-15-deprecation-notice-all-users-should-upgrade-to-whonix-16/12473 clarify it? I see https://www.qubes-os.org/news/2021/09/30/whonix-16-template-available/ was published, thank you! |
Yes, thanks. I'll set a reminder for myself to perform the aforementioned actions on 2021-11-14. |
Status:
Qubes-Whonix 16 images details:
Waiting for Whonix 16 qubes-mgmt-salt-dom0-virtual-machines#40 to be merged at Qubes.Edit was made using github web interface. I hope that's OK for minor edits?Images built:qubes-template-whonix-gw-16 4.0.6-202109061137 (r4.0) updates-status#2613(contains some discussion)qubes-template-whonix-ws-16 4.0.6-202109061137 (r4.0) updates-status#2614Any further Qubes salt changes required or something else?
The text was updated successfully, but these errors were encountered: