public inbox for
help / color / mirror / Atom feed
Subject: gnats/196: Not able to edit PRs
Date: Tue, 22 May 2001 23:24:00 -0000	[thread overview]
Message-ID: <> (raw)

>Number:         196
>Category:       gnats
>Synopsis:       Not able to edit PRs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue May 22 23:24:01 PDT 2001
>Originator:     Net
>Release:        unknown-1.0
Redhat Linux 2.2.14-5
I've created some PRs in various categories. The files reside with these permissions:
-rw-rw-rw-    1 root     root         1211 May 16 17:14 67

But, when I do an edit-pr 67, I get the following response from the edit-pr program. :
pr-edit: Invalid PR pending/67.

The PR resides in the GCCS directory, not the pending directory.
My default submitter is root in the config file.
Another strange thing is that in the same directory, i have another PR with number 66, with the SAME permissions
I am able to edit and modify 66, but not 67. This is just an example - its happening to many other PRs as well.

What could be the problem?
I'm attaching my categories file for reference. 


Content-Type: text/plain; name="categories"
Content-Disposition: inline; filename="categories"

#		    Possible categories for a PR.
# Any line which begins with a `#' is considered a comment, and GNATS
# will ignore it. 
# Each entry has the format:
# 	category:description:responsible:notify
# * `category' is the name of the classification for the PR.
# * `description' can be a normal text description for the
#   category, like "Development Tools" for the `tools' category.
# * `responsible' gives the name (which can be found in the remote
#   file) of the person who will be given responsibility for any PR
#   appearing in this category.
# * `notify' are other email addresses which should be given copies of
#    any PR in this category.
# The following category is mandatory for GNATS to work.
pending:Category for faulty PRs:gnats-admin:
# Sample categories:
doc:Documentation Bug:jeffrey:pesch
gcc:The GNU C compiler:wilson:tiemann
g++:The GNU C++ compiler:brendan:tiemann, mrs
#test:*Test Category:gnats-admin:

# Added by Venki for local project usage
# Format is category:description:responsible:notify

# Categories belonging to the GCCS project
SIP: SIP Module of GCCS project: mayank: shashi,mayank
MGCP: MGCP Module of GCCS project: prasad: shashi,prasad
SCL: SCL Module of GCCS project: imran: shashi,imran
InterWorking: InterWorking : shashi: shashi,prasad,mayank,imran

# Categories belonging to the SIP User Agent project
Registration: Registration Module of SIP UA: philip,dhanya: shashi,philip,dhanya,priya
Transaction: Transaction Module of SIP UA: dhanya: shashi,dhayna,priya
Parser: Parser Module of SIP UA: prakash: shashi,prakash,priya
SM: State Machine Module of SIP UA: mayank,priya: shashi,mayank,priya
Net If: Network Interface Module of SIP UA: dhanya: shashi,dhanya,priya
Receiver: Receiver Module of SIP UA: shashi: shashi,priya
SIP Lib: SIP Library Module of SIP UA: shashi: shashi,priya
PIL: Protocol Independent Layer Module of SIP UA: priya: shashi,priya
HAL: Hardware Abstraction Layer Module of SIP UA: prakash: shashi,prakash,priya
Simulator: Simulator Module of SIP UA: prakash: shashi,prakash,priya

# Categories for the GCCS project
GCCS: Generic Call Control System:prasad:shashi,prasad
test: Test Project Bug:venki:root

# More of test cases. REMOVE when done
# category:description:Person/Email id responsible:Also notify to this person
Venki: Venki's bugs: venki:venki
#Bugs : Bug's bugs: venki:venki

             reply	other threads:[~2001-05-22 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-22 23:24 m_venkateshkumar [this message]
2001-08-22 17:05 yngves
2001-08-23  5:14 Yngve Svendsen
2001-09-12 15:29 yngves

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).