Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: vasudeva@linkswarm.com (vasudeva)
Subject: [sup-talk] new user of sup
Date: Tue, 13 Nov 2007 13:41:29 -0500	[thread overview]
Message-ID: <20071113184129.GA11753@lenin.sovietwar.org> (raw)
In-Reply-To: <1194912687-sup-4696@south>

* on 11-12-07, William Morgan wrote:
> Excerpts from vasudeva's message of Wed Oct 31 11:05:10 -0700 2007:
> > I had an issue like this, and found it to be related somehow to the
> > following lines being present in my ~/.sup/sources.yaml...
> > 
> > - !masanjin.net,2006-10-01/Redwood/SentLoader
> >   cur_offset: 29245
> > - !masanjin.net,2006-10-01/Redwood/DraftLoader
> >   cur_offset: 4
> > 
> > It seems if I snipped those out, then sup-add would actually add all
> > the sources I told it, not simply the final one. That is, if those
> > lines were present, sup-add seemed to overwrite any recently-added
> > source with the next source I'd add. (The two lines get generated
> > and replaced by sup at some point.)
> 
> I'm not able to reproduce this. Does the same behavior happen now? If
> so, can you post a source.yaml and some commands that exhibit the
> overwriting?

I've just svn updated sup, and I can reproduce this.

I'm using the same sup-add command I documented in the wiki under
AddingSources...

http://sup.rubyforge.org/wiki/wiki.pl?AddingSources

to wit...

for i in $(find muttmail -type f); do ruby -I lib -w sup/trunk/bin/sup-add  -l `basename $i` -a mbox://`pwd`/$i; done

Here's my ~/.sup/sources.yaml before I start...

***
cat ~/.sup/sources.yaml
---
- !masanjin.net,2006-10-01/Redwood/MBox/Loader
  uri: mbox:///home/vasudeva/muttmail/projects/amsterdam
  cur_offset:
  usual: true
  archived: true
  id: 3
  labels:
  - amsterdam
- !masanjin.net,2006-10-01/Redwood/SentLoader
  cur_offset: 29245
- !masanjin.net,2006-10-01/Redwood/DraftLoader
  cur_offset: 4
***

And here it is after letting the batch sup-add command run...

***
cat ~/.sup/sources.yaml
---
- !masanjin.net,2006-10-01/Redwood/MBox/Loader
  uri: mbox:///home/vasudeva/muttmail/windows.lib
  cur_offset:
  usual: true
  archived: true
  id: 3
  labels:
  - windows.lib
- !masanjin.net,2006-10-01/Redwood/SentLoader
  cur_offset: 29245
- !masanjin.net,2006-10-01/Redwood/DraftLoader
  cur_offset: 4
***

The find routine returns 67 sources, the names of which are all
alpha plus the following characters: -_+.@

I'll send you a list of the sourcenames off-list, where my
meticulously-sorted furryporn email archive can't come back to haunt
me some day.



/></

--
linkswarm.com :: Collaborative Insolence
vasudeva.linkswarm.com/gallery :: For The Faint of Heart



  reply	other threads:[~2007-11-13 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-31 17:08 Manish Sapariya
2007-10-31 18:05 ` vasudeva
2007-11-02  4:02   ` William Morgan
2007-11-13  0:13   ` William Morgan
2007-11-13 18:41     ` vasudeva [this message]
2007-11-26 20:37       ` William Morgan

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=20071113184129.GA11753@lenin.sovietwar.org \
    --to=vasudeva@linkswarm.com \
    /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