Fix the URL and method used to remove someone's ACL in dist-git #9635
No reviewers
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
releng/tickets!9635
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "master"
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?
This should have been fixed in the original PR but apparently it
was merged before my push took effect
Signed-off-by: Pierre-Yves Chibon pingou@pingoured.fr
This should fix the error that @churchyard was seeing in the original PR.
I've since found an small oddity which I'm investigating, so feel free to merge this PR but don't be surprised if another one shows up :)
1 new commit added
When querying the list of packages maintained by people, also query dist-git itselfThere is now a second commit in this PR that fixes the oddity I had found. Basically if someone had "unwatch" a package, we were not taking it into account (since that wouldn't be synced to bugzilla).
This will make the script a little slower, but more reliable.
1 new commit added
Small optimization: do not query dist-git if we're only interested in packages watchedI plan to test this and report back.
This fixes the problem I had before.
Is seems that the bugzilla json is generated cron-ish-ly, so subsequent runs with
--retirestill report that the users are watching things. I can recheck again once the json is renewed (when is that?).As a matter of completeness I think the script could also remove the user from bugzilla assignee overrides.
That is correct (it's in the description in the
--help), the cron runs hourly.Good idea, I'll see to that
Waiting for at least an hour to see the results.
1 new commit added
Check if the packager has a bugzilla overrides and if so, reset itSupport for bugzilla overrides added, but we should double-check that it changes only the override of interest, leaving the other one as is (e.i: check that if we retire user "bar" on Fedora, we don't change the override to "foo" on Fedora EPEL)
This return seem bogus. The variable is not defined.
This docstring needs updating.
Works.
Sigh, I shouldn't rename variables before pushing...
4 new commits added
Check if the packager has a bugzilla overrides and if so, reset itSmall optimization: do not query dist-git if we're only interested in packages watchedWhen querying the list of packages maintained by people, also query dist-git itselfFix the URL and method used to remove someone's ACL in dist-git@churchyard comments fixed (and hopefully code as well :))
Pull-Request has been merged by humaton