public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: kmcfarland@starentnetworks.com To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org Subject: gnats/381: auto category creation doesn't set other permission - query-pr can't access Date: Tue, 23 Apr 2002 06:20:00 -0000 [thread overview] Message-ID: <E16zzqm-00083i-00@fencepost.gnu.org> (raw) >Number: 381 >Category: gnats >Synopsis: auto category creation doesn't set other permission - query-pr can't access >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 23 08:56:51 -0400 2002 >Originator: kmcfarland@starentnetworks.com >Release: beta4 3.999 >Organization: >Environment: Debian Linux >Description: I have gnats4 up and running just fine. Added a new category but did not run mkcat. The new documentation says that this isn't required. When a new bug came in for that Category the directory was created fine, but the permission for that category didn't allow read/execute access for "other". The gnatsweb was able to do querys/viewing of these bugs, but query-pr run by a individual would't allow the user to see the bugs in this new category. I changed the permission for that directory and everything was fine. It appears that gnats should do this when auto-creating new categories. /usr/bin/query-pr 3686 -d myDB would return a blank line. It created a dir like this: =========================== drwxr-x--- 2 gnats gnats 4096 Apr 22 16:56 . vs. Needs to be like this: ====================== drwxr-xr-x 2 gnats gnats 4096 Apr 22 16:56 . >How-To-Repeat: >Fix: Unknown >Unformatted: _______________________________________________ Gnats-prs mailing list Gnats-prs@gnu.org http://mail.gnu.org/mailman/listinfo/gnats-prs
next reply other threads:[~2002-04-23 13:20 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-23 6:20 kmcfarland [this message] 2002-05-26 11:24 ` Lars Henriksen
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=E16zzqm-00083i-00@fencepost.gnu.org \ --to=kmcfarland@starentnetworks.com \ --cc=bug-gnats@gnu.org \ --cc=gnats-prs@gnu.org \ --cc=pdm-gnats@zamazal.org \ /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: linkBe 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).