Hi, On 12-03-19 11:38, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Grep the list for your FAS name, follow the transitive deps: https://churchyard.fedorapeople.org/orphans-2019-03-11.txt
<snip> I'm sorry but just dropping all the java packages because they have been moved to modules, totally breaking rawhide is simply unacceptable. A solution for this needs to be found and be in place *before* dropping these packages not the otherway around. We are working to make rawhide more stable: https://fedoraproject.org/wiki/Changes/GatingRawhideSinglePackageUpdates https://fedoraproject.org/wiki/Infrastructure_2020/Rawhide_Gating Yet we are going to go ahead with this java package removal and break the world? That is just totally unacceptable. I've filed a FESCo issue requesting FESCo to block this: https://pagure.io/fesco/issue/2104 Regards, Hans p.s. I must admit that I've been too busy with other things to closely follow the whole modularity process. So far most talk has been about BuildRequires, but what about regular Requires, can a package in the base repo have a Requires on a package only available in a module ? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
