On Thu, 8 Mar 2007, Troy Dawson wrote:

> Testing results thus far:
>
> If you currently have installed
> j2sdk < 1.4.2-13 *only*
> no problems, it updates fine
>
> If you currently have installed
> j2sdk < 1.4.2-13 *and* jdk < 1.5.0-11
> no problems, it updates both the j2sdk and jdk fine
>
> If you currently have installed
> j2sdk < 1.4.2-13 *and* jdk = 1.5.0-11
> Problem:  It updates j2sdk and deletes jdk.
> Why?  I don't know.  It has nothing to do with yum or apt, because it does it 
> even if you do this by hand.

The answer is probably buried somewhere in the output when you do:
   rpm -vv -F j2sdk-1.4.2_13-fcs.i586.rpm

I see clearly that rpm does erase jdk:
  ...
  D: removing 1756 entries from Filemd5s index.
  D: ========== --- jdk-1.5.0_11-fcs i586-linux 0x0
  D:     erase: jdk-1.5.0_11-fcs has 2685 files, test = 0
  ...

I would guess that the epoch number is the problem when comparing
'provides' from j2sdk and from jdk; the j2sdk one wins big time:

$ rpm -qp j2sdk-1.4.2_13-fcs.i586.rpm --provides
j2sdk = 2000:1.4.2_13-fcs

$ rpm -qp jdk-1.5.0_11-fcs.i586.rpm --provides
jre = 1.5.0_11
j2sdk = 1.5.0_11
j2re = 1.5.0_11
jaxp_parser_impl 
xml-commons-apis 
jdk = 2000:1.5.0_11-fcs

$ rpm -qp j2sdk-1.4.2_13-fcs.i586.rpm --qf='%{EPOCH}\n'
2000

If jdk 'provided':        j2sdk = 2000:1.5.0_11
then I would guess that there wouldn't be a problem.

While on the subject of bad RPMs :-) I have tested that
one can sign these v3 RPMs provided that one uses an old rpm binary.
If you have an old version of the rpm 3 binary kicking around,
circa RH 6.x (they were always statically build until RH 9 I believe),
then it can be used to sign these old v3 RPMs.  It worked for me in a
quick test where I signed the RPM with a RH 6.0 rpm binary, set
gpgcheck=1 in the yum configuration and was able to yum-install the signed
package.

$ rpm -qpi j2sdk-1.4.2_13-fcs.i586.rpm |grep Sig
Signature   : DSA/SHA1, Thu 08 Mar 2007 02:24:31 PM PST, Key ID ab4b50e5c880dc45


cheers,
  denice
-- 
deatrich @ triumf.ca, Science/Atlas         PH: +1 604-222-7665
<*> This moment's fortune cookie:
New crypt.  See /usr/news/crypt.