Figure out for how long a package has been orphaned #14
Labels
No labels
Priority
High
Priority
Low
Priority
Medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
packaging/orphansv2#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As part of the report, we need to figure out when a package was orphaned. The previous script did this by looking at the
date_modifiedfield from the Pagure projects API. I don't like particularly like this approach, since thedate_modifiedfield can be moved forward if another user/group member withadminaccess makes other changes to the project's ACLs after the date/time it was originally orphaned. Also, I'm trying to avoid dealing with the Pagure projects API and instead rely on Koji (which we need to query anyways to figure out whether a package is blocked) and the https://src.fedoraproject.org/extras/ data (see also #10).It looks like we can instead get this data from Koji1. The question is whether we can rely on this data over the Pagure data and how/when the Koji tag package ownership is changed after a package is orphaned. The koji history says the
bodhiuser set the owner, but I'm not sure where that happens. Maybe it's part of the compose process?More investigation is needed.
Figure out for how long as package has been orphanedto Figure out for how long a package has been orphanedThis was basically implemented in
90cf80f417 (diff-10e2dde02).