intrigeri wrote:
> kytv wrote (21 Nov 2014 00:46:23 GMT) :
>> The build is currently broken for me when fetching TBB. The original
>> URLs are redirected to https.
>
> I can't reproduce that: our Jenkins has been successfully building
> from the stable and devel branches 15 hours ago.
> What's happening exactly?
I tried it a few times before changing the source and it consistently
failed each time. The log snippet below is from the 3rd or 4th attempt.
Build session log:
Install the Tor Browser^M
Fetching
http://archive.torproject.org/tor-package-archive/torbrowser//4.0/tor-browser-linux32-4.0_ar.tar.xz
...^M
% Total % Received % Xferd Average Speed Time Time Time
Current^M
Dload Upload Total Spent Left
Speed^M
^M 0 0 0 0 0 0 0 0 --:--:-- --:--:--
--:--:-- 0^M100 380 100 380 0 0 1081 0 --:--:--
--:--:-- --:--:-- 2638^M
SHA256 mismatch for tor-browser-linux32-4.0_ar.tar.xz^M
E: config/chroot_local-hooks/10-tbb failed (exit non-zero). You should
check for errors.^M
P: Begin unmounting filesystems...^M
^M
real 6m5.990s^M
user 3m50.920s^M
sys 0m55.940s^M
lb build failed (1).^M
root@tailsbuilder:/build# find . -name tor-browser-linux32-4.0_ar.tar.xz ^M
./chroot/tmp/tmp.7e0yW4OCCe/tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build# cd chroot/tmp/tmp.7e0yW4OCCe/^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# ls^M
tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# ls -lh^M
total 4.0K^M
-rw-r--r-- 1 root root 380 Nov 21 00:01 tor-browser-linux32-4.0_ar.tar.xz^M
root@tailsbuilder:/build/chroot/tmp/tmp.7e0yW4OCCe# cat
tor-browser-linux32-4.0_ar.tar.xz ^M
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">^M
<html><head>^M
<title>301 Moved Permanently</title>^M
</head><body>^M
<h1>Moved Permanently</h1>^M
<p>The document has moved <a
href="https://archive.torproject.org/tor-package-archive/torbrowser//4.0/tor-browser-linux32-4.0_ar.tar.xz">here</a>.</p>^M
<hr>^M
<address>Apache Server at archive.torproject.org Port 80</address>^M
>> This completely trivial change fixes the build by eliminating the
>> need for the redirect.
>
> Apparently, using https:// URLs breaks things with apt-cacher-ng.
> Are you using apt-cacher-ng or another HTTP proxy? If yes, which
> version?
s/trivial/useless/
I'm using apt-cacher-ng, 0.8.0-1 but the time of my change I disabled
acng to rule it out as being the culprit for the failures (this was a
completely new build environment). When I made my change it was used
without re-enabling acng.
I re-enabled acng and *now* the build works without this change and
without any other changes to my environment. Was someone at t.p.o
perhaps tinkering with the server config at the same time I was trying
to build?
>> git://repo.or.cz/tails/kytv.git bugfix/tbb-via-https
>
> Please base bugfix branches on top of stable.
Oops. Obvious and stupid mistake there. Sorry.
