It's not bad. Do `rpm --rebuilddb` and then install.
On Tuesday 06 February 2001 22:48, Ron Stodden wrote:
> Mandrake,
>
> A new glibc has recently appeared in the Mandrake-devel 'unsupported'
> directory.
>
> It is bad! Evidence:
>
> [root@small glibc]# rpm -Uvh glibc-2.1.3-18.4mdk.i586.rpm
> cannot read header at 0 for dependency check
> [root@small glibc]#
>
> This is after two downloads from the primary mirror in Oslo.
>
> Further important questions:
>
> 1. Why are additions to this 'unsupported' directory not notified to
> us in the Mandrake Change Log mailing list?
>
> 2. This glibc release consists of 3 RPMs:
>
> glibc-2.1.3-18.4mdk.i586.rpm
> glibc-profile-2.1.3-18.4mdk.i586.rpm
> glibc-devel-2.1.3-18.4mdk.i586.rpm
>
> Why were these not placed together under a new glibc subdirectory,
> following the good example set by Chris Molnar for kde2.1Beta2? If
> they were, all we would have to do is rpm -Uvh glibc* on that
> subdirectory.
>
> 3. This 'unsupported' directory contains duplicate xpp RPMs:
>
> xpp-1.0-3mdk.i586.rpm
> xpp-1.0-4mdk.i586.rpm
Duplicate? They're different versions. Sometimes people feel (right, wrong,
or indifferent) that one version is more stable, appropriate, whatever than
another.
> This is an absolute NO-NO!
>
> 4. Why are not all the CUPS RPMs collected together into a cups
> subdirectory so that we can simply do a cups upgrade from that
> subdirectory with rpm -Uvh *.rpm?
