Your message dated Sat, 18 May 2013 19:18:11 +0000 with message-id <e1udmdv-0004vj...@franck.debian.org> and subject line Bug#685952: fixed in ruby-gherkin 2.11.1-2 has caused the Debian Bug report #685952, regarding ruby-gherkin: does not build on several achitecture, blocking newer cucumber to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 685952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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-r...@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 <terce...@debian.org>
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Source: ruby-gherkin Source-Version: 2.11.1-2 We believe that the bug you reported is fixed in the latest version of ruby-gherkin, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 685...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro <terce...@debian.org> (supplier of updated ruby-gherkin package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Sat, 18 May 2013 15:24:59 -0300 Source: ruby-gherkin Binary: ruby-gherkin Architecture: source amd64 Version: 2.11.1-2 Distribution: unstable Urgency: low Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintain...@lists.alioth.debian.org> Changed-By: Antonio Terceiro <terce...@debian.org> Description: ruby-gherkin - lexer and parser for the Gherkin language in Ruby Closes: 685952 Changes: ruby-gherkin (2.11.1-2) unstable; urgency=low . * debian/patches/signed_char.patch: force the assumption of signedness for the char type (Closes: #685952) Checksums-Sha1: f49b9f35cf01f154cbb10b04851aeba6e20f6956 1491 ruby-gherkin_2.11.1-2.dsc de3f0e9656210145dedf0d86d347375e683ad942 3986 ruby-gherkin_2.11.1-2.debian.tar.gz 1044112020ddd7db644d8d092f99cf19dbdaee9a 769576 ruby-gherkin_2.11.1-2_amd64.deb Checksums-Sha256: fe164a3768d8a6ffbe26d83972309e293c6f62d370856df445af24c6f87c47c6 1491 ruby-gherkin_2.11.1-2.dsc 9f56a80797562ca99e7bb4b26102125a13167b73ae0073e2e27edf7b5b9eafe4 3986 ruby-gherkin_2.11.1-2.debian.tar.gz 4b7e0f287a1487cf027549099367cb08a7ff5c4445e0d93a6e714bc0c58a916e 769576 ruby-gherkin_2.11.1-2_amd64.deb Files: 7960ce96b5e76b539a9a1872e2f302db 1491 ruby optional ruby-gherkin_2.11.1-2.dsc 6fe4593bb6c2210551d16ff627ad9136 3986 ruby optional ruby-gherkin_2.11.1-2.debian.tar.gz d1784cdbd1118f38fc87e8ac4debd133 769576 ruby optional ruby-gherkin_2.11.1-2_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlGXzI0ACgkQDOM8kQ+cso8OigCff4Xy8tKxc7s5lqgLK/dEbRsZ BvUAn23gGJao+zMY3305I9Ng3kliXnjw =NYbi -----END PGP SIGNATURE-----
--- End Message ---
