RTT v1 updates

Submitted by snrkiwi on Sat, 2011-04-23 12:36

RTT-dev

Patches for boost v1.46, and back-ports of some v2 test-related patches.

I'll work up same boost patches for v2
S

Attachment	Size
0001-os-Cope-with-boost-filesystem-v3-changes.patch	2.54 KB
0002-scripting-Cope-with-boost-v1.46-namespace-changes.patch	4.94 KB
0003-cmake-Add-code-coverage.patch	4.53 KB
0004-Fixes-836-Test-timeout-ignored-by-ctest.patch	1.02 KB
0005-cmake-Add-option-to-set-CTest-timeout.patch	834 bytes

RTT v1 updates

Submitted by peter on Thu, 2011-04-28 13:32.

On Saturday 23 April 2011 14:33:50 S Roderick wrote:
> Patches for boost v1.46, and back-ports of some v2 test-related patches.
>
> I'll work up same boost patches for v2
> S

Thanks for all this. I've pushed them to trunk.

Peter

RTT v1 updates

Submitted by snrkiwi on Fri, 2011-04-29 12:28.

On Apr 28, 2011, at 09:31 , Peter Soetens wrote:

> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
>> Patches for boost v1.46, and back-ports of some v2 test-related patches.
>>
>> I'll work up same boost patches for v2
>> S
>
> Thanks for all this. I've pushed them to trunk.
>
> Peter

Thanks.

What's the plan re RTT and OCL v1 git repo's? I don't see these patches in their git repo's as of now - you mentioned adding some Hudson jobs to auto-sync SVN trunk with your github. What is the status of those? While I understand your desire to not disrupt SVN-only v1 users, the lack of sync'ing is making it really hard for us developers using git to work with both v1 and v2 ... is there any way we can help to resolve this situation?
S

RTT v1 updates

Submitted by peter on Fri, 2011-04-29 14:04.

On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
> > On Saturday 23 April 2011 14:33:50 S Roderick wrote:
> >> Patches for boost v1.46, and back-ports of some v2 test-related patches.
> >>
> >> I'll work up same boost patches for v2
> >> S
> >
> > Thanks for all this. I've pushed them to trunk.
> >
> > Peter
>
> Thanks.
>
> What's the plan re RTT and OCL v1 git repo's? I don't see these patches in
> their git repo's as of now - you mentioned adding some Hudson jobs to
> auto-sync SVN trunk with your github. What is the status of those? While I
> understand your desire to not disrupt SVN-only v1 users, the lack of
> sync'ing is making it really hard for us developers using git to work with
> both v1 and v2 ... is there any way we can help to resolve this situation?
> S

I was working on this, but it took some time to get it right. Cloning a git
repository is not enough to get git-svn working automatically. This is the
hudson job running now daily (after a git clone of the github repos):

has_svn="$(cat .git/config | grep svn-remote)" || true
if [ "x$has_svn" = x ]; then
   echo "
[svn]
    addAuthorFrom = true
    useLogAuthor = true
" >> .git/config
   git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
fi
 
sudo apt-get install -y git-svn subversion git
# go away from hudson branch
git checkout rtt-1.0-svn-patches
# re-create the meta data
git rev-parse HEAD > .git/refs/remotes/git-svn
git svn info
# pull in new changes from svn and rebase on them:
git svn rebase
# push our changes to svn server:
git svn dcommit
# push to github:
git push origin rtt-1.0-svn-patches

Peter

RTT v1 updates

Submitted by snrkiwi on Fri, 2011-04-29 14:08.

On Apr 29, 2011, at 10:02 , Peter Soetens wrote:

> On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
>> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
>>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
>>>> Patches for boost v1.46, and back-ports of some v2 test-related patches.
>>>>
>>>> I'll work up same boost patches for v2
>>>> S
>>>
>>> Thanks for all this. I've pushed them to trunk.
>>>
>>> Peter
>>
>> Thanks.
>>
>> What's the plan re RTT and OCL v1 git repo's? I don't see these patches in
>> their git repo's as of now - you mentioned adding some Hudson jobs to
>> auto-sync SVN trunk with your github. What is the status of those? While I
>> understand your desire to not disrupt SVN-only v1 users, the lack of
>> sync'ing is making it really hard for us developers using git to work with
>> both v1 and v2 ... is there any way we can help to resolve this situation?
>> S
>
> I was working on this, but it took some time to get it right. Cloning a git
> repository is not enough to get git-svn working automatically. This is the
> hudson job running now daily (after a git clone of the github repos):
>
>

