gdb-python git repository

gdb-python git repository

[Nick Roberts]

I've checked out the the code in the git repository repository as described
in the Wiki:

     git checkout --track -b python-revisited origin/python-revisited

but now if I do:

     cd mainline
     git pull

it asks for a passphrase and fails when I give it one, presumably because I'm
not registered for the project.

I just want to update to the changes, not push any back.  Is the repository set
up to do this anonymously (like pserver with CVS) or am I doing something
wrong?  It seems that it should work without passphrases otherwise I wouldn't
have been able to get the initial checkout.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Thiago Jung Bauermann]

Zitat von Nick Roberts <nickrob@snap.net.nz>:
> it asks for a passphrase and fails when I give it one, presumably because I'm
> not registered for the project.
>
> I just want to update to the changes, not push any back.  Is the   
> repository set
> up to do this anonymously (like pserver with CVS) or am I doing something
> wrong?

Could you try cloning with:

git clone http://git.gitorious.org/gdb-python/mainline.git

? I think that corresponds to the "anonymous checkout".

Sorry to take this long to respond. At the moment I'm only reading e-mail
eventually, and not all of it.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb-python git repository

[Nick Roberts]

 > > I just want to update to the changes, not push any back.  Is the   
 > > repository set
 > > up to do this anonymously (like pserver with CVS) or am I doing something
 > > wrong?
 > 
 > Could you try cloning with:
 > 
 > git clone http://git.gitorious.org/gdb-python/mainline.git
 > 
 > ? I think that corresponds to the "anonymous checkout".

I'll give it a go but can you say why you think this will give a different
result to:

  git clone git://git.gitorious.org/gdb-python/mainline.git

AFAICS it's just a different protocol to get the same files.

I can check the files out anonymously.  I just don't seem to to able to
update (pull).

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Thiago Jung Bauermann]

Zitat von Nick Roberts <nickrob@snap.net.nz>:
>  > Could you try cloning with:
>  >
>  > git clone http://git.gitorious.org/gdb-python/mainline.git
>  >
>  > ? I think that corresponds to the "anonymous checkout".
>
> I'll give it a go but can you say why you think this will give a different
> result to:
>
>   git clone git://git.gitorious.org/gdb-python/mainline.git
>
> AFAICS it's just a different protocol to get the same files.
>
> I can check the files out anonymously.  I just don't seem to to able to
> update (pull).

I believe git:// uses ssh underneath, so by switching to http you shouldn't
be getting any passphrase prompts I guess... (wave hand)
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb-python git repository

[Nick Roberts]

 > I believe git:// uses ssh underneath, so by switching to http you shouldn't
 > be getting any passphrase prompts I guess... (wave hand)

I had presumed it was just a more efficient protocol for downloading the
repository.  At the end I got:

    ...
    cat: /home/nickrob/mainline/.git/refs/remotes/origin/master: No such file or directory
    fatal: : not a valid SHA1
    fatal: Not a valid object name HEAD

but it seemed to work, as I could build GDB and git-pull now gives:

    ...
    Fetching refs/heads/python-revisited from http://git.gitorious.org/gdb-python/mainline.git using http
    Already up-to-date.

I guess CVS has a similar set of arcane rules, but at least they're ones that I
generally know.

Perhaps it's worth putting how to do this `anonymous' clone on the Wiki.

Thanks.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Andreas Schwab]

Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

> I believe git:// uses ssh underneath,

No, it doesn't.  If you want ssh transport, you use git+ssh://, or just
user@host:.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Nick Roberts]

 > > I believe git:// uses ssh underneath,
 > 
 > No, it doesn't.  If you want ssh transport, you use git+ssh://, or just
 > user@host:.

In that case, why did http:// work for me when git:// didn't?  More than
four words please.  Imagine you're talking to an idiot (might not be that
hard!).


-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Andreas Schwab]

Nick Roberts <nickrob@snap.net.nz> writes:

> I've checked out the the code in the git repository repository as described
> in the Wiki:
>
>      git checkout --track -b python-revisited origin/python-revisited
>
> but now if I do:
>
>      cd mainline
>      git pull
>
> it asks for a passphrase and fails when I give it one, presumably because I'm
> not registered for the project.

The third line in the instructions is wrong, there is no need to add
another origin.  Just leave it out.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Andreas Schwab]

Nick Roberts <nickrob@snap.net.nz> writes:

>  > > I believe git:// uses ssh underneath,
>  > 
>  > No, it doesn't.  If you want ssh transport, you use git+ssh://, or just
>  > user@host:.
>
> In that case, why did http:// work for me when git:// didn't?  More than
> four words please.  Imagine you're talking to an idiot (might not be that
> hard!).

The git protocol works fine for you, otherwise you would not have been
able to clone it.  But the third line in the instructions explicitly
changes the protocol to git+ssh, which is wrong.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Nick Roberts]

 > The git protocol works fine for you, otherwise you would not have been
 > able to clone it.  But the third line in the instructions explicitly
 > changes the protocol to git+ssh, which is wrong.

