-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bloom release noetic incomplete #22
Comments
@v4hn I am afraid that I also lost permission
|
@gbiggs Does anyone at OSRF have write or admin access to https://github.com/pr2-gbp ? |
I also do not have permission for that organization. |
OOB Geoff doesn't know what happened to permissions on the If that fails, as a last sort I would recommend cloning the release repo to a new org and updating ros/rosdistro accordingly. |
@wjwwood: Would be great if you could check your permissions for the I will contact gh support as well. |
I contacted GH support, but they will not change ownership or grant access following their policies. @sloretz @gbiggs Please nudge William through another channel to check whether he can grant access. If there's no reply from the anonymous owners in a while I guess the annoying, but logical, next step is to migrate the rosdistro release repo entries to a different organization, possibly @ros-gbp (or @ros2-gbp although there will not be a ROS2 release of the packages in the near future). |
It appears I no longer have any access to the pr2-gbp repository either. Sorry. |
@mqcmd196 rightfully requested a new noetic release in #21 and I tried to do it.
Turns out I am missing permissions for the https://github.com/orgs/pr2-gbp organization for some reason and cannot push the release to bloom right now (see below)
I believe @k-okada is the only one who might have access there and can be contacted.
@mqcmd196 Please talk to him in my name to check if he can grant me the missing permissions.
It's possible he's missing the permissions to do that as well, though he can at least run the command that fails for me below.
@davefeilseifer If you happen to read this: You were the one who pushed the original package release for this repo to noetic in 2021 and I believe you have full admin permissions for the @pr2-gbp org (permissions are not public for it). If you can, please grant me permissions so I can push out noetic fixes. I met with @k-okada et al. a while ago and we started clearing out some pr2 packages since then.
The text was updated successfully, but these errors were encountered: