Okay, thank you. Retired the package in rawhide and orphaned the
package. If the removal should be required also in stable releases, I
would have to take it again. It would be a part of f38 as it is now
sadly, should it be removed even when it is already in the final freeze?
I am not sure how much severe is the license problem. Should all stable
branches get it retired too? Should complete removal [1] apply to this
package?
1.
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#complete_removal
On 3/13/23 08:31, Florian Weimer wrote:
* Petr Menšík:
Is it enough if I orphan that package? Is there any guidance where
existing package is found to have licensing problem, how should it be
solved? Should something be done to the stable branches also? Should
it be retired from all stable branches as well? How should I proceed
in this case?
I think you should retire it from rawhide at least because it will fail
to build after the C99 transition for Fedora 40 anyway.
As far as I understand it, Fedora still has permission to distribute, we
just don't like the license, so no special action is required from a
licensing perspective. Neither Fedora Legal nor the packaging committee
request removal in such cases or carry it out themselves. At most, a
bug will be filed, but if the maintainer ignores it, basically nothing
happens.
Thanks,
Florian
--
Petr Menšík
Software Engineer, RHEL
Red Hat, https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
