-
Notifications
You must be signed in to change notification settings - Fork 106
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
Comments
Hey @aldeed - did you need to manually migrate it? Only the packages that automigrated have been registered with the server for |
An earlier version was auto-migrated, but this particular version I published with I don't know what qualifies as popular, but I would suggest these packages of mine:
Also had the same issue with these, that I would guess are popular:
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 |
Ok, I marked those as best I could. If you have sec, maybe try re-migrating On Thu, Aug 28, 2014 at 11:38 PM, Eric Dobbertin [email protected]
|
When trying
mrt migrate-app
using the latest meteorite (0.9.0), I get errors such as this: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.The text was updated successfully, but these errors were encountered: