[DRE-maint] Bug#685952: ruby-gherkin: does not build on several achitecture, blocking newer cucumber

[Antonio Terceiro]

Package: ruby-gherkin
Version: 2.11.1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Subject: ruby-gherkin: FTBFS on armel, armhf, powerpc, s390, and s390x
X-Debbugs-CC: debian-ruby at lists.debian.org

Hi,

shawn escreveu isso aí:
> On Wed, 2012-08-08 at 17:19 +0200, Cédric Boutillier wrote: 
> > Hi!
> > 
> > ruby-gherkin does not build on the current architectures: armel, armhf,
> > powerpc, s390 and s390x. Since I do not have access to any of these
> > architectures, I was wondering if someone else had any clue about why
> > the compilation fails (the failing tests are the same on all these
> > architectures).
> 
> Without having looked at the code, this list of failing architectures
> makes me almost certain it is a problem of assuming the C type "char" is
> signed. The easy fix is to change the offending "char" declaration
> "signed char".
> 
> Look at this table:
> 
> http://wiki.debian.org/ArchitectureSpecificsMemo 
> > 
> > See 
> >   https://buildd.debian.org/status/package.php?p=ruby-gherkin
> > for details.
> > 
> > This build failure is responsible for not having the new version of
> > ruby-gherkin in testing, which is in turn blocking cucumber...
> > 
> > Thanks in advance for your insights.
> > 
> > Cédric

I requested the installation of the build deps for ruby-gherkin in a
armhf porterbox to be able to investigate. This far into the freeze,
it's very unlikely that we will get this newer ruby-gherkin and the
newer cucumber into wheezy, though.

-- 
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20120826/54428892/attachment.pgp>