On 6/7/2013 5:26 PM, Brian wrote: > On Fri 07 Jun 2013 at 16:30:34 -0500, Stan Hoeppner wrote: > > [Snip] > >> What's the best method for fixing this, getting dpkg running again, and >> removing lshw, given some of its file have been corrupted/lost? There >> wouldn't happen to be a single command to rebuild the dpkg subsystem >> would there? > > A missing available file can be rebuilt with > > apt-get/aptitude/dselect update > > Doing > > touch /var/lib/dpkg/available > > beforehand might not come amiss.
Tried this but it didn't rebuild the file. However, simply having the empty available file after touch prevents the aptitude errors when removing a package. Aptitude also auto-creates available-old, which is also empty of course. > There should also be a /var/lib/dpkg/available-old file which you could > consider copying. It apparently got whacked as well when the system locked up. I'm wondering if it will every get repopulated. I also wonder how necessary it is at this point. I can remove packages without the error now. But I haven't tried installing any. I'm guessing I'll have a problem when I do, given the name "available". -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b272a3.2000...@hardwarefreak.com
