[Fedora-ia64-list] Updating glibc

[Doug Chapman]

On Thu, 2009-03-19 at 17:13 +0100, Bettoni Fabio wrote:
> Hi,
> I've got the following
> 
> # yum update glibc

Why just update glibc?  Did you try just a normal "yum update" first?

> Loaded plugins: refresh-packagekit
> Setting up Update Process
> Resolving Dependencies
> --> Running transaction check
> --> Processing Dependency: glibc = 2.8.90-8 for package: glibc-headers
> --> Processing Dependency: glibc = 2.8.90-8 for package: glibc-common
> --> Processing Dependency: glibc = 2.8.90-8 for package: glibc-devel
> ---> Package glibc.ia64 0:2.9.90-8.1 set to be updated
> --> Running transaction check
> ---> Package glibc-common.ia64 0:2.9.90-8.1 set to be updated
> ---> Package glibc-headers.ia64 0:2.9.90-8.1 set to be updated
> ---> Package glibc-devel.ia64 0:2.9.90-8.1 set to be updated
> --> Finished Dependency Resolution
> 
> Dependencies Resolved
> 
> =============================================================================================
>  Package                 Arch           Version               Repository                Size
> =============================================================================================
> Updating:
>  glibc                   ia64           2.9.90-8.1            cowboy-updates           6.1 M
>  glibc-common            ia64           2.9.90-8.1            cowboy-updates            23 M
>  glibc-devel             ia64           2.9.90-8.1            cowboy-updates           996 k
>  glibc-headers           ia64           2.9.90-8.1            cowboy-updates           616 k
> 
> Transaction Summary
> =============================================================================================
> Install      0 Package(s)
> Update       4 Package(s)
> Remove       0 Package(s)
> 
> Total size: 30 M
> Is this ok [y/N]: y
> Downloading Packages:
> Running rpm_check_debug
> Running Transaction Test
> Finished Transaction Test
> Transaction Test Succeeded
> Running Transaction
>   Updating       : glibc                                                                 1/8
> Error unpacking rpm package glibc-2.9.90-8.1.ia64
> error: unpacking of archive failed on file /etc/ld.so.conf;49c26e4b: cpio: MD5 sum mismatch
>   Updating       : glibc-common                                                          2/8
> Error unpacking rpm package glibc-common-2.9.90-8.1.ia64
> error: unpacking of archive failed on file /etc/default/nss;49c26e4b: cpio: MD5 sum mismatch
>   Updating       : glibc-headers                                                         3/8
> Error unpacking rpm package glibc-headers-2.9.90-8.1.ia64
> error: unpacking of archive failed on file /usr/include/_G_config.h;49c26e4b: cpio: MD5 sum mismatch
>   Updating       : glibc-devel                                                           4/8
> Error unpacking rpm package glibc-devel-2.9.90-8.1.ia64
> error: unpacking of archive failed on file /usr/lib/Mcrt1.o;49c26e4b: cpio: MD5 sum mismatch
>   Cleanup        : glibc-headers                                                         5/8
>   Cleanup        : glibc-common                                                          6/8
>   Cleanup        : glibc                                                                 7/8

This is odd.  With the errors yum/rpm should have refused to do the
update and left the system in a usable state.

> 
> Updated:
>   glibc.ia64 0:2.9.90-8.1                      glibc-common.ia64 0:2.9.90-8.1
>   glibc-devel.ia64 0:2.9.90-8.1                glibc-headers.ia64 0:2.9.90-8.1
> 
> Complete!
> 
> 
> # rpm -q rpm
> -bash: /bin/rpm: /lib/ld-linux-ia64.so.2: bad ELF interpreter: No such file or directory
> # ls
> -bash: /bin/ls: /lib/ld-linux-ia64.so.2: bad ELF interpreter: No such file or directory
> 
> 
> System lost  and now ?
> 
> Fabio
> 

Did you start with the cowboyhat F10 release?  Or was this an updated F9
release.  It appears you had an older version of rpm (which doesn't
understand the MD5 sum).

What you will need to do to recover is to boot the CowboyHat F10 DVD
with "rescue" as a command line arg (however I don't think anybody has
tested that so it might not work).  then you will need to try to
re-install glibc.  You will need to use the --root option to rpm to
install into the directory where the install was mounted (I think rescue
mode mounts it under /sysimage iirc).

However, easiest solution likely would be to just do a fresh install.
Such is the danger when using experimental software.


- Doug