[Pkg-postgresql-public] Postgres major version support policy on Debian

Alexander Wirt formorer at debian.org
Fri Oct 10 08:12:22 UTC 2008


Martin Pitt schrieb am Freitag, den 10. Oktober 2008:

> 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".
No of course not. This fails to often. 

> 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 ?
I don't like the idea of having software like postgresql 8.2 in bpo only
(spoken from the sight of a stable user). And if I hear something like "even
if its in experimental" I don't think that we are going the wrong approach. 
Maybe a debian postgresql repository would be better. 

Alex
-- 
Alexander Wirt, formorer at formorer.de 
CC99 2DDD D39E 75B0 B0AA  B25C D35B BC99 BC7D 020A



More information about the Pkg-postgresql-public mailing list