migrate-app says package "has not yet been migrated" even though it has about meteorite

[tmeasday]

Hey @aldeed - did you need to manually migrate it?

Only the packages that automigrated have been registered with the server for mrt migrate-app. Let me know any popular packages (autoform is popular right?) that are in this state and I'll fix it up.

[aldeed]

An earlier version was auto-migrated, but this particular version I published with meteor publish after that.

I don't know what qualifies as popular, but I would suggest these packages of mine:

• autoform (aldeed:autoform)
• collection2 (aldeed:collection2)

Also had the same issue with these, that I would guess are popular:

• accounts-entry (joshowens:accounts-entry)
• fast-render (meteorhacks:fast-render)
• moment (mrt:moment)
• numeral (mrt:numeral)

I got through the migration by removing each package it complained about until the migration completed, and then searching for them and adding back manually. Not horrible, and I appreciate the time that mrt migrate-app saved me by mapping the packages it did know about.

[tmeasday]

Ok, I marked those as best I could. If you have sec, maybe try re-migrating
your old app and see if it's better. (Or not :) )

On Thu, Aug 28, 2014 at 11:38 PM, Eric Dobbertin [email protected]
wrote:

An earlier version was auto-migrated, but this particular version I
published with meteor publish after that.

I don't know what qualifies as popular, but I would suggest these packages
of mine:

• autoform
• collection2

Also had the same issue with these, that I would guess are popular:

• accounts-entry
• fast-render
• moment
• numeral

I got through the migration by removing each package it complained about
until the migration completed, and then searching for them and adding back
manually. Not horrible, and I appreciate the time that mrt migrate-app
saved me by mapping the packages it did know about.

—
Reply to this email directly or view it on GitHub
#299 (comment).