Summary: | emerge madwifi-driver (-0.1_pre20050107) modules install problem | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick <jaano> |
Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | horton, solar, world.root |
Priority: | High | ||
Version: | 2004.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Patrick
2005-01-16 13:20:41 UTC
I also confirm this problem with the pre20050107 ebuild on vanilla sources 2.6.10. Adding solar and horton to CC: Same problem here. I suspect, that probably by mistake, the 0.1_pre20050106 (which worked fine, for me at least) has recently been keyworded "-*", instead of the 0.1_pre20050107 (which doesn't work). See, when we look at madwifi-tools, the version is still at 0.1_pre20050106 (and it's working fine). So, shouldn't the keywords of 0.1_pre20050106 and 0.1_pre20050107 be inverted, or am I wrong ? I can confirm Joel's idea: unmerged 20050107 # emerge -C net-wireless/madwifi-driver # echo =net-wireless/madwifi-driver-0.1pre20050106 >> /etc/portage/package.unmask # emerge =net-wireless/madwifi-driver-0.1pre20050106 # modprobe <all the modules> # /etc/init.d/net.ath0 start works great and let the fingers from emerge sync / emerge -u world because you can't: # echo =net-wireless/madwifi-driver-0.1pre20050107 >> /etc/portage/package.mask even if that would be pretty nice to avoid overwriting at next emerge -u world. but probably it's fixed till then greets patrick This should be fixed in the linux-mod.eclass. Please resync in a couple of hours and remerge. Reopen this bug if the problem still exists. |