From: kevin.mark@verizon.net (Kevin Mark)
Subject: [sup-talk] unable to sup-sync (new install)
Date: Mon, 17 Sep 2007 14:07:10 -0400 [thread overview]
Message-ID: <20070917180710.GI27677@horacrux> (raw)
In-Reply-To: <1190048921-sup-8612@south>
On Mon, Sep 17, 2007 at 10:12:15AM -0700, William Morgan wrote:
> Excerpts from Kevin Mark's message of Sun Sep 16 20:26:44 -0700 2007:
> > sudo gem install sup -y
> >
> > To run 'sup', I needed to add 'export PATH=/var/lib/gems/1.8/bin:"${PATH}"' to
> > .bashrc
>
> This is a symptom of how Ubuntu deals with gems. Unfortunately there's
> not a lot I can do about it from my end.
That sounds like what I expected, as I think Debian, more or less
upstream, may have a similar 'gem' status, although I have not checked.
>
> > /var/lib/gems/1.8/gems/sup-0.1/lib/sup/source.rb:80:in `done?': undefined method `>=' for nil:NilClass (NoMethodError)
>
> Is your maildir empty?
No.
> If so, this is lousy programming on my part. Sorry! If a maildir has
> no messages, Sup dies in this horrific way. I've just committed a
> patch to SVN to fix this. You can either pull down the SVN head, or
> just add a message to your maildir directory. :)
Hmm. No, my maildir has more than a GB. It includes a few subdirectories
of gziped mbox. And most of the maildir mail boxes start with '.', as in
'~/Maildir/.floss.sup_talk/'
>
> If the maildir isn't empty, then I need to think of another reason why
> this would happen.
Here is a sample:
/home/kevin/Maildir/.people.cothrige
/home/kevin/Maildir/.people.cothrige/cur
/home/kevin/Maildir/.people.cothrige/new
/home/kevin/Maildir/.people.cothrige/tmp
/home/kevin/Maildir/.people.dallas_a_clement
/home/kevin/Maildir/.people.dallas_a_clement/cur
/home/kevin/Maildir/.people.dallas_a_clement/new
/home/kevin/Maildir/.people.dallas_a_clement/tmp
/home/kevin/Maildir/.people.dana_spiegel
/home/kevin/Maildir/.people.dana_spiegel/cur
/home/kevin/Maildir/.people.dana_spiegel/new
/home/kevin/Maildir/.people.dana_spiegel/tmp
/home/kevin/Maildir/.people.david_weinehall
/home/kevin/Maildir/.people.david_weinehall/cur
/home/kevin/Maildir/.people.david_weinehall/new
/home/kevin/Maildir/.people.david_weinehall/tmp
/home/kevin/Maildir/.people.enrico_zini
I just have one thought as to the error:
there are many mail directories and some of them are empty. I archive
them every month. So '/home/kevin/Maildir/.david_weinehall/*' does not
have any messages.
I just thought of a second issue. In sup-config, you ask to define each
individual mailbox. What I did in the program 'mairix' is to define a
group of mail boxes with some kind of 'glob' so that I can say
'maildir/...' and mean all maildir's in that subdirectory.
cheers,
Kev
--
| .''`. == Debian GNU/Linux == | my web site: |
| : :' : The Universal |mysite.verizon.net/kevin.mark/|
| `. `' Operating System | go to counter.li.org and |
| `- http://www.debian.org/ | be counted! #238656 |
| my keyserver: subkeys.pgp.net | my NPO: cfsg.org |
|join the new debian-community.org to help Debian! |
|_______ Unless I ask to be CCd, assume I am subscribed _______|
next prev parent reply other threads:[~2007-09-17 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 3:26 Kevin Mark
2007-09-17 17:12 ` William Morgan
2007-09-17 18:07 ` Kevin Mark [this message]
2007-09-17 18:59 ` William Morgan
2007-09-18 6:26 ` Kevin Mark
2007-09-18 6:27 ` Magnus Therning
2007-09-18 23:18 ` William Morgan
2007-09-19 1:39 ` Kevin Mark
2007-09-18 6:38 ` Magnus Therning
2007-09-18 6:54 ` Kevin Mark
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=20070917180710.GI27677@horacrux \
--to=kevin.mark@verizon.net \
/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