ratatosk:svn sjan$ svn co http://www.evardsson.com/repos/projects/spdo/ spdo svn: Could not open the requested SVN filesystem
I only became aware of it this morning, and I knew (almost) right away where the problem might lie. I was still able to access the repos via svn (in the internal network) and via file (from the server) but could not access them from http or https. I checked the svn version number and got this:
xxxx spdo # svn --version svn, version 1.5.6 (r36142) compiled Mar 21 2009, 09:44:24 Copyright (C) 2000-2008 CollabNet. Subversion is open source software, see http://subversion.tigris.org/ This product includes software developed by CollabNet (http://www.Collab.Net/). The following repository access (RA) modules are available: * ra_neon : Module for accessing a repository via WebDAV protocol using Neon. - handles 'http' scheme - handles 'https' scheme * ra_svn : Module for accessing a repository using the svn network protocol. - with Cyrus SASL authentication - handles 'svn' scheme * ra_local : Module for accessing a repository on local disk. - handles 'file' scheme
Ok, so this version built on Saturday when I did my latest updates. So, ra_svn works, ra_local works but ra_neon does not. I recalled that neon upgraded from 0.28.3 to 0.28.4 on the same day with the warning:
* Neon has a policy of breaking API across minor versions, this means * that any package that links against neon may be broken after * updating. They will remain broken until they are ported to the * new API. You can downgrade neon to the previous version by doing: * * emerge --oneshot '<net-misc/neon-0.28' * * You may also have to downgrade any package that has already been * ported to the new API.
That shouldn’t be needed (downgrading earlier than 0.28) since everything was working fine with 0.28.3 so, a quick
emerge --oneshot =net-misc/neon-0.28.3
and all is right with the world again.