Red Hat Bugzilla – Bug 253996
Sabayon ignores mandatory attribute for files
Last modified: 2015-07-13 15:33:14 EDT
Description of problem:
Due to a bug in handling booleans sabayon ignores mandatory flag when applying
profiles. All files are treated as mandatory and they overwrite already present
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a sabayon profile with a file, say (excerpt from metadata):
<file path=".gnome2/mail-notification/mailboxes.xml" timestamp="1186147559"
<attribute name="mandatory" value="False"/>
2. Apply profile
3. Change above file
4. Apply profile again
5. Notice that the file got reset
Profile overwrites already present file every time.
Should not overwrite files when they are not marked as mandatory=True
Bug in handling bool(string). Patch attached and pretty self explanatory.
Created attachment 168899 [details]
Patch fixing bad conversion of string into boolean.
This patch has been applied upstream in revision 911 as reported by a community
Not sure which revision you are referring to but couldn't find any fixes on
cvs.gnome.org/viewcvs/sabayon though maybe it was fixed in a different fashion.
Also the fix is not in RHEL 5.1 - had to add the above patch to prevent user
config files from being overwritten.
Doah - please ignore the last comment - didn't notice they switched to
subversion and was looking at CVS :(... Sorry about that - Heath is absolutely
correct - the fix is indeed in the sabayon subversion repo.
I believe this will be fixed in sabayon-2.12.4-6.el5 since we basically did rebase sabayon in order to fix bug 442132 which also includes the fix reported in comment #1.
Once the update will be published, I will provide more information.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).