Stopping git-svn updates of GCC git mirror for move to git

Stopping git-svn updates of GCC git mirror for move to git

[Joseph Myers]

For the final conversion of GCC to git we'll need to stop git-svn updates 
of the existing mirror, which will be moved and replaced with a fresh 
clean conversion from SVN.

Where does the git-svn process updating that mirror run and how can it be 
disabled at the appropriate time?  What I propose is that once the nightly 
DATESTAMP updates for Saturday have run (shortly after midnight UTC), I 
check in a README.MOVED_TO_GIT file on SVN trunk, then change the SVN 
hooks to make the SVN repository readonly.  Then, once git-svn has 
mirrored those changes, the git-svn mirroring should be shut down.  I'll 
set up a pre-receive hook in the mirror to stop further changes being 
pushed to it, but we don't want git-svn to start trying to push changes to 
the new repository once that's been moved into place and made writable.

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: Stopping git-svn updates of GCC git mirror for move to git

[Frank Ch. Eigler]

Hi -

> [...] Where does the git-svn process updating that mirror run and
> how can it be disabled at the appropriate time?  [...]

I believe all of the gcc-svn automation is run out of cron jobs owned
by the gccadmin user, via scripts in /home/gccadmin/scripts/.  It's
not something set up or overseen by the overseers.  Let us know if you
need us to perform any unusual protective measures around the
transition time, beyond the routine backups etc. already going.

- FChE

Re: Stopping git-svn updates of GCC git mirror for move to git

[Joseph Myers]

On Wed, 8 Jan 2020, Frank Ch. Eigler wrote:

> Hi -
> 
> > [...] Where does the git-svn process updating that mirror run and
> > how can it be disabled at the appropriate time?  [...]
> 
> I believe all of the gcc-svn automation is run out of cron jobs owned
> by the gccadmin user, via scripts in /home/gccadmin/scripts/.  It's
> not something set up or overseen by the overseers.  Let us know if you
> need us to perform any unusual protective measures around the
> transition time, beyond the routine backups etc. already going.

No, git-svn isn't run there.  The snapshots, DATESTAMP updates and online 
documentation updates are run from there, and I'll disable them in the 
crontab at the appropriate point and then re-enable them once converted to 
work with git, but git-svn is run from somewhere else (possibly by 
Jason?).

Could you (now) set up a symlink /git/gcc-old.git -> 
/sourceware/projects/gcc-home/gitfiles-old ?  Right now gitfiles-old is a 
symlink to gitfiles that I just created, but at an appropriate point I'll 
move gitfiles to gitfiles-old (so gcc-old.git will be the location people 
use if they want to check out the old mirror after that) and put the newly 
converted repository at gitfiles (so gcc.git remains the main path to the 
main git repository for GCC).

-- 
Joseph S. Myers
joseph@codesourcery.com