Common problems

Last updated April 22, 2010. Created by Heine on April 24, 2006.
Edited by add1sun, ax. Log in to edit this page.

UNIX vs. Windows end-of-line encoding

Text files originating from UNIX systems use a single linefeed character (LF) to mark the end of a line, whereas Windows systems use a carriage return followed by a linefeed (CRLF).

The GnuWin32 patch program may crash on a patchfile with Unix end-of-line encoding throwing the error "Assertion failed: hunk, file [path]/patch.c, line 339".

Most patches downloaded from drupal.org are UNIX text files. When you use patch on Windows, you need to convert line-endings using a unix2dos utility or a decent text-editor.

One way to do this is to open the file with WORDPAD, choose "Save as" and select as type Text document.

Patch can't find the target file

This usually means that you are either executing patch in the wrong directory or that the patch was made relative to another directory. Open the patchfile and locate the lines describing the changed files to determine the path:

The above patch appears to be made relative to the drupal root directory so you can execute the following command from the Drupal root:

The number after -p determines the number of path elements that should be ignored. This is very useful when you need to apply a patch that was made against an old and new directory:

You can apply this patch from the Drupal root by stripping the first path element; 'olddir' / 'newdir':

patch unexpectedly ends in middle of line
Applying some patches generates the error:

This error seems to occur when the patch file ends on a line that includes nothing but whitespace characters. Patch files should always end with a Unix return character. If you encounter this error, check to see that the last line of your patch does not contain whitespace characters.

References: http://drupal.org/node/122734 and http://drupal.org/node/118660