meteor-scss: Error after 'meteor update' - no compatible binary found

The problem is still there 8 hours later.

For people who encountered error, you can use c9s:scss to get the binary package.

Version 3.9.0 has been published using the new method in meteor 1.4.1, that no longer requires pre-build binaries.

I’ve been able to publish it for win and mac, but not yet for linux…

Just pin the version with @=3.8.0_1

Running meteor add fourseven:scss@=3.8.0_1 in console did not work, however, adding the line:fourseven:scss@=3.8.0_1 directly to the .meteor/packages file worked.

Just update fourseven:scss to fourseven:scss@=3.8.0_1 in your package-file in the .meteor directory to pin the version.

1.4.1 is out, can this be fixed now?

Yes, if your deployment on heroku worked before and has now stopped it’s because of the missing linux binaries. Still trying to publish the build, but the meteor build servers shut down before the build completes…

In .meteor/versions change the package with fourseven:scss@3.8.0_1

It works for me on heroku

do you know if there is a place where we can check to see if the linux binary is also built and published (without actually trying to upgrade or deploy on heroku without a version constraint)?

Yes, you can do:

meteor show --ejson fourseven:scss

And you will see something like this in the output:

  "architecturesOS": [
    "os.windows.x86_32",
    "os.osx.x86_64"
  ]

Other versions have four entries.

@RaymondLC92 There are 2 alternatives prior to Meteor 1.4.1

1. pin the package to 3.8.0_1 in packages. Edit packages file inside .meteor folder from fourseven:scss to fourseven:scss@=3.8.0_1 Option 1 worked for me
2. clone the package If you don’t have a folder named packages inside your meteor root project directory, create packages folder. Then using your terminal cd inside packages directory. e.g. cd <meteor-proj>/packages Then execute the command : git clone https://github.com/fourseven/meteor-scss.git Then inside meteor-project directory i.e. cd .. after previous command, execute meteor reset and then meteor

It should work

problem is that 3.8.1 is the only one which would work with meteor 1.4. Only workaround for now that I can think of is cloning this package locally in the packages folder of your application

@serkandurusoy don’t know of such a place. At least not an easy one. You could check out the sqlite database meteor keeps on your hard drive containing all package information: meteor-installation/package-metadata/v2.0.1/packages.data.db. It has a table builds, wouldn’t be too hard to write a script that tells you this info.

Anyway, in this particular instance I’ll make a comment here when the build has finally succeeded.

Can confirm this 3.8.1 on my machine.

Doing as @danimbrogno suggested worked for me, replacing the current package in .meteor/packages to fourseven:scss@=3.8.0_1 worked.

+1

+1