Your message dated Sat, 28 Jan 2017 21:08:49 +0100 with message-id <[email protected]> and subject line Re: Bug#852814: Fails at 'policy-rc.d already exists' has caused the Debian Bug report #852814, regarding Poor error reporting on update 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.) -- 852814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852814 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: pbuilder Version: 0.228.3 Severity: normal Hi, updating a cowbuilder chroots fails like: # sudo cowbuilder --update --distribution wheezy --basepath /var/cache/pbuilder/base-wheezy.cow --configfile /home/agx/.pbuilderrc I: Copying COW directory I: forking: rm -rf /var/cache/pbuilder/tmpbuild/build/cow.13281 I: forking: cp -al /var/scratch/sdcard/pbuilder/base-wheezy.cow /var/cache/pbuilder/tmpbuild/build/cow.13281 I: removed stale ilistfile /var/cache/pbuilder/tmpbuild/build/cow.13281/.ilist I: Invoking pbuilder I: forking: pbuilder update --configfile /home/agx/.pbuilderrc --buildplace /var/cache/pbuilder/tmpbuild/build/cow.13281 --extrapackages ' eatmydata' --no-targz --internal-chrootexec 'chroot /var/cache/pbuilder/tmpbuild/build/cow.13281 cow-shell' W: /root/.pbuilderrc does not exist I: Running in no-targz mode I: Current time: Fri Jan 27 15:52:46 CET 2017 I: pbuilder-time-stamp: 1485528766 I: copying local configuration I: mounting /proc filesystem I: mounting /sys filesystem I: creating /{dev,run}/shm I: mounting /dev/pts filesystem I: Mounting /var/cache/pbuilder/ccache I: policy-rc.d already exists W: pbuilder update aborted, not cleaning # echo $? 139 It works when downgrading to 0.227. Let me know if I can provide any further input. Cheers, -- Gyido -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-rc8-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pbuilder depends on: ii debconf [debconf-2.0] 1.5.59 ii debootstrap 1.0.87 ii dpkg-dev 1.18.18 ii wget 1.18-4 Versions of packages pbuilder recommends: ii devscripts 2.17.0 ii eatmydata 105-5 ii fakeroot 1.21-3 ii iproute2 4.9.0-1 ii net-tools 1.60+git20161116.90da8a0-1 ii sudo 1.8.19-1 Versions of packages pbuilder suggests: ii cowdancer 0.83 pn gdebi-core <none> -- debconf information: pbuilder/nomirror: pbuilder/rewrite: false pbuilder/mirrorsite: http://ftp.de.debian.org/debian/
--- End Message ---
--- Begin Message ---On Sat, Jan 28, 2017 at 05:22:03PM +0100, Guido Günther wrote: > > There's --debug for pbuilder, which cowbuilder passes on. This will do a > > `set -x`. It will also keep your chroot build directory around rather than > > removing it on failure. To be precise, the chroot will be kept around only with `create` and `update`. It's not like chroots are kept for failed builds or so. > This can be closed then. Closing, thank you! -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
