Bug 326279

Summary:	dev-vcs/colorsvn fails on bad certificate
Product:	Gentoo Linux	Reporter:	Quasimodo <quasi>
Component:	[OLD] Development	Assignee:	Christian Ruppert (idl0r) <idl0r>
Status:	RESOLVED FIXED
Severity:	normal	CC:	xmw
Priority:	High
Version:	unspecified
Hardware:	AMD64
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Quasimodo 2010-06-30 09:08:32 UTC

While checking out a trunk from svn with a bad server cert, svn warns about it, but then it does not print the message with the options to except or dicard. Instead it sits and waits for user input, AFTER which it will show the input options.

subversion 1.6.9 does not have the error.

Reproducible: Always

Steps to Reproduce:
1. Install subversion 1.6.11
2. Checkout from a server with bad cert
3. Wait for the warning message of subversion

Actual Results:  
Subversion will print the information about the bad certificate and waits for user input. After Input it will show the input options for the prior input.

Expected Results:  
Subversion should print the input options before waiting for input.

This is a regressiojn to 1.6.9 where it is working as expected.

A svn trunk with broken server cert could be found at: https://svn.tabos.org/repos/ffgtk/trunk

Comment 1 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2010-07-01 22:18:01 UTC

Does this problem occur with dev-vcs/subversion-1.6.12?
Do you use Neon or Serf? Which version of Neon or Serf?

Comment 2 Quasimodo 2010-07-02 06:03:55 UTC

(In reply to comment #1)
> Does this problem occur with dev-vcs/subversion-1.6.12?
> Do you use Neon or Serf? Which version of Neon or Serf?
> 

Yes, it still occures in subversion-1.6.12.
I use neon-0.29.3, which is the latest stable version for amd64.

Comment 3 Arfrever Frehtes Taifersar Arahesis (RETIRED) gentoo-dev

2010-07-02 22:15:18 UTC

Please report your problem to upstream.
users@subversion.apache.org

Comment 4 Quasimodo 2010-09-04 05:36:04 UTC

Sorry my mistake. Yesterday I had an inspiration and the truth is, that the problem is caused by colorsvn, not svn itself. I usually don't use svn on cli so I didn't realize - or forgot - that I had colorsvn installed on one system.

So, you might close this one as invalid or move it to colorsvn.

Comment 5 Christian Ruppert (idl0r) gentoo-dev

2010-09-16 11:30:49 UTC

Should be fixed in dev-vcs/colorsvn-0.3.2-r2. Thanks!

Comment 6 Quasimodo 2010-09-16 17:35:36 UTC

(In reply to comment #5)
> Should be fixed in dev-vcs/colorsvn-0.3.2-r2. Thanks!
> 

Works for me, thanks