Discussions of development and use of the Sup email client
 help / color / mirror / Atom feed
From: avtobiff@gmail.com
To: supmua@googlegroups.com
Subject: Re: Sup being removed from Debian
Date: Mon, 25 Aug 2014 12:55:13 -0700 (PDT)	[thread overview]
Message-ID: <467a60fd-e8f7-4bcd-9cbd-6fbde1f92920@googlegroups.com> (raw)
In-Reply-To: <bf2ef7b3-ef84-4760-a6c7-9459c7d0f028@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 1028 bytes --]



On Saturday, August 23, 2014 4:06:22 AM UTC+2, Ian Munsie 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
>
>
I am the maintainer of the sup-mail Debian package. Sadly I have not
had enough time to update it since it was new-born.

There are a few question marks that I need some help with. (See
separate post.)


--
Per

 

> Cheers,
> -Ian
>

[-- Attachment #1.2: Type: text/html, Size: 2425 bytes --]

      parent reply	other threads:[~2014-08-25 19:55 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
2014-08-23 13:56   ` Mayeu
2014-08-25 19:55 ` avtobiff [this message]

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=467a60fd-e8f7-4bcd-9cbd-6fbde1f92920@googlegroups.com \
    --to=avtobiff@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