#49288: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports' svn: E175013: Access to '/repository/macports' forbidden -----------------------------+--------------------- Reporter: gunnlaugur@… | Owner: admin@… Type: defect | Status: new Priority: High | Milestone: Component: server/hosting | Version: 2.3.4 Resolution: | Keywords: Port: | -----------------------------+--------------------- Changes (by ryandesign@…): * cc: ryandesign@… (added) Old description:
The URL https://svn.macports.org/repository/macports/contrib/restore_ports/restore_p... (and apparently any other URL on that host) responds with a 403 Forbidden.
This gets in the way of the migration procedure described at https://trac.macports.org/wiki/Migration (which probably many people are going through these days after the recent OS X upgrade release)
New description: The URL https://svn.macports.org/repository/macports/contrib/restore_ports/restore_p... (and apparently any other URL on that host) responds with a 403 Forbidden. This gets in the way of the migration procedure described at wiki:Migration (which probably many people are going through these days after the recent OS X upgrade release) -- Comment: It seems access to any part of the repository is now forbidden: {{{ $ svn ls https://svn.macports.org/repository/macports svn: E170013: Unable to connect to a repository at URL 'https://svn.macports.org/repository/macports' svn: E175013: Access to '/repository/macports' forbidden }}} This affects all developers. And unfortunately, due to the recent rsync server problems, the only workaround available was to tell users to switch their MacPorts installations to use the svn server instead of the rsync server, so now those users will also experience errors yet again. Keith said all of the Mac OS Forge infrastructure was rebooted, so perhaps this is related. -- Ticket URL: <https://trac.macports.org/ticket/49288#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X