On Wed, 24 Feb 1999, Rainer Dorsch wrote: > Doing apt-get dist-upgrade: > [...] > Preparing to replace libdb2 2.3.16-7 (using libdb2_2.4.14-1.deb) ... > Unpacking replacement libdb2 ... > Preparing to replace libg++2.8 2.90.29-0.6 (using libg++2.8_2.90.29-2.deb) ... > Unpacking replacement libg++2.8 ... > Selecting previously deselected package libjpeg62. > E: Sub-process returned an error code > You can find a script log in > http://www.ra.informatik.uni-stuttgart.de/~rainer/Download/hamm2slink
I don't understand this, dpkg returned a failure code and yet it did not print any messagesm aside from this one which I belive to be not result in an error code. dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/man/man8/lilo.8.gz', which is also in package manpages I have seen this reported many times, and each time the reporter was unable to reproduce it. Actually if you examine the last output of dpkg it looks like this: Unpacking replacement libg++2.8 ... Selecting previously deselected package libjpeg62. E: Sub-process returned an error code Notice it how it says 'Selecting previouly dselected package' and then nothing more (it usually says unpacking)? It almost looks like it crashed right there! (Note: I do not explicy say if there has been a segfault in the child process with that APT version, CVS APT will print out a more usefull message) If dpkg is segfaulting on large upgrades we are in trouble - this is not an isolated case either, I have heard at least 3 other reports. Jason
