On 25. 01. 22 12:42, Miro Hrončok 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?
This problem might have solved itself. The bugzillas were recently closed due
to Fedora 34 EOL.
Hence, for each package 3 new bugzillas were created (for 35, 36 and 37), and
those are now NEW.
I wonder how many of them will be set to ASSIGNED without any action, how many
will get fixed, and how many will actually pass unnoticed this time, allowing
the packages to be orphaned and hopefully taken by somebody who will fix them.
--
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
