https://bugzilla.redhat.com/show_bug.cgi?id=808350
Daniel E. Wilson <d...@bureau-13.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |needinfo?
--- Comment #9 from Daniel E. Wilson <d...@bureau-13.org> ---
SPEC File URL: http://web.cecs.pdx.edu/~danw/racket.spec
SRPM File URL: http://web.cecs.pdx.edu/~danw/racket-5.2.1-2.fc17.src.rpm
I have created a new source package and spec file.
The URL tag has been corrected. I am more used to the Gentoo Portage system
that uses a similar URL tag to tell the emerge program where to fetch the file
from. The %defattr tags were also removed from the spec file.
The library bundling issue has been corrected by adding a dependency for libffi
and adding an option to the configure command to force racket to use the
library already installed in the system rather than the one packaged with
racket. The other libraries mentioned in bug 676124 appear to have been
replaced with scheme code long before this version of racket was released. At
least that is what the comment left by Eli Barzilay in bug 676124 would
indicate.
The RPM debug package is still removed because the mred program is a
stand-alone scheme program that has been turned into an executable. This
process involves embedding the scheme code into a copy of the mzscheme
executable. The result is two executable programs with the same build id.
This does not strike me as a bug in RPM but rather a use case that was not
considered when the build id rule was created. Unless someone knows how to
change a build id number in an executable the RPM debug package is going to
stay disabled.
What do you mean this package does not build with the mandatory set of compiler
flags? As far as I can tell if CFLAGS is set by RPM then the racket build
process should use them.
The new package completed the build but will not install during the mock build
process. Looking at the build.log file I can't even tell what running when the
process fails. The build log is at
http://kojipkgs.fedoraproject.org//work/tasks/705/4240705/build.log but the
relevant lines are:
make[1]: Leaving directory `/builddir/build/BUILD/racket-5.2.1/src/build'
make[1]: *** [install-3m] Aborted
make: *** [install] Error 2
make: Leaving directory `/builddir/build/BUILD/racket-5.2.1/src/build'
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.nZ0dpY (%install)
Bad exit status from /var/tmp/rpm-tmp.nZ0dpY (%install)
Child returncode was: 1
EXCEPTION: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bb --target i686 --nodeps
builddir/build/SPECS/racket.spec']
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line
70, in trace
result = func(*args, **kw)
File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 352, in do
raise mockbuild.exception.Error, ("Command failed. See logs for output.\n
# %s" % (command,), child.returncode)
Error: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bb --target i686 --nodeps
builddir/build/SPECS/racket.spec']
LEAVE do --> EXCEPTION RAISED
The build process works fine on my box so I have no way to track this failure
down when I can't even see the command that is failing. I have disabled the
x86_64 architecture for the moment to simplify debugging since my Fedora box is
i686. Unless anyone has any idea how to get the information I need to fix this
problem out of the mock build system this is as far as I can go.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/package-review
