Hi all,

I've received my initial committer password from root@apache.org, logged
in via SSH (Cygwin) to svn.apache.org, run passwd and svnpasswd
successfully, and now I can't commit my change to README.txt in the
source root due to an authorization failure.  Before doing anything, I
checked out everything ok via https with the command "svn checkout
https://svn.apache.org/repos/asf/incubator/jdo".  Here is my commit
attempt:

C:\apache-jdo\jdo>svn commit -m "Added redirect to real readme file"
--username madams
Sending        README.txt
Authentication realm: <https://svn.apache.org:443> ASF Committers
Password for 'madams': ***********
Authentication realm: <https://svn.apache.org:443> ASF Committers
Username: madams
Password for 'madams': ***********
Authentication realm: <https://svn.apache.org:443> ASF Committers
Username: svn: Commit failed (details follow):
svn: CHECKOUT of '/repos/asf/!svn/ver/171175/incubator/jdo/README.txt':
authorization failed (https://svn.apache.org)

C:\apache-jdo\jdo>

I know that I am entering the correct password.  I made my
svn.apache.org password the same as my svn password and I can log in ok
via SSH to svn.apache.org.

I noticed this paragraph in the email from root@apache.org:

Please note that until the Project Management Committee responsible
for the project to which you were given group membership actually
grants
you access to the relevant source code modules, you won't be able to
commit anything.

Does this have anything to do with it?

Thanks,
Matthew

Matthew T. Adams
Corporate Technical Advisor & Senior Consultant
Mobile:  +1 253 732 1051
Phone:  +1 206 331 3833
Fax:  +1 360 937 9616
matthew.adams@xcalia.com
P.O. Box 24163
Federal Way, WA  98093
www.xcalia.com



Xcalia helps businesses address the challenge of Enterprise Information
Access in a heterogeneous environment.  We provide products and services
that facilitate the two-way exchange of information between individuals,
mission-critical applications, and databases.  Our customers enjoy
improved performance, reduced operating and development costs, faster
time to market, and rejuvenated legacy systems.

[ Post a follow-up to this message ]

Matthew,

Matthew T. Adams wrote:
> I've received my initial committer password from root@apache.org, logged
> in via SSH (Cygwin) to svn.apache.org, run passwd and svnpasswd
> successfully, and now I can't commit my change to README.txt in the

I did the same steps, so, I have only a few wild guesses below ...

> source root due to an authorization failure.  Before doing anything, I
> checked out everything ok via https with the command "svn checkout
> https://svn.apache.org/repos/asf/incubator/jdo".  Here is my commit

Not sure if it makes a difference, but you might want to try passing
a --username option to the checkout command.  If that fails, it would
indicate a rather general problem with your svn account and not just
your svn committer status.

> attempt:
>
> C:\apache-jdo\jdo>svn commit -m "Added redirect to real readme file"
> --username madams

Just for you to double-check against my SVN version (on Windows XP
and Cygwin, downloaded from http://subversion.tigris.org):

$ svn --version
svn, version 1.1.4 (r13838)
compiled Apr  3 2005, 22:02:31

> I know that I am entering the correct password.  I made my
> svn.apache.org password the same as my svn password and I can log in ok
> via SSH to svn.apache.org.

For a test, I deleted the 'auth' direcory in the svn user config:
C:\Documents and Settings\MD\Application Data\Subversion\auth

When re-committing the README.txt with the --username again, I got
ask whether to acceppt a certificate (permanently) and to enter my
password again. The directory 'auth' got created from scratch.

Maybe it helps if you start over with a fresh 'auth' directory?

BTW, I had to change the svn 'servers' file for a firewall proxy.

> I noticed this paragraph in the email from root@apache.org:
>
> Please note that until the Project Management Committee responsible
> for the project to which you were given group membership actually
> grants
> you access to the relevant source code modules, you won't be able to
> commit anything.
>
> Does this have anything to do with it?

Don't know much about subversion, but with cvs, there's indeed
a (server) configuration file that contains the list of accounts
with read-only access.

Perhaps, it's similar with svn and a svnadmin has to explicitely
enable your account for write access.

Martin

[ Post a follow-up to this message ]

Matthew T. Adams wrote:

> I've received my initial committer password from root@apache.org,
> [but] I can't commit my change to README.txt in the source root
> due to an authorization failure.

There were no entries for you in the SVN authentication system.  Looks like
Geir could have done it.  I just read Geir's e-mail regarding accounts.  All
looks in order, so I've done the karma grants.

--- Noel

[ Post a follow-up to this message ]

That did the trick!  Thanks, Noel!

--matthew

>-----Original Message-----
>From: Noel J. Bergman [mailto:noel@devtech.com]
>Sent: Saturday, May 28, 2005 9:29 PM
>To: pmc@incubator.apache.org; matthew.adams@xcalia.com;
>jdo-dev@db.apache.org
>Subject: RE: Trouble authenticating to svn for incubator project jdo...
>
>
>Matthew T. Adams wrote:
> 
>
>There were no entries for you in the SVN authentication
>system.  Looks like
>Geir could have done it.  I just read Geir's e-mail regarding
>accounts.  All
>looks in order, so I've done the karma grants.
>
>	--- Noel
>
>

[ Post a follow-up to this message ]