[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#442416: marked as done (libmxml1: Cannot load zynaddsubfx's XML files)

Your message dated Sun, 20 Jan 2008 05:47:02 +0000
with message-id <E1JGT1K-0004RM-S9@ries.debian.org>
and subject line Bug#442416: fixed in mxml 2.4-1
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: zynaddsubfx
Version: 2.2.1-4
Severity: grave

--- Please enter the report below this line. ---
the 439152 bug concerns too the banks loading: at every banks loading tentative, I get the message: mxml: Missing close tag </!DOCTYPE ZynAddSubFX-data> under parent <?xml version="1.0" encoding="UTF-8"?>!
There should be a bug in this package.
thanks for your time

--- System information. ---
Architecture: i386
Kernel:       Linux

Debian Release: lenny/sid
  500 unstable        www.debian-multimedia.org
  500 unstable        sidux.com
  500 unstable        ftp.debian.org

--- Package information. ---
Depends                 (Version) | Installed
fftw3                             | 3.1.2-2
libasound2            (>> 1.0.10) | 1.0.14a-2
libc6                (>= 2.3.5-1) | 2.6.1-4
libfltk1.1             (>= 1.1.7) | 1.1.7-4
libgcc1              (>= 1:4.0.2) | 1:4.2.1-5
libjack0.100.0-0     (>= 0.100.0) | 0.103.0-6
libmxml1                 (>= 2.1) | 2.3-1
libstdc++6           (>= 4.0.2-4) | 4.2.1-5
zlib1g               (>= 1:1.2.1) | 1:

--- End Message ---
--- Begin Message ---
Source: mxml
Source-Version: 2.4-1

We believe that the bug you reported is fixed in the latest version of
mxml, which is due to be installed in the Debian FTP archive:

  to pool/main/m/mxml/libmxml-dev_2.4-1_amd64.deb
  to pool/main/m/mxml/libmxml1_2.4-1_amd64.deb
  to pool/main/m/mxml/mxml_2.4-1.diff.gz
  to pool/main/m/mxml/mxml_2.4-1.dsc
  to pool/main/m/mxml/mxml_2.4.orig.tar.gz

A summary of the changes between this version and the previous one is

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 442416@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
Luis Uribe <acme@eviled.org> (supplier of updated mxml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)

Hash: SHA1

Format: 1.7
Date: Tue, 15 Jan 2008 21:13:50 -0500
Source: mxml
Binary: libmxml1 libmxml-dev
Architecture: source amd64
Version: 2.4-1
Distribution: unstable
Urgency: low
Maintainer: Luis Uribe <acme@eviled.org>
Changed-By: Luis Uribe <acme@eviled.org>
 libmxml-dev - small XML parsing library (development)
 libmxml1   - small XML parsing library (runtime)
Closes: 391132 442416 460318
 mxml (2.4-1) unstable; urgency=low
   * New upstream release. (Closes: #460318). Thanks to Sam Morris
   * Fix loading zynaddsubfx's XML files. (Closes: #442416).
   * New maintainer. (Closes: #391132)
   * debian/control:
     - Update the homepage
     - Include part of the libmxml1 description into the libmxml-dev
   * debian/watch
     - Add file
   * Conforms with latest Standards Version 3.7.3
 d35c2d8a46ae00fa07177eb4c0ae4e79 592 libs optional mxml_2.4-1.dsc
 8dfa3d25d9a0146bd24324f5111d9db0 241325 libs optional mxml_2.4.orig.tar.gz
 27ab21bacc16df4e8979c15b957d8a92 4703 libs optional mxml_2.4-1.diff.gz
 5226eb2360b62de570563342ae7a1cfb 56494 libdevel optional libmxml-dev_2.4-1_amd64.deb
 ff6d0ad8b269326633183564eabe7123 26670 libs optional libmxml1_2.4-1_amd64.deb

Version: GnuPG v1.4.6 (GNU/Linux)


--- End Message ---

Reply to: