On 15-08-2025 12:28, Miro Hrončok wrote:
On 15. 08. 25 12:13, Miro Hrončok wrote:
On 15. 08. 25 9:15, Sandro wrote:
On 14-08-2025 22:27, Miro Hrončok wrote:
On 14. 08. 25 21:35, Sandro wrote:
Unlikely. The reason for orphaning is cleared (or should be) when a
package is picked up by another user. At least that's my experience
using the UI. The API may behave differently.
I think the reason is hidden from the UI but stays in the DB.
Assigning the package to orphan via the "give package to user" then
uncovers the old reason.
That would explain the misleading reason. The question then boils
down to:
Who gave the package away and why?
I suppose only users or scripts with elevated access would be able to
do so.
It look like all the packages from https://pagure.io/releng/
issue/12739 are orphaned now.
That makes me think I must have rerun that action by accident. I still
don't know how or when, but if it was indeed me, I sincerely apologize.
Maybe infra folks might be able to dig the previous owners up?
I've deduced the maintainers from Koji and emailed them.
Thanks for the heads up and for looking into it.
If I take back python-diff-match-patch now, should I take care of the
rebuild for 3.14.0rc2 myself? Or will it be picked up in the next run?
--
Sandro
--
_______________________________________________
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
