Bug 112784 - kdegraphics depends on gphoto2
kdegraphics depends on gphoto2
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kdegraphics (Show other bugs)
1
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-12-31 15:22 EST by manuel wolfshant
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-23 13:30:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description manuel wolfshant 2003-12-31 15:22:47 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When installing FC1, I wanted to make sure that I will be able to take
snapshots of [parts of] my desktop. I am a long term ksnapshot user,
so I installed kdegraphics. I was quite surprised to find out that not
only gphoto2 was also installed, but when trying to remove it I get:
#rpm -e gphoto2
error: Failed dependencies:
        libgphoto2.so.2 is needed by (installed) kdegraphics-3.1.4-1
        libgphoto2_port.so.0 is needed by (installed) kdegraphics-3.1.4-1
 The good part is that ksnapshot works OK even after rpm -e --nodeps
gphoto2.


Version-Release number of selected component (if applicable):
kdegraphics-3.1.4-1

How reproducible:
Always

Steps to Reproduce:
1.rpm -e gphoto2
2.
3.
    

Actual Results:
  error: Failed dependencies:
        libgphoto2.so.2 is needed by (installed) kdegraphics-3.1.4-1
        libgphoto2_port.so.0 is needed by (installed) kdegraphics-3.1.4-1

Expected Results:  removal of package, without forcing me to use rpm
-e --nodeps

Additional info:
Comment 1 Ngo Than 2004-09-23 13:30:58 EDT
there are some plugins (kio_kamera), which are linked against gphoto2.
the dependencies are ok here.

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