-
Notifications
You must be signed in to change notification settings - Fork 443
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
Can't (correctly) generate a deb with a file in /etc/sudoers.d #394
Comments
Can you provide a small sample project? I couldn't reproduce the error. |
FIX #394 adding tests for native packaging with 0440 permissions
The test does not address the problem at hand. Try adding a second
line to see the problem. |
So the actual problem that you can't run
That's the case. So this is rather a performance issue, as |
Our target dir need to be refactored I think. Now it seems quite messy and unstructured. Also, cleaning this directory (not whole target) before creating package is a good idea IMHO (I've got some bugs with this). |
@kardapoltsev you mean the created debian target directory structure? What particularly do you mean? I think the code base could always use a bit of a facelifting (there are too many debian related parts spread in the code base). Cleaning |
Yes, I mean dir structure created during packaging in target. |
IMHO the messy part is where all the bin, configure scripts are placed :/ |
When you try to generate a deb with a file in /etc/sudoers.d, you can choose between a lintian error bad-perm-for-file-in-etc-sudoers.d 0660 != 0440, or generate the file with the expected
withPerms "0440"
and have the second build fail with a (misleading) java.io.FileNotFoundException: ... (Permission denied). Looks like the target directory gets reused without cleanup between builds.The text was updated successfully, but these errors were encountered: