Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 405033 - nvidia-drivers and nvidia-settings collide on three files
Summary: nvidia-drivers and nvidia-settings collide on three files
Status: RESOLVED DUPLICATE of bug 404335
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-20 13:44 UTC by N. Andrew Walsh
Modified: 2012-02-20 14:29 UTC (History)
0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description N. Andrew Walsh 2012-02-20 13:44:25 UTC 
x11-drivers/nvidia-drivers-295.20-r1 provides
 *      /usr/bin/nvidia-settings
 *      /usr/share/man/man1/nvidia-settings.1.bz2
 *      /usr/share/pixmaps/nvidia-settings.png
 as does nvidia-settings-295.20, so emerge fails on collision check. If nvidia-settings is redundant, should it not be blocked? And if not, is there a way to get around this collision check?

Reproducible: Always

Steps to Reproduce:
1. emerge nvidia-drivers-295.20-r1
2. emerge nvidia-settings-295.20
3. emo tears
Actual Results:  
collision-check failure, feelings of inadequacy.

Expected Results:  
collision-check bypass, or blocked redundant package, and general satisfaction with one's life choices.
Comment 1 Nikolaos Chatzidakis 2012-02-20 14:01:56 UTC 
Had the same problem. I solved it by removing the three files that block the package, and emerge nvidia-drivers again. Worked for me in both my desktop and my laptop with ~amd64.
Comment 2 Remigius Wojdanowski 2012-02-20 14:09:52 UTC 
Additionally, x11-drivers/nvidia-drivers-295.20-r1 depends on media-video/nvidia-settings if the "gtk"-useflag is set, producing the reported file collisions.
Comment 3 Bernard Cafarelli gentoo-dev 2012-02-20 14:29:59 UTC 

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