From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.162.5 with SMTP id xw5csp461344vdb; Fri, 2 Aug 2013 14:55:20 -0700 (PDT) X-Received: by 10.60.43.138 with SMTP id w10mr6979212oel.23.1375480520038; Fri, 02 Aug 2013 14:55:20 -0700 (PDT) Return-Path: Received: from rubyforge.org ([50.56.192.79]) by mx.google.com with ESMTP id u6si5269604oes.81.2013.08.02.14.55.19 for ; Fri, 02 Aug 2013 14:55:19 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) client-ip=50.56.192.79; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 50.56.192.79 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id DF6452E390; Fri, 2 Aug 2013 21:55:20 +0000 (UTC) X-Greylist: delayed 901 seconds by postgrey-1.31 at rubyforge; Fri, 02 Aug 2013 21:48:50 UTC Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by rubyforge.org (Postfix) with ESMTP id 4BEB02E1DA for ; Fri, 2 Aug 2013 21:48:49 +0000 (UTC) Received: from mxin2-orange.clear.net.nz (lb2-srcnat.clear.net.nz [203.97.32.237]) by smtp5.clear.net.nz (CLEAR Net Mail) with ESMTP id <0MQX00JNEAJWC220@smtp5.clear.net.nz> for sup-talk@rubyforge.org; Sat, 03 Aug 2013 09:33:43 +1200 (NZST) Received: from 121-73-231-102.broadband.telstraclear.net (HELO [121.73.231.102]) ([121.73.231.102]) by smtpin2.clear.net.nz with ESMTP; Sat, 03 Aug 2013 09:33:43 +1200 Date: Sat, 03 Aug 2013 09:38:33 +1200 From: Adam Bogacki In-reply-to: To: sup-talk@rubyforge.org Message-id: <51FC26D9.5020708@clear.net.nz> MIME-version: 1.0 X-Enigmail-Version: 1.5.2 References: User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130701 Icedove/17.0.7 Subject: Re: [sup-talk] Release Sup 0.13.1 X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0707787562499765985==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org This is a multi-part message in MIME format. --===============0707787562499765985== Content-type: multipart/alternative; boundary=------------090208020008050908080805 This is a multi-part message in MIME format. --------------090208020008050908080805 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/08/13 01:17, sup-talk-request@rubyforge.org 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 > ---------------------------------------------------------------- > --- 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 ? Hang in there guys, many now polished projects have had rocky beginnings .. Regards, Adam Bogacki, adam.bogacki@clear.net.nz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQEcBAEBAgAGBQJR/CbHAAoJELXBCnrK+Nj6ftQH/15Io+NN72Sqmgj0yNoNSTyV t7rttkqbbp42WFrtOqH9lSjdkcMwpdEDENkhDfsRckjcSbGHsQwGOJXCE9iBUWwT rYvSqtcRTJS3keW0JAEX3hdauWIoSaqzVHCNJn6GM/YIScf6mwWddE8IP2Sil7SH AfBTwIlCSNQcPR6Tdyj5V8bXgIHw0j7V4GW0QyE+ijeGub3JOBDXg7tUERM/qR9j PzBPfQ25YMEMq8E8LBK6y/yNk8jxc2Q1FZrqwL17+hfJUeFzzAXQp8kzJzk/uVPI EqHK38KULOGS3h1T77x1XQXj7AjpUv/RneCYuoZo6YhXMuxg4YjKYGXVY6VuzY8= =7kB3 -----END PGP SIGNATURE----- --------------090208020008050908080805 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/08/13 01:17, sup-talk-request@rubyforge.org 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
> ----------------------------------------------------------------
> --- 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 ?

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

Regards,

Adam Bogacki,
adam.bogacki@clear.net.nz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQEcBAEBAgAGBQJR/CbHAAoJELXBCnrK+Nj6ftQH/15Io+NN72Sqmgj0yNoNSTyV
t7rttkqbbp42WFrtOqH9lSjdkcMwpdEDENkhDfsRckjcSbGHsQwGOJXCE9iBUWwT
rYvSqtcRTJS3keW0JAEX3hdauWIoSaqzVHCNJn6GM/YIScf6mwWddE8IP2Sil7SH
AfBTwIlCSNQcPR6Tdyj5V8bXgIHw0j7V4GW0QyE+ijeGub3JOBDXg7tUERM/qR9j
PzBPfQ25YMEMq8E8LBK6y/yNk8jxc2Q1FZrqwL17+hfJUeFzzAXQp8kzJzk/uVPI
EqHK38KULOGS3h1T77x1XQXj7AjpUv/RneCYuoZo6YhXMuxg4YjKYGXVY6VuzY8=
=7kB3
-----END PGP SIGNATURE-----

--------------090208020008050908080805-- --===============0707787562499765985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============0707787562499765985==--