Potentially Final Meteor 0.9.0 Release Candidate

[Ekaterina Kuznetsova]

Hi all!

We have put out a new release candidate for Meteor 0.9.0. At this point, we have fixed all the issues that we are aware of. As such, it is pretty close to being the official release for Meteor 0.9.0!

(Meteor 0.9.0 introduces the Meteor packaging system. We have changed the way that we build packages, and we have attempted to fold much of Meteorite's functionality into the Meteor core. We have also auto-migrated many Meteorite packages, into the official Meteor package server (and in the past few weeks, many other packages have been migrated by their authors)).

As a reminder: to migrate your app from meteorite, there is a helpful 'mrt migrate-app' command. There is also a hackpad detailing more information about this here. Similarly, the mostly-final draft of the Meteor documentation about the new package system is here.

To upgrade to the new release,  please run:

   meteor update --release 0.9.0-rc11

and let us know how it goes! If you are wondering what changed since the previous releases, there is a hackpad here. 

Thanks so much!

[Dave Workman]

My test suite passed 100% out of the box. Haven't tried the previous release candidates. I'm pleasantly surprised. I was worried how well it would work with old packages. Keep up the good work guys!

[Vincent Jaubert]

I don't know if this is the right place to report since it's perhaps mrt related, but i got following errors when trying to do mrt migrate-app:

mrt migrate-app

Updating all references to packages in .meteor/packages

/usr/lib/node_modules/meteorite/lib/project.js:371

      delete smartJson.packages[name];

                                ^

TypeError: Cannot convert null to object

    at /usr/lib/node_modules/meteorite/lib/project.js:371:33

    at /usr/lib/node_modules/meteorite/lib/atmosphere.js:240:9

    at /usr/lib/node_modules/meteorite/node_modules/ddp/lib/ddp-client.js:209:9

    at Array.forEach (native)

    at Function._.each._.forEach (/usr/lib/node_modules/meteorite/node_modules/underscore/underscore.js:76:11)

    at DDPClient._message (/usr/lib/node_modules/meteorite/node_modules/ddp/lib/ddp-client.js:206:7)

    at null.<anonymous> (/usr/lib/node_modules/meteorite/node_modules/ddp/lib/ddp-client.js:75:10)

    at emit (events.js:95:17)

    at EventTarget.dispatchEvent (/usr/lib/node_modules/meteorite/node_modules/ddp/node_modules/faye-websocket/lib/faye/websocket/api/event_target.js:24:10)

    at instance._receiveMessage (/usr/lib/node_modules/meteorite/node_modules/ddp/node_modules/faye-websocket/lib/faye/websocket/api.js:123:10)

[David Glasser]

Thanks, hopefully Tom can look into this!

--
You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

[Andreas Gabriel]

I can't start my bundled app until manually installing the fibers, underscore, source-map-support and semver npm packages. I think it's a bug because previously it got bundled with the app!?

[Tom Coleman]

Hi Vincent,

Can you open an issue at https://github.com/oortcloud/meteorite and post a couple more details (specifically what was in your `smart.json/lock`) ?

Thanks!

[Jens Ulrich Hjuler Pedersen]

I can't start my bundled app anymore either. Currently can't find the 'underscore' module, when running "node main.js"

[David Glasser]

Jens: Have you followed the instructions in the README in your bundle (which have changed slightly)?

--

[David Glasser]

Does it work now?

(Though actually we are up to rc14 :) )

On Sat, Aug 23, 2014 at 8:15 AM, אילנה חכים <ilana...@gmail.com> wrote:

   first time user. (no meteorote). tried to upgrade

meteor update --release 0.9.0-rc11

 got 

0.9.0-rc11: unknown release.

(working on windows)

the same goes with :

meteor update --release CORDOVA-PREVIEW@3

CORDOVA-PREVIEW@3: unknown release.

[Eric Dobbertin]

Just wanted to point out that in rc14 when you do some command that requires login but aren't logged in, there's a big ugly error. Somewhere within the error trace there is an "Error: access-denied", so I was able to guess that I needed to log in, but it would be much better if it just said "Sorry, you must log in to do that."

[David Glasser]

Which particular command? I thought this worked.

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[David Glasser]

And were you actually logged out?  Or just logged in as the wrong user or something?

[Eric Dobbertin]

It was with meteor admin maintainers --remove

