Meteor 1.3.2 isn't available on Windows


#1

updated to Meteor 1.3.2-rc.6.

meteor update --release 1.3.2
This project uses Meteor 1.3.2, which isn’t available on Windows. To work with this app on all supported
platforms, use meteor update --release METEOR@1.3.1 to pin this app to the newest Windows-compatible release.

Is this a mistake? I’ve been running 1.3.2* for over a week without any problems and I just upgraded to 1.3.2-rc.6 without issues.


Continuous Integration on Visual Studio Online
#2

I’m not up to date with the current releases, but the Windows version of each Meteor release typically shows up around 6 to 8 hours later. No idea why.


#3

Twenty-three hours later and Meteor 1.3.2 is still not available on Windows.


#4

Release 1.3.2.1 installs. So it looks like it was just 1.3.2 that does not install.


#5

1.3.2 did install for me by the way on Windows 8.1


#6

Well, windows installer installs 1.3.1 for me, not 1.3.2.1.
Then I have to manually meteor update --release METEOR@1.3.2.1


#7

Neither 1.3.2 nor 1.3.2.1 have been recommended, due to two relatively small but unacceptable bugs.
Version 1.3.2.2 is now recommended—try meteor update now?


#8

OK, that works. How can we find out that a release is recommended or not?


#9

The command meteor show METEOR will list all the recommended releases:

> meteor show METEOR                 
Release: METEOR                               
Maintainers: glasser                          
                                              
The Official Meteor Distribution              
                                              
Recommended versions:                         
  0.9.4.1  December 9th, 2014                 
  1.0.1    December 9th, 2014
  1.0.2    December 19th, 2014
  1.0.2.1  December 22nd, 2014
  1.0.3.1  January 20th, 2015
  1.0.3.2  February 25th, 2015
  1.0.4    March 17th, 2015
  1.0.4.1  March 18th, 2015
  1.0.4.2  March 20th, 2015
  1.0.5    March 25th, 2015
  1.1      March 31st, 2015
  1.1.0.1  April 2nd, 2015
  1.1.0.2  April 3rd, 2015
  1.1.0.3  August 3rd, 2015
  1.2      September 21st, 2015
  1.2.0.1  September 22nd, 2015
  1.2.0.2  September 28th, 2015
  1.2.1    October 26th, 2015
  1.3      March 27th, 2016
  1.3.1    April 3rd, 2016
  1.3.2.2  April 18th, 2016

Non-recommended versions of METEOR have been hidden. To see all 244 versions, run 'meteor show --show-all METEOR'.

#10

Right now if i launch meteor update and meteor show METEOR I get this result:

Release: METEOR                               
Maintainers: glasser                          
                                              
The Official Meteor Distribution              
                                              
Recommended versions:                         
  0.9.4.1  December 9th, 2014                 
  1.0.1    December 9th, 2014
  1.0.2    December 19th, 2014
  1.0.2.1  December 23rd, 2014
  1.0.3.1  January 21st, 2015
  1.0.3.2  February 25th, 2015
  1.0.4    March 17th, 2015
  1.0.4.1  March 18th, 2015
  1.0.4.2  March 20th, 2015
  1.0.5    March 25th, 2015
  1.1      March 31st, 2015
  1.1.0.1  April 2nd, 2015
  1.1.0.2  April 3rd, 2015
  1.1.0.3  August 3rd, 2015
  1.2      September 21st, 2015
  1.2.0.1  September 22nd, 2015
  1.2.0.2  September 29th, 2015
  1.2.1    October 26th, 2015
  1.3      March 28th, 2016
  1.3.1    April 4th, 2016

1.3.2.2 doesn’t appear on the list, is ti correct?

Thanks.


#11

1.3.2.2 has been unrecommended. See this for more details:


#12

Hmm… that’s the list I am seeing now. Yesterday, however, 1.3.2.2 April 18th, 2016 was at the end of the list.


#13

Yes - it was recommended at that time, so would have appeared.


#14

Thanks to that situation I have not recommended 1.3.2.2 inside app while my .meteor is 1.3.1 on windows (as it broken last night so I had to reinstall and got 1.3.1.)

What should I do now ?


#15

You can still force an update:

meteor update --release 1.3.2.2

#16

Can I revert app back to 1.3.1 ?

It was called 1.3.2_2 btw


#17

You can always update to an earlier version of meteor, although it can get messy to clean up packages. The simplest plan (assumimg you’re using git or other version control) is to commit your working 1.3.1 project, then reverting is just a case of restoring to that point. However, you can do the necessary tidying up yourself if you don’t use git.

1.3.2_2 is the same as 1.3.2.2


#18

Will force 1.3.2.2 again.


#19

Anyone has been able to update to 1.3.2.3? Running into this when I’m trying

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:1011:11)
    at Process.ChildProcess._handle.onexit (child_process.js:802:34)

#20

1.3.2.3 ?? I’m getting crazy …

Just installing the Linux box and got 1.3.2.2 on first update, while 1.3.2.2 is bad for my windows dev box … and you ask for 1.3.2.3 … mess.

Edit: Even saw 1.3.2.4 on the precesses list :slight_smile: