Your message dated Sat, 26 Dec 2015 08:15:55 +0100
with message-id <20151226071555.4674.56593@localhost>
and subject line Re: sbuild: sbuild-shell fails with E: Failed to create build 
directory /build
has caused the Debian Bug report #717523,
regarding sbuild: sbuild-shell fails with E: Failed to create build directory 
/build
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
717523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717523
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.64.0-1
Severity: normal

I have followed the directions listed at http://wiki.debian.org/sbuild
to create a chroot, and now trying to run sbuild-shell to install some
packages:

  vauxhall ok % sudo sbuild-shell source:sid-amd64-sbuild
  E: Failed to create build directory /build
  Failed to set up chroot
  Error setting up source:sid-amd64-sbuild chroot
  Chroot setup failed at /usr/bin/sbuild-shell line 42.

Trying sbuild-update fails in a similar way:

  vauxhall no % sudo sbuild-update -ud sid
  E: Failed to create build directory /build
  Failed to set up chroot
  Error setting up sid chroot
  Chroot setup failed at /usr/bin/sbuild-update line 168.

I expect any command that I run will be equally functional.

I have not found any documentation dealing with this issue, so if this
is something trivial to fix, please consider this a request for adding
documentation that will help users solve the problem for themselves.

The chroot information is below:

  [sid-amd64-sbuild]
  type=file
  description=Debian sid/amd64 autobuilder
  file=/var/lib/sbuild/sid-amd64.tar.gz
  groups=root,sbuild
  root-groups=root,sbuild

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.10-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sbuild depends on:
ii  adduser         3.113+nmu3
ii  apt-utils       0.9.9.2
ii  libsbuild-perl  0.64.0-1
ii  perl            5.14.2-21
ii  perl-modules    5.14.2-21

Versions of packages sbuild recommends:
ii  debootstrap  1.0.53
ii  fakeroot     1.19-2

Versions of packages sbuild suggests:
ii  deborphan  1.7.28.8
ii  wget       1.14-2

-- no debconf information

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Version: 0.66.0-5

Quoting brian m. carlson (2015-12-25 23:48:04)
> On Thu, Dec 24, 2015 at 01:07:33AM +0100, Johannes Schauer wrote:
> > On Sun, 21 Jul 2013 22:20:26 +0000 "brian m. carlson" 
> > <[email protected]> wrote:
> > > I have followed the directions listed at http://wiki.debian.org/sbuild
> > > to create a chroot, and now trying to run sbuild-shell to install some
> > > packages:
> > > 
> > >   vauxhall ok % sudo sbuild-shell source:sid-amd64-sbuild
> > >   E: Failed to create build directory /build
> > >   Failed to set up chroot
> > >   Error setting up source:sid-amd64-sbuild chroot
> > >   Chroot setup failed at /usr/bin/sbuild-shell line 42.
> > > 
> > > Trying sbuild-update fails in a similar way:
> > > 
> > >   vauxhall no % sudo sbuild-update -ud sid
> > >   E: Failed to create build directory /build
> > >   Failed to set up chroot
> > >   Error setting up sid chroot
> > >   Chroot setup failed at /usr/bin/sbuild-update line 168.
> > > 
> > > I expect any command that I run will be equally functional.
> > > 
> > > I have not found any documentation dealing with this issue, so if this
> > > is something trivial to fix, please consider this a request for adding
> > > documentation that will help users solve the problem for themselves.
> > 
> > I cannot reproduce this problem. Can you try again and confirm that you are
> > still seeing this problem? Otherwise I'll close this bug as unreproducible.
> 
> I'm not using sbuild at the moment, so it's fine to close this.  I'll
> reopen it if I start using sbuild again and it reoccurs.

okay, closing

Attachment: signature.asc
Description: signature


--- End Message ---

Reply via email to