On 2/27/06, Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote:
> I am getting the following errors and don't know how/what to check to
> learn which rpm they are in...
>
> ---> Package java-1.4.2-sun-devel.i586 0:1.4.2.10-1jpp set to be updated
> ---> Package java-1.4.2-sun.i586 0:1.4.2.10-1jpp set to be updated
> --> Running transaction check
> --> Processing Dependency: libjvm.so(SUNWprivate_1.1) for package:
> java-1.4.2-sun
> --> Processing Dependency: libnet.so(SUNWprivate_1.1) for package:
> java-1.4.2-sun
> --> Processing Dependency: libjava.so(SUNWprivate_1.1) for package:
> java-1.4.2-sun
> --> Processing Dependency: libverify.so(SUNWprivate_1.1) for package:
> java-1.4.2-sun
> --> Finished Dependency Resolution
> Error: Missing Dependency: libjvm.so(SUNWprivate_1.1) is needed by
> package java-1.4.2-sun
> Error: Missing Dependency: libnet.so(SUNWprivate_1.1) is needed by
> package java-1.4.2-sun
> Error: Missing Dependency: libjava.so(SUNWprivate_1.1) is needed by
> package java-1.4.2-sun
> Error: Missing Dependency: libverify.so(SUNWprivate_1.1) is needed by
> package java-1.4.2-sun
This is a jpackage issue, and is specific to their rpms. I assume you
rebuilt their nosrc rpm for sun java. If this is the case, it's a bug
with internal java dependency tracking. rpm -qpl the rebuilt rpms to
see that libjava.so, libnet.so etc are there. If they are, then you
can safely (THIS TIME ONLY) install with --nodeps. Since this is a
jpackage issue, you might want to ask them about it, as they may have
a more authoritative answer.
See https://www.zarb.org/pipermail/jpackage-discuss/2005-April/007836.html
for further info. (google should be your friend)
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety''
Benjamin Franklin 1775
