Package update broken for 0.0.28 #568
Comments
Ouch! Me too 😟 |
what os? |
OSX |
@tekknikk, In the mean time, you can force specifying the package number like so: meteor add cfs:gridfs@=0.0.27 |
@raix, I think this is the issue: |
not sure @PEM-- it's an optional field - I'm thinking if... rake?? investigating... |
Oh, this is my fault. I was trying to build for the Windows preview, but apparently there are some bugs with that process that they're still figuring out. I can build for the other architectures tomorrow, but just pin to 0.0.27 for now. |
@aldeed ahhh understand re builds. I wondered as I saw that comment in my search before posting. |
There should be a working 0.0.29 now. |
Just received the same message with 0.0.29 (osx) updated to Meteor 1.0.3.2. While checking for cfs:gridfs@0.0.29: |
$ meteor update
This project is already at Meteor 1.0.3.2, the latest release.
=> Errors while upgrading packages:
While checking for cfs:gridfs@0.0.28:
error: No compatible build found
The text was updated successfully, but these errors were encountered: