, I'd like to revisit this issue during "buster" development
> cycle.
Sure. I'd suggest coming to the next ruby sprint, whenever that will
be. Discussing the correct dependencies is a lot easier with a
whiteboard.
Cheers,
--
christian hofstaedtler <z...@debian.org>
__
This is
by modules with Multi-Arch: foreign and that
> tracker.d.o will tell you where (e.g. ruby-rd).
Noted. A number of dependency cycles would also go away, I imagine.
** Plus, ruby-interpreter serves as an escape hatch for
bootstrapping rubyX.Y on new archs.
*** This is done using code in dh_ruby.
ch indicates that jruby should simply drop the provides.
I do not think it is feasible today to ship a ruby implementation
that provides ruby-interpreter without (some form of) support in
gem2deb.
Best is probably to just drop the Provides in jruby.
--
,''`. Christian Hofstaedtler
-bash: /usr/bin/rake: /usr/bin/ruby: bad interpreter: No such file or
> directory
This is clearly jruby violating its advertisement of
ruby-interpreter. Reassigning.
Thanks,
--
,''`. Christian Hofstaedtler <z...@debian.org>
: :' : Debian Developer
`. `' 7D1A CFFA D9E0
-cpp
Carl Worth cwo...@debian.org
notmuch
ruby-mail (U)
ruby-treetop (U)
Carlos Zuferri ch...@altorricon.com
live-manual (U)
Christian Hofstaedtler z...@debian.org
bundler (U)
gist (U)
ruby-docile (U)
ruby-mechanize (U)
ruby-rack1.4 (U)
ruby-thor (U)
ruby2.0 (U
(see #730095), or any
of the existing FTBFS bugs:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ruby-defaults-2.0;users=debian-r...@lists.debian.org
Where to get help
-
Please see https://wiki.debian.org/Teams/Ruby
Thank you for your attention.
--
,''`. Christian
change your package to use Ruby 1.9 or 2.0. The ruby
metapackage depends on the current default interpreter version.
Thanks,
--
,''`. Christian Hofstaedtler z...@debian.org
: :' : Debian Developer
`. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03
`-
__
This is the maintainer address
7 matches
Mail list logo