> has_svn="$(cat .git/config | grep svn-remote)" || true
> if [ "x$has_svn" = x ]; then
>   echo "
> [svn]
>    addAuthorFrom = true
>    useLogAuthor = true
> " >> .git/config
>   git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
> fi
> 
> sudo apt-get install -y git-svn subversion git
> # go away from hudson branch
> git checkout rtt-1.0-svn-patches
> # re-create the meta data
> git rev-parse HEAD > .git/refs/remotes/git-svn
> git svn info
> # pull in new changes from svn and rebase on them:
> git svn rebase
> # push our changes to svn server:
> git svn dcommit
> # push to github:
> git push origin rtt-1.0-svn-patches
>

>
> Peter
>
UGH!!! Sorry this is so difficult ...

So this should be working now? Your gitub/rtt-1.0-svn-patches branch should be up to date (as of the previous night) with SVN trunk?
S

RTT v1 updates

Submitted by peter on Fri, 2011-04-29 14:32.

On Friday 29 April 2011 16:05:01 Stephen Roderick wrote:
> On Apr 29, 2011, at 10:02 , Peter Soetens wrote:
> > On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
> >> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
> >>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
> >>>> Patches for boost v1.46, and back-ports of some v2 test-related
> >>>> patches.
> >>>>
> >>>> I'll work up same boost patches for v2
> >>>> S
> >>>
> >>> Thanks for all this. I've pushed them to trunk.
> >>>
> >>> Peter
> >>
> >> Thanks.
> >>
> >> What's the plan re RTT and OCL v1 git repo's? I don't see these patches
> >> in their git repo's as of now - you mentioned adding some Hudson jobs
> >> to auto-sync SVN trunk with your github. What is the status of those?
> >> While I understand your desire to not disrupt SVN-only v1 users, the
> >> lack of sync'ing is making it really hard for us developers using git
> >> to work with both v1 and v2 ... is there any way we can help to resolve
> >> this situation? S
> >
> > I was working on this, but it took some time to get it right. Cloning a
> > git repository is not enough to get git-svn working automatically. This
> > is the hudson job running now daily (after a git clone of the github
> > repos):
> >
> >

> > has_svn="$(cat .git/config | grep svn-remote)" || true
> > if [ "x$has_svn" = x ]; then
> > 
> >   echo "
> > 
> > [svn]
> > 
> >    addAuthorFrom = true
> >    useLogAuthor = true
> > 
> > " >> .git/config
> > 
> >   git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
> > 
> > fi
> > 
> > sudo apt-get install -y git-svn subversion git
> > # go away from hudson branch
> > git checkout rtt-1.0-svn-patches
> > # re-create the meta data
> > git rev-parse HEAD > .git/refs/remotes/git-svn
> > git svn info
> > # pull in new changes from svn and rebase on them:
> > git svn rebase
> > # push our changes to svn server:
> > git svn dcommit
> > # push to github:
> > git push origin rtt-1.0-svn-patches
> >

> >
> > Peter
>
> UGH!!! Sorry this is so difficult ...
>
> So this should be working now? Your gitub/rtt-1.0-svn-patches branch should
> be up to date (as of the previous night) with SVN trunk? S

I hope/think so.

Peter

RTT v1 updates

Submitted by snrkiwi on Sat, 2011-04-30 11:28.

On Apr 29, 2011, at 10:28 , Peter Soetens wrote:

> On Friday 29 April 2011 16:05:01 Stephen Roderick wrote:
>> On Apr 29, 2011, at 10:02 , Peter Soetens wrote:
>>> On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
>>>> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
>>>>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
>>>>>> Patches for boost v1.46, and back-ports of some v2 test-related
>>>>>> patches.
>>>>>>
>>>>>> I'll work up same boost patches for v2
>>>>>> S
>>>>>
>>>>> Thanks for all this. I've pushed them to trunk.
>>>>>
>>>>> Peter
>>>>
>>>> Thanks.
>>>>
>>>> What's the plan re RTT and OCL v1 git repo's? I don't see these patches
>>>> in their git repo's as of now - you mentioned adding some Hudson jobs
>>>> to auto-sync SVN trunk with your github. What is the status of those?
>>>> While I understand your desire to not disrupt SVN-only v1 users, the
>>>> lack of sync'ing is making it really hard for us developers using git
>>>> to work with both v1 and v2 ... is there any way we can help to resolve
>>>> this situation? S
>>>
>>> I was working on this, but it took some time to get it right. Cloning a
>>> git repository is not enough to get git-svn working automatically. This
>>> is the hudson job running now daily (after a git clone of the github
>>> repos):
>>>
>>>

>>> has_svn="$(cat .git/config | grep svn-remote)" || true
>>> if [ "x$has_svn" = x ]; then
>>> 
>>>  echo "
>>> 
>>> [svn]
>>> 
>>>   addAuthorFrom = true
>>>   useLogAuthor = true
>>> 
>>> " >> .git/config
>>> 
>>>  git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
>>> 
>>> fi
>>> 
>>> sudo apt-get install -y git-svn subversion git
>>> # go away from hudson branch
>>> git checkout rtt-1.0-svn-patches
>>> # re-create the meta data
>>> git rev-parse HEAD > .git/refs/remotes/git-svn
>>> git svn info
>>> # pull in new changes from svn and rebase on them:
>>> git svn rebase
>>> # push our changes to svn server:
>>> git svn dcommit
>>> # push to github:
>>> git push origin rtt-1.0-svn-patches
>>>

>>>
>>> Peter
>>
>> UGH!!! Sorry this is so difficult ...
>>
>> So this should be working now? Your gitub/rtt-1.0-svn-patches branch should
>> be up to date (as of the previous night) with SVN trunk? S
>
> I hope/think so.
>
> Peter
>

RTT looks good, I got a set of changes, but I see no changes in OCL. I guess you haven't done the above for OCL?
S

RTT v1 updates

Submitted by snrkiwi on Sun, 2011-05-08 13:44.

On Apr 30, 2011, at 07:27 , Stephen Roderick wrote:

>
> On Apr 29, 2011, at 10:28 , Peter Soetens wrote:
>
>> On Friday 29 April 2011 16:05:01 Stephen Roderick wrote:
>>> On Apr 29, 2011, at 10:02 , Peter Soetens wrote:
>>>> On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
>>>>> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
>>>>>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
>>>>>>> Patches for boost v1.46, and back-ports of some v2 test-related
>>>>>>> patches.
>>>>>>>
>>>>>>> I'll work up same boost patches for v2
>>>>>>> S
>>>>>>
>>>>>> Thanks for all this. I've pushed them to trunk.
>>>>>>
>>>>>> Peter
>>>>>
>>>>> Thanks.
>>>>>
>>>>> What's the plan re RTT and OCL v1 git repo's? I don't see these patches
>>>>> in their git repo's as of now - you mentioned adding some Hudson jobs
>>>>> to auto-sync SVN trunk with your github. What is the status of those?
>>>>> While I understand your desire to not disrupt SVN-only v1 users, the
>>>>> lack of sync'ing is making it really hard for us developers using git
>>>>> to work with both v1 and v2 ... is there any way we can help to resolve
>>>>> this situation? S
>>>>
>>>> I was working on this, but it took some time to get it right. Cloning a
>>>> git repository is not enough to get git-svn working automatically. This
>>>> is the hudson job running now daily (after a git clone of the github
>>>> repos):
>>>>
>>>>

>>>> has_svn="$(cat .git/config | grep svn-remote)" || true
>>>> if [ "x$has_svn" = x ]; then
>>>> 
>>>> echo "
>>>> 
>>>> [svn]
>>>> 
>>>>  addAuthorFrom = true
>>>>  useLogAuthor = true
>>>> 
>>>> " >> .git/config
>>>> 
>>>> git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
>>>> 
>>>> fi
>>>> 
>>>> sudo apt-get install -y git-svn subversion git
>>>> # go away from hudson branch
>>>> git checkout rtt-1.0-svn-patches
>>>> # re-create the meta data
>>>> git rev-parse HEAD > .git/refs/remotes/git-svn
>>>> git svn info
>>>> # pull in new changes from svn and rebase on them:
>>>> git svn rebase
>>>> # push our changes to svn server:
>>>> git svn dcommit
>>>> # push to github:
>>>> git push origin rtt-1.0-svn-patches
>>>>

