Hi Cédric,

On 18-04-04 22:14:23, Cédric Boutillier wrote:
> Just a short question before going further:
> 
> Did you use the './setup' script in the meta repository to set up your
> autopkgtest environment ?

Honestly, I don't remember anymore; I've set this up initially ~ two years ago,
when I've started with Debian packaging.

Yesterday, I've tried build-and-upload for the first time, to check rdepends.
Because this didn't work OOTB (in contrast to calling autopkgtest via gbp
buildpackage / sbuild), I've used autopkgtest-build-lxc to create a new
container to check if this would make it work.

This failed as well, thus this thread.

Running setup gives the following:

+ sudo apt-get install -qy --no-remove autopkgtest build-essential gem2deb git 
git-buildpackage myrepos quilt sbuild lxc debci 
Reading package lists...
Building dependency tree...
Reading state information...
myrepos is already the newest version (1.20160123).
autopkgtest is already the newest version (5.2).
build-essential is already the newest version (12.4).
debci is already the newest version (1.8).
gem2deb is already the newest version (0.38.1).
lxc is already the newest version (1:2.0.9-6).
quilt is already the newest version (0.63-8.2).
sbuild is already the newest version (0.75.0-1).
git is already the newest version (1:2.17.0-1).
git-buildpackage is already the newest version (0.9.8).
0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded.
+ sudo sbuild-adduser georg
The user `georg' is already a member of `sbuild'.

# Setup tasks for sudo users:

# BUILD
# HOME directory in chroot, user:sbuild, 0770 perms, from
# passwd/group copying to chroot, filtered
# Maybe source 50sbuild, or move into common location.

Next, copy the example sbuildrc file to the home directory of each user and
set the variables for your system:

  cp /usr/share/doc/sbuild/examples/example.sbuildrc /home/georg/.sbuildrc

Now try a build:

  cd /path/to/source
  sbuild-update -ud <distribution>
  (or "sbuild-apt <distribution> apt-get -f install"
       first if the chroot is broken)
  sbuild -d <distribution> <package>_<version>
+ dpkg --print-architecture
+ chrootname=unstable-amd64-sbuild
+ chroot=/srv/chroot/unstable-amd64-sbuild
+ schroot --list --all-source-chroots
+ grep source:unstable-amd64-sbuild
source:unstable-amd64-sbuild
+ :
+ grep -l ^union-type= /etc/schroot/chroot.d/stretch-amd64-sbuild-zB1PYf 
/etc/schroot/chroot.d/stretch-backports-amd64-sbuild-KINeA1 
/etc/schroot/chroot.d/unstable-amd64-sbuild-MbgSkA
+ grep -q ^union-overlay-directory= 
/etc/schroot/chroot.d/stretch-amd64-sbuild-zB1PYf
+ echo union-overlay-directory=/dev/shm
+ sudo tee --append /etc/schroot/chroot.d/stretch-amd64-sbuild-zB1PYf
union-overlay-directory=/dev/shm
+ grep -q ^union-overlay-directory= 
/etc/schroot/chroot.d/stretch-backports-amd64-sbuild-KINeA1
+ grep -q ^union-overlay-directory= 
/etc/schroot/chroot.d/unstable-amd64-sbuild-MbgSkA
+ grep -q /var/cache/apt/archives /etc/schroot/sbuild/fstab
+ grep -q ^lxc.network.type\s*=\s*empty /etc/lxc/default.conf
+ sudo debci setup
Starting testbed setup: Wed Apr  4 22:53:25 CEST 2018
flock: failed to execute mispipe: No such file or directory

(I guess, looking at the above output, I've used this to set up my env
in the first place. Maybe there is a regression, somewhere?)

Thanks for your help,
Georg

Attachment: signature.asc
Description: Digital signature

Reply via email to