Subject: Re: [sup-talk] Release Sup 0.13.1

From: Gaute Hope <[email-masked]>
Date: Sat, 03 Aug 2013 11:47:59 +0200

On 03. aug. 2013 11:36, Gaute Hope wrote:
> On 03. aug. 2013 00:38, Gaute Hope wrote:
>> On 02. aug. 2013 23:38, Adam Bogacki wrote:
------------
>>>> --- TypeError from thread: main can't convert String into Array 
>>>> /usr/lib/ruby/vendor_ruby/sup/account.rb:64:in `add_account' 
>>>> /usr/lib/ruby/vendor_ruby/sup/account.rb:38:in `initialize' 
>>>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `new' 
>>>> /usr/lib/ruby/vendor_ruby/sup/util.rb:576:in `init' 
>>>> /usr/lib/ruby/vendor_ruby/sup.rb:166:in `start' 
>>>> /usr/bin/sup-mail:164:in `<module:Redwood>' 
>>>> /usr/bin/sup-mail:80:in `<main>' adam@Candide:~$
>>> .. and it has been that way ever since.
>>
>>> Can anyone explain what is happening and recommend a fix ?

The problem is likely an incorrectly set up :alternates: in config.yaml,
it should be of the format:

:alternates:
  - [email-masked]
  - [email-masked]

if it is set up like:
:alternates: [email-masked]

if will fail. A more descriptive error message should be shown with the
patch in pull request #119 [0]. Please test it if you have the chance,
otherwise let me know if changing config.yaml did the trick.

[0] https://github.com/sup-heliotrope/sup/pull/119

Cheers, Gaute

---

From: Gaute Hope <[email-masked]>
Date: Sat, 03 Aug 2013 00:38:09 +0200

On 02. aug. 2013 23:38, Adam Bogacki wrote:
> 
> On 03/08/13 01:17, [email-masked] wrote:
> 
> It's good to see signs of life on this list.
> 
> I was getting used to sup-mail on debian wheezy, then sid, but then
> one day I received
> 
>> adam@Candide:~$ sup-mail 
>> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require':
>> iconv
> will be deprecated in the future, use String#encode instead.
>> [2013-08-03 07:58:08 +1200] ERROR: oh crap, an exception 
>> ---------------------------------------------------------------- 
>> I'm very sorry. It seems that an error occurred in Sup. Please 
>> accept my sincere apologies. Please submit the contents of 
>> /home/adam/.sup/exception-log.txt and a brief report of the 
>> circumstances to http://masanjin.net/sup-bugs/ so that I might 
>> address this problem. Thank you!
> 
>> Sincerely, William 
>> ---------------------------------------------------------------- 

Hi, I think this is fixed in the latest release (there might be a
problem with sources.yaml). Try installing via gem.

Regards, Gaute

---

From: Adam Bogacki <[email-masked]>
Date: Sat, 03 Aug 2013 09:38:33 +1200

I was getting used to sup-mail on debian wheezy, then sid, but then one
day I received

> adam@Candide:~$ sup-mail
> /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv
> Sincerely,
> William

Hang in there guys, many now polished projects have had rocky beginnings ..

Regards,

Adam Bogacki,
[email-masked]

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

---

From: Gaute Hope <[email-masked]>
Date: Sat, 03 Aug 2013 11:36:24 +0200

> problem with sources.yaml). Try installing via gem.

On close inspection it seems this is a separate issue (originally though
of #42 [0]). Would you mind pastebinning/posting your config.yaml
(anonymized)? It seems like something in the account configuration is
triggering the error. Also, what version are you running of sup?

Feel free to open an issue at: https://github.com/sup-heliotrope/sup

Regards, Gaute

[0] https://github.com/sup-heliotrope/sup/pull/42