On Fri, Jan 22, 1999 at 12:03:28PM -0700, Jason Gunthorpe wrote: > > > I have heard of this serveral times in different contexts, some claim only > a single file will not install, this guy says alot of them. Could someone > perhaps investigate? > > Thanks, > Jason > > ---------- Forwarded message ---------- > Date: Fri, 22 Jan 1999 18:46:33 +0000 > From: Stefan Baums <[EMAIL PROTECTED]> > To: [email protected] > Subject: dpkg broken? > Resent-Date: 22 Jan 1999 18:44:55 -0000 > Resent-From: [email protected] > Resent-cc: recipient list not shown: ; > > Hi all. > > OK, so yesterday, in the process of updating my system to the newest > slink, I broke dpkg. I cannot install packages anymore. The error > messages are as follows: > > Preparing to replace modconf 0.2.23 (using modconf_0.2.24.deb) ... > Unpacking replacement modconf ... > > gzip: stdout: Broken pipe > dpkg-deb: subprocess gzip -dc returned error exit status 1 > dpkg: error processing modconf_0.2.24.deb (--unpack): > subprocess dpkg-deb --fsys-tarfile returned error exit status 2 > Errors were encountered while processing: > cron_3.0pl1-50.deb > freetype2-dev_1.2-3.deb > freetype2_1.2-3.deb > kernel-doc-2.0.36_2.0.36-2.deb > libg++2.8.2_2.91.60-4.deb > modconf_0.2.24.deb > E: Sub-process returned an error code > Exit 100 > > Actually, the problem might be not dpkg as such: to remedy the situation, > I grabbed dpkg and gzip from stable and manually (ar -x ; tar xvzf ; cp -R) > installed them, but that has not changed the situation. Some other > package must have broken dpkg. > > Any ideas? > Stefan
What does he have in LC_* and LANG variables? dpkg & friends do all sort of strange things if one sets those to a non-english language. -- Enrique Zanardi [EMAIL PROTECTED]
