Comment 15 for bug 1949579
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #15 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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-13.
Worst case in a week I'll file a bug to remove glom once I have a compelling reason out of trying to fix it.
But all of the above being said, postgresql-14 is IMHO ready now.
MIR ready, Dependencies ready, autopkgtests ready \o/
I'd ask the Ubuntu Archive admins to please promote postgresql-14 now.
Once it migrated it will clear many things in excuses, then afterwards we can have a look if we can remove postgresql-13 without further fallout (after glom is resolved).