Closed jasonxeno closed 9 years ago
sorry about that, just bumped versions - publishing for arch... (we are building auto publish scripts atm. so this can be avoided)
(its trying to publish for arch atm - give it 5 min)
Just in case anyone else can't build, I just hit the same problem (20 hours later) on OSX. I tried $ meteor remove cfs:gridfs
then $ meteor add cfs:gridfs => Errors while adding packages: While checking for cfs:gridfs@0.0.30: error: No compatible build found
I was able to build with $ meteor add cfs:gridfs@=0.0.27
Still not working.
Can confirm that $ meteor add cfs:gridfs@=0.0.27
works.
@raix, I'm starting to think this package ended up in some broken state that can't be fixed by bumping and republishing. It started with my attempt to publish it for the Windows preview, but since then I think we've both tried bumping the version and publishing from OSX, which seems to work but then somehow does not end up with an OSX-compatible build, even though that's the OS we used to publish?
Or is it also related to moving all our packages into a single repo? Have you tried copying the files for this package elsewhere and then publishing?
@stubailo?
Tried doing meteor update today again.
$ meteor update
This project is already at Meteor 1.0.3.2, the latest release.
Changes to your project's package version selections from updating package versions:
aslagle:reactive-table upgraded from 0.6.14 to 0.6.15
cfs:access-point upgraded from 0.1.43 to 0.1.44
cfs:base-package upgraded from 0.0.27 to 0.0.28
cfs:collection upgraded from 0.5.3 to 0.5.4
cfs:collection-filters upgraded from 0.2.3 to 0.2.4
cfs:data-man upgraded from 0.0.4 to 0.0.6
cfs:file upgraded from 0.1.15 to 0.1.16
cfs:gridfs upgraded from 0.0.29 to 0.0.30
cfs:s3 upgraded from 0.1.2 to 0.1.3
cfs:standard-packages upgraded from 0.5.3 to 0.5.4
cfs:storage-adapter upgraded from 0.1.1 to 0.2.1
cfs:tempstore upgraded from 0.1.3 to 0.1.4
cfs:upload-http upgraded from 0.0.19 to 0.0.20
cfs:worker upgraded from 0.1.3 to 0.1.4
msavin:mongol upgraded from 0.5.4 to 0.5.5
It did not complain about incompatible build this time.
But now I am getting the same error as issue #588 on startup.
I20150305-11:25:25.244(-6)? Exception in queued task: TypeError: Cannot read property 'start' of undefined
I20150305-11:25:25.245(-6)? at Object.FS.StorageAdapter.createReadStream (packages/cfs:gridfs/gridfs.server.js:78:1)
I20150305-11:25:25.245(-6)? at Object.self.adapter.createReadStreamForFileKey (packages/cfs:storage-adapter/storageAdapter.server.js:71:1)
I20150305-11:25:25.245(-6)? at Object.self.adapter.createReadStream (packages/cfs:storage-adapter/storageAdapter.server.js:79:1)
I20150305-11:25:25.245(-6)? at packages/cfs:tempstore/tempStore.js:364:1
I20150305-11:25:25.245(-6)? at runWithEnvironment (packages/meteor/dynamics_nodejs.js:108:1)
I20150305-11:25:25.245(-6)? at packages/meteor/dynamics_nodejs.js:121:1
I20150305-11:25:25.245(-6)? at CombinedStream._getNext (/home/jason/.meteor/packages/cfs_tempstore/.0.1.4.1kimx01++os+web.browser+web.cordova/npm/node_modules/combined-stream/lib/combined_stream.js:83:3)
I20150305-11:25:25.245(-6)? at CombinedStream.resume (/home/jason/.meteor/packages/cfs_tempstore/.0.1.4.1kimx01++os+web.browser+web.cordova/npm/node_modules/combined-stream/lib/combined_stream.js:132:10)
I20150305-11:25:25.245(-6)? at CombinedStream.pipe (/home/jason/.meteor/packages/cfs_tempstore/.0.1.4.1kimx01++os+web.browser+web.cordova/npm/node_modules/combined-stream/lib/combined_stream.js:64:8)
@raix @aldeed I don't really want to wade through a bunch of stack traces and try to solve this issue over GitHub comments - do you guys have an opportunity to get on a Google hangout sometime soon to take a look?
@stubailo I don't think there is a need. I seem to have 0.0.30 published correctly for all archs now, I think we were running into a combination of the window-preview issue and https://github.com/meteor/meteor/issues/3676 at the same time, which made it difficult to understand what was going on. Hopefully we can do a windows preview build at some point, but I'm not anxious to go through that confusion of errors again.
I fixed some of the errors we had with incorrect version numbers, so in theory it should just work on Windows now. It would actually be really helpful for us to test whether it works, but I guess I can just do that by cloning your package and publishing under my name.
If you think it will work, I can try again. In theory I know how to get out of the potential mess now.
Nah, I'll try it first and let you know.
I get the same error as jasonxeno.
downgrading to
meteor add cfs:gridfs@=0.0.27
works
@aldeed now I get this with 0.0.31
While checking for cfs:gridfs@0.0.31:
error: No compatible build found
With the release of cfs:gridfs@0.0.31, I can successfully update everything without the previous errors and it works now.
I'm actually still getting this error. And it also happens for 0.0.27
Hi there! I tried with 0.0.32 and it didn't work but meteor add cfs:gridfs@=0.0.33 works for me. Meteor version Meteor 1.1-rc.0 (Windows preview https://github.com/meteor/meteor/wiki/Preview-of-Meteor-on-Windows) I hope this will help you.
0.0.33
is the first release with support for Windows.
Getting this error when trying to update:
OS is: Linux Ubuntu 14.04
Package list and update attempt: