Cron <git-svn at code> $HOME/git-svn-sync

[Derek Atkins]

John Ralls <jralls at ceridwen.us> writes:

> On Aug 27, 2013, at 11:55 AM, Derek Atkins <derek at ihtfp.com> wrote:
>
>> UMMM..........
>> 
>> This looks.... potentially bad...
>> 
>> -derek
>> 
>> 
>> On Tue, August 27, 2013 2:47 pm, Cron Daemon wrote:
>>> Running git svn fetch
>>> remote: fatal: Invalid revision range
>>> 0000000000000000000000000000000000000000..df4f6a321c78b751d26f781ff59eb4558366e451
>>> remote: fatal: Invalid revision range
>>> 0000000000000000000000000000000000000000..df4f6a321c78b751d26f781ff59eb4558366e451
>>> remote: *** Push refs to origin (usually github)...
>>> remote: To ssh://git@github.com/Gnucash/gnucash.git
>>> remote:    7bb0ec7..0e18662  2.4 -> 2.4
>>> remote: Everything up-to-date
>>> To ssh://git@code.gnucash.org/gnucash.git
>>>   7bb0ec7..0e18662  svn/2.4 -> 2.4
>>> * [new branch]      svn/trunk -> trunk
>>> Everything up-to-date
>>> Running git svn fetch
>>> remote: fatal: Invalid revision range
>>> 0000000000000000000000000000000000000000..0d1348d05286fad89774bd2f7c44839c81bc790f
>>> remote: fatal: Invalid revision range
>>> 0000000000000000000000000000000000000000..0d1348d05286fad89774bd2f7c44839c81bc790f
>>> remote: *** Push refs to origin (usually github)...
>>> remote: Warning: Permanently added the RSA host key for IP address
>>> '192.30.252.128' to the list of known hosts.        remote:
>>> remote: To ssh://git@github.com/Gnucash/gnucash-docs.git
>>> remote:  * [new branch]      master -> master
>>> remote: Everything up-to-date
>>> To ssh://git@code.gnucash.org/gnucash-docs.git
>>> * [new branch]      svn/trunk -> trunk
>>> Everything up-to-date
>>> 
>> 
>
>
> Well, nothing bad happened: The github repo is fine. However, while a
> mirror-clone of code.gnucash.org/gnucash.git has the right commits on
> everything, it has a master branch which isn't a symbolic-ref but is
> pointing to the right sha1 and HEAD containing ref:
> refs/heads/master. A clone my local gnucash.git (the one that makes
> gnucash-old on github) which *doesn't* have a master and which has
> HEAD pointed at refs/heads/trunk matches that: No master and HEAD
> pointed at refs/heads/trunk.
>
> Might either the svn or gitolite hooks be doing something behind our backs?

I don't know.  You wrote the svn->git push script..  And I'm pretty sure
the git(olite)->github push is available (although I think Geert did
that).  I'm not sure what it could be doing behind our backs.

Maybe this is just something from the first push?  Maybe the next push
will be okay?

One thing I noticed is:

[root at code repositories]# cat gnucash*.git/refs/heads/master 
ref: refs/heads/trunk
ref: refs/heads/trunk
7407a508e79e64cb94b9792991999095ca141b2e

So master is still a ref to trunk..  However:

[root at code repositories]# cat gnucash*.git/HEAD
ref: refs/heads/trunk
ref: refs/heads/trunk
ref: refs/heads/master

Git can be so confusing sometimes.....

> Regards,
> John Ralls

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available