Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Alien-SVN CPAN distribution.

Report information
The Basics
Id: 80202
Status: rejected
Priority: 0/
Queue: Alien-SVN
People
Owner: Nobody in particular
Requestors: Steve.Hales [...] garmin.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Mon Oct 15 17:13:12 2012 Steve.Hales [...] garmin.com - Ticket created
Subject: Bad URL passed to RA layer in Alien-SVN-v1.7.3.1
Date: Mon, 15 Oct 2012 21:12:54 +0000
To: "bug-Alien-SVN [...] rt.cpan.org" <bug-Alien-SVN [...] rt.cpan.org>
From: "Hales, Steve" <Steve.Hales [...] garmin.com>
Hi, Today, I upgraded Alien::SVN to 1.7.3.1 for my web app. Now the following script: use SVN::Client; my $svn = new SVN::Client(); $svn->ls( "https://svn.example.com <https://svn.garmin.com>", 'HEAD', 0 ); Reports: Bad URL passed to RA layer: Unrecognized URL scheme for 'https://svn.example.com <https://svn.garmin.com>' I downgraded to 1.6.12.1 and the problem goes away. Am I doing something wrong or is this a bug? Thanks, Steve Show quoted text
________________________________ This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Thank you for your cooperation.
  Fri Oct 26 19:11:39 2012 mschwern [...] cpan.org - Correspondence added
In general, we just repackage the SVN libraries for CPAN. We don't actually work on them. The Subversion project can help you. I'd forward your issue, but they like a lot of personal contact with the reporter. Please contact them directly about your problem. http://subversion.apache.org/issue-tracker.html But I can tell you I believe the problem you're having is because of a change in SVN 1.7 which made their URL checking much, much, much more strict. "https://svn.example.com <https://svn.garmin.com>" is not a valid URL. Previously it might have made a guess, now it will throw an exception. You're going to have to clean up your URLs before you pass them into SVN.
  Fri Oct 26 19:11:41 2012 The RT System itself - Status changed from 'new' to 'open'
  Fri Oct 26 19:11:41 2012 mschwern [...] cpan.org - Status changed from 'open' to 'rejected'