Hi Ben, So are you saying that now we must supply username and password whenever we commit? That seems a little laborious given that we must supply the google generated password each time...
Is there a way to authenticate once, such as when check the code out, then not be required to supply user and password for commit (as was the "old" way)? -= Jason Stewart -= thunderandwalls.com On Fri, Jul 30, 2010 at 11:42 AM, Ben Collins-Sussman <[email protected]>wrote: > That's because about 3 months ago we changed our svn server to only > require credentials on writes, not on reads. Reads are never > challenged, ever, and even passing '--username --password' on the > commandline won't force a read to authenticate; they're just ignored. > :-) > > On Fri, Jul 30, 2010 at 9:59 AM, Jason Stewart <[email protected]> > wrote: > > Hi Ben, > > Yes, it prompts me for a password but it asks for the password for > terminal > > user (treker) and not my google user ([email protected]). Of course, > when > > I enter the password, it fails and gives me the 500 server error. > > If I supply credentials via [email protected] and > > --password=blahblah, the commit works fine. Although, I must note that > prior > > to a few days ago, I was not required to provide credentials when > commiting, > > only when checking out. > > Thanks for your help! > > > > -= Jason Stewart > > -= thunderandwalls.com > > > > > > On Fri, Jul 30, 2010 at 10:54 AM, Ben Collins-Sussman < > [email protected]> > > wrote: > >> > >> OK, but when you 'svn commit' from that same SSL working copy, does it > >> prompt you for a password? Or does it just throw 500? If the latter, > >> can you try putting your password on the commandline too? > >> (--password) > >> > >> On Fri, Jul 30, 2010 at 9:26 AM, Jason Stewart <[email protected]> > >> wrote: > >> > Hi Ben, > >> > Sure thing. Thank you for responding. > >> > Checkout command: > >> > svn checkout https://buddyball.googlecode.com/svn/trunk/buddyball > >> > --username > >> > trekerboy > >> > > >> > (at this point, it does not ask me for my password anymore) > >> > Yes, I've been able to commit for months prior to this. > >> > Any help is appreciated! > >> > > >> > -= Jason Stewart > >> > -= thunderandwalls.com > >> > > >> > > >> > On Fri, Jul 30, 2010 at 10:12 AM, Ben Collins-Sussman > >> > <[email protected]> > >> > wrote: > >> >> > >> >> 1. Can you show us the exact commandline you're typing, and the exact > >> >> response? > >> >> > >> >> 2. Have you been able to commit before? > >> >> > >> >> 3. Are you sure your working copy is https://? Commits only work > >> >> over > >> >> SSL. > >> >> > >> >> > >> >> > >> >> On Thu, Jul 29, 2010 at 9:42 PM, Jason Stewart <[email protected]> > >> >> wrote: > >> >> > I am also having the commit issue (internal 500 error) with my > >> >> > project: http://code.google.com/b/buddyball. > >> >> > > >> >> > I was able to get around the issue by supplying a username and > >> >> > password during commit using [email protected] -- > >> >> > password=abv123. > >> >> > > >> >> > Is there a fix in the works here? > >> >> > > >> >> > Thanks! > >> >> > > >> >> > - Jason > >> >> > > >> >> > On Jul 18, 9:23 am, tumba25 <[email protected]> wrote: > >> >> >> She tested and committed successfully today. > >> >> >> > >> >> >> On 13 Juli, 17:28, Tony Zale <[email protected]> wrote: > >> >> >> > >> >> >> > Please paste the user's full commandline request and response > into > >> >> >> > the > >> >> >> > thread, thanks! > >> >> >> > >> >> >> > On Tue, Jul 13, 2010 at 8:10 AM, tumba25 <[email protected]> > >> >> >> > wrote: > >> >> >> > > Still the same 500 error. > >> >> >> > >> >> >> > > On 12 Juli, 23:07, Tony Zale <[email protected]> wrote: > >> >> >> > > > We made some server-side svn adjustments this morning -- are > >> >> >> > > > you > >> >> >> > > > still > >> >> >> > > > experiencing these issues? > >> >> >> > >> >> >> > > > Thanks! > >> >> >> > > > Tony > >> >> >> > >> >> >> > > > On Mon, Jul 12, 2010 at 8:22 AM, Ryan Chouinard > >> >> >> > > > <[email protected] > >> >> >> > > >wrote: > >> >> >> > >> >> >> > > > > I'm getting similar behavior on my project, although it > >> >> >> > > > > seems > >> >> >> > > > > to be > >> >> >> > > > > intermittent. My situation is a little different as I'm > the > >> >> >> > > > > only user > >> >> >> > > > > committing to the project. Most of the time I get > MKACTIVITY > >> >> >> > > > > errors, > >> >> >> > > > > but occasionally I get CHECKOUT errors during a commit. If > I > >> >> >> > > > > keep > >> >> >> > > > > trying to commit, it will eventually go through. My latest > >> >> >> > > > > commit took > >> >> >> > > > > 12 tries before it finally went through. > >> >> >> > >> >> >> > > > > I've noticed this behavior off and on for about a week > now. > >> >> >> > > > > Does > >> >> >> > > > > anyone have any information about this? > >> >> >> > >> >> >> > > > > On Jul 11, 11:26 am, tumba25 <[email protected]> wrote: > >> >> >> > > > > > We > >> >> >> > > > > > > >> >> >> > > > > > havehttp:// > code.google.com/p/phpbb-sv/hostedatcode.google.com. > >> >> >> > >> >> >> > > > > > I can commit changes without errors, but the second > owner > >> >> >> > > > > > gets "svn: > >> >> >> > > > > > Server sent unexpected return value (500 Internal Server > >> >> >> > > > > > Error) in > >> >> >> > > > > > response to MKACTIVITY request for > >> >> >> > > > > > '/svn/!svn/act/737afc1c-6b04-4e58- > >> >> >> > > > > > ac45-fff6bb27c468'" when she tries to commit anything. > >> >> >> > >> >> >> > > > > -- > >> >> >> > > > > You received this message because you are subscribed to > the > >> >> >> > > > > Google > >> >> >> > > Groups > >> >> >> > > > > "Project Hosting on Google Code" group. > >> >> >> > > > > To post to this group, send email to > >> >> >> > > [email protected]. > >> >> >> > > > > To unsubscribe from this group, send email to > >> >> >> > > > > > >> >> >> > > > > > >> >> >> > > > > [email protected]<google-code-hosting%[email protected]> > <google-code-hosting%[email protected]<google-code-hosting%[email protected]> > > > >> >> >> > > > >> >> >> > > > >> >> >> > > <google-code-hosting%[email protected]<google-code-hosting%[email protected]> > <google-code-hosting%[email protected]<google-code-hosting%[email protected]> > > > >> >> >> > >> >> >> > > > > . > >> >> >> > > > > For more options, visit this group at > >> >> >> > > > >http://groups.google.com/group/google-code-hosting?hl=en. > >> >> >> > >> >> >> > > -- > >> >> >> > > You received this message because you are subscribed to the > >> >> >> > > Google > >> >> >> > > Groups > >> >> >> > > "Project Hosting on Google Code" group. > >> >> >> > > To post to this group, send email to > >> >> >> > > [email protected]. > >> >> >> > > To unsubscribe from this group, send email to > >> >> >> > > > >> >> >> > > > >> >> >> > > [email protected]<google-code-hosting%[email protected]> > <google-code-hosting%[email protected]<google-code-hosting%[email protected]> > > > >> >> >> > > . > >> >> >> > > For more options, visit this group at > >> >> >> > >http://groups.google.com/group/google-code-hosting?hl=en. > >> >> > > >> >> > -- > >> >> > You received this message because you are subscribed to the Google > >> >> > Groups "Project Hosting on Google Code" group. > >> >> > To post to this group, send email to > >> >> > [email protected]. > >> >> > To unsubscribe from this group, send email to > >> >> > [email protected]<google-code-hosting%[email protected]> > . > >> >> > For more options, visit this group at > >> >> > http://groups.google.com/group/google-code-hosting?hl=en. > >> >> > > >> >> > > >> >> > >> >> -- > >> >> You received this message because you are subscribed to the Google > >> >> Groups > >> >> "Project Hosting on Google Code" group. > >> >> To post to this group, send email to > >> >> [email protected]. > >> >> To unsubscribe from this group, send email to > >> >> [email protected]<google-code-hosting%[email protected]> > . > >> >> For more options, visit this group at > >> >> http://groups.google.com/group/google-code-hosting?hl=en. > >> >> > >> > > >> > -- > >> > You received this message because you are subscribed to the Google > >> > Groups > >> > "Project Hosting on Google Code" group. > >> > To post to this group, send email to > >> > [email protected]. > >> > To unsubscribe from this group, send email to > >> > [email protected]<google-code-hosting%[email protected]> > . > >> > For more options, visit this group at > >> > http://groups.google.com/group/google-code-hosting?hl=en. > >> > > >> > >> -- > >> You received this message because you are subscribed to the Google > Groups > >> "Project Hosting on Google Code" group. > >> To post to this group, send email to > [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]<google-code-hosting%[email protected]> > . > >> For more options, visit this group at > >> http://groups.google.com/group/google-code-hosting?hl=en. > >> > > > > -- > > You received this message because you are subscribed to the Google Groups > > "Project Hosting on Google Code" group. > > To post to this group, send email to > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]<google-code-hosting%[email protected]> > . > > For more options, visit this group at > > http://groups.google.com/group/google-code-hosting?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-code-hosting%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
