community/pipermail-archives/sup-talk/2013-01.txt (34463B) - raw
1 From jof@thejof.com Wed Jan 2 20:24:43 2013
2 From: jof@thejof.com (Jonathan Lassoff)
3 Date: Wed, 2 Jan 2013 12:24:43 -0800
4 Subject: [sup-talk] sup bug tracker down?
5 Message-ID: <CAHsqw9szovBD8_R+RBPXn66masg-i4RAH+s+k09mcrzc5EapqA@mail.gmail.com>
6
7 I hit a really unfortunate crash in my primary sup instance, and am
8 having trouble recovering from filesystem snapshot backups.
9
10 I went to go and submit a bug, but it seems that the bug tracker is
11 down. It still seems to be on wmorgan's domain. Should it still be
12 there? Maybe we could transition out to somewhere else?
13
14 I'll show the bug in another thread.
15
16 --j
17
18 From jof@thejof.com Wed Jan 2 20:26:15 2013
19 From: jof@thejof.com (Jonathan Lassoff)
20 Date: Wed, 2 Jan 2013 12:26:15 -0800
21 Subject: [sup-talk] sup Xapian crash
22 Message-ID: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
23
24 I'm having a sad day with sup. I'm crashing with a Xapian error I'll
25 have to dig into.
26
27 The exception is this:
28
29 --- IOError from thread: poll after loading inbox
30 DatabaseCorruptError: Expected another key with the same term name but
31 found a different one
32 /usr/lib/ruby/1.8/sup/index.rb:293:in `_dangerous_allterms_begin'
33 /usr/lib/ruby/1.8/sup/index.rb:293:in `each_prefixed_term'
34 /usr/lib/ruby/1.8/sup/index.rb:306:in `each_source_info'
35 /usr/lib/ruby/1.8/sup/maildir.rb:98:in `each'
36 /usr/lib/ruby/1.8/sup/maildir.rb:98:in `to_a'
37 /usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll'
38 /usr/lib/ruby/1.8/sup/util.rb:229:in `call'
39 /usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark'
40 /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
41 /usr/lib/ruby/1.8/sup/util.rb:229:in `benchmark'
42 /usr/lib/ruby/1.8/sup/maildir.rb:98:in `poll'
43 /usr/lib/ruby/1.8/sup/maildir.rb:90:in `each'
44 /usr/lib/ruby/1.8/sup/maildir.rb:90:in `poll'
45 /usr/lib/ruby/1.8/sup/poll.rb:155:in `poll_from'
46 /usr/lib/ruby/1.8/sup/poll.rb:113:in `do_poll'
47 /usr/lib/ruby/1.8/sup/poll.rb:103:in `each'
48 /usr/lib/ruby/1.8/sup/poll.rb:103:in `do_poll'
49 /usr/lib/ruby/1.8/sup/poll.rb:102:in `synchronize'
50 /usr/lib/ruby/1.8/sup/poll.rb:102:in `do_poll'
51 /usr/lib/ruby/1.8/sup/util.rb:572:in `send'
52 /usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing'
53 /usr/lib/ruby/1.8/sup/modes/poll-mode.rb:15:in `poll'
54 /usr/lib/ruby/1.8/sup/poll.rb:49:in `poll_with_sources'
55 /usr/lib/ruby/1.8/sup/poll.rb:68:in `poll'
56 /usr/lib/ruby/1.8/sup/util.rb:572:in `send'
57 /usr/lib/ruby/1.8/sup/util.rb:572:in `method_missing'
58 /usr/bin/sup-mail:223
59 /usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread'
60 /usr/lib/ruby/1.8/sup.rb:77:in `initialize'
61 /usr/lib/ruby/1.8/sup.rb:77:in `new'
62 /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
63 /usr/bin/sup-mail:223
64 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in `call'
65 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:699:in
66 `__unprotected_load_threads'
67 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in `call'
68 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:640:in
69 `load_n_threads_background'
70 /usr/lib/ruby/1.8/sup.rb:79:in `reporting_thread'
71 /usr/lib/ruby/1.8/sup.rb:77:in `initialize'
72 /usr/lib/ruby/1.8/sup.rb:77:in `new'
73 /usr/lib/ruby/1.8/sup.rb:77:in `reporting_thread'
74 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:638:in
75 `load_n_threads_background'
76 /usr/lib/ruby/1.8/sup/modes/thread-index-mode.rb:709:in
77 `__unprotected_load_threads'
78 (eval):12:in `load_threads'
79 /usr/bin/sup-mail:223
80
81
82 I can start sup, but it seems like it goes to add a new message from
83 pickup and crashes. Maybe something about the new message could be
84 causing this.
85
86 Anyone run into this before or have any ideas where I should start hacking away?
87
88 Cheers,
89 jof
90
91 From marka@pobox.com Wed Jan 2 21:33:39 2013
92 From: marka@pobox.com (Mark Alexander)
93 Date: Wed, 02 Jan 2013 16:33:39 -0500
94 Subject: [sup-talk] sup Xapian crash
95 In-Reply-To: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
96 References: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
97 Message-ID: <1357162160-sup-4225@bloovis.org>
98
99 Excerpts from Jonathan Lassoff's message of Wed Jan 02 15:26:15 -0500 2013:
100 > I'm having a sad day with sup. I'm crashing with a Xapian error I'll
101 > have to dig into.
102
103 I've never attempted to debug these kinds of crashes (which I run into
104 once or twice a year). Instead, I use sup-dump to save the state of
105 the index, rename .sup/xapian to .sup/xapian.bad, then use sup-sync
106 --restore to rebuild the index.
107
108 Even though sup is not maintained, I'm so addicted to it that I'm willing
109 to put up with this inconvenience once in a while.
110
111 From jof@thejof.com Wed Jan 2 23:20:28 2013
112 From: jof@thejof.com (Jonathan Lassoff)
113 Date: Wed, 2 Jan 2013 15:20:28 -0800
114 Subject: [sup-talk] sup Xapian crash
115 In-Reply-To: <1357162160-sup-4225@bloovis.org>
116 References: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
117 <1357162160-sup-4225@bloovis.org>
118 Message-ID: <CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com>
119
120 On Wed, Jan 2, 2013 at 1:33 PM, Mark Alexander <marka at pobox.com> wrote:
121 > Excerpts from Jonathan Lassoff's message of Wed Jan 02 15:26:15 -0500 2013:
122 >> I'm having a sad day with sup. I'm crashing with a Xapian error I'll
123 >> have to dig into.
124 >
125 > I've never attempted to debug these kinds of crashes (which I run into
126 > once or twice a year). Instead, I use sup-dump to save the state of
127 > the index, rename .sup/xapian to .sup/xapian.bad, then use sup-sync
128 > --restore to rebuild the index.
129
130 I started digging, but got bored with reading about the Xapian APIs,
131 so I mostly did what you just did as well :P
132
133 However, I needed to perform a sup-sync first to create the index and
134 add the messages in, so when I restored from the dump, pretty much
135 everything was marked as unread.
136 Working in the console to declare inbox bankruptcy and inbox zero, and
137 just clearing it all out. Thank goodness I'm starring threads that I
138 need to follow up on! :p
139
140 > Even though sup is not maintained, I'm so addicted to it that I'm willing
141 > to put up with this inconvenience once in a while.
142
143 Yeah, I've been using sup for so long that I can't just let it go now.
144 I've got all these excellent hooks and I know the system well.
145
146 Have you looked at Heliotrope / Turnisole yet?
147 That totally seems like wmorgan's future mail architecture, and I've
148 been curious to migrate to it, but haven't been able to sink the time
149 into it just yet.
150
151 Cheers,
152 jof
153
154 From marka@pobox.com Thu Jan 3 23:04:41 2013
155 From: marka@pobox.com (Mark Alexander)
156 Date: Thu, 03 Jan 2013 18:04:41 -0500
157 Subject: [sup-talk] sup Xapian crash
158 In-Reply-To: <CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com>
159 References: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
160 <1357162160-sup-4225@bloovis.org>
161 <CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com>
162 Message-ID: <1357254215-sup-7868@bloovis.org>
163
164 Excerpts from Jonathan Lassoff's message of Wed Jan 02 18:20:28 -0500 2013:
165 > Have you looked at Heliotrope / Turnisole yet?
166
167 I decided not to look at it when I heard it didn't support searches by date.
168 I do this kind of searching all the time in sup:
169
170 from:somebody AND after:(1 week ago)
171
172 and really can't live without it.
173
174 From jim@gonzul.net Fri Jan 4 09:49:58 2013
175 From: jim@gonzul.net (Jim Cheetham)
176 Date: Fri, 4 Jan 2013 22:49:58 +1300
177 Subject: [sup-talk] sup Xapian crash
178 In-Reply-To: <1357254215-sup-7868@bloovis.org>
179 References: <CAHsqw9uZk4bB0a8mz3ERNVZ7T+jO2zNNwc=+qDQ6dNO+1aYAFw@mail.gmail.com>
180 <1357162160-sup-4225@bloovis.org>
181 <CAHsqw9vha-C=g-nrcvA_dNMGjsfmz8+chOWXvq7e0N0Ns5KM0A@mail.gmail.com>
182 <1357254215-sup-7868@bloovis.org>
183 Message-ID: <CA+2knqtUwsXdziF5P5C7UBxaxXX1H+TKivjMW8zS3guiTHpP-Q@mail.gmail.com>
184
185 On Fri, Jan 4, 2013 at 12:04 PM, Mark Alexander <marka at pobox.com> wrote:
186 > Excerpts from Jonathan Lassoff's message of Wed Jan 02 18:20:28 -0500 2013:
187 >> Have you looked at Heliotrope / Turnisole yet?
188 >
189 > I decided not to look at it when I heard it didn't support searches by date.
190 > I do this kind of searching all the time in sup:
191 >
192 > from:somebody AND after:(1 week ago)
193
194 Mmm, I wondered why that wasn't working.
195
196 I have a heliotrope/turnsole 'working', but the index frequently
197 crashes and the rebuild is stupidly slow (<1message/sec)
198
199 I get the impression that development has stalled/stopped. I wouldn't
200 recommend heliotrope as an alternative to sup; the concept is
201 positive, but the current execution is lacking.
202
203 I guess I'll have to spend some time soon on rebuilding my sup
204 environment, which was broken by Ubuntu's upgrade of some underlying
205 libraries.
206
207 -jim
208
209 From dmishd@gmail.com Sun Jan 13 15:22:03 2013
210 From: dmishd@gmail.com (Hamish D)
211 Date: Sun, 13 Jan 2013 15:22:03 +0000
212 Subject: [sup-talk] replacement sup wiki
213 Message-ID: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
214
215 Hello
216
217 I've set up a wiki we can use as a replacement for the old unloved
218 wiki - http://foobacca.co.uk/sup/
219
220 Unfortunately, most of the old wiki appears to be lost. The wiki
221 software (usemod) only appears to keep the last 10 revisions of each
222 page. But most pages have been vandalised far more than that, and so
223 the content appears lost. I have checked the wayback machine but it
224 doesn't have anything from the wiki. I also note that the wiki is
225 covered by a Disallow line in the robots.txt - not sure how long
226 that's been there.
227
228 Anyway, please feel free to go and recreate the lost pages, or add new
229 content. The new wiki is ikiwiki, which is based on git, so all
230 history will remain available. At some point the spammers will start
231 hitting it, at which point I'll disable registration, but try
232 publishing an account on the front page and see if that foxes the
233 spammers. We'll see.
234
235 Hamish
236
237 From matthieu.rakotojaona@gmail.com Sun Jan 13 21:06:03 2013
238 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
239 Date: Sun, 13 Jan 2013 22:06:03 +0100
240 Subject: [sup-talk] replacement sup wiki
241 In-Reply-To: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
242 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
243 Message-ID: <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com>
244
245 This is excellent news, thank you for the move! I was myself considering
246 running our own bugtracker, seeing that wmorgan's github hasn't been
247 updated in the last 7 months and he is the only one being able to act on
248 them. Same thing would have to be done for the mailing-lists.
249
250 Speaking of the mailing list, is it okay if we hijack the wiki with
251 heliotrope content ? I read too many complaints about it being too hard to
252 install/use, and would love to fix it.
253
254
255 --
256 Matthieu RAKOTOJAONA
257 -------------- next part --------------
258 An HTML attachment was scrubbed...
259 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130113/00101d48/attachment.html>
260
261 From dmishd@gmail.com Sun Jan 13 23:40:19 2013
262 From: dmishd@gmail.com (Hamish D)
263 Date: Sun, 13 Jan 2013 23:40:19 +0000
264 Subject: [sup-talk] replacement sup wiki
265 In-Reply-To: <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com>
266 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
267 <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com>
268 Message-ID: <CAOxvSbdGF01FpdGnaYM43jTzz=mtwigAjfC_QGiRTgj+_eEiXA@mail.gmail.com>
269
270 > This is excellent news, thank you for the move! I was myself considering
271 > running our own bugtracker, seeing that wmorgan's github hasn't been updated
272 > in the last 7 months and he is the only one being able to act on them. Same
273 > thing would have to be done for the mailing-lists.
274
275 I have access to the gitorious account (can't remember if it is full
276 admin rights or just push access). But I would be equally happy for
277 there to be a github organisation account that a few of us were admins
278 for (including wmorgan if he wanted). It would definitely be nice to
279 have a working issue tracker.
280
281 Before doing more than this, might be worth seeing if wmorgan wants to
282 say if he has preferences on this. My impression is that he has left
283 sup behind, but would want to give a little time (a week, say) for him
284 to say what he'd like before doing a load of work. I guess one key
285 thing wmorgan has is the ability to push new sup gems to rubyforge.
286
287 I'd also be happy for the wiki to live elsewhere if there was some
288 collective decision that it would be better elsewhere. I just thought
289 I'd set it up for now.
290
291 > Speaking of the mailing list, is it okay if we hijack the wiki with
292 > heliotrope content ? I read too many complaints about it being too hard to
293 > install/use, and would love to fix it.
294
295 Please do put heliotrope stuff up there.
296
297 Hamish
298
299 From eg@gaute.vetsj.com Mon Jan 14 08:51:40 2013
300 From: eg@gaute.vetsj.com (Gaute Hope)
301 Date: Mon, 14 Jan 2013 09:51:40 +0100
302 Subject: [sup-talk] replacement sup wiki
303 In-Reply-To: <CAOxvSbdGF01FpdGnaYM43jTzz=mtwigAjfC_QGiRTgj+_eEiXA@mail.gmail.com>
304 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
305 <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com>
306 <CAOxvSbdGF01FpdGnaYM43jTzz=mtwigAjfC_QGiRTgj+_eEiXA@mail.gmail.com>
307 Message-ID: <50F3C71C.1070807@gaute.vetsj.com>
308
309 On 14. jan. 2013 00:40, Hamish D wrote:
310 >> This is excellent news, thank you for the move! I was myself considering
311 >> running our own bugtracker, seeing that wmorgan's github hasn't been updated
312 >> in the last 7 months and he is the only one being able to act on them. Same
313 >> thing would have to be done for the mailing-lists.
314 >
315 > I have access to the gitorious account (can't remember if it is full
316 > admin rights or just push access). But I would be equally happy for
317 > there to be a github organisation account that a few of us were admins
318 > for (including wmorgan if he wanted). It would definitely be nice to
319 > have a working issue tracker.
320 >
321 > Before doing more than this, might be worth seeing if wmorgan wants to
322 > say if he has preferences on this. My impression is that he has left
323 > sup behind, but would want to give a little time (a week, say) for him
324 > to say what he'd like before doing a load of work. I guess one key
325 > thing wmorgan has is the ability to push new sup gems to rubyforge.
326 >
327 > I'd also be happy for the wiki to live elsewhere if there was some
328 > collective decision that it would be better elsewhere. I just thought
329 > I'd set it up for now.
330 >
331 >> Speaking of the mailing list, is it okay if we hijack the wiki with
332 >> heliotrope content ? I read too many complaints about it being too hard to
333 >> install/use, and would love to fix it.
334 >
335 > Please do put heliotrope stuff up there.
336
337 Great! I agree with the organization-plan (github or whatever with a
338 full project page: repository, issues, wiki..) - it really strains the
339 project with these administrational bumps.
340
341 Most importantly: A admin group with full access to the organization to
342 allow for admins/devs to go off for a while without the project staggering.
343
344 Personally I think the best is to keep everything on the same place.
345
346 Regards, Gaute
347
348 From support@plecavalier.com Mon Jan 14 13:20:56 2013
349 From: support@plecavalier.com (Philippe LeCavalier)
350 Date: Mon, 14 Jan 2013 05:20:56 -0800
351 Subject: [sup-talk] replacement sup wiki
352 In-Reply-To: <50F3C71C.1070807@gaute.vetsj.com>
353 References: <CAOxvSbeLBiP9pGgpLek0AKfSSdUvG8Zix+Ly5wrNTDLQ-XuUZQ@mail.gmail.com>
354 <CAMiZLn248BGp9ZZ9_xRC2O=V150J+7jEA6j6+0mmJOfDMCFxfA@mail.gmail.com>
355 <CAOxvSbdGF01FpdGnaYM43jTzz=mtwigAjfC_QGiRTgj+_eEiXA@mail.gmail.com>
356 <50F3C71C.1070807@gaute.vetsj.com>
357 Message-ID: <CAKada-4peOZihAwo4nD32jG_6FQsbBeXd-+4DVRjF1rennVOeg@mail.gmail.com>
358
359 On Mon, Jan 14, 2013 at 12:51 AM, Gaute Hope <eg at gaute.vetsj.com> wrote:
360
361 > Great! I agree with the organization-plan (github or whatever with a
362 > full project page: repository, issues, wiki..) - it really strains the
363 > project with these administrational bumps.
364 >
365 > Most importantly: A admin group with full access to the organization to
366 > allow for admins/devs to go off for a while without the project staggering.
367 >
368 > Personally I think the best is to keep everything on the same place.
369 >
370
371 I second that!
372
373 Phil
374 -------------- next part --------------
375 An HTML attachment was scrubbed...
376 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130114/100eb6da/attachment.html>
377
378 From support@plecavalier.com Mon Jan 14 15:12:58 2013
379 From: support@plecavalier.com (Philippe LeCavalier)
380 Date: Mon, 14 Jan 2013 07:12:58 -0800
381 Subject: [sup-talk] help installing on FC17 on 64bit
382 Message-ID: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
383
384 Hi.
385
386 In light of recent activity I'd like to give sup another whirl. Last time I
387 installed sup was on i386 w/Deb. I'm now on FC17 64-bit -dunno if that's
388 what's making thing difficult or not...
389
390 I've installed everything from the fedora repo including sup gem.
391 Everything installs successfully however I get:
392
393 sup
394 /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': superclass
395 mismatch for class Iconv (TypeError)
396 from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'
397 from /usr/share/gems/gems/sup-0.10.2/lib/sup/rfc2047.rb:19:in `<top
398 (required)>'
399 from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'
400 from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'
401 from /usr/share/gems/gems/sup-0.10.2/lib/sup/source.rb:1:in `<top
402 (required)>'
403 from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'
404 from /usr/share/rubygems/rubygems/custom_require.rb:36:in `require'
405 from /usr/share/gems/gems/sup-0.10.2/lib/sup.rb:304:in `<top (required)>'
406 from /usr/share/rubygems/rubygems/custom_require.rb:55:in `require'
407 from /usr/share/rubygems/rubygems/custom_require.rb:55:in `require'
408 from /usr/share/gems/gems/sup-0.10.2/bin/sup:15:in `<top (required)>'
409 from /usr/bin/sup:19:in `load'
410 from /usr/bin/sup:19:in `<main>'
411
412 Any ideas?
413
414 Thanks in advance,
415 Phil
416 -------------- next part --------------
417 An HTML attachment was scrubbed...
418 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130114/31a16808/attachment-0001.html>
419
420 From marka@pobox.com Mon Jan 14 17:23:13 2013
421 From: marka@pobox.com (Mark Alexander)
422 Date: Mon, 14 Jan 2013 12:23:13 -0500
423 Subject: [sup-talk] help installing on FC17 on 64bit
424 In-Reply-To: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
425 References: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
426 Message-ID: <1358183706-sup-7745@bloovis.org>
427
428 Excerpts from Philippe LeCavalier's message of Mon Jan 14 10:12:58 -0500 2013:
429 > /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': superclass
430 > mismatch for class Iconv (TypeError)
431
432 I vaguely recall running into this when experimenting with sup on
433 Linux Mint 13 and got around the problem with the following patch. I
434 was just trying to see if it would even run at all on a new version of
435 Mint (I normally use sup on a machine running Mint 10). On this
436 experimental machine I had no mail in the index, and this was a patch
437 against my copy of the sup git repository, not against any installed
438 package. So no guarantees that this will work.
439
440 diff --git a/bin/sup b/bin/sup
441 index ad7a0d1..8e87a83 100755
442 --- a/bin/sup
443 +++ b/bin/sup
444 @@ -19,6 +19,7 @@ end
445
446 require 'fileutils'
447 require 'trollop'
448 +require 'iconv'
449 require "sup"; Redwood::check_library_version_against "git"
450
451 if ENV['SUP_PROFILE']
452
453 From matthieu.rakotojaona@gmail.com Thu Jan 17 20:15:01 2013
454 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
455 Date: Thu, 17 Jan 2013 21:15:01 +0100
456 Subject: [sup-talk] Github organization for sup and heliotrope
457 Message-ID: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
458
459 Hello,
460
461 I've set up a github organization at https://github.com/sup-heliotrope
462 for managing sup, heliotrope, turnsole and any needed bit in the
463 future. I've already added Hamish Downer (known as foobacca on github)
464 as an administrator; he has the rights to do whatever is needed on the
465 organization. Feel free to give me your github account names and I
466 will add you to the administrators team. I believe this is doable for
467 the moment because we are only a few people interested in
468 sup/heliotrope. If (when !) the popularity grows, we might want to
469 change the governance model.
470
471 I've been quite hesitant to use github because of the closed model (I
472 like running my own thing if possible) and wanted to run my own
473 redmine. However, github offers many advantages (uptime, speed, quick
474 visibility) and the data isn't that closed : wiki are just plain text
475 in git that can be exported, and there are more than complete APIs [0]
476 for issues. However, I'd like to keep the wiki in Hamish's ikiwiki
477 because I like it much better (but this is just personal preference)
478
479 I took the liberty of creating a repo for sup, which is just a
480 straight copy of git://gitorious.org/sup/mainline.git. I must admit I
481 don't follow sup's development that much, so feel free to do what you
482 want there. I've also set up a repo for sup with master being
483 William's master branch. I'm quite attracted to the git-flow [1]
484 model; I propose we follow it, and have therefore created a develop
485 branch which is just a branch at the same level as master. Please,
486 feel free to fork develop and code/test over it. I already have a
487 bunch of propositions to do and will soon put them in the repo (I just
488 realized my own repo was way too dirty to put it up now)
489
490 William, I know you are alive and well thanks to your tweetstream; If
491 you read this, I hope you won't take this organization as a treason of
492 any sort. It's just that the lack of activity on your repo is too
493 saddening for the development of heliotrope.
494
495 I'm sure we can do it.
496
497 See you soon,
498
499 [0] http://developer.github.com/v3/issues/
500 [1] http://nvie.com/posts/a-successful-git-branching-model/
501
502 --
503 Matthieu RAKOTOJAONA
504
505 From eg@gaute.vetsj.com Thu Jan 17 20:52:01 2013
506 From: eg@gaute.vetsj.com (Gaute Hope)
507 Date: Thu, 17 Jan 2013 21:52:01 +0100
508 Subject: [sup-talk] Github organization for sup and heliotrope
509 In-Reply-To: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
510 References: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
511 Message-ID: <50F86471.3000900@gaute.vetsj.com>
512
513 Hi,
514
515 I think this is a step in the right direction - given that there has
516 been silence on wmorgans part so long.
517
518 Kepping things in one place does work alot better, even if it means
519 sacrificing a few features - I think that keeping the wiki along with
520 the rest of the organization is the best. Also github is not linked or
521 dependant on any one admin / developer, so I think for this kind of
522 project it is ideal - expanding to a proper web site is no biggie with
523 github either, making future possible migration even easier.
524
525 I'd like to be part of the organization, but I am probably not going to
526 be active enough to be an administrator, github name: gauteh.
527
528 Cheers, Gaute
529
530 On to. 17. jan. 2013 kl. 21.15 +0100, Matthieu Rakotojaona wrote:
531 > Hello,
532 >
533 > I've set up a github organization at https://github.com/sup-heliotrope
534 > for managing sup, heliotrope, turnsole and any needed bit in the
535 > future. I've already added Hamish Downer (known as foobacca on github)
536 > as an administrator; he has the rights to do whatever is needed on the
537 > organization. Feel free to give me your github account names and I
538 > will add you to the administrators team. I believe this is doable for
539 > the moment because we are only a few people interested in
540 > sup/heliotrope. If (when !) the popularity grows, we might want to
541 > change the governance model.
542 >
543 > I've been quite hesitant to use github because of the closed model (I
544 > like running my own thing if possible) and wanted to run my own
545 > redmine. However, github offers many advantages (uptime, speed, quick
546 > visibility) and the data isn't that closed : wiki are just plain text
547 > in git that can be exported, and there are more than complete APIs [0]
548 > for issues. However, I'd like to keep the wiki in Hamish's ikiwiki
549 > because I like it much better (but this is just personal preference)
550 >
551 > I took the liberty of creating a repo for sup, which is just a
552 > straight copy of git://gitorious.org/sup/mainline.git. I must admit I
553 > don't follow sup's development that much, so feel free to do what you
554 > want there. I've also set up a repo for sup with master being
555 > William's master branch. I'm quite attracted to the git-flow [1]
556 > model; I propose we follow it, and have therefore created a develop
557 > branch which is just a branch at the same level as master. Please,
558 > feel free to fork develop and code/test over it. I already have a
559 > bunch of propositions to do and will soon put them in the repo (I just
560 > realized my own repo was way too dirty to put it up now)
561 >
562 > William, I know you are alive and well thanks to your tweetstream; If
563 > you read this, I hope you won't take this organization as a treason of
564 > any sort. It's just that the lack of activity on your repo is too
565 > saddening for the development of heliotrope.
566 >
567 > I'm sure we can do it.
568 >
569 > See you soon,
570 >
571 > [0] http://developer.github.com/v3/issues/
572 > [1] http://nvie.com/posts/a-successful-git-branching-model/
573 >
574 > --
575 > Matthieu RAKOTOJAONA
576 > _______________________________________________
577 > sup-talk mailing list
578 > sup-talk at rubyforge.org
579 > http://rubyforge.org/mailman/listinfo/sup-talk
580
581 From dmishd@gmail.com Thu Jan 17 21:09:18 2013
582 From: dmishd@gmail.com (Hamish D)
583 Date: Thu, 17 Jan 2013 21:09:18 +0000
584 Subject: [sup-talk] Github organization for sup and heliotrope
585 In-Reply-To: <50F86471.3000900@gaute.vetsj.com>
586 References: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
587 <50F86471.3000900@gaute.vetsj.com>
588 Message-ID: <CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com>
589
590 > I'd like to be part of the organization, but I am probably not going to
591 > be active enough to be an administrator, github name: gauteh.
592
593 OK, I've set up a team called committers (with commit access to all
594 repos) and added you. Also happy to make you an owner if you want.
595
596 I'm don't have strong views on where the wiki should be, but it would
597 be nice if people can just go and edit it with minimal fuss. It looks
598 like you'd have to be given access to edit the github wiki, so a bit
599 of a higher barrier to entry which I would prefer to not put in
600 people's way. But if we change our minds later (or if everyone
601 prefers it) then I have the pages as markdown, so transferring it
602 across to the github wiki would be very little work.
603
604 Right, should probably go and dig up various patches I've copied off
605 the email list that I wasn't sure about and turn them into pull
606 requests to open up discussion on them.
607
608 Hamish
609
610 From dmishd@gmail.com Thu Jan 17 23:43:01 2013
611 From: dmishd@gmail.com (Hamish D)
612 Date: Thu, 17 Jan 2013 23:43:01 +0000
613 Subject: [sup-talk] Github organization for sup and heliotrope
614 In-Reply-To: <CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com>
615 References: <CAMiZLn0QPzDPTxAuR9BcdWv2KPU4Zw-8wCQSSnLrYkq-tGSvow@mail.gmail.com>
616 <50F86471.3000900@gaute.vetsj.com>
617 <CAOxvSbctHrgaVXcpLVzasxKo8B+qLP6PCNLJBb2=YDFc5HObWA@mail.gmail.com>
618 Message-ID: <CAOxvSbd=VBvhC6YMN+xEJDj3Jk2rfVEv5HkdUv1_ufrrA96CeA@mail.gmail.com>
619
620 > Right, should probably go and dig up various patches I've copied off
621 > the email list that I wasn't sure about and turn them into pull
622 > requests to open up discussion on them.
623
624 I've started doing that with 4 well formatted patches I wasn't
625 entirely sure about (3 from Gaute) and put my comments on those pull
626 requests. If I get good answers we can merge them.
627
628 Got a few more diffs I'll have to get to another night.
629
630 Hamish
631
632 From fedzor@gmail.com Tue Jan 22 19:23:50 2013
633 From: fedzor@gmail.com (fedzor)
634 Date: Tue, 22 Jan 2013 14:23:50 -0500
635 Subject: [sup-talk] help installing on FC17 on 64bit
636 In-Reply-To: <1358183706-sup-7745@bloovis.org>
637 References: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
638 <1358183706-sup-7745@bloovis.org>
639 Message-ID: <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>
640
641 I'm getting a similar error. Why does this have to be, though? Why is this error coming up in the first place?
642
643 I'm posing the question now but I'll investigate shortly.
644
645 On Jan 14, 2013, at 12:23 PM, Mark Alexander wrote:
646
647 > Excerpts from Philippe LeCavalier's message of Mon Jan 14 10:12:58 -0500 2013:
648 >> /usr/share/rubygems/rubygems/custom_require.rb:36:in `require': superclass
649 >> mismatch for class Iconv (TypeError)
650 >
651 > I vaguely recall running into this when experimenting with sup on
652 > Linux Mint 13 and got around the problem with the following patch. I
653 > was just trying to see if it would even run at all on a new version of
654 > Mint (I normally use sup on a machine running Mint 10). On this
655 > experimental machine I had no mail in the index, and this was a patch
656 > against my copy of the sup git repository, not against any installed
657 > package. So no guarantees that this will work.
658 >
659 > diff --git a/bin/sup b/bin/sup
660 > index ad7a0d1..8e87a83 100755
661 > --- a/bin/sup
662 > +++ b/bin/sup
663 > @@ -19,6 +19,7 @@ end
664 >
665 > require 'fileutils'
666 > require 'trollop'
667 > +require 'iconv'
668 > require "sup"; Redwood::check_library_version_against "git"
669 >
670 > if ENV['SUP_PROFILE']
671 > _______________________________________________
672 > sup-talk mailing list
673 > sup-talk at rubyforge.org
674 > http://rubyforge.org/mailman/listinfo/sup-talk
675
676
677 From support@plecavalier.com Tue Jan 22 19:51:48 2013
678 From: support@plecavalier.com (Philippe LeCavalier)
679 Date: Tue, 22 Jan 2013 14:51:48 -0500
680 Subject: [sup-talk] help installing on FC17 on 64bit
681 In-Reply-To: <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>
682 References: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
683 <1358183706-sup-7745@bloovis.org>
684 <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>
685 Message-ID: <CAKada-46SFBeHsERvk8+3qV-ah+95pt+zQHwZYS_FRyecDuOXQ@mail.gmail.com>
686
687 On Tue, Jan 22, 2013 at 2:23 PM, fedzor <fedzor at gmail.com> wrote:
688
689 > I'm getting a similar error. Why does this have to be, though? Why is this
690 > error coming up in the first place?
691 >
692 > I'm posing the question now but I'll investigate shortly.
693 >
694 > dunno. I didn't attempt the patch suggested since I hadn't installed from
695 source and was too lazy to rebuilt the rpm.
696
697 Had you installed from source or rpm?
698 -------------- next part --------------
699 An HTML attachment was scrubbed...
700 URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20130122/82213856/attachment.html>
701
702 From matthieu.rakotojaona@gmail.com Tue Jan 22 20:14:25 2013
703 From: matthieu.rakotojaona@gmail.com (Matthieu Rakotojaona)
704 Date: Tue, 22 Jan 2013 21:14:25 +0100
705 Subject: [sup-talk] help installing on FC17 on 64bit
706 In-Reply-To: <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>
707 References: <CAKada-6gJLnz8sF1dVvF-R_QQ53KxXoLJSDpXx7W4WDB3XXEuw@mail.gmail.com>
708 <1358183706-sup-7745@bloovis.org>
709 <EECD4B7D-1CE9-4287-BCA3-D427465A49D2@gmail.com>
710 Message-ID: <CAMiZLn3iYci=-iUM44kmtFYNF1QFExkMySzBZnf7sTwrYrNaRQ@mail.gmail.com>
711
712 On Tue, Jan 22, 2013 at 8:23 PM, fedzor <fedzor at gmail.com> wrote:
713 > I'm getting a similar error. Why does this have to be, though? Why is this error coming up in the first place?
714
715 class Iconv is redefined in util.rb [0]. If you 'require "iconv"' over
716 that, there will be a conflict (which one is the real one). I really
717 don't know how to work around this one; the "easy" solution would be
718 to uninstall the iconv gem, but this isn't really long-term. If you
719 have time and courage, you should remove the custom Iconv class and
720 replace it with the Decoder[1] class from heliotrope. It's a
721 continuation of this Iconv class, taking into account the tricky 1.9.
722
723 [0] https://github.com/sup-heliotrope/sup/blob/dd129e12603f5c77846c5fa624b8f118d53fbd0e/lib/sup/util.rb#L661
724 [1] https://github.com/sup-heliotrope/sup/pull/1#issuecomment-12415689
725 --
726 Matthieu RAKOTOJAONA
727
728 From sup@zevv.nl Tue Jan 29 18:50:23 2013
729 From: sup@zevv.nl (Ico)
730 Date: Tue, 29 Jan 2013 19:50:23 +0100
731 Subject: [sup-talk] Automatically saving all attachements
732 Message-ID: <1359485303-sup-2521@pruts.nl>
733
734 Does anyone happen to have a hook that automatically saves all
735 attachements to a given directory when receiving or opening an e-mail?
736
737 Thanks,
738
739 Ico
740 --
741 :wq
742 ^X^Cy^K^X^C^C^C^C
743
744 From ezyang@MIT.EDU Tue Jan 29 23:40:28 2013
745 From: ezyang@MIT.EDU (Edward Z. Yang)
746 Date: Tue, 29 Jan 2013 15:40:28 -0800
747 Subject: [sup-talk] Automatically saving all attachements
748 In-Reply-To: <1359485303-sup-2521@pruts.nl>
749 References: <1359485303-sup-2521@pruts.nl>
750 Message-ID: <1359502714-sup-1444@javelin>
751
752 No, but OfflineIMAP+Sup effectively does this (as the attachments
753 will be stored with your mail).
754
755 A hook like this wouldn't be too hard to implement, but you will need to
756 think carefully about intended semantics: if you open an email twice,
757 should it save the attachment twice? If the hook is on-receive, what
758 should the attachment be named? How hard is it to find the attachment
759 you actually want, esp if you receive many? How do you deal with
760 multipart messages (txt + HTML versions; the HTML counts as an
761 "attachment").
762
763 Cheers,
764 Edward
765
766 Excerpts from Ico's message of Tue Jan 29 10:50:23 -0800 2013:
767 > Does anyone happen to have a hook that automatically saves all
768 > attachements to a given directory when receiving or opening an e-mail?
769 >
770 > Thanks,
771 >
772 > Ico
773
774 From eg@gaute.vetsj.com Wed Jan 30 09:32:16 2013
775 From: eg@gaute.vetsj.com (Gaute Hope)
776 Date: Wed, 30 Jan 2013 10:32:16 +0100
777 Subject: [sup-talk] Automatically saving all attachements
778 In-Reply-To: <1359485303-sup-2521@pruts.nl>
779 References: <1359485303-sup-2521@pruts.nl>
780 Message-ID: <5108E8A0.70005@gaute.vetsj.com>
781
782 On 29. jan. 2013 19:50, Ico wrote:
783 > Does anyone happen to have a hook that automatically saves all
784 > attachements to a given directory when receiving or opening an e-mail?
785 >
786 > Thanks,
787 >
788 > Ico
789 >
790
791 Maybe there is some inspiration to be found in the save_all_to_disk
792 function (keypress 'A' in thread view mode):
793
794 https://github.com/sup-heliotrope/sup/blob/master/lib/sup/modes/thread-view-mode.rb#L375
795
796 - gaute
797
798 From sup@zevv.nl Wed Jan 30 09:57:56 2013
799 From: sup@zevv.nl (Ico)
800 Date: Wed, 30 Jan 2013 10:57:56 +0100
801 Subject: [sup-talk] Automatically saving all attachements
802 In-Reply-To: <5108E8A0.70005@gaute.vetsj.com>
803 References: <1359485303-sup-2521@pruts.nl> <5108E8A0.70005@gaute.vetsj.com>
804 Message-ID: <1359539856-sup-2776@pruts.nl>
805
806 * On Wed Jan 30 10:32:16 +0100 2013, Gaute Hope wrote:
807
808 > Maybe there is some inspiration to be found in the save_all_to_disk
809 > function (keypress 'A' in thread view mode):
810
811 Just what the doctor ordered, thanks for the hint!
812 --
813 :wq
814 ^X^Cy^K^X^C^C^C^C
815