R is affected by the i686 Java collapse and Tom seems to be unreachable. I can take care of that if we push this forward.

Any ETA here? We would like to land R 4.2.1 on rawhide.

Sorry for the massive delay here. ;(

I have setup things from our side, but there's still more to do.

You need to:

• go to bugzilla.redhat.com and create a new user called 'r-maint-sig@lists.fedoraproject.org'
• The activation info for this user will go to the list and be moderated. You can then activate it and allow bugzilla to post (after the activation email)
• I added you and spot to the group as sponsors, so you should be able to add any other users you like now. (They should subscribe to the list if they want bugzilla emails)
• You / spot will need to then add this group as main admin by using the 'give package' option in settings in src.fedoraproject.org. Or if you need to, we can do this with a list for you.

I think that should do it, but let us know if you need anything else or have any other questions.

Thanks, Kevin. I suppose there's a way to mass-add the group to a list of packages, so we could use your help for this. It's R, rpy, rkward, and all the R packages, which can be listed as follows:

$ dnf repoquery --repo=fedora-source R-* | cut -d"-" -f 1,2

Also, r-maint-sig should be set as the Bugzilla assignee. I'm mentioning this because I'm not sure whether this is automatic when the group is added as admin or not.

Hum. The only script I can find for this is the one that gives main admin to a project, but that won't work here as a group cannot be main admin. ;(

@churchyard did you have a script for this? Or @humaton should be back tomorrow and should know more...

Ok. Meanwhile, a more refined way to get the list of R packages:

$ dnf repoquery -q --repo=fedora-source --releasever=rawhide --qf %{name} R-*

@churchyard did you have a script for this?

No, I don't. Perhaps @decathorpe.

• You / spot will need to then add this group as main admin by using the 'give package' option in settings in src.fedoraproject.org. Or if you need to, we can do this with a list for you.

This does not work, as groups cannot be "main admin"/ "owner" of a package.

You can only add groups as co-maintainers, but they cannot be the primary POC for a package.
The closest you can get to doing that is to add the group with "admin" ACL and set the bugzilla overrides to the group username, as well.

And yes, I have a script to mass-add packages to a group:
https://gist.github.com/decathorpe/9d128982cb00e2d345d9e397372538ec

It will need small adaptations (replace "rust-sig" with "r-maint-sig", obviously, and replace "commit" with "admin", if that is what you need).

The script also does not support setting bugzilla assignees, as I could not figure out how to do that with the undocumented pagure-dist-git REST API.

I'm also pretty the user who runs this script will need "cvsadmin" privileges or an API token with special superpowers, otherwise they won't be able to modify ACLs on packages they are not "main admin" or "admin" of.

And yes, I have a script to mass-add packages to a group:
https://gist.github.com/decathorpe/9d128982cb00e2d345d9e397372538ec

Side note: We will probably also use a script like this to enforce the new SIG policy (for Rust SIG only, until it's also approved for other SIGs), so if you see or encounter any problems with it, please let me know.

The script also does not support setting bugzilla assignees, as I could not figure out how to do that with the undocumented pagure-dist-git REST API.

See https://pagure.io/releng/blob/main/f/scripts/distgit/retire_packagers.py which uses that API

Back from vacation. Any update on adding admin ACLs to R, rpy, rkward and the current set of R packages? I see that the new version of R is still sitting in a side tag, and there are several hundred R packages waiting to be rebuilt there. I also opened https://pagure.io/fesco/fesco-docs/pull-request/69. Thanks.

Scripting is being worked on: https://pagure.io/releng/pull-request/10982 so hopefully soon...

Yeah, sorry ... errno = EBUSY :)

Once the first version of the script that handles rust-sig packages is accepted, I can help with adding rules for other SIGs.

@iucar can you do these steps? In particular we need to make sure the bugzilla user is created so bugs can be properly cc'ed...

I have setup things from our side, but there's still more to do.

You need to:

• go to bugzilla.redhat.com and create a new user called 'r-maint-sig@lists.fedoraproject.org'
• The activation info for this user will go to the list and be moderated. You can then activate it and allow bugzilla to post (after the activation email)
• I added you and spot to the group as sponsors, so you should be able to add any other users you like now. (They should subscribe to the list if they want bugzilla emails)
• You / spot will need to then add this group as main admin by using the 'give package' option in settings in src.fedoraproject.org. Or if you need to, we can do this with a list for you.

I think that should do it, but let us know if you need anything else or have any other questions.

I did! Sorry I didn't confirm. Did I miss anything?

huh. ok, let me check things over, perhaps I missed something on our end.

@kevin We are receiving BZ emails in the mailing list now. But messages are being held. I thought I give BZ permission to post. How do I do that now?

go to mass subscribe and subscribe bugzilla@redhat.com and then it should allow it to post.

Done, thanks.

Wouldn't that result in bugzilla@redhat.com being sent a copy of everything that happens on list?

When I set up my last mailing list, I just added a rule to accept all incoming emails from that address, but didn't subscribe it.

Good point. I've set the "Delivery status" in the member options for BZ to "Disabled". That would do, right?

I also see "header filters", but I don't see any documentation. Would "Header: from", "Pattern: bugzilla@redhat.com", "Action: Accept immediately" work?

Oh yeah, sorry, you want to disable email for that address.

You can do ^From: bugzilla@redhat.com too in header filters.