Your message dated Thu, 13 Jul 2017 21:18:56 -0300
with message-id <[email protected]>
and subject line Re: Bug#867599: gem2deb fails to install pure ruby part when a
gem has both pure ruby and native libs
has caused the Debian Bug report #867599,
regarding gem2deb: support installing Ruby code not in lib/
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 [email protected]
immediately.)
--
867599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867599
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: gem2deb
version: 0.34
gem2deb is not installing the pure ruby libraries of grpc (ruby-grpc is
in alioth) and tests fail.
──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.3 from debian/ruby-tests.rake
│
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/<<PKGBUILDDIR>>/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/2.3.0:.
GEM_PATH=debian/ruby-grpc/usr/share/rubygems-integration/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.3 /usr/bin/rspec --pattern
./src/ruby/spec/\*\*/\*_spec.rb --format documentation
/<<PKGBUILDDIR>>/src/ruby/lib/grpc/errors.rb:48:in `<class:BadStatus>':
uninitialized constant GRPC::Core (NameError)
from /<<PKGBUILDDIR>>/src/ruby/lib/grpc/errors.rb:45:in `<module:GRPC>'
from /<<PKGBUILDDIR>>/src/ruby/lib/grpc/errors.rb:33:in `<top
(required)>'
from /<<PKGBUILDDIR>>/src/ruby/lib/grpc.rb:32:in `require_relative'
from /<<PKGBUILDDIR>>/src/ruby/lib/grpc.rb:32:in `<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /<<PKGBUILDDIR>>/src/ruby/spec/call_credentials_spec.rb:30:in
`<top (required)>'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in
`load'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1435:in
`block in load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in
`each'
from /usr/lib/ruby/vendor_ruby/rspec/core/configuration.rb:1433:in
`load_spec_files'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:100:in `setup'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:86:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:71:in `run'
from /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:45:in `invoke'
from /usr/bin/rspec:4:in `<main>'
/usr/bin/ruby2.3 /usr/bin/rspec --pattern
./src/ruby/spec/\*\*/\*_spec.rb --format documentation failed
ERROR: Test "ruby2.3" failed. Exiting.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Wed, Jul 12, 2017 at 08:12:17PM +0530, Pirate Praveen wrote:
> On Mon, 10 Jul 2017 01:22:39 +0530 Pirate Praveen
> <[email protected]> wrote:
> > make[2]: *** No rule to make target
> > '/home/pravi/forge/debian/gitlab/grpc-1.3.2/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0/gems/grpc-1.3.2/src/ruby/ext/grpc/libs/opt/libgrpc.a'.
> > Stop.
>
> This is happening because Makefile was not copied to
> /home/pravi/forge/debian/gitlab/grpc-1.3.2/debian/ruby-grpc/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0/gems/grpc-1.3.2/
> even though grpc.gemspec includes the Makefile.
>
> after adding the following line to debian/rules,
> export DH_RUBY_GEM_INSTALL_WHITELIST_APPEND=Makefile
>
> build is succeeding
Cool - and yeah, that makes sense.
so, there is nothing to be fixed in gem2deb. as documented in
dh_ruby(1):
Note that by default all top-level files are automatically
blacklisted, except VERSION* which is used by some packages. If you
need a top-level file to be installed, you need to whitelist it.
Unfortunately this blacklisting/whitelisting is needed to make sure the
contents of binary packages produced with --gem-install is minimally
sane.
So, FTR: anyone that needs to handle packages that are non-standard,
such as Ruby code not under lib/, should 1) use --gem-install and 2) pay
attention to the documented blacklisting/whitelisting used by
--gem-install.
signature.asc
Description: PGP signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
