Bug#832020: ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm

2018-02-01 Thread Gianfranco Costamagna
control: severity -1 serious

On Thu, 21 Jul 2016 14:56:57 +0300 Dmitry Bogatov  wrote:
> Source: ruby2.3
> Version: 2.3.1-5
> Severity: important
> 
> Dear Maintainer,
> 
> 
> Latest version of libgdbm(1.12) in experimental have new SONAME and
> separates away dbm_* interface in libgdbm-compat4 binary package.
> 
> As such, it is transition, and I have to make sure, that reverse
> dependencies are okay. Most of them was trivial to fix -- just build-depend
> on libgdbm-compat-dev, but ruby2.3 proved to be harder.
> 
> Here is snippet from test suite, when building aganist gdbm/experimental:
> 
>   TestGDBM#test_s_open_nolock:
>   GDBMError: Bad magic number
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:190:in `open'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:190:in `block 
> (2 levels) in test_s_open_nolock'
>   
> /home/user/stuff/ruby2.3-2.3.1/test/lib/test/unit/assertions.rb:171:in 
> `assert_nothing_raised'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:189:in `block 
> in test_s_open_nolock'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:152:in `block 
> in open_db_child'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:149:in `popen'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:149:in 
> `open_db_child'
>   /home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:188:in 
> `test_s_open_nolock'
> 
> I barely read Ruby and it is hard for me to debug this issue, and, as
> ruby package maintainer, you are more competent than me at it. Would
> you be so kind to try build ruby aganist gdbm/experimental and see why
> this test fails?
> 
> 

it is now serious

G.



signature.asc
Description: OpenPGP digital signature


Bug#832020: ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm

2016-07-21 Thread Dmitry Bogatov
Source: ruby2.3
Version: 2.3.1-5
Severity: important

Dear Maintainer,


Latest version of libgdbm(1.12) in experimental have new SONAME and
separates away dbm_* interface in libgdbm-compat4 binary package.

As such, it is transition, and I have to make sure, that reverse
dependencies are okay. Most of them was trivial to fix -- just build-depend
on libgdbm-compat-dev, but ruby2.3 proved to be harder.

Here is snippet from test suite, when building aganist gdbm/experimental:

TestGDBM#test_s_open_nolock:
GDBMError: Bad magic number
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:190:in `open'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:190:in `block 
(2 levels) in test_s_open_nolock'

/home/user/stuff/ruby2.3-2.3.1/test/lib/test/unit/assertions.rb:171:in 
`assert_nothing_raised'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:189:in `block 
in test_s_open_nolock'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:152:in `block 
in open_db_child'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:149:in `popen'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:149:in 
`open_db_child'
/home/user/stuff/ruby2.3-2.3.1/test/gdbm/test_gdbm.rb:188:in 
`test_s_open_nolock'

I barely read Ruby and it is hard for me to debug this issue, and, as
ruby package maintainer, you are more competent than me at it. Would
you be so kind to try build ruby aganist gdbm/experimental and see why
this test fails?