#877396 torbrowser-launcher: no migration path possible from tbb 6.5.1 to 7.0.6 (News.debian.gz)

Package:
torbrowser-launcher
Source:
torbrowser-launcher
Submitter:
shirish शिरीष
Date:
2017-12-02 20:42:03 UTC
Severity:
normal
#877396#5
Date:
2017-10-01 11:41:18 UTC
From:
To:
Dear Maintainer,

This is more of an upstream issue rather than Debian's but still
reporting so that others are aware and maybe it can be documented in
News.Debian.gz

See https://www.debian.org/doc/manuals/developers-reference/best-pkging-practices.html#bpp-news-debian
for what I mean.

I had been using torbrowser 6.5.1 for a long time and each time trying
to update/upgrade it failed.

Now because the browser detaches itself from the console I do not
know/have any other way to document why the update fails but just know
it fails.

The only way (sadly) is to remove your tbb profile from
~/.local/share/tbb and then try running torbrowser-launcher. It
downloads the latest version and now it also updates to point versions
as I experienced on couple of other debian boxes where I had done the
change earlier.

It would be nice if this pain point is mentioned in a NEWS.gz file so
people can know about it and take proper action.

FWIW I tried both 0.2.8-2 and 0.2.8-3 with .local/share/tbb old
profile in the hopes that the profile will also get upgraded which
sadly didn't happen and was forced to have a new blank profile which I
would build over days and weeks etc.

#877396#10
Date:
2017-12-02 20:38:35 UTC
From:
To:
Again after the update, the file/binary goes missing and have to do
the whole thing again.


I still burrowed again a bit and found this is where it stays/is
occupied when it works -

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser>
ls | grep start-tor
[100%]
start-tor-browser
start-tor-browser.desktop


Just to make sure it wasn't a symlink I had it listed long -

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser>
ll -h start-tor-browser
[100%]
-rwx------ 1 shirish shirish 13K 2000-01-01 05:30 start-tor-browser

that turned out to be the script and not actually firefox with
whatever scripts it is supposed to run.

The real deal seems to happen after this longwinded-route after

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser>


The profile sits in


/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/TorBrowser/Data/Browser>
ls             [100%]
.  ..  Caches  profile.default  profile.meek-http-helper  profiles.ini

and just transfer tree things, key3.db, logins.json and persdict.dat

Documenting it here so if anybody has the same issue tey know what to do.