Hi, The Java maintainers have orphaned most, if not all, of the Java stack in Fedora, in favor of modules: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject... https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... As this change would lead into a lot of retired packages (maven and all that depends on it, like Dogtag), there was a proposal to create a SIG that would take care of these packages. It does not seem to have advanced much for the past month: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/... And it seems unrealistic for the Dogtag and FreeIPA teams to take over all these packages. In the future packages will be able to BuildRequire modules: https://tree.taiga.io/project/modularity-wg/epic/12 but it is not possible yet and there is no ETA. The consequence is that Dogtag will be considered FTBFS as soon as maven and other dependencies are retired. Dogtag will therefore will be retired (along with FreeIPA) if maintenance for the dependencies is not picked up. There does not seem to be a good solution except by moving both Dogtag and FreeIPA to modules (where we could BR: existing modules) before Fedora releng starts to retire our packages. Thoughts? Cheers François
On Mon, Mar 11, 2019 at 03:58:17PM +0100, François Cami wrote:
Hi,
The Java maintainers have orphaned most, if not all, of the Java stack in Fedora, in favor of modules: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject...
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
As this change would lead into a lot of retired packages (maven and all that depends on it, like Dogtag), there was a proposal to create a SIG that would take care of these packages. It does not seem to have advanced much for the past month: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...
And it seems unrealistic for the Dogtag and FreeIPA teams to take over all these packages.
In the future packages will be able to BuildRequire modules: https://tree.taiga.io/project/modularity-wg/epic/12 but it is not possible yet and there is no ETA.
The consequence is that Dogtag will be considered FTBFS as soon as maven and other dependencies are retired. Dogtag will therefore will be retired (along with FreeIPA) if maintenance for the dependencies is not picked up.
There does not seem to be a good solution except by moving both Dogtag and FreeIPA to modules (where we could BR: existing modules) before Fedora releng starts to retire our packages.
Thoughts?
Cheers François
We are already in a module for RHEL 8. I don't perceive any major disadvantage if we have to move to modules in Fedora too. Are there any big reasons, from a user point of view, against moving to modules? Thanks, Fraser
_______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
Here is my take on moving to modules (speaking from dogtag side of things): Pros: * We would be version-focused instead of fedora-release focused [1]* One source for multiple fedora-release [2]* Dogtag's future would be as described in [3] Cons: * Dogtag's CI runs on Travis. Moving into modules would break the CI workflow leading to a major restructure of upstream CI* In addition to official releases via koji/bodhi, we do maintain an official COPR repo (@pki/10.x). This would need to be reconfigured* Dogtag's nightlies run on COPR. This would again need to be reconfigured. Though in future modules MIGHT help us, the effort required to move into modules (and to make it work) is releatively VERY HIGH. [1] https://docs.fedoraproject.org/en-US/modularity/architecture/building/#_modular_package_builds[2 ] https://docs.fedoraproject.org/en-US/modularity/architecture/building/#_building_one_source_for_multiple_releases[3 ] https://i.ibb.co/23nbNWK/module-branching.jpg
Of course, we can move FreeIPA to a module relatively fast in Rawhide. But first we need to understand whether the same is possible for Dogtag.
-- / Alexander Bokovoy Sr. Principal Software Engineer Security / Identity Management Engineering Red Hat Limited, Finland
_______________________________________________ Pki-devel mailing list Pki-devel@redhat.com https://www.redhat.com/mailman/listinfo/pki-devel
participants (3)
-
Dinesh Prasanth Moluguwan Krishnamoorthy -
François Cami -
Fraser Tweedale