Aaron M. Ucko
2017-07-23 15:33:55 UTC
Package: jruby
Version: 1.7.26-1
Severity: important
Control: affects -1 ruby-psych
jruby's dependency on ruby-psych is satisfiable only on amd64 because
ruby-psych is new but already build-depends on jruby, and as such
indirectly on itself. You could address the immediate problem by
temporarily rebundling ruby-psych until all architectures (ideally
including the non-release ones) have had time to build the separate
ruby-psych package. However, this circularity would still be problematic
when bootstrapping new architectures, or if it ever became necessary to
upgrade both packages in lockstep for some reason.
As such, a better solution would be to split the architecture-independent
portions of ruby-psych into a separate binary package and have jruby
depend on that rather than on the full ruby-psych package, since it
presumably has no need for an extension built for the traditional C ruby
implementation.
Could you please take a look? (I'm reporting this bug against jruby
because you'll need to make changes to its packaging regardless.)
Thanks!
Version: 1.7.26-1
Severity: important
Control: affects -1 ruby-psych
jruby's dependency on ruby-psych is satisfiable only on amd64 because
ruby-psych is new but already build-depends on jruby, and as such
indirectly on itself. You could address the immediate problem by
temporarily rebundling ruby-psych until all architectures (ideally
including the non-release ones) have had time to build the separate
ruby-psych package. However, this circularity would still be problematic
when bootstrapping new architectures, or if it ever became necessary to
upgrade both packages in lockstep for some reason.
As such, a better solution would be to split the architecture-independent
portions of ruby-psych into a separate binary package and have jruby
depend on that rather than on the full ruby-psych package, since it
presumably has no need for an extension built for the traditional C ruby
implementation.
Could you please take a look? (I'm reporting this bug against jruby
because you'll need to make changes to its packaging regardless.)
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?***@monk.mit.edu
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?***@monk.mit.edu