Arch Linux

shark3189

Member

Registered: 2011-01-18

Posts: 4

Applying a patch

I'm having a problem setting my wireless card to monitor mode and apparently this is the solution. Unfortunately, I have no idea how to apply this patch or which files to patch. Could somebody please help me out? Thanks!

litemotiv

Forum Fellow

Registered: 2008-08-01

Posts: 5,026

Re: Applying a patch

I would suggest to start with the information that is available in the wiki: https://wiki.archlinux.org/index.php/Pa … ng_patches

---

ᶘ ᵒᴥᵒᶅ

metzengerstein

Member

Registered: 2010-06-04

Posts: 60

Re: Applying a patch

This is a kernel patch. You need the sources and compile it for yourself. If you think you are fit for this look here https://wiki.archlinux.org/index.php/Ke … rom_Source.
But when you don't know how to patch a file, then better wait for the next kernel release.

dexxra

Member

Registered: 2011-02-09

Posts: 1

Re: Applying a patch

SOLVED!

Speak of the devil! I was just about to make a thread on the same subject about a patch problem I have had for a few days now.

Ok, I have read the "Patching in ABS" wiki entry, but I am still having issues with patching a custom WINE build. At the moment I am unsure of whether it is an issue with the patch or if it is an issue with my PKGBUILD. Here is the output I get from makepkg:

can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -pur wine/dlls/user32/Makefile.in wine/dlls/user32/Makefile.in
|--- wine/dlls/user32/Makefile.in    2010-10-15 21:37:09.000000000 +0400
|+++ wine/dlls/user32/Makefile.in    2010-10-18 22:44:01.000000000 +0400
--------------------------

Instantly I'm thinking this is possibly a directory transversal issue. The way the PKGBUILD for wine works is it has a 64-bit and 32-bit install and creates them in seperate directories from the looks of things. I may be completely wrong, I am only a newb (Tread softly, please ). I have tried everything possible from copying the patch file to the source directory like the wiki mentions, copying the patch file to the actual package directory itself, and a few other iterations of changes that I can't seem to recall.

Here is the PKGBUILD and patch I am trying to use.
PKGBUILD: http://paste.pocoo.org/show/335187/
Patch: http://paste.pocoo.org/show/335188/

Yes, I realize it's using an older version of WINE. I was backtracking to see if it was just a possible issue with the patch or not. I am not extremely knowledgeable about patching (Or ABS for that matter yet!), but I am willing to learn.

EDIT: Oh also I could not figure out how to add the patch to the source array. Any help with this would be appreciated as it would probably solve the problem of having to copy the patch two times in the PKGBUILD.

EDIT2 (SOLVED): My problem was solved simply by adding the patch to sources (Figured out how to finally do that with the help of people in IRC and looking at Skype's PKGBUILD). I also removed the individual "cp ($patch)" lines and made an individual one underneath where PKBUILD renames the '$pkgbuild' directory. Also ran into to some compiling errors because I forgot to add a forward slash spacer in the configure portions of the install. Newb mistakes fixed thanks to some help, reading, and common sense (Doh, I lost mine in the /tmp/ folder apparently).

Last edited by dexxra (2011-02-09 20:17:36)