Files installed through as_utils_install_metadata_file() have executable bit set #681
Comments
|
Hmm, I'm pretty sure the source file does not have set the executable bit, while the destination does have it set (even when it does not exist yet). Your change suggests the problem can be somewhere else, somewhere deeper, because you do not fiddle with the file attributes at all, furthermore you let glib to "inherit the file attributes from the source file", which makes it confusing, like if the problem was in the glib itself. |
|
I'm reopening this, the problem is still present. |
mcrha
added a commit
to mcrha/appstream
that referenced
this issue
Jan 16, 2025
The file has set the attributes after commit c6903ab, thus this is not needed. If it was meant to set the executable flag on the parent directory, then it is not needed either, at least according to my tests. The `path_dest` points to the installed file here, not to the parent directory. Closes ximion#681
|
See #694 for my finding. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a file is installed through
as_utils_install_metadata_file(), it has set the executable bit in the destination. See:This is with appstream-1.0.2-4.fc41.x86_64
The text was updated successfully, but these errors were encountered: