Possible Bug with "--non-interactive" mode on OS X Leopard

[Garrett Reinard]

Hello All,

I'm in need of some help in confirming a bug.  I encountered a problem today while trying to use svn on a new MacBook Pro running OS X Leopard.

It appears the "--non-interactive" parameter causes "authorization failed" errors when attempting to run svn commands against our repository even when the auth information is already cached.

When I run any of the svn commands without the "--non-interactive" parameter, they work fine with no prompting, etc...  My username/password/server_key are already cached...

My understanding of the "--non-interactive" parameter is that it should only fail out IF prompting is necessary.  In my case, it's not, but the failure still occurs.

Below is a command sequence to reproduce the issue, along with information about the Subversion and OS X versions I'm running.  I should point out that we have been running these commands successfully on Windows XP Pro for quite some time with no issues...  Therefore I believe the issue is most likely specific to this newer OS...

This is somewhat of a blocking issue for myself and the rest of our development team as we are migrating to MacBook Pro's for mobility etc, and we use Maven 2 for our application builds and deployments.  The SVN SCM Provider used by the Maven release plugin uses the "--non-interactive" parameter whenever it executes svn commands.

Any info or help you all could provide would be great.

Thanks very much for your time...

-Garrett 

Example Command Sequence:

First execute this command in some directory (i.e. temp1)

svn checkout https://host/svn/MyProject some_dir

It should complete successfully with no user/password/key prompting at all.  Then execute this command in another directory (temp2):

svn --non-interactive checkout https://host/svn/MyProject some_dir

This will fail complaining that "authorization failed".  Remove the "--non-interactive" parameter and re-run the command.  It will succeed as before with no prompting.

Subversion Version:

garrett-reinards-macbook-pro:~ reinhag$ svn --version

svn, version 1.4.4 (r25188)

   compiled Sep 23 2007, 22:32:34

Copyright (C) 2000-2006 CollabNet.

Subversion is open source software, see http://subversion.tigris.org/

This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.

  - handles 'http' scheme

  - handles 'https' scheme

* ra_svn : Module for accessing a repository using the svn network protocol.

  - handles 'svn' scheme

* ra_local : Module for accessing a repository on local disk.

  - handles 'file' scheme

OS Version: Mac OS X 10.5.1 Build 9B18

[Garrett Reinard]

I forgot to mention...  Our windows svn client is the same version/revision as the Mac OSX client.

Also, the svn server version is 1.4.0 (r21228).

We are currently investigating whether or not running version 1.4.4 server will fix the problem...  It would seem the issue is not simply that the client is 1.4.4 and the server 1.4.0 since the windows client works fine...  but we thought it would be nice to rule that out for sure...

-Garrett

On Dec 14, 2007, at 10:05 AM, Garrett Reinard wrote:

Hello All,

I'm in need of some help in confirming a bug.  I encountered a problem today while trying to use svn on a new MacBook Pro running OS X Leopard.

It appears the "--non-interactive" parameter causes "authorization failed" errors when attempting to run svn commands against our repository even when the auth information is already cached.

When I run any of the svn commands without the "--non-interactive" parameter, they work fine with no prompting, etc...  My username/password/server_key are already cached...

My understanding of the "--non-interactive" parameter is that it should only fail out IF prompting is necessary.  In my case, it's not, but the failure still occurs.

Below is a command sequence to reproduce the issue, along with information about the Subversion and OS X versions I'm running.  I should point out that we have been running these commands successfully on Windows XP Pro for quite some time with no issues...  Therefore I believe the issue is most likely specific to this newer OS...

This is somewhat of a blocking issue for myself and the rest of our development team as we are migrating to MacBook Pro's for mobility etc, and we use Maven 2 for our application builds and deployments.  The SVN SCM Provider used by the Maven release plugin uses the "--non-interactive" parameter whenever it executes svn commands.

Any info or help you all could provide would be great.

Thanks very much for your time...

-Garrett 

Example Command Sequence:

First execute this command in some directory (i.e. temp1)

svn checkout https://host/svn/MyProject some_dir

It should complete successfully with no user/password/key prompting at all.  Then execute this command in another directory (temp2):

svn --non-interactive checkout https://host/svn/MyProject some_dir

This will fail complaining that "authorization failed".  Remove the "--non-interactive" parameter and re-run the command.  It will succeed as before with no prompting.

Subversion Version:

garrett-reinards-macbook-pro:~ reinhag$ svn --version

svn, version 1.4.4 (r25188)

   compiled Sep 23 2007, 22:32:34

Copyright (C) 2000-2006 CollabNet.

Subversion is open source software, see http://subversion.tigris.org/

