Re: [sup-talk] Getting ready for sup-0.13
Gaute -- thank you so much for organizing and calling out what needs to get done. It's great to see sup getting some love again! On Sun, Apr 28, 2013 at 11:23 AM, Gaute Hope e...@gaute.vetsj.com wrote: Greetings list, William has graciously given us access to the rest of the Sup infrastructure and the plan is to move as much as possible to GitHub. At the moment we are three maintainers: Hamish Downer, Matthieu Rakotojaona and myself. There are three categories for the sup repository team: Owner, Commiter, Contributor. Pretty much any kind of contribution would mean we would add you to the contributor team if you asked to be. The plan for sup is: Release sup-0.13 relatively soon: - including the last bugfixes otherwise leave out the major changes that have been discussed lately And the proposed roadmap for sup-0.14: - support ruby 2.0.0 - migrate to psych - remove all deprecated and abandoned dependencies (e.g. switch from RMail to Mail) - implement IMAP syncback support - get uft-8 encoding right We have documented this setup and the roadmap in the wiki at: - https://github.com/sup-heliotrope/sup/wiki/Development%3A-Administration-and-Team - https://github.com/sup-heliotrope/sup/wiki/Development Please see https://github.com/sup-heliotrope/sup/wiki/Contributing on how to submit changes or contribute. There are a few tasks and roles that need some love, among them: maintaining the web site and maintaining the maildir feature branch. I'd love to help contribute to testing, but am short on time these days. However, I setup the site, and will work to fix up the content on there. Please file requests here: https://github.com/sup-heliotrope/sup-heliotrope.github.io/issues Cheers, jof Regards, Fellow Suppers ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope e...@gaute.vetsj.com wrote: Hi, Jonathan: I put your commit into a pull request at: - https://github.com/sup-heliotrope/sup/pull/19 Also, re-branding and updating to web-references: - https://github.com/sup-heliotrope/sup/pull/20 any comments on this? You can see the changes I made. I have absolutely no intentions of stepping on any toes, but this is a suggestion. No, thank you very much! That looks great! It is a pity that the official home page and probably first search results direct to the abandoned home and gem of sup. It is too bad. Hopefully William could hand off access or at least push updates somehow. If not, maybe we could stand up another domain pointing to github pages? Looks like supmua.org and supm.ua are available. :p --j ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
On Fri, Apr 12, 2013 at 12:46 PM, Hamish D dmi...@gmail.com wrote: We've set up https://github.com/sup-heliotrope/sup Please feel free to put pull requests up there. And contributions to the new wiki are also very welcome. We have lots of missing pages ... https://github.com/sup-heliotrope/sup/wiki Hey -- that's a most excellent place to put a wiki up. Glad to find where the action's at. We have emailed William about this but have had no response. So currently we have no access to publishing gems under the sup name. As to a meet up, I'm in England so won't be coming to San Francisco :-P Oh no worries, I just mention it because I know WIlliam is from somewhere around here. I think he's working in SF now. I'm very sorry. It seems that an error occurred in Sup. Please accept my sincere apologies. Please submit the contents of /home/jof/.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 We should update this text ... Hamish ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
http://supmua.org/ Just tossed this, up but it's mostly stuff from the old rubyforge page. On Sat, Apr 13, 2013 at 10:14 AM, Gaute Hope e...@gaute.vetsj.com wrote: On 13. april 2013 18:35, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope e...@gaute.vetsj.com wrote: On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope e...@gaute.vetsj.com wrote: Hi, Jonathan: I put your commit into a pull request at: - https://github.com/sup-heliotrope/sup/pull/19 Also, re-branding and updating to web-references: - https://github.com/sup-heliotrope/sup/pull/20 any comments on this? You can see the changes I made. I have absolutely no intentions of stepping on any toes, but this is a suggestion. No, thank you very much! That looks great! It is a pity that the official home page and probably first search results direct to the abandoned home and gem of sup. It is too bad. Hopefully William could hand off access or at least push updates somehow. If not, maybe we could stand up another domain pointing to github pages? Looks like supmua.org and supm.ua are available. :p --j Yeah.. I think some web page is pretty essential, perhaps just the standard github-pages domain for a start. Anyone feel up for the task, I'd be happy to add you to the github-organization. Agreed. I snagged supmua.org for a year, and have it pointing at sup-heliotrope.github.io for pages. Stick me on the org, and I'll see about getting a simple site started. Nice. You're on. Cheers, Gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] sup: Fix for an UndefinedMethodError
Maybe William can help out? https://twitter.com/wm/status/323175493367119873 On Sat, Apr 13, 2013 at 12:19 PM, Jonathan Lassoff j...@thejof.com wrote: On Sat, Apr 13, 2013 at 10:37 AM, Gaute Hope e...@gaute.vetsj.com wrote: If we go sup2 I would suggest the following plan: - Release the best we can get with the current code for 1.9.3 as a last community release of sup-0.12, say.. sup-0.13. For sup2: - Fork a new repo: sup2 - Go for Mail in stead of RMail (index breakage) - Go for only Psych (config breakage), requires psych gem in 1.8 - Integrate the IMAP / label sync back stuff (personally this is what I miss the most) - Go for ruby 2.0.0 and maybe 1.8 - Get rid of all dependencies that are abandoned or deprecated (ncurses gem..) And target ncursesw? - Try to do tests on most stuff for different encodings - Try to get UTF-8 / encoding right - Move all the rest of the infrastructure to something the project is in control of Would be very nice: - Index migration - Config migration For the web page (eventually): - note about the original project - note about the last sup-0.13 release - wiki and project page for sup2 This plan more or less holds whether we go sup2 or not, but I think it is easier to get rid of the hopeless dependencies. I agree that it's worth it to drop unmaintained dependencies and just fix what breaks. It would be unfortunate to have to fork the project and make a different name. I wonder if Morgan has lost interest or is just busy with other things. Cheers, jof @sup-devel readers: discussion is currently at sup-talk, please send any responses there. Regards, Gaute On 13. april 2013 19:14, Gaute Hope wrote: On 13. april 2013 18:35, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 6:17 AM, Gaute Hope e...@gaute.vetsj.com wrote: On la. 13. april 2013 kl. 12.09 +0200, Jonathan Lassoff wrote: On Sat, Apr 13, 2013 at 2:16 AM, Gaute Hope e...@gaute.vetsj.com wrote: Hi, Jonathan: I put your commit into a pull request at: - https://github.com/sup-heliotrope/sup/pull/19 Also, re-branding and updating to web-references: - https://github.com/sup-heliotrope/sup/pull/20 any comments on this? You can see the changes I made. I have absolutely no intentions of stepping on any toes, but this is a suggestion. No, thank you very much! That looks great! It is a pity that the official home page and probably first search results direct to the abandoned home and gem of sup. It is too bad. Hopefully William could hand off access or at least push updates somehow. If not, maybe we could stand up another domain pointing to github pages? Looks like supmua.org and supm.ua are available. :p --j Yeah.. I think some web page is pretty essential, perhaps just the standard github-pages domain for a start. Anyone feel up for the task, I'd be happy to add you to the github-organization. Agreed. I snagged supmua.org for a year, and have it pointing at sup-heliotrope.github.io for pages. Stick me on the org, and I'll see about getting a simple site started. Nice. You're on. Cheers, Gaute ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
[sup-talk] sup bug tracker down?
I hit a really unfortunate crash in my primary sup instance, and am having trouble recovering from filesystem snapshot backups. I went to go and submit a bug, but it seems that the bug tracker is down. It still seems to be on wmorgan's domain. Should it still be there? Maybe we could transition out to somewhere else? I'll show the bug in another thread. --j ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
[sup-talk] sup Xapian crash
I'm having a sad day with sup. I'm crashing with a Xapian error I'll have to dig into. The exception is this: --- IOError from thread: poll after loading inbox DatabaseCorruptError: Expected another key with the same term name but found a different one /usr/lib/ruby/1.8/sup/index.rb:293:in `_dangerous_allterms_begin' /usr/lib/ruby/1.8/sup/index.rb:293:in `each_prefixed_term' /usr/lib/ruby/1.8/sup/index.rb:306:in `each_source_info' /usr/lib/ruby/1.8/sup/maildir.rb:98:in `each' /usr/lib/ruby/1.8/sup/maildir.rb:98:in `to_a' /usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll' /usr/lib/ruby/1.8/sup/util.rb:229:in `call' /usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark' /usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll' /usr/lib/ruby/1.8/sup/maildir.rb:90:in `each' /usr/lib/ruby/1.8/sup/maildir.rb:90:in `poll' /usr/lib/ruby/1.8/sup/poll.rb:155:in `poll_from' /usr/lib/ruby/1.8/sup/poll.rb:113:in `do_poll' /usr/lib/ruby/1.8/sup/poll.rb:103:in `each' /usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll' /usr/lib/ruby/1.8/sup/poll.rb:102:in `synchronize' /usr/lib/ruby/1.8/sup/poll.rb:102:in `do_poll' /usr/lib/ruby/1.8/sup/util.rb:572:in `send' /usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing' /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll' /usr/lib/ruby/1.8/sup/poll.rb:49:in `poll_with_sources' /usr/lib/ruby/1.8/sup/poll.rb:68:in `poll' /usr/lib/ruby/1.8/sup/util.rb:572:in `send' /usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing' /usr/bin/sup-mail:223 /usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread' /usr/lib/ruby/1.8/sup.rb:77:in `initialize' /usr/lib/ruby/1.8/sup.rb:77:in `new' /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread' /usr/bin/sup-mail:223 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in `call' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in `__unprotected_load_threads' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in `call' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in `load_n_threads_background' /usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread' /usr/lib/ruby/1.8/sup.rb:77:in `initialize' /usr/lib/ruby/1.8/sup.rb:77:in `new' /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:638:in `load_n_threads_background' /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:709:in `__unprotected_load_threads' (eval):12:in `load_threads' /usr/bin/sup-mail:223 I can start sup, but it seems like it goes to add a new message from pickup and crashes. Maybe something about the new message could be causing this. Anyone run into this before or have any ideas where I should start hacking away? Cheers, jof ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] Delete A Source From Ferret Index
Excerpts from William Morgan's message of Tue Jan 05 13:55:42 -0800 2010: In this particular case you could also have run sup-tweak-labels to add the spam label to everything from that source (and then edited sources.yaml to make it autoapply for any new messages). Ah. Nice other way around that. Would have been an even quicker solution in this case. I added this recipe to the wiki: http://sup.rubyforge.org/wiki/wiki.pl?RemovingASource --j ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
Re: [sup-talk] Delete A Source From Ferret Index
Excerpts from Jonathan Lassoff's message of Sun Jan 03 19:35:08 -0800 2010:
Any suggestions for removing all messages from the index that belong to
a certain source?
A solution that ended up working for me:
- Start the devel console (cd ~/src/sup; ./devel/console.sh)
- Search for message ids from the source you want to remove and run
Redwood::FerretIndex#delete on each (the evil source id was 10 in my case):
Index.each_id(Index.parse_query(source_id:10)){|m| Index.delete(m)};
Index.save_index
Cheers,
jonathan
___
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
[sup-talk] Delete A Source From Ferret Index
I've run into a predicament with my regular-use sup index. I was hit by the Spamassassin 2010 bug over New Years just now, and realized I ought to take an occasional look at what gets dropped in my folder for things marked spam. Silly me, I ran sup-add for the maildir containing spam email, but forgot to add an option to label it as spam. Any suggestions for removing all messages from the index that belong to a certain source? Thanks, jonathan ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
[sup-talk] sup 0.8.1 crash
Yikes! I found a way to crash my sup! I'm running sup 0.8.1 (sourced from whatever's current on rubygems.org, not a git branch), and can get sup to crash on specific searches. I took a little time to poke around in the sup source to try and get an idea what was going on. I'm led to believe this is because I added a source in the past that I later deleted -- but all of the mesages are still in the index. So, when certain searches turn up results that are in that deleted source, the sup index fails to reference the message source in Redwood::Index. Is there a way to delete a source without having to re-index everything? So, I figured I might find a way to search the index for any documents whose source id is the same as the deleted one and remove them from the index, but am having a hard time finding a way to iterate over all documents in the index (no search query). Is there a simple way to iterate over all messages? Here's some example crash output: --- RuntimeError from thread: load threads for thread-index-mode invalid source 1 /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:403:in `build_message' /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:399:in `build_message' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:297:in `each_id_by_date' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/thread.rb:330:in `call' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/thread.rb:330:in `load_n_threads' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:297:in `each_id_by_date' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:296:in `each' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/index.rb:296:in `each_id_by_date' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/thread.rb:326:in `load_n_threads' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/modes/thread-index-mode.rb:620:in `__unprotected_load_n_threads' (eval):12:in `load_n_threads' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/modes/thread-index-mode.rb:604:in `load_n_threads_background' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup.rb:71:in `reporting_thread' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup.rb:69:in `initialize' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup.rb:69:in `new' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup.rb:69:in `reporting_thread' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/modes/thread-index-mode.rb:603:in `load_n_threads_background' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/modes/thread-index-mode.rb:673:in `__unprotected_load_threads' (eval):12:in `load_threads' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/lib/sup/modes/search-results-mode.rb:34:in `spawn_from_query' /usr/lib/ruby/gems/1.8/gems/sup-0.8.1/bin/sup:270 /usr/bin/sup:19:in `load' /usr/bin/sup:19 Thanks, jonathan ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
[sup-talk] sup crashes while performing general searches
Hi, I'm mailing the list as prompted to do so by the cute crash banner. I'm just trying sup out for the first several times, and I've added a single Maildir source in my local home directory. I find that when doing a general search (\) that returns more than 5 results or so, sup crashes. For example, when I do a general search for banana, I get two messages in my inbox just fine. However, if I perform a search for hello (should be ~80 results), sup crashes with the attached error. --jonathan --- RuntimeError from thread: load threads for thread-index-mode invalid source 2 /var/lib/gems/1.8/gems/sup-0.5/lib/sup/index.rb:362:in `build_message' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/index.rb:261:in `each_id_by_date' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/thread.rb:330:in `call' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/thread.rb:330:in `load_n_threads' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/index.rb:261:in `each_id_by_date' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/index.rb:261:in `each' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/index.rb:261:in `each_id_by_date' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/thread.rb:326:in `load_n_threads' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/modes/thread-index-mode.rb:493:in `__unprotected_load_n_threads' (eval):12:in `load_n_threads' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/modes/thread-index-mode.rb:477:in `load_n_threads_background' /var/lib/gems/1.8/gems/sup-0.5/lib/sup.rb:60:in `reporting_thread' /var/lib/gems/1.8/gems/sup-0.5/lib/sup.rb:58:in `initialize' /var/lib/gems/1.8/gems/sup-0.5/lib/sup.rb:58:in `new' /var/lib/gems/1.8/gems/sup-0.5/lib/sup.rb:58:in `reporting_thread' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/modes/thread-index-mode.rb:476:in `load_n_threads_background' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/modes/thread-index-mode.rb:546:in `__unprotected_load_threads' (eval):12:in `load_threads' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/modes/search-results-mode.rb:34:in `spawn_from_query' /var/lib/gems/1.8/gems/sup-0.5/bin/sup:262 /var/lib/gems/1.8/bin/sup:18:in `load' /var/lib/gems/1.8/bin/sup:18 --- SystemExit from thread: main invalid source 2 /var/lib/gems/1.8/gems/sup-0.5/lib/sup.rb:64:in `select' /var/lib/gems/1.8/gems/sup-0.5/lib/sup/buffer.rb:31:in `nonblocking_getch' /var/lib/gems/1.8/gems/sup-0.5/bin/sup:227 /var/lib/gems/1.8/bin/sup:18:in `load' /var/lib/gems/1.8/bin/sup:18 ___ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
