threads / bug / 45866

Bug? git svn tag Authentication failed

Subject: Bug? git svn tag Authentication failed

## tl;dr

2 messages between May 4, 2017 and May 4, 2017.

replies: 1people: 2as markdown or json

Ethan Clevenger· May 4, 2017, 16:21 UTC · lore
Git version: 2.12.2.windows.2
`git svn tag 1.0` results in:
> Copying https://plugins.svn.wordpress.org/gf-payment-continue/trunk at r1651123 to https://plugins.svn.wordpress.org/gf-payment-continue/tags/1.0...
> Authentication failed: No more credentials or we tried too many times.
> Authentication failed at C:\Program Files\Git\mingw64/libexec/git-core\git-svn line 1200.

In my .subversion directory I do have cached credentials under auth/svn.simple. A vanilla svn CLI commit also works:

Show 5 quoted lines
>  svn ci -m 'do creds work?'
> Adding         trunk\.bar
> Transmitting file data .done
> Committing transaction...
> Committed revision 1651133.
Unsure if this is actually a bug or my oversight.

Cheers, Ethan Sterner Stuff Design https://sternerstuffdesign.com

Eric Wong· May 4, 2017, 16:37 UTC · re: Ethan Clevenger · lore

Re: Bug? git svn tag Authentication failed

Ethan Clevenger <ethan@sternerstuffdesign.com> wrote:
> Git version: 2.12.2.windows.2
> 
> `git svn tag 1.0` results in:
<snip>

Note, "git svn tag" uses the same backend code as "git svn branch", and there was a recent fix for that in commit e0688e9b28f2c5ff711460ee8b62077be5df2360 ("git svn: fix authentication with 'branch'")

Looks like that change will be in 2.13 (it's in all the release-canditates), but it should backported to 2.12.x

Junio: I think that commit should go into 'maint', too.  Thanks.
Show 11 quoted lines
> In my .subversion directory I do have cached credentials under
> auth/svn.simple. A vanilla svn CLI commit also works:
> 
> >  svn ci -m 'do creds work?'
> > Adding         trunk\.bar
> > Transmitting file data .done
> > Committing transaction...
> > Committed revision 1651133.
> 
> 
> Unsure if this is actually a bug or my oversight.

Seems like a bug to me. Can you try one of the 2.13 release candidates to confirm? Thanks.

← back to recent threads