[DSE-Dev] Bug#720220: libsemanage: FTBFS with ruby2.0: semanageswig_ruby_wrap.c:832:18: fatal error: ruby.h: No such file or directory

[David Suárez]

Source: libsemanage
Version: 2.1.10-2
Severity: important
Tags: jessie sid
User: debian-ruby at lists.debian.org
Usertags: ruby2-ftbfs-20130818 ruby2-ftbfs
Justification: FTBFS on amd64 with ruby2.0

Hi,

During a rebuild of all packages that build depends on gem2deb
using the new ruby2.0 interpreter, your package failed to build
on amd64.

Relevant part (hopefully):
> cc -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I../include -I/usr/include -D_GNU_SOURCE  -Wno-error -Wno-unused-but-set-variable -Wno-unused-variable -Wno-shadow -Wno-unused-parameter -I/usr/lib/ruby/1.8// -fPIC -DSHARED -c -o ruby1.8semanageswig_ruby_wrap.lo semanageswig_ruby_wrap.c
> make[2]: ruby1.8: Command not found
> semanageswig_ruby_wrap.c:832:18: fatal error: ruby.h: No such file or directory
>  #include <ruby.h>
>                   ^
> compilation terminated.
> make[2]: *** [ruby1.8semanageswig_ruby_wrap.lo] Error 1

The full build log is available from:
  http://aws-logs.debian.net/ftbfs-logs/ruby2.0/libsemanage_2.1.10-2_unstable_ruby2.log

This build is part of an effort to add gem2deb support for ruby2.0.
Information about is available at https://wiki.debian.org/Teams/Ruby/Jessie.

About the rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services,
using a clean, minimal and up-to-date chroot, plus gem2deb and ruby2.0 packages from
the repository at http://people.debian.org/~terceiro/packages/. The gem2deb version
in that repository does not pull ruby1.8 as a dependency anymore, and builds packages
against ruby1.9.1 and ruby2.0. Every failed build was retried once to eliminate random
failures.

The version of gem2deb used for this rebuild, as well as ruby2.0,
will be uploaded to unstable soon.