Bug#876576: marked as done (orbit2 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)
Your message dated Fri, 29 Sep 2017 21:39:11 +0000
with message-id <E1dy303-0002aG-ID@fasolo.debian.org>
and subject line Bug#876576: fixed in orbit2 1:2.14.19-4
has caused the Debian Bug report #876576,
regarding orbit2 FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available
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 owner@bugs.debian.org
immediately.)
--
876576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876576
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: orbit2
Version: 1:2.14.19-3
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/orbit2.html
...
Making all in api
make[4]: Entering directory '/build/1st/orbit2-2.14.19/docs/api'
gtk-doc: Scanning header files
gtk-doc: Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:625: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: orbit2
Source-Version: 1:2.14.19-4
We believe that the bug you reported is fixed in the latest version of
orbit2, 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 876576@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk <bunk@debian.org> (supplier of updated orbit2 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@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 29 Sep 2017 23:17:07 +0300
Source: orbit2
Binary: liborbit-2-0 liborbit2 orbit2 orbit2-nameserver liborbit2-dev
Architecture: source
Version: 1:2.14.19-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Adrian Bunk <bunk@debian.org>
Description:
liborbit-2-0 - high-performance CORBA implementation - common libraries
liborbit2 - high-performance CORBA implementation - extra libraries
liborbit2-dev - high-performance CORBA implementation - development
orbit2 - high-performance CORBA implementation - Object Request Broker
orbit2-nameserver - high-performance CORBA implementation - name server
Closes: 842099 876576
Changes:
orbit2 (1:2.14.19-4) unstable; urgency=medium
.
* QA upload.
* Run gtkdocize to fix FTBFS with gtk-doc-tools 1.26.
(Closes: #876576)
* Stop building with -fPIC. (Closes: #842099)
Checksums-Sha1:
cb5ea92d951e1d3edbd0362008df9e6954d394af 2068 orbit2_2.14.19-4.dsc
13f9d2356ef77707660947b420e041e8485ac6cf 15068 orbit2_2.14.19-4.debian.tar.xz
Checksums-Sha256:
ccd6e85e7d1682ee0626589be7b1e1b319c733f745e204b650483e5a97b4c15c 2068 orbit2_2.14.19-4.dsc
57cd7553c4fae6a8d28665e6cb3c4835eb7eea1ca2db9a5326830140ae8047ae 15068 orbit2_2.14.19-4.debian.tar.xz
Files:
b49bc839501fdefc9e3797e86a063bee 2068 net optional orbit2_2.14.19-4.dsc
87a8b93d83b2351e4fe7ba370fffd41a 15068 net optional orbit2_2.14.19-4.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlnOs8MACgkQiNJCh6LY
mLEM/A/9EaDKa0NASFZyH+8DiBTpFmPsZfn9m1GdAbgAnHR32B/8SHFvahWMkHTz
3oRRg3AclbLtn4OlfOAsPzzXb7hdis1vTatLoaSQR34VTi4ZpMqxKdf7KXHDDqVY
Gx0Tyuj6x06WMVIihiDi7zJjDI73PSOcj4byBuPkX160ri/iw3JHM2f1bYC36LoJ
CfW/Cudfk77IvpHFIIHVDbVR7IR+45+KD2voxcdOOX0w3V17sJcjhTgIHtG11KdW
Q7ZnAaO9+L/0N+vPsYd0LO4s9dVmBNMbIRQ79EGGHcJoRyuwh6mQOv8dm00xlJVu
GhorvWaSzmoXRP3iZKgjGh9sW0e5Mh8BcdtupaT044o3z2ktx8zBaIqb0vsloMUJ
Iyr3E34aW2djGB0uCaLg9dSvz2YFRPcXm2zseiYPf1MVgbBtNJehQJ52e+2YpX1n
om5zqxiN4XxFCFvQhjXuKe1AsilJGL7bqZ5tIs4ooZRas7fv3IyJviDA0i0WGTWS
djXYFUlmWjl+KLJj57R7gbAMJahmqY0Qil43m7ELSuuhp+LEpGSgpVnaHMjA6rKx
59gc/6YfXB3tTLl4PEsEBcRzBKv6U78P8XSpL9BATwJ1HumJx0JBpr3y/OQcI1a4
2PaVl0U3Y8hliRIh5XQLw0titM+E4Eia0si4SgbJNspR75k2A24=
=QTR4
-----END PGP SIGNATURE-----
--- End Message ---
Reply to: