From: Gaute Hope <eg@gaute.vetsj.com>
To: Adam Bogacki <adam.bogacki@clear.net.nz>
Cc: sup-talk@rubyforge.org
Subject: Re: [sup-talk] Release Sup 0.13.1
Date: Sat, 03 Aug 2013 00:38:09 +0200 [thread overview]
Message-ID: <51FC34D1.9050302@gaute.vetsj.com> (raw)
In-Reply-To: <51FC26D9.5020708@clear.net.nz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02. aug. 2013 23:38, Adam Bogacki wrote:
>
> 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 ?
Hi, I think this is fixed in the latest release (there might be a
problem with sources.yaml). Try installing via gem.
Regards, Gaute
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR/DTRAAoJEJgnp+igdJAjRlYP/iTISP47irKhXc4KsRPq7RTu
QAbaMEwGvMTdE8E3Lq+wuB1ikbs9elYrWbqzatv1F2K0jcc8II73KYNOexFBhlSZ
MGDPB/N9KP1XIeDYMuJ/TE1zfaW25GZevjahpVjkQj/XBh/YfV66dFPLWb7HReEb
wpmSz8BDoLvQwGJ6Ydl/2BhR9g0JlCvMeuAjYNn135QjzBeCM5QvGQHtH6JGIexx
pV1EI1hTelRfL9spnOWpzar5C1trxlh/evlfp0xG5wIAjt+hmgrdWezNv+P6YF6/
Ul2KwcLx0T3ObchjRGKWUMyUqPY7593Xby1UMK6ll+Zqs0eFutGoEUhGPri/gxQJ
MfXZ3M/ZKPoTBk2xsIEUIH1oRRwgjdglIgy9easagjKjF51ZJu55K01DtXJMKsqD
DWkLw1AN92KH8Sb6eutpjHiUxoC+Rwj0d/mtD9paVDljL7Iie5lSKl6LVVhfZKG7
WKiGDoO081IhYwsbT6ORLJ2/NJr0PF4VWIBBs8xdOD37dLbznzFT56i3+NO8sjK0
MPnqVxc4ZK+/ezUpMZ8vFY3OZeECUq1UqZeOkaV6SbhgQmK+J+Mpi36HI/rqWy1C
l2oS00GS9xkhbAt3If56D1WbqiOdgwntUwljNoRupxRdAbugL/d+EzK24fDHaxbM
apXcVpArB3Qs3/QIh5us
=c2xe
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-08-02 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.20.1375449469.10946.sup-talk@rubyforge.org>
2013-08-02 21:38 ` Adam Bogacki
2013-08-02 22:38 ` Gaute Hope [this message]
2013-08-03 9:36 ` Gaute Hope
2013-08-03 9:47 ` Gaute Hope
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=51FC34D1.9050302@gaute.vetsj.com \
--to=eg@gaute.vetsj.com \
--cc=adam.bogacki@clear.net.nz \
--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