Your message dated Mon, 30 Apr 2018 22:30:29 +0000 with message-id <e1fdhjv-0002pe...@fasolo.debian.org> and subject line Bug#897187: Removed package(s) from unstable has caused the Debian Bug report #832020, regarding ruby2.3: ruby2.3_2.3.1-5 does not build with latest gdbm 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.) -- 832020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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?
--- End Message ---
--- Begin Message ---Version: 2.3.6-2+rm Dear submitter, as the package ruby2.3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/897187 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
