On Mon, Mar 05, 2012 at 11:00:38AM +, James wrote:
> Francisco
>
> >> 15 * * * * cd /home/james/lilypond-git && python
> >> /home/james/patchy/lilypond-patchy-staging.py
cron ignores your ~/.profile, ~/.bashrc, etc. Remember that shell
script I sent you a few month ago, along with my sample
Francisco
On 5 March 2012 10:57, Francisco Vila wrote:
> 2012/3/5 James :
>>> What is your complete cron line? You are aware that the PATH variable
>>> is set to a quite basic path?
>>
>> It was
>>
>> 15 * * * * cd /home/james/lilypond-git && python
>> /home/james/patchy/lilypond-patchy-staging.
2012/3/5 James :
>> What is your complete cron line? You are aware that the PATH variable
>> is set to a quite basic path?
>
> It was
>
> 15 * * * * cd /home/james/lilypond-git && python
> /home/james/patchy/lilypond-patchy-staging.py
>
> I intended to leave it for a few hours to see if I got the
Hello,
On 5 March 2012 10:32, David Kastrup wrote:
> James writes:
>
>> Hello,
>>
>> On 5 March 2012 09:41, David Kastrup wrote:
>>> James writes:
>>
I cant seem to get cron jobs to run on my LilyDev - I've done all the
cron.allow etc. I was wondering (if anyone knows immediatel
James writes:
> Hello,
>
> On 5 March 2012 09:41, David Kastrup wrote:
>> James writes:
>
>>>
>>> I cant seem to get cron jobs to run on my LilyDev - I've done all the
>>> cron.allow etc. I was wondering (if anyone knows immediately) if
>>> stating the command in cron requires anything special
Hello,
On 5 March 2012 09:41, David Kastrup wrote:
> James writes:
>>
>> I cant seem to get cron jobs to run on my LilyDev - I've done all the
>> cron.allow etc. I was wondering (if anyone knows immediately) if
>> stating the command in cron requires anything special if using two
>> concatenate
James writes:
> On 4 March 2012 11:10, Graham Percival wrote:
>> On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote:
>>> Anyway, I'm back at home this evening and will have a few more test
>>> runs (with cron just to make sure I can leave it unattended) and then
>>> by Monday I should be runn
Hello,
On 4 March 2012 11:10, Graham Percival wrote:
> On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote:
>> Anyway, I'm back at home this evening and will have a few more test
>> runs (with cron just to make sure I can leave it unattended) and then
>> by Monday I should be running 'lilypond-
Hello,
On 4 March 2012 11:10, Graham Percival wrote:
> On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote:
>> Anyway, I'm back at home this evening and will have a few more test
>> runs (with cron just to make sure I can leave it unattended) and then
>> by Monday I should be running 'lilypond-
On Sun, Mar 04, 2012 at 08:10:59AM +, James wrote:
> Anyway, I'm back at home this evening and will have a few more test
> runs (with cron just to make sure I can leave it unattended) and then
> by Monday I should be running 'lilypond-patchy-staging.py' as often as
> people want me to. Any spec
Phil,
On 4 March 2012 10:55, Phil Holmes wrote:
> - Original Message - From: "James"
>
>
>> I'm not sure if Phil wants to leave his machine running during his day
>> (I know it's too noisy during the evening) but I'll let him tell me
>> when he wants to schedule his. I have said I get in
- Original Message -
From: "James"
I'm not sure if Phil wants to leave his machine running during his day
(I know it's too noisy during the evening) but I'll let him tell me
when he wants to schedule his. I have said I get intermittent loss of
internet so him and I running in tandem or
James writes:
> David,
>
> On 4 March 2012 08:20, David Kastrup wrote:
>> James writes:
>>
>>> I don't really understand why I still had the same issues as I had
>>> before - git would complain about shallow repositories (I did look it
>>> up but it didn't shed any light)
>>
>> I answered your
David,
On 4 March 2012 08:20, David Kastrup wrote:
> James writes:
>
>> I don't really understand why I still had the same issues as I had
>> before - git would complain about shallow repositories (I did look it
>> up but it didn't shed any light)
>
> I answered your respective last time on the
James writes:
> I don't really understand why I still had the same issues as I had
> before - git would complain about shallow repositories (I did look it
> up but it didn't shed any light)
I answered your respective last time on the list with a recipe of how to
unshallow a clone.
> so I simply
Hello,
Looks like I am (just about) good to go.
--snip--
- Forwarded message --
From:
Date: 4 March 2012 07:01
Subject: Patchy email
To: pkx1...@gmail.com
Cc: pkx1...@gmail.com
Begin LilyPond compile, commit: acb4ce2a0927ae1899752c991d1c843f5b01196e
Merged staging, now at: a
16 matches
Mail list logo
