Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

migrate-app says package "has not yet been migrated" even though it has #299

Open
aldeed opened this issue Aug 27, 2014 · 3 comments
Open

Comments

@aldeed
Copy link
Contributor

aldeed commented Aug 27, 2014

When trying mrt migrate-app using the latest meteorite (0.9.0), I get errors such as this:

Error: The version 0.17.1 of package autoform has not yet been migrated

But that is my package, which I know has been released, and meteor show aldeed:autoform does list 0.17.1. So what checks are being done that result in this error? I've seen the same wrong error for 4 other packages so far, some mine and some others'. But it does find matches for other packages.

@tmeasday
Copy link
Member

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
Copy link
Contributor Author

aldeed commented Aug 28, 2014

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
Copy link
Member

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants