From: | Christoph Berg <cb(at)df7cb(dot)de> |
---|---|
To: | Georges Racinet <gracinet(at)anybox(dot)fr> |
Cc: | pgsql-pkg-debian(at)postgresql(dot)org |
Subject: | Re: pg_rewind |
Date: | 2015-02-16 09:47:09 |
Message-ID: | 20150216094709.GA2985@msg.df7cb.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
Re: Georges Racinet 2015-02-16 <54E1BB68(dot)8020308(at)anybox(dot)fr>
> >> Lastly, the FAQ seems to suggest that apt.p.o is actually downstream of
> >> Debian unstable ("rebuilt"), but I'm not sure to get it right,
> >> especially for stuff that's not part of PostgreSQL releases.
> > That means that the packages on apt.postgresql.org should preferably
> > be in unstable as well, but that's not a hard requirement. You'll have
> > to argue with me if you don't want that, though ;)
> I was just wondering about the workflow (which one should come first)
> and the consequences of Debian's freeze, don't worry :-)
There's also experimental, which works as well. Though for new
packages (not present in jessie anyway), uploading to unstable doesn't
disturb anything freeze-related.
> >> [1] https://github.com/vmware/pg_rewind (has separate branches for 9.3
> >> and 9.4)
> > Hmm that might be a bit of an issue - the source packages usually
> > support several PG versions in parallel, and then there's individual
> > binary packages built from that. But it's not like that's an
> > unsolvable problem.
>
> I'll make a first try with the 9.4 branch, with explicit PG version pinning.
Sounds promising :)
Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/
From | Date | Subject | |
---|---|---|---|
Next Message | Sébastien Lardière | 2015-02-18 09:32:10 | Re: pg-common 9.4-bdr patch |
Previous Message | Georges Racinet | 2015-02-16 09:42:00 | Re: pg_rewind |