PGLOADER The pgloader issue stays reproducible but unclear. I double checked if this was a regression in release, but without PG-14/PG-common from proposed it continues to work fine.
Debian seems to be affected by the same (at least for subtest ssl) https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pgloader/17321761/log.gz But there it was essentially avoided via migration-reference/0 resetting the expectation. See: https://ci.debian.net/packages/p/pgloader/unstable/amd64/ I'm not sure this was correct, in Debian at the last time of a pass it was PG-13. Then something unrelated broke the ssl test and then migration-reference/0 made it reset expectations and thereby accept PG-14. As outlined above, it seems to be (at least on Ubuntu) a real regression and a recheck with a migration-reference/0 on the real infrastructure confirmed this. We can't get out the same way :-) SQLALCHEMY-I18N The story here is similar, this also works fine with the older version and seems to be a real regression. A no-change migration-reference run confirmed that even on that infrastructure it works fine with the non-proposed set of packages. Since this one can not be reproduced locally (so far) the path still is debugging in a PPA. But currently there is an issue in LP so that builds do not get uploaded stalling this debugging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949579 Title: [MIR] postgresql-14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pgloader/+bug/1949579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
