Learn more about these different git repos.
Other Git URLs
This Monday in the EU infra/releng standup, @lenkaseg mentioned that there are packages to be blocked in certain koji tags but nobody around with koji admin powers to do so (people being on vacation, public holiday, hopefully asleep because it’s not their time zone, etc.).
On a whim, I took this as an excuse to attempt finding out if I (as a member of sysadmin-main but not a koji admin) could dig myself out of this, but after some poking around came to the conclusion that I’d rather not mess with the koji database directly, except and unless this would have been a dire emergency.
sysadmin-main
My request is: could some more trusted people get the koji admin permission, primarily so they can perform tasks needing that permission when releng people can’t be reached? As a side effect, these people could serve as planned backups for simple tasks (like blocking a package in a tag) when releng folks are unavailable or just busy with something more important.
admin
I would propose @lenkaseg to be one of these persons, she regularly asked to block packages in the recent past and could do so herself if she had the permission. I would volunteer for this, too – I have some experience with koji (assisting on the CentOS side with side tags for SIGs, odd fixes and extensions to koji), and I think I’ve been using my powers responsibly and shown to tread carefully in matters outside my experience (but you be the judge 😉).
When it’s convenient
When koji is no more
We might find ourselves without a koji admin in a situation where on is needed.
Yeah, I was afraid the blocking was going to cause issues being run manually... but hopefully we are getting near automation doing it again.
I'd support adding you both.
Metadata Update from @phsmoura: - Issue tagged with: low-trouble, medium-gain, ops
+1 to this
Thanks for your cooperation, patience, and awesome work. We discussed this in our releng call today, and after all the votes, @nphilipp and @lenkaseg now have the power of koji admins! Please use your power safely :D
Metadata Update from @jnsamyak: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.