Subject: [sup-talk] Sup bug tracker down for >week?

From: Shadowfirebird <[email-masked]>
Date: Mon, 21 Mar 2011 09:53:12 +0000

Does everyone else see the sup bug tracker as down?  It seems to have been
down for at least a week.

My Sup has crashed, no-one on this list seems to be able to help me and the
bug tracker is down.  Much as I like Sup, I think this might be game over as
far as I'm concerned...

-- 
What a tangled web we weave / Go 'round with circumstance / Someone show me
how to tell / The dancer from the dance...
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Shadowfirebird <[email-masked]>
Date: Tue, 22 Mar 2011 16:47:47 +0000

Having tried to recreate the index, after four hours this process has
crashed too.

/usr/lib/ruby/gems/1.8/gems/lockfile-1.4.3/lib/lockfile.rb:364:in `unlock':
/home/fred/.sup/lock (Lockfile::StolenLockError)

from /usr/lib/ruby/gems/1.8/gems/sup-0.12/lib/sup/index.rb:87:in `unlock'

from /usr/lib/ruby/gems/1.8/gems/sup-0.12/bin/sup-sync:206

from /usr/bin/sup-sync:19:in `load'

from /usr/bin/sup-sync:19

That's it for me I think.  Maybe I'll try Sup again after it's been through
a few more versions.
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk

---

From: Michael Stapelberg <[email-masked]>
Date: Mon, 21 Mar 2011 16:20:51 +0100

Hi Shadowfirebird,

> down for at least a week.

William has taken it down due to the amount of spambot traffic killing his
server, see his message from 2011-01-10 with Message ID
[email-masked].

Best regards,
Michael

---

From: Amadeusz Żołnowski <[email-masked]>
Date: Mon, 21 Mar 2011 16:31:12 +0100

Excerpts from Shadowfirebird's message of Mon Mar 21 10:53:12 +0100
2011:
> Does everyone else see the sup bug tracker as down?  It seems to have
> been down for at least a week.

“The page you are looking for is temporarily unavailable.
Please try again later.”

> My Sup has crashed,

How? If it still crashes after restart, try to recreate the index. It
helped once when I had a total crash.

-- 
Amadeusz Żołnowski

PGP key fpr: C700 CEDE 0C18 212E 49DA  4653 F013 4531 E1DB FAB5
_______________________________________________
sup-talk mailing list
[email-masked]
http://rubyforge.org/mailman/listinfo/sup-talk