On Tue, Jul 17, 2007 at 11:17:21AM -0400, Zac Elston wrote: > so I have some inhouse packages that require a specific java...no > problem, we download the jdk rpm from SUN and add a Requires: jdk >= > 1.5.0_12 line to my inhouse rpm...and... > > Unresolvable chain of dependencies: > newstuff requires jdk >= 1.5.0_12 > > checking the jdk rpm, it's there and ready to go..I can install it > manually and the inhouse packages sees it as installed and completes, > but it (the jdk rpm) refuses to be seen during up2date runs. > [...] > arg...ok. how do I determine what the package wants to be > referenced as or is there some reason I'm not aware of why this won't > work? like sun jdk rpms are broken and I have to roll my own.... Check to see if it has an epoch number, If it exists the version info is ignored. See the thread from: http://www.redhat.com/archives/rpm-list/2006-August/msg00071.html -- -- rouilj John Rouillard System Administrator Renesys Corporation 603-643-9300 x 111 _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
