#143 closed defect (fixed)
HTTPS repository checkout "broken"
| Reported by: | olaf.meeuwissen@… | Owned by: | cmlenz |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Infrastructure | Version: | devel |
| Keywords: | Cc: | olaf.meeuwissen@… |
Description
I'm unfortunate enough to be behind a "clueless" firewall and tried checking out using HTTPS. Everything went fine until svn hit the svn:externals property for common in the doc/ directory. As that is set to http://svn.edgewall.org/repos/edgewall/tools/doc my clueless firewall caused the PROPFIND request to fail :-(
I'd appreciate it if this could get fixed, at least on trunk/doc but if possible also on all other places affected.
On a related note, the Babel and Bitten repositories suffer the same fate. Should I file separate tickets for those?
Change History (3)
comment:1 Changed 17 years ago by cmlenz
- Component changed from General to Infrastructure
- Milestone 0.5 deleted
- Status changed from new to assigned
- Version changed from 0.4.3 to devel
comment:2 follow-up: ↓ 3 Changed 17 years ago by cmlenz
- Resolution set to fixed
- Status changed from assigned to closed
Okay, I've changed the URL to point to the HTTPS repos now.
comment:3 in reply to: ↑ 2 Changed 17 years ago by anonymous
Replying to cmlenz:
Okay, I've changed the URL to point to the HTTPS repos now.
Thanks for the quick response and apologies for the late followup. The Genshi repository is fine now but the Babel one still bombs on the external in babel/tags/0.9.0/doc/common but I guess we can live with that.
On a related note, you could also use Subversion's --ignore-externals to work around things, maybe after checking out the common doc module manually.
Dammit, forgot about that. Looks like svn:externals won't support a protocol-less specification until Subversion 1.5, so I'll have to hardcode them to HTTPS, which would work for both cases.
I'll take care of Babel and Bitten (and probably Posterity, too). No need for other tickets.
Thanks for reporting this!