Source: ruby-pathname2
Version: 1.8.0-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest

Hi Michael,

The ruby-pathname2 package has been failing the generic ruby module
autopkgtest since the upload of 1.8.0-1, as seen at
<https://ci.debian.net/packages/r/ruby-pathname2/unstable/amd64/>:

Invalid gemspec in [pathname2.gemspec]: uninitialized constant Gem::Specificatio
n::FileList
Did you mean?  FileUtils
               FileTest
Invalid gemspec in [pathname2.gemspec.gem2deb]: uninitialized constant 
Gem::Specification::FileList
Did you mean?  FileUtils
               FileTest
/usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:124:in `load_gemspec': E: cannot 
load gemspec pathname2.gemspec (RuntimeError)
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:34:in `block in 
initialize'
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33:in `chdir'
        from /usr/lib/ruby/vendor_ruby/gem2deb/metadata.rb:33: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>'

This problem is reproducible for me locally, and is not reproducible with
the previous version of ruby-pathname2, 1.7.4-1 (so this is not a regression
in the gem2deb-test-runner, but in the ruby-pathname2 package).  The problem
has also been reproduced on the Ubuntu autopkgtest infrastructure:

  http://autopkgtest.ubuntu.com/packages/r/ruby-pathname2/

Unfortunately Debian does not consider a regressed autopkgtest a blocker for
testing (which would be useful to help us improve the quality of the
release), but Ubuntu does; so this regression has blocked the new
ruby-pathname2 package from inclusion in Ubuntu 17.04 and will continue to
block it from reaching an Ubuntu release until fixed.

I don't speak ruby so I don't know if this bug has a serious impact on the
package at runtime; it appears that
/usr/share/rubygems-integration/all/specifications/pathname2-1.8.0.gemspec
and pathname2.gemspec are significantly different, and if I copy the
installed one to the source tree the test then passes.  So maybe that's all
that's required to fix this?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
slanga...@ubuntu.com                                     vor...@debian.org

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers

Reply via email to