>>>>
>>>> Peter
>>>
>>> UGH!!! Sorry this is so difficult ...
>>>
>>> So this should be working now? Your gitub/rtt-1.0-svn-patches branch should
>>> be up to date (as of the previous night) with SVN trunk? S
>>
>> I hope/think so.
>>
>> Peter
>>
>
> RTT looks good, I got a set of changes, but I see no changes in OCL. I guess you haven't done the above for OCL?
> S

Any chance you can do the same with OCL v1?
S

RTT v1 updates

Submitted by peter on Mon, 2011-05-09 08:04.

On Sunday 08 May 2011 15:40:01 S Roderick wrote:
> On Apr 30, 2011, at 07:27 , Stephen Roderick wrote:
> > On Apr 29, 2011, at 10:28 , Peter Soetens wrote:
> >> On Friday 29 April 2011 16:05:01 Stephen Roderick wrote:
> >>> On Apr 29, 2011, at 10:02 , Peter Soetens wrote:
> >>>> On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
> >>>>> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
> >>>>>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
> >>>>>>> Patches for boost v1.46, and back-ports of some v2 test-related
> >>>>>>> patches.
> >>>>>>>
> >>>>>>> I'll work up same boost patches for v2
> >>>>>>> S
> >>>>>>
> >>>>>> Thanks for all this. I've pushed them to trunk.
> >>>>>>
> >>>>>> Peter
> >>>>>
> >>>>> Thanks.
> >>>>>
> >>>>> What's the plan re RTT and OCL v1 git repo's? I don't see these
> >>>>> patches in their git repo's as of now - you mentioned adding some
> >>>>> Hudson jobs to auto-sync SVN trunk with your github. What is the
> >>>>> status of those? While I understand your desire to not disrupt
> >>>>> SVN-only v1 users, the lack of sync'ing is making it really hard for
> >>>>> us developers using git to work with both v1 and v2 ... is there any
> >>>>> way we can help to resolve this situation? S
> >>>>
> >>>> I was working on this, but it took some time to get it right. Cloning
> >>>> a git repository is not enough to get git-svn working automatically.
> >>>> This is the hudson job running now daily (after a git clone of the
> >>>> github repos):
> >>>>
> >>>>

> >>>> has_svn="$(cat .git/config | grep svn-remote)" || true
> >>>> if [ "x$has_svn" = x ]; then
> >>>> 
> >>>> echo "
> >>>> 
> >>>> [svn]
> >>>> 
> >>>>  addAuthorFrom = true
> >>>>  useLogAuthor = true
> >>>> 
> >>>> " >> .git/config
> >>>> 
> >>>> git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
> >>>> 
> >>>> fi
> >>>> 
> >>>> sudo apt-get install -y git-svn subversion git
> >>>> # go away from hudson branch
> >>>> git checkout rtt-1.0-svn-patches
> >>>> # re-create the meta data
> >>>> git rev-parse HEAD > .git/refs/remotes/git-svn
> >>>> git svn info
> >>>> # pull in new changes from svn and rebase on them:
> >>>> git svn rebase
> >>>> # push our changes to svn server:
> >>>> git svn dcommit
> >>>> # push to github:
> >>>> git push origin rtt-1.0-svn-patches
> >>>>

> >>>>
> >>>> Peter
> >>>
> >>> UGH!!! Sorry this is so difficult ...
> >>>
> >>> So this should be working now? Your gitub/rtt-1.0-svn-patches branch
> >>> should be up to date (as of the previous night) with SVN trunk? S
> >>
> >> I hope/think so.
> >>
> >> Peter
> >
> > RTT looks good, I got a set of changes, but I see no changes in OCL. I
> > guess you haven't done the above for OCL? S
>
> Any chance you can do the same with OCL v1?
> S

