Loading Profile...
SVN integration doesn't work, no matter what I've tried.
I admit, this is possibly due to something strange on my end, but I see no way to adequately test that theory. Google searching turns up nothing relevant, and a slow email thread with Tim didn't get me anywhere.
My repositories are created with svn 1.4.4 (Leopard's included binary, I believe). I was a Versions.app beta tester, so a bunch of my repos were inadvertently upgraded with svn 1.5.4 back when they included it without an option. My default svn binary is 1.4.4, but I've also got svn 1.5.4 installed at /usr/local/bin/.
If I simply try to connect to my 1.5.4 repos through Coda, I get nowhere. The sheet always pops up with "Could not retrieve status." Directly after this error, I check ~/Library/Application Support/Coda/SVN Logs/, but there's no content in either of the log files.
I have also tried just creating a brand new repo with the svn 1.4.4 binary, and checking it out directly from the Site setup sheet within Coda. Still no joy. With each trial (with 1.5.4 and with 1.4.4) I have selected the proper path to the binary in the Coda Preferences.
I'd likely be able to get somewhere, if only the log files were actually logging something.
I do still use Versions.app, but I've really been looking forward to getting basic svn functionality working in Coda. The whole "one-window development" thing is really appealing, and it sucks that I can't really do that.
My repositories are created with svn 1.4.4 (Leopard's included binary, I believe). I was a Versions.app beta tester, so a bunch of my repos were inadvertently upgraded with svn 1.5.4 back when they included it without an option. My default svn binary is 1.4.4, but I've also got svn 1.5.4 installed at /usr/local/bin/.
If I simply try to connect to my 1.5.4 repos through Coda, I get nowhere. The sheet always pops up with "Could not retrieve status." Directly after this error, I check ~/Library/Application Support/Coda/SVN Logs/, but there's no content in either of the log files.
I have also tried just creating a brand new repo with the svn 1.4.4 binary, and checking it out directly from the Site setup sheet within Coda. Still no joy. With each trial (with 1.5.4 and with 1.4.4) I have selected the proper path to the binary in the Coda Preferences.
I'd likely be able to get somewhere, if only the log files were actually logging something.
I do still use Versions.app, but I've really been looking forward to getting basic svn functionality working in Coda. The whole "one-window development" thing is really appealing, and it sucks that I can't really do that.
I’m frustrated
4
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Would absolutely LOVE some support on this. Growing discouraged.
I’m extremely frustrated
-
Inappropriate?I'm experiencing the same problems on my end. I too use Versions.app w/ SVN 1.5.4 but have done so successfully alongside Coda SVN for a few months. I didn't start receiving the "Could not retrieve status." warnings until a couple of weeks back. Possibly following the Coda upgrade to 1.6.2?
I have tried redirecting the version of SVN that Coda uses to the default local copy, but no luck.
Sean
I’m blah.
-
Inappropriate?Not exactly the same problem but this might help somebody out there:
I couldn't check out from a secure server (HTTPS) with an autosigned certificate. Coda reports an error in the certificate and doesn't allow you to check out. So I had to open terminal, and do:
svn checkout https://serveraddresshere/folder/
When warned about the certificate:
Error validating server certificate for 'https://servername:443':
....blablabla...
(R)eject, accept (t)emporarily or accept (p)ermanently?
Choose "P" and after checking it out the first time, you'll be able to do it from coda anytime.
I’m lost in the wild...naked and screaming!
-
Inappropriate?Please e-mail our Coda support guys with any SVN issues, so we can start a direct dialog to figure this out. The back and forth troubleshooting is something we're not sure we want to clog up Get Satisfaction with! :)
-
Inappropriate?Thanks for checking into this, Cabel. Sadly, my first email message to support@panic.com was on 12/30/08, with a subject of "Using SVN, getting errors." I've traded about one message per week with Tim, but the last message I received from him was on 1/22. I responded the same day, and even provided SVN credentials so he could test my particular setup (note: I trust Panic that much), but no one has replied since.
I'm not entirely discouraged, but it's really putting a damper on my enjoyment of the product. I WANT TO LOVE IT! :-)
I’m still hopeful
-
Inappropriate?It looks like we lost your message in the shuffle, Jim, and I apologize for that. I had passed your info onto someone more qualified to investigate the issue, and somehow we both neglected to follow up on it. Sorry about that. We'll be in touch soon.
I’m a human blanket.
-
Inappropriate?Many, many thanks, and I look forward to hearing from you. I'm always available to provide any further information to help solve the issue. Lemme know if you need anything.
-
Inappropriate?Add my name to the list of people with this problem, Coda now constantly pops-up 'could not retrieve status'.
I have set the Subversion Tool Path in preferences to: /opt/subversion/bin/svn (SVN ver. 1.5.5)
I changed this as Coda originally complained that the local directory was not under SVN control, everything was working fine for a few days then for no obvious reason it has stopped. I have not had any system updates or changed any settings in this time.
I have several sites configured with remote repositories ie: https://svn.example.com but I also have a local repository at: file:///Users/Shared/svn/myuser neither work any more.
I have tried checking out new working copies with both Cornerstone and from within Coda, it also makes no difference if the working copy is using the 1.4 or 1.5 SVN format.
PS I did have the Versions beta app but removed it as I prefer Cornerstone.
I’m hopeful this will get fixed
-
Inappropriate?Just a quick update to this. I managed to fix mine by downgrading my working copies back down to svn 1.4 format and switched the Subversion preference in Coda back to the original /usr/bin/svn (Leopard's default 1.4.4).
Please see: http://subversion.tigris.org/svn_1.5_...
in particular the section named Working Copy Upgrades and the stuff about working copies being automatically upgraded. I'm no Subversion expert but I'm sure something to do with this is what had me ripping my hair out. Hope this helps someone.
I’m happy one-windowed goodness is back.
1 person says
this solves the problem
-
Inappropriate?I appreciate your contribution, and I'm glad you've got your issue fixed! Sadly, that's not related to what's going on with my machine.
I can actually login to another user account on the same machine, and use Coda to interact with these repositories without error. I've tried various things with editing my $PATH, trashing the preference files for Coda, and everything in between that I could think of. Still no joy.
It's pretty clear there's something not-quite-right in my particular user account on the computer, but it would be nice to know why Coda is the only svn front-end that has a problem with it. Still awaiting assistance from Panic (last email exchange two days ago). -
Inappropriate?Alright, after an enormous amount of time, this issue is fixed for me. The culprit was...
Apparently, somewhere along the way, a previous GUI app for svn had placed a wayward .svn directory into my main ~/Sites folder. Even though I had specified the local site root for each Site as ~/Sites/my_site_name, Coda was completely refusing to do anything because the parent folder had an old .svn directory present.
I can't exactly say Coda is doing the wrong thing. It's good that the software is at least looking one level up, to see if the selected local site root is part of a larger working copy...but it would still have been nice if Coda had given a more adequate check to see if the selected site root stands on its own as a proper working copy. I'm not sure if that's asking too much.
Perhaps I should have checked my ~/Sites folder in the terminal (or at least in the Coda file browser) sooner. I didn't think I needed to, and that's my oversight. I also should have tried checking out svn sites into folders on different parts of the file system. If I'd tried checking out to the Desktop, I'm pretty sure I would have found the problem sooner.
I’m happy as hell
2 people say
this solves the problem
-
Inappropriate?And apparently, I can't solve my own problem. There's no links under my own posts that say "This solves the problem"
EMPLOYEE
EMPLOYEE
