Gerfried Fuchs writes:
> that postgresql actually _is_ pretty unique here indeed.
Well, can you say that the kernel package currently in stable,
apparently 2.6.26, is still maintained by its upstream? I guess there's
a debian team able to maintain it independantly?
> And it seems to
> me that (
Stephen Frost writes:
> * Dimitri Fontaine (dfonta...@hi-media.com) wrote:
>> So ideally the extensions packaging should not have to be edited at all
>> and produce binaries for all supported PostgreSQL version. Supported by
>> the debian release which is building the package and by the extension
* Dimitri Fontaine [2009-12-28 16:22:40 CET]:
> Stephen Frost writes:
> > I seriously doubt Debian would be able to properly maintain PG packages
> > after they've been EOL'd upstream.
>
> So do I. I guess some other software ends up in debian stable and
> reaches EOL before debian stable does,
Stephen Frost writes:
> Nah, that's fine, someone else can and will maintain it properly if he's
> not willing to. Of course, I'm curious as to just what extension this
> is, since I might be that 'someone else'.
Well, I'll still be using them as debian packages, so hopefully you will
just have
Gerfried Fuchs writes:
> Erm, the extensions need only to be available for the same set of
> postgres versions we release. Why do we *need* to have the extensions
> available for postgres versions we never released? If you don't mean
> that, why would you upgrade the extensions then when you don'
* Dimitri Fontaine (dfonta...@hi-media.com) wrote:
> So ideally the extensions packaging should not have to be edited at all
> and produce binaries for all supported PostgreSQL version. Supported by
> the debian release which is building the package and by the extension
> itself, of course.
That's
* Gerfried Fuchs (rho...@deb.at) wrote:
> * Dimitri Fontaine [2009-12-28 12:14:25 CET]:
> > PS: I surely do not intend to fix my packages by desuporting 8.3, even
> > if that means they don't get into squeeze when it's labelled
> > stable. Having them hosted outside of debian will be less work and
Luk Claes writes:
> This would not work without rebuilding everything in testing which would
> create a chicken and egg problem: we want to have everything tested and
> build in unstable before migrating it to testing...
Ok. So what you want is automated-without-rebuild packages migration
from un
* Dimitri Fontaine [2009-12-28 12:14:25 CET]:
> This might look strange for the debian project itself but please
> consider that switching a production server from stable to next stable
> seldom means upgrading PostgreSQL alongside. So we *need* to have the
> extensions available for old-major som
9 matches
Mail list logo
