Author: bertagaz Date: To: The Tails public development discussion list Subject: Re: [Tails-dev] Iceweasel backports experiments
Hi,
On Wed, Sep 12, 2012 at 10:34:17AM +0200, intrigeri wrote: > Hi,
>
> bertagaz@??? wrote (10 Sep 2012 21:13:20 GMT) :
> > The build went almost fine appart from a few tests that failed.
> > I don't know if they are green in the iceweasel from wheezy.
>
> FWIW, I tried running "grep -w -c TEST-UNEXPECTED-FAIL" on both your
> backport log and the current wheezy one [0], and the result is:
>
> - 190 for the build of the package that's currently in Wheezy
> - 666 (no kidding) for your backport
I admit I was a bit frustrated about this test, so I took the opportunity
that I was moving part of my package building system to give it another
try on another system.
This time, for a reason I don't really understand, I had less failing
tests than before, even less than the package that is in Debian. The
remaining failing tests were all related to dates, so I guess the pbuilder
chroot environment has something to do in there. This time my build
environment uses pbuilder on tmpfs rather than cowbuilder, isn't inside a
vserver, and its DNS isn't torified. Might explain why less tests are
failing.
Then by curiosity, I tried to see if Torbrowser's patches apply in
Iceweasel source tree, starting from the current squeeze-backports
version. And it appears they are.
I've imported all of them but four that I felt weren't necessary:
I'm not so sure about the branding one, but it probably would require more
work to have it correctly working in Iceweasel.
In the end the build went well and succeeded. There was a bit more failing
tests, but more or less related to plugins and other Torbrowser's patches.
Next step is giving it a try in a Tails session.
Unfortunately I haven't been able to put that in a git, since Iceweasel's
git repo is still not up to date.
