Micah Lee: > Hey Mike, I have a question about filenames. > > The 3.0 alpha1s are all hosted here for now? > https://people.torproject.org/~mikeperry/tbb-3.0alpha1-builds/official/ > > But soon (maybe Monday with your blog post) they will be here too? > https://www.torproject.org/dist/torbrowser/linux/ Correct. > Tor Browser Launcher's auto-updating works by loading and parsing > https://check.torproject.org/RecommendedTBBVersions and then uses that > string to build the full URL of the .tar.gz and the .tar.gz.asc files to > download. > > Right now the latest alpha version is "3.0-alpha-1-Linux", so TBL is > trying to download this URL: > > https://www.torproject.org/dist/torbrowser/linux/tor-browser-gnu-linux-x86_64-3.0-alpha-1-dev-en-US.tar.gz > > But that's returning a 404 error for now, because the 3.0-alpha-1s > aren't in https://www.torproject.org/dist/torbrowser/linux/ yet. But > even when they are, it looks like the file naming system has changed. > TBL expects these: > > tor-browser-gnu-linux-i686-3.0-alpha-1-dev-en-US.tar.gz > tor-browser-gnu-linux-x86_64-3.0-alpha-1-dev-en-US.tar.gz > > But it looks like the new files are in this format: > > tor-browser-linux32-3.0-alpha-1_en-US.tar.xz > tor-browser-linux64-3.0-alpha-1_en-US.tar.xz > > They're also .tar.xz files instead of .tar.gz files. When they're > uploading directly to torproject.org/dist will the file names remain in > the format that TBL is currently expecting? Yeah, all of these filename changes are due to various aspects of Gitian that make the bundle names different. The current naming scheme should remain the same for the rest of the 3.0 series, though. As a heads up: somewhere later in the alpha series we will be redoing the directory organization inside the bundles as well. > And do you think it would be possible to only update > RecommendedTBBVersions when there's an associated tarball available > for download in a predictable place so that we don't get into a > situation where there's an updated version but TBL can't find it? There will always be a chicken/egg problem here. We need to update the recommended versions file before the bundles get uploaded so that the first people who download them don't immediately get told they are out of date. > And 3.0 looks great btw! > > On 06/14/2013 11:07 PM, Mike Perry wrote: > > Should be fixed. Good luck! > > > > Micah Lee: > > > >> This is awesome! Can you fix a typo in this file? > >> https://check.torproject.org/RecommendedTBBVersions > >> > >> It says: > >> > >> [ > >> "2.3.25-8-MacOS", > >> "2.3.25-8-Windows", > >> "2.3.25-8-Linux", > >> "2.3.25-9-Linux", > >> "2.4.12-alpha-2-MacOS", > >> "2.4.12-alpha-2-Windows", > >> "2.4.12-alpha-2-Linux" > >> "3.0-alpha-1-Linux" > >> "3.0-alpha-1-MacOS" > >> "3.0-alpha-1-Windows" > >> ] > >> > >> There missing commas at the end of the array. I tried updating to > >> 3.0alpha1 with Tor Browser Launcher but it failed parsing > >> RecommendedTBBVersions. > >> > >> On 06/14/2013 07:39 PM, Mike Perry wrote: > >>> The new TBB 3.0 series is almost ready for its first alpha release! > >>> > >>> Here are the major highlights of the 3.0 series: > >>> > >>> 1. Usability, usability, usability! We've attempted to solve several > >>> major usability issues in this series, including: > >>> > >>> A. No more Vidalia. The Tor process management is handled by the Tor > >>> Launcher extension. If you want the Vidalia features, you can > >>> point an existing Vidalia binary at control port 9151 after Tor > >>> Browser has launched, and it should still work. > >>> > >>> B. The browser now uses a local about:tor homepage instead of > >>> check.torproject.org. A local verification against the control port > >>> is still performed, to ensure Tor is working, and a link to > >>> check.torproject.org is provided from the about:Tor homepage > >>> for manual verification as well. > >>> > >>> C. For Windows users: an NSIS-based extractor now guides you through > >>> the TBB extraction and ensures the extracted bundle ends up on your > >>> Desktop, or in a known location chosen by you. Hopefully this > >>> will mean no more losing track of the extracted bundle files! > >>> > >>> 2. The bundles are all under the 25M gmail attachment size limit, so > >>> direct email and gettor attachments are once again possible. > >>> > >>> 3. We now use Gitian to build the bundles. The idea behind Gitian is to > >>> allow independent people to take our source code and produce exactly > >>> identical binaries on their own. We're not quite at the point where > >>> you always get a matching build, but the remaining differences are > >>> minor, and within a couple more releases we should have it fully > >>> reproducible. For now, we are posting all of the builds for > >>> comparison, and you can of course build and compare your own: > >>> https://gitweb.torproject.org/builders/tor-browser-bundle.git/blob/HEAD:/gitian/README.build > >>> > >>> > >>> Please try these out, test them, and give us feedback! The plan is to > >>> post them on the blog by Monday, unless something goes horribly wrong. > >>> > >>> https://people.torproject.org/~mikeperry/tbb-3.0alpha1-builds/official/ > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> tor-talk mailing list > >>> tor-talk@xxxxxxxxxxxxxxxxxxxx > >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk > >> > >> > >> -- > >> Micah Lee > >> @micahflee > >> > > > > > > > > > -- > Micah Lee > @micahflee > -- Mike Perry
Attachment:
signature.asc
Description: Digital signature
_______________________________________________ tor-talk mailing list tor-talk@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk