Your message dated Thu, 09 Apr 2009 10:17:06 +0000
with message-id <e1lrrji-0005e6...@ries.debian.org>
and subject line Bug#516964: fixed in jaula 1.4.0-1
has caused the Debian Bug report #516964,
regarding jaula_1.3.0-4(mips/unstable): FTBFS - documentation fails to build
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 ow...@bugs.debian.org
immediately.)


-- 
516964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jaula
Version: 1.3.0-4
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of jaula_1.3.0-4 on mayr by sbuild/mips 99.999
> Build started at 20090224-0211

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), flex, doxygen, texlive, ghostscript, texinfo

[...]

>                                                   
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on refman.log.
> make[5]: *** [refman.pdf] Error 1
> make[5]: Leaving directory `/build/buildd/jaula-1.3.0/doc/latex'
> make[4]: *** [doc] Error 2
> make[4]: Leaving directory `/build/buildd/jaula-1.3.0/doc'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/buildd/jaula-1.3.0/doc'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/jaula-1.3.0'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/jaula-1.3.0'
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=mips&pkg=jaula&ver=1.3.0-4




--- End Message ---
--- Begin Message ---
Source: jaula
Source-Version: 1.4.0-1

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

jaula_1.4.0-1.diff.gz
  to pool/main/j/jaula/jaula_1.4.0-1.diff.gz
jaula_1.4.0-1.dsc
  to pool/main/j/jaula/jaula_1.4.0-1.dsc
jaula_1.4.0.orig.tar.gz
  to pool/main/j/jaula/jaula_1.4.0.orig.tar.gz
jparse_1.4.0-1_i386.deb
  to pool/main/j/jaula/jparse_1.4.0-1_i386.deb
libjaula-dev_1.4.0-1_i386.deb
  to pool/main/j/jaula/libjaula-dev_1.4.0-1_i386.deb
libjaula-doc_1.4.0-1_i386.deb
  to pool/main/j/jaula/libjaula-doc_1.4.0-1_i386.deb
libjaula1_1.4.0-1_i386.deb
  to pool/main/j/jaula/libjaula1_1.4.0-1_i386.deb



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

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

Debian distribution maintenance software
pp.
Loic Dachary (OuoU) <l...@debian.org> (supplier of updated jaula 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 ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 09 Apr 2009 11:55:07 +0200
Source: jaula
Binary: libjaula1 libjaula-dev libjaula-doc jparse
Architecture: source i386
Version: 1.4.0-1
Distribution: unstable
Urgency: low
Maintainer: Loic Dachary (OuoU) <l...@debian.org>
Changed-By: Loic Dachary (OuoU) <l...@debian.org>
Description: 
 jparse     - JSON parser utility
 libjaula-dev - JSON parser/writer library for C++ (development files)
 libjaula-doc - JSON parser/writer library for C++ (documentation)
 libjaula1  - JSON parser/writer library for C++
Closes: 516964
Changes: 
 jaula (1.4.0-1) unstable; urgency=low
 .
   * New upstream release
   * debian directory does not need to be removed from sources
   * add --enable-doc-gen to configure
   * make docs has been fixed upstream (Closes: #516964).
Checksums-Sha1: 
 c40eefa6d03487d454ac9d8d8f62771f1a3a7a29 1058 jaula_1.4.0-1.dsc
 f348464eaff41e2fbee869e7d1645f48cdb2a266 408075 jaula_1.4.0.orig.tar.gz
 26046c6e43a4322d527943b2ecf2c569092e8f31 4502 jaula_1.4.0-1.diff.gz
 40100abca94fe98a0d12bde01ef0b3ff7ecd1412 45742 libjaula1_1.4.0-1_i386.deb
 20e33d939e774611b7db56f2c0a9587fbebbee1d 65890 libjaula-dev_1.4.0-1_i386.deb
 a8acf6b0974c0789f0f4ff3c9b83599f42d12277 825274 libjaula-doc_1.4.0-1_i386.deb
 09c4084b237363ecd6da01034fa7210f5a0e4daf 9436 jparse_1.4.0-1_i386.deb
Checksums-Sha256: 
 f3eddcc0a176bd1df2824c25df559326be90c1d4890b5dc140d264ce4e119c77 1058 
jaula_1.4.0-1.dsc
 e22ab944d2821f3109e29e4b572a317185b6e3579cb46d74c9a70f10a7158364 408075 
jaula_1.4.0.orig.tar.gz
 20efe4501d7244d5a850e67e59de3cf73f507f002befab896c197900f22e01b1 4502 
jaula_1.4.0-1.diff.gz
 39161901d9d71743045f71d3e2191188ed5244d51752e8c20e2f5e52a57c757d 45742 
libjaula1_1.4.0-1_i386.deb
 cff200ea9b5b1744e39cdd37ed6c414fd162ba540a65599381ae0a9de784d7e6 65890 
libjaula-dev_1.4.0-1_i386.deb
 d3d639ff31c2bd5c5ed9eb1347b1b41238ccbd027ad3256828e8dc7392d94e38 825274 
libjaula-doc_1.4.0-1_i386.deb
 a9eceb31ef347eee4673d046cac2cfa7b75304d852a9bba425b05f018a7c2166 9436 
jparse_1.4.0-1_i386.deb
Files: 
 c9d31fec12a3fdbe965c22eb94c18a90 1058 libs extra jaula_1.4.0-1.dsc
 33cda1b94dac066d1a7303fd39b04282 408075 libs extra jaula_1.4.0.orig.tar.gz
 0f7b91b3130bfd938cb237dbc10cb997 4502 libs extra jaula_1.4.0-1.diff.gz
 a3eb390cb80e151e46452de0dfb4e3cd 45742 libs extra libjaula1_1.4.0-1_i386.deb
 60cc0263570984eb3074191b30708211 65890 libdevel extra 
libjaula-dev_1.4.0-1_i386.deb
 d61d94e2d8403e5b9569bb42b932a814 825274 doc extra libjaula-doc_1.4.0-1_i386.deb
 ca9b82d700ebf16d8e2102080e406e53 9436 utils extra jparse_1.4.0-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkndyOgACgkQ8dLMyEl6F21BMwCeLicMbHdluCvZrPDykL3r8CoE
8RwAn0e/7Pr2PObfNejeR3zdrE/Y8uzo
=z51F
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to