#18666 closed defect (fixed)
Subversion 1.5.5 - --non-interactive option does not work when password stored in OSX keychain
Reported by: | thewoolleyman@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | ports | Version: | 1.7.0 |
Keywords: | svn keychain --non-interactive subversion password | Cc: | thewoolleyman@… |
Port: | subversion |
Description
You used to be able to work around this in 1.4:
Now, however, ANYTIME you do a SVN command from the GUI, it stores the PW in the keychain, which breaks --non-interactive.
This breaks other tools which require on noninteractive svn commands, such as cruisecontrol.rb.
Change History (6)
comment:1 Changed 16 years ago by danielluke (Daniel J. Luke)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 16 years ago by thewoolleyman@…
Great. That variant should help us work around the problem. I wasn't sure if this was a bug in the port or the original svn source, thanks for letting me know.
comment:3 Changed 16 years ago by thewoolleyman@…
Update - These svn tickets look relevant:
http://subversion.tigris.org/issues/show_bug.cgi?id=2789 http://subversion.tigris.org/issues/show_bug.cgi?id=3059 http://subversion.tigris.org/issues/show_bug.cgi?id=3061
comment:4 Changed 16 years ago by thewoolleyman@…
This seems to be the most relevant bug: http://subversion.tigris.org/issues/show_bug.cgi?id=3059
...but things are worse in 1.6, ANY use of gui auth breaks subsequent --non-interactive usage. Will ask on IRC and try to get an answer/status, and whether a new bug should be opened.
comment:5 Changed 16 years ago by thewoolleyman@…
I discussed this on the svn irc with jeremyw (jwhitloc/apache/committer). He verified that this should be handled under bug 3059, and that we will have to wait for svn 1.6 for a fix.
To summarize, the root cause is 1.4 would remember passtype=simple even after use of gui terminal, 1.5 will always replace passtype=keychain on first use of gui terminal. Jeremy says that is the intended behavior in 1.5, the workaround in 1.4 is a bug.
If you want to see this fixed correctly, please file a bug upstream with subversion.
I'm adding a variant (disable_keychain) to the 1.5.6 port (r47374), which should allow you to work around the issue.