Getting EINVAL here is unexpected and may be a bzr-explorer bug, but that's being masked the problem pointed out in the logging that was added in r6046 on trunk. Same old mixing of unicode paths and localised bytestrings in OSError messages.
Getting EINVAL here is unexpected and may be a bzr-explorer bug, but that's being masked the problem pointed out in the logging that was added in r6046 on trunk. Same old mixing of unicode paths and localised bytestrings in OSError messages.