You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that when importing a omex archive in pymetadata, that it complains on windows about entries missing in the manifest, even though they are present.
which on windows will create a string with a backslash as separator, if the file in the manifest is encoded with a slash, then the entry will not be able to be properly resolved.
The text was updated successfully, but these errors were encountered:
thanks! locally i've solved it with just replacing the backslashes with forward ones and was able to get it running
forroot, _dirs, filesinos.walk(str(directory)):
forfileinfiles:
file_path=os.path.join(root, file)
location=f"./{os.path.relpath(file_path, directory)}"iflocation=="./manifest.xml":
# manifest is created from the internal manifest entriescontinue# replace backslashes with forward slashes <--------location=location.replace("\\", "/")
...
I've noticed that when importing a omex archive in pymetadata, that it complains on windows about entries missing in the manifest, even though they are present.
Looking through the code, this is due to
pymetadata/src/pymetadata/omex.py
Line 576 in d09ca89
which on windows will create a string with a backslash as separator, if the file in the manifest is encoded with a slash, then the entry will not be able to be properly resolved.
The text was updated successfully, but these errors were encountered: