Mandriva Expert
The place where your Mandriva Linux system finds support

RPM Requires Incorrectly Recognized

+/- details
User bownetworks
Incident Number 95340
Date 2006/02/03 21:28
Status Incident closed
Paid No

Product Corporate Desktop 3.0
Architecture x86_32
Scope Installation

Products owned
Community Support question - to convert into a paid question, click here

Lines in bold below have not yet been seen by the customer - those in blue are from the customer

Username : Date : Action : Comments [ close all ]    
 
bownetworks : 03/02/06 09:28 PM : Incident created
-   When building an RPM, I setup a number of requires, it builds fine, but when I try to install the RPM, it complains about a number of the requires which are installed at the correct versions.

Spec File:

Requires: ldconfig == 2.3.3

Error when installing the RPM:

error: Failed dependencies:

ldconfig = 2.3.3 is needed by package-1.00.00-1.C30mdk

When I do an RPM check, I get the following:

#rpm -qa | grep ldconfig

ldconfig-2.3.3-12.8.100mdk

#rpm -q ldconfig-2.3.3-12.8.100mdk --queryformat '%{NAME}tt%{VERSION}n'

ldconfig 2.3.3

I am using the following RPM packages:

rpm-4.2.2-7mdk

rpm-build-4.2.2-7mdk

rpmdrake-2.1.3-3.1.C30mdk

rpmtools-4.5-19.1.100mdk

rpm-helper-0.9.1-1mdk

rpm-devel-4.2.2-7mdk

 
Linegod_7611 : 04/02/06 02:04 PM : Reply received
-   Did you try 'Requires: ldconfig >= 2.3.3', as it may be picking it up as
'%{version}-%{release}'

----------
Note: If this answer resolves your problem, please remember to close this
incident.

 
Linegod_7611 : 04/02/06 02:04 PM : Reply received
-   Dupe. Please close.

 
bownetworks : 07/02/06 03:37 PM : More info provided
-   Appreciated. Will investigate possible version-release combo that may apply.
HOWEVER your suggestion response has different symantics - we require exact match for our purposes. Does your comment still apply for '==' too?

 
bownetworks : 07/02/06 03:39 PM : More info provided
-   Appreciated. Will investigate possible version-release combo that may apply.
HOWEVER your suggestion response has different symantics - we require exact match for our purposes. Does your comment still apply for '==' too?

 
bownetworks : 07/02/06 03:53 PM : More info provided
-   Performed a query on the package with the following command:
rpm -q ldconfig-2.3.3-12.8.100mdk --queryformat '%{NAME} %{VERSION} %{RELEASE}n'
ldconfig 2.3.3 12.8.100mdk

Changed the requires in the rpm to include the release information, and it still fails.

 
Linegod_7611 : 10/02/06 03:48 AM : Reply received
-   Did you try '>' or '>='?

What is the output of:

# rpm -qp --requires {your_rpm}

----------
Note: If this answer resolves your problem, please remember to close this
incident.

 
bownetworks : 14/02/06 09:06 PM : More info provided
-   I tried >=, and it builds the rpm, and the requires doesn't complain when it is installed, but it isn't what I want/need. I need the requires to be absolute, otherwise, I can't guarantee that it will build or act the same.
I need the ability to perform an == on the requires.
Please advise.

 
bownetworks : 21/02/06 10:19 PM : More info provided
-   Here's a snippet from the rpm requires query:
#rpm -qp package-1.00.00-1.C30mdk.i586.rpm --requires
ctags = 5.5.2
xemacs = 21.4.15
tcp_wrappers-devel = 7.6
bash = 2.05b
grep = 2.5.1
ldconfig = 2.3.3
...

 
Linegod_7611 : 05/03/06 01:14 PM : Reply received
-   '=' should give you what you need, since everything after that is simply the distro
vendors release version. There would be no changes to the functioning of
ldconfig. By using '==' you would have to bind it to vendor-release.

---------
Note: If this answer resolves your problem, please remember to close this
incident.

 
bownetworks : 08/03/06 05:01 PM : More info provided
-   Changed the spec from from == to = and it doesn't act any differently.
It still complains that the required RPM isn't installed.
Please advise.

 
Linegod_7611 : 11/03/06 01:30 PM : Reply received
-   So did you try it with the release appended?

Requires: ldconfig = 2.3.3-12.8.100mdk

---------
Note: If this answer resolves your problem, please remember to close this
incident.

 
bownetworks : 15/03/06 04:25 PM : More info provided
-   Yes, we tried adding the VERSION and RELEASE combinations for '=' with no change in results. You seem to be having difficulty with this RPM question - are there other experts available that might know what is going wrong?

 
bownetworks : 15/03/06 04:26 PM : More info provided
-   Yes, we tried adding the VERSION and RELEASE combinations for '=' with no change in results. You seem to be having difficulty with this RPM question - are there other experts available that might know what is going wrong?

 
Linegod_7611 : 18/03/06 10:39 AM : Reply received
-   There is no method for me to turn this over to someone else, or escalate it (I
really wish there was).

I believe your only option is to close it out, and repost it.

 
bownetworks : 21/03/06 12:53 PM : More info provided
-   Thank you Linegod.

I noticed something else about the new RPM lately that might be a clue. The example is from mozilla-firefox (rpm -qp /mnt/guinness/Mandrake/cdrom102/media/main/mozilla-firefox-1.0.2-3mdk.i586.rpm --requires) which lists the following (among others).
gtk 2 >= 0:2.2.0
I wonder what the "0:" prefix means; I have not found it documented anywhere yet. Do you think that this might be related?

 
bownetworks : 21/03/06 12:53 PM : More info provided
-   Thank you Linegod.

I noticed something else about the new RPM lately that might be a clue. The example is from mozilla-firefox (rpm -qp /mnt/guinness/Mandrake/cdrom102/media/main/mozilla-firefox-1.0.2-3mdk.i586.rpm --requires) which lists the following (among others).
gtk 2 >= 0:2.2.0
I wonder what the "0:" prefix means; I have not found it documented anywhere yet. Do you think that this might be related?

 
 
bownetworks : 06/10/06 06:18 PM : Incident closed
-   The issue was due to customer not using EPOCH specification in Requirement as follows.

Requires: my_package = 2:2.02



This Incident is closed. It can not be edited anymore. You can create a new one by signing up/logging in your Mandriva Expert account.

  Mandriva  |  Contact  |  Legal  |  Privacy  |  Careers