Package: mini-buildd
Version: 1.0.41
Severity: important

Hi,

I had to rebuild my mini-buildd builder on armhf, a Banana Pi. After installing
mini-buildd and installing sources and gnupg keys, I proceeded to build
the file chroots, which fails:

Aug  2 06:52:01 banana [CP Server Thread-6 ] WARNING : # 
/usr/sbin/debootstrap.. (stdout): W: Failure trying to run: chroot 
"/var/lib/mini-buildd/var/chroots/stretch/amd64/tmp" /bin/true 
[mini_buildd.call:116]
Aug  2 06:52:01 banana [CP Server Thread-6 ] WARNING : # 
/usr/sbin/debootstrap.. (stdout): W: See 
/var/lib/mini-buildd/var/chroots/stretch/amd64/tmp/debootstrap/debootstrap.log 
for details [mini_buildd.call:116]
Aug  2 06:52:01 banana [CP Server Thread-6 ] ERROR   : Sequence failed at: 1 
(rolling back) [mini_buildd.call:153]
Aug  2 06:52:01 banana [CP Server Thread-6 ] INFO    : Called with retval 64: 
sudo -n /bin/umount -v /var/lib/mini-buildd/var/chroots/stretch/amd64/tmp/proc 
/var/lib/mini-buildd/var/chroots/stretch/amd64/tmp/sys  [mini_buildd.call:72]
Aug  2 06:52:01 banana [CP Server Thread-6 ] WARNING : # /bin/umount.. 
(stderr): umount: /var/lib/mini-buildd/var/chroots/stretch/amd64/tmp/proc: not 
mounted. [mini_buildd.call:116]
Aug  2 06:52:01 banana [CP Server Thread-6 ] WARNING : # /bin/umount.. 
(stderr): umount: /var/lib/mini-buildd/var/chroots/stretch/amd64/tmp/sys: not 
mounted. [mini_buildd.call:116]
Aug  2 06:52:03 banana [CP Server Thread-6 ] INFO    : Called with retval 0: 
sudo -n /bin/rm --recursive --one-file-system --force 
/var/lib/mini-buildd/var/chroots/stretch/amd64/tmp  [mini_buildd.call:72]
Aug  2 06:52:03 banana [CP Server Thread-6 ] ERROR   : prepare failed: Debian 
'stretch:amd64' (tar): Call failed with retval 1: 'sudo -n 
/usr/sbin/debootstrap --variant buildd --keyring 
/var/lib/mini-buildd/var/chroots/stretch/amd64/keyring.gpg --arch amd64 stretch 
/var/lib/mini-buildd/var/chroots/stretch/amd64/tmp 
http://debian.debian.zugschlus.de/debian/ ' [base:368] 
[mini_buildd.models.base:78]

I would be able to debug this if the log mentioned by debootstrap was
here. It is not, it gets deleted by mini-buildd after the failure.

Too bad, so I need upstream's help again.

Greetings
Marc

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 5.2.5-zgbpi-armmp-lpae (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mini-buildd depends on:
ii  adduser                3.118
ii  debconf [debconf-2.0]  1.5.72
ii  debootstrap            1.0.115
ii  devscripts             2.19.6
ii  dirmngr                2.2.17-3
ii  dpkg-dev               1.19.7
ii  gnupg                  2.2.17-3
ii  libjs-jquery           3.3.1~dfsg-3
ii  libjs-sphinxdoc        1.8.5-2
ii  lintian                2.16.0
ii  lsb-base               10.2019051400
ii  mini-buildd-common     1.0.41
ii  python                 2.7.16-1
ii  python-cherrypy3       8.9.1-2
ii  python-daemon          2.2.3-1
ii  python-mini-buildd     1.0.41
ii  python-pyftpdlib       1.5.4-1
ii  reprepro               5.3.0-1
ii  sbuild                 0.78.1-2
ii  schroot                1.6.10-6+b1
ii  sudo                   1.8.27-1

Versions of packages mini-buildd recommends:
ii  python-apt  1.8.4

Versions of packages mini-buildd suggests:
pn  binfmt-support          <none>
pn  btrfs-progs             <none>
ii  debian-archive-keyring  2019.1
ii  haveged                 1.9.1-8
ii  lvm2                    2.03.02-3
pn  qemu-user-static        <none>
pn  ubuntu-keyring          <none>

-- Configuration Files:
/etc/default/mini-buildd changed:
MINI_BUILDD_OPTIONS='--verbose -W :::8066'

/etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: 
'/etc/sudoers.d/mini-buildd-sudoers'

-- debconf information:
  mini-buildd/purge_warning:
* mini-buildd/home: /var/lib/mini-buildd
* mini-buildd/options: --verbose --httpd-bind=:::8066
* mini-buildd/note:

Reply via email to