On 08/10/2014 06:30 AM, intrigeri wrote:
> https://lists.torproject.org/pipermail/tor-qa/2014-August/000439.html
> 
> (Maybe some of the torbrowser-launcher package maintainers should read
> that low-volume list?)

Good idea, I'll subscribe.

The main upstream bug is at [1]. But there are a couple things going on
here.

The format of the RecommendedTBBVersions file [2] keeps changing
(upstream bug [3]). It was only listing stable releases for a long time,
and then with this next release it started listing alphas again.

And TBL has been checking TBB releases against Mike Perry's key using
the file sha256sums.txt-mikeperry.asc, but the new releases don't have
that file, only sha256sums.txt.asc and Erinn Clark's key. Which means
that debian bug [4] and upstream bug [5] look like they're not possible,
until we get clarity from the Tor devs.

I'm preparing an upstream release to fix this. But I'm also at an
airport and my plane is already boarding, so if there isn't wifi on the
plane I might not be able to get to it until late tonight.

[1] https://github.com/micahflee/torbrowser-launcher/issues/120
[2] https://check.torproject.org/RecommendedTBBVersions
[3] https://github.com/micahflee/torbrowser-launcher/issues/63
[4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756194
[5] https://github.com/micahflee/torbrowser-launcher/issues/113

-- 
Micah Lee

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to