I would file a bug report with [email protected] Be sure to list the exact steps required to reproduce the error.
Ted Stresen-Reuter On Jun 13, 2009, at 8:38 PM, Watts Martin wrote: > > Okay, I'm sure there's something really obvious I'm missing here... > but I'm missing it. > > The BBEdit 9.2 manual says that if a repository requires > authentication, you can "let Subversion cache your credentials," and > that "this will happen automatically." I've done that. I've been using > this particular repository for a few months. The svn command line app > works with it transparently. TextMate works with it transparently. > Using the "Show Working Copy Status..." command in BBEdit works just > fine. > > But when I try to update the working copy, or an individual file, or > even do a diff with an individual file, I get an "authorization > failed" error in BBEdit's Subversion log: > > ### Saturday, June 13, 2009 12:30:38 PM > > Retrieving Revision Contents > > svn: PROPFIND request failed on '/cardwest/trunk/controllers/ > specials_controller.php' > svn: PROPFIND of '/cardwest/trunk/controllers/ > specials_controller.php': authorization failed (https:// > svn.cardinalwest.webfactional.com) > > What's going on? Do I actually have to add the repository in the > preferences with my username and password, despite what the manual > seems to imply? The error message suggests it may have to do with > properties -- There are svn:ignore properties set on a few files/ > directories. Surely that isn't a problem? > > I've done some Googling and general searching, and can't find anything > that really seems to fix the issue. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" 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/bbedit?hl=en If you have a specific feature request or would like to report a suspected (or confirmed) problem with the software, please email to "[email protected]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
