From: marc.hartstein@alum.vassar.edu (Marc Hartstein)
Subject: [sup-talk] Workaround for sup-config crash in 0.4 on some platforms
Date: Fri, 04 Apr 2008 17:43:44 -0400 [thread overview]
Message-ID: <1207345193-sup-7377@cabinet> (raw)
Some users have been having trouble where sup-config crashes on a stock
0.4 install. While updating to git is supposed to correct this problem,
many people won't want to go to that effort just to see if sup even
works. For them, this workaround:
1. Create and edit ~/.sup/config.yaml to contain the following:
-------------------- SNIP HERE --------------------
---
:accounts:
:default:
:name: foo
:email: foo at bar
-------------------- SNIP HERE --------------------
2. Run sup-config as normal.
( This has been crossposted to
http://sup.rubyforge.org/wiki/wiki.pl?WorkAroundSupConfigCrash )
Hope this helps somebody.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20080404/0ca096c2/attachment.bin
next reply other threads:[~2008-04-04 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 21:43 Marc Hartstein [this message]
2008-04-06 0:06 ` William Morgan
2008-04-10 15:39 ` Marc Hartstein
2008-04-20 22:26 ` 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=1207345193-sup-7377@cabinet \
--to=marc.hartstein@alum.vassar.edu \
/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