-
Notifications
You must be signed in to change notification settings - Fork 46
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
Deal with Whonix 16 EOL #934
Comments
More of a porting to Qubes R4.2 issue (#863) than Whonix issue? Would it help if Whonix 17 was supported on Qubes R4.1? |
Hey @adrelanos, that would be great if possible. There's still a bit of work to do on updating SDW for 4.2, so there will be users on 4.1 for the next few months until Qubes 4.1 hits its EOL. If it is an option, let us know if there's anything we can do to help. |
Discussed with @marmarek. Let's see what can be done. |
Just a just a short status update. Marek doing builds apparently. (QubesOS/updates-status#566 (comment)) I'll see what I can do if something is needed from my side. This is not an announcement / call for testers / etc. |
Thanks a lot @adrelanos (and @marmarek). Since we'll likely go a little bit past the EOL date here - will users receive see any warning screens about the end-of-life e.g. when booting up the VM or making a Tor connection? |
There's a Package
So yeah, actually the plan was as usual to show a one time deprecation popup. One time means there is a "don't show this again" check box which if checked will result in not showing that notice again. If you want to nuke it then [1] In Whonix 17 it's in [2] Paths could be slightly different in Whonix 16. |
It's on Jan 18, 2024. See https://www.qubes-os.org/news/2023/12/22/whonix-16-approaching-eol/.
The text was updated successfully, but these errors were encountered: