Promoted python-pysaml2 and xmlsec1 to main.
** Changed in: python-pysaml2 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: xmlsec1 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Thanks James and Michael, looks good to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407695
Title:
[MIR] python-saml2, xmlsec1
To manage notifications about this bug go to:
https://bugs.launc
OK, xmlsec1 and python-pysaml2 both are fine from a security and
maintainability sense then. Approving both.
** Changed in: python-pysaml2 (Ubuntu)
Status: New => Fix Committed
** Changed in: xmlsec1 (Ubuntu)
Status: New => Fix Committed
** Changed in: python-pysaml2 (Ubuntu)
Michael
I've uploaded a new version of xmlsec1 which detects any failures in the
test suite exection and skips any tests that would fail in offline
environments.
I also had to limit some test execution to openssl only due to the way
the xmlsec1 apps are built in Debian/Ubuntu (openssl only).
**
What's the story with xmlsec1's tests? I remember that failing tests
don't stop the build on that one.
** Changed in: python-pysaml2 (Ubuntu)
Assignee: (unassigned) => Seth Arnold (seth-arnold)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
