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

Re: 1.13.x and swig-py3

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Thu, 24 Oct 2019 02:46:39 +0000

Nathan Hartman wrote on Wed, Oct 23, 2019 at 01:11:19 -0400:
> James McCoy wrote:
> > FWIW, since we switched to the new release model, I (in my capacity as
> > packager for Debian) basically ignore non-LTS releases. It's easier to
> > ignore them, since I know I only want an LTS release in Debian's
> > release, and would rather not risk getting "stuck" with a non-LTS
> > release when Debian freezes.
> And this is completely okay!
> I use Debian myself. Most Debian packages "lag" behind the latest and
> greatest. The same is true of other stability-oriented OSes. When you
> have 50,000 packages in your repositories and a whole dependency hell
> between them (circular / diamond dependencies, anyone?), you have to
> move forward cautiously. This is where users must decide if they favor
> stability or new features and choose their distro accordingly. It's a
> trade-off.
> Thank you for maintaining the Debian package. It works great!

Nathan, if I understood James correctly, he's saying that he doesn't package
non-LTS releases even for Debian unstable and Debian testing, so users of those
flavours of Debian will only be served LTS versions of Subversion by Debian.
That _is_ noteworthy: those two flavours of Debian normally have little lag behind
upstream. It's only the "stable" flavour that typically (by design) has lag.

The upshot of this is that users of Debian testing/unstable, which are by and
large "low lag" distros, don't get STS releases of Subversion.

James, please correct me if I'm wrong.


Received on 2019-10-24 04:56:38 CEST

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.