For what it's worth, installation and removal scripts are stored in /var/lib/dpkg/info, are named after the package they belong to and have the following extensions: .preinst: pre installation. .postinst: post installation. .prerm: pre removal. .postrm: post removal. and the .list files in those directories list all the files on the system that belong to that page. removing a script that failed will cause dpkg to ignore it the next time you attempt the package operation that ran the script, but I'm not sure this is advisable if you plan to try compiling the package your trying to remove from source. Also, removing a package's entry from /var/lib/dpkg/status will render it invisible to apt/dpkg/most apt frontends, but again, not sure if advisable, and errors in the status file will make apt/dpkg refuse to do anything until its fixed. Messing with this stuff is quite hackerish, and even if it solves the immediate problem, there's no guarantee it won't cause bigger problems down the line. -- Sincerely, Jeffery Wright Bachelor of Computer Science President Emeritus, Nu Nu Chapter, Phi Theta Kappa. _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list