On Sun, Apr 12, 2009 at 17:50:48 -0500, M. Lewis wrote: > > Florian Kulzer wrote: >> On Sun, Apr 12, 2009 at 03:07:50 -0500, M. Lewis wrote: >>> I'm having an issue with Aptitude that I'm not sure how to correct. I >>> was having an issue with OpenOffice so I decided the easiest way to >>> resolve the problem might be to completely remove it, then re-install >>> it. That is when the problem began. Aptitude hung trying to remove >>> openoffice.org-writer2latex.
[...] >> It seems that the pre-removal script gets stuck while trying to >> determine the full name of the writer2latex extension. You can try this >> yourself: >> >> /usr/lib/openoffice/program/unopkg list --shared | grep latex >> >> If that command comes up empty or if it hangs then you might have to >> comment out every invocation of /usr/lib/openoffice/program/unopkg in >> /var/lib/dpkg/info/openoffice.org-writer2latex.prerm and run "aptitude >> install -f" to get the broken package off your system. >> > > Hey Florian. Unfortunately this did not work. The command unopkg did in > fact hang. OK, so at least we know for sure that we have to get rid of it in the script. > I did comment out all of the occurrences of unopkg in > /var/lib/dpkg/info/openoffice.org-writer2latex.prerm and ran 'aptitude > install -f' as you said. Here is the result: [...] > Removing openoffice.org-writer2latex ... > /var/lib/dpkg/info/openoffice.org-writer2latex.prerm: line 7: syntax > error near unexpected token `}' > dpkg: error processing openoffice.org-writer2latex (--remove): > subprocess pre-removal script returned error exit status 2 > Errors were encountered while processing: > openoffice.org-writer2latex > E: Sub-process /usr/bin/dpkg returned an error code (1) Now the problem is that the function flush_unopkg_cache is empty since its only instruction has been commented out and shells tend not to like that. I should have realized that my somewhat vague instructions could lead to this problem. Anyway, if unopkg does not work anymore for you then you might as well comment out the entire script from line 2 to the end and be done with it. (The only purpose of the pre-removal script seems to be ensuring that unopkg is invoked correctly, but that horse has left the barn already on your system.) -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
