On Tue, Oct 28, 2003 at 09:14:52PM -0300, Cristian Gutierrez said > I even tried downloading 1.10.18 (.17 was on my system, an unstable one, > BTW), unpacking it and installing it "by hand", but the result was the > same. Yeah, nasty thing to do.. but I'm freaking out, you know? ;-)
Does a previous version work? I'm using 1.10.15 with no problems at all. > Is anybody else going through this? I didn't find any bugreports nor > related messages in debian-dpkg, and I'm starting to guess there could > be something b0rked on my disk after today's local power outage... :-( Check the package for corrupt files, maybe? I'd suggest using "debsums", but the dpkg package doesn't include md5sums. I can give you this, however: 6fa24e23b306cc11fc399f7fa467c0d0 /usr/bin/dpkg That's 1.10.15 on i386. I do have prelink installed, bug I reinstalled the .deb from /var/cache/apt/archives/ just before checksumming and it was identical. That said, if you reinstalled dpkg and it's still messed up, it's unlikely to be a problem with dpkg itself. If you can get debsums installed, maybe do a check of all the packages on your system? If libc6 or such gets broken, you'll get lots of weird problems. -- Rob Weir <[EMAIL PROTECTED]> | [EMAIL PROTECTED] | Do I look like I want a CC? Words of the day: Peking e-bomb defense information warfare Adriatic Soviet
signature.asc
Description: Digital signature
