From: "Chad C. Walstrom" <chewie@wookimus.net>
To: help-gnats@gnu.org
Cc: "Jamin W. Collins" <jcollins@asgardsrealm.net>
Subject: Re: send-pr error!
Date: Fri, 09 Nov 2001 02:55:00 -0000 [thread overview]
Message-ID: <20011214232040.GG21056@wookimus.net> (raw)
In-Reply-To: <1008358460.17204.8.camel@Cerberus>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
On Fri, Dec 14, 2001 at 01:34:20PM -0600, Jamin W. Collins wrote:
> No problem. At least you've given me a configuration that IS working
> to try to emulate. I will try installing Debian (2.2 r4) on my test
> system and see if I can get it working this weekend. Other than the
> distribution difference, did you (or anyone else) see anything wrong
> with the steps taken?
Not really. It looked fine. Sounds like you had it somewhat working.
I'm not an Apache guru, so I couldn't really tell you where things went
wrong. Debian's 'testing' branch is feature frozen, now. There are no
new packages entering, just RC bugfixes and security fixes. Given that
the gnats and gnatsweb packages (fairly recent CVS versions) install
fine, I'd recommend that.
The only thing you'll need to do with the gnats package is that if you
want to run mkdb on /var/lib/gnats/gnats-db, you'll have to recreate the
directory. The gnats user installs w/a home directory of
/var/lib/gnats/gnats-db. I'm planning on changing my local config so
that it defaults to /var/lib/gnats instead.
Other than that, I had very few problems.
--
Chad Walstrom <chewie@wookimus.net> | a.k.a. ^chewie
http://www.wookimus.net/ | s.k.a. gunnarr
Get my public key, ICQ#, etc. $(mailx -s 'get info' chewie@wookimus.net)
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
WARNING: multiple messages have this Message-ID
From: "Chad C. Walstrom" <chewie@wookimus.net>
To: help-gnats@gnu.org
Cc: "Jamin W. Collins" <jcollins@asgardsrealm.net>
Subject: Re: send-pr error!
Date: Fri, 14 Dec 2001 15:24:00 -0000 [thread overview]
Message-ID: <20011214232040.GG21056@wookimus.net> (raw)
Message-ID: <20011214152400.2WzaiVIRwkJ0OnoIXi9wx2mur0uYz4oFzK-j5i84pv0@z> (raw)
In-Reply-To: <1008358460.17204.8.camel@Cerberus>
On Fri, Dec 14, 2001 at 01:34:20PM -0600, Jamin W. Collins wrote:
> No problem. At least you've given me a configuration that IS working
> to try to emulate. I will try installing Debian (2.2 r4) on my test
> system and see if I can get it working this weekend. Other than the
> distribution difference, did you (or anyone else) see anything wrong
> with the steps taken?
Not really. It looked fine. Sounds like you had it somewhat working.
I'm not an Apache guru, so I couldn't really tell you where things went
wrong. Debian's 'testing' branch is feature frozen, now. There are no
new packages entering, just RC bugfixes and security fixes. Given that
the gnats and gnatsweb packages (fairly recent CVS versions) install
fine, I'd recommend that.
The only thing you'll need to do with the gnats package is that if you
want to run mkdb on /var/lib/gnats/gnats-db, you'll have to recreate the
directory. The gnats user installs w/a home directory of
/var/lib/gnats/gnats-db. I'm planning on changing my local config so
that it defaults to /var/lib/gnats instead.
Other than that, I had very few problems.
--
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8GolIDMcLGCBsWv0RAsMYAKCUBLVt6B0Nsmm91wpGau/uD+Dz7QCfSNic
ZPfQ33sCAhd2aMwm0DERNH4=
=ufE/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2001-12-14 23:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 10:23 Chad C. Walstrom
2001-11-08 10:23 ` Jamin W. Collins
2001-11-08 13:05 ` Chad C. Walstrom
2001-11-08 18:22 ` Jamin W. Collins
2001-11-09 2:55 ` Chad C. Walstrom [this message]
2001-11-09 14:16 ` Jamin W. Collins
2001-11-09 14:17 ` Yngve Svendsen
2001-12-15 2:54 ` Yngve Svendsen
2001-11-10 2:46 ` Milan Zamazal
2001-11-12 10:40 ` My inability to configure Gnats(web)4 (was send-pr error!) Jamin W. Collins
2001-11-12 11:28 ` Jamin W. Collins
2001-11-17 13:06 ` Jamin W. Collins
2001-12-22 13:41 ` Jamin W. Collins
2001-12-16 8:37 ` Jamin W. Collins
2001-12-15 8:36 ` Jamin W. Collins
2001-12-15 7:24 ` send-pr error! Milan Zamazal
2001-12-14 20:45 ` Jamin W. Collins
2001-12-14 15:24 ` Chad C. Walstrom
2001-12-14 11:39 ` Jamin W. Collins
2001-12-14 10:55 ` Chad C. Walstrom
2001-12-14 8:34 ` Jamin W. Collins
2001-11-08 10:23 ` Yngve Svendsen
2001-11-08 13:08 ` Chad C. Walstrom
2001-11-09 18:10 ` Milan Zamazal
2001-12-15 7:24 ` Milan Zamazal
2002-01-17 19:14 ` Hugo Gayosso
2001-12-14 11:17 ` Chad C. Walstrom
2001-12-14 9:28 ` Yngve Svendsen
2001-12-14 8:27 ` Chad C. Walstrom
-- strict thread matches above, loose matches on Subject: below --
2001-11-06 9:23 Choi, Jang-Wook
2001-11-06 9:25 ` Yngve Svendsen
2001-11-12 10:06 ` Milan Zamazal
2001-11-12 10:40 ` Yngve Svendsen
2001-11-18 19:55 ` Milan Zamazal
2001-12-23 12:36 ` Milan Zamazal
2001-12-15 10:52 ` Yngve Svendsen
2001-12-15 7:24 ` Milan Zamazal
2001-12-14 3:09 ` Yngve Svendsen
2001-12-14 0:43 ` Choi, Jang-Wook
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=20011214232040.GG21056@wookimus.net \
--to=chewie@wookimus.net \
--cc=help-gnats@gnu.org \
--cc=jcollins@asgardsrealm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).