Bug#820699: possible upcoming incompatibility with schroot 1.7
On Sat, Sep 17, 2016 at 10:38:03AM +0200, Stephan Sürken wrote: > On Mo, 2016-04-11 at 15:54 +0200, Marc Haber wrote: > (...) > > So please be advised to check compatiblity with schroot 1.7. > > thx. I checked, and it's indeed not compatible ;). I hate it when my fears become true. > > It would also be a good idea to give a clear error message if sbuild > > does not find the spool directory mounted in the chroot. I have found > > this to be an extremely common error which is a hell to debug. > > Different issue, however: Is there an easy way to detect that specific > error (or does this need monkey-parsing the build log)? Better error messages are probably a wishlist item for sbuild. Unfortunately, this is too far in the past so that I still remember details. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany| lose things."Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
Bug#820699: possible upcoming incompatibility with schroot 1.7
Hi Marc, On Mo, 2016-04-11 at 15:54 +0200, Marc Haber wrote: (...) > So please be advised to check compatiblity with schroot 1.7. thx. I checked, and it's indeed not compatible ;). However, I will not try to fix this right now, rather avoid it for the moment: control: Dep: Avoid schroot >= 1.7 for now (atm, we are not compatible with schroot 1.7). 1.7 is a development release. We rather postbone trying to be compatible until 1.8 is released (or it hits unstable). In the meantime, avoid people accidentially updating to it. > It would also be a good idea to give a clear error message if sbuild > does not find the spool directory mounted in the chroot. I have found > this to be an extremely common error which is a hell to debug. Different issue, however: Is there an easy way to detect that specific error (or does this need monkey-parsing the build log)? Thx, S
Bug#820699: possible upcoming incompatibility with schroot 1.7
Package: mini-buildd Version: 1.0.11 Severity: minor Hi, this is just a heads-up warning that mini-buildd might be incompatible with schroot 1.7 which is currently in experimental. I had one builder (on armhf, if that's of any importantce) inadvertently updated to schroot 1.7, and my builds spontaneously started to fail with "apt_sources.list not found". This was caused by /var/lib/mini-buildd not bind-mounted into the schroot. So please be advised to check compatiblity with schroot 1.7. It would also be a good idea to give a clear error message if sbuild does not find the spool directory mounted in the chroot. I have found this to be an extremely common error which is a hell to debug. Greetings Marc -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-zgsrv20080 (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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.114 ii debconf [debconf-2.0] 1.5.59 ii debootstrap 1.0.80 ii devscripts 2.16.2 ii dpkg-dev1.18.4 ii gnupg 1.4.20-5 ii libjs-jquery1.12.3-1 ii libjs-sphinxdoc 1.3.6-2 ii lintian 2.5.43 pn mini-buildd-common ii python-cherrypy33.5.0-2 ii python-daemon 2.0.5-1 ii python-django 1.9.5-1 ii python-django-registration 2.0.4-1 ii python-mini-buildd 1.0.11 ii python-pyftpdlib1.4.0-1 pn python:any ii reprepro4.17.0-1 ii sbuild 0.68.0-1 ii schroot 1.6.10-2 ii sudo1.8.15-1.1 Versions of packages mini-buildd recommends: ii python-apt 1.1.0~beta2 Versions of packages mini-buildd suggests: pn binfmt-support ii haveged 1.9.1-3 ii lvm2 2.02.146-1 pn qemu-user-static -- Configuration Files: /etc/default/mini-buildd changed [not included] /etc/sudoers.d/mini-buildd-sudoers [Errno 13] Permission denied: u'/etc/sudoers.d/mini-buildd-sudoers' -- debconf information excluded
