public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: rouveyro@polyspace.com
To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org
Subject: gnats/397: can not remove the gnats.lock file with queue-pr / multiple databases
Date: Thu, 04 Jul 2002 06:39:00 -0000	[thread overview]
Message-ID: <E17Q5Da-0003Gk-00@fencepost.gnu.org> (raw)

>Number:         397
>Category:       gnats
>Synopsis:       can not remove the gnats.lock file with queue-pr / multiple databases
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 04 07:56:14 -0400 2002
>Originator:     Benjamin
>Release:        gnats 3.113
>Organization:
none
>Environment:
linux
>Description:
Hi

I installed last year a gnats-database and everything was fine. But yesterday, I tried to create a new database : the new mail was "bugs-supp@..." and everything seemed to be fine : when I e-mailed a PR, gnats just queued it in the good directory. But each time queue-pr was launched, thanks to the crontab, a gnats.lock file is created, but is not removed. The problem is now for the new, and the old database : PRs are queued, and that's all folks !

PS: I know there was a known-bug for gnats 3.111 but I'm using gnats 3.113
PPS: If I delete gnats.lock just after the queue-pr, I don't receive a mail acknowledgement, although my config file has ACKNOWLEGE=1

Thanks for an answer
>How-To-Repeat:

>Fix:
Unknown
>Unformatted:
 

_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs


                 reply	other threads:[~2002-07-04 13:39 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=E17Q5Da-0003Gk-00@fencepost.gnu.org \
    --to=rouveyro@polyspace.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: 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).