Seems to work now. I've scheduled the rtt/ocl syncs every 4 hours daily.

Peter

RTT v1 updates

Submitted by snrkiwi on Mon, 2011-05-09 12:08.

On May 9, 2011, at 04:01 , Peter Soetens wrote:

> On Sunday 08 May 2011 15:40:01 S Roderick wrote:
>> On Apr 30, 2011, at 07:27 , Stephen Roderick wrote:
>>> On Apr 29, 2011, at 10:28 , Peter Soetens wrote:
>>>> On Friday 29 April 2011 16:05:01 Stephen Roderick wrote:
>>>>> On Apr 29, 2011, at 10:02 , Peter Soetens wrote:
>>>>>> On Friday 29 April 2011 14:23:24 Stephen Roderick wrote:
>>>>>>> On Apr 28, 2011, at 09:31 , Peter Soetens wrote:
>>>>>>>> On Saturday 23 April 2011 14:33:50 S Roderick wrote:
>>>>>>>>> Patches for boost v1.46, and back-ports of some v2 test-related
>>>>>>>>> patches.
>>>>>>>>>
>>>>>>>>> I'll work up same boost patches for v2
>>>>>>>>> S
>>>>>>>>
>>>>>>>> Thanks for all this. I've pushed them to trunk.
>>>>>>>>
>>>>>>>> Peter
>>>>>>>
>>>>>>> Thanks.
>>>>>>>
>>>>>>> What's the plan re RTT and OCL v1 git repo's? I don't see these
>>>>>>> patches in their git repo's as of now - you mentioned adding some
>>>>>>> Hudson jobs to auto-sync SVN trunk with your github. What is the
>>>>>>> status of those? While I understand your desire to not disrupt
>>>>>>> SVN-only v1 users, the lack of sync'ing is making it really hard for
>>>>>>> us developers using git to work with both v1 and v2 ... is there any
>>>>>>> way we can help to resolve this situation? S
>>>>>>
>>>>>> I was working on this, but it took some time to get it right. Cloning
>>>>>> a git repository is not enough to get git-svn working automatically.
>>>>>> This is the hudson job running now daily (after a git clone of the
>>>>>> github repos):
>>>>>>
>>>>>>

>>>>>> has_svn="$(cat .git/config | grep svn-remote)" || true
>>>>>> if [ "x$has_svn" = x ]; then
>>>>>> 
>>>>>> echo "
>>>>>> 
>>>>>> [svn]
>>>>>> 
>>>>>> addAuthorFrom = true
>>>>>> useLogAuthor = true
>>>>>> 
>>>>>> " >> .git/config
>>>>>> 
>>>>>> git svn init https://svn.mech.kuleuven.be/repos/orocos/trunk/rtt
>>>>>> 
>>>>>> fi
>>>>>> 
>>>>>> sudo apt-get install -y git-svn subversion git
>>>>>> # go away from hudson branch
>>>>>> git checkout rtt-1.0-svn-patches
>>>>>> # re-create the meta data
>>>>>> git rev-parse HEAD > .git/refs/remotes/git-svn
>>>>>> git svn info
>>>>>> # pull in new changes from svn and rebase on them:
>>>>>> git svn rebase
>>>>>> # push our changes to svn server:
>>>>>> git svn dcommit
>>>>>> # push to github:
>>>>>> git push origin rtt-1.0-svn-patches
>>>>>>

>>>>>>
>>>>>> Peter
>>>>>
>>>>> UGH!!! Sorry this is so difficult ...
>>>>>
>>>>> So this should be working now? Your gitub/rtt-1.0-svn-patches branch
>>>>> should be up to date (as of the previous night) with SVN trunk? S
>>>>
>>>> I hope/think so.
>>>>
>>>> Peter
>>>
>>> RTT looks good, I got a set of changes, but I see no changes in OCL. I
>>> guess you haven't done the above for OCL? S
>>
>> Any chance you can do the same with OCL v1?
>> S
>
> Seems to work now. I've scheduled the rtt/ocl syncs every 4 hours daily.
>
> Peter

Confirm picked up OCL v1 changes this morning. Thanks!
S