From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] sup v2 progress report
Date: Wed, 13 Apr 2011 17:18:24 -0300 [thread overview]
Message-ID: <1302724410-sup-5965@alvh.no-ip.org> (raw)
In-Reply-To: <1301257195-sup-9486@masanjin.net>
Excerpts from William Morgan's message of dom mar 27 17:41:59 -0300 2011:
> Heliotrope, the server component, is close to ready for a version 1 release.
> You can find it at https://github.com/wmorgan/heliotrope/.
Hi,
I find this to be great. Thanks for writing it.
I just tried to follow the instructions on a Debian machine and noticed
that you need to install the package ruby1.9.1-dev in order for the
whistlepig and oklahoma_mixer gems. Probably most Ruby-addicted people
already have it so they don't see that problem, but since I'm not one of
those, it did bit me. I suggest this should be in the README file.
I ran into a problem importing email that has Latin1 headers. The crash
I got was:
/home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:44:in `block in get_date_in_file': invalid byte sequence in UTF-8 (ArgumentError)
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:42:in `open'
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:42:in `get_date_in_file'
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:35:in `block in get_files'
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:35:in `map'
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:35:in `get_files'
from /home/alvherre/Code/heliotrope/lib/heliotrope/maildir-walker.rb:21:in `done?'
from bin/heliotrope-add:98:in `<main>'
I added a debugging rescue to that block and found that the message has
this header:
List-Id: Consultas T<E9>cnicas sobre Linux y Software Libre <l-linux.velug.org.ve>
Note that the <E9> is actually a Latin-1 "é". (The message has a valid Date:
header).
This is obviously a bogus message; you're not supposed to use non-ASCII
chars in the header. But these guys did it anyway. I'm not sure what
would be a good fix for this problem. I guess it involves discarding
the failing line so that it can index the message using the proper date
instead of "0".
I haven't tried Turnsole yet. I checked the WEBrick thingy and it seems
pretty neat.
Thanks!
--
Álvaro Herrera <alvherre@alvh.no-ip.org>
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-04-14 1:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 20:41 William Morgan
2011-03-28 4:14 ` [sup-talk] " Matthieu Rakotojaona
2011-03-28 22:57 ` William Morgan
2011-03-28 12:52 ` [sup-devel] " Nicolas Pouillard
2011-03-29 3:11 ` [sup-talk] " William Morgan
2011-03-29 4:00 ` William Morgan
2011-03-29 21:19 ` [sup-talk] " Nicolas Pouillard
2011-03-29 21:31 ` William Morgan
2011-04-13 20:18 ` Alvaro Herrera [this message]
2011-04-14 7:39 ` Ico Doornekamp
2011-04-14 7:51 ` Ico Doornekamp
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=1302724410-sup-5965@alvh.no-ip.org \
--to=alvherre@alvh.no-ip.org \
--cc=sup-devel@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