On 2016-06-09 23:00, Ryan Kavanagh wrote: > piuparts -d unstable --single-changes-list --lvm-volume > /dev/wd/sid-chroot ../freetuxtv_0.6.8\~dfsg1-1_amd64.changes
I never used (nor tested) the -lvm* options ... > causes piuparts to enter an infinite loop and abort with: > > RuntimeError: maximum recursion depth exceeded > > This happens after a long string of errors like the following: > > dpkg: error processing archive > /var/cache/apt/archives/freetuxtv_0.6.6~dfsg1-1_amd64.deb (--unpack): > unable to sync file '/var/lib/dpkg/tmp.ci//md5sums': Input/output error > Processing triggers for libc-bin (2.22-11) ... > dpkg: unrecoverable fatal error, aborting: > unable to fsync updated status of 'libc-bin': Input/output error > E: Sub-process /usr/bin/dpkg returned an error code (2) > > 2m15.5s DEBUG: Starting command: ['umount', '/tmp/tmpm8VEae/dev/shm'] > 2m15.5s DUMP: > umount: /tmp/tmpm8VEae/dev/shm: mountpoint not found > 2m15.5s DEBUG: Command failed (status=32), but ignoring error: ['umount', > '/tmp/tmpm8VEae/dev/shm'] My gut feeling says that this is unrelated to piuparts and you have some problem with your disk or lvm or the chroot. piuparts just puts a lot of stress on these. Andreas
