I am still working on the meteor-coverage package, and yesterday I tryed to publish the 1.0.0 update.
I tryed meteor publish like I did several times in the past but this way does not look supported anymore.
I tryed to publish-for-each on several build machines (by first using meteor admin get-machine os.linux.x86_64), but I always get an error:
meteor@ip-172-x-x-x:~$ meteor publish-for-arch lmieulet:meteor-coverage@1.0.0
lmieulet:meteor-coverage: updating npm dependencies -- istanbul-api, body-parser, homedir, minimatch, mkdirp,
remap-istanbul...
=> Errors while initializing project:
While building package lmieulet:meteor-coverage:
error: couldn't install npm packages from npm-shrinkwrap: Command failed:
/home/meteor/.meteor/packages/meteor-tool/.1.4.1_1.139xb76++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm
install
npm ERR! addLocal Could not install
/tmp/package-source18b58q6/lmieulet_meteor-coverage/.npm/package-new-1iq10df/.cache/minimist/0.0.10/package.tgz
npm ERR! Linux 3.2.0-105-virtual
npm ERR! argv
"/home/meteor/.meteor/packages/meteor-tool/.1.4.1_1.139xb76++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/node"
"/home/meteor/.meteor/packages/meteor-tool/.1.4.1_1.139xb76++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm"
"install"
npm ERR! node v4.5.0
npm ERR! npm v3.10.6
npm ERR! path
/tmp/package-source18b58q6/lmieulet_meteor-coverage/.npm/package-new-1iq10df/.cache/minimist/0.0.10/package.tgz
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
[...]
How can I debug that ?
Is it mandatory to publish for arch if meteor-coverage dependencies has no dependency that needs to be build for that specific arch ?
meteor publish-for-arch is no longer required. Quoting from the 1.4.1 release notes:
The meteor publish-for-arch command is no longer necessary when publishing Meteor packages with binary npm dependencies. Instead, binary dependencies will be rebuilt automatically on the installation side. Meteor package authors are not responsible for failures due to compiler toolchain misconfiguration, and any compilation problems with the underlying npm packages should be taken up with the authors of those packages. That said, if a Meteor package author really needs or wants to continue using meteor publish-for-arch, she should publish her package using an older release: e.g. meteor --release 1.4 publish
Thanks for your reply @hwillson
But how do you install meteor-coverage if there is no architecture available ? If I execute the following in a meteor app
meteor add lmieulet:meteor-coverage@1.0.0
it just crash
While checking for lmieulet:meteor-coverage@1.0.0:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it for your platform.
I already read what you linked but I still donβt get how to install now
I can rebuild minimist without any issue. METEOR_FORCE_PORTABLE=1 meteor publish did what I was looking for whereas meteor [publish|publish-for-arch] failed, it should be documented on the meteor guide, right ?