Seattle.rb ownership was overzealous in migration

Ryan Davis's Avatar

Ryan Davis

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 cleaned up.

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.

  1. Support Staff 1 Posted by Nick Quaranto on 05 Aug, 2011 02:54 PM

    Nick Quaranto's Avatar

    Hey Ryan,

    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.

  2. Support Staff 2 Posted by Ryan Davis on 06 Aug, 2011 02:22 AM

    Ryan Davis's Avatar

    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.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac