0.11.18 [cube] update fail "unexpected content" bug
- darksparks
- Inserter
- Posts: 32
- Joined: Mon Aug 11, 2014 4:08 am
- Contact:
0.11.18 [cube] update fail "unexpected content" bug
it fails on linux mint 64bt.. throws error "unexpected content" but i have a standard directory and just updated to 11.17
i have many mods.. and a while back i edited a caimpaign mission to so that i could play with dytech and still build stuff that needed stone gears.. but its been playing clean in 11.17 for a while now and i updated after i changed things so its the latest 11.18 update that doesnt like my directory =/
i have many mods.. and a while back i edited a caimpaign mission to so that i could play with dytech and still build stuff that needed stone gears.. but its been playing clean in 11.17 for a while now and i updated after i changed things so its the latest 11.18 update that doesnt like my directory =/
Last edited by darksparks on Thu Mar 12, 2015 8:42 pm, edited 3 times in total.
Re: 11.8 bug!
same problem here. I have never used mods.
Re: 11.8 bug!
Yup, same error here (Debian, 64bit).
@darksparks - could you change the title to be more informative, and also contain the correct version (0.11.18, not 11.8) - just so it is clear what the problem is, and that it is indeed a problem in the current version, not 10 versions ago
Edit: Thanks, much better!
@darksparks - could you change the title to be more informative, and also contain the correct version (0.11.18, not 11.8) - just so it is clear what the problem is, and that it is indeed a problem in the current version, not 10 versions ago
Edit: Thanks, much better!
-
- Inserter
- Posts: 29
- Joined: Sun Dec 28, 2014 10:01 am
- Contact:
Re: 0.11.18 update fail "unexpected content" bug
Same issue on OS X, no mods.
- darksparks
- Inserter
- Posts: 32
- Joined: Mon Aug 11, 2014 4:08 am
- Contact:
Re: 0.11.18 update fail "unexpected content" bug
here is my directory as it stands
- Attachments
-
- 2.jpg (29.91 KiB) Viewed 7321 times
Re: 0.11.18 update fail "unexpected content" bug
Confirming same issue, openSUSE 13.1 x86_64 here. Just updated to 0.11.17 a few days ago from a clean download of the last 'stable' release, and no mods installed (yet!)
- darksparks
- Inserter
- Posts: 32
- Joined: Mon Aug 11, 2014 4:08 am
- Contact:
Re: 0.11.18 update fail "unexpected content" bug
working full download.. updater download is the ussue.. if you cant wait download full version.. problem solved
Re: 0.11.18 update fail "unexpected content" bug
Yep, can confirm - downloading it from the site and simply unpacking it over the old version, worked correctly.
Re: 0.11.18 update fail "unexpected content" bug
0.11.17->0.11.18 fails on mac os x too.
I was trying to update from 0.11.16->0.11.18, and first part was ok (0.11.16->0.11.17), but second part failed.
I was trying to update from 0.11.16->0.11.18, and first part was ok (0.11.16->0.11.17), but second part failed.
Code: Select all
Update failed:
File /Applications/factorio.app/Contents/data/../MacOS/factorio has unexpected content
Re: 0.11.18 update fail "unexpected content" bug
This is probably not a bug in 0.11.18, but rather a bug in the 0.11.17 updater...
I am only guessing, but I think it means there will be no choice but upgrading manually, and hoping the devs fix the bug for 0.11.19 (if it isn't already fixed in 0.11.18, which we have no way of knowing).
I am only guessing, but I think it means there will be no choice but upgrading manually, and hoping the devs fix the bug for 0.11.19 (if it isn't already fixed in 0.11.18, which we have no way of knowing).
Re: 0.11.18 [cube] update fail "unexpected content" bug
This is most probably only a bug in the 0.11.18 release, I'll hope I'll fix it in a few hours.
Re: 0.11.18 [cube] update fail "unexpected content" bug
Good to know I was wrong! This is much bettercube wrote:This is most probably only a bug in the 0.11.18 release, I'll hope I'll fix it in a few hours.
Re: 0.11.18 [cube] update fail "unexpected content" bug
This problem was caused by my experiments with the deploy scripts. Basically I have overwritten the 0.11.17 state with something between 0.11.17 and 0.11.18. This version was then expected as the original state in the update packages.
I have fixed the stored versions and re-run the deploy, updates should work fine now. Sorry for the trouble.
I have fixed the stored versions and re-run the deploy, updates should work fine now. Sorry for the trouble.