On Wed, Feb 12, 2020 at 07:30:22AM +0100, clematis wrote: > 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.
ok good, it's just that in mozilla land, build1 is "first release candidate", that's all - cf https://ftp.mozilla.org/pub/firefox/candidates/73.0-candidates/build1/source/ & https://ftp.mozilla.org/pub/firefox/candidates/73.0-candidates/build2/source/ & https://ftp.mozilla.org/pub/firefox/candidates/73.0-candidates/build3/source/ of course TB-browser might not use the same convention :) > > 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. Great, thanks ! > 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 We'll see what ${MAINTAINER} thinks about it, but at some point an update (9.0.4 or 9.0.5) might get commited with a MAINTAINER timeout.. Landry
