No version 0.9.1 of package iron-router was found in the atmosphere database

[oorabona]

Hi IR team,

I have this error when issuing mrt add or mrt update. I have seen on Atmosphere this version have been released by mistake but I am stuck with it and this is blocking my devs.

I have tested these two shell commands from an existing project and from a newly "meteor create dummy" project.

Am I doing something wrong ?

Thanks,

[chhib]

I have the same problem.

[ghost]

As do I.

[cmather]

Releasing 0.9.0 and 0.9.1 to Atmosphere was a mistake. These releases are for the new Meteor packaging system. So make sure you're smart.json file isn't specifying 0.9.0 or 0.9.1 for iron router and you might also have to delete your smart.lock file and do mrt update after that. My apologies for this mistake.

On Aug 20, 2014, at 5:30 AM, Olivier notifications@github.com wrote:

Hi IR team,

I have this error when issuing mrt add or mrt update. I have seen on Atmosphere this version have been released by mistake but I am stuck with it and this is blocking my devs.

I have tested these two shell commands from an existing project and from a newly "meteor create dummy" project.

Am I doing something wrong ?

Thanks,

— Reply to this email directly or view it on GitHub.

[oorabona]

Hi @cmather , following your advices, I did these steps :

$ meteor create foo foo: created.

To run your new app: cd foo meteor

$ cd foo foo$ ls foo.css foo.html foo.js

foo$ mrt add iron-router

/usr/lib/node_modules/meteorite/lib/dependencies/package.js:63 throw('No version ' + version + ' of package ' + self.name + ' was found ^ No version 0.9.1 of package iron-router was found in the atmosphere database

foo$ ls foo.css foo.html foo.js smart.json

foo$ cat smart.json { "packages": { "iron-router": {} } }

foo$ mrt update /usr/lib/node_modules/meteorite/lib/dependencies/package.js:63 throw('No version ' + version + ' of package ' + self.name + ' was found ^ No version 0.9.1 of package iron-router was found in the atmosphere database

Now if I specify a version in smart.json so that I use the latest "stable" version to date aka "0.8.2" then it works..

Hope that helps.

[ottacom]

Hi had the same problem today, and I spent some hours to fixing the problem without success. I tried to install iron-router in this way

mrt add iron-router --version 0.8.2 Meteorite version 0.7.8 smart.json changed.. installing from smart.json

/usr/local/lib/node_modules/meteorite/lib/dependencies/package.js:63 throw('No version ' + version + ' of package ' + self.name + ' was found ^ No version 0.9.1 of package iron-router was found in the atmosphere database

Nothing! Could you post your smart.json? Some suggestions? Thanks everybody!!

[scottmcpherson]

Hey guys, this is what worked for me:

1) delete the entire smart.lock file 2) specify version 0.8.2 for iron-router in your smart.json

{
  "packages": {
    "iron-router": {
      "version": "0.8.2"
    }
    ...
}

3) and run the command mrt update

Note: I'm running meteor version 0.8.3. You can check your version by running meteor --version.

[ottacom]

Thank you scott!! Well done!

[alejandronanez]

Thank you Scott.

[tmeasday]

Argggh. Sorry, my bad everyone.

No need to lock the version, should be fixed now.

[ottacom]

Thank you Tom , doesn't matter!

[benjiqq]

get an error on MacOSX, meteor 0.8.3. I tried the mentioned fix above with inserting the version, but did not work for me. will this get republished?

$ mrt add iron-router
✓ iron-router
    tag: https://github.com/EventedMind/iron-router.git#v0.8.2
ERROR: 128 Command failed: fatal: Not a git repository (or any of the parent directories): .git

STDOUT:  

STDERR: fatal: Not a git repository (or any of the parent directories): .git

/usr/local/lib/node_modules/meteorite/lib/sources/git.js:181
            self.checkoutType + ": " + (self.commit || self.head);
                                     ^
There was a problem checking out tag: v0.8.2

[tmeasday]

@benjyz - try mrt uninstall --system -- it sounds like your ~/.meteorite has gotten messed up.

[benjiqq]

thanks - it's working. should have tested on a fresh machine.