Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: ehabkost@raisama.net (Eduardo Habkost)
Subject: [sup-talk] Removing sources (+ crash after trying)
Date: Wed, 5 Nov 2008 12:17:00 -0200	[thread overview]
Message-ID: <20081105141700.GF5247@blackpad> (raw)

Hi,

While testing sup, sometimes I had typed incorrectly the path for sup-add,
and I've found any way to remove the sources I've added. Is there a way
to do that?

Risking doing something stupid, I simply removed the source from
~/.sup/sources.yaml, and now I am getting this when running sup-sync:

[Wed Nov 05 11:54:15 -0200 2008] saving index and sources...
/usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/label.rb:81:in `sort': undefined method `<=>' for :"kvm-devel":Symbol (NoMethodError)
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/label.rb:81:in `save'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/label.rb:81:in `open'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/label.rb:81:in `save'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `send'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup/util.rb:499:in `method_missing'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/lib/sup.rb:131:in `finish'
        from /usr/lib/ruby/gems/1.8/gems/sup-999/bin/sup-sync:243
        from /usr/bin/sup-sync:19:in `load'
        from /usr/bin/sup-sync:19

I have little ruby experience, so I have no clue on what could be causing
that error. I am not even sure if the error was really caused by the
mess I did on sources.yaml.

I am running sup from mainline.git.

I've did the 'sup-dump;rm -rf ~/.sup/ferret;sup-sync' stuff mentioned
on the FAQ, but the problem persists.

My labels.txt file is empty (maybe because of the crash?). My sources.yaml
currently looks like this:

=========================================
--- 
- !masanjin.net,2006-10-01/Redwood/Maildir 
  uri: maildir:/home/ehabkost/mail/lkml-l/
  cur_offset: 12258932500006359
  usual: true
  archived: true
  id: 1
  labels: 
  - lkml
  mtimes: 
    cur: 2008-11-03 10:19:13 -02:00
    new: 2008-11-05 11:54:10 -02:00
- !masanjin.net,2006-10-01/Redwood/Maildir 
  uri: maildir:/home/ehabkost/mail/kvm-devel-l/
  cur_offset: 12258909480004381
  usual: true
  archived: true
  id: 2
  labels: 
  - kvm-devel
  mtimes: 
    cur: 2008-11-04 18:19:50 -02:00
    new: 2008-11-05 11:15:48 -02:00
- !masanjin.net,2006-10-01/Redwood/Maildir 
  uri: maildir:/home/ehabkost/mail/rh/memo-l/
  cur_offset: 12258930050005616
  usual: true
  archived: true
  id: 3
  labels: 
  - rh-memo
  mtimes: 
    cur: 2008-10-13 20:09:02 -03:00
    new: 2008-11-05 11:50:05 -02:00
- !masanjin.net,2006-10-01/Redwood/Maildir 
  uri: maildir:/home/ehabkost/mail/sup-talk-l/
  cur_offset: 12258880050004663
  usual: true
  archived: true
  id: 6
  labels: 
  - sup-talk
  mtimes: 
    cur: 2008-11-05 11:31:51 -02:00
    new: 2008-11-05 10:42:29 -02:00
- !masanjin.net,2006-10-01/Redwood/SentLoader 
  cur_offset: 919
- !masanjin.net,2006-10-01/Redwood/DraftLoader 
  cur_offset: 0
=====================

-- 
Eduardo


             reply	other threads:[~2008-11-05 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05 14:17 Eduardo Habkost [this message]
2008-11-05 18:34 ` William Morgan
2008-11-05 18:54   ` Eduardo Habkost
2008-11-05 20:49     ` 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=20081105141700.GF5247@blackpad \
    --to=ehabkost@raisama.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