Your message dated Sat, 20 Sep 2008 10:45:49 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: monodoc-mysql5.0-manual: node `mysql' is not defined on 
the documentation map
has caused the Debian Bug report #485741,
regarding monodoc-mysql5.0-manual: node `mysql' is not defined on the 
documentation map
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
485741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485741
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: monodoc-mysql5.0-manual
Version: 5.2.1+dfsg-1
Severity: normal


Hi,

here is the problem:

# monodoc --make-index
node `mysql' is not defined on the documentation map
[...]


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages monodoc-mysql5.0-manual depends on:
ii  monodoc-manual                1.9-1.1    compiled XML documentation from th

monodoc-mysql5.0-manual recommends no packages.

-- no debconf information

-- 
Laurent Bonnaud.
http://www.lis.inpg.fr/pages_perso/bonnaud/





--- End Message ---
--- Begin Message ---
fixed 485741 5.2.1+dfsg-2
thanks

Hello Laurent,

On Wed, 11 Jun 2008 09:14:50 +0200, Laurent Bonnaud wrote:
> Hi,
> 
> here is the problem:
> 
> # monodoc --make-index
> node `mysql' is not defined on the documentation map
> [...]

I'm sorry I haven't been able to reproduce the problem. I have 5.2.1+dfsg-2
installed, thus marking this bug as fixed in this version (and closing it).

Could you please try to install 5.2.1+dfsg-2, and see if that still happens? If
yes, please feel free to reopen the bug by sending:

reopen 485741
found 485741 5.2.1+dfsg-2
thanks

to [EMAIL PROTECTED], CCing also [EMAIL PROTECTED] and me :) (and
explaining what happened, in case)

Kindly,
David

-- 
 . ''`.  Debian maintainer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://snipr.com/qa_page
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to