The third line is:

   git checkout --track -b python-revisited origin/python-revisited

I don't see how that changes the protocol to git+ssh.

 > ...Just leave it out.

If I do:

   git checkout --track -b python-revisited origin/python-revisited

or

   git checkout --track -b python-revisited

I get:

   git checkout: branch python-revisited already exists

I have the repository checked out as described in the wiki and which didn't
appear to involve ssh.  What git command should I use (from the mainline
directory?) to do an update (anonymously)?  I would guess it's some kind
of "git pull"

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Thiago Jung Bauermann]

Zitat von Andreas Schwab <schwab@suse.de>:
> The third line in the instructions is wrong, there is no need to add
> another origin.  Just leave it out.

That line was there because the latest git version at the time had a bug
which would leave the origin blank when cloning a "HEADless" repository.

It was fixed since then, so if you use a recent git then it is unnecessary.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb-python git repository

[Andreas Schwab]

Nick Roberts <nickrob@snap.net.nz> writes:

>  > The git protocol works fine for you, otherwise you would not have been
>  > able to clone it.  But the third line in the instructions explicitly
>  > changes the protocol to git+ssh, which is wrong.
>
> The third line is:

I have already removed that line.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Andreas Schwab]

Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

> Zitat von Andreas Schwab <schwab@suse.de>:
>> The third line in the instructions is wrong, there is no need to add
>> another origin.  Just leave it out.
>
> That line was there because the latest git version at the time had a bug
> which would leave the origin blank when cloning a "HEADless" repository.

Would it be possible to add a HEAD to the repository?

> It was fixed since then, so if you use a recent git then it is unnecessary.

At least it would have to use the correct url.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Nick Roberts]

Andreas Schwab writes:
 > Nick Roberts <nickrob@snap.net.nz> writes:
 > 
 > >  > The git protocol works fine for you, otherwise you would not have been
 > >  > able to clone it.  But the third line in the instructions explicitly
 > >  > changes the protocol to git+ssh, which is wrong.
 > >
 > > The third line is:
 > 
 > I have already removed that line.

OK (I still don't see where ssh comes into the picture).

How do I update from the repository using the working copy that I've already
checked out?

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Andreas Schwab]

Nick Roberts <nickrob@snap.net.nz> writes:

> How do I update from the repository using the working copy that I've already
> checked out?

Just move the origin back to the original url.

$ git config remote.origin.url git://git.gitorious.org/gdb-python/mainline.git

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Nick Roberts]

 > > How do I update from the repository using the working copy that I've already
 > > checked out?
 > 
 > Just move the origin back to the original url.
 > 
 > $ git config remote.origin.url git://git.gitorious.org/gdb-python/mainline.git

That worked.  Thanks.

-- 
Nick                                           http://www.inet.net.nz/~nickrob

Re: gdb-python git repository

[Thiago Jung Bauermann]

Zitat von Andreas Schwab <schwab@suse.de>:
>> That line was there because the latest git version at the time had a bug
>> which would leave the origin blank when cloning a "HEADless" repository.
>
> Would it be possible to add a HEAD to the repository?

I don't know.

>> It was fixed since then, so if you use a recent git then it is unnecessary.
>
> At least it would have to use the correct url.

It was correct for people who have commit access and want to help with
development, which is the main purpose of that repository.

Of course, people are welcome to just follow what's going on there, but it
was not the primary intent of the instructions (we are posting patches to
the mailing list for that).


-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center

Re: gdb-python git repository

[Andreas Schwab]

Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

> Zitat von Andreas Schwab <schwab@suse.de>:
>>> That line was there because the latest git version at the time had a bug
>>> which would leave the origin blank when cloning a "HEADless" repository.
>>
>> Would it be possible to add a HEAD to the repository?
>
> I don't know.

It would simplify the instructions.  If HEAD would point to the
python-revisited branch then people would just have to clone using
either the git:// or the git+ssh:// url (depending on whether they need
write access) and be done with it.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: gdb-python git repository

[Thiago Jung Bauermann]

Zitat von Andreas Schwab <schwab@suse.de>:
> Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
>> Zitat von Andreas Schwab <schwab@suse.de>:
>>> Would it be possible to add a HEAD to the repository?
>>
>> I don't know.
>
> It would simplify the instructions.  If HEAD would point to the
> python-revisited branch then people would just have to clone using
> either the git:// or the git+ssh:// url (depending on whether they need
> write access) and be done with it.

Good point. Unfortunately I won't be able to look into it in the next
week or so. If anybody else wants to try it before then, feel free.

Hopefuly we'll get the first two or three python patches committed soon,
and then all work with python support can move to this list and the git
repository can fade away.

BTW, just as FYI to the list, I'm slowly fixing the values patch, but
again I probably won't be able to really work on it in the next week
or so.
-- 
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center