Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 394441 - dev-python/pyopencl-0.92 wrongly depends on >=dev-util/nvidia-cuda-toolkit-3.0
Summary: dev-python/pyopencl-0.92 wrongly depends on >=dev-util/nvidia-cuda-toolkit-3.0
Status: RESOLVED DUPLICATE of bug 320607
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-12 12:22 UTC by Pavel Potocek
Modified: 2011-12-12 12:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Potocek 2011-12-12 12:22:33 UTC
dev-python/pyopencl-0.92 should not automatically pull in CUDA dependency. >=dev-util/nvidia-cuda-toolkit-3.0 conflicts with dev-util/ati-stream-sdk-2.3-r1::c1pher , which is needed by users of AMD graphic cards. The latter package should also provide dependency. The same problem as on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/pyopencl/+bug/763457

Reproducible: Always

Steps to Reproduce:
1. layman -a c1pher
2. emerge -v ati-stream-sdk 
3. download necessary file from amd.com, as advised in emerge output
4. emerge ati-stream-sdk
5. emerge -v pyopencl
Actual Results:  
Emerge failed, package conflict:
dev-util/ati-stream-sdk-2.3-r1::c1pher
dev-util/nvidia-cuda-toolkit-4.0::gentoo
 pulled in by >=dev-util/nvidia-cuda-toolkit-3.0
 required by dev-python/pyopencl-0.92::gentoo

Expected Results:  
Emerge: success
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2011-12-12 12:37:32 UTC
Packages in the main tree should never depend on packages in overlays. You can fix the overlay by adding an alternative cat/pkg there that has the dependency on the other package in the overlay.

Or you can look at bug #320607 comment #7 for the current status of the bug you are re-reporting.

*** This bug has been marked as a duplicate of bug 320607 ***