[quote=“Patrick, post:1, topic:1038”]https://phabricator.whonix.org/T273 made me think. I am not sure it’s worth trying to get a Whonix 10 based qubes-whonix ready. Because Whonix 10 is wheezy / sysvinit based and Whonix 11 will be jessie / systemd based.
Have a very small task list.
Wheezy / systemd just doesn’t work well together. Shipping the systemd unit files in the qubes-whonix package would likely lead to issues, when these unit files are later removed and moved to the appropriate specific packages (such as control-port-filter-python). Namely, the package manager would refuse upgrading, because the file is already owned by another package, unless we figure out using some complex - easy to get wrong - ‘replaces’ (Debian packaging terminology) magic.[/quote]
What ya mean Wheezy / systemd doesn’t work well together? It pretty much works as expected. As the ‘distributor’ of a package, you will be expected to place those unit files in ‘/lib/systemd/system’ for files such as ‘control-port-filter-python’. Now, Tor on the other hand is not distributed by you, so you would then place the Whonix overriding unit file in ‘/etc/systemd/system’ as that is meant for local unit files.
Therefore qubes-whonix can create a ‘/etc/systemd/system/control-port-filter-python’ and ‘/etc/systemd/system/qubes-whonix-tor’ (which will can set a requires / conflict so as not to run when whonix provides its own). This is pretty simple and standard and really only needs a bit of planing, which I think we just did
So options are, we maintain Whonix 9 with all it's issues (Tor Browser starter, updater broken and more) a little more and skip Whonix 10 [although non-Qubes versions are in RC and quite releaseable, looks like] or skip Whonix 10, get quickly Whonix 11 with full jessie / systemd support ready.
I guess if you want to get Whonix 10, originally wheezy / sysvinit to work for qubes-whonix (due to requirement on systemd) you’ll be going in circles and there will still be weird [upgrading] issues.
So, given that there is an easy solution to this issue, and that I have Whonix 10 ready to go, I would suggest I make the suggested changes and let it roll.
I also suggest you add a ‘–testing-current-sources’ option to your current builder so I can start building Whonix in Jessie