Closed dandv closed 9 years ago
Looks like I'm a little late doing this...
$ meteor admin maintainers matb33:collection-hooks --remove mrt
Removing a maintainer from matb33:collection-hooks...
Error from package server: Not a maintainer [400]
$ meteor admin set-unmigrated mrt:collection-hooks
Setting mrt:collection-hooks@0.2.0 as unsuccessfully migrated ... Error from package server: You are not an authorized maintainer for this package. [401]
/cc @tmeasday
Hey @matb33 - can you link your MD account at atmosphere.meteor.com/accounts ? Cheers.
Thanks @tmeasday. Apologies that you have to direct me manually on this.
The copy on the migration page tells me: You're done! Sit back, profit, party
, which I fully plan on doing -- but is this accurate with regards to retiring mrt:collection-hooks
, or do I need to take a few more steps before this can be wrapped up?
Done @matb33. No worries :)
What is your plan from here? Are you going to mark it unmigrated or something?
On 23 Dec 2014, at 6:01 am, Mathieu Bouchard notifications@github.com wrote:
Thanks @tmeasday https://github.com/tmeasday. Apologies that you have to direct me manually on this.
The copy on the migration page tells me: You're done! Sit back, profit, party, which I fully plan on doing -- but is this accurate with regards to retiring mrt:collection-hooks, or do I need to take a few more steps before this can be wrapped up?
— Reply to this email directly or view it on GitHub https://github.com/matb33/meteor-collection-hooks/issues/72#issuecomment-67875612.
Not sure if I did this right, still confused:
$ meteor admin set-unmigrated mrt:collection-hooks
Setting mrt:collection-hooks@0.2.0 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.2.1 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.2.2 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.2.3 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.3.0 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.3.1 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.3.2 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.5.0 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.5.1 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.5.2 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.5.3 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.5.4 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.0 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.1 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.2 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.3 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.6 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.6.7 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.7.0 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.7.1 as unsuccessfully migrated ... done.
Setting mrt:collection-hooks@0.7.2 as unsuccessfully migrated ... done.
Running the same command many times produces the same output, and mrt:collection-hooks
still appears in the search results. Will keep trying...
Looks right @matb33 -- we are just having a problem syncing with upstream right now (see https://github.com/percolatestudio/atmosphere/issues/332)
OK, thanks for letting me know -- I can now go to bed :)
Gone now :)
https://atmospherejs.com/mrt/collection-hooks
might work