[DRE-maint] Bug#837672: autopkgtest fails even when there are multiple gemspec files and DH_RUBY_GEMSPEC is set

Antonio Terceiro terceiro at debian.org
Tue Sep 13 13:08:14 UTC 2016


On Tue, Sep 13, 2016 at 05:37:20PM +0530, Pirate Praveen wrote:
> package: gem2deb-test-runner:
> version: 0.32
> 
> adt-run [09:07:02]: test command1: gem2deb-test-runner --autopkgtest
> --check-dependencies 2>&1
> adt-run [09:07:02]: test command1: [-----------------------
> 
> ┌──────────────────────────────────────────────────────────────────────────────┐
> │ Checking Rubygems dependency resolution on ruby2.3
>> └──────────────────────────────────────────────────────────────────────────────┘
> 
> /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:120:in `load_gemspec':
> More than one .gemspec file in this directory:
> concurrent-ruby-edge.gemspec, concurrent-ruby-ext.gemspec,
> concurrent-ruby.gemspec (RuntimeError)
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `block in
> initialize'
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `chdir'
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:32:in `initialize'
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in `new'
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:77:in
> `do_check_dependencies'
> 	from /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb:67:in `run_tests'
> 	from /usr/bin/gem2deb-test-runner:61:in `<main>'
> adt-run [09:07:02]: test command1: -----------------------]
> adt-run [09:07:02]: test command1:  - - - - - - - - - - results - - - -
> - - - - - -
> command1             FAIL non-zero exit status 1
> adt-run [09:07:02]: @@@@@@@@@@@@@@@@@@@@ summary
> command1             FAIL non-zero exit status 1
> 
> 
> Full log
> https://ci.debian.net/data/packages/unstable/amd64/r/ruby-concurrent/latest-autopkgtest/log.gz

you can't expect gem2deb-test-runner to pick up DH_RUBY_GEMSPEC being set in
debian/rules when running under autopkgtest ... but we should probably have a
DRY way to declare that. maybe we could expec debian/$pkg.gemspec to be a
symlink to the _correct_ gemspec, or maybe some other way. Either way I cannot
promise a solution for that any time soon.

if you want to work around that for now, I suggest setting DH_RUBY_GEMSPEC in
an explicit debian/tests/control ...

Test-Command: DH_RUBY_GEMSPEC=foo.gemspec gem2deb-test-runner --autopkgtest --check-dependencies 2>&1


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20160913/86da34fd/attachment-0001.sig>


More information about the Pkg-ruby-extras-maintainers mailing list