But you’re right, if I logout and try that again, I get the nice message. I wasn’t logged in as the wrong user, but I suspect I was logged in as the correct user but that login happened while on Meteor 0.8.3 (I had just upgraded on this particular machine). That’s the only thing I can think of. I guess the lesson is that you should re-log in after you meteor update to 090.

If it helps:

Refreshing package metadata. This may take a moment.

/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/dev_bundle/lib/node_modules/fibers/future.js:173

throw(ex);

      ^

Error: access-denied

    at sendAuthorizeRequest (/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/auth.js:447:11)

    at oauthFlow (/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/auth.js:469:25)

    at Object.exports.loginWithTokenOrOAuth (/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/auth.js:1110:17)

    at Object.exports.loggedInPackagesConnection (/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/package-client.js:291:8)

    at main.registerCommand.name [as func] (/Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/commands-packages.js:1895:32)

    at /Users/Eric/.meteor/packages/meteor-tool/.1.0.17.ut200e++os.osx.x86_64+web.browser+web.cordova/meteor-tool-os.osx.x86_64/tools/main.js:1212:23

You received this message because you are subscribed to a topic in the Google Groups "meteor-talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-talk/_or7T0OgFZo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-talk...@googlegroups.com.

[Eric Dobbertin]

Currently `meteor show METEOR` only shows rc14 even though I'm using rc19.

[David Glasser]

Yes, I have not yet marked newer rc's as recommended because I haven't done the slow full build process required to make them the default release.  (The reason for so many intermediate releases is extra testing of some update commands.)

--

You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[Eric Dobbertin]

OK, one side effect is that if my app is on rc19 and I type `meteor update`, it downgrades the app to rc14. Seems like it should keep the current higher version even though it is not recommended.

You received this message because you are subscribed to a topic in the Google Groups "meteor-talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-talk/_or7T0OgFZo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-talk...@googlegroups.com.

[David Glasser]

Thanks, reproduced and fixing.

[David Glasser]

Fixed in rc20, though you can't actually verify that directly without making an unrecommended rc21. Thanks for the report, it was really helpful in finding a few related issues.

[David Glasser]

And now we're up to rc22!  "meteor update --release 0.9.0-rc22" (or just "meteor update" if you're already running an rc!)  We've been making some tiny little tweaks to ensure that the transition from 0.8.3 goes smoothly, but we believe this one is releasable.  Bang on it in the next few hours if you'd like!

[Andrew Mao]

Bangin.

[Dave Workman]

Last time I updated (I think it was rc-10 or so) it said I no longer need Meteorite. Now it says update it and run "mrt migrate-app" but meteorite complains there is no sub command named migrate-app. Everything runs fine so do I even need to worry about this?

[David Glasser]

Have you upgraded mrt recently?  "npm install -g meteorite"

[Jens Ulrich Hjuler Pedersen]

Thanks for the pointer, David.

I've issued a PR for meteor-up that should support Meteor 0.9.0 bundles, that fixed the issues I had with deploying. Anyone care to try it out?

[David Glasser]

That's right! 0.9.0 is out! "meteor update" should bring you up to date (temporarily erasing your current install, but it'll happily re-download 0.8.3 for you).

https://www.meteor.com/blog/2014/08/26/meteor-090-new-packaging-system

Thanks so much to everyone who tested the RC, and especially to Tom Coleman (and the rest of Percolate Studio) and Mike Bannister for building Meteor's first package system and putting in plenty of work to help us move smoothly to the official package system!

Enjoy!

--dave

[ps: I am sending this instead of Ekate, who really did the lion's share of work on this project, because she is enjoying a well-deserved vacation already :) ]

On Tue, Aug 26, 2014 at 8:24 AM, Andrew Mao <miz...@gmail.com> wrote:

It's out! The monster is released!

On Tuesday, August 26, 2014 10:43:53 AM UTC-4, Dave Workman wrote:

Looking at meteorite's source, there's a script called migrate-all, not migrate-app in the scripts directory. But that doesn't work for me either. Could this be because I don't have ruby installed? ( the scripts have a .rb extension )

On Tuesday, August 26, 2014 10:26:00 AM UTC-4, David Glasser wrote:

Huh. Works for me.

On Tue, Aug 26, 2014 at 7:10 AM, Dave Workman <davidw...@gmail.com> wrote:

Yeah, should have mentioned that. I tried that, as well as uninstalling and then installing again.

--
You received this message because you are subscribed to a topic in the Google Groups "meteor-core" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-core/_or7T0OgFZo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-core...@googlegroups.com.

To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

For more options, visit https://groups.google.com/d/optout.

--

You received this message because you are subscribed to the Google Groups "meteor-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.
To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.

[Chris Mather]

Sweet!

[Andrew Mao]

FYI, updating from rc12 or earlier just freezes for me. I had to meteor update --release 0.9.0 to get it to take.

[David Glasser]

There were definitely some update bugs in rc12.

[Vincent Jaubert]

Whatever i do, the installer freeze without errors. I have tried meteor update --release 0.9.0 without success. 

I have been triying versions up to 0.9.0-rc22.

I have tryed on a virgin project, it works, but not on my main app.

[David Glasser]

So you can run your app with 'meteor' and what does 'meteor --version' say, but meteor update doesn't work?

Does it print something about refreshing metadata?

[Vincent Jaubert]

Le mardi 26 août 2014 18:30:31 UTC+2, David Glasser a écrit :

So you can run your app with 'meteor' and what does 'meteor --version' say, but meteor update doesn't work?

"meteor" works as usual, launching 0.8.3 and informing about availability of 0.9.0

"meteor --version" reports Release 0.8.3

meteor update or meteor update --release 0.9.0, or meteor --release 0.9.0 just freeze

The first time i ran it, it frooze after saying :

Installing Meteor 0.9.0:

 * 'meteor' build tool (version 8301fde275)

After something like 10 minutes, i killed it.

Does it print something about refreshing metadata?

Nope.

I tried meteor reset, but it doesn't improve the situation.

[Andrew Mao]

I'm finding it currently impossible to update from rc12. Both freezing:

$ meteor update --release 0.9.0

Installing Meteor 0.9.0:

 * 'meteor' build tool (version 8301fde275)

$ meteor update --release MET...@0.9.0

  downloading meteor-tool at version 1.0.25 ... 

Why is it that both of the above even work, and they do different things?

[Andrew Mao]

Manually updating `.meteor/release` and then running `meteor update` also just hangs.

$ meteor update

  downloading meteor-tool at version 1.0.25 ... 

[Andrew Mao]

Uh, sorry. The last one completed after a while. So I'm good now.

[Andrew Mao]

If an app references a locally installed package @0.7.0 for example, and I run a separate app or tests (on the same machine) asking for that package @0.7.0, will it grab the canonical one or the locally installed one (which has additional commits)?

Is the package manager smart enough to not build locally installed app packages into the machine's package cache, and grab the canonical versions when they are referenced elsewhere?

[David Glasser]

Hmm. If you already had a Meteor RC installed, but not one of the last ones, I can see how that would happen --- an interaction between the special update-from-legacy scripts and buggier old releases.  I think once you have it updated to 0.9.0, it should be fine.

If all else fails:

 $ rm -rf /usr/local/bin/meteor ~/.meteor

 $ curl https://install.meteor.com/ | sh

--dave

--

[David Glasser]

The first one is the special update-from-legacy script being downloaded from the OLD meteor release server, whereas the second is the actual real 0.9.0 release.

--

You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[David Glasser]

If you have a locally installed package (ie, a package whose source is in your app's packages directory, in a directory listed in $PACKAGE_DIRS, or is a part of your Meteor checkout if not running for a release) then it will ALWAYS take precedence over any other version of that package.

--

[David Glasser]

(This allows you to easily fork a package into your app and make local changes.)

[Mitar]

Hi!

Meteor does not provide npm executable anymore? Or it is somewhere
hidden very deep:

.meteor/packages/meteor-tool/.1.0.25.2me099++os.linux.x86_64+web.browser+web.cordova/meteor-tool-os.linux.x86_64/dev_bundle/bin/

Could you expose this somewhere higher? The way it was before?

.meteor/tools/latest/bin

What is the curl URL for old version of Meteor?


Mitar

> --
> You received this message because you are subscribed to the Google Groups
> "meteor-core" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to meteor-core...@googlegroups.com.
> To post to this group, send email to meteo...@googlegroups.com.
> Visit this group at http://groups.google.com/group/meteor-core.
> For more options, visit https://groups.google.com/d/optout.



--

http://mitar.tnode.com/
https://twitter.com/mitar_m

[Vincent Jaubert]

Le mardi 26 août 2014 20:09:07 UTC+2, David Glasser a écrit :

If all else fails:

 $ rm -rf /usr/local/bin/meteor ~/.meteor

 $ curl https://install.meteor.com/ | sh

David, i finally removed meteor as instructed and reinstalled it.
When i started my project, it installed 0.8.3 (normal, since it's the set version).
Then i did "meteor update"

 meteor update

Installing Meteor 0.9.0:

 * 'meteor' build tool (version 8301fde275)

Refreshing package metadata. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

Figuring out the best package versions to use. This may take a moment.

This project is at the latest release which is compatible with your

current package constraints.

Cool, no freezing this time ! and then "meteor"

meteor

[[[[[ ~/dev/Cadendar ]]]]]

=> Started proxy.

=> Meteor 0.9.0 is available. Update this project with 'meteor update'.

=> Started MongoDB.     

=> Errors prevented startup:

While building the application:

error: no such package: 'buzz.js'

error: no such package: 'vjau'

error: no such package: 'simison'

error: no such package: 'brentjanderson'

=> Your application has errors. Waiting for file change.

What ??? I'm still at 0.8.3 !

meteor --version

Release 0.8.3

[Mitar]

Hi!

(This broke now all my automatic builds and tests everywhere.)


Mitar

[Andrew Mao]

Does package@version no longer do the greater-than-or-equal to constraint anymore?

I'm seeing stuff like the following, when `@3.2.0-1` and `@3.2.0-2` are specified in different places.

Could not resolve the specified constraints for this project:

Error: conflict: mrt:boots...@3.2.0-1 vs 3.2.0-2

[David Glasser]

You only get things with dashes in the name if you explicitly request them by name.  That way you won't get rc's and alphas that you don't ask for.  This is consistent with the semver standard: "A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version"

--dave

[Andrew Mao]

That is crappy, because we can't simultaneously follow upstream versions exactly without having dashes to denote package changes not with upstream versions, or four digit places. Any suggestions for how I can work around that?

[Andrew Mao]

It's really frustrating how you guys make these decisions without considering all their ramifications, and causing tons of headaches for package authors that have to run around in circles to try and figure out what we must do to make things work.

I guess I'll just number all of my wrapped packages starting at 1.0.0 then, like MDG has...sigh.

[Mitar]

Hi!

Yes, we were using 4 digit places things a lot. When you wrap a NPM
package, you want to mirror upstream in first three digits places.


Mitar

[Andrew Mao]

Well, ya can't use 4 digits, and you can't use dashes, so let's all clap for being "consistent with the semver standard".

While reading package from `/home/mao/projects/CrisisMapping/CrowdMapper/packages/natestrauser:x-editable-bootstrap`:

error: The package version (specified with Package.describe) must be valid semver (see http://semver.org/).

FYI: this is still buggy even considering Glasser's definition: https://github.com/meteor/meteor/issues/2443#issuecomment-53478782

[Mitar]

Hi!

SemVar does allow for digits, x.y.z-w. Semantics is a bit different,
but it does allow it.


Mitar

[Andrew Mao]

Did you just read what Glasser wrote above?

On Tuesday, August 26, 2014 4:02:24 PM UTC-4, Mi Tar wrote:

Hi!

[אילנה חכים‎]

meteor update

Can't contact the update server. Are you online?

This project is already at Meteor 0.8.3, the latest release

installed on this computer.

I am working on windows and behind a corporate proxy...

any ideas ?

2014-08-25 10:14 GMT+03:00 David Glasser <gla...@meteor.com>:

Does it work now?

(Though actually we are up to rc14 :) )

On Sat, Aug 23, 2014 at 8:15 AM, אילנה חכים <ilana...@gmail.com> wrote:

   first time user. (no meteorote). tried to upgrade

meteor update --release 0.9.0-rc11

 got 

0.9.0-rc11: unknown release.

(working on windows)

the same goes with :

meteor update --release CORDOVA-PREVIEW@3

CORDOVA-PREVIEW@3: unknown release.

--

You received this message because you are subscribed to the Google Groups "meteor-core" group.

To unsubscribe from this group and stop receiving emails from it, send an email to meteor-core...@googlegroups.com.

To post to this group, send email to meteo...@googlegroups.com.
Visit this group at http://groups.google.com/group/meteor-core.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "meteor-core" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-core/_or7T0OgFZo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-core...@googlegroups.com.

[Daniel Chcouri]

Hi Ilana,

I had the same problem, curl 403 error when trying to downgrade, right?

I've slightly modified Mitar's* script that installs v0.8.3 and disables autoupdate. Download it and run it, it'll do the job.

https://gist.github.com/theosp/42525654297d6b31fa18

Now I am happy with v0.8.3 .

* https://groups.google.com/d/msg/meteor-talk/wLxgDhtr7HM/chQvF21ENb4J

Daniel C. <http://theosp.github.com/>

[David Glasser]

When you say Windows, do you mean with Vagrant?

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[Arunoda Susiripala]

I don't think so. Then it's not windows :)

---

Arunoda Susiripala

I curate Meteor Weekly - Check it out!

[Gadi Cohen]

Yeah, since it's fairly common in our ecosystem to want to package an upstream library, we're going to need some clear guidelines on this.  A lot of packages in Atmosphere currently use the 3.2.1-5 format (where 3.2.1 is the upstream version and -5 is the smart package iteration for that version).

I think a good compromise - if you're willing to forego strict semver compliance - would be to treat labels that are all numeric differently.  e.g.  3.2.1-5 is probably desirable whereas 3.2.1-rc1, 3.2.1-beta, etc are more clearly pre-releases.  Could also be dependent on whether any non-dashed version exists, at all.

I did a little research and it seems the semver "recommendation" is to add build metadata like 1.2.3-meteor+3.2.1 (the initial version is the smart package version, and the end of the string is the upstream version).  Besides being quite confusing, this doesn't actually help anyone at all, since it still has a pre-release tag, and "two versions that differ only in the build metadata, have the same precedence".

I see also that in general, labels should be dotted for new versions, e.g. 0.9.0-rc.1, 0.9.0-rc.2 and not -rc2, etc; according to semver at least.  That's actually kind of nice though because then we can say request 0.9.0-rc and get the latest iteration.

[David Glasser]

That's definitely worth considering. I like it.

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[אילנה חכים‎]

hi Daniel -

1. windows - i.e. actual windows (can't afford a mac yet...)

2. I didn't try to downgrade . I am trying to update to 0.9.0 in order to be able to checkout CORDOVA-PREVIEW@3 version

    I would really like to try that one...

10xs,

ilana

[Sashko Stubailo]

Hi Ilana!

If you would like to try the Cordova preview release but don't have access to a Mac, the easiest thing to do would be to install a virtual machine or dual booth with Linux. CORDOVA-PREVIEW@3 was tested on the newest release of Ubuntu, which you can download here: http://www.ubuntu.com/desktop

Thanks,

Sashko

[David Glasser]

Agreed. Meteor has never officially supported Windows.  It is on our roadmap for later. https://trello.com/c/ZMvnfMfI/11-official-windows-support

[Ivan Brykov]

While trying to do 'meteor update' I'm getting this:

=> Errors while scanning packages:

While reading package from `/somepath/packages/cfs-access-point`:

package.js:39:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-collection`:

package.js:35:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-collection-filters`:

package.js:19:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-file`:

package.js:43:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-tempstore`:

package.js:22:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-upload-ddp`:

package.js:35:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-upload-http`:

package.js:29:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/cfs-worker`:

package.js:17:7: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

While reading package from `/somepath/packages/collectionFS`:

error: Package names can only contain lowercase ASCII alphanumerics, dash, dot, or colon, not "F".

[Eric Dobbertin]

Ivan, CollectionFS is not switching to the new packaging system yet. See the readme installation steps: https://github.com/CollectionFS/Meteor-CollectionFS#installation-meteor-090-and-later

--
You received this message because you are subscribed to a topic in the Google Groups "meteor-talk" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/meteor-talk/_or7T0OgFZo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to meteor-talk...@googlegroups.com.

[Marin Pranjić]

Refreshing package metadata. This may take a moment.

Error connecting to package server: DDP connection timed out
Warning: could not connect to package server
CORDOVA-PREVIEW@5: unknown release.

Blah...

--
You received this message because you are subscribed to the Google Groups "meteor-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meteor-talk...@googlegroups.com.

[Gadi Cohen]

Awesome!  Happy my suggestion was well received.