Hello release and security teams, PostgreSQL just announced new microreleases which fix one security issue and several bugs. Details at http://www.postgresql.org/about/news.1289 I already uploaded 8.4.7 and 9.0.3 to unstable with the fixes. I prepared a lenny update in [1] which is ready for upload. I built the binaries in a clean lenny chroot, and confirm that they pass both the upstream and my postgresql-common test suite. [2] is the complete debdiff, [3] the debdiff minus po diff and documentation noise (much easier to read). How do you want me to handle the update for squeeze? 8.3.13 didn't get uploaded to squeeze because it was deemed too late [4], but 8.3.13 was only a normal bug fix update. As this update will go to -security, is that reasonably independent from squeeze itself to upload it now, or do you want me to hold it for now? Thanks, Martin [1] http://people.debian.org/~mpitt/psql/lenny/ [2] http://people.debian.org/~mpitt/psql/lenny/postgresql-8.3_8.3.14-0lenny1.debdiff [3] http://people.debian.org/~mpitt/psql/lenny/postgresql-8.3_8.3.14-0lenny1.debdiff.cleaned [4] http://lists.debian.org/debian-release/2010/12/msg00783.html -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Attachment:
signature.asc
Description: Digital signature