This morning I woke up to releng orphaning bunch of packages that I maintain.
I have not received any notification about that in advance and I have not seen any reasoning for the orphaning. This looks like a pretty bad behavior.
Can someone explain why and how this has happened.
Affected packages lead to FreeIPA removal: - oddjob - cifs-utils - java-1.8.0-openjdk - augeas - few more Java related
I have not orphaned those via https://pagure.io/releng/issue/9561
I skimmed over my local older copy of https://src.fedoraproject.org/extras/pagure_owner_alias.json
"augeas": [ "lutter", "mdbooth", "apevec" ], "oddjob": [ "abbra", "nalin" ],
See https://pagure.io/find-inactive-packagers/issue/903 and https://pagure.io/find-inactive-packagers/issue/738
I suspect this will be the case for all listed packages. It was communicated on the devel announce list.
I found https://pagure.io/fedora-infrastructure/issue/11271
This is weird. from koji list-history
Wed Apr 26 08:32:53 2023 package owner changed for oddjob in f39 by bodhi owner.name: nalin -> orphan Wed Apr 26 11:07:04 2023 package owner changed for oddjob in f38 by bodhi owner.name: nalin -> abbra
The latter change is mine -- I picked it back to avoid orphaning.
Yet, this looks like a bug in the inactive packagers' processing. A script should not switch the package to orphaned if an inactive packager is removed but there are still packagers to maintain the package.
It might be in owner-sync script on the bodhi side. I am looking into it.
This was https://pagure.io/fedora-infrastructure/issue/11271 ie, the fesco approved policy about inactive package maintainers.
Sorry it came as a surprise. ;(
Metadata Update from @kevin: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)