I bisected the hardy failure on i386 and lpia down to this glibc upgrade: https://launchpad.net/ubuntu/+source/glibc/2.7-10ubuntu8.2
Both postgresql 8.3.21 and 8.3.22 build fine on hardy final, and fail the same way as in comment 9 on a fully upgraded hardy. Downgrading libc6, libc6-dev, and libc6-i686 from 2.7-10ubuntu8.2 to 2.7-10ubuntu8.1 fixes the bug. For cross-checking I built 8.3.22 on current raring i386 successfully, so it's not a general i386 problem, but one with hardy specifically. Perhaps the backport of the security patches to hardy were faulty, or make assumptions that are not true on hardy? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 Status in “postgresql-8.3” package in Ubuntu: Invalid Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: Fix Committed Status in “postgresql-9.1” source package in Oneiric: Fix Committed Status in “postgresql-8.4” source package in Precise: Fix Committed Status in “postgresql-9.1” source package in Precise: Fix Committed Status in “postgresql-9.1” source package in Quantal: Fix Committed Status in “postgresql-9.1” source package in Raring: Fix Released Status in “postgresql-8.3” source package in Hardy: In Progress Bug description: PostgreSQL announced new microreleases some days ago: http://www.postgresql.org/about/news/1430/ As per the standing SRU microrelease exception I would like to update our stable releases with the new versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
