Learn more about these different git repos.
Other Git URLs
It would be great if the process is automated. It cannot be fully automated, but a script that runs the unretirement rather than running each step manually.
When do you need this? (YYYY/MM/DD) Sooner the better
When is this no longer needed or useful? (YYYY/MM/DD) There will be always unretirement requests
If we cannot complete your request, what is the impact? Someone has to run the steps manually every time there is a unretirement request.
The fact that unorphaning is no longer self service is a huge step backwards -- the new system should have had feature parity with the old one IMO.
Adopting a package to keep it maintained is a hurdle these days -- the day(s?) long wait to gain access is a huge discouragement to fixing things.
I think we need changes in pagure over dist git for this. Have a 'orphan' user that is special. Users can give packages to orphan and any user (who is in packager) can take over a package from orphan. There's probibly other ways to do it.
CC @pingou
I think we need changes in pagure over dist git for this. Have a 'orphan' user that is special. Users can give packages to orphan and any user (who is in packager) can take over a package from orphan. There's probibly other ways to do it. CC @pingou
This would be nice but it also needs to check the retirement status of packages.
In Mageia, we have a nobody user that is used in this manner. If nobody is still blacklisted in FAS, we should use that user for this.
nobody
There is already the orphan user but there is not yet the special behavior that everyone can adopt the packages.
Also see: https://pagure.io/fesco/issue/2091 which I filed today.
That issue is about steering people who are orphaning packages in the direction of actively looking to give it to co-maintainers / maintainers of packages which depend on it, rather then always "giving" the package to the orphan user.
But as the discussion there shows, the conclusion might very well be that we should not make the person doing the orphaning do more work (introducing a hurdle to orphan packages), but rather what we want is the old frictionless take over from pkgdb where any existing packager can just hit a "take over" button on orphaned packages and then everything happens automatically.
IMHO we need a UI for this at: http://src.fedoraproject.org/ , rather the some semi-automatic way to process requests from releng issues.
@pingou can we just add a rule to dist-git pagure that when a package is owned by the orphan user and not all branches are retired, anyone has admin privileges and can therefore assign the package to themselves?
Closing as a duplicate of https://teams.fedoraproject.org/project/fedora-release-tooling/us/998?kanban-status=15
Metadata Update from @syeghiay: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
Woah, how is this a duplicate? The issue you linked to is about automating orphan package status notifications. This ticket is about the releng process of unorphaning and unretiring packages.
Please re-open.
@mbooth Sorry for the confusion.
Unorphaning automation will be part of dist-git - https://pagure.io/pagure-dist-git/pull-request/72 Unretirement automation is tracked in https://teams.fedoraproject.org/project/fedora-release-tooling/us/851?kanban-status=17
Can we please not close tickets in Pagure with things in Taiga? It's hard to keep track of everything when you do this.
Login to comment on this ticket.