Migrate archive-repo-manager from pagure #13386
Labels
No labels
after freeze
automation
backlog
blocked
change-ack
change-nak
change-noreleng
changes
Closed As
Can't Fix
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Get back later
Closed As
Grooming
Closed As
Insufficient data
Closed As
Invalid
Closed As
It's all good
Closed As
taiga
Closed As
upstream
day-to-day
dev
docs
easyfix
epel
f26
f27
f28
f29
f30
f31
f32
f33
f34
f35
f36
f37
f38
f39
f40
f41
f42
f43
f44
f45
fedora
groomed
high-gain
high-trouble
in-progress
in-review
investigation
legal
low-gain
low-trouble
mass rebuild
medium-gain
medium-trouble
meeting
mini-initiative
new_artifact
ops
pdc_retirement
rawhide
RCA
review
script
sidetarget
sprint-0
sprint-1
sprint-2
sprint-3
sprint-4
sprint-5
unfrozen
waiting on external
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets#13386
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?
The archive-repo is used for atomic variants that need to be able to download updates that have been removed from the
fedora-updatesrepository.I think someone with the repo access should merge: https://pagure.io/releng/archive-repo-manager/pull-request/40
Newer repo: releng/archive-repo-manager#40
Need to see if there are any external dependencies that needs changing.
Thank you @jnsamyak, is it possible to have a subset of CoreOS members c.f https://accounts.fedoraproject.org/group/sysadmin-coreos/ to own that repo ? or at least have the permission to merge PRs, close issues, etc
Until now it was mainly maintained by @dustymabe
Ofcourse, let me look!
@jcapitao, are there any external dependencies we need to look at for updating the paths for this migration?
infra/ansible#3402! once, I get a +1 here, I'll merge it up. And, assign the access to the repository.
@jcapitao wrote in #13386 (comment):
Is there a chance you might want to moderate access to that repository independently of the sysadmin-coreos group? If that is the case, we just need to create new group in ipa and map that group to the forge team. If you are ok with the
sysadmin-coreosgroup will be the only place that specify access to that repo, the ansible PR by @jnsamyak should do that.@jnsamyak hmm not that I'm aware of, I think it's self contained. But let's wait for @dustymabe confirmation.
@humaton let me ask more broadly to the CoreOS folks
I'm +1 for re-using the
sysadmin-coreosgroupYeah,
sysadmin-coreosis fineSounds good to me
I see @dustymabe already in the team added, need to see why others didn't made it to the team maybe because they haven't logged to new forge yet but that dont seem to be the case with @jcapitao and others
Hey folks, the process is still ongoing with fedora forge, but to unblock you all, I added @dustymabe and @jbtrystram and @jcapitao as colloborator on that repo, meanwhile I'll figure that out.
Okay, I think this is fixed, as people are relogging or logging into Forge for the first time, they are getting synced. So, all working well here in case there are anything else that needs to be done, please file a ticket, migration is done here!
Thanks for the patience.