intrigeri wrote (28 May 2015 11:27:38 GMT) : > The root cause is that libeatmydata on Jessie is installed in > a multiarch path, but LD_PRELOAD is passed by Wheezy's eatmydata, so > points to a non-multiarch path. Perhaps the easiest solution is to > upload Jessie's eatmydata to wheezy-backports, and require that > version on Wheezy build systems. Thoughts?
Actually, eatmydata from Jessie installs just fine on Wheezy. Any problem with requiring having Jessie's APT sources + proper pinning on build systems? I can easily implement it on [[contribute/build]] and on our Jenkins ISO builders. Not sure about Vagrant. Now, another solution would be to just stop using eatmydata entirely, given its benefit are tiny in most common build envs (building in tmpfs), and only really beneficial in corner cases (building without a tmpfs). Thoughts? Cheers, -- intrigeri _______________________________________________ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
