[email protected] wrote (19 May 2015 04:25:03 GMT) : > See <https://jenkins.tails.boum.org/job/build_Tails_ISO_feature-jessie/493/>
> Selected version '0.2.0-1' (testing) for torbrowser-launcher This is wrong. The root cause is, I believe, that current devel hasn't been merged into feature/jessie yet => feature/jessie lacks 'testing' APT sources => our build system can't possibly fetch the right version of torbrowser-launcher source package. So: anonym's plate++ > patching file /etc/apparmor.d/torbrowser > Hunk #3 FAILED at 79. > Hunk #4 succeeded at 87 (offset 1 line). > 1 out of 4 hunks FAILED -- saving rejects to file > /etc/apparmor.d/torbrowser.rej > E: config/chroot_local-hooks/19-install-tor-browser-AppArmor-profile failed > (exit non-zero). You should check for errors. That's exactly what our fancy system should avoid (5-days unstable->testing migration + Jenkins job that tries to merge upstream profiles into our own forked ones), but in this case it could not possibly help due to the above problem. _______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
