can you please mark net-wireless/rt2500-1.10_beta3 stable, there havn't been any bug reports and it would be very good, because if it is stable then it can go on the livecd
*** Bug 126555 has been marked as a duplicate of this bug. ***
Stable on x86... Here's a quick blurb from IRC where we were discussing this. If someone has a problem with this line of reasoning, please contact me directly and we can work on a better solution for the future, but I don't think that our users should suffer simply because nobody from the x86 team owns the hardware to test this themselves. <wolf31o2-work> ok... here's my take on it... as I told genstef at FOSDEM <wolf31o2-work> there's no current stable version, which means it is *very* unlikely that it will break any stable systems... it's been in ~arch for quite some time now without complaint... since it is a kernel module, it interacts fine with lots of kernels... so I would say that as long as there is at least 1 user to test, which has been done, and the package doesn't break anything *else* instable, to go ahead and stabilize it <wolf31o2-work> like I said... that's my take... things still need the 30+ days in ~arch, but being a driver, it is very unlikely to take out anything else <wolf31o2-work> and it is better than the current situation of having no driver available for stable users <tsunam> wolf31o2-work: I've had a driver, take out the kernel ;) <wolf31o2-work> tsunam: yes, and it would probably happen within the first 30 days, too <tsunam> lol <wolf31o2-work> which is my point <wolf31o2-work> if it survived ~arch and all the various kernels that people use, then it should be pretty safe I've also added ppc and amd64 to the bug. I leave it up to them to decide if they like my reasoning or not and keyword for themselves.
I guess I shouldn't have added x86 to this bug.
can't do more than compiling it, but that works. amd64 is happy
(In reply to comment #4) > can't do more than compiling it, but that works. amd64 is happy +1, pcc stable.
