Hi josch, On Donnerstag, 1. Januar 2015, Johannes Schauer wrote: > that would be great, because then I could test everything locally and only > submit you one commit that makes everything work instead of going back and > forth :)
the schroot setup is defined in dpkg.yaml... it should be better explained in
README one day...
> Which is the "part where the jessie chroot is created"? Casually looking
> through files in job-cfg which use chroot-run.sh I cannot see where to add
> additional packages to the chroot.
from dpkg.yaml:
my_shell: '/srv/jenkins/bin/schroot-create.sh dpkg-jessie jessie
python apt-file dose-extra'
-> create a schroot called jenkins-dpkg-jessie, base it on jessie and install
the additional packages python, apt-file and dose-extra.
So now https://jenkins.debian.net/view/d-
i_misc/job/dpkg_sid_find_trigger_cycles/19/console has this issue:
curl: (5) Could not resolve proxy: $http_proxy
I'll look into this now...
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
