What does "Update file corrupted" mean? - maemo.org

vees | # 1 | 2007-10-25, 16:10 | Report

Hi,

This morning I ran the usual "check updates" tool. I downloaded the new package list, and then I upgraded FBReader with no problems. The second package to update was python2.5-runtime. It downloaded just fine, but then I got this message:

"Unable to update
Update file corrupted"

How do I fix this?

Thanks,

VS

rone | # 2 | 2007-10-25, 17:39 | Report

I am getting the same error.

My first guess is that the update file is bad. It did not appear to me as something I can fix on my end.

vees | # 3 | 2007-10-25, 17:59 | Report

but what is the "update file"?

is that the python2.5-runtime file or the APT database?

TA-t3 | # 4 | 2007-10-26, 09:46 | Report

From the message it's a bit difficult to tell if it's the apt database (if it is, how to fix it is described below) or the actual python download. Try to figure out by starting an xterm, then log in as root, and do

apt-get install python2.5-runtime -su

(the -s makes it do nothing, but it should tell you of any problems).
If it looks bad, try dpkg --purge python2.5-runtime

If you get any other kind of message (better post it here in case it isn't clear) then it could be the apt database:
Check /var/lib/dpkg/status
There is a /var/lib/dpkg/status-old as well. That's your backup. If you have becomeroot installed, or any other means of logging in as root, try the following:

cd /var/lib/dpkg
cp -p status status.bad
cp status-old status

then try refreshing your application list from the application manager. Oh, and do a 'df' first to check that your file system isn't full or nearly full (the filesystem you're looking for is the one which says just '/' in the rightmost column).

Last edited by TA-t3; 2007-10-26 at 09:52. Reason: Adding more

lardman | # 5 | 2007-10-26, 11:22 | Report

Out of interest are updates distributed as binary diffs?

Rocketman | # 6 | 2007-10-26, 12:09 | Report

I get the same error

vees | # 7 | 2007-10-27, 02:24 | Report

Originally Posted by TA-t3 View Post

Oh, and do a 'df' first to check that your file system isn't full or nearly full (the filesystem you're looking for is the one which says just '/' in the rightmost column).

Here is what I get when I do a df:

Code:

Filesystem                Size      Used Available Use% Mounted on
/dev/mtdblock4            2.0M      2.0M         0 100% /mnt/initfs
none                    512.0k     76.0k    436.0k  15% /mnt/initfs/tmp
/dev/mtdblock4          251.5M    212.3M     39.2M  84% /
none                    512.0k     76.0k    436.0k  15% /tmp
none                      1.0M     64.0k    960.0k   6% /dev
/dev/mmcblk1p1            1.9G    943.2M    970.9M  49% /media/mmc1
/dev/mmcblk0p1            1.9G      1.7G    139.6M  93% /media/mmc2

should I worry about the /mnt/initfs being full?

Originally Posted by TA-t3 View Post

Try to figure out by starting an xterm, then log in as root, and do apt-get install python2.5-runtime -su

I did that. Here is what I got:

Code:

Reading package lists...
Building dependency tree...
The following extra packages will be installed:
  python2.5 python2.5-dbus python2.5-gnome python2.5-gobject python2.5-gtk2
  python2.5-hildon python2.5-imaging python2.5-osso
The following packages will be REMOVED:
  zsh
The following packages will be upgraded:
  python2.5 python2.5-dbus python2.5-gnome python2.5-gobject python2.5-gtk2
  python2.5-hildon python2.5-imaging python2.5-osso python2.5-runtime
