I have experimented with glom a bit and the summary for now is: 1. it also fails in Debian, I filed bug [3] 2. it is a FTBFS regression in release independent to postgres 3. The newer glom 1.32 fails as well, Desktop let me know that it would need the not yet packaged libxml++3.0 4. In a discussion with Desktop it was suggested to push it back from -release to -proposed (if that is possible) or remove the current version from Jammy and let it sync back once Debian uploads a new version 5. Bug [1][2] are currently present in Jammy when rebuilding glom and would break it as well. 6. no reverse dependencies of glom that would be affected $ reverse-depends --release jammy src:glom No reverse dependencies found
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686 [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956709 [3]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001611 ** Bug watch added: Debian Bug tracker #976686 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686 ** Bug watch added: Debian Bug tracker #956709 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956709 ** Bug watch added: Debian Bug tracker #1001611 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001611 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954374 Title: [RM] Remove src:postgresql-13 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glom/+bug/1954374/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
