public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Gray <andrewg@gnu.org>
To: Chad Walstrom <chewie@wookimus.net>,
	Yngve Svendsen <yngve.svendsen@sun.com>
Cc: help-gnats@gnu.org
Subject: Restoring GNATS database
Date: Thu, 15 Apr 2004 14:32:00 -0000	[thread overview]
Message-ID: <20040415122435.GB12184@nandakot.anu.edu.au> (raw)

Hi Yngve and Chad,

One important outstanding issue with GNATS is the bug database.  After
the main GNU host was cracked in August last year the GNATS database
was unavailable.  I have started looking at getting it back on-line again.

Two key problems are (1) recoving the data from the old database and
(2) identifying a machine that can host the GNATS database.

I have sent a message to the GNU sysadmins and received a response.

Regarding recovering the old database, they asked where the data was.
I guessed it would be in /usr/local/com/gnatsdb or /usr/com/gnatsdb.
Yngve, do you recall what directory the GNATS database on fencepost
was in?

Regarding running the GNATS database on fencepost, the response included:

> Can GNATS run as a non-root user?  If so, reinstalling on
> fencepost shouldn't be a problem.  I recall that in years past the
> installation was poorly maintained / undocumented, and whenever we had
> to swap out hardware or reinstall fencepost, GNATS broke.  Is there a
> stable Debian package that we can keep installed on the machine, or
> does the install need to constantly change?

My response included:

> Yes, GNATS normally run as a specially created "gnats" user.  However,
> I think that root access was required to administer that GNATS and
> Gnatsweb installation.

> I think there is a stable Debian package (3.999.beta1+cvs20020303-1),
> but I'm not sure if we would need to run a newer version of GNATS.
> 
> Another option I am considering is using a cheap Linux virtual hosting
> service for the GNATS database.  If installing and maintaining
> GNATS/Gnatsweb on fencepost would involve significant work for the
> fencepost admins, this approach might shift the admin burden to the
> GNATS maintainer and/or contributers.

Chad, was my response to the question about the stable Debian package
correct?

The Linux virtual hosting service I was thinking of was on jvds.com.
They have a plan that is USD 12.50 per month, I would be happy to pay
this for a year if it would help get the GNATS database online again
quickly.  What do you think about using such a service for the GNATS
database?

-- 
Andrew Gray
GNU GNATS Maintainer




_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://mail.gnu.org/mailman/listinfo/help-gnats

             reply	other threads:[~2004-04-15 12:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 14:32 Andrew Gray [this message]
2004-04-15 16:01 ` Yngve Svendsen
2004-04-15 17:08   ` Chad Walstrom
2004-04-15 17:57     ` [OT] CC'ing and the list Chad Walstrom
2004-04-16 20:56     ` Restoring GNATS database Mel Hatzis
2004-04-16  8:18   ` Andrew Gray
2004-04-15 16:20 ` Chad Walstrom

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=20040415122435.GB12184@nandakot.anu.edu.au \
    --to=andrewg@gnu.org \
    --cc=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    --cc=yngve.svendsen@sun.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).