Page 1 of 1
SVN with HTTPS (again!!) (SF.net)
Posted: Mon Nov 20, 2006 4:13 am
by Chris Corbyn
Trying to get SwiftMailer into sf.net's SVN repository. Everything works fine except for the usual issue I always get with using SSL connections with subversion. Look at this:
Code: Select all
[d11wtq@pc-cac swiftmailer]$ svn copy trunk/php5 tags/php5/2.1.17
A tags/php5/2.1.17
[d11wtq@pc-cac swiftmailer]$ svn copy trunk/php4 tags/php4/2.1.17
A tags/php4/2.1.17
[d11wtq@pc-cac swiftmailer]$ svn commit tags -m "Taking clean snapshot at 2.1.17"
Adding tags/php4/2.1.17
svn: Commit failed (details follow):
svn: COPY of php4/2.1.17: 502 Bad Gateway (https://swiftmailer.svn.sf.net)
[d11wtq@pc-cac swiftmailer]$ svn commit tags/php5 -m "Taking clean snapshot at 2.1.17"
Adding tags/php5/2.1.17
svn: Commit failed (details follow):
svn: COPY of 2.1.17: 502 Bad Gateway (https://swiftmailer.svn.sf.net)
[d11wtq@pc-cac swiftmailer]$
Am I really doing something wrong? I have never once got "copy" to work with SSL and I find it hard to belive SF.net would use SSL if it didn't work. BUT I have read elsewhere the svn copy doesn't work with SSL since the instructions for dav are turned into normal unecrypted requests and something breaks along the way.
Can anyone help me out here?
Cheers,
d11
Posted: Mon Nov 20, 2006 7:32 am
by Chris Corbyn
I don't get it. Half a day's worth of Googling and loads of people have the same problem. Everything suggests the issue is at the server and not the client. SF have provided SVN access for ages now so I doubt they're still fixing issues considering they've even gone to the extent of creating tools tools to convert your CVS based project into SVN.
The weird thing is that this has happened to me on every linux box I have used SVN from and not just on SF's servers; but only when going over SSL.
I trawled through the SF support tracker and found a fair few people also complaining about this only to be responded to by the usual automated bot. Very frustrating
EDIT | I discovered that you don't need SSL like they say you do on their guide. It works with just http too and voila! It's working fine now

Posted: Mon Nov 20, 2006 10:43 am
by Maugrim_The_Reaper
https://svn.sourceforge.net/svnroot/UNIXNAME
The URI I use for SF when exporting/checking out from a project with HTTPS. Not sure if this is what they set in the docs (I rarely read them) but it definitely works to date. Chances are the SSL is being rejected because of the constantly varying domain from your format...?
Direct link to Swiftmailer's SVN repo:
https://svn.sourceforge.net/svnroot/swiftmailer (works from a browser)
Posted: Mon Nov 20, 2006 5:11 pm
by Chris Corbyn
... and there you have it
Works a peach, thanks.
Posted: Thu Dec 14, 2006 4:43 pm
by Chris Corbyn
Aaaarggghhhh
I've been working with this fine for almost a month and now COPY is failing again. Only this time it's a 403 permission error not a 405 gateway error.
Code: Select all
w3style:~/public_html/swiftmailer d11wtq$ ls
branches tags trunk
w3style:~/public_html/swiftmailer d11wtq$ svn copy trunk/php5 tags/php5/2.1.last
A tags/php5/2.1.last
w3style:~/public_html/swiftmailer d11wtq$ svn commit tags/php5/2.1.last -m "Version 2 going out of development"
Adding tags/php5/2.1.last
svn: Commit failed (details follow):
svn: COPY of 2.1.last: 403 Forbidden (https://svn.sourceforge.net)
w3style:~/public_html/swiftmailer d11wtq$ svn commit --username=d11wtq tags/php5/2.1.last -m "Version 2 going out of development"
Adding tags/php5/2.1.last
svn: Commit failed (details follow):
svn: COPY of 2.1.last: 403 Forbidden (https://svn.sourceforge.net)
w3style:~/public_html/swiftmailer d11wtq$
It happens for MOVE too.
Posted: Thu Dec 14, 2006 4:52 pm
by Chris Corbyn
Oh gimme strength

Turns out they switched the SSL hack for DAV to now use the project subdomain rather than the root svn subdomain. Before it *only* worked on the root svn subdomain.
Working with
https://swiftmailer.svn.sourceforge.net ... wiftmailer now

Posted: Thu Dec 14, 2006 7:50 pm
by Ambush Commander
This is why I don't use SourceForge for source code control.
Posted: Fri Dec 15, 2006 1:42 am
by Chris Corbyn
Ambush Commander wrote:This is why I don't use SourceForge for source code control.
I prefer to have somebody else with all the hardware keeping my code since I'm more likely to lose it knowing me
I should probably set up one of the svn mirroring tool to mirror to the VDS.
On a side note I am getting a new computer today! w00t!
