Hi everyone,
I have some updates about the orphaned packages process. Feedback is
always welcome!
=== IMPORTANT REMINDER ===
Please make sure to pay special attention to the orphaned packages
report [1]. There are many more packages there than usual in part due to
nonresponsive maintainer processes. There is also a special note about
Golang packages at the beginning of the report that may impact your
packages.
=== Comps groups ===
Recently, Fedora Atomic image builds broke [2] due to the retirement of
fros that was orphaned and not picked up within six weeks. I suggested
adding a section to this report that lists orphaned packages that are
part of comps groups or that are dependents of packages include in comps
groups to help catch issues like this earlier. If anybody would like to
contribute that change to
releng/scripts/orphaned-packages-process/find_unblocked_orphans.py [3]
(my time to work on this is currently limited) or has other ideas about
preventing issues like this, please chime in.
I believe that occasionally breaking packages ensures that this process
actually fulfills its purpose of removing unmaintained packages from the
distribution, but I obviously don't want to break composes and create
extra work for Releng and QA if these issues can be avoided. There are
ongoing discussions about issues with packages retirements in the releng
tracker [4].
=== Less important updates about the way these reports are processed ===
On 7/28/25 9:36 PM, maxw...@gtmx.me wrote:
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Note that, since I took over the reports a year and a half ago, the
emails have only been sent directly to co-maintainers of the orphaned
packages, not of any of the packages that depend on orphans, due to a
scripting error. I only identified the problem recently, but I have
decided not to fix it yet, as due to the current amount of orphans, I
worry that sending emails with ~300 addresses BCCed will make my email
hosting provider unhappy.
Also, as of last month, I no longer not use the @fedoraproject.org
aliases to send direct copies of the reports and instead query FASJSON
manually for addresses for better reliability and to avoid issues I've
had with rejected emails when using the aliases (although I hope
changing my domain's SPF records will remedy this) [5]. Members of SIG
co-maintainers also receive direct copies of these reports to the emails
they have listed in FAS. I no longer send to the private packaging SIG
mailing lists as these are usually only set up to receive mails from
Bugzilla and reject or moderate other messages.
Feedback about the way the reports are sent is always welcome.
Best,
Maxwell
[1] https://a.gtmx.me/orphans/orphans.txt
[2] https://pagure.io/releng/failed-composes/issue/8412
[3]
https://pagure.io/releng/blob/main/f/scripts/orphaned-packages-process/find_unblocked_orphans.py.
Please apply changes on top of
https://pagure.io/releng/pull-request/12840 to avoid conflicts.
[4] https://pagure.io/releng/issue/11957
[5]
https://git.sr.ht/~gotmax23/fedora-scripts/tree/main/item/get_fas_mail.py
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
