On Mon, 23 Dec 2013, Guillem Jover wrote: > The problem is that something messes with dpkg's standard output and > error, and it fails when doing the fflush() and ferror() check on it > in m_output() I think. But this seems to be coming from something > lower than dpkg or apt, perhaps a change in glibc or the kernel. As > I've tried with downgraded versions matching the ones in stable, and > it still fails. I've not tested further. > > The last thing reported from dpkg to apt through the status-fd channel > is: > > status: git : error : error writing to '<standard output>': No such file or > directory
This is not without reminding me of this years old bug on launchpad (with hundreds of duplicates) that we never clearly understood: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/545790 I don't know if they are related but if that's the case, then it's good to finally have a way to reproduce it more reliably. Cheers, -- Raphaël Hertzog ◈ Debian Developer Discover the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131223073257.gb9...@x230-buxy.home.ouaza.com
