It is hard to track changes in pagure_owner_alias.json from https://src.fedoraproject.org/extras/, because the generated JSON has no order.
pagure_owner_alias.json
<img alt="Screenshot_from_2021-12-30_00-38-40.png" src="/fedora-infrastructure/issue/raw/files/2563b1217fb7ca708a61e22d61bbf93739e00a88e41cf47cc40809ab45dee9f0-Screenshot_from_2021-12-30_00-38-40.png" />
Well, the files there are not meant for human consumption at all. Could you expand a little on what you are trying to do?
I've got an old copy in static packages build and was curious how the data changes over time.
Hello! This change needs to happen in Pagure Dist-Git, since this file is generated by the pagure_owner_alias.py script, could you open a ticket there please?
pagure_owner_alias.py
Metadata Update from @abompard: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Thanks for the pointer. Would be nice if Pagure had a way to propose tickets to upstream.
Creating the PR was easier.
https://pagure.io/pagure-dist-git/pull-request/149
@abompard there is no activity in https://pagure.io/pagure-dist-git/ for more than 6 months, so I have to reopen this issue to raise that problem.
Metadata Update from @abitrolly: - Issue status updated to: Open (was: Closed)
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
[backlog refinement] The plan for this ticket is following: - Merge all opened PR's on pagure-dist-git - Release new version - Close this ticket
pagure-dist-git is upgraded.
Thanks for your patience
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.