Subject: Sup Release 0.14.0

From: Gaute Hope <[email-masked]>
Date: Thu, 15 Aug 2013 10:33:23 +0200

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.

---

From: Gaute Hope <[email-masked]>
Date: Thu, 15 Aug 2013 23:36:45 +0200

Excerpts from Matthieu Rakotojaona's message of 2013-08-15 20:30:52 +0200:
> Thank you !
> 
> I've tried the install sup via the gem on a naked machine and I've faced
> a few problems:
> 
> * There is a bug in rubymail as pointed in [0]. I see it hasn't been
>   merged yet and doubt it will ever be. I replaced the upstream one with
>   the one from your repo (1) and it works as needed. Can we use a
>   rmail-sup, specific to us, just for the time we use this lib, just
>   like ncursesw-sup ?

Yeah, was a bit hesitant to go there, but I guess it is reasonably
sensible fix :) I'm OK with it. I would rather see us get Mail running
(writing this email from the use-mail branch, seamlessly using RMail on
the same index), but it is still a while to go..
 
> * There was a problem with the unicode gem. I had an old version of
> gem running (you need >= 2.0.2 as stated in [2] and followings). Here
> are the steps that fixed the problem:
> 
>   Update gem: $ sudo gem update --system
> 
>   Reinstall the unicode gem: $ gem uninstall unicode $ gem install
>   unicode

Ah nice catch, we should put this somewhere in the wiki..! troubleshooting?
 
> * Those damn encoding problems struck me. We're trying to fix_encoding a
>   bunch of Strings here and there and one of them at least is a frozen
>   string so it doesn't work. See PR130 [3] for this.

Nice, its extremly hackishy, but those mails and user inputs just don't
make any sense.. :D Your PR should be good to merge.
 
> Apart from that, it works well. Thank you guys for the hard work !
> You're making me ashamed of not being very participative in this,
> though :)

Yey, thanks!
 
Cheers, Gaute

---

From: Matthieu Rakotojaona <[email-masked]>
Date: Thu, 15 Aug 2013 20:30:52 +0200

Thank you !

  Update gem:
  $ sudo gem update --system

  Reinstall the unicode gem:
  $ gem uninstall unicode
  $ gem install unicode

[0] https://github.com/matta/rubymail/pull/2
[1] https://github.com/gauteh/rubymail
[2] https://github.com/blackwinter/unicode/issues/4#issuecomment-14086773
[3] https://github.com/sup-heliotrope/sup/pull/130

-- 
Matthieu Rakotojaona
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk