On 08/29/2014 03:36 PM, Bruce Ashfield wrote:
On 14-08-29 04:32 PM, Peter A. Bigot wrote:
mkdir -p .$(dirname $checkpoint_dir)
mv $checkpoint_dir .$checkpoint_dir
and even that wouldn't do the right thing in all cases.
I'm restricting what is valid, so I don't have to worry about the
On 14-08-29 04:32 PM, Peter A. Bigot wrote:
On 08/29/2014 03:02 PM, Bruce Ashfield wrote:
On 14-08-29 03:31 PM, Peter A. Bigot wrote:
The point is that issuing a mv like:
mv $checkpoint_dir .$checkpoint_dir
without ensuring that the value of the variable doesn't contain path
componen
On 08/29/2014 03:02 PM, Bruce Ashfield wrote:
On 14-08-29 03:31 PM, Peter A. Bigot wrote:
The point is that issuing a mv like:
mv $checkpoint_dir .$checkpoint_dir
without ensuring that the value of the variable doesn't contain path
components is fragile. I'm not really clear on the g
On 14-08-29 03:31 PM, Peter A. Bigot wrote:
On 08/29/2014 02:17 PM, Bruce Ashfield wrote:
On 14-08-29 03:09 PM, Peter A. Bigot wrote:
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot
wrote:
First, some yak shaving:
If something goes wrong with li
On 08/29/2014 02:17 PM, Bruce Ashfield wrote:
On 14-08-29 03:09 PM, Peter A. Bigot wrote:
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot
wrote:
First, some yak shaving:
If something goes wrong with linux-yocto's do_patch, it prints:
| ERROR. Co
On 14-08-29 03:09 PM, Peter A. Bigot wrote:
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot wrote:
First, some yak shaving:
If something goes wrong with linux-yocto's do_patch, it prints:
| ERROR. Could not apply patches for beaglebone.
|
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot wrote:
First, some yak shaving:
If something goes wrong with linux-yocto's do_patch, it prints:
| ERROR. Could not apply patches for beaglebone.
|Patch failures can be resolved in the devshel
On Thu, Aug 7, 2014 at 2:47 PM, Peter A. Bigot wrote:
> On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
>>
>> On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot wrote:
>>>
>>> Now: What goes wrong with do_patch for me ultimately turns out to be
>>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=509
On 08/07/2014 11:16 AM, Bruce Ashfield wrote:
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot wrote:
Now: What goes wrong with do_patch for me ultimately turns out to be
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5090 biting me again a
year after I filed and forgot it, because I set KMET
On Thu, Aug 7, 2014 at 10:27 AM, Peter A. Bigot wrote:
> First, some yak shaving:
>
> If something goes wrong with linux-yocto's do_patch, it prints:
>
> | ERROR. Could not apply patches for beaglebone.
> |Patch failures can be resolved in the devshell (bitbake -c devshell
> linux-yocto)
>
First, some yak shaving:
If something goes wrong with linux-yocto's do_patch, it prints:
| ERROR. Could not apply patches for beaglebone.
|Patch failures can be resolved in the devshell (bitbake -c
devshell linux-yocto)
In fact, you can't, because meta/classes/devshell.bbclass has:
a
11 matches
Mail list logo
