Hi! On Tue, 2016-05-17 at 13:04:04 +0200, Thorsten Glaser wrote: > unfortunately, the problem is reproducible:
That's always good! > -----cutting here may damage your screen surface----- > 100|root@ci-busyapps:~ # dpkg -i --force-all > /var/cache/apt/archives/texlive-latex-extra-doc_2016.20160512> > (Reading database ... 213695 files and directories currently installed.) > Preparing to unpack .../texlive-latex-extra-doc_2016.20160512-1_all.deb ... > Unpacking texlive-latex-extra-doc (2016.20160512-1) over (2016.20160512-1) ... > dpkg (subprocess): failed to chdir to '': No such file or directory > dpkg: warning: subprocess old post-removal script returned error exit status 2 > dpkg: trying script from the new package instead ... > dpkg (subprocess): failed to chdir to '': No such file or directory > dpkg: error processing archive > /var/cache/apt/archives/texlive-latex-extra-doc_2016.20160512-1_all.deb > (--install): > subprocess new post-removal script returned error exit status 2 > dpkg (subprocess): failed to chdir to '': No such file or directory > *** Error in `dpkg': munmap_chunk(): invalid pointer: 0x00005651c4573f9f *** > ======= Backtrace: ========= […] > Aborted > -----cutting here may damage your screen surface----- > > Anything I can do to help debugging, before I bring the system into > a saner state manually? This was reported on IRC some days ago with a proposed patch which I've got locally, pending next push. This was affecting cdebootstrap. The problem comes from using --force-all, which enables among others the new --force-chrootless, but that fails when not setting --instadir. Your immediate solution is to stop using --force-all, now and probably in general, as that is beyond dangerous, it enables alll force flags, including unsafe-io, all conffile ones for example, or any other future behavior changing option. I mentioned also on IRC it could be appropriate to change the character legend in --force-help for --force-all to one of [☢], [☠] or [☣]. :) Thanks, Guillem
