[meta-freescale] user layer problem with udev_173.bbappend

[Lewis, Nick]

I have to alter the protocol that git uses for the udev recipe. Rather than hacking at the udev_173.bbappend at the meta-fsl-arm layer, I have 'done the right thing' and added a priority 6 user layer and made the changes there. However it is not working as I expected. Could you please assist me?

The amendment is:
 $ cat ../sources/meta-nick/recipes-core/udev/udev_173.bbappend
 SRC_URI := "${@oe_filter_out('git://git.kernel.org/pub/scm/linux/hotplug/udev.git;protocol=git', '${SRC_URI}', d)}"
 SRC_URI_prepend = "git://git.kernel.org/pub/scm/linux/hotplug/udev.git;protocol=http "

And the result is:
 | DEBUG: Python function base_do_unpack finished
 | DEBUG: Python function do_unpack finished
 | ERROR: Function failed: Fetcher failure: Fetch command failed with exit code 128, output:
 | sh: 0: getcwd() failed: No such file or directory
 | fatal: Could not get current working directory: No such file or directory
 |
 ERROR: Task 0 (/data/yocto/rootfs_builder/sources/meta-openembedded/meta-oe/recipes-core/udev/udev_173.bb, do_unpack) failed with exit code '1'

Why would git not be able to getcwd in this case?
(I have other bbappend files in the user layer that seem to work ok but this is the only one that shares a corresponding bbappend file with the meta-fsl-arm layer)

Any clues would be gratefully received

The details of this company are as follows:
G4S Technology Limited, Registered Office: Challenge House, International Drive, Tewkesbury, Gloucestershire GL20 8UQ, Registered in England No. 2382338.

This communication may contain information which is confidential, personal and/or privileged.

It is for the exclusive use of the intended recipient(s).
If you are not the intended recipient(s), please note that any distribution, forwarding, copying or use of this communication or the information in it is strictly prohibited.

Any personal views expressed in this e-mail are those of the individual sender and the company does not endorse or accept responsibility for them.

Prior to taking any action based upon this e-mail message, you should seek appropriate confirmation of its authenticity.

This e-mail has been scanned for all viruses by MessageLabs.