Accepted postgresql-15 15.0-2 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 24 Oct 2022 11:30:00 +0200
Source: postgresql-15
Architecture: source
Version: 15.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Changes:
postgresql-15 (15.0-2) unstable; urgency=medium
.
* Add Breaks on dbconfig-common (<< 2.0.22~) which doesn't support the
stricter permissions on the default public schema yet.
* Cherry-pick 4a6de748d3 from upstream to help fix #1021859.
* Mark -doc package as <!nodoc>.
Checksums-Sha1:
06098cf306486f3a6afd3681a33307f2f5cbdef4 3878 postgresql-15_15.0-2.dsc
35559f017784538f05c7ef6a8764b76ac6f92744 22600 postgresql-15_15.0-2.debian.tar.xz
Checksums-Sha256:
3db0294c02c6f3b3b7386a06fbf8dc3426a041e13ef0d91f8de57e80564fabe9 3878 postgresql-15_15.0-2.dsc
039a7f89c197138822ed1f2781a1da5399cfd6a6896d38e4747448a249dfc76c 22600 postgresql-15_15.0-2.debian.tar.xz
Files:
29cebfc28d36b3563e118aa67ad35ef0 3878 database optional postgresql-15_15.0-2.dsc
955be4839d58891addcfdd7a7826463e 22600 database optional postgresql-15_15.0-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmNWeRsACgkQTFprqxLS
p66D4Q//Sm3ihIIkWcZKPUP/TomISmaxUwLT1c8vY1WVGV35MHeggunOZzYWnUlG
JmnqYCfBOkwPY3B1mTU5xRD0R+hYXXUbIcQUh2H5iCnTWO36wB5hiII3hB4dJcr8
KrvuwRE8cD6KA5TE3uSmfFl3eiQWyz3JBgj9Z4ydGzovULxaCiZNxzRncmu07DUb
0J8qRVcoByMRK6Cn3sySs/OAzEkWRlzTmeljGGDqt2jSnseF4u8GCtUZLqHHnnR0
KPW79fAPPjkjW5mDriTcR3xhDtKhIQcHtQoCOLL+YA4X5W1z4g8EXRdM6bp/F8qt
4T7PdwzVOzSANE626IxTKd/lZtzs9+YDriNcN/yCN8xmH3iWYDxhvjR904AFpU/p
VMJiSVIXCmQLeHJP4csBKXN06vjNQLhAEWOB79olZJtSm52jEY8ZaXutTBDx/udr
yVsxv9cseu0iWtB6yakHfqBqpOovy12ymKPdRpLkme7UHpkYEMVQzNJGwKbFn8Hr
Dw0ujC3OZqQl7pZHQ1CdEj+z2jbEP0xbBA1pQwEDtmX7/+gM+fWnOJDRAFIIXSOR
FNn1UY0np0QaQU9ZucMA+rT1JA3s9RgziaUaQd2+dFSe3ha0YACleqXl3m7bAjQz
/9AZ7N4SkpyCg9J52HyHuFlfbG6RPbh6c4SFMRG01TGU0TJQF2s=
=UgB2
-----END PGP SIGNATURE-----
Reply to: