Apt-Get Upgrade Issues... (resolved)

[Stephen]

ARGGGGGGGGGGHHHHHHHHHH,

How do I just blow JOE out of the water?????? dpkg isnt doing anything but crashing, remove just crashes, apt-get just crashes - how the heck can I just get through this JOE problem and get on with my UPGRADE ????? My menus aren't getting any better with all of this, I am even getting GNOME errors during booting now... This JOE needs to blow, period.

Cuddles

Edit the file /var/lib/dpkg/info/joe.postrm and the line 3 that it is failing on insert the # (comment character) at the start of the line. Then apt-get install --reinstall joe to have it hopefully install properly if succesful then remove the damn thing if not then put exit 0 as the second line in the file this will cause the script file to exit immediatley with a succees (no error) code. Before you try to update any more packages you should run the update-menus as root to hopefully fix your menus and start removing all the excess programs that are in your install to save yourself the time and effort you are going through for programs that you will never use. Once you get joe removed you should use dselect update to get both the apt and dselect databases back in sync. The first thing you should do however is install 1 package apt-get install localepurge to get rid of all the locales that are on the system and one of them is going to cause the same error you are getting with joe they have just not been regenerated yet. When you install the localepurge you will get a screen asking for the locales you want to remain on the system unless you want others besides the US ones you should keep only the en, en_US ISO-8859-1,en_US.ISO-8859-15 and en_US.UTF-8 UTF-8 then edit the file /etc/locale.gen and make sure it looks like this:

# This file lists locales that you wish to have built. You can find a list
# of valid supported locales at /usr/share/i18n/SUPPORTED. Other
# combinations are possible, but may not be well tested. If you change
# this file, you need to rerun locale-gen.
#
# XXX GENERATED XXX
#
# NOTE!!! If you change this file by hand, and want to continue
# maintaining manually, remove the above line. Otherwise, use the command
# "dpkg-reconfigure locales" to manipulate this file. You can manually
# change this file without affecting the use of debconf, however, since it
# does read in your changes.

en_US ISO-8859-1
en_US.ISO-8859-15 ISO-8859-15
en_US.UTF-8 UTF-8

### BEGIN DEBCONF SECTION FOR localeconf
# Do not edit within this region if you want your changes to be preserved
# by debconf.  Instead, make changes before the "### BEGIN DEBCONF SECTION
# FOR localeconf" line, and/or after the "### END DEBCONF SECTION FOR
# localeconf" line.
### END DEBCONF SECTION FOR localeconf

These will be the locales that will be regenerated when the locale package is upgraded and unless you edit out the knoppix extras in there they will be regenerated along with taking a long to to do this there are ususally at least a couple of locales with error that will stop apt in its tracks with errors. The program will also ask you if you want to remove the man pages in the other languages that you do not want on the system as well you should say yes here and say no to the verbose output of what it is doing and as to whether you want an accurate or guesstimate count of what was removed that is up to you choose whichever you want.

Suggested removals:

apt-get -s remove --purge kde-i18n-cs kde-i18n-da kde-i18n-de kde-i18n-es kde-i18n-fr kde-i18n-it
kde-i18n-ja kde-i18n-nl kde-i18n-pl kde-i18n-ru kde-i18n-tr

To get rid of the localizations for KDE that you will most likely never use, remove the -s to for the simulation of the command if the output looks good to do the removal and purge of the configuration files.

If you need anymore suggestion of the packages to remove I can see all kinds of them in your output above so ask if you do. And before you start installing anything you should go to this page and get the libsensors-1debian1 and save it somewhere where you can acces it before you run into that bug it will happen with the ksysguardd package and the suggestion for the libxcursor-dev above will be needed if you run into that bug as well.