[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: Installed version of java should but does not match required version
- From: John Rouillard <rouilj-rpm renesys com>
- To: RPM Package Manager <rpm-list redhat com>
- Subject: Re: Installed version of java should but does not match required version
- Date: Tue, 15 Aug 2006 12:27:33 -0400
On Tue, Aug 15, 2006 at 09:08:59AM -0700, Frank Cusack wrote:
> On August 15, 2006 10:15:11 AM -0400 John Rouillard
> <rouilj-rpm renesys com> wrote:
> > sudo rpm -U pipe-0.2.1-2.i386.rpm
> > error: Failed dependencies:
> > j2sdk = 1.4.2_05 is needed by pipe-0.2.1-2.i386
> >
> >However rpm -q --qf '%{VERSION}\n' j2sdk reports:
> >
> > 1.4.2_05
>
> There might be an epoch. rpm -q --qf '%{EPOCH}:%{VERSION}\n' j2sdk
That returns: 2000:1.4.2_05
So yup. good call. Also the serial number of the package (rpm -q --qf
'%{SERIAL}\n' is 2000. So I could replace the original dependency line
of "j2sdk = 1.4.2_05" with "j2sdk =S 2000" but would that work with
yum?
If I want to go the epoch route how do I deal with this in the
dependency spec? The Max-RPM book (in pdf) format doesn't really
discuss epoch (at least a search for "epoch" turns up no hits, which
is wierd because I know the concept and I am sure I got it from one of
my 2 reads through the book).
A newer snapshot of the book I found at rpm.org has the section on
manual dependencies/serial numbers replaced by "Epoch numbers". So
does that mean that the serial number handling is really the epoch
handling?
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-643-9300 x 111
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]