From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>, sup-talk <sup-talk@rubyforge.org>
Subject: Sup Release 0.14.0
Date: Thu, 15 Aug 2013 10:33:23 +0200 [thread overview]
Message-ID: <1376554850-sup-6592@qwerzila> (raw)
Greetings,
I have just release Sup 0.14.0 which contains a lot of updates. Check
out the Release Notes below for more details.
Important:
- This release does no longer work on Ruby 1.8.
- Configuration files must be migrated from Sup 0.13 [1].
- Read the migration notice [1].
If you are not feeling very adventurous, stay with Sup 0.13 for a little
while yet. Remember to back up your current ~/.sup before upgrading in
case you need to downgrade.
Happy sup! Thanks to all the contributors and testers!
Check the wiki for installation instructions [2] or just do a:
$ gem install sup
Report issues to our tracker at GitHub [3].
Cheers, Gaute
[1] https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14
[2] https://github.com/sup-heliotrope/sup/wiki/
[3] https://github.com/sup-heliotrope/sup/issues
== Release Notes ==
CJK-compatability, Psych usage, thread safety, GPGME 2.0 support. Sup is now
Ruby 1.9 based, and apart from RMail - ready for Ruby 2.0.0.
Sup now uses Psych as a YAML parser (default by Ruby) and your previous
configuration files (~/.sup/*.yaml) may need to be migrated or re-created for
them to work with the new sup. A migration script is included for this.
Check https://github.com/sup-heliotrope/sup/wiki/Migration-0.13-to-0.14 for
the latest instructions.
First back up your ~/.sup directory and index, after installing the new sup
run:
$ sup-psych-ify-config-files
to migrate your files. You should now be all set for buisness.
reply other threads:[~2013-08-15 8:34 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=1376554850-sup-6592@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