<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 1, 2013 at 1:16 PM, McClintock Matthew-B29882 <span dir="ltr"><<a href="mailto:B29882@freescale.com" target="_blank">B29882@freescale.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Feb 1, 2013 at 4:12 AM, <<a href="mailto:b28495@freescale.com">b28495@freescale.com</a>> wrote:<br>
> From: Ting Liu <<a href="mailto:b28495@freescale.com">b28495@freescale.com</a>><br>
><br>
> Fix the below issue:<br>
> | DEBUG: Executing shell function do_configure<br>
> | sed: can't read ./.pc/opstart.patch/doc/<a href="http://opstop.1.in" target="_blank">opstop.1.in</a>: Permission denied<br>
> | sed: can't read ./.pc/opstart.patch/doc/<a href="http://opstart.1.in" target="_blank">opstart.1.in</a>: Permission<br>
> denied<br>
> | sed: can't read ./.pc/opstart.patch/utils/opstart.c: Permission denied<br>
> | ERROR: Function failed: do_configure<br>
<br>
</div>Permissions are messed up on these files, obviously:<br>
<br>
$ ls -alh .pc/opstart.patch/doc/<br>
total 12K<br>
drwxr-sr-x 2 jenkins jenkins 4.0K Jan 31 20:49 .<br>
drwxr-sr-x 4 jenkins jenkins 4.0K Jan 31 20:49 ..<br>
-rw-r--r-- 1 jenkins jenkins 2.5K Jan 31 20:49 Makefile.am<br>
---------- 1 jenkins jenkins 0 Jan 31 20:49 <a href="http://opstart.1.in" target="_blank">opstart.1.in</a><br>
---------- 1 jenkins jenkins 0 Jan 31 20:49 <a href="http://opstop.1.in" target="_blank">opstop.1.in</a><br>
<br>
But this was only occurring on one machine (our CentOS box). So, I've<br>
actually isolated this down to the version of patch we were using<br>
which is creating these new files with odd permissions.<br>
<br>
So, I'm not sure how to handle this - do we actually require a newer<br>
version of patch? patch-native is assume provided and we can't just<br>
remove that since we will get circular deps.<br>
<br>
Should we require the user upgrade patch on this old CentOS 5.x box? I<br>
need to leave now so I'm leaving the problem here for now to see if<br>
anyone else has a comment.</blockquote></div><br>This seems like a silly reason to require a newer patch version, when it's trivial to fix the recipe to not enter .pc, IMO. Nothing should be modifying files in there directly anyway.<br>
-- <br>Christopher Larson</div></div>