Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: Re: EPICS 7 Release Candidate 1
From: Mark Rivers <rivers@cars.uchicago.edu>
To: Michael Davidsaver <mdavidsaver@gmail.com>, Andrew Johnson <anj@aps.anl.gov>, "core-talk@aps.anl.gov" <core-talk@aps.anl.gov>
Date: Mon, 4 Dec 2017 02:00:57 +0000
Next problem.


After successfully cloning with https: I tried to check out the R7.0.1-pre1 tag.  I did this successfully at the top-level, and then tried to do it for each submodule with

git submodule foreach git checkout R7.0.1-pre1

It succeeded for ca, database, and libCom, but failed for normativeTypes.


What is the correct way to check out each module at the release which is equivalent to R7.0.1-pre1?  Is it sufficient to do that at the top level, i.e. was the top level R7.0.1-pre1 tag applied when each submodule was at the R7.0.1-pre1 version?


corvette:local/epics/epics-base>git checkout R7.0.1-pre1
M       modules/database
M       modules/libcom
M       modules/normativeTypes
M       modules/pvAccess
M       modules/pvData
M       modules/pvDatabase
M       modules/pva2pva
M       modules/pvaClient
Note: checking out 'R7.0.1-pre1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b new_branch_name

HEAD is now at e785d87... Set version 7.0.1-pre1 in CONFIG_BASE_VERSION
corvette:local/epics/epics-base>git submodule foreach git checkout R7.0.1-pre1
Entering 'modules/ca'
Previous HEAD position was 5dfd1fc... Export tool configurations as cfg/CONFIG_* files
HEAD is now at e785d87... Set version 7.0.1-pre1 in CONFIG_BASE_VERSION
Entering 'modules/database'
Previous HEAD position was eac8865... Merge 'ignore-siml-failure' into database/master
HEAD is now at e785d87... Set version 7.0.1-pre1 in CONFIG_BASE_VERSION
Entering 'modules/libcom'
Previous HEAD position was 3ca5c20... perl 5.8 compatibility fix
HEAD is now at e785d87... Set version 7.0.1-pre1 in CONFIG_BASE_VERSION
Entering 'modules/normativeTypes'
error: pathspec 'R7.0.1-pre1' did not match any file(s) known to git.
Stopping at 'modules/normativeTypes'; script returned non-zero status.

Thanks,

Mar




________________________________
From: Mark Rivers
Sent: Sunday, December 3, 2017 7:51 PM
To: Michael Davidsaver; Andrew Johnson; core-talk@aps.anl.gov
Subject: Re: EPICS 7 Release Candidate 1


> I see the same.  I can't say I've tried this before as "git@github.com:..." is using SSH to pull,
> which isn't usual due to speed.


> Were you trying for "git://github.com/" which is the git native protocol?

> I usually use http for checkouts.


No, I have always cloned with git@github.com.  I just tested it with

git clone --recursive git@github.com:/areaDetector/areaDetector

and it worked fine.  It was getting 4.2 MiB/s.


I then tested epics-base using https.

git clone --recursive https://github.com/epics-base/epics-base


That worked.  But it is no faster than ssh, also 4.2 MiB/s.


Thanks,

Mark




________________________________
From: Michael Davidsaver <mdavidsaver@gmail.com>
Sent: Sunday, December 3, 2017 6:44 PM
To: Mark Rivers; Andrew Johnson; core-talk@aps.anl.gov
Subject: Re: EPICS 7 Release Candidate 1

On 12/03/2017 05:44 PM, Mark Rivers wrote:
> I would like to get this via git rather than a tar file. I tried the following but it failed.  What am I doing wrong?
>
>
>
> corvette:/usr/local/epics>git clone --recursive git@github.com:epics-base/epics-base

I see the same.  I can't say I've tried this before as "git@github.com:..." is using SSH to pull,
which isn't usual due to speed.  Were you trying for "git://github.com/" which is the git native protocol?
I usually use http for checkouts.

> git clone --recursive https://github.com/epics-base/epics-base.git


Also, as this is as good a point as any.  My usual git configuration to mangle remote
urls so that I can clone via http and automatically push via ssh.

> git config --global --replace-all url.git@github.com:.pushInsteadOf https://github.com/
> git config --global --add         url.git@github.com:.pushInsteadOf git://github.com/
> git config --global --replace-all url.git+ssh://git.launchpad.net/.pushInsteadOf https://git.launchpad.net/
> git config --global --add         url.git+ssh://git.launchpad.net/.pushInsteadOf lp:
> git config --global --replace-all url.https://git.launchpad.net/.insteadof lp:

Replies:
Re: EPICS 7 Release Candidate 1 Mark Rivers
Re: EPICS 7 Release Candidate 1 Michael Davidsaver
References:
Re: EPICS 7 Release Candidate 1 Mark Rivers
Re: EPICS 7 Release Candidate 1 Michael Davidsaver
Re: EPICS 7 Release Candidate 1 Mark Rivers

Navigate by Date:
Prev: Re: EPICS 7 Release Candidate 1 Mark Rivers
Next: Re: EPICS 7 Release Candidate 1 Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: Re: EPICS 7 Release Candidate 1 Mark Rivers
Next: Re: EPICS 7 Release Candidate 1 Mark Rivers
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 03 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·