Hi,
from #debian-qa this morning:
h01ger | #766921 - anybody have an idea why adding gcc to the chroot helps?
ntyni | h01ger: looks like eatmydata calls dpkg-architecture which calls gcc
h01ger | ah!
h01ger | so the options are really just disabling eatmydata or adding gcc?
mapreri | h01ger: you
On 2014-11-13 12:41, Holger Levsen wrote:
mapreri | h01ger: well, is there a pythonic way to preload library? :)
we don't need it in python, we need it for the chroot ... just adding
something to the environment for the run() should do
def run(..., extra_env=[])
...
if extra_env:
On Nov 13, 2014, at 12:41 PM, Holger Levsen wrote:
mapreri | h01ger: well, is there a pythonic way to preload library? :)
A *very* quick look at piuparts seems to show that the run() function is used
to run subprocesses from piuparts. You can even see where this function is
setting up the env
I ran into this too while trying to reproduce locally bug #768286. I ended up
actually modifying /usr/sbin/piuparts to add --include=gcc as an option, which
is sub-optimal. I wonder if it makes sense to add an option to piuparts so
that additional options can be passed to debootstrap?
--
To
4 matches
Mail list logo
