Closed alienth closed 5 months ago
Confirmed bug, I could reproduce on my end. I'll have a fix up.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Comment generated by the GitHub Lock Issues workflow.
Paste the command
igir copy --dat /foo --input /bar --output /baz
Describe the bug
If igir copies a read-only file (with a mode such as
0444
), it will copy those permissions as well. When it tries to do a subsequent operation on that copied file, it spams anEACCES
error:When igir exits after encountering this, it leaves the temporary file in the output dir that it wrote for the copy.
I'm guessing it's trying to open the files in write-mode when it does the rename from the temp file?
Note that this error occurs regarding the file in the output directory. The directory itself has standard perms that allows it being written to.
Changing the source file to allow writes (
0666
) avoids the issue.Expected behavior
A
copy
operation should work on files with mode0444
.If igir needs to perform a write on a copied file, perhaps it should make the temporary file writable?
Debug logs
DAT(s) used
No-Intro
igir version
2.6.2
Node.js version
21.6.1
Operating system
Debian
Additional context
No response