From: Gaute Hope <eg@gaute.vetsj.com>
To: Ian Munsie <darkstarsword@gmail.com>
Cc: "supmua@googlegroups.com" <supmua@googlegroups.com>
Subject: Re: [sup] Sup being removed from Debian
Date: Sat, 23 Aug 2014 10:20:52 +0200 [thread overview]
Message-ID: <CABKe4MsM=pu7ob=Qn0QV7iZ-5kgOaxgB8T2yeOQqwpfrMmQPRA@mail.gmail.com> (raw)
In-Reply-To: <bf2ef7b3-ef84-4760-a6c7-9459c7d0f028@googlegroups.com>
On Sat, Aug 23, 2014 at 4:06 AM, Ian Munsie <darkstarsword@gmail.com> wrote:
> Hi All,
>
> It looks like the version of Sup in Debian is slated to be removed due to a
> dependency on ruby 1.9 which has been removed, and a mixup thinking Sup's
> upstream had vanished after it moved away from Rubyforge.
>
>> Someone needs to jump on this if the want to prevent removal. It needs to
>> be updated to work with ruby2.1 very soon.
>
>
> I haven't been following upstream development but I don't want to see this
> removed from Debian - has the latest version already been updated to support
> Ruby 2.1, or can it easily be updated?
>
> The relevant Debian bug reports are here:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758515
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747878
Hi,
Yeah, Sup should run on ruby 2.1. The latest version is 0.19.0 which
is to be got from here: http://rubygems.org/gems/sup or
https://github.com/sup-heliotrope/sup/releases.
Note that sup wasn't removed from Rubyforge, Rubyforge was shut down.
Sup development is happening here:
https://github.com/sup-heliotrope/sup
Cheers, Gaute
next prev parent reply other threads:[~2014-08-23 8:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-23 2:06 Ian Munsie
2014-08-23 2:54 ` [sup] " C. R. Oldham
2014-08-23 8:20 ` Gaute Hope [this message]
2014-08-23 13:56 ` Mayeu
2014-08-25 19:55 ` avtobiff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABKe4MsM=pu7ob=Qn0QV7iZ-5kgOaxgB8T2yeOQqwpfrMmQPRA@mail.gmail.com' \
--to=eg@gaute.vetsj.com \
--cc=darkstarsword@gmail.com \
--cc=supmua@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox