The script that syncs owners/cc to bugzilla components seems to be expanding groups in pagure to all their members in bugzilla. This is unexpected to maintainers and should be reverted. It doesn't seem like it was doing this until after the 26th, but it's unclear what the change might have been that caused it.
This is discussed on the devel list: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/AP4ZGQHG5V4ZOXLC24FUB7MEBGSTSFCC/
@ralph and @mprahl any ideas?
Metadata Update from @kevin: - Issue tagged with: src.fp.o
OK, after looking at the script.. it looks like it gets the expanded watchers from the pagure watchers api directly, so we have to patch things there.
Posted a fix here: https://pagure.io/pagure/pull-request/2563
/cc @pingou
For the curious, the sync script is here: https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/distgit/pagure/templates/pagure-sync-bugzilla.py.j2
You can see that if it receives '@' group names from pagure, it will use them correctly and get the associated sig mailing list.. but pagure doesn't return any group names - only expanded user lists, addressed in https://pagure.io/pagure/pull-request/2563.
OK - @pingou hotfixed pagure on dist-git with the patch from https://pagure.io/pagure/pull-request/2563.
I confirmed that the script works with a small run on the nodejs-accepts package, only. It worked, and set the cclist to just the nodejs sig mailing list.
I kicked off a full run just now which takes quite a while to complete.
This is fixed now.
:round_pushpin:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Is this really fixed? I'm still getting CC'd on (abort) bugs that are filed against the xgl-maint and the control-center-groups, as recent as yesterday. Or is this a separate issue?
See bugs 1487635, 1487810 and 1487014
There might be a second part to this bug, with the default "watch" being reset in the migration to Pagure. As I mentioned on the mailing-list, I have 280 packages which I "watch" now, and already removed my watch from 99% of those in pkgdb, would be good to reimport that data (at 30 seconds per package, that'd be more than 2 hours of clicking)
@pingou did you migrate any of the watch statuses from PkgDB? I seem to recall you did.
@mprahl I am not sure, the script is there: https://pagure.io/pagure-dist-git/pull-request/7
@whot I think it is fixed, but the script didn't change any of the old bugs. ie, new bugs filed during the time it had the component wrong are still wrong, just now new bugs should be back to normal.
Hopefully there aren't too many of those bugs and you can just unCC. If thats not tenable, we can try and do something.
It does appear the pkgdb watchbugs state was not synced over.
Can we do that please?
Login to comment on this ticket.