[svk-devel] SVN mirroring with different credentials

[Alexandru Popescu]

On 1/21/07, Mark Burton <mark.burton at greensocs.com> wrote:
> I had the same problem
> My solution is - frankly - disgusting - so DONT do it - but lease tell
> me a better way!
>
> I did this...
>   I set up a user name to match the credentials needed - for me this
> makes sense anyway, but it is not ideal.
>         -) From that user, I did a check in - it's used the users name, I
> provided the password
>         -) I then copied the cached server credentials file (in
> ~name/.subversion/auth/svn.simple/....) from this user to the user that
> would actually do the check in.
> Now, hey- presto - the user that does the check in, sees a cached
> credentials file and uses it.
>
> If you haven't reached for the sick bag yet, you probably should have
> done. At least, you should note that this will ONLY work for _ONE_
> user.
>
> Of course, you could try (as I did) to "fool" svk into believing that
> the real user is a different user by setting $HOME and $USER. This
> works fine for SVK (it reads it's configuration from ~HOME/.svk etc) -
> but totally fails to fool the underlying subversion - so you end up
> with a bit of a dog's dinner...
>
> Please, somebody on the list  - give us a better way :-)
>         (like a -user -password flag?)
>
> Cheers
>
> Mark.
>
>
>
>
> On 21 Jan 2007, at 16:04, Alexandru Popescu wrote:
>
> > Hi!
> >
> > I am wondering what must be the setup to allow to mirror a SVN where
> > the credentials are different than your current user. In my case I
> > have I have such a mirror and when trying to smerge back it looks like
> > a dance:
> >
> > svk smerge -I /pub/local/groovy/trunk /pub/groovy/trunk
> > Auto-merging (0, 11638) /local/groovy/trunk to /groovy/trunk (base
> > /groovy/trunk:11631).
> > ===> Auto-merging (0, 11157) /local/groovy/trunk to /groovy/trunk
> > (base /groovy/trunk:11154).
> > Merging back to mirror source https://svn.codehaus.org/groovy/trunk.
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Password for 'x':
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Username:
> > Password for 'y':
> > Empty merge.
> > ===> Auto-merging (11157, 11546) /local/groovy/trunk to /groovy/trunk
> > (base /groovy/trunk:11541).
> > Merging back to mirror source https://svn.codehaus.org/groovy/trunk.
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Password for 'x':
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Username:
> > Password for 'y':
> > Empty merge.
> > ===> Auto-merging (11546, 11547) /local/groovy/trunk to /groovy/trunk
> > (base /groovy/trunk:11542).
> > Merging back to mirror source https://svn.codehaus.org/groovy/trunk.
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Password for 'x':
> > Authentication realm: <https://svn.codehaus.org:443> groovy Repo
> > Username:
> > Password for 'y':
> > Empty merge.
> >
> > [... and so on... after 25-30 such iterations I finally gave out).
> >
> > I am quite sure there are better ways to do this, so please let me
> > know.
> >
> > ./alex
> > --
> > .w( the_mindstorm )p.
> > _____________________________________
> >  Alexandru Popescu, OSS Evangelist
> > TestNG/Groovy/AspectJ/WebWork/more...
> >  Information Queue ~ www.InfoQ.com

I am wondering if anybody is watching the ml or the #irc. I have asked
this question both here and there, but nobody seems to be available.

If you are involved in OSS projects, you will notice that not all the
time you can pick the user to exactly match what you have on your
machine. So, in this case svk usage is completely useless, as
committing back to the source repository doesn't really work.

./alex
--
.w( the_mindstorm )p.