public inbox for gnats-prs@sourceware.org help / color / mirror / Atom feed
From: frank@brightail.com To: gnats-gnats@sourceware.cygnus.com Subject: gnats/21: when category change fails, gnatsd leaves #.old Date: Mon, 01 Nov 1999 17:04:00 -0000 [thread overview] Message-ID: <19991102005800.2695.qmail@sourceware.cygnus.com> (raw) >Number: 21 >Category: gnats >Synopsis: when category change fails, gnatsd leaves #.old >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Nov 01 17:04:01 PST 1999 >Closed-Date: >Last-Modified: >Originator: frank@brightail.com >Release: gnats 3.111 >Organization: >Environment: Solaris 2.6 >Description: I added two new categories to the categories file, but neglected to run `mkcat`. Then I tried to move an existing report to a new category with gnatsweb. gnatsweb gave a nice error message about a missing dir, so I remembered and ran `mkcat`. Then I tried to re-update the bug report, and it failed with "couldn't find PR ..." Looking in the directoty I found that the bug had been moved to bug.old, but not moved back. Better than losing the info, but not great. >How-To-Repeat: add a cat to categories file don't run mkcat chage an existing report to new report. notice the report is "missing" >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~1999-11-01 17:04 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19991102005800.2695.qmail@sourceware.cygnus.com \ --to=frank@brightail.com \ --cc=gnats-gnats@sourceware.cygnus.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: 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).