From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from [192.168.1.207] (c4C8F5BC1.dhcp.as2116.net. [193.91.143.76]) by mx.google.com with ESMTPSA id w9sm4863594lbk.7.2013.08.03.02.37.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 03 Aug 2013 02:37:25 -0700 (PDT) Message-ID: <51FCCF18.1040807@gaute.vetsj.com> Date: Sat, 03 Aug 2013 11:36:24 +0200 From: Gaute Hope User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Adam Bogacki CC: sup-talk@rubyforge.org Subject: Re: [sup-talk] Release Sup 0.13.1 References: <51FC26D9.5020708@clear.net.nz> <51FC34D1.9050302@gaute.vetsj.com> In-Reply-To: <51FC34D1.9050302@gaute.vetsj.com> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 03. aug. 2013 00:38, Gaute Hope wrote: > On 02. aug. 2013 23:38, Adam Bogacki wrote: >>> 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 >>> ---------------------------------------------------------------- >>> --- 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 `' >>> /usr/bin/sup-mail:80:in `
' adam@Candide:~$ >> .. and it has been that way ever since. > >> Can anyone explain what is happening and recommend a fix ? > > Hi, I think this is fixed in the latest release (there might be a > 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