9 upgraded, 0 newly installed, 1 to remove and 64 not upgraded.
1 not fully installed or removed.
Remv zsh [4.3.2-13mh2]
Inst python2.5 [2.5.1-1osso3] (2.5.1-1osso4 bora:bora)
Inst python2.5-dbus [0.71-1osso5] (0.71-1osso6 bora:bora)
Inst python2.5-gnome [2.18.0-1osso1] (2.18.0-1osso2 bora:bora)
Inst python2.5-gobject [2.12.2-1osso3] (2.12.2-1osso4 bora:bora)
Inst python2.5-gtk2 [2.10.3-1osso6] (2.10.3-1osso8 bora:bora)
Inst python2.5-hildon [0.8.7-1osso4] (0.8.7-1osso5 bora:bora)
Inst python2.5-imaging [1.1.6-1osso1] (1.1.6-1osso2 bora:bora)
Inst python2.5-osso [0.2-1osso4] (0.2-1osso5 bora:bora)
Inst python2.5-runtime [0.4-12] (0.4-13 bora:bora)
Conf python2.5 (2.5.1-1osso4 bora:bora)
Conf python2.5-dbus (0.71-1osso6 bora:bora)
Conf python2.5-gnome (2.18.0-1osso2 bora:bora)
Conf python2.5-gobject (2.12.2-1osso4 bora:bora)
Conf python2.5-gtk2 (2.10.3-1osso8 bora:bora)
Conf python2.5-hildon (0.8.7-1osso5 bora:bora)
Conf python2.5-imaging (1.1.6-1osso2 bora:bora)
Conf python2.5-osso (0.2-1osso5 bora:bora)
Conf python2.5-runtime (0.4-13 bora:bora)

Notice that zsh needs to be removed?

Well, that bloody package is not removable (not does it work). I tried all sorts of things to remove it, but its just stuck there. Could it be that the zsh problem is now screwing up the python2.5-runtime update?

Do you know of a safe way for me to (finally) "shoot" zsh?

Many thanks,

VS

TA-t3 | # 8 | 2007-10-27, 14:11 | Report

A 100% full /mnt/initfs is as it should be, this is an initial system image (traditionally a ramdisk on desktops) which the N800 uses to boot itself up to full consciousness. It's not used after that.

The rest looks fine too.

Ok, so you're bitten by the zsh bug.. we've seen it before. Avoid it like the plague. It's not in any of the standard repos which I use, so I can't find it and check it out, but as far as I remember it has a broken post-removal script. You seem to have xterm installed and hopefully also becomeroot. First find the name of the removal scripts, it'll typically be 'zsh.postrm' and/or 'zsh.prerm'. Simply do 'ls -l /var/lib/dpkg/info/zsh*' (without the quotes) and check. Then do 'rm /var/lib/dpkg/info/zsh.postrm', or whatever the name is (it should be that, I believe).

After (hopefully) getting rid of the broken script, try with 'dpkg --purge zsh'. If it fails (as in post-inst error message), try removing any zsh.prerm as well. It may also fail with a message telling you do do apt-get install -f, that would probably be ok if so (do execute apt-get install -f I mean).

EDIT: I had a look at the desktop version of the zsh package. It's put together in a slightly strange way, the postrm script is used to remove parts of what's usually removed automatically as part of the de-installation.
So, after you've hopefully sucessfully removed zsh by the beforementioned procedure, run the following additional commands:

rm /bin/zsh
rm /bin/zsh4
rm /usr/bin/zsh

NBNB: I also fixed some typos I did in the instructions above, particularly where I had use 'postinst' where I meant 'prerm'. So, the scripts that we are talking about (one or both are broken) is zsh.prerm nd zsh.postrm. They both live in /var/lib/dpkg/info/ if it's just like the desktop version (I suspect that it is, and that's why it's broken: Not adjusted for the IT environment.)

Last edited by TA-t3; 2007-10-27 at 16:05.

vees | # 9 | 2007-10-28, 20:06 | Report

Hi TA-t3,

I did get rid (finally!!!) of the bloody zsh package thanks to your instructions. Guess what happens now? When I try to update python2.5-runtime I get a message 'unable to update. Update file corrupted'

What do I do know?! Is that python2.5-runtime which is corrupted now or is it the entire APT database?

Heeeeeeeeelp!

TA-t3 | # 10 | 2007-10-29, 09:50 | Report

Try the 'apt-get install python2.5-runtime -su' command again (the '-s' makes it a do-nothing command). Let's have a look at the messages.