-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updates using factorio-updater do not work for 2.x #207
Comments
quick answer to patch it on the related issue of the related repos. |
I will not accept a patch to mangle the provided input; please either make |
Here is the relevant place to fix in Lines 559 to 561 in 94e9499
You can't look only for |
You were just too fast for me. Here is what's returned by factorio --version and than can be helped to determine the version:
Either Version: 64 or linux64 could be the one to determine arch. Edit: here is the patch proposed, it detect 64 bit version, and keep the same system (just returning the command rather than conditionnal test).
|
Right, I did not comment here again, but I don't think it's worth to fix the architecture detection (which is always dangerous, as it does not rely on a documented API, it could break at any time again) and instead just assume it's always the 64 bit build. I can't really image that there are any users who want to use the latest version of this repo to update a years old Factorio version. In the worst case one could always take an old version of this repo, which was fully working for the older versions of Factorio. |
I guess due to a changed package name, using the update function does not work for 2.xDue to a change of the --version output of the binary, updates are not working for the 2.x version.
Factorio 1.x prints a Binary version, while 2.x prints just a Version:
This leads to the 64 missing in the package name.
Running the updater by hand did work (at least from 2.0.7 stable to 2.0.8 experimental). The server-init itself is also still running well.
The text was updated successfully, but these errors were encountered: