https://bugzilla.novell.com/show_bug.cgi?id=652818 https://bugzilla.novell.com/show_bug.cgi?id=652818#c1 --- Comment #1 from Vincent Untz 2010-11-11 15:25:27 UTC --- Yeah, that's because the way the script works, it would likely break the spec file (by adding/removing stuff from the %if) if we tried to interpret the content of %if. So I went the safe way... Thinking about it, I'm event not sure what would be the correct behavior in your case: some people would want the %if to be at the end of the BuildRequires, while some others would want the BuildRequires to be alphabetically sorted anyway, even if it means having multiple %if. Anyway. Correctly fixing this would require the internal rewrite to have a real spec file parser. Pavol, were you convinced by your tests with the rpm python bindings? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=652818 https://bugzilla.novell.com/show_bug.cgi?id=652818#c Pavol Rusnak changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |prusnak@opensuse.org AssignedTo|prusnak@suse.com |vuntz@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=652818 https://bugzilla.novell.com/show_bug.cgi?id=652818#c4 Tomas Cech changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #4 from Tomas Cech 2014-01-26 21:59:57 CET --- I believe that this issue is no longer present in spec-cleaner. %if BuildRequires..%endif section is moved to the after unconditional BuildRequires. Summary is placed correctly as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.