2.4.0 uploaded (as requested in security review) with repoze-who support disabled in testing and pushed back to a suggests at runtime.
Please can this MIR be reviewed on this basis. ** Changed in: python-repoze.who (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - [MIR] python-saml2, python-repoze.who, xmlsec1 + [MIR] python-saml2, xmlsec1 ** Description changed: >> python-pysaml2 << Avaliability: In universe Rationale: New dependency for keystone. Security: No CVE's found. Quality assurance: Unit tests executed as part of package build (two xfails). - Dependencies: All in main apart from those identified on this MIR - Standards compliance: OK - Maintenance: Server Team - - >> python-repoze.who << - - Avaliability: In universe - Rationale: Dependency for pysaml2. - Security: No CVE's found. - Quality assurance: Unit tests executed as part of package build. Dependencies: All in main apart from those identified on this MIR Standards compliance: OK Maintenance: Server Team >> xmlsec1 << Avaliability: In universe Rationale: Dependency for pysaml2. Security: Some old CVE's found, all resolved. Quality assurance: Unit tests executed as part of package build. Dependencies: All in main apart from those identified on this MIR Standards compliance: OK Maintenance: Server Team -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-pysaml2 in Ubuntu. https://bugs.launchpad.net/bugs/1407695 Title: [MIR] python-saml2, xmlsec1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pysaml2/+bug/1407695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs