[Pkg-postgresql-public] Helping with postgresql-8 packaging?

[Stephen Frost]

--nO3oAMapP4dBpMZi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Martin Pitt (mpitt@debian.org) wrote:
> Stephen Frost [2005-04-18 22:22 -0400]:
> > Get sarge released.  There won't be an update to Postgres 8.0 in
> > unstable before sarge is released because of the libpq ABI change
> > (there's another in 8.0.2 aiui, which sucks, but oh well).
>=20
> No, in fact 8.0.2 just fixed what should have been fixed in 8.0.0
> already. I made this SONAME change in advance to be able to install
> 8.0 and 7.4 in parallel.

That's interesting- are you saying that there isn't an SONAME change
between 7.4 and 8.0.2 then?  We should not be making SONAME changes
ourselves unless there is a dire need for it because we'll end up not
being binary-compatible to other distributions then.

> The new architecture will not be put into Sarge, as Stephen already
> explained.

The SONAME change was actually the main reason the release team had an
issue with it.  If that's not being changed then it's not impossible
that they'd allow it and I'd rather not close the door on it.

	Thanks,

		Stephen

--nO3oAMapP4dBpMZi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCZQQkrzgMPqB3kigRAmpRAJ42aC10yYXXDTBU7sj7j1Kf8kFttACfSEOk
bW/5kB0zI79t2vrbQpbBoYI=
=CRPo
-----END PGP SIGNATURE-----

--nO3oAMapP4dBpMZi--