Well, that sucks (see below)
I think that for the FDO project, the SVN used in their checkout script was:
https://osgeo.org/svn/fdo *
I'm not sure how many folks are affected, but it's probably a lot.
Bob? Greg? Can we live with breaking the non-"svn.osgeo.org" (wildcard) access, and having any users stuck with this URL manually merge their changes into a fresh checkout from the new location?
Howard, is it an option to leave the /svn/ alias on the svn.osgeo.org site broken (and inaccessible) until end of Monday (meaning that those folks can't check in changes or switch to the new location) and then break the wildcard access at that time, re-enabling the /svn/ alias? I guess we've got GDAL and MapBender to consider here too...
We may want to think about what caused this problem in the first place. I have a feeling it was because of the chaos of the initial changeover. Does SAC need to put a notification procedure in place for projects using the OSGeo infrastructure, or should a post to the SAC mailing list be enough, with a requirement that projects monitor that list?
As an aside, I HATE wildcard DNS, as it leads to this kind of situation, and I will be extremely glad when it's gone.
Jason
________________________________
From: sac-bounces@lists.osgeo.org on behalf of Howard Butler
Sent: Sat 2007-03-03 9:52 PM
To: System Administration Committee Discussion/OSGeo
Subject: Re: [SAC] Subversion vhost migration underway
Jason,
If I switch on the old configuration to support the wildcard, it then
breaks http://svn.osgeo.org/svn/mapguide or http://svn.osgeo.org/svn/fdo
I'm at a loss as to what to do because we're screwed both ways...
support the wildcard and break for the people using the old canonical
URL or don't support the wildcard and break for the people who were
using any old URL. My guess is that subversion sees absolute paths
regardless of the vhost, so /svn/fdo is the same repository on both
vhosts (they are configured differently).
I propose that we break the support for wildcard svn. How many folks
do we imagine this issue might affect?
Input requested...
Howard
On Mar 3, 2007, at 2:31 PM, Jason Birch wrote:
Hi all,
If you are currently using a host other than svn.osgeo.org, please
make sure that you update your local repository to point to the new
location by 5pm CST, Monday.
For instance, if you are using https://osgeo.org/svn/fdo <https://
osgeo.org/svn/fdo> (or mapguide), use the following command:
svn switch --relocate https://osgeo.org/svn/fdo <https://osgeo.org/
svn/fdo> <http:///> http:///> <http://svn.osgeo.org/fdo>
svn.osgeo.org/fdo
(all on one line)
This change is necessary so that we can move away from wildcard
DNS, which is causing considerable problems in managing the
website, and to allow for future separate of SVN and WWW services
onto different servers. If you require extended time to make this
change, please let the SAC mailing list know by email as soon as
possible.
If you are pointing to the svn.osgeo.org host but including /svn/
at the beginning of your path, you do not have to change
immediately, but you are still encouraged to update to the new
canonical URI as soon as possible. e.g.:
svn switch --relocate https://svn.osgeo.org/svn/fdo <https://
svn.osgeo.org/svn/fdo> https://svn.osgeo.org/fdo <https://
svn.osgeo.org/fdo>
Jason
________________________________
From: sac-bounces@lists.osgeo.org on behalf of Howard Butler
Sent: Sat 2007-03-03 6:36 AM
To: System Administration Committee Discussion/OSGeo
Subject: Re: [SAC] Subversion vhost migration underway
I have turned it on long enough for users to do a svn switch. I
propose that we switch it off Monday at 5 pm CST. I think it would
be pretty important that they don't *commit* anything to the old URL,
and only commit to the new URL after they issue the switch. The svn
switch --relocate command below should work fine with the appropriate
substitutions for their URLs.
Howard
On Mar 3, 2007, at 1:49 AM, Jason Birch wrote:
Howard,
Several users were/are taking advantage of the wildcard DNS to
reference the repositories with paths like:
https://osgeo.org/svn/fdo
Is there any way to re-enable that path on the www vhost until
these users get switched over? I misunderstood the impact of the
changes and indicated in my note that these aliases would continue
to work until the wildcard DNS was pulled.
Jason
________________________________
From: sac-bounces@lists.osgeo.org on behalf of Howard Butler
Sent: Fri 2007-03-02 8:20 PM
To: System Administration Committee Discussion/OSGeo
Subject: [SAC] Subversion vhost migration underway
Folks,
I have flipped the switch on the DNS, and the subversion virtual host
migration is underway. The TTL was set to 6 hours a couple of days
ago (after being turned down to 1 day more than a week ago), so the
new DNS should propagate fairly quickly. After some time for DNS to
propagate, we'll flip the switch back on for the repositories.
Note that it is expected that both http://svn.osgeo.org/gdal and
http://svn.osgeo.org/svn/gdal will continue to work as repository
URLs, but the shorter one is the preferred one. At some indefinite
point in the future, we will quit answering to /svn/gdal.
After the repositories are back up, at your leisure you may do:
svn switch --relocate http://svn.osgeo.org/svn/gdal http:///>
<http:///> <http:///>
svn.osgeo.org/gdal
and all should be well.
Howard
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac
<winmail.dat>
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac
_______________________________________________
Sac mailing list
Sac@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/sac
