Dne 17. 09. 20 v 18:29 Kevin Fenzi napsal(a): > On Thu, Sep 17, 2020 at 12:39:28PM +0200, Vít Ondruch wrote: >> 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. > Well, many maintainers don't touch packages that keep working and don't > need updates or bugfixes. That is perfectly fine and I expect that in such cases, the maintainer would step up and responded to BZ, explained situation and intentions, everything would be documented and we could move on. But maintainers also does not touch packages, because the keep building and that is different situation. > So, if we know the package doesn't work, we > should file a bug on it. If not, I am not sure if we should try and > remove such packages. Just out of curiosity, I filed this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1880144 I used to see a lot of similar packages in Ruby land. Nowadays, they are finally gone, because somebody used the non-responsive maintainer policy in the end. But I don't want to use non-responsive maintainer policy, because I think some package does not serve it purpose anymore. Actually, maintaining 200 packages myself, it might happen that some of them are in zombie state. I would not mind if they were called out via this process. Vít
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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
