reassign 542136 bugs.debian.org tag 542136 - pending retitle 542136 'block' attempts to block by requested bug and #1, fails to grab lock thanks
On Mon, Aug 17, 2009 at 09:42:44PM -0400, Frédéric Brière wrote:
> bts sends "block X with Y" messages, which apparently cont...@b.d.o
> doesn't like too much. Shouldn't this be "block X by Y", according to
> the documentation?
Looking into this further, the bug has nothing to do with "by" vs.
"with". As such, I'll back out the change from devscripts and reassign
to debbugs so Don can take a look at it.
> >From debb...@rietz.debian.org Mon Aug 17 21:01:47 2009
> Return-Path: <debb...@rietz.debian.org>
> To: =?UTF-8?Q?Fr=C3=A9d=C3=A9ric_?= =?UTF-8?Q?Bri=C3=A8re?=
> <fbri...@fbriere.net>
> Cc: Debian logcheck Team <logcheck-de...@lists.alioth.debian.org> (logcheck
> for {475553})
> Subject: Processed (with 1 errors): block 475553 with 174331
> In-Reply-To: <1250556585-3295-bts-fbri...@fbriere.net>
> References: <1250556585-3295-bts-fbri...@fbriere.net>
> Message-ID: <handler.s.c.125055658827624.transcr...@bugs.debian.org>
> Sender: Debian BTS <debb...@rietz.debian.org>
> Date: Tue, 18 Aug 2009 01:00:10 +0000
>
> Processing commands for cont...@bugs.debian.org:
>
> > block 475553 with 174331
> Bug #475553 [logcheck] Please add support for RFC 3339 high precision
> timestamps
> Was not blocked by any bugs.
> Added blocking bug(s) of 475553: 1 and 174331
> Failed to set blocking bugs of 475553: Unable to get file lock while trying
> to add blocker '1'.
The command was properly parsed as adding #174331 as a blocker for
#475553, but some other problem caused it to also see #1 as being added
and, potentially related, fail to grab a lock to adjust the status.
> >
> End of message, stopping processing here.
>
> Please contact me if you need assistance.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org>
signature.asc
Description: Digital signature
