On Fri, Apr 10, 2009 at 2:33 AM, Mat Booth wrote:
On Wed, Apr 8, 2009 at 9:07 PM, Ville Skyttä wrote:
Hello,
Quite a few packages that produce *-debuginfo without sources have crept again in rawhide. See https://fedoraproject.org/wiki/Packaging/Debuginfo for possible reasons, the most usual of which in my (past, haven't checked this batch that closely) experience is failure to honor $RPM_OPT_FLAGS during build which can also mean that the default security related compiler flags aren't being applied either.
List of such packages identified by my debuginfo-check.py is attached (ownership info generated with Thorsten's fedoradev-pkgowners). I intend to submit debuginfo-check.py to yum-utils (probably as debugrepo-check) and have added a similar check in upstream svn rpmlint, hopefully with these additions people will start noticing the issues easier.
Maintainer Package Co-maintainers
mbooth brazil (none)
This is a Java package that is AOT compiled for GCJ so the RPM flags are beyond my control. Compilation is done by the aot-compile-rpm script from the java-1.5.0-gcj-devel package. What do I need to do (if anything)?
Do you see error messages during find-debuginfo stage, such as in this bug? https://bugzilla.redhat.com/show_bug.cgi?id=472292
If so, sometimes (underlined), passing -g to javac helps. If you are using ant, try to add debug="on" on the javac part of your build.xml
Orcan