please report bugs to get them fixed instead of telling each and everybody (or documentating) how work around them (was: Re: EeePC - to Fedora or not?)

[Thorsten Leemhuis]

On 17.10.2008 16:35, Jim wrote:
> Thorsten Leemhuis wrote:
>> On 12.10.2008 21:26, Jim wrote:
>>> Beartooth wrote:
>>>> On Sun, 12 Oct 2008 14:24:03 +0100, Timothy Murphy wrote:
>>> [...]
>>> The madwifi  drivers at Livna does not work as they should for the 
>>> 2.6.26 kernels.
>> Did you (or somebody else) file a bug so this can be fixed? Then we 
>> can save a lot of users trouble, as they don't need to wander around 
>> on mailing lists and web forums asking question ;-)
> They did fix it, in FC10 with the 2.6.27 kernels only.

Afaics that doesn't answer the question.

The comment above says "The madwifi drivers at Livna does not work as 
they should for the 2.6.26 kernels" (from F9 I suppose). Well, they 
should just work; if not then it's a bug that should be fixed.

So if someone has more details what wrong *please* file a bug -- that 
way the package maintainer will get aware of the issue and then the 
problem hopefully can be fixed for all users out there that still use F9 
(reminder: F9 as of now is still the lastest stable release, hence most 
users likely use it and expect things to "just work").

Cu
knurd

P.S.: In case it's not obvious: I'm one (actually the only active one 
that has access to the signing keys) of the Livna contributors (and one 
of those that drives RPM Fusion forward). I often see critique about 
livna or "foo does not work in livna; here is a workaround" on this 
list. That of course is fine (this is a free world), but that doesn't 
fix the underlying problem. So if we want to make Fedora better then we 
need to get those problems fixed, to make things "just work" (the goal 
is to have each and every package to "just work" to avoid that users 
have to type magic commands or do modifications to the system). That 
only works if problems get reported to the package maintainer, as the 
package likely works just fine for him (maybe because he uses the 
package differently or on different hardware).