Re: [Pkg-postgresql-public] Postgres major version support policy on Debian - Mailing list pgsql-general

From Martin Pitt
Subject Re: [Pkg-postgresql-public] Postgres major version support policy on Debian
Date
Msg-id 20081010074901.GB6886@piware.de
Whole thread Raw
In response to Re: [Pkg-postgresql-public] Postgres major version support policy on Debian  (Martin Pitt <mpitt@debian.org>)
Responses Re: [Pkg-postgresql-public] Postgres major version support policy on Debian  (Gerfried Fuchs <rhonda@deb.at>)
List pgsql-general
Alexander Wirt [2008-10-10  7:02 +0200]:
> > > So a compromise I can live with is to put it back into unstable (or
> > > even just experimental), but never let it propagate to testing. Then
> > > backports.org can do mechanized backports of updates without being

> mechanized? No.

I meant it in the sense of "run a script to create a backport from a
particular testing/unstable release, as opposed to changing any source
package and upload it manually to backports.org". I would very much
assume that this is what currently happens with backports.org. At
least that's how we do backports in Ubuntu, with "backport-source.py
package_name source_release".

I didn't mean "automatically move every -8.2 unstable upload to
-backports", of course.

> Only if they are tested carefully.

Goes without saying.

> And I still don't like this.

--verbose ?

Thanks,

Martin

--
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

pgsql-general by date:

Previous
From: Martin Pitt
Date:
Subject: Re: [Pkg-postgresql-public] Postgres major version support policy on Debian
Next
From: Markus Wanner
Date:
Subject: Re: [Pkg-postgresql-public] Postgres major version support policy on Debian