On Tue, Feb 15, 2011 at 10:25:06AM +0100, Victor Stinner wrote:

Le mardi 15 f??vrier 2011 ?? 09:30 +0100, "Martin v. L??wis" a ??crit :

...

I'm going to perform a Debian upgrade of svn.python.org on Friday, between 9:00 UTC and 11:00 UTC. I'll be disabling write access during that time. The outage shouldn't be longer than an hour.

It's time to move to Mercurial! :-)

Never do two upgrades at once! Especially on Fridays! Oleg. -- Oleg Broytman http://phdru.name/ phd@phdru.name Programmers don't die, they just GOSUB without RETURN.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2/15/2011 8:03 AM, Benjamin Peterson wrote:

2011/2/15 Victor Stinner :

...

Le mardi 15 février 2011 à 09:30 +0100, "Martin v. Löwis" a écrit :

...

I'm going to perform a Debian upgrade of svn.python.org on Friday, between 9:00 UTC and 11:00 UTC. I'll be disabling write access during that time. The outage shouldn't be longer than an hour.

It's time to move to Mercurial! :-)

And doubtless there will be times when Mercurial must be upgraded, too...

True, but on those days you just keep committing locally... John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1aqpkACgkQJdeBCYSNAAMW3gCgt/Ea75R/HfKM4KlmGmCmfjtL BBYAoI89GYsxrsa4/Eefifg3i6+Euv+T =Kz3A -----END PGP SIGNATURE-----

Am 17.02.2011 23:19, schrieb Santoso Wijaya:

Speaking of, what is the current status and timeline on the move to Mercurial?

I think it's fair to say that the project currently rests, lacking a project lead. The most recent timeline is that conversion should be completed by PyCon, and, failing that, should start at PyCon. Regards, Martin

On Fri, 18 Feb 2011 08:09:12 +0100 Dirkjan Ochtman wrote:

On Fri, Feb 18, 2011 at 00:17, "Martin v. Löwis" wrote:

...

I think it's fair to say that the project currently rests, lacking a project lead. The most recent timeline is that conversion should be completed by PyCon, and, failing that, should start at PyCon.

It's not exactly resting; I've been pushing around the cvs2svn-converted tags to get them to behave sensibly, and I've been having good discussions with Antoine and Georg about several things we need to hash out in IRC. Sorry I haven't been doing more progress reports here.

But yes, it would be nice if we could actually switch by PyCon, but at the very least there should be a fresh test repo and consensus on most of the workflow issues by PyCon (for those interested who live in Europe, I'm going to be at a hg sprint in Karlsruhe during the PyCon weekend).

Would be nice if at least a simple repo (e.g. peps) got fully migrated as soon as possible. Thanks Antoine.

Am 18.02.2011 14:41, schrieb Dirkjan Ochtman:

On Tue, Feb 15, 2011 at 09:30, "Martin v. Löwis" wrote:

...

I'm going to perform a Debian upgrade of svn.python.org on Friday, between 9:00 UTC and 11:00 UTC. I'll be disabling write access during that time. The outage shouldn't be longer than an hour.

It seems hg is no longer installed on dinsdale, does that have anything to do with this?

Yes, it must have gotten uninstalled during the upgrade. I have now reinstalled it. Please let me know if there is anything else missing. Regards, Martin

On Feb 22, 2011, at 5:43 PM, Nick Coghlan wrote:

On Tue, Feb 15, 2011 at 6:30 PM, "Martin v. Löwis" wrote:

...

I'm going to perform a Debian upgrade of svn.python.org on Friday, between 9:00 UTC and 11:00 UTC. I'll be disabling write access during that time. The outage shouldn't be longer than an hour.

This may have caused some issues with the SVN viewer - I'm currently getting "code" with no syntax highlighting and all leading whitespace stripped when attempting to look at file contents.

I saw the same thing yesterday when viewing with the Chrome browser but it looked fine on Firefox. Later, after restarting the browsers the problem disappeared. I wonder if there was some sort of caching issue. Raymond

On Wed, Feb 23, 2011 at 4:22 PM, "Martin v. Löwis" wrote:

The ViewVC configuration has significantly changed, so I originally tried to adjust the old configuration. I went now the other path of configuring starting with the new configuration template. I may have broken things in the process; if so, please let me know. Post the specific URL that gives troubles.

Seems to be OK now when checking from my home machine - I'll check the misbehaving box again tomorrow. Cheers, Nick. -- Nick Coghlan   |   ncoghlan@gmail.com   |   Brisbane, Australia