[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: mass bug report filing, update of the Ruby-Version attribute is needed for jessie

On Thu, May 01, 2014 at 10:51:15PM +0200, Matthias Klose wrote:
> Currently more than 300 packages have a Ruby-Version attribute which lists
> either ruby1.8 or ruby1.9, but neither ruby2.0 or ruby2.1.  When using these
> packages as gems, then the gem is not found.  The recent ruby gems
> infrastructure now uses 'all' as this Ruby-Version attribute for architecture
> independent packages, so after an one time update these packages should be
> usable as gems for future ruby versions as well.  Most of these packages only
> build architecture independent packages, so source full uploads are needed.
> Not sure if all of these packages are used as gems, but at least for these the
> bug severity should be serious, maybe less for the others.
> $ cat /var/lib/apt/lists/*Packages | grep-dctrl -n -sSource:Package
> -FRuby-Versions -r 'ruby1.[89]' | sort -u | wc -l
> 366

Note that the real issue is not the contents of the Ruby-Versions field,
which is not used for anything other than this very type of checking.

The real problem is the fact that their gemspecs (distro-agnostic
metadata that tells Ruby which packages are installed) are not installed
in a place that will be picked up by newer versions of Ruby, so yes they
need a sourcefull upload, but only if they actually ship gemspecs.

Looking for packages that still ship gemspecs for 1.8 or 1.9.1, the number is
slightly lower/

$ (apt-file search /usr/share/rubygems-integration/1.8; apt-file search /usr/share/rubygems-integration/1.9.1) | cut -d : -f 1 | sort -u | wc -l

Antonio Terceiro <terceiro@debian.org>

Attachment: signature.asc
Description: Digital signature

Reply to: