public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Chad C. Walstrom" <chewie@wookimus.net>
To: Yngve Svendsen <yngve.svendsen@clustra.com>
Cc: "Chad C. Walstrom" <chewie@wookimus.net>, help-gnats@gnu.org
Subject: Re: send-pr error!
Date: Fri, 14 Dec 2001 11:17:00 -0000	[thread overview]
Message-ID: <20011214191007.GD21056@wookimus.net> (raw)
Message-ID: <20011214111700.Hpkd4l5p-JTXyLjlQk1k73YLhUYIwOWg8pAa1F4G2oo@z> (raw)
In-Reply-To: <5.1.0.14.2.20011214182038.00a15100@10.10.1.1>

On Fri, Dec 14, 2001 at 06:22:30PM +0100, Yngve Svendsen wrote:
> Actually, GNATS is supposed to be *the* bug tracking system for
> Savannah, but we have had very little resources to integrate things
> properly.

Low on disk space?  Bodies (sysadmins)? Needed a dedicated bug tracking
server?

> We need to fix the admin interface so it work with GNATS 4, then
> polish it a bit, and we need a proper system to integrate Savannah
> user accts with GNATS.

Hmm...  Ever think of doing a pam module for gnats?  It would allow you
to use any authentication pam supports.  Of course, that doesn't take
away the need to manage user permissions, but at least it'll take away
the dependency upon a gnats-specific passwd file.  .oO(mmm...  ldap +
kerberose...)

<offtopic>
    You know.  One thing I never understood was the fact that the passwd
    program didn't have a target file option.  Take NIS, for example.
    Most people revert to manually editing and maintaining a separate
    map file for passwd and group in /var/yp/<DOMAIN> for security
    reason (though that's like spitting in the wind if you ask me).  Why
    not just use a modified passwd program and specify
    /var/yp/maps/passwd?
</offtopic>

Anyway, it looks like that last time PAM popped up on the radar for
gnats was back in October 1999.  Regardless, it would be a welcome
addition.  May as well add that as a feature request. ;-)

Well, back to work.

-- 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8Gk6PDMcLGCBsWv0RAjWjAKDW7Xq4AsSzrPWYkD1bbirCDzPxSgCcD9Uh
c63/AByozetwmN6KOP4LsB0=
=TjoK
-----END PGP SIGNATURE-----

  reply	other threads:[~2001-12-14 11:17 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 ` Yngve Svendsen
2001-11-08 13:08   ` Chad C. Walstrom [this message]
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-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
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-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=20011214191007.GD21056@wookimus.net \
    --to=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    --cc=yngve.svendsen@clustra.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).