To install Ladybird on Caldera Linux, we have to use the following command:

rpm -iv --nodeps --force <filename>.rpm

where <filename>.rpm is the name of the Ladybird Linux build being installed.

The right command for installing rpm file should be

rpm -iv filename.rpm

The following information came from Alexei Semyonov:

But, there are several buts for Caldera linux

1. Caldera linux is shipped with its own JDK1.2.2 package

2. Sun's JDK rpm is not 100% correct, it does not contain proper version
   number. So rpm can not compare versions (even Sun's jdk1.2.2 and jdk1.3)
   and believes that caldera's package (with proper version number) is newer
   than Sun's jdk1.3.1

To override this you have to use option --force
But this way is not recommended and rpm package should be fixed in the
future.

3. I guess ladybird jdk was built on redhat 6.2 linux, which contains
newer version of glibc, than caldera. So when package was created
the requirement of redhat's glibc version was written into the package.
The rpm checks all required packages for the ladybird package and
finds that caldera's glibc is older then necessary and reports error.

To override this you have to use --nodeps option.
But again it is highly not recommended, because you can miss real
necessary check. Caldera's glibc and redhat's are not 100% compatible.


So, I would recommend to fix rpm package instead of using several
workarounds (which might not work next time).


pratul.wadher@Eng 2001-03-16

I verified the bug with Ladybird build 19. The package is installed once you update Caldera linux OS with a newer version of glibrc. My suggestion is that the update document be corrected as I had to force the installation o fthe newer glibrc as it has dependencies too.