Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Sean Whitton wrote on Wed, Sep 14, 2016 at 07:40:00 -0700: > On Wed, Sep 14, 2016 at 07:17:10AM -0700, Sean Whitton wrote: > > I think that the current stable sbuild is meant to be able to build > > for unstable (pretty common use case), so if you can reproduce it, a > > stable update might be in order. > > Sorry for a second e-mail, but I just remembered that there is a > backport of a version of sbuild that can build for unstable, so I don't > think the sbuild maintainer would want to a stable update in addition to > this. If you can reproduce the bug with the backport, though, it should > definitely be reported. I can't reproduce the problem with sbuild 0.70.0-1~bpo8+1. Thanks for the help Sean. Daniel
Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Hello Daniel, On Wed, Sep 14, 2016 at 07:17:10AM -0700, Sean Whitton wrote: > I think that the current stable sbuild is meant to be able to build > for unstable (pretty common use case), so if you can reproduce it, a > stable update might be in order. Sorry for a second e-mail, but I just remembered that there is a backport of a version of sbuild that can build for unstable, so I don't think the sbuild maintainer would want to a stable update in addition to this. If you can reproduce the bug with the backport, though, it should definitely be reported. -- Sean Whitton
Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Hello Daniel, On Wed, Sep 14, 2016 at 04:46:02AM +, Daniel Shahaf wrote: > I still don't know why the stable sbuild didn't work, though. (Or > whether upgrading sbuild was the fix: perhaps something changed in the > archive since Friday.) Should I file a bug about that? It's more likely just an archive change, so I wouldn't file a bug unless you can reliably reproduce it. That said, I think that the current stable sbuild is meant to be able to build for unstable (pretty common use case), so if you can reproduce it, a stable update might be in order. -- Sean Whitton
Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Sean Whitton wrote on Tue, Sep 13, 2016 at 17:08:03 -0700: > Does etc exist in /srv/chroot/unstable-amd64 (or wherever you have the > base chroot)? No, it doesn't exist: % tar tf unstable-amd64.tar.gz | cut -d/ -f 1,2 | uniq -c 1 ./ 2668 ./usr 65 ./sbin 1 ./build 1 ./mnt 5 ./run 1 ./proc 46 ./dev 65 ./bin % When I create /etc in the tarball, I get further errors, about various other dirents not existing: /etc/apt/apt.conf.d/, /root, /bin/bash, even /bin/sh. By comparison, the (working) jessie chroot has: % tar tf jessie.tar.gz | cut -d/ -f 1,2 | uniq -c | sort -n ⋮ 82 ./sbin 103 ./bin 354 ./etc 607 ./lib 898 ./var 10887 ./usr % I created the sid chroot last Friday with «/usr/sbin/sbuild-createchroot --include=eatmydata --make-sbuild-tarball=/path/to/unstable-amd64.tar.gz unstable `mktemp -d` http://httpredir.debian.org/debian». At the time I used sbuild from stable (0.65.2-1). I just now re-created that chroot using sbuild 0.71.0-2 (locally rebuilt on jessie), and it now works. I still don't know why the stable sbuild didn't work, though. (Or whether upgrading sbuild was the fix: perhaps something changed in the archive since Friday.) Should I file a bug about that? Thanks, Daniel
Re: schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Dear Daniel, Does etc exist in /srv/chroot/unstable-amd64 (or wherever you have the base chroot)? -- Sean Whitton
schroot: 20copyfiles: cp: cannot create regular file '.../etc/resolv.conf'
Hello, I usually build packages in a sid chroot using sbuild, but that stopped working at some point: % sudo schroot -c source:unstable-amd64-sbuild -d /root E: 20copyfiles: cp: cannot create regular file '/var/run/schroot/mount/unstable-amd64-sbuild-0d2f358b-da5e-41fa-8221-d416e21f9d2e/etc/resolv.conf': No such file or directory E: unstable-amd64-sbuild-19f85771-f85c-4a5d-89da-3c6644ff7005: Chroot setup failed: stage=setup-start zsh: exit 1 The 'cp' fails because /var/run/schroot/mount/unstable-amd64-sbuild-0d2f358b-da5e-41fa-8221-d416e21f9d2e/ exists but does not have an "etc/" subdirectory. It works fine with a jessie schroot on the same host. The host runs jessie. schroot version is 1.6.10-2~bpo8+1. What might be the problem? Thanks, Daniel
