-
Notifications
You must be signed in to change notification settings - Fork 311
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
Installer can't handle paths containing non-ASCII letters #86
Comments
thanks for the report, will investigate. I assume you fixed the config file manually and got it running (were there errors in any other file?), if so, please report version info from the top of /logs in the console. If not, please report what OS and what the OS locale is set to. |
reproduced here on a UTF-8 locale and JRE with izpack 5.1.3. Setting the encoding to UTF-8 for the parsables in install5.xml didn't help. Appears to be this bug https://izpack.atlassian.net/jira/software/c/projects/IZPACK/issues/IZPACK-1617?jql=project%20%3D%20%22IZPACK%22%20ORDER%20BY%20created%20DESC fixed in 5.2.0 Current version is now 5.2.3, we will have to update and test |
Update shortcut spec format, old format does not work with 5.2.3, new format works with 4.3.0, 5.1.3, and 5.2.3 Format grabbed from ./izpack-dist/src/main/izpack/shortcutSpec.xml in izpack repo https://github.com/izpack/izpack and specified at https://izpack.atlassian.net/wiki/spaces/IZPACK/pages/491733/Shortcut+Specification
Prep for 5.2.3 in 7e9e78f to be 2.7.0-3, lightly tested with 5.2.3 and 5.2.4-SNAPSHOT, posted 5.2.3 build instructions on http://zzz.i2p/topics/3661 , started discussions with @eyedeekay about build/upgrade/test before our release, as he's the one that will have to do it, we don't bundle izpack 5 in our repo, it's too big |
Hello.
After installing I2P, I wasn't able to run it.
i2prouter
gives me this error:I opened
i2prouter
with my text editor and there's indeed this path hardcoded. The problem is it's wrong: the folder where I store my apps is calledПриложения
, not@8;>65=8O
.The text was updated successfully, but these errors were encountered: