Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 170838
Alias:
Product:
Component:
Status: RESOLVED
Resolution: DUPLICATE of bug 166328
Assigned To: Gentoo Linux bug wranglers <bug-wranglers@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Tobias Leupold <tobias.leupold@web.de>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 170838 depends on: Show dependency tree
Bug 170838 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2007-03-14 09:49 0000 
I use ~dev-python/pykde-3.16.0 and not kde-base/pykde, as I need KABC bindings
which are not provided by kde-base/pykde at this time. After the sync I just
did and a emerge -uavD world (and a emerge -uavD --tree world to see what's
going on ;-), I noticed that app-portage/kelogviewer wants to have
kde-base/pykde, which blocks dev-python/pykde.

As these two packages provide the same functionality (don't they?), I suppose
to fix the ebuild, so that the user can choose which one to install.

Anyway ... what's the necessity to have dev-python/pykde AND kde-base/pykde?
Esp. when the kde-base version is way older and doesn't provide the most recent
version?

Reproducible: Always

Steps to Reproduce:

------- Comment #1 From Jakub Moc (RETIRED) 2007-03-14 10:50:48 0000 ------- 
NOT portage...

------- Comment #2 From Jakub Moc (RETIRED) 2007-03-14 10:51:18 0000 ------- 

*** This bug has been marked as a duplicate of bug 166328 ***
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug