From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Removing sources (+ crash after trying)
Date: Wed, 05 Nov 2008 10:34:13 -0800 [thread overview]
Message-ID: <1225909971-sup-384@entry> (raw)
In-Reply-To: <20081105141700.GF5247@blackpad>
Reformatted excerpts from Eduardo Habkost's message of 2008-11-05:
> 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?
What you did is the best option so far: edit sources.yaml directly.
> [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)
Weird. I'm not sure what would've caused this, but I doubt it was the
removal of that source.
At any rate, I've pushed a "defensive programming" patch that should fix
this, so git pull and see if it works now.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-11-05 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 14:17 Eduardo Habkost
2008-11-05 18:34 ` William Morgan [this message]
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=1225909971-sup-384@entry \
--to=wmorgan-sup@masanjin.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