Hi,
Arjan Oosting wrote:
> I am using the madwifi drivers (from madwifi-source) and I guess the
change
> from madwifi to madwifi-ng headers is the cause of this failure
> * Update madwifi headers to madwifi-ng, rev1390.
As (joint) maintainer of madwifi in debian (and madwifi-ng *out* of
debian) and also an upstream developer/contributor to the madwifi
project, I cannot understand the decision to include headers from an
experimental and rapidly developed/changing module that is *not* in the
debian archive.
The existing madwifi packages are based on the currently most stable
madwifi code (branches/madwifi-old) and I and Michael Renzmann strongly
agree that it is the only version that should be used by the general
public (developers or curious customers can use it at own risk :-) ) at
this time. When madwifi-ng is tagged as being stable, we can upload it
to the debian archive and co-ordinate with you to include the current
madwifi headers at that time.
Can you please revert to using the madwifi headers provided by
madwifi-dev (= 0.svn20060207-1) ?
If you would like me to provide a dpatch for this, just ask.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
