From: jeff.covey@pobox.com (jeff covey)
Subject: [sup-talk] ~/.sup/sources.yaml disappearing
Date: Sun, 10 Jun 2007 14:00:44 -0400 [thread overview]
Message-ID: <1181497661-sup-448@mona> (raw)
has anyone else experienced a problem with ~/.sup/sources.yaml being wiped
out? it's gone away on me a few times, though i'm not sure exactly what
happens to it. sup hits an error, and either deletes sources.yaml or makes
it an empty file. i can't say which, i just suddenly notice that my sup
wrapper script is running sup-add to add a bunch of sources which should
already be there, and when i look at sources.yaml, it's starting to rebuild
my supiverse from scratch.
i'm afraid i can't say what caused it, either. the latest time it happened
was with an error about draw_screen, but the backtrace was gone too fast for
me to grab it.
sorry to give you so little information, william. maybe you could check the
handling of sources.yaml generally? maybe there's a place where it's opened
for writing, then never closed before an error occurs?
i'll try to get more details if it happens again.
thanks,
--
jeff covey
http://jeffcovey.net/
next reply other threads:[~2007-06-10 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 18:00 jeff covey [this message]
2007-06-10 21:57 ` jeff covey
2007-06-11 15:42 ` William Morgan
2007-06-13 0:48 ` 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=1181497661-sup-448@mona \
--to=jeff.covey@pobox.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