Looking at rubygem-sinatra-rabbit [1], I wonder if we should not have process for removing "zombie" packages. The issue with this package is that while it keeps building, it is very likely not working. The `%check` suite is disable for ages already. Upstream is dead. I know I could open BZ questioning the utility of such packages and maybe I would get some answer or maybe I would not get any answer. The thing is that if the package was properly maintained, the test suite would not be disabled, the package would be updated to recent packaging standards and what not. But that have not happened past several years. Therefore I doubt I would get any reasonable answer in BZ ticket. Anyway, the process could be like: 1) Open BZ ticket questioning utility of such packages, blocking some "ZOMBIE" tracker. 2) Ask opinion on fedora-devel. 3) If there were no negative responses in the ticket (or some other activity making sure the package is in good shape) for one month, the package would get orphaned. 4) The package could be later collected as orphaned package. I know we have unresponsive maintainer policy, but I don't care much if somebody is responsive or not, I care about specific packages. At the end, if the packages are removed one by one, there won't be need for unresponsive maintainer call. Vít P.S. take the rubygem-sinatra-rabbit just as an example, there are other packages which are in zombie state which I stumble upon now and then. [1] https://src.fedoraproject.org/rpms/rubygem-sinatra-rabbit _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
