Summary: | sys-kernel/linux-firmware collides with a bunch of different packages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Chí-Thanh Christopher Nguyễn <chithanh> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chithanh, denilsonsa, gregkh, kernel, marcus.disi, pacho, ulm |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Diego Elio Pettenò (RETIRED)
2009-06-16 13:19:21 UTC
Those other packages can go away. Feel free to propose an ebuild change to handle this automatically, otherwise, I don't know what to suggest. Adding blockers and mask for removal all the other packages? You know this is something that should have done from the start. Sorry, no, I didn't realize this was needed, I didn't know there were so many different packages out there to conflict with this one :) I'll start marking them off... A new package net-wireless/iwl1000-ucode has been added to the tree, which installs the colliding file iwlwifi-1000-3.ucode *** Bug 318827 has been marked as a duplicate of this bug. *** (In reply to comment #2) > Adding blockers and mask for removal all the other packages? You know this is > something that should have done from the start. Regarding licenses, this would be a bad idea. There are users who don't want to install a whole bunch of non-free firmware blobs, if they just need support for one specific device. sys-kernel/linux-firmware-20100930 collides with x11-drivers/radeon-ucode-20100408 to complete the list, collision-protect kicks in Since this bug was filed, several new firmware packages were added to the tree that collide with linux-firmware. If there are no objections, I am going to update the list of blockers with the collisions I can find. (In reply to comment #8) > Since this bug was filed, several new firmware packages were added to the tree > that collide with linux-firmware. If there are no objections, I am going to > update the list of blockers with the collisions I can find. As I talked with gregkh time ago, he expected someone else than he to do that and, then, would be nice if you could fix blockers yourself :) Thanks a lot It seems that most if not all colliding packages are listed in blockers now. |