Package: src:ruby-ncurses Version: 1.4.13-1 Severity: serious Tags: ftbfs forky sid
Dear maintainer: During a rebuild of all packages in unstable, this package failed to build. Below you will find the last part of the build log (probably the most relevant part, but not necessarily). If required, the full build log is available here: https://people.debian.org/~sanvila/build-logs/202607/ About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages. If you cannot reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and add an affects on src:ruby-ncurses, so that this is still visible in the BTS web page for this package. Thanks. -------------------------------------------------------------------------------- [...] debian/rules clean dh clean --buildsystem=ruby --with ruby dh: warning: Implicitly activating single-binary dh addon for backwards compatibility. In compat 14+, dh: warning: this fallback will *not* happen automatically via dh_auto_install will instead use a dh: warning: different default for --destdir unless the single-binary add-on is active, dh: warning: which can cause the source to produce an empty binary package dh: warning: dh: warning: To keep the existing behaviour (compat 13), please activate the single-binary addon explicitly. dh: warning: This can be done by adding "dh-sequence-single-binary" to Build-Depends or passing dh: warning: --with=single-binary to dh. dh: warning: dh: warning: If you have solved this issue differently (e.g., by passing --destdir explicitly to dh: warning: dh_auto_install or not using dh_auto_install at all) and want to silence this warning dh: warning: without activating the addon, you can do that by passing --without=single-binary to dh dh: warning: to explicitly acknowledge the change. dh: warning: dh: warning: Please see the description of the "single-binary" in "man dh" for more details of what dh: warning: it does and why this is changing from implicit behaviour to explicitly opt-in. dh_auto_clean -O--buildsystem=ruby dh_ruby --clean Invalid gemspec in [ncursesw.gemspec.gem2deb]: undefined method `has_rdoc=' for an instance of Gem::Specification ncursesw.gemspec:3: warning: already initialized constant Gem::Specification::SUMMARY ncursesw.gemspec.gem2deb:3: warning: previous definition of SUMMARY was here Invalid gemspec in [ncursesw.gemspec]: undefined method `has_rdoc=' for an instance of Gem::Specification /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:135:in `load_gemspec': E: cannot load gemspec ncursesw.gemspec (RuntimeError) from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:37:in `block in initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:36:in `chdir' from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:36:in `initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `new' from /usr/lib/ruby/vendor_ruby/gem2deb/installer.rb:24:in `initialize' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:228:in `new' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:228:in `block in installers' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:227:in `map' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:227:in `installers' from /usr/lib/ruby/vendor_ruby/gem2deb/dh_ruby.rb:121:in `clean' from /usr/bin/dh_ruby:91:in `<main>' dh_auto_clean: error: dh_ruby --clean returned exit code 1 make: *** [debian/rules:6: clean] Error 25 dpkg-buildpackage: error: debian/rules clean subprocess failed with exit status 2 -------------------------------------------------------------------------------- _______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
