[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn.collab.net scheduled maintenance downtime

From: Mark Phippard <markphip_at_gmail.com>
Date: Sat, 21 Feb 2009 15:22:55 -0500

On Sat, Feb 21, 2009 at 3:12 PM, Arfrever Frehtes Taifersar Arahesis
<arfrever.fta_at_gmail.com> wrote:
> 2009-02-21 20:40:54 Mark Phippard napisaƂ(a):
>> It seems to be back. I pinged our ops team and they restarted Apache.
>> But ultimately, we probably need Mike to login and look at it.
>> He also upgraded the server to 1.6.0-rc2 a few hours before the
>> downtime began and I know he was having some problems due to the new
>> Python 2.4 requirement in SVN. So that may still be factoring in.
>> Was this Python change intentional BTW?
> AFAIK yes.
>> I thought we just wanted to require it for our tests. It seems crazy
>> to me that we would be requiring it for our bindings and other things.
> SQLite 3.4.0 was released on 2007-06-18.
> Python 2.4 was released on 2004-11-30.
> If somebody wants to use the newest versions of Subversion, then he
> shouldn't use too ancient dependencies.

I do not find that answer acceptable. We should strive to support as
many users/platforms as possible and support the oldest dependencies
that do not create a burden. I do not think the burden was great

>> How are we supposed to support RHEL 4?
> Support for particular distributions is the matter of appropriate packagers.

Hence the reason I am asking. I maintain a package for RHEL. How am
I supposed to provide Python bindings? You cannot update the Python
version in RHEL without breaking a lot of the core OS components. We
cannot just push all issues off to the packagers and pretend that
means there is a ready-made solution available for them to use.

Mark Phippard
Received on 2009-02-21 21:23:09 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.