[Pkg-postgresql-public] Dropping postgresql 8.3 for squeeze

Gerfried Fuchs rhonda at deb.at
Wed Dec 30 14:37:03 UTC 2009


	Hi!

 Just a short comment. :)

* Julien Danjou <acid at debian.org> [2009-12-30 14:56:00 CET]:
> >  This is the whole point of this thread: You won't be able to build and
> > run it just fine in Debian because the package won't be there anymore at
> > a certain point in time.
> 
> Removing a package should not impact the built modules source.

 Hmm, right, I see the point in that. Though, this doesn't seem to be
enough for Dimitri - but I guess it would be part of the things he rants
against. :)

> If Python version changes, a binNMU is triggered on affected packages,
> which is damn faster and more efficient than mass filling bug reports.
> Without a line change to the modules sources.
> 
> I do not see why this is not doable for PostgreSQL.

 In this case you have a point. Dimitri though wants every single
postgres version out there in the pool, which just doesn't scale.

 Have fun!
Rhonda



More information about the Pkg-postgresql-public mailing list