Hi Antonio, I hoped you would jump in here, as I'm quite clueless what this is about, or what is wrong:
On 18-04-05 08:10:09, Antonio Terceiro wrote: > On Thu, Apr 05, 2018 at 09:49:02AM +0200, Georg Faerber wrote: > > On 18-04-05 07:53:57, Cédric Boutillier wrote: > > > On Wed, Apr 04, 2018 at 10:56:31PM +0200, Georg Faerber wrote: > > > > flock: failed to execute mispipe: No such file or directory > > > > > > mispipe is in the moreutils package. Do you have it installed? It > > > is recommended by debci. > > > > Thanks, this made the setup part work (I still believe that this is > > quite similar to autopkgtest-build-lxc). > > it is. the container creation part it just a call to `sudo debci > setup`, which in turn basically just calls autopkgtest-build-lxc. Thanks for clarification. > > However, running > > build-and-upload after this leads to the same result: > > > > [...] > > autopkgtest [09:41:33]: version 5.2 > > autopkgtest [09:41:33]: host debian; command line: /usr/bin/autopkgtest > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc -- lxc > > autopkgtest-unstable-amd64 > > autopkgtest [09:41:53]: testbed dpkg architecture: amd64 > > autopkgtest [09:41:54]: testbed running kernel: Linux 4.15.0-1-amd64 #1 SMP > > Debian 4.15.4-1 (2018-02-18) > > autopkgtest [09:41:54]: @@@@@@@@@@@@@@@@@@@@ source > > /home/georg/code/debian/ruby-team/build-area/ruby-sequel_5.7.0-1.dsc > > Cannot execute /bin/sh > > ^ this is very weird Yes, it is. Especially, because it works if called manually.. > does the autopkgtest-unstable-amd64 lxc container work fine otherwise? > e.g. > > [...] All of this works as expected.. Thanks for your help, Georg
signature.asc
Description: Digital signature
