-
Notifications
You must be signed in to change notification settings - Fork 15
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
Non-UTF-8 file name creation command fails with IOError #14
Comments
@jrwdunham in your testing, did you come across this issue again? We can close this if not. |
@ross-spencer Slightly different IOError when I run this on my Mac now:
|
Talking to @jrwdunham, the issue resides in OSX so we'll update the README to let users know that the create-variously-encoded-files subcommand of createtransfers is not supported on mac os x. |
I think when I said ^ I was confused. The issue is that our am.git Docker Compose configuration creates a volume on both the host and the container. The Max OS X host is probably also responsible for disallowing the strangely encoded files in this case too. |
I was testing the archivematica CentOS deploy with Vagrant. I tested on linux and MacOS as host. It works fine on linux but not on MacOS. I have compared environment settings, and I found that exporting LC_ALL as utf-8 fixes the issue. On MacOS, after loging Vagrant VM with
Setting
But setting
|
I think this has impacted @jrwdunham on OSX too. What do you think the best approach is @mamedin? I am have two initial thoughts:
But maybe there are other better ways to look after this kind of issue? |
I think we can export this variable in Makefile, for example:
|
The new
createtransfers.py
script fails when calling./createtransfers.py create-variously-encoded-files
withIOError: [Errno 84] Invalid or incomplete multibyte or wide character
.This failure happens on the following platforms:
This failure does not happen with:
The text was updated successfully, but these errors were encountered: