Description of problem: i am using posgresql 11 on my mageia 8 system which is supported. now on the last updates i got this php-pgsql-8.0.13-1.mga8.x86_64 (due to unsatisfied postgresql-libs[>= 13.5]) at this time i have php-pgsql-8.0.12-1.mga8 which works very well with posgresql 11. Did you change the dependencies without Version change (mageia 8) ? How reproducible: Steps to Reproduce: 1.urpmi.update -a 2.urpmi --auto-select
it is more bad than i thought. a package postgresql-libs[>= 13.5]) doesn't exist. The last version on the repositories is lib64pq5.11-11.13-1.mga8.x86_64.rpm I think this is version 13.1
See https://bugs.mageia.org/show_bug.cgi?id=29655 13.5 is in testing for the moment. You can install them from testing and report if this is OK or not.
CC: (none) => yves.brungard_mageia
I don't understand why updates are issued for a productive release that don't work. I can't test this on productive machines and the updates are for Mageia 8 and not for a development versions ? I hope that after the php updates, queries about postgresql-server 11 will continue to work. Since these are also supported in Mageia 8.
(In reply to Dieter Schütze from comment #3) > I don't understand why updates are issued for a productive release that > don't work. That shouldn't happen, but the PHP updates fixed a potential security issue and will already work for users who don't need postgresql. Maybe that was the reason? > > I can't test this on productive machines and the updates are for Mageia 8 > and not for a development versions ? They are for Mageia 8 > > I hope that after the php updates, queries about postgresql-server 11 will > continue to work. Since these are also supported in Mageia 8. They should. There's also a pending update to postgresql11-server-11.14-1.mga8, new php-pgsql should work with that just as well as before in Mageia 8 Assigning to the php maintainers because I'm not sure. CC'ing some persons with much more understanding of php-pgsql and postgresql and how they work together, than I have.
Assignee: bugsquad => phpCC: (none) => davidwhodgins, mageia, marja11, nicolas.salgueroDepends on: (none) => 29655
We do test all updates, however it is not possible to test all possible combinations of packages. In the case of php, the testing usually consists of the update installing cleanly on the tester's system, and the testing with a few php applications such as phpmyadmin. The regression introduced for php-pgsql was missed, because none of the qa team members involved in it's testing were using postgresql 11 on their systems. You're welcome to join the qa team so regressions affecting your normal usage don't get missed. See https://wiki.mageia.org/en/QA_Team
It all should be fine, after postgres-update is released from testing. The required version of postgres-libs is determined during build process. It is bad luck postgres was updated just the same time, as php was. This code was introduced long ago and this was the first time we hit this. Maybe I can have a look, so we don't need to match the exact version, as it is determined now. This would remove that unneeded hard dependancy.
Bug confirmed even with the updated postgresql11 version. bug 29655#4
Apparently php-pgsql is only expected to work with postgresql13. Closing as invalid since it's the expected behaviour.
Resolution: (none) => INVALIDStatus: NEW => RESOLVED
Everyone can still have/use postgres11 - we just use the latest driver which should still work with old servers and can be installed in parallel.