postgresql-14 | 14.1-1ubuntu1 | jammy | source, amd64, arm64, armhf, ppc64el,
riscv64, s390x
postgresql-common | 234 | jammy | source, all
This is complete.
The cleanup will be getting glom to build as then we can remove
src:postgresql-13 tracked in bug 1954374
** Changed i
pgsql-ogr-fdw@amd64 migration-reference/0 (was auto-scheduled it seems) is bad
as expected.
That should (tm) have been the last blocker.
Maybe I need to check installability in update_output after the next
run, I didn't do so so far ...
--
You received this bug notification because you are a me
python-sqlalchemy-utils fully resolved now
Now excuses lists the amd64 variant of pgsql-ogr-fdw as failing (it didn't
before)
https://autopkgtest.ubuntu.com/packages/p/pgsql-ogr-fdw/jammy/amd64
Here (as on the other architectures) a migration-reference run is running,
assuming that fails like th
Thanks to RAOF the postgresql-server-dev-1 -> llvm issue is resolved.
python-sqlalchemy-utils was a test on an old version 0.36.8-2ubuntu2 failing
when openssl3 migrated. There now is a merge of the new version 0.37.8-1ubuntu1
with new tests.
Migration reference runs with that new version worked
python-sqlalchemy-utils was not shown before, but now is a test fail for
postgresql-common
About the dependency to llvm-11-dev, clang-11.
Two things to know here, first of all that will sooner or later be llvm-13 due
to [1].
But right now there is an issue around s390x that blocks this:
+ERROR:
Thank you,
it seems its llvm-11 dependency (incompatible with 13 on s390x, being worked on
in Debian) still prevents migration to -release. I'll have a more detailed look
tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Override component to main
postgresql-14 14.1-1ubuntu1 in jammy: universe/misc -> main
libecpg-compat3 14.1-1ubuntu1 in jammy amd64: main/libs/optional/100% -> main
libecpg-compat3 14.1-1ubuntu1 in jammy arm64: main/libs/optional/100% -> main
libecpg-compat3 14.1-1ubuntu1 in jammy armhf: main/libs/
sqlalchemy worked out as expected, some tests are still in the queue but
others completed.
** No longer affects: sqlalchemy-i18n (Ubuntu)
--
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:
All other entries on the transition tracker that are left are false
positives AFAICS.
Thereby all that is left I'm aware of is glom, which I found to be an FTBFS
(independent to postgresql-14). The work on glom can continue after
postgresql-14 migrates as we do not immediately remove postgresql-
sqlalchemy was a case of re-debugging, I'll skip all the details, it
essentially is the same as:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997086
That works for us as well, but the version was an FTBFS - on all PPA and local
tests that I had for the tests I used 1.0.1 already - so it shou
Status update:
- Both removals got resolved
- sqlalchemy-i18n still has issues, but seems to be a flaky heisenbug
(any debug I add makes it work fine)
- next to resolve is glom, it still has a dependency to postgresql-13 but it
FTBFS right now.
In Debian [1] it worked to pick up PG-14, both D
Since the MIR Acks is here let us mark this committed to show up
correctly
** Changed in: postgresql-14 (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: postgresql-common (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you ar
Also filed a removal bug against the known-bad multicorn at
https://bugs.launchpad.net/debian/+source/postgresql-multicorn/+bug/1953515
--
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:
[
FYI I created a tracker for postgresql-14
https://people.canonical.com/~ubuntu-archive/transitions/html/postgresql-14.html
--
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] postgres
** Changed in: sqlalchemy-i18n (Ubuntu)
Status: Confirmed => In Progress
--
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 b
After talking with the maintainer and further summarizing the situation I
really think pgloader should be removed for now and come back into jammy later.
I filed bug 1953486 for that removal - removing the pgloader task here as it
now has an own bug.
** No longer affects: pgloader (Ubuntu)
--
Bonus-pain on pgloader - pgloader wasn't updated for ages:
https://launchpad.net/ubuntu/+source/pgloader/3.6.2-1
And the new rebuild (openssl 3) fails on armhf:
https://launchpad.net/ubuntu/+source/pgloader/3.6.2-1build1
--
You received this bug notification because you are a member of Ubuntu
Bu
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/unstabl
Current Autopkgtest-Blockers:
Note: all of those that remain already had "just reruns" from vorlon and
ginggs on their +1 duty, to each of them there must be more :-/
Postgreql-14:
- dovecot
Affects all architectures.
This wasn't really a PG-14 issue. But with the new dovecot 2.3.16 + o
** Changed in: postgresql-common (Ubuntu)
Status: Invalid => In Progress
--
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 b
Some smaller fixes related got uploaded to Ubuntu recently:
- https://launchpad.net/ubuntu/+source/postgis/3.1.4+dfsg-3ubuntu1
- https://bugs.launchpad.net/ubuntu/+source/postgresql-14/+bug/1953128
But all of them still wait on the overall transition to happen.
As usual we waited for the transiti
** Tags removed: server-next
** Tags added: server-todo
--
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.l
Yes, demoting PG-13 is part of the plan to promote this.
Ubuntu-Server is now subscribed to postgresql-14.
** Changed in: postgresql-14 (Ubuntu)
Assignee: Lukas Märdian (slyon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
As in the past, we do not really need a MIR re-review for a version bump
like this, so this is just a formalism:
MIR team ACK
But please add a bug-subscriber (=ubuntu-server) for the new
postgresql-14 package and let's make sure to demote the old
postgresql-13 package before the end of the Jammy
** Changed in: postgresql-common (Ubuntu)
Status: New => Invalid
** Changed in: postgresql-14 (Ubuntu)
Assignee: (unassigned) => Lukas Märdian (slyon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I think we can do the MIR processing on this now, even though the
transition itself might still take a while for the last dependencies to
be ready. Therefore setting state back to NEW.
I'd assume that this is a "yes, just as before but please ensure that
PG-13 is removed before end of cycle". But
26 matches
Mail list logo
