Jun 21 2019
Apr 6 2019
Feb 16 2019
I also noticed the file "~/.tb/first-boot-home-population.done" which suggests that whonix does something on first boot
Jan 23 2019
Jan 22 2019
With TPO infrastructure using onions, its now a good idea to switch tb-updater to check for version info and downloads to these more secure mirrors.
Dec 7 2018
Oct 13 2018
We can now grab the browser tarball from the TPO onion instead which makes this ticket obsolete. Close if you concur.
Oct 1 2018
Jul 24 2018
Jun 13 2018
Apr 2 2018
Mar 23 2018
Mar 21 2018
The ticket can be closed now since TPO has fixed the problem. (I do not have the permission to close it.)
Mar 7 2018
Mar 6 2018
Dec 15 2017
In whonix-ws-dvm the status file /var/cache/tb-updater/first-boot-home-population.done is not persistent either.
Dec 4 2017
How do I detect being run inside a DispVM Template? @marmarek
Nov 3 2017
Oct 20 2017
tb-updater fix for Whonix 14 / master.
Backported to Whonix 13 tb-updater.
Here is the fix for tb-updater. Please have a look. Untested. Will test now. If it works, I will backport to Whonix 13 tb-updater.
Is that changing to 127.0.0.1 work on Qubes 3.2? Anyway, yes, it should be good enough for Qubes 4.0.
is already using
Oct 9 2017
Oct 8 2017
> Just setting `tbb_version` or `tbb_hardcoded_version` variable isn't enough, because it isn't propagated through all the layers to postinst of tb-updater.
Just setting tbb_version or tbb_hardcoded_version variable isn't enough, because it isn't propagated through all the layers to postinst of tb-updater. But creating temporarily a configuration file works (in /etc/torbrowser.d).
Use tbb_version there, because tbb_hardcoded_version is unconditionally overridden by /usr/share/tb-updater/tbb_hardcoded_version. But later is ignored if tbb_version is already set.
marmarek (Marek Marczykowski-Górecki):
marmarek added a comment.The problem is back again, 7.0.4 is no longer available at https://dist.torproject.org/torbrowser/ What is the easiest/elegant way to choose different version, without modifying tb-updater package? Some env variable? Some config file? I don't consider https://github.com/SimonSelg/qubes-template-whonix/blob/SimonSelg-fix-tb-updater/whonix-gateway/04_install_qubes_post.sh#L65-L79 elegant...
Oct 7 2017
The problem is back again, 7.0.4 is no longer available at https://dist.torproject.org/torbrowser/
What is the easiest/elegant way to choose different version, without modifying tb-updater package? Some env variable? Some config file? I don't consider https://github.com/SimonSelg/qubes-template-whonix/blob/SimonSelg-fix-tb-updater/whonix-gateway/04_install_qubes_post.sh#L65-L79 elegant...
Sep 20 2017
Since https://github.com/Whonix/qubes-whonix/commit/01964e3c8c53b49aa14e56f7924fce5e88b5a448, other places can simply source /usr/lib/qubes-whonix/utility_function.sh and use PROXY_SERVER variable to get appropriate proxy address.
Aug 30 2017
Aug 26 2017
Yes, it works now: https://travis-ci.org/marmarek/qubes-template-whonix/builds/263033873
Aug 24 2017
tb-updater with updated hardcoded Tor Browser version is now available in Whonix jessie-proposed-updates repository. Could you try a build please? Quite likely it will go past that issue now.
Aug 10 2017
Indeed, TEMPLATE_OPTIONS variable wasn't properly propagated. Fixing this fixes whonix-gateway build:
Aug 9 2017
tb-updater must not be installed on Whonix-Gateway at all cost. It's a blocker, since that messes up a carefully selected and package selection.
K interesting. I'll check this out, thanks.
Also, it worked before (when tor browser 7.0 was still downloadable)... See builds history on travis (https://travis-ci.org/marmarek/qubes-template-whonix/builds).
In above linked travis job, workstation build (17.6) fails with:
(Debugging information: curl_status_message:  - [HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f, --fail is used.])
Probably package installation order is non-deterministic here...
In whonix-ws the package is called anon-ws-dns-conf . Yes I'm sure about that. The build log explicitly says "Couldn't resolve host".
Are you sure about that? According to build log, the issue with whonix-ws is missing 7.0.0 version on server. anon-gw-dns-conf is not installed in whonix-ws
Nope, tb-updater getting installed in whonix-gw doesn't cause this issue.
Ah, you're right. So the second line in my comment _is_ a blocker too.
IMO the chain doesn't solve the issue of tb-updater not getting any internet connectivity during postinst, which is the root cause of this issue ("Couldn't resolve host. The given remote host was not resolved").
I prefer the proper fix, which is a chain of three tickets in total: https://phabricator.whonix.org/T671#14310
Independently (not a blocker), it would be good to find out why tb-updater is installed in whonix-gw.
Aug 6 2017
tb-updater should not be installed on Whonix-Gateway anyhow. That's
strange. That's the root cause to be fixed.
Jul 31 2017
Jul 30 2017
What does it mean in practice?
Also "Couldn't resolve host" doesn't look like file removed from torproject's download server...
Jul 29 2017
The build was done using jessie-proposed-updates, which is still at tbb_hardcoded_version="7.0.0", that download version was removed from torproject's download server. tbb_hardcoded_version wasn't updated to prevent more breakage due unresolved T671.
Jul 23 2017
Jun 14 2017
Jun 7 2017
Jun 6 2017
May 31 2017
May 30 2017
May 5 2017
Unlikely. I've been doing these stable upgrades all the time.
May 3 2017
I sense some evil breakage going on :P
A python download progress bar class. Works with Python 3. Author has since moved to golang.
Apr 29 2017
Mar 15 2017
Mar 10 2017
Jan 18 2017
No newer options in stretch.