or Create a profile
22 Jul, 2011 12:28 AM
We have a TON of people on every project because of the way that
migration came over from rubyforge.
I've created a script (attached) that should clean up most of
our mess... but I've locked myself out of nearly everything due to
a couple data snafus in my script munging.
I've also modified the owner_command in trunk to deal with
errors more gracefully... this is required for said snafus to get
Assuming you have overrides in the api for you to manage all
ownership stuff from the commandline, running it while in your
updated rubygems checkout should suffice.
2 Posted by Nick Quaranto on 05 Aug, 2011 02:54 PM
This didn't show up the queue, so thats why it took so long to
respond :/ Anyway, you're added back to those gems now so you
should be able to manipulate the permissions the way you want them
3 Posted by Ryan Davis on 06 Aug, 2011 02:22 AM
On Aug 5, 2011, at 07:53 , Nick Quaranto wrote:
> This didn't show up the queue, so thats why it took so long to respond :/ Anyway, you're added back to those gems now so you should be able to manipulate the permissions the way you want them now.
Sweet. I fixed everything I could find.
Comments are currently closed for this discussion.
You can start a new one.
2 people watching.
No more actions from RubyGems.org or the discussion starter are required.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
Powered by Tender™.