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

Martin Pitt mpitt at debian.org
Mon Jan 11 08:50:36 UTC 2010

Hey Dimitri,

Dimitri Fontaine [2010-01-09 22:01 +0100]:
> Ok, I'm mixing two things here that Gerfried thinks should not be mixed,
> but I think in our context are the same one. Or at least it's how I
> understand the situation after some breathing.

Right, I think Gerfried and the others are speaking about the
migration to different releases (unstable → testing → stable), which
does not, and should not, require any rebuilds.

You are discussing the problem of a transition to a new (set of)
supported PostgreSQL releases, which will require a source package
change and new binary packages. But all of those will _always_ happen
in unstable.

Your goal is to make the transition (second case) as easy as possible,

Does this summarize the current discussion?

> For this to serve the goal of not having to edit the packages because
> all of sudden a major version of PostgreSQL is now deprecated in next
> stable version, we'll need to issue binNMU on existing source
> packages.

This does not work due to packages being versioned (we discussed that
already why this is necessary). Even if you don't have to change
anything else, you will at least need a rebuild of debian/control
(manually or script supported) to produce the new set of
postgresql-foo-X.Y package records. This will change the source

I totally agree that this can be made as easy as possible, but under
the assumption of keeping versioned -X.Y packages binNMUs can't work.

Thank you,

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

More information about the Pkg-postgresql-public mailing list