This product includes software developed by CollabNet (http://www.Collab.Net/).

The following repository access (RA) modules are available:

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.

  - handles 'http' scheme

  - handles 'https' scheme

* ra_svn : Module for accessing a repository using the svn network protocol.

  - handles 'svn' scheme

* ra_local : Module for accessing a repository on local disk.

  - handles 'file' scheme

OS Version: Mac OS X 10.5.1 Build 9B18

[Pete Clark]

I can confirm the same behavior, both with the macports build of svn and with the leopard-native version of svn.

[Garrett Reinard]

Can someone please direct me as to which mailing list I should post  
this bug to?  Would it be the dev mailing list?  Or is there a  
specific method in place for submitting a bug report to the Subversion  
team?

Thanks,
-Garrett


On Dec 17, 2007, at 12:23 PM, Pete Clark wrote:

>
> I can confirm the same behavior, both with the macports build of svn  
> and with
> the leopard-native version of svn.
>
>
> --
> View this message in context: http://www.nabble.com/Possible-Bug-with-%22--non-interactive%22-mode-on-OS-X-Leopard-tp14338652p14373968.html
> Sent from the Subversion Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Ryan Schmidt-23]

On Dec 19, 2007, at 23:28, Garrett Reinard wrote:

> On Dec 17, 2007, at 12:23 PM, Pete Clark wrote:
>
>> I can confirm the same behavior, both with the macports build of  
>> svn and with
>> the leopard-native version of svn.
>
> Can someone please direct me as to which mailing list I should post  
> this bug to?  Would it be the dev mailing list?  Or is there a  
> specific method in place for submitting a bug report to the  
> Subversion team?

http://subversion.tigris.org/project_issues.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Edward Ned Harvey-5]

Some parts of this message have been removed. Learn more about Nabble's security policy.

I didn’t see your thread, 2 months ago.  I recently started a new thread on the same subject.

 

Have you learned anything about this?  I have no answers yet.

 

 

 

 

From: Garrett Reinard [mailto:garrett.reinard@...]
Sent: Friday, December 14, 2007 11:05 AM
To: users@...
Subject: Possible Bug with "--non-interactive" mode on OS X Leopard

 

Hello All,

 

I'm in need of some help in confirming a bug.  I encountered a problem today while trying to use svn on a new MacBook Pro running OS X Leopard.

 

It appears the "--non-interactive" parameter causes "authorization failed" errors when attempting to run svn commands against our repository even when the auth information is already cached.

 

When I run any of the svn commands without the "--non-interactive" parameter, they work fine with no prompting, etc...  My username/password/server_key are already cached...

 

My understanding of the "--non-interactive" parameter is that it should only fail out IF prompting is necessary.  In my case, it's not, but the failure still occurs.

 

Below is a command sequence to reproduce the issue, along with information about the Subversion and OS X versions I'm running.  I should point out that we have been running these commands successfully on Windows XP Pro for quite some time with no issues...  Therefore I believe the issue is most likely specific to this newer OS...

 

This is somewhat of a blocking issue for myself and the rest of our development team as we are migrating to MacBook Pro's for mobility etc, and we use Maven 2 for our application builds and deployments.  The SVN SCM Provider used by the Maven release plugin uses the "--non-interactive" parameter whenever it executes svn commands.

 

Any info or help you all could provide would be great.

 

Thanks very much for your time...

 

-Garrett 

 

 

Example Command Sequence:

 

First execute this command in some directory (i.e. temp1)

 

svn checkout https://host/svn/MyProject some_dir

 

It should complete successfully with no user/password/key prompting at all.  Then execute this command in another directory (temp2):

 

svn --non-interactive checkout https://host/svn/MyProject some_dir

 

This will fail complaining that "authorization failed".  Remove the "--non-interactive" parameter and re-run the command.  It will succeed as before with no prompting.

 

 

Subversion Version:

 

garrett-reinards-macbook-pro:~ reinhag$ svn --version

svn, version 1.4.4 (r25188)

   compiled Sep 23 2007, 22:32:34

 

Copyright (C) 2000-2006 CollabNet.

Subversion is open source software, see http://subversion.tigris.org/

