Your message dated Tue, 27 Sep 2016 13:27:50 +0000
with message-id <e1bosqi-0001sj...@franck.debian.org>
and subject line Bug#838677: fixed in python-jellyfish 0.5.6-2
has caused the Debian Bug report #838677,
regarding python-jellyfish: FTBFS: dh: unable to load addon sphinxdoc
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.)


-- 
838677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jellyfish
Version: 0.5.6-1
Severity: serious
Justification: fails to build from source

Builds of python-jellyfish in minimal environments geared towards
building only its architecture-dependent binary packages have been failing:

  dh clean --with python2,python3,sphinxdoc --buildsystem=pybuild
  dh: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: [...]) at (eval 
13) line 2.
  BEGIN failed--compilation aborted at (eval 13) line 2.

  debian/rules:15: recipe for target 'clean' failed
  make: *** [clean] Error 2

Please either conditionalize the usage of --with sphinxdoc or move
python-sphinx from Build-Depends-Indep to Build-Depends.

Thanks!

--- End Message ---
--- Begin Message ---
Source: python-jellyfish
Source-Version: 0.5.6-2

We believe that the bug you reported is fixed in the latest version of
python-jellyfish, which is due to be installed in the Debian FTP archive.

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 838...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Diego M. Rodriguez <diego.pl...@gmail.com> (supplier of updated 
python-jellyfish 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...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 17:55:05 +0200
Source: python-jellyfish
Binary: python-jellyfish python3-jellyfish python-jellyfish-doc
Architecture: source
Version: 0.5.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Diego M. Rodriguez <diego.pl...@gmail.com>
Description:
 python-jellyfish - Library for approximate and phonetic matching of strings 
(Python
 python-jellyfish-doc - Library for approximate and phonetic matching of 
strings (documen
 python3-jellyfish - Library for approximate and phonetic matching of strings 
(Python
Closes: 838677
Changes:
 python-jellyfish (0.5.6-2) unstable; urgency=medium
 .
   * Move python-sphinx to Build-Depends. (Closes: #838677)
   * Add Vcs-Git and Vcs-Browser fields.
Checksums-Sha1:
 1d11c09e217212828641d1e1ef8f508553ce3d68 2382 python-jellyfish_0.5.6-2.dsc
 fec7acf61e337dbe69d010539490d52b8214d695 3280 
python-jellyfish_0.5.6-2.debian.tar.xz
Checksums-Sha256:
 7b893d701db91bf37a9b98a58bbb46549e189a9de63db8105cda4ad92b480549 2382 
python-jellyfish_0.5.6-2.dsc
 9a0f3e66de2e2926274228cd30fac0f269ad2e8d62fa18e72c6be283da9f7daf 3280 
python-jellyfish_0.5.6-2.debian.tar.xz
Files:
 ca841894e4f90cafc87278e1849b6588 2382 python optional 
python-jellyfish_0.5.6-2.dsc
 b98ff89ed0fc8fe2ece14ff44f800f6e 3280 python optional 
python-jellyfish_0.5.6-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJX6my4AAoJEPNPCXROn13Zs1EP/0ySWsvfippA/JmVNcWDlpID
I6+vQZxWlpStlEAbfyAhHKb/o8IF2sYFi5jaxWLgjdwMGE6UkO2o64vTKac4AFhQ
3iNaJnMkZTJYHOZaXD9tUCKW6ZPKpaHw0DH0YlDai1UpT5fDmlEUwo5iqdZPJZH+
KHDOtPUI3chgxGJO8yRPOk+gNGYNp1YCoL8NLItzoESrMzXNTVI15pNexZqh4OMZ
qAXSvNS1zwLHD22jQUJrJaqNZICRjzJEXx5WhvvSs29OrM/DIKvwaWHhwXRkBrVf
TCYvm6+cyff/wKOzVnmcFVOFFOb4fNdCghx0IBLdo5s1y+VjQ32Z/BnoAy64QY4+
rkYDYu10YZtWDnn8CcMEfpSD4F2yffE2co1LDbf25FzJETlueEcipMGjqdpLDWln
tdhe+yUzg0bbgwRmA3+SAqkdiYw2AxO5/a4YlIQu7V3YSojSFECwMoy6C2R1Zq/k
wUgBIDtsDfPdARvQt9ee4PX1rpIinGqKjCFoXG7pzX7iJgJttwkJy/qvEMCuy/1b
y5aiyuJArxvZV51SnxR1kPSOVsSUcWreBJmUzknD9uOW5sltNX0UuGsxbcMHINhG
DuNZCZizTlWniU0E2eGrOumSxKuVecgsUqXQRrNjdF8Ymo67g+WptvDIhdbXjZI3
kPQE6HuPjO1yXfIfaBLz
=mxTr
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to