they are minor bugfixes from the privious versions. please mark stable on each arches. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 72576 [details] libpq-7.3.11 patch failure libpq-7.3.11 fails during the patch phase.
i just fixed #2 problem
Looks good now. Out of curiosity, different libpq versions have different SLOTs, but they clash on some header files which makes it impossible to link to a specific version if you already have more than one around, is this intentional?
I was talking with nakano about the whole header files ordeal. Are you referring to collision protection? The actual header files themselves should be linked to a version specific directory (or at least they appear to be?). You can correct me on this if I'm wrong :P.
Yes, they do get linked, in a last-come last-serve fashion (the last emerged libpq takes over, be it an older or newer rev). Problem is when you unmerge the last emerged libpq it all ends up in a broken state. Granted, stuff that's already linked to the libraries won't break, but you won't be able to emerge anything new against postgresql since the header symlinks are then broken. Also if your last emerged libpq is an older rev you'll be linking against an older postgresql protocol, which may not be so great.
7.4.9 and 8.0.4 stable on ppc64. 7.3.* was never marked ppc64 in any way.
Looks good on x86, thanks
sparc stable though i'm not overly happy about the possible b0rkage. try using eselect for libpq, that would be a good solution to the issue i mentioned.
Marked ppc stable.
okay, i've done some testing on amd64: 7.3.11: is not multilib-strict aware, i committed a fix to 7.3.12, so i'd rather mark that one stable 7.4.9: it has the python use flag, but is it actually used? i can't find anything python related in `equery f postgresql`, and the ebuild says: einfo "Python modules was removed from PostgreSQL package." einfo "If you need it, please run \"emerge dev-db/pygresql\"." as this is just cosmetical, i marked it stable nevertheless 8.0.4: same as 7.4.9, marked stable nevertheless
Alpha stable.
mips stable on 7.3.14, 7.4.12, 8.0.7, & 8.1.3.
scratch 8.1.3, it's back in mips unstable. Didn't wanna jump ahead of everyone else :P
It seems is all done...reopen if it's not