This product includes software developed by CollabNet (http://www.Collab.Net/).

 

The following repository access (RA) modules are available:

 

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.

  - handles 'http' scheme

  - handles 'https' scheme

* ra_svn : Module for accessing a repository using the svn network protocol.

  - handles 'svn' scheme

* ra_local : Module for accessing a repository on local disk.

  - handles 'file' scheme

 

 

OS Version: Mac OS X 10.5.1 Build 9B18

http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_____________________________________________________________________

This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin@... and delete this mail.
_____________________________________________________________________

[Garrett Reinard]

Hi Edward,

The topic was escalated to the dev mailing list and a defect was entered in both the Subversion and Apple bug trackers...

Here is a link to the dev thread: http://www.opensubscriber.com/message/dev@.../8234471.html

I have yet to hear of any resolution to the problem though...  It had something to do with how the Keychain stuff works on Leopard...

In the meantime we have just been building our maven releases on Windows XP running in VMWare fusion...

-Garrett

On Feb 12, 2008, at 11:06 AM, Harvey, Edward wrote:

I didn’t see your thread, 2 months ago.  I recently started a new thread on the same subject.

 

Have you learned anything about this?  I have no answers yet.

 

 

 

 

From: Garrett Reinard [garrett.reinard@...] 
Sent: Friday, December 14, 2007 11:05 AM
To: users@...
Subject: Possible Bug with "--non-interactive" mode on OS X Leopard

 

Hello All,

 

I'm in need of some help in confirming a bug.  I encountered a problem today while trying to use svn on a new MacBook Pro running OS X Leopard.

 

It appears the "--non-interactive" parameter causes "authorization failed" errors when attempting to run svn commands against our repository even when the auth information is already cached.

 

When I run any of the svn commands without the "--non-interactive" parameter, they work fine with no prompting, etc...  My username/password/server_key are already cached...

 

My understanding of the "--non-interactive" parameter is that it should only fail out IF prompting is necessary.  In my case, it's not, but the failure still occurs.

 

Below is a command sequence to reproduce the issue, along with information about the Subversion and OS X versions I'm running.  I should point out that we have been running these commands successfully on Windows XP Pro for quite some time with no issues...  Therefore I believe the issue is most likely specific to this newer OS...

 

This is somewhat of a blocking issue for myself and the rest of our development team as we are migrating to MacBook Pro's for mobility etc, and we use Maven 2 for our application builds and deployments.  The SVN SCM Provider used by the Maven release plugin uses the "--non-interactive" parameter whenever it executes svn commands.

 

Any info or help you all could provide would be great.

 

Thanks very much for your time...

 

-Garrett 

 

 

Example Command Sequence:

 

First execute this command in some directory (i.e. temp1)

 

svn checkout https://host/svn/MyProject some_dir

 

It should complete successfully with no user/password/key prompting at all.  Then execute this command in another directory (temp2):

 

svn --non-interactive checkout https://host/svn/MyProject some_dir

 

This will fail complaining that "authorization failed".  Remove the "--non-interactive" parameter and re-run the command.  It will succeed as before with no prompting.

 

 

Subversion Version:

 

garrett-reinards-macbook-pro:~ reinhag$ svn --version

svn, version 1.4.4 (r25188)

   compiled Sep 23 2007, 22:32:34

 

Copyright (C) 2000-2006 CollabNet.

Subversion is open source software, see http://subversion.tigris.org/

This product includes software developed by CollabNet (http://www.Collab.Net/).

 

The following repository access (RA) modules are available:

 

* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.

  - handles 'http' scheme

  - handles 'https' scheme

* ra_svn : Module for accessing a repository using the svn network protocol.

  - handles 'svn' scheme

* ra_local : Module for accessing a repository on local disk.

  - handles 'file' scheme

 

 

OS Version: Mac OS X 10.5.1 Build 9B18

http://www.patni.com
World-Wide Partnerships. World-Class Solutions. 
_____________________________________________________________________ 

This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netadmin@... and delete this mail. 
_____________________________________________________________________

[jake_hodges]

So, im playing with a workaround on the client side, and we seem to be okay so far.

Buildbot installs the following file:

  /Library/Python/2.5/site-packages/buildbot/slave/commands.py

The string '--non-interactive' appears three times in there.  I removed it from all three places, deleted commands.pyc (at the recommendation of someone who has ever seen Python before), and bounced buildbot.  We're up and running.

No warranties expressed or implied, mind you.  Keep a backup of your commands.py file. :)

If you have the correct credentials, what would update ever interact with you about?  I expect you'd just see the build fail if there were a problem with this.

Jake

--
This message was sent on behalf of jake_hodges@... at openSubscriber.com
http://www.opensubscriber.com/message/users@.../8197745.html

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Karl Fogel-2]

jake_hodges@... writes:
> If you have the correct credentials, what would update ever interact
> with you about?  I expect you'd just see the build fail if there were
> a problem with this.

Update might interact with the user because it encounters a conflict and
wants to know how to merge it.  this will be a 1.5 behavior, it's not
released yet, but those who are testing 1.5 already see it.  See:

http://subversion.tigris.org/svn_1.5_releasenotes.html#interactive-conflict-resolution

There might be other possible interactive behaviors unrelated to authn,
that's just the first one that comes to mind.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...