From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-talk <sup-talk@rubyforge.org>, sup-devel <sup-devel@rubyforge.org>
Subject: ncursesw-sup gem has been yanked from rubygems
Date: Sun, 22 Dec 2013 14:44:53 +0100 [thread overview]
Message-ID: <1387719755-sup-9865@qwerzila> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
Hi,
the ncursesw-sup gem has been yanked from rubygems. The gems are still
available for download if you really need it:
https://rubygems.org/gems/ncursesw-sup
note that the gem namespace is now free for someone else to take over, so
I do not recommend doing that.
The ncursesw-sup gem is replaced by the ncursesw gem which the newest
sup 0.15.2 depends on.
Regards, Gaute
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-12-22 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1387719755-sup-9865@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
--cc=sup-talk@rubyforge.org \
/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