pgpool2_3.1.3-3~bpo60+1_amd64.changes ACCEPTED into squeeze-backports
Accepted:
libpgpool-dev_3.1.3-3~bpo60+1_amd64.deb
to main/p/pgpool2/libpgpool-dev_3.1.3-3~bpo60+1_amd64.deb
libpgpool0_3.1.3-3~bpo60+1_amd64.deb
to main/p/pgpool2/libpgpool0_3.1.3-3~bpo60+1_amd64.deb
pgpool2_3.1.3-3~bpo60+1.debian.tar.gz
to main/p/pgpool2/pgpool2_3.1.3-3~bpo60+1.debian.tar.gz
pgpool2_3.1.3-3~bpo60+1.dsc
to main/p/pgpool2/pgpool2_3.1.3-3~bpo60+1.dsc
pgpool2_3.1.3-3~bpo60+1_amd64.deb
to main/p/pgpool2/pgpool2_3.1.3-3~bpo60+1_amd64.deb
pgpool2_3.1.3.orig.tar.gz
to main/p/pgpool2/pgpool2_3.1.3.orig.tar.gz
postgresql-8.4-pgpool2_3.1.3-3~bpo60+1_amd64.deb
to main/p/pgpool2/postgresql-8.4-pgpool2_3.1.3-3~bpo60+1_amd64.deb
postgresql-9.1-pgpool2_3.1.3-3~bpo60+1_amd64.deb
to main/p/pgpool2/postgresql-9.1-pgpool2_3.1.3-3~bpo60+1_amd64.deb
Changes:
pgpool2 (3.1.3-3~bpo60+1) squeeze-backports; urgency=low
.
* Rebuild for squeeze-backports.
* Bump postgresql-server-dev-all B-D to >= 130~bpo60+2 to pull in bpo's
current list of supported postgresql versions.
.
pgpool2 (3.1.3-3) unstable; urgency=low
.
* Remove /etc/pgpool2/pgpool.conf on purge, ucf doesn't do that by itself.
Closes: #674238.
.
pgpool2 (3.1.3-2) unstable; urgency=low
.
* Use ucf to handle /etc/pgpool2/pgpool.conf. Closes: #671359.
Also, try to keep the port number used instead of calling next_free_port
on every upgrade.
.
pgpool2 (3.1.3-1) unstable; urgency=low
.
* New upstream release.
.
pgpool2 (3.1.2-1) unstable; urgency=low
.
* New upstream release.
.
pgpool2 (3.1.1-2) unstable; urgency=low
.
* debian/control.in
- libpgpool0: set Breaks to solve "fails to upgrade from squeeze"
Thanks to Hideki Yamane for the patch. Closes: #657418.
.
pgpool2 (3.1.1-1) unstable; urgency=low
.
* New upstream release. Closes: #646116.
Change the lock method of insert_lock. The previous insert_lock uses row
locking against the sequence relation, but the current one uses row
locking against pgpool_catalog.insert_lock table. The reason is that
PostgreSQL core developers decided to disallow row locking against the
sequence relation to avoid an internal error which it leads. So creating
insert_lock table in all databases which are accessed via pgpool-II
beforehand is required. If does not exist insert_lock table, pgpool-II
locks the insert target table. This behavior is same as pgpool-II 2.2 and
2.3 series.
* Build pgpool-recovery pgpool-regclass pgpool-walrecrunning server modules.
Closes: #630465.
* Build pgpool_adm server module.
* Split libpcp.so into a separate package.
There is already another libpcp in Debian, libpcp3/libpcp3-dev, therefore
we call our packages libpgpool0/libpgpool-dev. We have a file conflict
with /usr/lib/libpcp.{a,so}, so libpgpool-dev conflicts with libpcp3-dev.
As they are already at SONAME 3 while we are at 0, the other package will
not problems with our files in /usr/lib. (The alternative solution of
putting libpcp.so.* in /usr/lib/pgpool2 would require setting RPATH in
several places, which was both unsupported by the current build system
(despite the documentation claiming otherwise) and also pretty ugly.)
.
pgpool2 (3.0.4-1) unstable; urgency=low
.
* New upstream release
* Use format 3.0 (quilt).
Override entries for your package:
libpgpool-dev_3.1.3-3~bpo60+1_amd64.deb - optional libdevel
libpgpool0_3.1.3-3~bpo60+1_amd64.deb - optional database
pgpool2_3.1.3-3~bpo60+1.dsc - source database
pgpool2_3.1.3-3~bpo60+1_amd64.deb - optional database
postgresql-8.4-pgpool2_3.1.3-3~bpo60+1_amd64.deb - optional database
postgresql-9.1-pgpool2_3.1.3-3~bpo60+1_amd64.deb - optional database
Announcing to debian-backports-changes@lists.debian.org
Thank you for your contribution to backports.debian.org archive.
Reply to: