Re: Problem: Google Code SSL certificates
Yet more info: Please 'star' this issue at Google Code if you're experiencing the problem in Versions: http://code.google.com/p/support/issues/detail?id=3312 The more votes, the more likely they'll be able to give it a higher priority. Thank you all for your patience, - Dirk the Versions team On Nov 24, 9:57 pm, Stratification wrote: > That sounds very much like what I'm seeing and would really explain > its intermittent nature. Thanks for the update, here's to hoping > there's a reasonable fix on the horizon (or Google gets their act > together). > > Aaron > > On Nov 24, 11:59 am, Dirk Stoop wrote: > > > > > Some more info: > > > It seems that people using the command line client, or other > > Subversion clients are also running into this problem (minus the modal > > dialogs of course). > > >http://groups.google.com/group/google-code-hosting/browse_thread/thre.. > > > Apparently Google Code is sending one of two SSL certificates back (at > > random) on every new connection to an https Google Code URL. One of > > these certs is signed by Thawte, one by Google themselves. Every time > > there's a mismatch between a previously accepted certificate for a > > particular URL and one that's being used on a new connection, SVN > > chokes and asks the user to accept the new certificate. > > > Everything seems to point out that this is a problem with Google Code, > > not with Versions or Subversion in general. We're still looking for a > > workaround and ideally for a solution. > > > Like Nick said, turning of working copy badges will help, because > > every time those are refreshed a new connection is made. It won't > > make the problem go away completely, but you'll see a lot fewer > > dialogs. > > > Importing the *.googlecode.com certificate that Google signed > > themselves in your Keychain will not fix the problem, at least it > > doesn't for me; I still get the dialog asking me to accept the > > certificate, the difference is that the dialog claims the certificate > > is set to be trusted (which I just did in Keychain Access) instead of > > untrusted. > > > If anyone here knows someone at or close to Google Code, please ask > > them to take a look at this thread. Any help we can get to clear this > > up would be appreciated. :) > > > Cheers, > > - Dirk > > > the Versions team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Problem: Google Code SSL certificates
That sounds very much like what I'm seeing and would really explain its intermittent nature. Thanks for the update, here's to hoping there's a reasonable fix on the horizon (or Google gets their act together). Aaron On Nov 24, 11:59 am, Dirk Stoop wrote: > Some more info: > > It seems that people using the command line client, or other > Subversion clients are also running into this problem (minus the modal > dialogs of course). > > http://groups.google.com/group/google-code-hosting/browse_thread/thre...http://groups.google.com/group/google-code-hosting/browse_thread/thre... > > Apparently Google Code is sending one of two SSL certificates back (at > random) on every new connection to an https Google Code URL. One of > these certs is signed by Thawte, one by Google themselves. Every time > there's a mismatch between a previously accepted certificate for a > particular URL and one that's being used on a new connection, SVN > chokes and asks the user to accept the new certificate. > > Everything seems to point out that this is a problem with Google Code, > not with Versions or Subversion in general. We're still looking for a > workaround and ideally for a solution. > > Like Nick said, turning of working copy badges will help, because > every time those are refreshed a new connection is made. It won't > make the problem go away completely, but you'll see a lot fewer > dialogs. > > Importing the *.googlecode.com certificate that Google signed > themselves in your Keychain will not fix the problem, at least it > doesn't for me; I still get the dialog asking me to accept the > certificate, the difference is that the dialog claims the certificate > is set to be trusted (which I just did in Keychain Access) instead of > untrusted. > > If anyone here knows someone at or close to Google Code, please ask > them to take a look at this thread. Any help we can get to clear this > up would be appreciated. :) > > Cheers, > - Dirk > > the Versions team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Problem: Google Code SSL certificates
Some more info: It seems that people using the command line client, or other Subversion clients are also running into this problem (minus the modal dialogs of course). http://groups.google.com/group/google-code-hosting/browse_thread/thread/eef9caa43addd401 http://groups.google.com/group/google-code-hosting/browse_thread/thread/f2c77e5da0f6e555 Apparently Google Code is sending one of two SSL certificates back (at random) on every new connection to an https Google Code URL. One of these certs is signed by Thawte, one by Google themselves. Every time there's a mismatch between a previously accepted certificate for a particular URL and one that's being used on a new connection, SVN chokes and asks the user to accept the new certificate. Everything seems to point out that this is a problem with Google Code, not with Versions or Subversion in general. We're still looking for a workaround and ideally for a solution. Like Nick said, turning of working copy badges will help, because every time those are refreshed a new connection is made. It won't make the problem go away completely, but you'll see a lot fewer dialogs. Importing the *.googlecode.com certificate that Google signed themselves in your Keychain will not fix the problem, at least it doesn't for me; I still get the dialog asking me to accept the certificate, the difference is that the dialog claims the certificate is set to be trusted (which I just did in Keychain Access) instead of untrusted. If anyone here knows someone at or close to Google Code, please ask them to take a look at this thread. Any help we can get to clear this up would be appreciated. :) Cheers, - Dirk the Versions team On Nov 24, 6:54 pm, Nick wrote: > I've been seeing this for the past few days. I tried importing the > certs into Keychain and now they show up as "trusted for this user" > when Versions displays them, but it hasn't stopped the popups. > > I had to turn off working copy badges to make it go away. So sad, > because I really depend on those! > > I'm using svn:external to bring in my google code repos. > > Nick > > On Nov 23, 5:08 pm, Paul Lefebvre wrote: > > > > > I also have been seeing this problem the last couple days. I have > > about 4 or 5 Google Groups projects that I've bookmarked. Here's > > hoping to a fix soon; this is driving me crazy! > > > Thanks, > > > -- Paul > > > On Nov 20, 5:38 pm, Dirk Stoop wrote: > > > > Hi Jared, > > > > Thanks for the info. > > > > There seems to be a problem with Subversion and wildcard SSL > > > certificates, which it seems Google has switched to for google code. > > > We're looking into a way around this problem. That's a lot of "it > > > seems"s in one sentence, but that's as much as we know right now. > > > I'll follow up here as soon as we know more. > > > > - Dirk > > > > On Nov 20, 9:45 pm, jared wrote: > > > > > I'm having this problem as well, and my google code project is not set > > > > up as external in another repository. > > > > > Thanks for looking into this! > > > > > On Nov 20, 2:48 pm, Dirk Stoop wrote: > > > > > > Thank you all for the feedback, > > > > > > I think this problem may only happen to people who have authenticated > > > > > google code projects set up as externals in other repositories that > > > > > they've bookmarked. We'll investigate more over here, if any of you > > > > > who are running into this problem don't have any google code externals > > > > > defined, please drop us a line here. > > > > > > Thanks again, > > > > > - Dirk > > > > > > the Versions team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Problem: Google Code SSL certificates
I've been seeing this for the past few days. I tried importing the certs into Keychain and now they show up as "trusted for this user" when Versions displays them, but it hasn't stopped the popups. I had to turn off working copy badges to make it go away. So sad, because I really depend on those! I'm using svn:external to bring in my google code repos. Nick On Nov 23, 5:08 pm, Paul Lefebvre wrote: > I also have been seeing this problem the last couple days. I have > about 4 or 5 Google Groups projects that I've bookmarked. Here's > hoping to a fix soon; this is driving me crazy! > > Thanks, > > -- Paul > > On Nov 20, 5:38 pm, Dirk Stoop wrote: > > > > > Hi Jared, > > > Thanks for the info. > > > There seems to be a problem with Subversion and wildcard SSL > > certificates, which it seems Google has switched to for google code. > > We're looking into a way around this problem. That's a lot of "it > > seems"s in one sentence, but that's as much as we know right now. > > I'll follow up here as soon as we know more. > > > - Dirk > > > On Nov 20, 9:45 pm, jared wrote: > > > > I'm having this problem as well, and my google code project is not set > > > up as external in another repository. > > > > Thanks for looking into this! > > > > On Nov 20, 2:48 pm, Dirk Stoop wrote: > > > > > Thank you all for the feedback, > > > > > I think this problem may only happen to people who have authenticated > > > > google code projects set up as externals in other repositories that > > > > they've bookmarked. We'll investigate more over here, if any of you > > > > who are running into this problem don't have any google code externals > > > > defined, please drop us a line here. > > > > > Thanks again, > > > > - Dirk > > > > > the Versions team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Versions unusable because too many crashes
Versions is working nicely again, thanks for the help! On Nov 24, 1:01 pm, Quinn Taylor wrote: > Only in the sense that they will not be readable by an earlier SVN client. > (It won't actually modify the working copy, it's a version compatibility > issue.) > - Quinn > > On Nov 24, 2009, at 12:24 AM, tim wrote: > > > > > but wait... if I go back to svn 1.5.x, won't this mess with my > > existing working copies? > > > On Nov 24, 9:17 am, tim wrote: > >> yep, I'm on svn 1.6.5! > > >> I'll try reverting to 1.5 and see what's happening then... > > >> thanks! > > >> On Nov 23, 1:54 pm, oltbaba wrote: > > >>> Which Subversion Version are you using? > >>> In our Team (3 People) two persons can use Versions (running > >>> Subversion v1.4.x & v1.5.x) > > >>> Our new team member runs subversion v1.6.5, with this subversion the > >>> Versions app crashes on start-up. > >>> Anybody experiences the same problems with newer subversion version (= > >>> 1.6.5)? > > > > > > smime.p7s > 4KViewDownload --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Removing 'Open Repository URL' from context menu
On Nov 20, 6:38 am, Dan Fairs wrote: > I've therefore uninstalled Versions, but I notice I've still > got the 'Open Repository URL' option in my context menu. > How do I remove that? I also have not been able to figure out how to remove the "Open Repository URL" service entry completely. However, I think you can remove it from the Services context menu by unchecking the entry for it under "Services" in System Preferences > Keyboard > Keyboard Shortcuts I guess until I figure out more about the entire "Services" menu on a Mac that's the best I'll be able to do. -irrational john --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Versions not starting
Since Versions uses SVN libraries contained within its application bundle, you can only choose 1.6.5. I should clarify that I was talking about using Versions with later versions of the command-line tools — I did no upgrade the SVN within Versions, it remains at 1.6.5 regardless of the version of other tools. On Nov 24, 2009, at 4:25 AM, tim wrote: > > Hi Quinn, > > How do you make Versions work with subversion 1.6.6? > I have 1.6.6 installed, but can't select it in Versions preferences > > thanks, > tim. > > On Nov 23, 5:14 pm, Quinn Taylor wrote: >> I'll be a contrary example. Versions works flawlessly for me on Snow Leopard >> with SVN 1.6.5, and on other machines with custom 1.6.6 binaries installed. >> - Quinn >> >> On Nov 23, 2009, at 4:56 AM, oltbaba wrote: >> >> >> >>> Which subversion version are you using? >>> We are experiencing problems with subversion (1.6.5). >>> Although older version are working (1.4.x. and 1.5.x). >> >> >> >> smime.p7s >> 4KViewDownload > --~--~-~--~~~---~--~~ > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versions@googlegroups.com > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/versions?hl=en > -~--~~~~--~~--~--~--- > smime.p7s Description: S/MIME cryptographic signature
Re: Versions not starting
Hi Quinn, How do you make Versions work with subversion 1.6.6? I have 1.6.6 installed, but can't select it in Versions preferences thanks, tim. On Nov 23, 5:14 pm, Quinn Taylor wrote: > I'll be a contrary example. Versions works flawlessly for me on Snow Leopard > with SVN 1.6.5, and on other machines with custom 1.6.6 binaries installed. > - Quinn > > On Nov 23, 2009, at 4:56 AM, oltbaba wrote: > > > > > Which subversion version are you using? > > We are experiencing problems with subversion (1.6.5). > > Although older version are working (1.4.x. and 1.5.x). > > > > smime.p7s > 4KViewDownload --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Versions unusable because too many crashes
Only in the sense that they will not be readable by an earlier SVN client. (It won't actually modify the working copy, it's a version compatibility issue.) - Quinn On Nov 24, 2009, at 12:24 AM, tim wrote: > > but wait... if I go back to svn 1.5.x, won't this mess with my > existing working copies? > > > > On Nov 24, 9:17 am, tim wrote: >> yep, I'm on svn 1.6.5! >> >> I'll try reverting to 1.5 and see what's happening then... >> >> thanks! >> >> On Nov 23, 1:54 pm, oltbaba wrote: >> >>> Which Subversion Version are you using? >>> In our Team (3 People) two persons can use Versions (running >>> Subversion v1.4.x & v1.5.x) >> >>> Our new team member runs subversion v1.6.5, with this subversion the >>> Versions app crashes on start-up. >>> Anybody experiences the same problems with newer subversion version (= >>> 1.6.5)? > --~--~-~--~~~---~--~~ > You received this message because you are subscribed to the Google Groups > "Versions" group. > To post to this group, send email to versions@googlegroups.com > To unsubscribe from this group, send email to > versions+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/versions?hl=en > -~--~~~~--~~--~--~--- > smime.p7s Description: S/MIME cryptographic signature
Re: Problem: Google Code SSL certificates
I also have been seeing this problem the last couple days. I have about 4 or 5 Google Groups projects that I've bookmarked. Here's hoping to a fix soon; this is driving me crazy! Thanks, -- Paul On Nov 20, 5:38 pm, Dirk Stoop wrote: > Hi Jared, > > Thanks for the info. > > There seems to be a problem with Subversion and wildcard SSL > certificates, which it seems Google has switched to for google code. > We're looking into a way around this problem. That's a lot of "it > seems"s in one sentence, but that's as much as we know right now. > I'll follow up here as soon as we know more. > > - Dirk > > On Nov 20, 9:45 pm, jared wrote: > > > > > I'm having this problem as well, and my google code project is not set > > up as external in another repository. > > > Thanks for looking into this! > > > On Nov 20, 2:48 pm, Dirk Stoop wrote: > > > > Thank you all for the feedback, > > > > I think this problem may only happen to people who have authenticated > > > google code projects set up as externals in other repositories that > > > they've bookmarked. We'll investigate more over here, if any of you > > > who are running into this problem don't have any google code externals > > > defined, please drop us a line here. > > > > Thanks again, > > > - Dirk > > > > the Versions team --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Versions unusable because too many crashes
but wait... if I go back to svn 1.5.x, won't this mess with my existing working copies? On Nov 24, 9:17 am, tim wrote: > yep, I'm on svn 1.6.5! > > I'll try reverting to 1.5 and see what's happening then... > > thanks! > > On Nov 23, 1:54 pm, oltbaba wrote: > > > Which Subversion Version are you using? > > In our Team (3 People) two persons can use Versions (running > > Subversion v1.4.x & v1.5.x) > > > Our new team member runs subversion v1.6.5, with this subversion the > > Versions app crashes on start-up. > > Anybody experiences the same problems with newer subversion version (= > > 1.6.5)? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
Re: Versions unusable because too many crashes
yep, I'm on svn 1.6.5! I'll try reverting to 1.5 and see what's happening then... thanks! On Nov 23, 1:54 pm, oltbaba wrote: > Which Subversion Version are you using? > In our Team (3 People) two persons can use Versions (running > Subversion v1.4.x & v1.5.x) > > Our new team member runs subversion v1.6.5, with this subversion the > Versions app crashes on start-up. > Anybody experiences the same problems with newer subversion version (= > 1.6.5)? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~--~~~~--~~--~--~---
