-
Notifications
You must be signed in to change notification settings - Fork 25
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
RPM build warnings for "File listed twice" #332
Comments
ok, so this is coming from manageiq-core
We define a general rule on the first line (so we don't miss any). These are all owned by working on a fix that does not need to list every file |
Overview ======== Fixes ManageIQ#332 The goal is to remove a warning: ``` warning: File listed twice: /var/www/miq/vmdb/certs (a few hundred files do this) ``` Before ====== ``` %defattr(-,root,root,-) %{app_root} %attr(-,manageiq,manageiq) %{app_root}/certs ``` We stated that we included all files recursively under app_root (/var/www/miq/vmdb). Then we stated a few directories (with different privileges) under app_root. So we ended up with duplicates. Why? ==== Most app_root subdirectories are owned by root, which is the default, so using the app_root line works. There are a few config directories that need to be editable and owned by the end user. That is why they are listed with the `%attr()` syntax. After ===== We explicitly listed each folder in the rails root. I would have liked to keep on using the app_root rule so any additional files would be auto added. This is tricky because we tend to not debug the directory listing of the `rpm` So there is a good chance that we will add a directory to app_root (vmdb / manageiq-core root) and will think it is all set but will fail on the appliance.
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
Not sure why this is happening, but opening a bug. Decided to not put this in #200 since that is more focused on the other WARNING entries.
The text was updated successfully, but these errors were encountered: