Adam Conrad wrote: > Geoff Crompton wrote: > >>ii apache 1.3.33-6sarge1 versatile, high-performance HTTP server >>pc apache-perl 1.3.9-13.1-1.2 Versatile, high-performance HTTP > > > There's nothing I can do to fix the potato (!) version of apache-perl at > this point. > > ... Adam
Thats an excellent point, one which occured to me after I sent my bug report through. Do you have any recommendations on how to safely purge apache-perl? I thought it'd be good to have it documented in this bug report, for future people that might stumble across this. Strategies that I thought might work (but don't want to test on the clients system) were: * install newest version of apache-perl, then purge it (don't know if that will trigger the old apache-perl postrm * manually edit files in /var/lib/dpkg/info to remove references to things belonging to apache, then purge * manually purge it by removing files in /var/lib/dpkg/info However in each of these cases, I'm not sure of the specifics. Ie, what would need to be removed for the third option, or what changes will make purging safe in the second option. -- Geoff Crompton Debian System Administrator Strategic Data +61 3 9340 9000 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
