[DRE-maint] Bug#665262: ruby-childprocess: FTBFS: /usr/lib/ruby/vendor_ruby/rspec/core/shared_example_group.rb:64:in `ensure_shared_example_group_name_not_taken': Shared example group 'a platform that provides the child's pid' already exists (ArgumentError)
Lucas Nussbaum
lucas at lucas-nussbaum.net
Thu Mar 22 16:44:06 UTC 2012
Source: ruby-childprocess
Version: 0.3.1-1
Severity: serious
Tags: wheezy sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20120321 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> fakeroot debian/rules binary
> dh binary --buildsystem=ruby --with ruby
> dh_testroot -O--buildsystem=ruby
> dh_prep -O--buildsystem=ruby
> dh_installdirs -O--buildsystem=ruby
> dh_auto_install -O--buildsystem=ruby
> Entering dh_ruby --install
> install -d /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby
> install -D -m644 lib/childprocess/unix.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix.rb
> install -D -m644 lib/childprocess/jruby/io.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/jruby/io.rb
> install -D -m644 lib/childprocess/jruby/process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/jruby/process.rb
> install -D -m644 lib/childprocess/jruby/pump.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/jruby/pump.rb
> install -D -m644 lib/childprocess/unix/posix_spawn_process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/posix_spawn_process.rb
> install -D -m644 lib/childprocess/unix/fork_exec_process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/fork_exec_process.rb
> install -D -m644 lib/childprocess/unix/io.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/io.rb
> install -D -m644 lib/childprocess/unix/process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/process.rb
> install -D -m644 lib/childprocess/unix/lib.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/lib.rb
> install -D -m644 lib/childprocess/unix/platform/i386-solaris.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/platform/i386-solaris.rb
> install -D -m644 lib/childprocess/unix/platform/x86_64-linux.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/platform/x86_64-linux.rb
> install -D -m644 lib/childprocess/unix/platform/i386-linux.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/platform/i386-linux.rb
> install -D -m644 lib/childprocess/unix/platform/x86_64-macosx.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/unix/platform/x86_64-macosx.rb
> install -D -m644 lib/childprocess/abstract_process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/abstract_process.rb
> install -D -m644 lib/childprocess/errors.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/errors.rb
> install -D -m644 lib/childprocess/abstract_io.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/abstract_io.rb
> install -D -m644 lib/childprocess/tools/generator.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/tools/generator.rb
> install -D -m644 lib/childprocess/jruby.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/jruby.rb
> install -D -m644 lib/childprocess/windows.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows.rb
> install -D -m644 lib/childprocess/version.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/version.rb
> install -D -m644 lib/childprocess/windows/structs.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/structs.rb
> install -D -m644 lib/childprocess/windows/io.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/io.rb
> install -D -m644 lib/childprocess/windows/process.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/process.rb
> install -D -m644 lib/childprocess/windows/process_builder.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/process_builder.rb
> install -D -m644 lib/childprocess/windows/lib.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/lib.rb
> install -D -m644 lib/childprocess/windows/handle.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess/windows/handle.rb
> install -D -m644 lib/childprocess.rb /«PKGBUILDDIR»/debian/ruby-childprocess/usr/lib/ruby/vendor_ruby/childprocess.rb
> /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb
> /usr/lib/ruby/vendor_ruby/rspec/core/shared_example_group.rb:64:in `ensure_shared_example_group_name_not_taken': Shared example group 'a platform that provides the child's pid' already exists (ArgumentError)
> from /usr/lib/ruby/vendor_ruby/rspec/core/shared_example_group.rb:15:in `shared_examples_for'
> from ./spec/pid_behavior.rb:3
> from -e:1:in `require'
> from -e:1
> from -e:1:in `each'
> from -e:1
> ERROR: Test "ruby1.8" failed. Exiting.
> dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/ruby-childprocess returned exit code 1
> make: *** [binary] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/21/ruby-childprocess_0.3.1-1.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
More information about the Pkg-ruby-extras-maintainers
mailing list