Re: Debian readline/libedit breakage

From: Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>
To: Markus Wanner <markus(at)bluegap(dot)ch>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Debian readline/libedit breakage
Date: 2011-02-14 10:57:22
Message-ID: AANLkTinJn6_WgqQViqGzJPyTKoj5jZyyheg7yTgwwG1=@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2011/2/14 Markus Wanner <markus(at)bluegap(dot)ch>:
> On 02/14/2011 10:23 AM, Dimitri Fontaine wrote:
>> Hey, wanna join the fun?  That'd be awesome :)
>
> Sure, I'll try to help.  Don't be surprised if that's not too often,
> though.  I currently cannot promise to provide packaging in any kind of
> timely fashion.  :-(
>
>> 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.
>
> That's pretty much what I meant.  I tried to avoid that warning by
> providing a newer version of the postgresql-common package.  However,
> that approach doesn't work well with upgrades from Debian (because then
> you get the warning back).

one way might be to suggest apt-preferences here, I believe.

>
> Another thing I tried was adding support for release candidates.  The
> ability to distribute these as Debian packages could help getting them
> more tested.  However, the "rc" in the version identifier isn't
> currently appreciated by the perl scripts provided.  Anyway, that's
> probably not top priority.
>
> Where do we start?  How would you like to organize this?

First, we must have an agreement here.

Is debian.postgresql.org to host and distribute the debian packages
(and the ubuntu's) linked with readline and openSSL something that we
want and assume ?

So far, it looks like. Before pushing more efforts here, I would like
people who not agree to stand up. Other options exists like a 3rd
party website, but this is not my favorite solution.

>
> (Martin used to have a git branch per distribution and per major
> version.  That quickly gives you lots of branches and lots of only
> slightly different code bases to work on.  Patching (or cherry picking)
> back and forth turned out to be quite a mess.  Ideally I'd envision some
> kind of template system to build all of the variations.  That would make
> the minor differences obvious).

--
Cédric Villemain               2ndQuadrant
http://2ndQuadrant.fr/     PostgreSQL : Expertise, Formation et Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Cédric Villemain 2011-02-14 11:01:53 Re: Scheduled maintenance affecting gitmaster
Previous Message Magnus Hagander 2011-02-14 10:49:01 Re: Scheduled maintenance affecting gitmaster