-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Test failures on Windows #8
Comments
@Changaco I cannot understand what this code does, why and how. Sorry for my crass ignorance, but I need your help. here: https://github.com/Changaco/python-libarchive-c/blob/master/libarchive/write.py#L61 |
Because that's the correct way to do it. libarchive handles walking the file system and filling the |
FWIW, I do not care for writing archives since I use libarchive only to extract things, but I am still not sure why you would use a combo of opening and reading the file in Python and using the directory traversal of libarchive. If read things correctly, libarchive can do both traversal and file reading? |
@Changaco I still think that there is something that is likely not to work at all on posix for special files here: https://github.com/Changaco/python-libarchive-c/blob/master/libarchive/write.py#L68 |
@Changaco any idea on this? |
Looks like I forgot to answer here.
Does it? I don't remember seeing a function to do the actual file reading in libarchive. |
These tests fail for mysterious reasons.
They are all somehow related to writing archives.
I wonder why the new_archive_entry is reused in the paths loop when adding files rather than having a new entry? Nevertheless the failure might be due to the fact that somehow the file being added may be already opened for writing? Not sure. To investigate.. This could all be due to a single problem.
Possibly a build problem, though the built lib works rather well otherwise.
FWIW errno 22 is EINVAL
The text was updated successfully, but these errors were encountered: