Bug#811484: Need mentor for packaging ruby-did-you-mean (RFP #811484)

2016-01-23 Thread Petter Reinholdtsen

I noticed ruby-did-you-mean is uploaded now.  Should ITP #811484 be
closed?

https://tracker.debian.org/pkg/ruby-did-you-mean >

-- 
Happy hacking
Petter Reinholdtsen



Bug#811484: Need mentor for packaging ruby-did-you-mean (RFP #811484)

2016-01-20 Thread Hanno Zulla
Hi Antonio,

first of all, thanks for looking into this.

Yes, you're right, the Sonic Pi source made did_you_mean optional
recently. However, it *is* a component that Sam, the Sonic Pi main
developer, really wants to see included with the software, as it makes
the error messages more helpful for the users.

As you can see in https://github.com/samaaron/sonic-pi/issues/928 we
have already identified all gems that are needed to get the vendor/
directory out of Sonic Pi and thus remove all convenience copies of 3rd
party gem sources from upstream.

We are only missing did_you_mean, hamster (#811390) and wavefile
(#811086) in Debian to proceed packaging Sonic Pi for sid.

> Hi, after out chat on IRC today I have just uploaded
> ruby-did-you-mean

Thank you so much, that's great.

You asked on IRC about the deployment strategy for Sonic Pi. My goal is
to make Sonic Pi debian-compliant and maintain that package on Debian.
Based on that package, I want to make packages ready for Raspbian and
Ubuntu.

The Ubuntu PPA is already the test bed for my current incomplete
packaging attempt. The current state is
https://github.com/deb-pkg-sonic-pi/pkg-sonic-pi - it's not ready for
review and I haven't begun to remove the vendor/ directory there, yet.

ruby2.3 won't come to Raspbian in a long while, so I will have to make
sure that the package works with earlier ruby versions, too. While I can
live with offering ports of dependencies for Sonic Pi, I wouldn't want
to backport the ruby2.3 package to Raspbian just for this. So I'll see
if I can package a did_you_mean 0.10.0 version based on your example
that I can use for those distributions that don't have ruby2.3.

Yes, in the long run, the problem will just go away once the other
distributions ship with ruby2.3.

Thanks again, your help is very appreciated.

Kind regards,

Hanno



Bug#811484: Need mentor for packaging ruby-did-you-mean (RFP #811484)

2016-01-19 Thread Antonio Terceiro
Control: retitle -1 ITP: ruby-did-you-mean -- "did you mean?" experience for 
misspelled code in Ruby.

On Tue, Jan 19, 2016 at 01:43:33PM +0100, Hanno Zulla wrote:
> Hi,
> 
> Sonic Pi (ITP #796550) needs the did_you_mean gem (RFP #811484).
> 
> That gem has been bundled with Ruby 2.3 and now ships with the Debian
> ruby2.3 package.

Note that the ruby2.3 package in Debian does *not* ship did_you_mean. It
will _depend_ on ruby-did-you-mean as soon as it gets in the archive,
though.

> However, Sonic Pi needs to stay compatible with Debian ruby2.1 and
> ruby2.2 (https://github.com/samaaron/sonic-pi/issues/928) and therefore
> I need a Debian package of ruby-did-you-mean that works for 2.1 and 2.2,
> but that won't install if ruby2.3 is used.
> 
> No idea how to achieve that. If anyone on this list would want to help,
> I'd appreciate it.

Hi, after out chat on IRC today I have just uploaded ruby-did-you-mean,
but it is the latest version of did_you_mean, which will not work on
Ruby < 2.3.

However, I went to look at the Sonic Pi source, and not having
did_you_mean is not fatal, as the only place where it is explicitly
mentioned is this (app/server/core.rb, line 43):

begin
  require 'did_you_mean'
rescue LoadError
  warn "Non-critical error: Could not load did_you_mean"
end

So if `require 'did_you_mean'` fails -- and it will fail on Ruby < 2.3
-- Sonic Pi seems to just goes ahead and ignores it.

The solution for having did_you_mean working on Ruby < 2.3 would be to
take version 0.10.0. I tried that, but that would require an extra
dependency (interception), which seems to be obsolete because the newer
did_you_mean does not have that dependency anymore (I imagine the needed
features have been added to Ruby 2.3 itself).

-- 
Antonio Terceiro 


signature.asc
Description: PGP signature