On 25. 01. 22 15:48, Stephen Gallagher wrote:
On Tue, Jan 25, 2022 at 6:43 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
Hello,
during the Fedora 34 development cycle a year ago, I've reported the following
buzgillas about packages that don't install:
https://bugzilla.redhat.com/buglist.cgi?bug_status=ASSIGNED&f1=blocked&f2=blocked&f3=blocked&list_id=12391194&o1=substring&o2=substring&o3=substring&product=Fedora&query_format=advanced&v1=F34FailsToInstall&v2=F35FailsToInstall&v3=F36FailsToInstall
They were set to ASSIGNED by their maintainers but since then, they still don't
install on Fedora 34, Fedora 35 or Fedora 36.
I see no point in keeping such packages in the repositories, yet the policy
does not currently allow to do anything other than keep them.
Should I take some steps, or do we keep building and shipping the broken
packages forever?
Wouldn't this fit under the non-responsive maintainer policy?
Well, the obvious problem with that approach is that the packagers are
otherwise active (at least the majority of them):
Fabian Affolter (5 bugzillas)
Dan Horák (4 bugzillas)
Peter Robinson, Rust SIG, Mukundan Ragavan...
And the non-responsive maintainer policy kinda assumes the maintainers are
generally not interested / responsive.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
