| Summary: | Local SVN on build.eclipse.org | ||
|---|---|---|---|
| Product: | Community | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Stephan Herrmann
I've restarted xinetd and things seem to be happy. hudsonbuild@build:~> svn list svn://localhost/svnroot/tools/org.eclipse.objectteams/ branches/ tags/ trunk/ -M. Thanks indeed, I can access SVN on build again, however, somehow this seems to be a read-only connection? $ svn commit svn: Commit failed (details follow): svn: Authorization failed I can still commit remotely, but changes done locally on build I cannot commit. Is that by intention? (I tried all sorts of things to tell svn about my username) Sorry, to bother again.. Well the only way to commit is via svn+ssh or HTTPs(if your repo is setup for it). I would be really surprised if you were able to commit in the past using just svn as that is for anonymous read only access. Certainly I can commit to my sandbox with with the svn+ssh://localhost syntax. -M. (In reply to comment #3) > Well the only way to commit is via svn+ssh or HTTPs(if your repo is setup for > it). I would be really surprised if you were able to commit in the past using > just svn as that is for anonymous read only access. > > Certainly I can commit to my sandbox with with the svn+ssh://localhost syntax. > > -M. Thanks for clarification. In fact I can't remember exactly how I committed changes made on build. Re-closing, as the original issue is indeed resolved. |