Your message dated Sun, 15 Apr 2007 22:39:11 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#419468: bts: unrecognised BTS URL type
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: devscripts
Version: 2.9.26
Hi,
When starting bts to look at a bug I sometimes see messages like this
passing by:
[EMAIL PROTECTED]:~$ bts show 155467
bts: in href_to_filename: unrecognised BTS URL type: <a
href="bugreport.cgi?bug=155467;mbox=yes;mboxstatus=yes">
bts: in href_to_filename: unrecognised BTS URL type: <a
href="bugreport.cgi?bug=155467;mboxmaint=yes;mbox=yes">
I'm not sure if this is anything important or not, but I didn't see it
happening with the sarge version, and I always wonder why I see strange
messages.
Kurt
--- End Message ---
--- Begin Message ---
Version: 2.10.0
Hi,
On Sun, 2007-04-15 at 23:12 +0200, Kurt Roeckx wrote:
> Package: devscripts
> Version: 2.9.26
>
> Hi,
>
> When starting bts to look at a bug I sometimes see messages like this
> passing by:
> [EMAIL PROTECTED]:~$ bts show 155467
> bts: in href_to_filename: unrecognised BTS URL type: <a
> href="bugreport.cgi?bug=155467;mbox=yes;mboxstatus=yes">
> bts: in href_to_filename: unrecognised BTS URL type: <a
> href="bugreport.cgi?bug=155467;mboxmaint=yes;mbox=yes">
>
> I'm not sure if this is anything important or not, but I didn't see it
> happening with the sarge version, and I always wonder why I see strange
> messages.
The messages are caused by changes in the structure of the pages
returned by the BTS (specifically the addition of status and maintainer
mboxes).
This was previously reported as #414200, which was fixed in 2.10.0, so
marking accordingly.
Regards,
Adam
--- End Message ---
