Bug 217058 - Cups needs libgpg-error but the RPM does not indicate this
Cups needs libgpg-error but the RPM does not indicate this
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-23 10:17 EST by david.hagood
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-23 11:57:03 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description david.hagood 2006-11-23 10:17:54 EST
Description of problem:
CUPS needs libgpg-error.so.0, but the RPM does not indicate this - so if you
don't have libgpg-error installed, cups will install, and die.


Version-Release number of selected component (if applicable):
cups-1.2.7-4.fc7
libgpg-error-1.4-2

How reproducible:
Every time



Steps to Reproduce:
1. insure libgpg-error-1.4-2 is not installed
2. install/upgrade to cups-1.2.7-4.fc7
3. restart cups
  
Actual results:
CUPS dies because it cannot find libgpg-error.so.o

Expected results:
RPM should detect that CUPS needs libgpg-error.so.o and refuse to install CUPS.
yum should detect the dependancy and install libgpg-error

Additional info:
Comment 1 Tim Waugh 2006-11-23 11:39:38 EST
$ rpm -q --requires cups | grep libgnutls
libgnutls.so.13()(64bit)  
libgnutls.so.13(GNUTLS_1_3)(64bit)  
$ rpm -q --whatprovides 'libgnutls.so.13(GNUTLS_1_3)(64bit)'
gnutls-1.4.1-2
$ rpm -q --requires gnutls | grep gpg
libgpg-error.so.0()(64bit)  
libgpg-error.so.0  

So cups requires gnutls which requires libgpg-error.  If you don't have it
installed, something has been installed without satisfying dependencies.

So what's the installation history of this machine?  Is it possible to narrow
down which tool (rpm, yum, anaconda etc) may have been responsible?
Comment 2 david.hagood 2006-11-23 11:55:57 EST
No, I cannot tell how this happened.

Note You need to log in before you can comment on or make changes to this bug.