It even migrated python-xmlschema | 1.10.0-1 | jammy/universe | source This was the last missing bit (thanks Corey!).
Furthmore AFAICS it is already in https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html Blocking the transition of python3-pysaml2 | 6.1.0-0ubuntu2 | jammy | all python3-pysaml2 | 7.1.0-0ubuntu2 | jammy-proposed | all That is otherwise ok to go: python-pysaml2 (6.1.0-0ubuntu2 to 7.1.0-0ubuntu2) Migration status for python-pysaml2 (6.1.0-0ubuntu2 to 7.1.0-0ubuntu2): BLOCKED: Rejected/violates migration policy/introduces a regression Issues preventing migration: python3-pysaml2/amd64 in main cannot depend on python3-xmlschema in universe Impossible Depends: python-pysaml2 -> python3-xmlschema/1.10.0-1/amd64 Additional info: 5 days old So it is ready for promotion. And doing so does not change a feature, but it would allow python3-pysaml2 to migrate clearing excuses a bit. Since it isn't on any image I think it can be promoted now (I'll need to ask to be sure I'm not missing a secret roadblock). ** Changed in: python-xmlschema (Ubuntu) Status: New => 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/1953363 Title: [MIR] python-xmlschema, elementpath, importlib-resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elementpath/+bug/1953363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
