Learn more about these different git repos.
Other Git URLs
The dpm-xrootd package is retired in F33. But instead of closing the FTBFS bug because the package is retired, new comments asking the maintainers to fix it are added to the bug by rel-eng (by some scripted procedure, I guess):
https://src.fedoraproject.org/rpms/dpm-xrootd/commits/f33 https://bugzilla.redhat.com/show_bug.cgi?id=1863449
The package was retired 2020-08-26, and rel-eng added comment on 2020-09-30, 2020-10-04 and again 2020-10-25.
Can you please consider changing the script adding these comments to close the bug if the package i retired instead of adding the "please do something" comment.
I would like to close bugzillas for retired packages automatically, but IIRC others say that they are helpful to remain open in case a package gets uretired :/
Arguably, the bumping is useless here. Maybe it should be recommended to close all the bugzillas manually when a packager retires a package because it is obsoleted by a different one?
Metadata Update from @mohanboddu: - Issue tagged with: medium-gain, medium-trouble, ops
@pingou What do you think of adding, when a package gets retired, unassign all the maintainers and assign the package to orphan user to the bz sync toddler? That should fix this issue and also helps people to find retired/orphaned packages.
orphan
We already have a toddler that run monthly and clean up retired packages: https://pagure.io/fedora-infra/toddlers/blob/master/f/toddlers/plugins/clean_retired_packages.py
It orphans them (if they aren't already orphaned) and removes the co-maintainers (users and groups) if there are any.
Metadata Update from @mohanboddu: - Issue untagged with: ops - Issue tagged with: dev
So, perhaps we should move it to running weekly or even daily?
It takes a little bit of time as it needs to retrieve all the info from PDC (to find out the list of retired packages). weekly would be doable, I'd be favor of every two weeks to start with.
AFAIK the script only orphans packages with all branches retired. I.e. when I would retire a package today (on rawhide), it would only get orphaned in 13 months, once Fedora 33 goes EOL (not even considering EPEL branches in the example).
That is correct, the package needs to be retired on all branches to be processed by this toddler. Otherwise it doesn't know if the package is retired on F33 but still maintained in F32 (or epel8).
Login to comment on this ticket.