Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=572512 --- Comment #12 from Mamoru Tasaka <mtasaka@xxxxxxxxxxxxxxxxxxx> 2010-04-02 13:37:30 EDT --- (In reply to comment #11) > > I guess changing "optimize" "debug" option to honor Fedora specific > > compilation flags will make debuginfor rpm being correctly created. > I'm not sure on what to do here... I'm not used to java, but I'm working on > this packages to satisfy some dependencies. If this kind of chages are beyond > my skills, is there a problem if a drop this debuginfo package? - Rather, honoring Fedora specific compilation flags is mandatory (as written in https://fedoraproject.org/wiki/Packaging/Guidelines#Compiler_flags ) With Fedora specific compilation flags correctly honored, debuginfo rpm should be correctly generated. Note that you can check what "Fedora specific compilation flags" are by $ rpm --eval %optflags -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review