A pki-core that works with this update is now also in updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4d226a5f7e . With both updates installed, things should work OK. It's unfortunate that the updates are separate, though, as it is possible that pki-core could be pushed stable before resteasy, which would break things for users who don't have updates-testing enabled. Ideally these two updates should be combined, or at least autopush should be disabled for both and the maintainers (gil and mharmsen) should co-ordinate to push both stable at the same time. I've sent a longer more detailed email about this to the relevant folks.
This update has been submitted for testing by gil.
This update has been pushed to testing.
This update prevents freeIPA (CA subsytem) to be installed on F24
Breaks FreeIPA installation on F24.
This update has been obsoleted.
Breaks FreeIPA installation.
It breaks FreeIPA installation.
What is the RESTEasy problem is not listed among the Build / Requires of freeippa ... ?
freeipa indirectly depends on resteasy. But it looks like real bug is in pki-core. https://fedorahosted.org/pki/ticket/2403
/usr/share/java/resteasy/jaxrs-api.jar is no more available please, use instead jboss-jaxrs-2.0-api
The new dogtag has been pushed to updates-testing, can you please respin this package?
This update has been submitted for testing by gil.
This update has been submitted for testing by gil.
gil edited this update.
A pki-core that works with this update is now also in updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2016-4d226a5f7e . With both updates installed, things should work OK. It's unfortunate that the updates are separate, though, as it is possible that pki-core could be pushed stable before resteasy, which would break things for users who don't have updates-testing enabled. Ideally these two updates should be combined, or at least autopush should be disabled for both and the maintainers (gil and mharmsen) should co-ordinate to push both stable at the same time. I've sent a longer more detailed email about this to the relevant folks.
This update has been pushed to testing.
This update has been obsoleted.