On Tue, Feb 11, 2020 at 10:12:20PM +0100, Caspar Schutijser wrote: > On Tue, Feb 11, 2020 at 03:23:03PM +0100, Landry Breuil wrote: > > On Sat, Jan 11, 2020 at 03:43:06PM +0100, Caspar Schutijser wrote: > > > On Fri, Jan 10, 2020 at 10:31:15AM +0000, Stuart Henderson wrote: > > > > On 2019/12/28 09:07, Caspar Schutijser wrote: > > > > That seems built on top of a release candidate tarball > > (src-firefox-tor-browser-68.4.1esr-9.0-1-build1) is it expected ? > > To the best of my knowledge, it is not a release candidate tarball. > It is the only file in that directory of their mirror > (https://dist.torproject.org/torbrowser/9.0.4/) which contains source > code for the Tor Browser, I think. But I may be wrong. What makes you > think the tarball contains a release candidate? The structure of the > name of the distfile is definitely a little unusual.
That's a good question, I will try to ask upstream see how to identify release candidate, but as per the release note, Tb-browser 9.0.4 was to update Firefox to 68.4.1esr. > > Would > > be good to get that commited so that this port is not left rotting > > in-tree, can anyone give it a testbuild with rust 1.41 that just got > > updated ? > > I can probably do this during the weekend but if someone beats me to it > that's fine of course. gdb-7.12.1p9 rust-1.41.0 tb-browser-9.0.4 tb-noscript-11.0.11 tb-https-everywhere-2019.11.7 build/package/install OK on amd64 with rust-1.41.0 Just ran it a bit this morning and it's working as expected. Well, seems like 9.0.5 is in the pipe [1] Tor Browser 9.0.5 -- February 11 2020 * All Platforms * Update Firefox to 68.5.0esr * Bump NoScript to 11.0.13 * Bug 32053: Fix LLVM reproducibility issues * Bug 32255: Missing ORIGIN header breaks CORS * Bug 32891: Add new default bridges [1] https://gitweb.torproject.org/builders/tor-browser-build.git/plain/projects/tor-browser/Bundle-Data/Docs/ChangeLog.txt?h=maint-9.0 Hope this help. Cheers, -- clematis (0x7e96fd2400fe7b59)
