Re: Debian readline/libedit breakage

Markus Wanner <markus(at)bluegap(dot)ch> writes:
> Once upon a time, I started such an approach, see packages.bluegap.ch.
> However, I didn't upgrade these packages for quite some time, because I
> didn't need them anymore for my day job. I received at least two mails
> thanking me for this service. (And judging from the server logs, I'm
> afraid they still use that unmaintained repository).

Hey, wanna join the fun? That'd be awesome :)

>> Now, what I think I would do about the core package is a quite simple
>> backport of them, using Martin's excellent work.
>
> Yeah, I've mostly run into Debian specific compatibility issues (like
> newer debhelper versions and stuff like that).
>
> Another major annoyance might be that (IIRC) postgresql-common has the
> knowledge about which Postgres versions are supported. So you don't
> ever want the Debian package to override the one you are providing.
> However, that means you either need to always be ahead of the Debian
> repo (version wise) or you need to rename that package (to something
> that's easier to your ears, like postgres-common *ducks*)

Well in fact if you install a PostgreSQL version that is not officially
supported in the debian release you're working with, then the script
/usr/share/postgresql-common/supported-versions will output it too.

> But yeah, as long as Debian itself doesn't provide at least the newest
> few major versions still supported upstream, it would certainly make
> sense for the Postgres project to provide its own Debian / Ubuntu
> repositories.

+1 That's a big service to offer to our users.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support