On 4/24/05, Jeff Spaleta <jspaleta@xxxxxxxxx> wrote: > I can't get the uninstall of jre behavior to happen with an install of > java-1.4.2-gcj-compat via rpm or yum. And since i dont have a local > cache of an older versions of java-1.4.2-gcj-compat I can't test the > update scenario which was originally commented on. great... that was fun... i could not reproduce the behavior as seen by the original reporter even using yum update. Here's my setup: *Start with Sun's jre-1.5.0_02-fcs package installed *install the older java-1.4.2-gcj-compat-1.4.2.0-40jpp_16rh.i386.rpm using rpm -i or yum install, my jre package was not removed. Note you have to install the jessie package from development as well. *run yum update to update to java-1.4.2-gcj-compat-1.4.2.0-40jpp_18rh, my jre is not removed. *or rpm -U to java-1.4.2-gcj-compat-1.4.2.0-40jpp_18rh, my jre is not removed On my rawhide system I have tested rpm -i, yum install, rpm -U and yum update on java-1.4.2-gcj-compat packages. I even did rpm -U --oldpackage. Specically working with: java-1.4.2-gcj-compat-1.4.2.0-40jpp_16rh.i386.rpm java-1.4.2-gcj-compat-1.4.2.0-40jpp_18rh.i386.rpm and jessie-1.0.0-5.noarch.rpm when doing these operations. I can not reproduce the removal of Sun's latest rpm package jre-1.5.0_02-fcs on my x86 rawhide system in any scenario. Anyone who can reproduce this is going to have to provide some verbose output from rpm and yum. -jef
