ansaurus

Question

Answer 1

A:

First thing that's catching my eye is that the javahl one isn't calling the update on the same directory as the last one:

/Users/david.marr/Documents/Flex Builder 3/AssetLibrary

vs.

/Users/david.marr/Documents/Flex Builder 3/DataService

It could be that there is some other SVN problem underlying and you're just getting a misleading error message. Also, are you sure url https://svn.frogdesign.com/{redacted} is being parsed correct whatnot? "{redacted}" doesn't look like ANT syntax to me, and neither a regular url.

tehmou 2009-12-18 21:48:44

Thanks tehmou,I removed the url from the paste and added {redacted}. I just wasn't sure it was cool to paste my company's svn repo structure. I agree though, the difference is the javahl call. I don't thing there is anything in the build script that would cause that though.

2009-12-18 22:01:29

Oh, sorry, it seems I was restating the obvious then. I just happen to have these issues sometimes when unparsed things are left in the requests :PWith what kind of command do you run the first one? I am only familiar with running ANT scripts from Eclipse or command-line, and it sounds like this working one is executed from somewhere else?

tehmou 2009-12-18 22:23:52

They are both run via a svn_update task. No extra parameters are used to tell one to use command line and one to use javahl. Is this a known issue at all?

2009-12-23 01:33:22

Answer 2

A:

Maybe your command line client is too old, and the server has a versioning constraint on clients allowed to connect? What does svn --version say?

JesperE 2009-12-22 08:04:59

svn, version 1.6.6 (r40053) compiled Oct 22 2009, 14:13:09

2009-12-23 01:31:48

Well, I don't really care which version you use, but the **server** might. You'll want to talk to the server admins about that.

JesperE 2009-12-23 14:00:51

"Rejected Basic challenge" sounds suspiciously like a server attempting to verify that the connected client is new enough.

JesperE 2009-12-23 14:02:15

Hmm,I am running the opencollab svn binaries. Seems like they would be new enough. It's odd because other svn_update tasks are working correctly. Additionally this repo is the same server as the other ones.

2009-12-23 21:36:09

Answer 3

A:

I usually get the Could not authenticate to server: ignored NTLM challenge, rejected Basic challenge error I use svn update in non interactive mode (example: svn update --non-interactive > output.txt) and when my NT or Active Directory password has changed. The way to fix this would be to first run svn update > output.txt which will then prompt you for your password. Once provided, you will get the following

Authentication realm: <http://svnserver:80&gt; SVN Server
Password for 'siacca':
-----------------------------------------------------------------------
ATTENTION!  Your password for authentication realm:

   <http://svnserver:80&gt; SVN Server

can only be stored to disk unencrypted!  You are advised to configure
your system so that Subversion can store passwords encrypted, if
possible.  See the documentation for details.

You can avoid future appearances of this warning by setting the value
of the 'store-plaintext-passwords' option to either 'yes' or 'no' in
'/cygdrive/u/.subversion/servers'.
-----------------------------------------------------------------------
Store password unencrypted (yes/no)? yes

Once this is done (I'm with you, I don't like storing my password unencrypted either, but this is the only way I can run automated nightly svn updates), you should be able to run svn update in non-interactive mode.

Siacca 2010-02-17 16:21:24

ansaurus

tags:

views:

answers:

Why are my svn ant tasks failing?

related questions