Network Manager Patch

[Patton Echols]

On 03/23/2007 05:44 AM, Matthew Flaschen wrote:
> Patton Echols wrote:
>   
>> On 03/22/2007 08:58 PM, Matthew Flaschen wrote:
>>
>> Thank you Matthew for the instructions.  As I mentioned to Matthew off 
>> the list, it appears that there are two patches in the page I linked, I 
>> don't know if that's the trouble Matthew ran into.
>>     
>
> That was the original problem, but then I found the "correct" patch
> conflicted with one already provided in the sources.
>
>   
>>> Then, (starting in the NetworkManager directory)
>>>
>>> cd network-manager-*
>>> cp ../atheros.patch .
>>> patch -p0 < atheros.patch
>>>   
>>>       
>> I got to this point and received what I take to be an error.  Here is 
>> the out put of the command followed by the contents of the file listed 
>> in the output:
>>
>> patton at Mycroft:~/NetworkManager/network-manager-0.6.3$ patch -p0  < 
>> atheros.patch
>> patching file src/nm-device-802-11-wireless.c
>> Hunk #1 succeeded at 117 (offset -4 lines).
>> Hunk #2 succeeded at 1152 (offset 134 lines).
>> Hunk #3 succeeded at 1248 (offset 134 lines).
>> Hunk #4 FAILED at 1308.
>> Hunk #5 succeeded at 3309 with fuzz 1 (offset 114 lines).
>> 1 out of 5 hunks FAILED -- saving rejects to file 
>> src/nm-device-802-11-wireless.c.rej
>>
>> =======================
>>
>> And here is the contents of file src/nm-device-802-11-wireless.c.rej
>>
>> [snip]
>>
>> I stopped at this point.  I really don't want to render NM useless.  Any 
>> thoughts?
>>     
>
> Just generating the package won't change your NM install.  You would
> have to install it first.
>   

Right, but I thought I should not generate the package either to avoid 
messing it up.  I suppose that worst case I could scrap the directory 
and start over.

>   Matthew had suggested I'd find that the madwifi patch was
>   
>> already in place when I downloaded the source.  i didn't find it where 
>> it should have been.
>>     
>
> Did you find the debian/patches directory?
>
>   

Yes, here is the output of ls -al

patton at Mycroft:~/NetworkManager/network-manager-0.6.3/debian/patches$ ls -al
total 48
drwxr-xr-x 2 patton patton 4096 2007-03-23 04:31 .
drwxr-xr-x 3 patton patton 4096 2007-03-23 04:31 ..
-rw-r--r-- 1 patton patton  459 2007-03-23 04:31 01-supplicant_timeout.patch
-rw-r--r-- 1 patton patton  709 2007-03-23 04:31 
02-dbus_access_network_manager.patch
-rw-r--r-- 1 patton patton  676 2007-03-23 04:31 04-if_fix.patch
-rw-r--r-- 1 patton patton  299 2007-03-23 04:31 05-resolvconf.patch
-rw-r--r-- 1 patton patton 4675 2007-03-23 04:31 
06-dispatch_more_events.patch
-rw-r--r-- 1 patton patton 1334 2007-03-23 04:31 08-disabled_devices.patch
-rw-r--r-- 1 patton patton 3399 2007-03-23 04:31 
10-rml-wpa-workarounds.patch
-rw-r--r-- 1 patton patton  432 2007-03-23 04:31 
11-j-hostap-supplicant-driver.patch
-rw-r--r-- 1 patton patton  759 2007-03-23 04:31 12_dbus0.9.patch

No obvious madwifi patch.
>> Should I carry on with trying to build with the patch?
>>     
>
> Probably not.  I doubt it will work.  I should say that I'm on Dapper
> (well really gnewsense 1.1 but hopefully that doesn't matter).
>
> Matt Flaschen
>
>
>   
 
No, I suppose not.  any ideas about where I should go from here?

Thanks again for all your thoughts.

Patton