On Thu, May 09, 2002 at 07:42:07AM +0200, Jan Svarc wrote: > > [EMAIL PROTECTED] ~ > $ dpkg -i dpkg_1.9.18_w32.deb > Selecting previously deselected package dpkg. > (Reading database ... 0 files and directories currently installed.) > Unpacking dpkg (from dpkg_1.9.18_w32.deb) ... > dpkg: error processing dpkg_1.9.18_w32.deb (--install): > corrupted filesystem tarfile - corrupted package archive: error 0 > dpkg-deb: subprocess paste killed by signal (Broken pipe) > Errors were encountered while processing: > dpkg_1.9.18_w32.deb >
dpkg-deb --fsys-tarfile dpkg_1.9.18_w32.deb| tar t doesn't give any error messages on my copy of the file. I haven't tried installing it, because I'm on a Linux system. However, your dpkg is saying that the fsys tarfile is bad, but it isn't according to i386/Linux dpkg tools (which are very likely to be reliable :). BTW, what does error 0 mean? Is that the exit status from something? Why is 0 an error? Does anybody know? -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BCE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
