Your message dated Wed, 18 Nov 2015 10:41:20 +0100
with message-id <564c47c0.8010...@balintreczey.hu>
and subject line Re: ruby-bert ftbfs in unstable
has caused the Debian Bug report #798534,
regarding ruby-bert ftbfs in unstable
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.)


-- 
798534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-bert
Version: 1.1.6-1
Severity: serious
Tags: sid stretch

[...]
┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.1 from debian/ruby-test-files.yaml                       │
└──────────────────────────────────────────────────────────────────────────────┘

RUBYLIB=/home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0:/home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert/usr/lib/ruby/vendor_ruby:.
ruby2.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\
\|f\|\ require\ f\ \}
*** Error in `ruby2.1': munmap_chunk(): invalid pointer: 0x00007fcc26f12e10 ***
/usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:126:in `exit': no implicit
conversion from nil to integer (TypeError)
        from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:126:in `run'
        from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:102:in `run_ruby'
        from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:180:in 
`do_run_tests'
        from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:70:in `run_tests'
        from /usr/bin/gem2deb-test-runner:53:in `<main>'
ERROR: Test "ruby2.1" failed. Exiting.
dh_auto_install: dh_ruby --install
/home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert returned exit code 1
debian/rules:15: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2

--- End Message ---
--- Begin Message ---
On Thu, 10 Sep 2015 13:40:21 +0200 Matthias Klose <d...@debian.org> wrote:
> Package: src:ruby-bert
> Version: 1.1.6-1
> Severity: serious
> Tags: sid stretch
> 
> [...]
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Run tests for ruby2.1 from debian/ruby-test-files.yaml                    
>    │
> └──────────────────────────────────────────────────────────────────────────────┘
> 
> RUBYLIB=/home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.1.0:/home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert/usr/lib/ruby/vendor_ruby:.
> ruby2.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\
> \|f\|\ require\ f\ \}
> *** Error in `ruby2.1': munmap_chunk(): invalid pointer: 0x00007fcc26f12e10 
> ***
> /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:126:in `exit': no implicit
> conversion from nil to integer (TypeError)
>         from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:126:in `run'
>         from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:102:in 
> `run_ruby'
>         from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:180:in 
> `do_run_tests'
>         from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:70:in 
> `run_tests'
>         from /usr/bin/gem2deb-test-runner:53:in `<main>'
> ERROR: Test "ruby2.1" failed. Exiting.
> dh_auto_install: dh_ruby --install
> /home/packages/tmp/ruby-bert-1.1.6/debian/ruby-bert returned exit code 1
> debian/rules:15: recipe for target 'binary' failed
> make: *** [binary] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
It seems the FTBS is caused by Ruby 2.1. Now with the migration to Ruby
2.2 in unstable ruby-bert builds again.

Cheers,
Balint

--- End Message ---

Reply via email to