What happened to release repos?

[wico-silva]

The release repo and account are gone: https://github.com/pr2-gbp/pr2_common-release
What happened to it? What's the alternative?

This is currently breaking the build of meta-ros1-noetic, see ros/meta-ros#1238

[v4hn]

Please see PR2/pr2_self_test#22 for the full backstory.

This is unprecedented for me. It's not like it's hard enough to maintain these robots in-lab without random upstream problems.

Concretely w.r.t. meta-ros:
Do you need the release repositories or can you instead use upstream directly?
This is what multiple ROS-O builders do [0, 1].

Obviously the missing release repositories should be fixed for ROS noetic at least.

[wico-silva]

Thank you for the reply and context @v4hn. Open source is amazing but sometimes stuff like this happens 😅 .

As to meta-ros, in the meantime, since yesterday, we changed to the upstream and it builds again 🎉

[UltronDestroyer]

I've contacted github support to restore the repository, once it is restored I will transfer ownership back to the community. I have not been involved for 10+ years with this project, so I had no idea the community was still relying on it.. sorry all! @wico-silva @v4hn

[v4hn]

Hello there @UltronDestroyer!
Thank you for responding here.
Are you looking into restoring the repository or the whole organization (including the other still relevant repositories)?

[UltronDestroyer]

I'm going to restore the entire org of pr2-gbp (and thus all its repos) and I will transfer ownership to all that are active in the community. Github hasn't gotten back to me, but it is my understanding that this is something possible to do. If you could compile a list of who should become owners that would be great, or if there is a particular individual that the keys should be given to let me know.

Edit: As per discussion with OSRF reps, @gbiggs will be the owner of the org (Open Robotics/OSRF) and he will handle permissions out to the community @v4hn @k-okada + et al ..

After that it's up to you guys to fix any broken links in the distro to any new org names

[OpsysUser1]

Can anyone please post a zip of "pr2-gbp/pr2_common-release" that he might have locally, so I can fix my build of "meta-ros1-noetic - ros-image-world" at least for now?

[UltronDestroyer]

If you wanted to take the matters into your own hands and not wait for Github support - you could create a new org called "pr2-release" and then recreate the 15 or so repositories and re-bloom them all. The existing pr2 code is still up, and then you would need to make a PR into the rosdistros to redirect all pr2-gbp -> pr2-release org. It would probably not take that long to do so.

https://wiki.ros.org/ROS/ReleasingAPackage

[wico-frad]

Can anyone please post a zip of "pr2-gbp/pr2_common-release" that he might have locally, so I can fix my build of "meta-ros1-noetic - ros-image-world" at least for now?

Hi, to resolve the build issue with 'meta-ros1-noetic -' please refer to this pull request (PR) for more details: ros/meta-ros#1240

[v4hn]

Let's wait for the response please. If it turns out they cannot/will not restore it, we can go for that option still.
But yes, there is no reason you would need to use the *-release repository to build in a OR-independent build system. Upstream is still intact.

[OpsysUser1]

Can anyone please post a zip of "pr2-gbp/pr2_common-release" that he might have locally, so I can fix my build of "meta-ros1-noetic - ros-image-world" at least for now?

Hi, to resolve the build issue with 'meta-ros1-noetic -' please refer to this pull request (PR) for more details: ros/meta-ros#1240

The repository https://github.com/pr2/pr2_common does not have "noetic" branch.

[wico-frad]

Can anyone please post a zip of "pr2-gbp/pr2_common-release" that he might have locally, so I can fix my build of "meta-ros1-noetic - ros-image-world" at least for now?

Hi, to resolve the build issue with 'meta-ros1-noetic -' please refer to this pull request (PR) for more details: ros/meta-ros#1240

The repository https://github.com/pr2/pr2_common does not have "noetic" branch.

Did you find any problem using the melodic-devel branch? To my knowledge noetic does not need any patches. Please refer to #283 for further details.

[UltronDestroyer]

Update: Still nothing from Github support. Messaged them 3 times. I'm so very glad I moved away from Github a long long time ago.

[UltronDestroyer]

Ownership is being transferred to @gbiggs. pr2-gbp has been restored

[v4hn]

Thank you for your initiative to help here @UltronDestroyer ! ❤️

@gbiggs Could you please grant me write permission to the organization so I can finish at least PR2/pr2_self_test#22 for now? Probably others later. Feel free to get in touch by mail if you want to talk about more here.