* Paul Wise [140512 09:13]:
> Is this something I should file a bug about or will it be handled during
> the ruby2.0/ruby2.1 transitions?
BTW, there was already some discussion about this on d-d:
https://lists.debian.org/debian-devel/2014/05/msg00012.html
--
,''`. Christian Hofstaedtler
: :
On Mon, 2014-05-12 at 09:20 +0200, Christian Hofstaedtler wrote:
> (Most) Packages that need reuploading/fixing can be found by
> inspecting the Ruby-Versions field, if it still says ruby1.8 or
> ruby1.9.1 then it's very likely affected.
According to a quick grep of sid main Packages there are 14
Paul,
Let me answer with a summary answer below:
* Paul Wise [140512 09:13]:
> I noted that ruby-term-ansicolor doesn't provide a gemspec file for
> ruby2.0 (just 1.9.1 and 1.8) and doesn't declare this in its
> dependencies. Simply rebuilding ruby-term-ansicolor with a current
> chroot of unsta
Hi all,
I noted that ruby-term-ansicolor doesn't provide a gemspec file for
ruby2.0 (just 1.9.1 and 1.8) and doesn't declare this in its
dependencies. Simply rebuilding ruby-term-ansicolor with a current
chroot of unstable will fix this it seems since it only creates one
gemspec file in the 'all'
4 matches
Mail list logo