Re: PostgreSQL transition ahead

2005-06-08 Thread Andreas Metzler
Martin Pitt <[EMAIL PROTECTED]> wrote: > Andreas Metzler [2005-06-07 20:03 +0200]: >> Martin Pitt <[EMAIL PROTECTED]> wrote: >> [...] >> > I will upload the new packages to unstable very soon. This has a >> > reasonably big impact to all packages that depend/build-depend on >> > PostgreSQL since t

Re: PostgreSQL transition ahead

2005-06-08 Thread Martin Pitt
Hi! Adeodato Simó [2005-06-08 2:36 +0200]: > Do you plan on filing bugs to prevent loosing track of the remaining > uploads? Yes, that's what I'm going to do. > - file bugs against remaining packages after e.g. 2 or 4 weeks. A > bit more of effort, won't create a flood of RC bugs

Re: PostgreSQL transition ahead

2005-06-07 Thread Adeodato Simó
* Martin Pitt [Tue, 07 Jun 2005 10:22:00 +0200]: Hello Martin, > I already did these steps for a fair number of packages. So if you > maintain one of the packages that have a debdiff at [3], you are lucky > and only need to apply the patch there (however, cyrus-sasl2 and > dovecot were nasty case

Re: PostgreSQL transition ahead

2005-06-07 Thread Kurt Roeckx
On Tue, Jun 07, 2005 at 07:24:06PM +0200, Florian Weimer wrote: > * Martin Pitt: > > > (2) PostgreSQL 8.0 brought a new SONAME for libpq (libpq4), which > > removed a few symbols which were only intended for internal use, > > but were used nevertheless by some client apps (like "psql"). >

Re: PostgreSQL transition ahead

2005-06-07 Thread Martin Pitt
Hi! Andreas Metzler [2005-06-07 20:03 +0200]: > Martin Pitt <[EMAIL PROTECTED]> wrote: > [...] > > I will upload the new packages to unstable very soon. This has a > > reasonably big impact to all packages that depend/build-depend on > > PostgreSQL since the package structure changed a bit: > >

Re: PostgreSQL transition ahead

2005-06-07 Thread Martin Pitt
Hi Florian! Florian Weimer [2005-06-07 19:24 +0200]: > * Martin Pitt: > > > (2) PostgreSQL 8.0 brought a new SONAME for libpq (libpq4), which > > removed a few symbols which were only intended for internal use, > > but were used nevertheless by some client apps (like "psql"). > > libp

Re: PostgreSQL transition ahead

2005-06-07 Thread Steinar H. Gunderson
On Tue, Jun 07, 2005 at 07:24:06PM +0200, Florian Weimer wrote: > I assume applications linked to libpq3 should be able to connect to > PostgreSQL 8.0 servers. Is this correct? (According to a few tests, > it is.) It is correct; older protocol versions are supported upstream. /* Steinar */ --

Re: PostgreSQL transition ahead

2005-06-07 Thread Andreas Metzler
Martin Pitt <[EMAIL PROTECTED]> wrote: [...] > I will upload the new packages to unstable very soon. This has a > reasonably big impact to all packages that depend/build-depend on > PostgreSQL since the package structure changed a bit: > (1) postgresql-dev was split into libpq-dev (for client app

Re: PostgreSQL transition ahead

2005-06-07 Thread Florian Weimer
* Martin Pitt: > (2) PostgreSQL 8.0 brought a new SONAME for libpq (libpq4), which > removed a few symbols which were only intended for internal use, > but were used nevertheless by some client apps (like "psql"). > libpq4 can talk to all PostgreSQL servers back to 7.3 (same like >

PostgreSQL transition ahead

2005-06-07 Thread Martin Pitt
(Sorry if you got this mail several times, I just CC'ed it to every affected binary package). Hi fellow Debian developers! Three months ago I announced the first alpha versions of the new architecture of the PostgreSQL packages [1] in experimental. Now, a few months later, they are mature enough