Processed: python-pysam: FTBFS: Test failures

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 871083 = sid
Bug #871083 [src:python-pysam] python-pysam: FTBFS: Test failures
Removed tag(s) buster.
> tags 871314 = sid
Bug #871314 [htslib] htslib: new version break python-pysam
Removed tag(s) buster.
> tags 871315 = sid
Bug #871315 [samtools] samtools: new version breaks python-pysam
Removed tag(s) buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871083
871314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871314
871315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853354: marked as done (connectome-workbench: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 05:19:20 +
with message-id 
and subject line Bug#853354: fixed in connectome-workbench 
1.2.3+git41-gc4c6c90-2
has caused the Debian Bug report #853354,
regarding connectome-workbench: ftbfs with GCC-7
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.)


-- 
853354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:connectome-workbench
Version: 1.2.3+git3-g7b83782-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/connectome-workbench_1.2.3+git3-g7b83782-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
#endif
}

Determining if the Q_WS_MAC exist failed with the following output:
Change Dir: 
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_4152d/fast"
make[2]: Entering directory 
'/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_4152d.dir/build.make 
CMakeFiles/cmTC_4152d.dir/build
make[3]: Entering directory 
'/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_4152d.dir/CheckSymbolExists.cxx.o
/usr/bin/c++-I/usr/include/qt4  -g -O2 
-fdebug-prefix-map=/<>/connectome-workbench-1.2.3+git3-g7b83782=. 
-fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2 -o CMakeFiles/cmTC_4152d.dir/CheckSymbolExists.cxx.o -c 
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
 In function 'int main(int, char**)':
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
 error: 'Q_WS_MAC' was not declared in this scope
   return ((int*)(_WS_MAC))[argc];
   ^~~~
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:8:19:
 note: suggested alternative: 'Q_WS_X11'
   return ((int*)(_WS_MAC))[argc];
   ^~~~
   Q_WS_X11
CMakeFiles/cmTC_4152d.dir/build.make:65: recipe for target 
'CMakeFiles/cmTC_4152d.dir/CheckSymbolExists.cxx.o' failed
make[3]: *** [CMakeFiles/cmTC_4152d.dir/CheckSymbolExists.cxx.o] Error 1
make[3]: Leaving directory 
'/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Makefile:126: recipe for target 'cmTC_4152d/fast' failed
make[2]: *** [cmTC_4152d/fast] Error 2
make[2]: Leaving directory 
'/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

File 
/<>/connectome-workbench-1.2.3+git3-g7b83782/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.cxx:
/* */
#include 

int main(int argc, char** argv)
{
  (void)argv;
#ifndef Q_WS_MAC
  return ((int*)(_WS_MAC))[argc];
#else
  (void)argc;
  return 0;
#endif
}

dh_auto_configure: cmake ../src -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_SKIP_RPATH:BOOL=OFF returned exit code 1
cd /<>/connectome-workbench-1.2.3+git3-g7b83782
debian/rules:38: recipe for target 'override_dh_auto_configure' failed
make[1]: *** 

Bug#871291: marked as done (libsbml5: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 05:20:44 +
with message-id 
and subject line Bug#871291: fixed in libsbml 5.15.2+dfsg-1
has caused the Debian Bug report #871291,
regarding libsbml5: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsbml5
Version: 5.13.0+dfsg-1
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.15.2+dfsg-1

We believe that the bug you reported is fixed in the latest version of
libsbml, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libsbml 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: Tue, 08 Aug 2017 04:50:29 +0200
Source: libsbml
Binary: libsbml5-dev libsbml5 libsbml5-python libsbml5-java libsbml5-perl 
libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc libsbml5-cil-doc 
libsbml5-java-doc libsbml5-perl-doc libsbml5-python-doc
Architecture: source amd64 all
Version: 5.15.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libsbml5   - System Biology Markup Language library
 libsbml5-cil - System Biology Markup Language library - CLI bindings
 libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation
 libsbml5-dev - System Biology Markup Language library - development files
 libsbml5-doc - System Biology Markup Language library -- documentation
 libsbml5-examples - System Biology Markup Language library -- example files
 libsbml5-java - System Biology Markup Language library - Java bindings
 libsbml5-java-doc - System Biology 

Bug#868150: imapproxy: fails to start

[Richard Laager]

On 07/18/2017 01:28 PM, Richard Laager wrote:
> Agreed on stable-proposed-updates. I plan to prepare an upload in the next 
> few days.

I have prepared the changes and submitted the required bug for
stable-proposed-updates here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871451

I assume I need to hear some sort of ACK on that bug before I (ask my
sponsor to) upload.

-- 
Richard

Bug#870827: marked as done (jadetex Provides/dependencies on the wrong packages)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 04:55:57 +
with message-id 
and subject line Bug#870827: fixed in texlive-extra 2017.20170808-1
has caused the Debian Bug report #870827,
regarding jadetex Provides/dependencies on the wrong packages
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.)


-- 
870827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: docbook-utils
Version: 0.6.14-3.3
Severity: serious

In my bootstrapping pbuilder chroot, I'm getting numerous build
failures like this:

docbook2pdf shared-mime-info-spec.xml && \
docbook2html -o shared-mime-info-spec.html shared-mime-info-spec.xml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#print
Working on: /build/shared-mime-info-1.8/shared-mime-info-spec.xml
/usr/share/docbook-utils/backends/pdf: 15:
/usr/share/docbook-utils/backends/pdf: pdfjadetex: not found
debian/rules:14: recipe for target 'build/shared-mime-info' failed
make: *** [build/shared-mime-info] Error 9
dpkg-buildpackage: error: debian/rules build gave error exit status 2

It seems that in a chroot with all dependencies available, apt by
default happens to satisfy the dependencies of docbook-utils in a way
which includes texlive-formats-extra.  However, it's also possible to
satisfy the dependencies without installing texlive-formats-extra, in
which case the PDF backend will fail to run.

(I haven't tracked down exactly what the dependencies are that bring
in texlive-formats-extra by default but optionally.  But you should be
able to reproduce it for yourself: pbuilder login and then in the
chroot run "apt install docbook-utils texlive-formats-extra-" .)
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:42:51 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music texlive-games texlive-pstricks 
texlive-publishers texlive-humanities texlive-science texlive-fonts-extra-doc 
texlive-humanities-doc texlive-latex-extra-doc texlive-science-doc 
texlive-pstricks-doc texlive-publishers-doc
Architecture: source all
Version: 2017.20170808-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 texlive-science - TeX Live: Mathematics, natural sciences, computer science 
package
 texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 870827 871159
Changes:
 

Bug#871159: marked as done (pstoedit: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\([a-zA-Z]+){([^}]*)}{ <-- HERE ([^}]*)}/ at /usr/bin/latex2man line 1327.

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 04:55:57 +
with message-id 
and subject line Bug#871159: fixed in texlive-extra 2017.20170808-1
has caused the Debian Bug report #871159,
regarding pstoedit: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\([a-zA-Z]+){([^}]*)}{ <-- HERE ([^}]*)}/ at 
/usr/bin/latex2man line 1327.
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.)


-- 
871159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pstoedit
Version: 3.70-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> cd doc && latex2man -M -t pstoedit.trans pstoedit.tex pstoedit.1
> Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in 
> m/\\([a-zA-Z]+){([^}]*)}{ <-- HERE ([^}]*)}/ at /usr/bin/latex2man line 1327.
> debian/rules:21: recipe for target 'override_dh_auto_build' failed
> make[1]: *** [override_dh_auto_build] Error 255

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/pstoedit_3.70-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-extra 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:42:51 +0900
Source: texlive-extra
Binary: texlive-bibtex-extra texlive-extra-utils texlive-font-utils 
texlive-formats-extra texlive-plain-generic texlive-latex-extra 
texlive-fonts-extra texlive-music texlive-games texlive-pstricks 
texlive-publishers texlive-humanities texlive-science texlive-fonts-extra-doc 
texlive-humanities-doc texlive-latex-extra-doc texlive-science-doc 
texlive-pstricks-doc texlive-publishers-doc
Architecture: source all
Version: 2017.20170808-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 texlive-bibtex-extra - TeX Live: BibTeX additional styles
 texlive-extra-utils - TeX Live: TeX auxiliary programs
 texlive-font-utils - TeX Live: Graphics and font utilities
 texlive-fonts-extra - TeX Live: Additional fonts
 texlive-fonts-extra-doc - TeX Live: Documentation files for texlive-fonts-extra
 texlive-formats-extra - TeX Live: Additional formats
 texlive-games - TeX Live: Games typesetting
 texlive-humanities - TeX Live: Humanities packages
 texlive-humanities-doc - TeX Live: Documentation files for texlive-humanities
 texlive-latex-extra - TeX Live: LaTeX additional packages
 texlive-latex-extra-doc - TeX Live: Documentation files for texlive-latex-extra
 texlive-music - TeX Live: Music packages
 texlive-plain-generic - TeX Live: Plain (La)TeX packages
 texlive-pstricks - TeX Live: PSTricks
 texlive-pstricks-doc - TeX Live: Documentation files for texlive-pstricks
 texlive-publishers - TeX Live: Publisher styles, theses, etc.
 texlive-publishers-doc - TeX Live: Documentation files for texlive-publishers
 texlive-science - TeX Live: Mathematics, natural sciences, computer science 
package
 texlive-science-doc - TeX Live: Documentation files for texlive-science
Closes: 870827 871159
Changes:
 texlive-extra (2017.20170808-1) unstable; urgency=medium
 .
   [ Gregor 

Bug#871143: marked as done (auto-multiple-choice: FTBFS: ld: cannot find -lopencv_imgcodecs)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id 
and subject line Bug#870280: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #870280,
regarding auto-multiple-choice: FTBFS: ld: cannot find -lopencv_imgcodecs
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.)


-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: auto-multiple-choice
Version: 1.3.0-3
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/ld: cannot find -lopencv_imgcodecs
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/05/auto-multiple-choice_1.3.0-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-base, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-base 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:32:11 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended 
texlive-fonts-recommended texlive-pictures texlive-luatex texlive-metapost 
texlive-xetex texlive-lang-african texlive-lang-indic 
texlive-generic-recommended texlive-generic-extra texlive-plain-extra 
texlive-htmlxml texlive-omega luasseq texlive texlive-full 
texlive-fonts-recommended-doc texlive-latex-base-doc 
texlive-latex-recommended-doc texlive-metapost-doc texlive-pictures-doc
Architecture: source all
Version: 2017.20170808-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 luasseq- TeX Live: transitional dummy package
 texlive- TeX Live: A decent selection of the TeX Live packages
 texlive-base - TeX Live: Essential programs and files
 texlive-fonts-recommended - TeX Live: Recommended fonts
 texlive-fonts-recommended-doc - TeX Live: Documentation files for 
texlive-fonts-recommended
 texlive-full - TeX Live: metapackage pulling in all components of TeX Live
 texlive-generic-extra - TeX Live: transitional dummy package
 texlive-generic-recommended - TeX Live: transitional dummy package
 texlive-htmlxml - TeX Live: transitional dummy package
 texlive-lang-african - TeX Live: transitional dummy package
 texlive-lang-indic - TeX Live: transitional dummy package
 texlive-latex-base - TeX Live: LaTeX fundamental packages
 texlive-latex-base-doc - TeX Live: Documentation files for texlive-latex-base
 texlive-latex-recommended - TeX Live: LaTeX recommended packages
 texlive-latex-recommended-doc - TeX Live: Documentation files for 
texlive-latex-recommended
 texlive-luatex - TeX Live: LuaTeX packages
 texlive-metapost - TeX Live: MetaPost and Metafont packages
 texlive-metapost-doc - TeX Live: Documentation files for texlive-metapost
 texlive-omega - TeX Live: transitional dummy package
 texlive-pictures - TeX Live: Graphics, pictures, diagrams
 texlive-pictures-doc - TeX Live: Documentation files for texlive-pictures
 texlive-plain-extra - TeX Live: transitional dummy package
 texlive-xetex - TeX Live: XeTeX and packages
Closes: 826465 870280
Changes:
 texlive-base (2017.20170808-1) unstable; urgency=medium
 .
   [ 

Bug#871092: marked as done (maint-guide: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id 
and subject line Bug#870280: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #870280,
regarding maint-guide: FTBFS: dh_install: missing files, aborting
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.)


-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maint-guide
Version: 1.2.39
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  fakeroot debian/rules binary
> dh  binary
>dh_testroot
>dh_prep
>dh_auto_install
>dh_install
> dh_install: Cannot find (any matches for) "tmp/maint-guide.en.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide missing files: tmp/maint-guide.en.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.ca.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-ca missing files: tmp/maint-guide.ca.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.de.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-de missing files: tmp/maint-guide.de.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.es.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-es missing files: tmp/maint-guide.es.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.fr.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-fr missing files: tmp/maint-guide.fr.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.it.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-it missing files: tmp/maint-guide.it.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.ja.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-ja missing files: tmp/maint-guide.ja.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.ru.pdf" (tried in 
> ., debian/tmp)
> 
> dh_install: maint-guide-ru missing files: tmp/maint-guide.ru.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.zh-cn.pdf" (tried 
> in ., debian/tmp)
> 
> dh_install: maint-guide-zh-cn missing files: tmp/maint-guide.zh-cn.pdf
> dh_install: Cannot find (any matches for) "tmp/maint-guide.zh-tw.pdf" (tried 
> in ., debian/tmp)
> 
> dh_install: maint-guide-zh-tw missing files: tmp/maint-guide.zh-tw.pdf
> dh_install: missing files, aborting
> debian/rules:35: recipe for target 'binary' failed
> make: *** [binary] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/maint-guide_1.2.39_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-base, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-base 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:32:11 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended 
texlive-fonts-recommended texlive-pictures texlive-luatex texlive-metapost 
texlive-xetex texlive-lang-african texlive-lang-indic 
texlive-generic-recommended texlive-generic-extra texlive-plain-extra 
texlive-htmlxml texlive-omega luasseq texlive texlive-full 
texlive-fonts-recommended-doc texlive-latex-base-doc 
texlive-latex-recommended-doc texlive-metapost-doc texlive-pictures-doc
Architecture: source all
Version: 

Bug#871067: marked as done (developers-reference: FTBFS: Error: xelatex compilation failed)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id 
and subject line Bug#870280: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #870280,
regarding developers-reference: FTBFS: Error: xelatex compilation failed
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.)


-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: developers-reference
Version: 3.4.18
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> cd ja && ln -sf ../common.ent .
> make[3]: Leaving directory '/<>'
> echo '' >  ja/version.ent
> echo '' >> ja/version.ent
> cd ja && xsltproc --nonet --novalid --xinclude /<>/xslt/html.xsl 
> index.dbk
> Writing ch01.html for chapter(scope)
> Writing ch02.html for chapter(new-maintainer)
> Writing ch03.html for chapter(developer-duties)
> Writing ch04.html for chapter(resources)
> Writing ch05.html for chapter(pkgs)
> Writing ch06.html for chapter(best-pkging-practices)
> Writing ch07.html for chapter(beyond-pkging)
> Writing ch08.html for chapter(l10n)
> Writing apa.html for appendix(tools)
> Writing index.html for book
> cp -r /<>/images /<>/developers-reference.css ja
> xsltproc --nonet --novalid --xinclude /<>/xslt/txt.xsl 
> ja/index.dbk \
> | LC_ALL=C.UTF-8 w3m -o display_charset=UTF-8 -cols 70 -dump -no-graph -T 
> text/html > ja/developers-reference.txt
> Can't create config directory (/sbuild-nonexistent/.w3m)!dblatex 
> --style=db2latex ja/index.dbk \
> --backend=xetex \
> --xsl-user=xslt/user_param.xsl \
> --xsl-user=xslt/xetex_param.xsl \
> --param=lingua=ja \
> && mv ja/index.dbk.pdf ja/developers-reference.pdf
> Build the book set list...
> Build the listings...
> XSLT stylesheets DocBook - LaTeX 2e (0.3.10)
> ===
> Build index.dbk.pdf
> xelatex failed
> index.dbk.tex:69: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:69: Missing number, treated as zero.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:69: Missing number, treated as zero.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:69: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:69: Missing number, treated as zero.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:69: Missing number, treated as zero.
> index.dbk.tex:69: leading text: \lstsetup
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: v
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: v
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: v
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: vo
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vo
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vo
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: vor
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vor
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vor
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: vore
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vore
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vore
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: vore$
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vore$
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vore$
> index.dbk.tex:734: Undefined control sequence \l__xeCJK_listings_letter_bool.
> index.dbk.tex:734: leading text: vore$ 
> index.dbk.tex:734: Missing number, treated as zero.
> index.dbk.tex:734: leading text: vore$ 
> index.dbk.tex:734: Missing number, treated as 

Bug#826465: marked as done (texlive-latex-recommended: Unescaped left brace in regex is deprecated)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id 
and subject line Bug#826465: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #826465,
regarding texlive-latex-recommended: Unescaped left brace in regex is deprecated
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.)


-- 
826465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-recommended
Version: 2016.20160523-1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition

Building the backup-manager package triggers deprecation warnings with
Perl 5.24 (currently in experimental), and probably with Perl 5.22
(current sid) too.

  Unescaped left brace in regex is deprecated, passed through in regex; marked 
by <-- HERE in m/\\UseRGB{ <-- HERE (\d+)}\\\s*\d+\s*R/ at /usr/bin/thumbpdf 
line 1456.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-base, 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 826...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-base 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:32:11 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended 
texlive-fonts-recommended texlive-pictures texlive-luatex texlive-metapost 
texlive-xetex texlive-lang-african texlive-lang-indic 
texlive-generic-recommended texlive-generic-extra texlive-plain-extra 
texlive-htmlxml texlive-omega luasseq texlive texlive-full 
texlive-fonts-recommended-doc texlive-latex-base-doc 
texlive-latex-recommended-doc texlive-metapost-doc texlive-pictures-doc
Architecture: source all
Version: 2017.20170808-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 
Description:
 luasseq- TeX Live: transitional dummy package
 texlive- TeX Live: A decent selection of the TeX Live packages
 texlive-base - TeX Live: Essential programs and files
 texlive-fonts-recommended - TeX Live: Recommended fonts
 texlive-fonts-recommended-doc - TeX Live: Documentation files for 
texlive-fonts-recommended
 texlive-full - TeX Live: metapackage pulling in all components of TeX Live
 texlive-generic-extra - TeX Live: transitional dummy package
 texlive-generic-recommended - TeX Live: transitional dummy package
 texlive-htmlxml - TeX Live: transitional dummy package
 texlive-lang-african - TeX Live: transitional dummy package
 texlive-lang-indic - TeX Live: transitional dummy package
 texlive-latex-base - TeX Live: LaTeX fundamental packages
 texlive-latex-base-doc - TeX Live: Documentation files for texlive-latex-base
 texlive-latex-recommended - TeX Live: LaTeX recommended packages
 texlive-latex-recommended-doc - TeX Live: Documentation files for 
texlive-latex-recommended
 texlive-luatex - TeX Live: LuaTeX packages
 texlive-metapost - TeX Live: MetaPost and Metafont packages
 texlive-metapost-doc - TeX Live: Documentation files for texlive-metapost
 texlive-omega - TeX Live: transitional dummy package
 texlive-pictures - TeX Live: Graphics, pictures, diagrams
 texlive-pictures-doc - TeX Live: Documentation files for texlive-pictures
 texlive-plain-extra - TeX Live: transitional dummy package
 texlive-xetex - TeX Live: XeTeX and packages
Closes: 826465 870280
Changes:
 texlive-base (2017.20170808-1) unstable; urgency=medium
 .
   [ Gregor Herrmann ]
   * Fix "Unescaped left brace in regex is deprecated":
 add patch thumbpdf-unescaped-left-brace to fix unescaped literal curly.
 (Closes: #826465)
 .
   [ Norbert Preining ]
   * new upstream checkout
 - new xecjk fixes undefined boolean (Closes: #870280)
Checksums-Sha1:
 c2c24322e6f2670a2fb26775d4b94dc36c72503f 3095 texlive-base_2017.20170808-1.dsc
 

Bug#871327: marked as done (kicad: FTBFS: a2x: ERROR: "dblatex" -t pdf -p "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0 -P d

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id <e1devyc-000fqf...@fasolo.debian.org>
and subject line Bug#870280: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #870280,
regarding kicad: FTBFS: a2x: ERROR: "dblatex" -t pdf -p 
"/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s 
"/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0 -P 
doc.publisher.show=0 -s 
/<>/kicad-4.0.6+dfsg1/doc/CMakeSupport/pdf-cover-dblatex.sty -b xetex 
-p 
/<>/kicad-4.0.6+dfsg1/doc/src/gerbview/../../xsl/dblatex-pdf-ja.xsl 
-o 
/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.pdf  
"/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.xml" 
returned non-zero exit status 1
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.)


-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kicad
Version: 4.0.6+dfsg1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/kicad-4.0.6+dfsg1/debian/build/doc'
> cd /<>/kicad-4.0.6+dfsg1/debian/build/doc/src/idf_exporter && 
> /usr/bin/a2x --xsltproc-opts=--nonet --no-xmllint -f pdf -a lang=it 
> --dblatex-opts -P\ latex.output.revhistory=0\ -P\ doc.publisher.show=0\ -s\ 
> /<>/kicad-4.0.6+dfsg1/doc/CMakeSupport/pdf-cover-dblatex.sty\ -o\ 
> /<>/kicad-4.0.6+dfsg1/debian/build/doc/src/idf_exporter/it/idf_exporter.pdf
>  
> /<>/kicad-4.0.6+dfsg1/debian/build/doc/src/idf_exporter/it/idf_exporter.adoc
> a2x: ERROR: "dblatex" -t pdf -p "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" 
> -s "/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0 
> -P doc.publisher.show=0 -s 
> /<>/kicad-4.0.6+dfsg1/doc/CMakeSupport/pdf-cover-dblatex.sty -b 
> xetex -p 
> /<>/kicad-4.0.6+dfsg1/doc/src/gerbview/../../xsl/dblatex-pdf-ja.xsl 
> -o 
> /<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.pdf 
>  
> "/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.xml"
>  returned non-zero exit status 1
> src/gerbview/CMakeFiles/gerbview_pdf_ja.dir/build.make:60: recipe for target 
> 'src/gerbview/CMakeFiles/gerbview_pdf_ja' failed
> make[4]: *** [src/gerbview/CMakeFiles/gerbview_pdf_ja] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/kicad_4.0.6+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2017.20170808-1

We believe that the bug you reported is fixed in the latest version of
texlive-base, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Norbert Preining <prein...@debian.org> (supplier of updated texlive-base 
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: SHA512

Format: 1.8
Date: Tue, 08 Aug 2017 10:32:11 +0900
Source: texlive-base
Binary: texlive-base texlive-latex-base texlive-latex-recommended 
texlive-fonts-recommended texlive-pictures texlive-luatex texlive-metapost 
texlive-xetex texlive-lang-african texlive-lang-indic 
texlive-generic-recommended texlive-generic-extra texlive-plain-extra 
texlive-htmlxml texlive-omega luasseq texlive texlive-full 
texlive-fonts-recommended-doc texlive-latex-base-doc 
texlive-latex-recommended-doc texlive-metapost-doc texlive-pictures-doc
Ar

Bug#870280: marked as done (xelatex: Undefined control sequence \l__xeCJK_listings_letter_bool)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id 
and subject line Bug#870280: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #870280,
regarding xelatex: Undefined control sequence \l__xeCJK_listings_letter_bool
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.)


-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-latex-recommended
Version: 2017.20170724-1
Severity: serious
Control: affects -1 src: auto-multiple-choice src:debian-reference 
src:installation-guide src:maint-guide

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/auto-multiple-choice.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debian-reference.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/installation-guide.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maint-guide.html

These packages FTBFS with an error that can be reproduced with:

$ cat test.tex  
\documentclass{article}
\usepackage{ifxetex}
\usepackage{docbook}
\setuplocale{ja}
\usepackage{xeCJK}
\setCJKmainfont{IPAexMincho}
\setCJKsansfont{IPAexGothic}
\setCJKmonofont{IPAexGothic}

\begin{document}
\begin{CJK}{UTF8}{gkai}
\lstsetup
\end{CJK}
\end{document}
$ xelatex test.tex  
This is XeTeX, Version 3.14159265-2.6-0.8 (TeX Live 2017/Debian) (preloaded 
format=xelatex)
 restricted \write18 enabled.
entering extended mode
(./test.tex
LaTeX2e <2017-04-15>
Babel <3.12> and hyphenation patterns for 9 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
(/usr/share/texmf/tex/latex/dblatex/style/docbook.sty
(/usr/share/texlive/texmf-dist/tex/latex/titlesec/titlesec.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ifpdf.sty)
(/usr/share/texlive/texmf-dist/tex/latex/pdfpages/pdfpages.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/tools/calc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/eso-pic/eso-pic.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/atbegshi.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/ltxcmds.sty))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/xetex.def)))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/pdfpages/ppxetex.def))
(/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty)
(/usr/share/texlive/texmf-dist/tex/latex/subfigure/subfigure.sty

* Local config file subfigure.cfg used *

(/usr/share/texlive/texmf-dist/tex/latex/subfigure/subfigure.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/tools/tabularx.sty
(/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
(/usr/share/texlive/texmf-dist/tex/latex/footmisc/footmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/appendix/appendix.sty)
(/usr/share/texmf/tex/latex/dblatex/style/dbk_fonts.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty)))
(/usr/share/texmf/tex/latex/dblatex/style/dbk_hyper.sty
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
(/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
(/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
(/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
(/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)

Bug#871345: marked as done (kimwitu-doc: FTBFS: Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/\\UseRGB{ <-- HERE (\d+)}\\\s*\d+\s*R/ at /usr/bin/thumbpdf line 1456.)

[Debian Bug Tracking System]

Your message dated Tue, 08 Aug 2017 03:51:24 +
with message-id <e1devyc-000fqz...@fasolo.debian.org>
and subject line Bug#826465: fixed in texlive-base 2017.20170808-1
has caused the Debian Bug report #826465,
regarding kimwitu-doc: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\UseRGB{ <-- HERE (\d+)}\\\s*\d+\s*R/ at 
/usr/bin/thumbpdf line 1456.
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.)


-- 
826465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kimwitu-doc
Version: 10a+1-2.2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>/kimwitu-doc-10a+1'
> #/usr/bin/make tp.man.ps
> #-rm -f tp.man.aux
> #perl5 /Text/LaTeX/bin/thumbpdf tp.man.ps
> pdflatex '\scrollmode \input '"tp.man"
> This is pdfTeX, Version 3.14159265-2.6-1.40.18 (TeX Live 2017/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> LaTeX2e <2017-04-15>
> Babel <3.12> and hyphenation patterns for 3 language(s) loaded.
> 
> (./tp.man.tex (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
> (/usr/share/texlive/texmf-dist/tex/latex/ntgclass/a4.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/makeidx.sty) (./lgrind.sty)
> Writing index file tp.man.idx
> (/usr/share/texlive/texmf-dist/tex/generic/thumbpdf/thumbpdf.sty
> 
> Package thumbpdf Warning: Compressed PDF objects of PDF 1.5 are not supported.
> 
> 
> Package thumbpdf Warning: Thumbnail data file `tp.man.tpt' not found.
> 
> ) (/usr/share/texlive/texmf-dist/tex/latex/tools/varioref.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/tools/xr.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-hyperref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/hobsub-generic.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ifxetex/ifxetex.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/auxhook.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/kvoptions.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/pd1enc.def)
> (/usr/share/texlive/texmf-dist/tex/latex/latexconfig/hyperref.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/backref.sty
> (/usr/share/texlive/texmf-dist/tex/latex/oberdiek/rerunfilecheck.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/url/url.sty))
> 
> Package hyperref Message: Driver (autodetected): hpdftex.
> 
> (/usr/share/texlive/texmf-dist/tex/latex/hyperref/hpdftex.def)
> 
> Package hyperref Warning: Option `hyperindex' has already been used,
> (hyperref)setting the option has no effect on input line 50.
> 
> No file tp.man.aux.
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/color.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def
> (/usr/share/texlive/texmf-dist/tex/context/base/mkii/supp-pdf.mkii
> [Loading MPS to PDF converter (version 2006.09.02).]
> ))) (/usr/share/texlive/texmf-dist/tex/latex/hyperref/nameref.sty
> (/usr/share/texlive/texmf-dist/tex/generic/oberdiek/gettitlestring.sty))
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] (./license.tex
> (/usr/share/texlive/texmf-dist/tex/latex/base/omscmr.fd))
> Underfull \hbox (badness 1) in paragraph at lines 72--81
> 
> [2]pdfTeX warning (ext4): destination with the same identifier (name{page.1}) 
> h
> as been already used, duplicate ignored
>  
>\relax 
> l.116 \newpage
>[1]
> 
> LaTeX Warning: Reference `sec:input' on page 1 undefined on input line 140.
> 
> 
> LaTeX Warning: Reference `sec:output' on page 1 undefined on input line 149.
> 
> 
> LaTeX Warning: Reference `sec:running' on page 1 undefined on input line 151.
> 
> 
> LaTeX Warning: Citation `csg:sigplan' on page 1 u

Bug#854733: Zoneminder issues fixed? (was: Re: Bug#854733 tagged as pending)

[Chris Lamb]

Hi Salvatore,

> found 854272 1.30.4+dfsg-1
> found 854733 1.30.4+dfsg-1
> thanks
> 
> Hi Salvatore,
>  
> > The recent upload to unstable claims to fix several CVEs. While for
> > #854733 this is the case for CVE-2017-5595, I fail to find fixing
> > commits for the other two CVEs from that bug. Where are they fixed?
> > Can you help identifying the commits?
> 
> Oh crumbs, I was either misinformed on (or more likely I misinterpreted!)
> an off-list conversation about these CVEs.
> 
> Am immediately re-opening them all for now whilst I investigate.

Hm, so I think these were all fixed in:

   
https://github.com/ZoneMinder/ZoneMinder/commit/d38bae72aeece85a20e3774c4953080e2e09e63c

What do you think?


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#871445: linux-image-4.9.0-3-amd64: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]

[Damien Myracle]

Package: src:linux
Version: 4.9.30-2+deb9u3
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?

I installed 'oracle java8' using ppa from Ubuntu, Team8, during the 
installation, ssh session began to 'freeze' and syslog recorded messages 
regarding CPU locking up. 
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Just installed Orcale Java8 on a virgin isntance of Debian9 server.

   * What was the outcome of this action?
OS began to 'freeze' with kernel messages about 'locked up CPU'

   * What outcome did you expect instead?
A normal operation of the OS. 

*** End of the template - remove these template lines ***


-- Package-specific info:
** Version:
Linux version 4.9.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06)

** Command line:
BOOT_IMAGE=/vmlinuz-4.9.0-3-amd64 root=/dev/mapper/docs--vg-root ro quiet

** Tainted: L (16384)
 * Kernel has detected soft lockup before.

** Kernel log:
[  139.486220] swapper/0   R  running task0 0  0 0x0008
[  139.486224]  93313580 926a3bcb  
93313580
[  139.486226]  9277a4b6 9ccf3fc18fc0 9324a6c0 

[  139.486229]  93313580  926dee04 
00983df7
[  139.486231] Call Trace:
[  139.486233]   
[  139.486238]  [] ? sched_show_task+0xcb/0x130
[  139.486242]  [] ? rcu_dump_cpu_stacks+0x92/0xb2
[  139.486244]  [] ? rcu_check_callbacks+0x754/0x8a0
[  139.486247]  [] ? update_wall_time+0x473/0x790
[  139.486250]  [] ? tick_sched_handle.isra.12+0x50/0x50
[  139.486252]  [] ? update_process_times+0x28/0x50
[  139.486254]  [] ? tick_sched_handle.isra.12+0x20/0x50
[  139.486255]  [] ? tick_sched_timer+0x38/0x70
[  139.486257]  [] ? __hrtimer_run_queues+0xdc/0x240
[  139.486258]  [] ? hrtimer_interrupt+0x9c/0x1a0
[  139.486261]  [] ? smp_apic_timer_interrupt+0x39/0x50
[  139.486263]  [] ? apic_timer_interrupt+0x82/0x90
[  139.486266]  [] ? _raw_spin_unlock_irqrestore+0x11/0x20
[  139.486283]  [] ? pvscsi_queue+0x42d/0x870 [vmw_pvscsi]
[  139.486294]  [] ? scsi_test_unit_ready+0x150/0x150 
[scsi_mod]
[  139.486302]  [] ? scsi_dispatch_cmd+0xd6/0x200 [scsi_mod]
[  139.486309]  [] ? scsi_request_fn+0x460/0x5e0 [scsi_mod]
[  139.486312]  [] ? __blk_run_queue+0x2f/0x40
[  139.486313]  [] ? blk_run_queue+0x21/0x40
[  139.486320]  [] ? scsi_run_queue+0x243/0x2c0 [scsi_mod]
[  139.486327]  [] ? scsi_end_request+0x122/0x1a0 [scsi_mod]
[  139.486333]  [] ? scsi_io_completion+0x1a6/0x670 [scsi_mod]
[  139.486335]  [] ? blk_done_softirq+0x88/0xb0
[  139.486337]  [] ? __do_softirq+0x105/0x290
[  139.486339]  [] ? irq_exit+0xae/0xb0
[  139.486341]  [] ? do_IRQ+0x4f/0xd0
[  139.486343]  [] ? common_interrupt+0x82/0x82
[  139.486344]   
[  139.486347]  [] ? native_safe_halt+0x2/0x10
[  139.486348]  [] ? default_idle+0x1a/0xd0
[  139.486351]  [] ? cpu_startup_entry+0x1ca/0x240
[  139.486353]  [] ? start_kernel+0x443/0x463
[  139.486355]  [] ? early_idt_handler_array+0x120/0x120
[  139.486357]  [] ? x86_64_start_kernel+0x14c/0x170
[  187.362590] TCP: ens192: Driver has suspect GRO implementation, TCP 
performance may be compromised.
[  708.602102] INFO: rcu_sched detected stalls on CPUs/tasks:
[  708.707854]  0-...: (1 GPs behind) idle=6f3/1/0 softirq=5911/5911 fqs=263 
[  708.707877]  (detected by 1, t=5282 jiffies, g=7910, c=7909, q=167)
[  708.707898] Task dump for CPU 0:
[  708.707899] swapper/0   R  running task0 0  0 0x0008
[  708.707903]  9320e500  0001 

[  708.707905]  0100   

[  708.707906]    ff4b 
92c05b02
[  708.707908] Call Trace:
[  708.707914]  [] ? native_safe_halt+0x2/0x10
[  708.707915]  [] ? default_idle+0x1a/0xd0
[  708.707917]  [] ? cpu_startup_entry+0x1ca/0x240
[  708.707920]  [] ? start_kernel+0x443/0x463
[  708.707922]  [] ? early_idt_handler_array+0x120/0x120
[  708.707923]  [] ? x86_64_start_kernel+0x14c/0x170
[  712.156417] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[swapper/0:0]
[  712.156451] Modules linked in: vmw_vsock_vmci_transport vsock coretemp 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ppdev vmw_balloon 
intel_rapl_perf joydev serio_raw pcspkr evdev shpchp sg vmwgfx vmw_vmci ttm 
drm_kms_helper drm parport_pc nfit libnvdimm parport battery ac acpi_cpufreq 
button ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic fscrypto ecb 
mbcache hid_generic usbhid hid dm_mod sr_mod cdrom sd_mod ata_generic 
crc32c_intel aesni_intel uhci_hcd aes_x86_64 glue_helper lrw gf128mul ehci_pci 
ablk_helper cryptd ata_piix psmouse ehci_hcd 

Bug#870688: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

[Ximin Luo]

-#869778

Ximin Luo:
> [..]
> 
> Hi, I see that libgsl23 was uploaded but who is taking care of the library 
> transition? It seems that this process was not followed:
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions
> 
> The transition tracker detected the library change:
> https://release.debian.org/transitions/html/auto-gsl.html
> 
> However there is no corresponding Transition Tracking bug report:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=release.debian.org
> 
> Currently this prevents me from doing test builds of sagemath, because some 
> of its build dependencies are not installable [..]
> 

As a temporary workaround:

$ aptitude search '~Dlibgsl2$ ~R^sagemath$ ~rnative' --disable-columns
p  python-cvxopt - Python package for convex optimization   
   
p  xcas - Computer Algebra System - console and graphical calculator

Since this list is quite small, I've done my own binNMUs of these packages 
(using sbuild --binNMU etc) and uploaded them to deb-sci-sage. This makes 
`debian/rules release-deb-sci-sage` work again, I'll run it properly in the 
morning and report the results.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#870827: docbook-utils: PDF backend requires texlive-formats-extra

[Norbert Preining]

Hi Adrian,

> jadetex is a transitional package depending on texlive-htmlxml.

That is fine.

> texlive-htmlxml is a transitional package that does not depend
> on texlive-formats-extra.

Huu?
$ apt-cache show texlive-htmlxml
...
Depends: texlive-formats-extra (>= 2017.20170628), ...


> texlive-plain-generic has Provides: jadetex

That is the bug, both xmltex and jadetex happened to be
treated in the same way as tex4ht, but are in different
packages.

> - texlive-htmlxml should depend on texlive-formats-extra, and

It does.

> - the "Provides: jadetex" should move from texlive-htmlxml
>   to texlive-formats-extra

Done in git, uploading soon

> And src:jadetex should be removed, no (build) dependency is versioned
> so the existing Provides already covers that (after the bug above has 
> been fixed).

Ok.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Processed: Re: Bug#870280: xelatex: Undefined control sequence \l__xeCJK_listings_letter_bool

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 870280 texlive-xetex
Bug #870280 [texlive-latex-recommended] xelatex: Undefined control sequence 
\l__xeCJK_listings_letter_bool
Bug #871067 [texlive-latex-recommended] developers-reference: FTBFS: Error: 
xelatex compilation failed
Bug #871092 [texlive-latex-recommended] maint-guide: FTBFS: dh_install: missing 
files, aborting
Bug #871143 [texlive-latex-recommended] auto-multiple-choice: FTBFS: ld: cannot 
find -lopencv_imgcodecs
Bug #871327 [texlive-latex-recommended] kicad: FTBFS: a2x: ERROR: "dblatex" -t 
pdf -p "/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s 
"/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0 -P 
doc.publisher.show=0 -s 
/<>/kicad-4.0.6+dfsg1/doc/CMakeSupport/pdf-cover-dblatex.sty -b xetex 
-p 
/<>/kicad-4.0.6+dfsg1/doc/src/gerbview/../../xsl/dblatex-pdf-ja.xsl 
-o 
/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.pdf  
"/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.xml" 
returned non-zero exit status 1
Bug reassigned from package 'texlive-latex-recommended' to 'texlive-xetex'.
Bug reassigned from package 'texlive-latex-recommended' to 'texlive-xetex'.
Bug reassigned from package 'texlive-latex-recommended' to 'texlive-xetex'.
Bug reassigned from package 'texlive-latex-recommended' to 'texlive-xetex'.
Bug reassigned from package 'texlive-latex-recommended' to 'texlive-xetex'.
No longer marked as found in versions texlive-base/2017.20170724-1.
No longer marked as found in versions texlive-base/2017.20170724-1.
No longer marked as found in versions texlive-base/2017.20170724-1.
No longer marked as found in versions texlive-base/2017.20170724-1.
No longer marked as found in versions texlive-base/2017.20170724-1.
Ignoring request to alter fixed versions of bug #870280 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871067 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871092 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871143 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871327 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
870280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870280
871067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871067
871092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871092
871143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871143
871327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

[Debian Bug Tracking System]

Processing control commands:

> block 870688 by 869778
Bug #870688 [sagemath] sagemath: new upstream release 8.0
870688 was not blocked by any bugs.
870688 was not blocking any bugs.
Added blocking bug(s) of 870688: 869810, 869778, 869779, and 869781
> affects 869778 + sagemath
Bug #869778 [libgsl2] libgsl2: soname change breaks dependencies
Bug #869779 [libgsl2] bogofilter dependencies on libgsl2
Bug #869781 [libgsl2] libgsl2: bumped library version without soname change, 
breaking reverse dependencies
Bug #869810 [libgsl2] krita: Crash on startup, missing libgsl.so.19
Added indication that 869778 affects sagemath
Added indication that 869779 affects sagemath
Added indication that 869781 affects sagemath
Added indication that 869810 affects sagemath

-- 
869778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869778
869779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869779
869781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869781
869810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869810
870688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

[Debian Bug Tracking System]

Processing control commands:

> block 870688 by 869778
Bug #870688 [sagemath] sagemath: new upstream release 8.0
870688 was blocked by: 869810 869779 869781 869778
870688 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #870688 to the same blocks 
previously set
> affects 869778 + sagemath
Bug #869778 [libgsl2] libgsl2: soname change breaks dependencies
Bug #869779 [libgsl2] bogofilter dependencies on libgsl2
Bug #869781 [libgsl2] libgsl2: bumped library version without soname change, 
breaking reverse dependencies
Bug #869810 [libgsl2] krita: Crash on startup, missing libgsl.so.19
Ignoring request to set affects of bug 869778 to the same value previously set
Ignoring request to set affects of bug 869779 to the same value previously set
Ignoring request to set affects of bug 869781 to the same value previously set
Ignoring request to set affects of bug 869810 to the same value previously set

-- 
869778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869778
869779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869779
869781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869781
869810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869810
870688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869778: [Debian-science-sagemath] Sage 8.0 status (was Re: Sage 7.6 upload for RC bugfix and GAP 4.8.7 in unstable)

[Ximin Luo]

Control: block 870688 by 869778
Control: affects 869778 + sagemath

Ximin Luo:
> Tobias Hansen:
>> [..]
>>
>> The accidental upload of cysignals 1.6.5 to unstable is now a RC bug
>> (#870688). Not sure if we should fix it by downgrading cysignals,
>> patching sage 7.6 or just let the bug sit until we upload sage 8.0. At
>> least the "Breaks: sagemath (<< 8.0~)" does indeed prevent cysignals
>> from migrating to testing, which is good.
>>
>> [..]
> 
> Hi, I'm at DebConf over the next week and will very likely be able to find 
> some time to deal with this.
> 

Hi, I see that libgsl23 was uploaded but who is taking care of the library 
transition? It seems that this process was not followed:
https://wiki.debian.org/Teams/ReleaseTeam/Transitions

The transition tracker detected the library change:
https://release.debian.org/transitions/html/auto-gsl.html

However there is no corresponding Transition Tracking bug report:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=release.debian.org

Currently this prevents me from doing test builds of sagemath, because some of 
its build dependencies are not installable:

[..]
cd .. && sbuild \
  --extra-repository='deb http://httpredir.debian.org/debian experimental main' 
\
  --chroot-setup-commands='apt-get install -y apt-transport-https' \
  --extra-repository='deb https://debian-science.alioth.debian.org/apt 
sid-sage/' \
  
--extra-repository-key=/home/infinity0/var/lib/sage/sagemath/debian/deb-sci-sage.asc
 \
  --build-dep-resolver=aspcud \
  --build-failed-commands '%SBUILD_SHELL' \
   \
  "sagemath_8.0-0~sage1.dsc"
[..]
(I)Distcheck: Solving...
output-version: 1.2
native-architecture: amd64
report:
 -
  package: sbuild-build-depends-sagemath-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
conflict:
 pkg1:
  package: libgslcblas0
  version: 2.4+dfsg-5
  architecture: amd64
  unsat-conflict: libgsl2:amd64
 pkg2:
  package: libgsl2
  version: 2.4+dfsg-2
  architecture: amd64
 depchain1:
  -
   depchain:
-
 package: sbuild-build-depends-sagemath-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: libgsl-dev:amd64
-
 package: libgsl-dev
 version: 2.4+dfsg-5
 architecture: amd64
 depends: libgslcblas0:amd64 (= 2.4+dfsg-5)
 depchain2:
  -
   depchain:
-
 package: sbuild-build-depends-sagemath-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: python-cvxopt:amd64
-
 package: python-cvxopt
 version: 1.1.9+dfsg-1+b1
 architecture: amd64
 depends: libgsl2:amd64
[..]

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#826465: texlive-latex-recommended: Unescaped left brace in regex is deprecated

[Norbert Preining]

> Here's a one-character-patch for this issue.

Thanks, added to the git repo, I will upload soon after fixing a few more bugs.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: Re: Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #871155 [brltty] brltty: FTBFS: cc1: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
Added tag(s) pending.

-- 
871155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Samuel Thibault]

Control: tags -1 + pending

Matthias Klose, on lun. 07 août 2017 19:38:01 -0400, wrote:
> but it's brltty setting -Wno-format

Oh, right, we haven't uploaded brltty 5.5 to unstable yet. That version
doesn't set that any more.

Thanks,
Samuel

Processed: Re: git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 868738 + unreproducible
Bug #868738 {Done: Jonathan Nieder } [src:git] git FTBFS on 
several architectures: not ok 134 - --dump-aliases must be used alone
Added tag(s) unreproducible.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
868738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 brltty
Bug #871155 [python2.7] brltty: FTBFS: cc1: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
Bug reassigned from package 'python2.7' to 'brltty'.
Ignoring request to alter found versions of bug #871155 to the same values 
previously set
Ignoring request to alter fixed versions of bug #871155 to the same values 
previously set
> tags -1 + patch
Bug #871155 [brltty] brltty: FTBFS: cc1: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
Added tag(s) patch.

-- 
871155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Matthias Klose]

Control: reassign -1 brltty
Control: tags -1 + patch

http://launchpadlibrarian.net/332236575/brltty_5.4-7ubuntu3_5.4-7ubuntu4.diff.gz

On 07.08.2017 19:18, Samuel Thibault wrote:
> Control: reassign -1 python2.7
> Control: affects -1 brltty
> 
> Hello,
> 
> Lucas Nussbaum, on dim. 06 août 2017 17:15:27 -0400, wrote:
>> Relevant part (hopefully):
>>> gcc -shared -Wl,-soname,libbrlapi.so.0.6 -o libbrlapi.so brlapi_client.o 
>>> -lpthread -lsupc++ 
>>> ar rc libbrlapi.a brlapi_client.o
>>> /usr/bin/ranlib libbrlapi.a
>>> make[2]: Leaving directory '/<>/build-py2.7/Programs'
>>> set -- --quiet build --build-temp .; \
>>> [ "linux-gnu" != "mingw32" ] || set -- "${@}" --compiler mingw32; \
>>> /usr/bin/python2.7 ./setup.py "${@}"
>>> cc1: error: -Wformat-security ignored without -Wformat 
>>> [-Werror=format-security]
>>> cc1: some warnings being treated as errors
>>> error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
>>> Makefile:72: recipe for target 'brlapi.so' failed
>>> make[1]: *** [brlapi.so] Error 1
>>
>> The full build log is available from:
>>http://aws-logs.debian.net/2017/08/05/brltty_5.4-7_unstable.log
> 
> AIUI, this is coming from python2.7 itself:
> 
> /usr/lib/python2.7/plat-x86_64-linux-gnu/_sysconfigdata_nd.py: 'PY_CFLAGS': 
> '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
> -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-HVkOs2/python2.7-2.7.13=. 
> -fstack-protector-strong -Wformat -Werror=format-security  ',
> 
> Samuel
> 

but it's brltty setting -Wno-format

Bug#826465: texlive-latex-recommended: Unescaped left brace in regex is deprecated

[gregor herrmann]

Control: tag -1 + patch

On Tue, 07 Jun 2016 15:28:42 +0200, =?UTF-8?Q?Preu=C3=9Fe wrote:

> On 05.06.2016 19:49, Niko Tyni wrote:
> 
> Dear Heiko,
> 
> here in the DBTS we got a bug report about a small syntax error in thumbpdf. 
> It
> becomes visible when calling the script using perl 5.22. Simply call thumbpdf 
> w/
> argument:
> 
> hille@sid:~ $ thumbpdf
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by
> <-- HERE in m/\\UseRGB{ <-- HERE (\d+)}\\\s*\d+\s*R/ at /usr/bin/thumbpdf 
> line 1456.
> THUMBPDF 3.16, 2014/07/15 - Copyright (c) 1999-2014 by Heiko Oberdiek.
> Syntax:   thumbpdf [options] 
> 
> Fix should be straight forward, please be so kind to comment on this and 
> upload
> a fixed package.

Here's a one-character-patch for this issue.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   
diff -Nru texlive-base-2017.20170801/debian/changelog texlive-base-2017.20170801/debian/changelog
--- texlive-base-2017.20170801/debian/changelog	2017-08-01 03:06:47.0 -0400
+++ texlive-base-2017.20170801/debian/changelog	2017-08-07 19:23:07.0 -0400
@@ -1,3 +1,12 @@
+texlive-base (2017.20170801-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Unescaped left brace in regex is deprecated":
+add patch thumbpdf-unescaped-left-brace to fix unescaped literal curly.
+(Closes: #826465)
+
+ -- gregor herrmann   Mon, 07 Aug 2017 19:23:07 -0400
+
 texlive-base (2017.20170801-1) unstable; urgency=medium
 
   * new upstream checkout: The Long Dark release!
diff -Nru texlive-base-2017.20170801/debian/patches/series texlive-base-2017.20170801/debian/patches/series
--- texlive-base-2017.20170801/debian/patches/series	2017-07-24 20:59:46.0 -0400
+++ texlive-base-2017.20170801/debian/patches/series	2017-08-07 19:23:07.0 -0400
@@ -29,3 +29,4 @@
 texdoctk-colors
 oberdiek-fix-boxdraw
 texdoctk-warn-missing-perltk
+thumbpdf-unescaped-left-brace
diff -Nru texlive-base-2017.20170801/debian/patches/thumbpdf-unescaped-left-brace texlive-base-2017.20170801/debian/patches/thumbpdf-unescaped-left-brace
--- texlive-base-2017.20170801/debian/patches/thumbpdf-unescaped-left-brace	1969-12-31 19:00:00.0 -0500
+++ texlive-base-2017.20170801/debian/patches/thumbpdf-unescaped-left-brace	2017-08-07 19:23:07.0 -0400
@@ -0,0 +1,18 @@
+Description: Fix "Unescaped left brace in regex is illegal here in regex" error
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/826465
+Forwarded: no
+Author: gregor herrmann 
+Last-Update: 2017-08-07
+
+--- a/texmf-dist/scripts/thumbpdf/thumbpdf.pl
 b/texmf-dist/scripts/thumbpdf/thumbpdf.pl
+@@ -1453,7 +1453,7 @@
+ my $length = $thumblength[$i];
+ my $dict = $objtext[$thumbobj[$i]];
+ $dict =~ s/\\the\\pdflastobj\\\s*\d+\s*R/{RGB_$i}/;
+-$dict =~ s/\\UseRGB{(\d+)}\\\s*\d+\s*R/{RGB_$1}/;
++$dict =~ s/\\UseRGB\{(\d+)}\\\s*\d+\s*R/{RGB_$1}/;
+ $dict =~ s/\/Length\s+\d+\s*//;
+ $dict =~ s/^\s+//;
+ $dict =~ s/\s+$//;


signature.asc
Description: Digital Signature

Processed: Re: Bug#826465: texlive-latex-recommended: Unescaped left brace in regex is deprecated

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #826465 [texlive-latex-recommended] texlive-latex-recommended: Unescaped 
left brace in regex is deprecated
Bug #871345 [texlive-latex-recommended] kimwitu-doc: FTBFS: Unescaped left 
brace in regex is illegal here in regex; marked by <-- HERE in m/\\UseRGB{ <-- 
HERE (\d+)}\\\s*\d+\s*R/ at /usr/bin/thumbpdf line 1456.
Added tag(s) patch.
Added tag(s) patch.

-- 
826465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826465
871345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#868738: marked as done (git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 16:30:50 -0700
with message-id <20170807233050.gz13...@aiede.mtv.corp.google.com>
and subject line Re: git FTBFS on several architectures: not ok 134 - 
--dump-aliases must be used alone
has caused the Debian Bug report #868738,
regarding git FTBFS on several architectures: not ok 134 - --dump-aliases must 
be used alone
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.)


-- 
868738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git
Version: 1:2.13.3-1
Severity: serious

https://buildd.debian.org/status/package.php?p=git=sid

...
expecting success: 
test_must_fail git send-email --dump-aliases --to=jan...@example.com -1 
refs/heads/accounting

--dump-aliases incompatible with other options
test_must_fail: command not found: git send-email --dump-aliases 
--to=jan...@example.com -1 refs/heads/accounting
not ok 134 - --dump-aliases must be used alone
#   
#   test_must_fail git send-email --dump-aliases 
--to=jan...@example.com -1 refs/heads/accounting
#   
...
# failed 1 among 149 test(s)
1..149
Makefile:49: recipe for target 't9001-send-email.sh' failed
make[4]: *** [t9001-send-email.sh] Error 1
--- End Message ---
--- Begin Message ---
Version: 1:2.14.0-1
Control: tags -1 + unreproducible

Jonathan Nieder wrote:

> Thanks for reporting.  The relevant code is
>
>   die __("--dump-aliases incompatible with other options\n")
>   if !$help and $dump_aliases and @ARGV;
>
> test_must_fail prints the "command not found" message if and only if
> the status code was 127.  I would have expected it to be 1 or 128
> here.
[...]
> int exitstatus;
> if (errno & 255)
> STATUS_UNIX_SET(errno);
> else {
> exitstatus = STATUS_UNIX >> 8;
> if (exitstatus & 255)
> STATUS_UNIX_SET(exitstatus);
> else
> STATUS_UNIX_SET(255);
> }
>
> which seems risky (there are many functions that could set errno, so
> this is prone to spooky action at a distance if any caller forgets to
> set it explicitly).  Looking for errno values that could be 127 in
> glibc and linux using "git grep --cached -e '#.*define.*E.*127'", I
> find
>
>  linux:arch/alpha/include/uapi/asm/errno.h:#define ERESTART127
>  linux:arch/mips/include/uapi/asm/errno.h:#define ENETDOWN 127
>  linux:arch/sparc/include/uapi/asm/errno.h:#define ECANCELED   127
>  linux:include/uapi/asm-generic/errno.h:#defineEKEYEXPIRED 127
>
> so that doesn't look likely to be the cause.
>
> Next step is to ssh into porterboxes and get the output of
>
>   perl -e 'die "testing"'; echo $?"

Alas, it doesn't appear to be reproducible.  I fully expect this to
happen again later, but closing for now.--- End Message ---

Processed: Intent to NMU: pelican/3.7.1+dfsg.1-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #868047 [src:pelican] pelican ships non-free files
Added tag(s) pending.

-- 
868047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Intent to NMU: pelican/3.7.1+dfsg.1-1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #868049 [src:pelican] pelican: privacy breach in "notmyidea" theme
Added tag(s) pending.

-- 
868049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#868047: Intent to NMU: pelican/3.7.1+dfsg.1-1

[Ben Finney]

Control: tags -1 + pending

Given that both these (bug#868049, bug#868047) are Severity: serious,
the ‘pelican’ package is scheduled for removal from “testing” very
soon.

I have a Git repository to develop release “3.7.1+dfsg.1-1”
.

If there is no substantive objection before my evening today (Tue
2017-08-08 UTC+10:00), I will do a Non-Maintainer Upload of the
release I have prepared, incorporating the patches to fix these bugs
to allow the package to remain.

-- 
 \   “The apparent lesson of the Inquisition is that insistence on |
  `\ uniformity of belief is fatal to intellectual, moral, and |
_o__)spiritual health.” —_The Uses Of The Past_, Herbert J. Muller |
Ben Finney 


signature.asc
Description: PGP signature

Processed: Re: Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 python2.7
Bug #871155 [src:brltty] brltty: FTBFS: cc1: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
Bug reassigned from package 'src:brltty' to 'python2.7'.
No longer marked as found in versions brltty/5.4-7.
Ignoring request to alter fixed versions of bug #871155 to the same values 
previously set
> affects -1 brltty
Bug #871155 [python2.7] brltty: FTBFS: cc1: error: -Wformat-security ignored 
without -Wformat [-Werror=format-security]
Added indication that 871155 affects brltty

-- 
871155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871155: brltty: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Samuel Thibault]

Control: reassign -1 python2.7
Control: affects -1 brltty

Hello,

Lucas Nussbaum, on dim. 06 août 2017 17:15:27 -0400, wrote:
> Relevant part (hopefully):
> > gcc -shared -Wl,-soname,libbrlapi.so.0.6 -o libbrlapi.so brlapi_client.o 
> > -lpthread -lsupc++ 
> > ar rc libbrlapi.a brlapi_client.o
> > /usr/bin/ranlib libbrlapi.a
> > make[2]: Leaving directory '/<>/build-py2.7/Programs'
> > set -- --quiet build --build-temp .; \
> > [ "linux-gnu" != "mingw32" ] || set -- "${@}" --compiler mingw32; \
> > /usr/bin/python2.7 ./setup.py "${@}"
> > cc1: error: -Wformat-security ignored without -Wformat 
> > [-Werror=format-security]
> > cc1: some warnings being treated as errors
> > error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
> > Makefile:72: recipe for target 'brlapi.so' failed
> > make[1]: *** [brlapi.so] Error 1
> 
> The full build log is available from:
>http://aws-logs.debian.net/2017/08/05/brltty_5.4-7_unstable.log

AIUI, this is coming from python2.7 itself:

/usr/lib/python2.7/plat-x86_64-linux-gnu/_sysconfigdata_nd.py: 'PY_CFLAGS': 
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-HVkOs2/python2.7-2.7.13=. 
-fstack-protector-strong -Wformat -Werror=format-security  ',

Samuel

Bug#871367: fftw: FTBFS: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/\@(\w+){ <-- HERE ([^\{\}]+)}/ at texi2html

[gregor herrmann]

Control: tag -1 + patch

On Mon, 07 Aug 2017 11:50:33 -0400, Lucas Nussbaum wrote:

> Source: fftw
> Version: 2.1.5-4.1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170807 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>/doc'
> > perl texi2html -split_chapter -no_toc_href fftw.texi
> > Unescaped left brace in regex is deprecated here (and will be fatal in Perl 
> > 5.30), passed through in regex; marked by <-- HERE in m/\@(\w+){ <-- HERE 
> > ([^\{\}]+)}/ at texi2html line 1771.
> > Unescaped left brace in regex is illegal here in regex; marked by <-- HERE 
> > in m/\@value{ <-- HERE ([^\s\{\}]+)}/ at texi2html line 842,  line 4.
> > Makefile:799: recipe for target 'html' failed
> > make[1]: *** [html] Error 25

Here's yet another patch for texi2html.
(And a bonus feature to make testing the build easier.)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   
diff -Nru fftw-2.1.5/debian/changelog fftw-2.1.5/debian/changelog
--- fftw-2.1.5/debian/changelog	2016-09-18 08:15:51.0 -0400
+++ fftw-2.1.5/debian/changelog	2017-08-07 18:39:10.0 -0400
@@ -1,3 +1,14 @@
+fftw (2.1.5-4.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS: Unescaped left brace in regex is deprecated here":
+add patch fix-texi2html-perl526.patch to fix Perl 5.26 regexp
+warnings/errors.
+(Closes: #871367)
+  * Add support for DEB_BUILD_OPTIONS=nocheck in debian/rules.
+
+ -- gregor herrmann <gre...@debian.org>  Mon, 07 Aug 2017 18:39:10 -0400
+
 fftw (2.1.5-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch
--- fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch	1969-12-31 19:00:00.0 -0500
+++ fftw-2.1.5/debian/patches/fix-texi2html-perl526.patch	2017-08-07 18:39:10.0 -0400
@@ -0,0 +1,35 @@
+Description: Fix perl 5.26 regexp warnings/errors
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/871367
+Author: gregor herrmann <gre...@debian.org>
+Last-Update: 2017-08-07
+
+--- a/doc/texi2html
 b/doc/texi2html
+@@ -839,7 +839,7 @@
+ s/\@refill\s+//g;
+ # other substitutions
+ _substitutions;
+-s/\@value{($VARRE)}/$value{$1}/eg;
++s/\@value\{($VARRE)}/$value{$1}/eg;
+ s/\@footnote\{/\@footnote$docu_doc\{/g; # mark footnotes, cf. pass 4
+ #
+ # analyze the tag again
+@@ -1169,7 +1169,7 @@
+ #
+ # xref
+ #
+-while (/\@(x|px|info|)ref{($XREFRE)(}?)/o) {
++while (/\@(x|px|info|)ref\{($XREFRE)(}?)/o) {
+ 	# note: Texinfo may accept other characters
+ 	($type, $nodes, $full) = ($1, $2, $3);
+ 	($before, $after) = ($`, $');
+@@ -1768,7 +1768,7 @@
+ while ($changed) {
+ 	$changed = 0;
+ 	$done = '';
+-	while (/\@(\w+){([^\{\}]+)}/) {
++	while (/\@(\w+)\{([^\{\}]+)}/) {
+ 	$text = _style($1, $2);
+ 	if ($text) {
+ 		$_ = "$`$text$'";
diff -Nru fftw-2.1.5/debian/patches/series fftw-2.1.5/debian/patches/series
--- fftw-2.1.5/debian/patches/series	2016-09-18 08:06:40.0 -0400
+++ fftw-2.1.5/debian/patches/series	2017-08-07 18:39:10.0 -0400
@@ -5,3 +5,4 @@
 info-syntax
 fix-texi2html-perl522.patch
 perl-cwd-in-inc.patch
+fix-texi2html-perl526.patch
diff -Nru fftw-2.1.5/debian/rules fftw-2.1.5/debian/rules
--- fftw-2.1.5/debian/rules	2016-07-11 15:59:11.0 -0400
+++ fftw-2.1.5/debian/rules	2017-08-07 18:39:10.0 -0400
@@ -30,17 +30,21 @@
 	# single precision
 	F77=gfortran CFLAGS="$(CFLAGS)" CC=mpicc ./configure $(CONFFLAGS) --enable-float --enable-type-prefix $(ARCHCONFFLAGS)
 	$(MAKE)
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 	#$(MAKE) -C tests check
 	./tests/fftw_test  -t -e -v -p 1024 -x 1
 	./tests/rfftw_test -t -e -v -p 1024 -x 1
+endif
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp-single
 	$(MAKE) clean
 	# double precision
 	F77=gfortran CFLAGS="$(CFLAGS)" CC=mpicc ./configure $(CONFFLAGS) $(ARCHCONFFLAGS)
 	$(MAKE)
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 	#$(MAKE) -C tests check
 	./tests/fftw_test  -t -e -v -p 1024 -x 1
 	./tests/rfftw_test -t -e -v -p 1024 -x 1
+endif
 	$(MAKE) install DESTDIR=$(CURDIR)/debian/tmp-double
 	touch build-arch-stamp
 


signature.asc
Description: Digital Signature

Processed: Re: Bug#871367: fftw: FTBFS: Unescaped left brace in regex is deprecated here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- HERE in m/\@(\w+){ <-- HERE ([^\{\}]+)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #871367 [src:fftw] fftw: FTBFS: Unescaped left brace in regex is deprecated 
here (and will be fatal in Perl 5.30), passed through in regex; marked by <-- 
HERE in m/\@(\w+){ <-- HERE ([^\{\}]+)}/ at texi2html line 1771.
Added tag(s) patch.

-- 
871367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 859577 by 871439
Bug #859577 {Done: Michael Lustfield } 
[golang-github-syndtr-goleveldb-dev] golang-github-syndtr-goleveldb-dev: file 
conflict with golang-goleveldb-dev
859577 was not blocked by any bugs.
859577 was not blocking any bugs.
Added blocking bug(s) of 859577: 871439
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
859577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#870796: [tex-live] segfault on build-testing luatex

[Norbert Preining]

> > Related to gcc-7.1?
> > http://tug.org/pipermail/tex-live/2017-June/040192.html
> 
> Ahh, sounds reasonable ... will try tomorrow, time for bed.

Confirmed that the patch fixes it, at leasts for now.

THanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#870796: marked as done (texlive-bin: FTBFS: Test falure)

[Debian Bug Tracking System]

Your message dated Tue, 8 Aug 2017 07:57:41 +0900
with message-id <20170807225741.ro2huia5csode...@bulldog.preining.info>
and subject line Re: Bug#870796: texlive-bin: FTBFS: Test falure
has caused the Debian Bug report #870796,
regarding texlive-bin: FTBFS: Test falure
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.)


-- 
870796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texlive-bin
Version: 2017.20170613.44572-3
Severity: serious

>From my pbuilder build log (on amd64):

...
FAIL: luatexdir/luaimage


This is LuaTeX, Version 1.0.4 (TeX Live 2017/Debian)  (INITEX)
restricted system commands enabled.
(../../../texk/web2c/luatexdir/tests/luaimage.tex
(../../../texk/web2c/tests/basic.tex Preloading the plain format: codes,
registers, parameters, macros, math definitions, output routines, hyphenation))

Beginning to dump on file luaimage.fmt
(format=luaimage 2017.7.9)
2374 strings using 6763 bytes
10085 memory locations dumped; current usage is 132&5003
1335 multiletter control sequences
\font\nullfont=nullfont
0 preloaded fonts
No pages of output.
Transcript written on luaimage.log.
Segmentation fault
FAIL luatexdir/luaimage.test (exit status: 1)


Testsuite summary for Web2C 2017

# TOTAL: 89
# PASS:  85
# SKIP:  3
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to te...@tug.org

Makefile:13508: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1
make[6]: Leaving directory
'/build/texlive-bin-2017.20170613.44572/Work/texk/web2c'
Makefile:13614: recipe for target 'check-TESTS' failed
make[5]: *** [check-TESTS] Error 2
make[5]: Leaving directory
'/build/texlive-bin-2017.20170613.44572/Work/texk/web2c'
Makefile:13855: recipe for target 'check-am' failed
make[4]: *** [check-am] Error 2
make[4]: Leaving directory
'/build/texlive-bin-2017.20170613.44572/Work/texk/web2c'
Makefile:13394: recipe for target 'check-recursive' failed
make[3]: *** [check-recursive] Error 1
make[3]: Leaving directory
'/build/texlive-bin-2017.20170613.44572/Work/texk/web2c'
Makefile:451: recipe for target 'check-recursive' failed
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory '/build/texlive-bin-2017.20170613.44572/Work/texk'
Makefile:540: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/texlive-bin-2017.20170613.44572/Work'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:67: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 2017.20170613.44572-4

Fixed in previous upload, but changelog was messed up due. Closing
it now with correct version number.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#871369: marked as done (wings3d: FTBFS: wings_cc_ref.erl:23: export_all flag enabled - all functions will be exported)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 22:24:02 +
with message-id <e1deqro-0005qk...@fasolo.debian.org>
and subject line Bug#871369: fixed in wings3d 2.1.5-2
has caused the Debian Bug report #871369,
regarding wings3d: FTBFS: wings_cc_ref.erl:23: export_all flag enabled - all 
functions will be exported
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.)


-- 
871369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wings3d
Version: 2.1.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[4]: Entering directory '/<>/src'
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_lang.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin user_default.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_align.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_body.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_camera.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_cl.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_cc.erl
> erlc -Werror -I ../e3d +debug_info '-Dwings_version="2.1.5"' -pa 
> ../intl_tools  -o../ebin wings_cc_ref.erl
> compile: warnings being treated as errors
> wings_cc_ref.erl:23: export_all flag enabled - all functions will be exported
> Makefile:168: recipe for target '../ebin/wings_cc_ref.beam' failed
> make[4]: *** [../ebin/wings_cc_ref.beam] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/wings3d_2.1.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: wings3d
Source-Version: 2.1.5-2

We believe that the bug you reported is fixed in the latest version of
wings3d, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan <sgolo...@debian.org> (supplier of updated wings3d 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: Tue, 08 Aug 2017 00:40:12 +0300
Source: wings3d
Binary: wings3d
Architecture: source amd64
Version: 2.1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers <pkg-erlang-de...@lists.alioth.debian.org>
Changed-By: Sergei Golovan <sgolo...@debian.org>
Description:
 wings3d- Nendo-inspired 3D polygon mesh modeller
Closes: 871369
Changes:
 wings3d (2.1.5-2) unstable; urgency=medium
 .
   * Added a patch by upstream which fixes FTBFS when building with
 Erlang/OTP 20 (closes: #871369).
Checksums-Sha1:
 0816786603499d9af6c43c1ffab0a0e0297025e8 1940 wings3d_2.1.5-2.dsc
 c275ef78ecd5e294764a86e7521aa170834ee323 15628 wings3d_2.1.5-2.debian.tar.xz
 88b84822a3b8c4ff77cba54b3873a3b215c1bf83 2214 wings3d-dbgsym_2.1.5-2_amd64.deb
 88a8b8cd7d67f12b0b430859e3b551c57942797d 10287 wings3d_2.1.5-2_amd64.buildinfo
 48c7bf08aacadb557452770511167b7738999313 6065022 wings3d_2.1.5-2_amd64.deb
Checksums-Sha256:
 cc7ae58c02c64902bef67127618794e3d10c474c3fcc2e947b31fe33a36b3aa8 1940 
wing

Bug#871206: libxmlbird: FTBFS: make[1]: doit3: Command not found

[Hideki Yamane]

Hi,

On Sun, 6 Aug 2017 18:37:52 -0400
Lucas Nussbaum  wrote:
> Source: libxmlbird
(snip)
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> > doit3
> > make[1]: doit3: Command not found

 It was introduced changes in doit (0.30.3-1), just "doit" is okay for now.
 Unfortunately, I cannot upload packages until back to home after DebConf17,
 so this is just a note.


-- 
Hideki Yamane 

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 870599 grave
Bug #870599 [ansible] ansible: Needs pinned Jinja2 dependency due to upstream 
bug #20494
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
870599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forwarded 853664 https://github.com/a2o/snoopy/issues/123

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 853664 https://github.com/a2o/snoopy/issues/123
Bug #853664 [src:snoopy] snoopy: ftbfs with GCC-7
Set Bug forwarded-to-address to 'https://github.com/a2o/snoopy/issues/123'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
853664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forwarded 853570 https://github.com/nmap/ncrack/issues/24

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 853570 https://github.com/nmap/ncrack/issues/24
Bug #853570 [src:ncrack] ncrack: ftbfs with GCC-7
Set Bug forwarded-to-address to 'https://github.com/nmap/ncrack/issues/24'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
853570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871307: marked as done (libmimetic0v5: requires rebuild against GCC 7 and symbols/shlibs bump)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 21:09:55 +
with message-id 
and subject line Bug#871307: fixed in mimetic 0.9.8-6
has caused the Debian Bug report #871307,
regarding libmimetic0v5: requires rebuild against GCC 7 and symbols/shlibs bump
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.)


-- 
871307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmimetic0v5
Version: 0.9.8-5
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-op-mangling

Hi,

It appears that your package provides an external symbol that is
affected by the recent name mangling changes in GCC 7. See:
https://gcc.gnu.org/gcc-7/porting_to.html#conversion-op-mangling

In GCC 7, the name mangling for C++ conversion operators which return a
type using the abi_tag attribute (most commonly std::string) has
changed. When your library is compiled with GCC 7, it will now emit two
symbols for the conversion operator using the new and old naming.
Executables compiled with GCC 7 will always use the new symbol, while
old executables compiled using <= GCC 6 will use the old symbol. For new
executables to build without undefined references, your library will
need rebuilding with GCC 7.

To ensure that new executables will pull in the newer version of the
library built with GCC 7:
- Your library package should Build-Depend on g++ (>= 4:7).
- If your package provides a symbols file, ensure that the new
  conversion operator symbols have a version matching the version this
  bug is fixed in (including the Debian revision and tilde if
  necessary).

  Using apt as an example (debian/libapt-pkg5.0.symbols):
(c++)"URI::operator std::__cxx11::basic_string[abi:cxx11]()@APTPKG_5.0" 0.8.0
  + (c++)"URI::operator std::__cxx11::basic_string()@APTPKG_5.0" 1.5~beta2~

  Where "1.5~beta2" is the version this bug was fixed in.

- If your package does not provide a symbols file, add a dh_makeshlibs
  override so that tight enough dependencies are generated.

  Using libebml as an example (debian/rules):
  + override_dh_makeshlibs:
  + # For new symbols when compiled with GCC 7
  + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'

  Where "1.3.4-2" is the version this bug was fixed in.

- If your package is about to be renamed due to an upstream SONAME bump,
  you do not need to add any special symbols handling.

If you would like to know the exact name of the new symbols, using
"abipkgdiff" from abigail-tools might be able to help.

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: mimetic
Source-Version: 0.9.8-6

We believe that the bug you reported is fixed in the latest version of
mimetic, 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 871...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated mimetic 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: SHA512

Format: 1.8
Date: Mon, 07 Aug 2017 16:21:19 -0400
Source: mimetic
Binary: libmimetic-dev libmimetic-doc libmimetic0v5
Architecture: source
Version: 0.9.8-6
Distribution: unstable
Urgency: medium
Maintainer: gregor herrmann 
Changed-By: gregor herrmann 
Closes: 871307
Description: 
 libmimetic-dev - C++ MIME library (development)
 libmimetic-doc - C++ MIME library (documentation)
 libmimetic0v5 - C++ MIME library (runtime)
Changes:
 mimetic (0.9.8-6) unstable; urgency=medium
 .
   * Adapt to C++ name mangling in GCC 7:
 - Build-Depend on g++ (>= 4:7)
 - Override dh_makeshlibs for new symbols from gcc 7
 Thank to James Cowgill for the bug report.
 Closes: #871307
   * Update years of packaging copyright.
   * Bump debhelper compat level and dependency to 10.
 Drop manual autoreconf fragments.
   * Support DEB_BUILD_OPTIONS/DEB_BUILD_PROFILES "nodoc".
   * Use HTTPS for Format URL in debian/copyright.
   * Add linitian override about insecure Vcs URLs.
   * Add all hardening options in 

Bug#870821: marked as done (esys-particle FTBFS with perl 5.26)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 21:05:28 +
with message-id 
and subject line Bug#870821: fixed in esys-particle 2.3.5+dfsg1-2
has caused the Debian Bug report #870821,
regarding esys-particle FTBFS with perl 5.26
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.)


-- 
870821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870821
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: esys-particle
Version: 2.3.5+dfsg1-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/esys-particle.html

...
./makeglos.pl paper.glo
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in 
m/\\newglossarytype\[(.*)\]{ <-- HERE (.*)}{(.*)}{(.*)}/ at ./makeglos.pl line 
49.
Makefile:606: recipe for target 'ESyS-Particle_Tutorial.pdf' failed
make[4]: *** [ESyS-Particle_Tutorial.pdf] Error 255
--- End Message ---
--- Begin Message ---
Source: esys-particle
Source-Version: 2.3.5+dfsg1-2

We believe that the bug you reported is fixed in the latest version of
esys-particle, 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 870...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated esys-particle 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: Mon, 07 Aug 2017 22:05:00 +0200
Source: esys-particle
Binary: esys-particle
Architecture: source
Version: 2.3.5+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 esys-particle - Software for particle-based numerical modelling. MPI version.
Closes: 870821
Changes:
 esys-particle (2.3.5+dfsg1-2) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * [1da0be3] Fix "Unescaped left brace in regex is illegal" error in perl
   helper scripts. (Closes: #870821)
 .
   [ Anton Gladky ]
   * [314841d] Drop dependencies on dh-autoreconf and autotools-dev.
   * [337b5dc] Bump Standards-Version: 4.0.0
Checksums-Sha1:
 ebe12851f1c2955e0c16f8e0440d5cba531afe0f 2372 esys-particle_2.3.5+dfsg1-2.dsc
 fb6de015e6a58cfd02739799abc900c98b5b4e35 565068 
esys-particle_2.3.5+dfsg1-2.debian.tar.xz
 ecf3bc46ebab0ee3da07cbc8840ac2c7be619653 14329 
esys-particle_2.3.5+dfsg1-2_source.buildinfo
Checksums-Sha256:
 f574841494bd545399dcf8dab1b3552719dc649d9fe043c88607affd43c8 2372 
esys-particle_2.3.5+dfsg1-2.dsc
 57e98e9a71d67f0c260f8df5ab3d3bb50fabef9feac960dafa900c0362c79c74 565068 
esys-particle_2.3.5+dfsg1-2.debian.tar.xz
 a9185c12382cc698825837ba2dcb8b95232a6c5a1054c9b0f668e0cf66d54db1 14329 
esys-particle_2.3.5+dfsg1-2_source.buildinfo
Files:
 751d16a6129838ffd816ce94938ccb77 2372 science extra 
esys-particle_2.3.5+dfsg1-2.dsc
 f2061b0a3414c122c9e12904513bb271 565068 science extra 
esys-particle_2.3.5+dfsg1-2.debian.tar.xz
 6e178ea78444387b7a9a7f1d27e24d3b 14329 science extra 
esys-particle_2.3.5+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlmIyEYACgkQ0+Fzg8+n
/waqmg//TCTYS/2W2/n8nLzOsb6qwAz4reqm5yeBrMRiTQJSWunRF8RWauAqImVl
7qbnmCR3dpV2QDOQXxq7lBaQGtHin/Ltf3oYwODzc8lEoVbMBjZel/Eo7PIYiYBZ
jtZqCHZS4N8zLPDksjRL/KkFjUe7k6U3G2EdHVIzHLKtb/xemaRUIUZq7OiV3GIZ
ZhAd848h4X9eNFTVvKdh4K2lgQ3FDJwUxrm36qxmo9FUawP/e0myj9Kzq0B8VzPJ
EBCbqqTDMdBaadMN9bXewDWu+aE/uiBh7Z4Apk90ZV00Iui2d6l3TgRCk8kXkfWr
TjdRpXlPH83nbPQ5R7hNZdkkg5SzILzyD9/cnoabYD+m2eU7+weE+FGYm/ih8Urj
HiSvoy3W+3Z1VBXP1XmS4p2wKvqpSElHnbclayakcZ7VQ1obhjZzcuY714+jxZkz
opTa7/EgTRD3BVL8opYaWtSa5kHHsmffv+YU9GYK9ZpjFbC7eE8VCpf/4KYI3bCn
HbqF1m9mL9RJBCHnaBK/2xlq0PAQrKCngg1Ce/vqYwSsP8LbrMiEVsKhHKrwMGUk
x0YLym2NX0JRZJSbx23vLvjaQ6kdK4txp9hyFqQucy5azAJsPX82RRxxJ1YEwmb/
iMcHlT13YCKkV7bAEpcD1Coi+qTokec3FHRZbBp09Dq9XQ5Yc40=
=13sG
-END PGP SIGNATURE End Message ---

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Bernhard Schmidt]

Control: tags -1 + pending

On Thu, Aug 03, 2017 at 11:21:28AM +0200, Bernhard Schmidt wrote:

> stretch-pu filed as
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870604

Accepted into p-u, will be part of Debian 9.2 and should be available
shortly on https://www.debian.org/releases/proposed-updates.en.html

Best Regards,
Bernhard

Processed: Re: Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #863110 {Done: Bernhard Schmidt } [openvpn] openvpn: VPN 
remains connected, but network is unreachable after 30-45 min and requires 
reconnect
Added tag(s) pending.

-- 
863110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#863110: marked as done (openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 21:02:09 +
with message-id 
and subject line Bug#863110: fixed in openvpn 2.4.0-6+deb9u2
has caused the Debian Bug report #863110,
regarding openvpn: VPN remains connected, but network is unreachable after 
30-45 min and requires reconnect
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.)


-- 
863110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvpn
Version: 2.4.0-5
Severity: important

Dear Maintainer,

   After the upgrade to openvpn 2.4.0-5 (from *-4), an issue has been
   occuring where after having been connected to the VPN for an
   approximate amount of time of around 30-45 minutes, the network
   connection will drop.  NetworkManager continues to state that the VPN
   is currently active, but no network is reachable.  The only way to
   restart the VPN network is to bring the connection up again.

   As stated before, I am using openvpn through NetworkManger, and use
   nmcli with a configured VPN config file and a separate password file from a 
paid service I
   subscribe to.


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (300, 'experimental'), (300, 'unstable')
Architecture: amd64
 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.60
ii  init-system-helpers1.48
ii  iproute2   4.9.0-1
ii  libc6  2.24-10
ii  liblz4-1   0.0~r131-2+b1
ii  liblzo2-2  2.08-1.2+b2
ii  libpam0g   1.1.8-3.5
ii  libpkcs11-helper1  1.21-1
ii  libssl1.0.21.0.2k-1
ii  libsystemd0232-23
ii  lsb-base   9.20161125

Versions of packages openvpn recommends:
ii  easy-rsa  2.2.2-2

Versions of packages openvpn suggests:
ii  openssl 1.1.0e-2
pn  resolvconf  

-- debconf information:
  openvpn/create_tun: false
--- End Message ---
--- Begin Message ---
Source: openvpn
Source-Version: 2.4.0-6+deb9u2

We believe that the bug you reported is fixed in the latest version of
openvpn, 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 863...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated openvpn 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: Tue, 18 Jul 2017 22:15:17 +0200
Source: openvpn
Binary: openvpn
Architecture: source
Version: 2.4.0-6+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Alberto Gonzalez Iniesta 
Changed-By: Bernhard Schmidt 
Description:
 openvpn- virtual private network daemon
Closes: 863110
Changes:
 openvpn (2.4.0-6+deb9u2) stretch; urgency=medium
 .
   * Fix broken reconnect on connection loss due to wrong push digest 
calculation.
 Thanks to Patrick Matthäi for testing (Closes: #863110)
Checksums-Sha1:
 ece690d8456bd677635a2c90cb421bc68e9a29cc 2120 openvpn_2.4.0-6+deb9u2.dsc
 254410cbaa4518d5b7d4c24c1b61491ad7c4837c 60688 
openvpn_2.4.0-6+deb9u2.debian.tar.xz
 dabe641e43f38fe90d9014e88690a920870be54d 6664 
openvpn_2.4.0-6+deb9u2_amd64.buildinfo
Checksums-Sha256:
 c69da23755b553507bb3892a03ac681c1223aa98a65605e8742e62e02696c331 2120 
openvpn_2.4.0-6+deb9u2.dsc
 1334d6faffb2be1fb23306f381f3cc8c5af6ef03eca2954e69a1051741fe0618 60688 
openvpn_2.4.0-6+deb9u2.debian.tar.xz
 e2b8970d9820f0220e23db3ccc641a37d8908c4818fe90005dab4af2986dd41d 6664 
openvpn_2.4.0-6+deb9u2_amd64.buildinfo
Files:
 536591aeef529fdfa414f26142a385c3 2120 net optional openvpn_2.4.0-6+deb9u2.dsc
 c63e13af0c0099cd10c64e3c7bdfaf68 60688 net optional 
openvpn_2.4.0-6+deb9u2.debian.tar.xz
 829b6d0c9414b5ed11c073e4e23867d0 6664 net optional 
openvpn_2.4.0-6+deb9u2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAlmHbE4RHGJlcm5pQGRl

Bug#871300: [Pkg-gmagick-im-team] Bug#871300: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[James Cowgill]

Hi,

On 07/08/17 16:55, roucaries bastien wrote:
> On Mon, Aug 7, 2017 at 4:47 PM,   wrote:
>> Package: libmagick++-6.q16-7
>> Version: 8:6.9.7.4+dfsg-16
>> Severity: serious
>> Tags: sid buster
>> User: debian-...@lists.debian.org
>> Usertags: gcc-7-op-mangling
>>
> 
> I need a change that break ABI, I will release a new version. Does it
> exist in this case a short cut

If you are going to rename the Debian package and trigger a package
transition, you do not need to add any of the extra symbols/shlibs
stuff. You should still build-depend on gcc (>= 4:7) however - I'm not
sure if all the buildds use GCC 7 by default yet.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#871300: [Pkg-gmagick-im-team] Bug#871300: libmagick++-6.q16-7: requires rebuild against GCC 7 and symbols/shlibs bump

[roucaries bastien]

On Mon, Aug 7, 2017 at 4:47 PM,   wrote:
> Package: libmagick++-6.q16-7
> Version: 8:6.9.7.4+dfsg-16
> Severity: serious
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: gcc-7-op-mangling
>

I need a change that break ABI, I will release a new version. Does it
exist in this case a short cut

>
> Thanks,
> James
>
> ___
> Pkg-gmagick-im-team mailing list
> pkg-gmagick-im-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gmagick-im-team

Processed: Tagging #871231 as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 871231 + pending
Bug #871231 [src:doris] doris: FTBFS with GCC-7: error: ISO C++ forbids 
comparison between pointer and integer
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869986: [Debian-ha-maintainers] Bug#869986: Bug#869986: pacemaker FTBFS: missing symbols

[Valentin Vidic]

On Mon, Aug 07, 2017 at 02:31:57PM -0400, Ferenc Wágner wrote:
> There's no problem with the Pacemaker libs, the "missing" symbols are a
> manifestation of the binutils incompatibility in the libqb headers.

Ok, didn't realize the pacemaker FTBFS was caused by the libqb problem.
Even better, than we only have one nasty bug to squash :)

-- 
Valentin

Processed: Re: Bug#869938: Raising severity to serious since g-s-d 3.24 has been uploaded to unstable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 869938 important
Bug #869938 [afterstep] afterstep: Adapt to gnome-settings-daemon 3.24
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867736: marked as done ([fbpanel] fbpanel crashes with default config)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 16:54:31 -0300
with message-id <3d12e009-a412-269d-9f1d-d4b133482...@debian.org>
and subject line Re: Bug#867736: [fbpanel] fbpanel crashes with default config
has caused the Debian Bug report #867736,
regarding [fbpanel] fbpanel crashes with default config
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.)


-- 
867736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: fbpanel
Version: 7.0-3
Severity: serious

When fbpanel is run with the default config file 
(/usr/share/fbpanel/default) it crashes without displaying any GUI.


The crash output from the terminal follows:
- - -
*** Error in `fbpanel': double free or corruption (out): 
0x558a947cda10 ***

=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f4d4469bbcb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f4d446a1f96]
/lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7f4d446a27de]
/usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7f4d44f38699]
fbpanel(get_utf8_property_list+0x141)[0x558a94308e71]
/usr/lib/fbpanel/libtaskbar.so(+0x453c)[0x7f4d3da7f53c]
/usr/lib/fbpanel/libtaskbar.so(taskbar_constructor+0x4c0)[0x7f4d3da812f0]
fbpanel(plugin_start+0xd8)[0x558a9430aee8]
fbpanel(main+0xdbe)[0x558a943041ce]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f4d4464b2b1]
fbpanel(_start+0x2a)[0x558a9430468a]
=== Memory map: 
558a942fb000-558a9431 r-xp  08:24 1194991
/usr/bin/fbpanel
558a9450f000-558a9451 r--p 00014000 08:24 1194991
/usr/bin/fbpanel
558a9451-558a94511000 rw-p 00015000 08:24 1194991
/usr/bin/fbpanel
558a94726000-558a9488d000 rw-p  00:00 0  
[heap]

7f4d3000-7f4d30022000 rw-p  00:00 0
7f4d30022000-7f4d3400 ---p  00:00 0
7f4d3400-7f4d34021000 rw-p  00:00 0
7f4d34021000-7f4d3800 ---p  00:00 0
7f4d3800-7f4d38021000 rw-p  00:00 0
7f4d38021000-7f4d3c00 ---p  00:00 0
7f4d3d643000-7f4d3d659000 r-xp  08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d659000-7f4d3d858000 ---p 00016000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d858000-7f4d3d859000 r--p 00015000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d859000-7f4d3d85a000 rw-p 00016000 08:24 3015814
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4d3d873000-7f4d3d879000 r-xp  08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3d879000-7f4d3da78000 ---p 6000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da78000-7f4d3da79000 r--p 5000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da79000-7f4d3da7a000 rw-p 6000 08:24 1187724 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
7f4d3da7b000-7f4d3da83000 r-xp  08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3da83000-7f4d3dc82000 ---p 8000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc82000-7f4d3dc83000 r--p 7000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc83000-7f4d3dc84000 rw-p 8000 08:24 1195014
/usr/lib/fbpanel/libtaskbar.so
7f4d3dc8b000-7f4d3dc8d000 r-xp  08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3dc8d000-7f4d3de8c000 ---p 2000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3de8c000-7f4d3de8d000 r--p 1000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so
7f4d3de8d000-7f4d3de8e000 rw-p 2000 08:24 1195019
/usr/lib/fbpanel/libwincmd.so

7f4d3de91000-7f4d3de92000 ---p  00:00 0
7f4d3de92000-7f4d3e692000 rw-p  00:00 0
7f4d3e692000-7f4d3e693000 ---p  00:00 0
7f4d3e693000-7f4d3ee93000 rw-p  00:00 0
7f4d3ee93000-7f4d3ee95000 r-xp  08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3ee95000-7f4d3f094000 ---p 2000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f094000-7f4d3f095000 r--p 1000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f095000-7f4d3f096000 rw-p 2000 08:24 3020637
/lib/x86_64-linux-gnu/libutil-2.24.so
7f4d3f0b3000-7f4d3f0e9000 r-xp  08:24 

Bug#869938: Raising severity to serious since g-s-d 3.24 has been uploaded to unstable

[Robert Luberda]

severity 869938 important
thanks

> I have the package ready, I will upload it shortly.

I'm lowering the severity so that the package won't migrate to testing
too early.

Regards,
robert

Bug#871332: [Pkg-opencl-devel] Bug#871332: beignet: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -

[Rebecca N. Palmer]

Control: tags -1 pending

Fixed in Alioth, ready for upload.

On 07/08/17 16:47, Lucas Nussbaum wrote:

Source: beignet
Version: 1.3.0-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):

make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building CXX object CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o
/usr/bin/c++-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DGBE_DEBUG=1-std=c++98 -o 
CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.cxx
Linking CXX executable cmTC_62e05
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_62e05.dir/link.txt 
--verbose=1
/usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DGBE_DEBUG=1   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_62e05.dir/feature_tests.cxx.o  -o cmTC_62e05
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


 Feature record: CXX_FEATURE:0cxx_aggregate_default_initializers
 Feature record: CXX_FEATURE:0cxx_alias_templates
 Feature record: CXX_FEATURE:0cxx_alignas
 Feature record: CXX_FEATURE:0cxx_alignof
 Feature record: CXX_FEATURE:0cxx_attributes
 Feature record: CXX_FEATURE:0cxx_attribute_deprecated
 Feature record: CXX_FEATURE:0cxx_auto_type
 Feature record: CXX_FEATURE:0cxx_binary_literals
 Feature record: CXX_FEATURE:0cxx_constexpr
 Feature record: CXX_FEATURE:0cxx_contextual_conversions
 Feature record: CXX_FEATURE:0cxx_decltype
 Feature record: CXX_FEATURE:0cxx_decltype_auto
 Feature record: CXX_FEATURE:0cxx_decltype_incomplete_return_types
 Feature record: CXX_FEATURE:0cxx_default_function_template_args
 Feature record: CXX_FEATURE:0cxx_defaulted_functions
 Feature record: CXX_FEATURE:0cxx_defaulted_move_initializers
 Feature record: CXX_FEATURE:0cxx_delegating_constructors
 Feature record: CXX_FEATURE:0cxx_deleted_functions
 Feature record: CXX_FEATURE:0cxx_digit_separators
 Feature record: CXX_FEATURE:0cxx_enum_forward_declarations
 Feature record: CXX_FEATURE:0cxx_explicit_conversions
 Feature record: CXX_FEATURE:0cxx_extended_friend_declarations
 Feature record: CXX_FEATURE:0cxx_extern_templates
 Feature record: CXX_FEATURE:0cxx_final
 Feature record: CXX_FEATURE:0cxx_func_identifier
 Feature record: CXX_FEATURE:0cxx_generalized_initializers
 Feature record: CXX_FEATURE:0cxx_generic_lambdas
 Feature record: CXX_FEATURE:0cxx_inheriting_constructors
 Feature record: CXX_FEATURE:0cxx_inline_namespaces
 Feature record: CXX_FEATURE:0cxx_lambdas
 Feature record: CXX_FEATURE:0cxx_lambda_init_captures
 Feature record: CXX_FEATURE:0cxx_local_type_template_args
 Feature record: CXX_FEATURE:0cxx_long_long_type
 Feature record: CXX_FEATURE:0cxx_noexcept
 Feature record: CXX_FEATURE:0cxx_nonstatic_member_init
 Feature record: CXX_FEATURE:0cxx_nullptr
 Feature record: CXX_FEATURE:0cxx_override
 Feature record: CXX_FEATURE:0cxx_range_for
 Feature record: CXX_FEATURE:0cxx_raw_string_literals
 Feature record: CXX_FEATURE:0cxx_reference_qualified_functions
 Feature record: CXX_FEATURE:0cxx_relaxed_constexpr
 Feature record: CXX_FEATURE:0cxx_return_type_deduction
 Feature record: CXX_FEATURE:0cxx_right_angle_brackets
 Feature record: CXX_FEATURE:0cxx_rvalue_references
 Feature record: CXX_FEATURE:0cxx_sizeof_member
 Feature record: CXX_FEATURE:0cxx_static_assert
 Feature record: CXX_FEATURE:0cxx_strong_enums
 Feature record: CXX_FEATURE:1cxx_template_template_parameters
 Feature record: CXX_FEATURE:0cxx_thread_local
 Feature record: CXX_FEATURE:0cxx_trailing_return_types
 Feature record: CXX_FEATURE:0cxx_unicode_literals
 Feature record: CXX_FEATURE:0cxx_uniform_initialization
 Feature record: CXX_FEATURE:0cxx_unrestricted_unions
 Feature record: CXX_FEATURE:0cxx_user_literals
 Feature record: CXX_FEATURE:0cxx_variable_templates
 Feature record: CXX_FEATURE:0cxx_variadic_macros
 Feature record: CXX_FEATURE:0cxx_variadic_templates
dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DLLVM_INSTALL_DIR=/usr/lib/llvm-4.0/bin -DENABLE_OPENCL_20=1 returned exit 
code 1
debian/rules:26: recipe for target 'override_dh_auto_configure' failed
make[1]: *** 

Processed: Re: [Pkg-opencl-devel] Bug#871332: beignet: FTBFS: dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/et

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #871332 [src:beignet] beignet: FTBFS: dh_auto_configure: cmake .. 
-DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
-DLLVM_INSTALL_DIR=/usr/lib/llvm-4.0/bin -DENABLE_OPENCL_20=1 returned exit 
code 1
Added tag(s) pending.

-- 
871332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871332
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867736: [fbpanel] fbpanel crashes with default config

[Will Brokenbourgh]

On 08/07/2017 12:24 PM, Dererk wrote:

tags 867736 +unreproducible +moreinfo

thanks


Hi Will.

I'm unable to reproduce the mentioned behavior. Just to go through it
step-by-step on this, what do you get at the end of the process?

$  mkdir ~/.config/fbpanel && cp /usr/share/fbpanel/default
~/.config/fbpanel/default

$  fbpanel


Cheers,

Dererk


Greetings Dererk,

This bug appears to be resolved as it is no longer crashing on Stretch.  
I had already performed the steps you suggested before filing this 
report, but it appears a dependency was changed since I filed the report 
which has fixed the crashing behavior.


Thanks!

Will Brokenbourgh
Pacific Northwest, USA

Sent from my Linux desktop

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Mattia Rizzolo]

On Tue, Aug 08, 2017 at 02:29:48AM +0800, Drew Parsons wrote:
> It's been sitting in NEW for a month, so it would have been gcc-6 I
> think.  But the upload is to experimental.  I figure we can ignore
> anything in experimental, the symbols will get reset for the new ABI
> when we drop it into unstable.

Right, that would be fine.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: Re: Bug#867736: [fbpanel] fbpanel crashes with default config

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 867736 +unreproducible +moreinfo
Bug #867736 [fbpanel] [fbpanel] fbpanel crashes with default config
Added tag(s) unreproducible.
Bug #867736 [fbpanel] [fbpanel] fbpanel crashes with default config
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
867736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#867736: [fbpanel] fbpanel crashes with default config

[Dererk]

tags 867736 +unreproducible +moreinfo

thanks


Hi Will.

I'm unable to reproduce the mentioned behavior. Just to go through it
step-by-step on this, what do you get at the end of the process?

$  mkdir ~/.config/fbpanel && cp /usr/share/fbpanel/default
~/.config/fbpanel/default

$  fbpanel


Cheers,

Dererk


On 08/07/17 23:50, Will Brokenbourgh wrote:
> Package: fbpanel
> Version: 7.0-3
> Severity: serious
>
> When fbpanel is run with the default config file
> (/usr/share/fbpanel/default) it crashes without displaying any GUI.
>
> The crash output from the terminal follows:
> - - -
> *** Error in `fbpanel': double free or corruption (out):
> 0x558a947cda10 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f4d4469bbcb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f4d446a1f96]
> /lib/x86_64-linux-gnu/libc.so.6(+0x777de)[0x7f4d446a27de]
> /usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7f4d44f38699]
> fbpanel(get_utf8_property_list+0x141)[0x558a94308e71]
> /usr/lib/fbpanel/libtaskbar.so(+0x453c)[0x7f4d3da7f53c]
> /usr/lib/fbpanel/libtaskbar.so(taskbar_constructor+0x4c0)[0x7f4d3da812f0]
> fbpanel(plugin_start+0xd8)[0x558a9430aee8]
> fbpanel(main+0xdbe)[0x558a943041ce]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f4d4464b2b1]
> fbpanel(_start+0x2a)[0x558a9430468a]
> === Memory map: 
> 558a942fb000-558a9431 r-xp  08:24
> 1194991/usr/bin/fbpanel
> 558a9450f000-558a9451 r--p 00014000 08:24
> 1194991/usr/bin/fbpanel
> 558a9451-558a94511000 rw-p 00015000 08:24
> 1194991/usr/bin/fbpanel
> 558a94726000-558a9488d000 rw-p  00:00
> 0  [heap]
> 7f4d3000-7f4d30022000 rw-p  00:00 0
> 7f4d30022000-7f4d3400 ---p  00:00 0
> 7f4d3400-7f4d34021000 rw-p  00:00 0
> 7f4d34021000-7f4d3800 ---p  00:00 0
> 7f4d3800-7f4d38021000 rw-p  00:00 0
> 7f4d38021000-7f4d3c00 ---p  00:00 0
> 7f4d3d643000-7f4d3d659000 r-xp  08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d659000-7f4d3d858000 ---p 00016000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d858000-7f4d3d859000 r--p 00015000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d859000-7f4d3d85a000 rw-p 00016000 08:24
> 3015814/lib/x86_64-linux-gnu/libgcc_s.so.1
> 7f4d3d873000-7f4d3d879000 r-xp  08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3d879000-7f4d3da78000 ---p 6000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da78000-7f4d3da79000 r--p 5000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da79000-7f4d3da7a000 rw-p 6000 08:24 1187724
> /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so
> 7f4d3da7b000-7f4d3da83000 r-xp  08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3da83000-7f4d3dc82000 ---p 8000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc82000-7f4d3dc83000 r--p 7000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc83000-7f4d3dc84000 rw-p 8000 08:24
> 1195014/usr/lib/fbpanel/libtaskbar.so
> 7f4d3dc8b000-7f4d3dc8d000 r-xp  08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3dc8d000-7f4d3de8c000 ---p 2000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de8c000-7f4d3de8d000 r--p 1000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de8d000-7f4d3de8e000 rw-p 2000 08:24
> 1195019/usr/lib/fbpanel/libwincmd.so
> 7f4d3de91000-7f4d3de92000 ---p  00:00 0
> 7f4d3de92000-7f4d3e692000 rw-p  00:00 0
> 7f4d3e692000-7f4d3e693000 ---p  00:00 0
> 7f4d3e693000-7f4d3ee93000 rw-p  00:00 0
> 7f4d3ee93000-7f4d3ee95000 r-xp  08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3ee95000-7f4d3f094000 ---p 2000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f094000-7f4d3f095000 r--p 1000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f095000-7f4d3f096000 rw-p 2000 08:24
> 3020637/lib/x86_64-linux-gnu/libutil-2.24.so
> 7f4d3f0b3000-7f4d3f0e9000 r-xp  08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f0e9000-7f4d3f2e9000 ---p 00036000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f2e9000-7f4d3f2ef000 r--p 00036000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 7f4d3f2ef000-7f4d3f2f rw-p 0003c000 08:24 1317789
> /usr/lib/x86_64-linux-gnu/gvfs/libgvfscommon.so
> 

Bug#750946: libhtml-html5-parser-perl: UTF-8 character breaks parse_file

[gregor herrmann]

On Mon, 07 Aug 2017 08:48:36 -0700, Gregory Williams wrote:

> On Aug 7, 2017, at 8:26 AM, gregor herrmann  wrote:
> > This looks indeed much better than my crude workarounds, thanks for
> > that!
> > Do you think you can take this up with upstream?
> Yes, I think Kjetil and I can work on getting this merged upstream.

Aweseome, thank you!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: affects 871190

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 871190 + ejabberd
Bug #871190 [src:erlang-p1-oauth2] erlang-p1-oauth2: FTBFS: dh_auto_test: make 
--no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test 
returned exit code 2
Added indication that 871190 affects ejabberd
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#869938: Raising severity to serious since g-s-d 3.24 has been uploaded to unstable

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 869938 +pending
Bug #869938 [afterstep] afterstep: Adapt to gnome-settings-daemon 3.24
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
869938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#869938: Raising severity to serious since g-s-d 3.24 has been uploaded to unstable

[Robert Luberda]

Jeremy Bicha pisze:
> Control: severity -1 serious
> 
> gnome-settings-daemon 3.24 has been uploaded to unstable. We intend to
> NMU your package today so that the transition is not delayed.

I have the package ready, I will upload it shortly.


Regards,
robert

Bug#853513: libvigraimpex: ftbfs with GCC-7

[Daniel Stender]

On 07.08.2017 20:26, Matthias Klose wrote:
> Control: tags -1 + patch
> 
> patch at
> http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

Great! I'll take care of it shortly.

DS

-- 
4096R/DF5182C8 (sten...@debian.org)
http://www.danielstender.com/

Bug#871409: libio-socket-ssl-perl: FTBFS: t/protocol_version.t failure

[Niko Tyni]

Package: libio-socket-ssl-perl
Version: 2.049-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net:

 https://ci.debian.net/packages/libi/libio-socket-ssl-perl/unstable/amd64/

this package fails to build on current sid/amd64. debci.log indicates
this is fallout from openssl disabling TLS 1.0 and 1.1 recently:

 -openssl 1.1.0f-3
 +openssl 1.1.0f-4

See https://lists.debian.org/debian-devel-announce/2017/08/msg4.html

>From the build log:


  # looks like OpenSSL was compiled without SSLv3 support
  
  #   Failed test 'accept TLSv1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2:!TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept TLSv1_1'
  #   at t/protocol_version.t line 125.
  
  #   Failed test 'accept SSLv23:!TLSv1_2'
  #   at t/protocol_version.t line 125.
  # Looks like you failed 4 tests of 7.
  t/protocol_version.t .. 
  ok 1 - accept SSLv23 with any, got TLSv1_2
  not ok 2 - accept TLSv1
  not ok 3 - accept SSLv23:!TLSv1_2:!TLSv1_1
  not ok 4 - accept TLSv1_1
  not ok 5 - accept SSLv23:!TLSv1_2
  ok 6 - accept TLSv1_2 with TLSv1_2
  ok 7 - accept SSLv23 with TLSv1_2
  1..7
  Dubious, test returned 4 (wstat 1024, 0x400)
  Failed 4/7 subtests 
  [...]
  Test Summary Report
  ---
  t/protocol_version.t(Wstat: 1024 Tests: 7 Failed: 4)
Failed tests:  2-5
Non-zero exit status: 4
  t/sessions.t(Wstat: 256 Tests: 11 Failed: 1)
Failed test:  10
Non-zero exit status: 1
Parse errors: Bad plan.  You planned 35 tests but ran 11.
  Files=36, Tests=747, 42 wallclock secs ( 0.27 usr  0.04 sys +  7.04 cusr  
0.73 csys =  8.08 CPU)
  Result: FAIL
 
-- 
Niko Tyni   nt...@debian.org

Processed: Re: Bug#871371: singularity-container: FTBFS: help2man: can't get `--version' info from /tmp/tmp.YU5T8oOc4W/run-singularity

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 871371 important
Bug #871371 [src:singularity-container] singularity-container: FTBFS: help2man: 
can't get `--version' info from /tmp/tmp.YU5T8oOc4W/run-singularity
Severity set to 'important' from 'serious'
> tags 871371 + unreproducible
Bug #871371 [src:singularity-container] singularity-container: FTBFS: help2man: 
can't get `--version' info from /tmp/tmp.YU5T8oOc4W/run-singularity
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
871371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871371: singularity-container: FTBFS: help2man: can't get `--version' info from /tmp/tmp.YU5T8oOc4W/run-singularity

[Yaroslav Halchenko]

severity 871371 important
tags 871371 + unreproducible
thanks

Ran rebuild which succeeded just fine on up to date sid for both amd64
and i386 (binary only)

Would need to be able to reproduce to figure out WTF

On Mon, 07 Aug 2017, Lucas Nussbaum wrote:

> Source: singularity-container
> Version: 2.3.1-1
> Severity: serious
> Tags: buster sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170807 qa-ftbfs
> Justification: FTBFS on amd64

> Hi,

> During a rebuild of all packages in sid, your package failed to build on
> amd64.

> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > : # Very sloppy man pages for now
> > debian/generate_manpages debian/singularity-container
> > help2man: can't get `--version' info from 
> > /tmp/tmp.YU5T8oOc4W/run-singularity
> > Try `--no-discard-stderr' if option outputs to stderr
> > debian/rules:21: recipe for target 'override_dh_installman' failed
> > make[1]: *** [override_dh_installman] Error 1

> The full build log is available from:
>
> http://aws-logs.debian.net/2017/08/07/singularity-container_2.3.1-1_unstable.log

> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.


-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#869986: [Debian-ha-maintainers] Bug#869986: Bug#869986: pacemaker FTBFS: missing symbols

[Ferenc Wágner]

Valentin Vidic  writes:

> Right, the upstream is having problems with libqb, but maybe they don't
> see the problem with pacemaker libs if they are not checking the
> exported symbols.

There's no problem with the Pacemaker libs, the "missing" symbols are a
manifestation of the binutils incompatibility in the libqb headers.

> Do you know if these start/stop symbols were used anywhere or it would
> be safe to drop them from the pacemaker libs?

They are not used explicitly, but the bug report you found mentions
silent loss of log messages, let's not paper over that.
-- 
Feri

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Drew Parsons]

On Mon, 2017-08-07 at 17:44 +, Mattia Rizzolo wrote:
> 
> > dolfin 2017.1 is in the NEW queue, so that upgrade will handle this
> > bug.
> 
> Is the binary you uploaded built with gcc-7?  Otherwise that would
> not fix this bug.

It's been sitting in NEW for a month, so it would have been gcc-6 I
think.  But the upload is to experimental.  I figure we can ignore
anything in experimental, the symbols will get reset for the new ABI
when we drop it into unstable.

Drew

Processed: Re: libvigraimpex: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #853513 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-7
Added tag(s) patch.

-- 
853513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853513: libvigraimpex: ftbfs with GCC-7

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/332312910/libvigraimpex_1.10.0+git20160211.167be93+dfsg-2build3_1.10.0+git20160211.167be93+dfsg-2ubuntu1.diff.gz

Bug#871405: gdm3: russian secondary languaje not displayed if not default

[PICCORO McKAY Lenz]

Package: gdm3
Severity: serious
Tags: l10n
Justification: causes serious data loss

gdm3 has a terribe bug: does not show russian languaje if are
secondary or as alternative

i installed debian 8 from scrach in spanish and then adde russian
languaje locale as second optionaly..

the iso used was DVD flavor with GDM3 as display manager..
NOTE: all the es_XX, ru_XX and en_XX locales where are generated
correctly i mans ALL including ucranian russian UTF8 and non UTF8
locales

then the screen of the GDM3 are showed, only englich and spanish are
availables..

restarted and again try to login and only spanish and russian are availables..

install the lightdm (due now debians only offerts NOTHING display
managers such GMD3 and LIGHTY)

then now russian are available in languaje choices only if lightdm are
set as default

but are not saved for specific users as defaul languje, so all users
if choose another languaje optionally to use, does not saved as user
default.. like DEbian squeeze does perfectly and debian lenny!


-- System Information:
Debian Release: 8.5
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


Versions of packages gdm3 depends on:
ii  accountsservice0.6.37-3+b1
ii  adduser3.113+nmu3
ii  dconf-cli  0.22.0-1
ii  dconf-gsettings-backend0.22.0-1
ii  debconf [debconf-2.0]  1.5.56
ii  gir1.2-gdm33.14.1-6
ii  gnome-session [x-session-manager]  3.14.0-2
ii  gnome-session-bin  3.14.0-2
ii  gnome-settings-daemon  3.14.2-3
ii  gnome-shell3.14.2-3+b1
ii  gnome-terminal [x-terminal-emulator]   3.14.1-1
ii  gsettings-desktop-schemas  3.14.1-1
ii  kde-window-manager [x-window-manager]  4:4.11.13-2
ii  libaccountsservice00.6.37-3+b1
ii  libaudit1  1:2.4-1+b1
ii  libc6  2.19-17
ii  libcanberra-gtk3-0 0.30-2.1
ii  libcanberra0   0.30-2.1
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgdm13.14.1-6
ii  libglib2.0-0   2.42.1-1
ii  libglib2.0-bin 2.42.1-1
ii  libgtk-3-0 3.14.5-1
ii  libpam-modules 1.1.8-3.1
ii  libpam-runtime 1.1.8-3.1
ii  libpam-systemd 215-14
ii  libpam0g   1.1.8-3.1
ii  librsvg2-common2.40.5-1
ii  libselinux12.3-2
ii  libsystemd0215-14
ii  libwrap0   7.6.q-25
ii  libx11-6   2:1.6.2-3
ii  libxau61:1.0.8-1
ii  libxdmcp6  1:1.1.1-1+b1
ii  libxrandr2 2:1.4.2-1+b1
ii  lsb-base   4.1+Debian13+nmu1
ii  metacity [x-window-manager]1:3.14.3-1
ii  mutter [x-window-manager]  3.14.2-1
ii  policykit-10.105-8
ii  ucf3.0030
ii  x11-common 1:7.7+7
ii  x11-xserver-utils  7.7+3+b1
ii  xterm [x-terminal-emulator]312-2

Versions of packages gdm3 recommends:
ii  at-spi2-core   2.14.0-1
ii  desktop-base   8.0.2
ii  gnome-icon-theme   3.12.0-1
ii  gnome-icon-theme-symbolic  3.12.0-1
ii  x11-xkb-utils  7.7+1
ii  xserver-xephyr 2:1.16.4-1
ii  xserver-xorg   1:7.7+7
ii  zenity 3.14.0-1

Versions of packages gdm3 suggests:
ii  gnome-orca3.14.0-4
ii  libpam-gnome-keyring  3.14.0-1+b1

-- Configuration Files:
/etc/gdm3/daemon.conf changed [not included]

-- debconf information:
  gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: kdm


Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 871070 https://github.com/Microsoft/GSL/issues/525
Bug #871070 [src:ms-gsl] ms-gsl: FTBFS: multi_span:1191:57: error: conversion 
to 'long unsigned int' from 'long int' may change the sign of the result 
[-Werror=sign-conversion]
Set Bug forwarded-to-address to 'https://github.com/Microsoft/GSL/issues/525'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
871070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#870796: [Dev-luatex] [tex-live] segfault on build-testing luatex

[luigi scarso]

On Mon, Aug 7, 2017 at 4:17 PM, Norbert Preining  wrote:
>> Related to gcc-7.1?
>> http://tug.org/pipermail/tex-live/2017-June/040192.html
>
> Ahh, sounds reasonable .



OK I see it with gcc 7.1 and -O3 , but not with -O0

It happens when luatex exits and closes the state L;
the garbage collector calls the pending finalizers and luaffi fails.
I am working on the luaffi code,  it could be that will aply the patch.


(gdb) fr 1
#1  check_cdata (L=L@entry=0x30e8b90, idx=idx@entry=1,
ct=ct@entry=0x7fff8b5aed30) at
../../../source/texk/web2c/luatexdir/luaffi/ctype.c:266
266void* p = to_cdata(L, idx, ct);
(gdb) fr 2
#2  0x006845d5 in cdata_gc (L=0x30e8b90) at
../../../source/texk/web2c/luatexdir/luaffi/ffi.c:1429
1429check_cdata(L, 1, );
(gdb) fr 3
#3  0x006a9ea8 in luaD_precall (L=L@entry=0x30e8b90,
func=, nresults=0) at
../../../source/libs/lua52/lua52-src/src/ldo.c:319
319  n = (*f)(L);  /* do the actual call */
(gdb) fr 4
#4  0x006aa582 in luaD_call (L=0x30e8b90, func=, nResults=, allowyield=) at
../../../source/libs/lua52/lua52-src/src/ldo.c:401
401  if (!luaD_precall(L, func, nResults))  /* is a Lua function? */
(gdb) fr 5
#5  0x006a9599 in luaD_rawrunprotected (L=0x30e8b90,
f=0x6abc30 , ud=0x0) at
../../../source/libs/lua52/lua52-src/src/ldo.c:131
131  LUAI_TRY(L, ,
(gdb) fr 6
#6  0x006aa933 in luaD_pcall (L=L@entry=0x30e8b90,
func=func@entry=0x6abc30 , u=u@entry=0x0, old_top=896,
ef=ef@entry=0) at ../../../source/libs/lua52/lua52-src/src/ldo.c:603
603  status = luaD_rawrunprotected(L, func, u);
(gdb) fr 7
#7  0x006ad750 in GCTM (propagateerrors=0, L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lgc.c:824
824status = luaD_pcall(L, dothecall, NULL, savestack(L, L->top - 2), 0);
(gdb) fr 8
#8  callallpendingfinalizers (propagateerrors=,
L=) at
../../../source/libs/lua52/lua52-src/src/lgc.c:978
978GCTM(L, propagateerrors);
(gdb) fr 9
#9  luaC_freeallobjects (L=L@entry=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lgc.c:988
988  callallpendingfinalizers(L, 0);
(gdb) fr 10
#10 0x006b7677 in close_state (L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lstate.c:226
226  luaC_freeallobjects(L);  /* collect all objects */
(gdb) fr 11
#11 lua_close (L=0x30e8b90) at
../../../source/libs/lua52/lua52-src/src/lstate.c:320
320  close_state(L);
(gdb) fr  12
#12 0x00476ff6 in do_final_end () at
../../../source/texk/web2c/luatexdir/tex/errors.w:223
223lua_close(Luas); /* new per 0.99 */
(gdb) fr 13
#13 0x00447abe in main (ac=, av=) at ../../../source/texk/web2c/luatexdir/luatex.c:582
582main_body();

-- 
luigi

Processed: Adjust the severity (program is broken, causes other package to FTBFS)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 826465 serious
Bug #826465 [texlive-latex-recommended] texlive-latex-recommended: Unescaped 
left brace in regex is deprecated
Bug #871345 [texlive-latex-recommended] kimwitu-doc: FTBFS: Unescaped left 
brace in regex is illegal here in regex; marked by <-- HERE in m/\\UseRGB{ <-- 
HERE (\d+)}\\\s*\d+\s*R/ at /usr/bin/thumbpdf line 1456.
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
826465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826465
871345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#871392: marked as done (miaviewit: FTBFS: build-dependency not installable: libmia-2.4-dev (>= 2.4.4))

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871392,
regarding miaviewit: FTBFS: build-dependency not installable: libmia-2.4-dev 
(>= 2.4.4)
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.)


-- 
871392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871392
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: miaviewit
Version: 1.0.5-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9.0.0), autotools-dev, libmia-2.4-dev (>= 
> 2.4.4), libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, 
> libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev
> Filtered Build-Depends: debhelper (>= 9.0.0), autotools-dev, libmia-2.4-dev 
> (>= 2.4.4), libgle3-dev, libgtkglextmm-x11-1.2-dev, libboost-thread-dev, 
> libgtkmm-2.4-dev, libxml++2.6-dev, libvistaio-dev
> dpkg-deb: building package 'sbuild-build-depends-miaviewit-dummy' in 
> '/<>/resolver-WxzSAH/apt_archive/sbuild-build-depends-miaviewit-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-miaviewit-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-WxzSAH/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-WxzSAH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-WxzSAH/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-WxzSAH/apt_archive ./ Sources [566 B]
> Get:5 copy:/<>/resolver-WxzSAH/apt_archive ./ Packages [648 B]
> Fetched 2177 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install miaviewit build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-miaviewit-dummy : Depends: libmia-2.4-dev (>= 2.4.4) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/miaviewit_1.0.5-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871391: marked as done (pygpiv: FTBFS: build-dependency not installable: libgpiv3-dev)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871391,
regarding pygpiv: FTBFS: build-dependency not installable: libgpiv3-dev
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.)


-- 
871391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygpiv
Version: 2.0.0-4.2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), python-all-dev 
> (>= 2.6.6-3~), swig, libglib2.0-dev, libfftw3-dev, libgsl0-dev, libhdf5-dev 
> (>= 1.8.8), libnetpbm10-dev, libpng-dev, libgpiv3-dev
> Filtered Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), 
> python-all-dev (>= 2.6.6-3~), swig, libglib2.0-dev, libfftw3-dev, 
> libgsl0-dev, libhdf5-dev (>= 1.8.8), libnetpbm10-dev, libpng-dev, libgpiv3-dev
> dpkg-deb: building package 'sbuild-build-depends-pygpiv-dummy' in 
> '/<>/resolver-xp8Ktu/apt_archive/sbuild-build-depends-pygpiv-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pygpiv-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-xp8Ktu/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-xp8Ktu/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-xp8Ktu/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-xp8Ktu/apt_archive ./ Sources [569 B]
> Get:5 copy:/<>/resolver-xp8Ktu/apt_archive ./ Packages [649 B]
> Fetched 2181 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pygpiv build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-pygpiv-dummy : Depends: libgpiv3-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/pygpiv_2.0.0-4.2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871388: marked as done (gqrx-sdr: FTBFS: unsatisfiable build-dependency: libgsl0-dev (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871388,
regarding gqrx-sdr: FTBFS: unsatisfiable build-dependency: libgsl0-dev 
(versioned dep on a virtual pkg?)
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.)


-- 
871388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gqrx-sdr
Version: 2.6-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake (>= 2.8), debhelper (>= 9), gnuradio-dev (>> 
> 3.7.10), gr-osmosdr (>> 0.1.4-11), libasound2-dev, libboost-dev, 
> libboost-program-options-dev, libboost-system-dev, libfftw3-dev, libgsl0-dev, 
> liblog4cpp5-dev, libpulse-dev, libqt5svg5-dev, libsoapysdr-dev, libudev-dev, 
> pkg-config, qt5-qmake, qtbase5-dev, qtbase5-dev-tools, qtchooser
> Filtered Build-Depends: cmake (>= 2.8), debhelper (>= 9), gnuradio-dev (>> 
> 3.7.10), gr-osmosdr (>> 0.1.4-11), libasound2-dev, libboost-dev, 
> libboost-program-options-dev, libboost-system-dev, libfftw3-dev, libgsl0-dev, 
> liblog4cpp5-dev, libpulse-dev, libqt5svg5-dev, libsoapysdr-dev, libudev-dev, 
> pkg-config, qt5-qmake, qtbase5-dev, qtbase5-dev-tools, qtchooser
> dpkg-deb: building package 'sbuild-build-depends-gqrx-sdr-dummy' in 
> '/<>/resolver-BOjegu/apt_archive/sbuild-build-depends-gqrx-sdr-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-gqrx-sdr-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-BOjegu/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-BOjegu/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-BOjegu/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-BOjegu/apt_archive ./ Sources [653 B]
> Get:5 copy:/<>/resolver-BOjegu/apt_archive ./ Packages [722 B]
> Fetched 2338 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install gqrx-sdr build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-gqrx-sdr-dummy : Depends: libgsl0-dev
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/gqrx-sdr_2.6-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871389: marked as done (altree: FTBFS: build-dependency not installable: libmath-tamuanova-perl)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871389,
regarding altree: FTBFS: build-dependency not installable: 
libmath-tamuanova-perl
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.)


-- 
871389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: altree
Version: 1.3.1-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: bash-completion, debhelper (>= 9), latex-make, 
> ghostscript, texlive-lang-french, texlive-latex-extra, 
> texlive-latex-recommended, texlive-fonts-recommended, libmath-tamuanova-perl, 
> libgsl-dev, libatlas-base-dev, libtest-deep-perl
> Filtered Build-Depends: bash-completion, debhelper (>= 9), latex-make, 
> ghostscript, texlive-lang-french, texlive-latex-extra, 
> texlive-latex-recommended, texlive-fonts-recommended, libmath-tamuanova-perl, 
> libgsl-dev, libatlas-base-dev, libtest-deep-perl
> dpkg-deb: building package 'sbuild-build-depends-altree-dummy' in 
> '/<>/resolver-rsVmG6/apt_archive/sbuild-build-depends-altree-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-altree-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-rsVmG6/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-rsVmG6/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-rsVmG6/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-rsVmG6/apt_archive ./ Sources [591 B]
> Get:5 copy:/<>/resolver-rsVmG6/apt_archive ./ Packages [676 B]
> Fetched 2230 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install altree build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-altree-dummy : Depends: libmath-tamuanova-perl but it 
> is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/altree_1.3.1-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871382: marked as done (3depict: FTBFS: unsatisfiable build-dependencies: libgsl-dev, libmgl-dev (>= 2.0))

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871382,
regarding 3depict: FTBFS: unsatisfiable build-dependencies: libgsl-dev, 
libmgl-dev (>= 2.0)
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.)


-- 
871382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 3depict
Version: 0.0.19-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-autoreconf (>= 9), dpkg-dev (>= 
> 1.16.1~), libgl1-mesa-dev | libgl-dev, libpng-dev | libpng15-dev, 
> libqhull-dev, libwxgtk3.0-dev, libgsl-dev, libftgl-dev, libxml2-dev, 
> libmgl-dev (>= 2.0), libvigraimpex-dev, automake, autotools-dev, pkg-config
> Filtered Build-Depends: debhelper (>= 9), dh-autoreconf (>= 9), dpkg-dev (>= 
> 1.16.1~), libgl1-mesa-dev, libpng-dev, libqhull-dev, libwxgtk3.0-dev, 
> libgsl-dev, libftgl-dev, libxml2-dev, libmgl-dev (>= 2.0), libvigraimpex-dev, 
> automake, autotools-dev, pkg-config
> dpkg-deb: building package 'sbuild-build-depends-3depict-dummy' in 
> '/<>/resolver-YpzjUj/apt_archive/sbuild-build-depends-3depict-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-3depict-dummy 
> sbuild-build-depends-core-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-YpzjUj/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-YpzjUj/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-YpzjUj/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-YpzjUj/apt_archive ./ Sources [601 B]
> Get:5 copy:/<>/resolver-YpzjUj/apt_archive ./ Packages [666 B]
> Fetched 2230 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install 3depict build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-3depict-dummy : Depends: libgsl-dev but it is not going 
> to be installed
>   Depends: libmgl-dev (>= 2.0) but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/3depict_0.0.19-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871379: marked as done (libpdl-stats-perl: FTBFS: build-dependency not installable: pdl (>= 1:2.016))

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871379,
regarding libpdl-stats-perl: FTBFS: build-dependency not installable: pdl (>= 
1:2.016)
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.)


-- 
871379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpdl-stats-perl
Version: 0.75-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9.20120312~), libgsl-dev, pdl (>= 
> 1:2.016), perl
> Filtered Build-Depends: debhelper (>= 9.20120312~), libgsl-dev, pdl (>= 
> 1:2.016), perl
> dpkg-deb: building package 'sbuild-build-depends-libpdl-stats-perl-dummy' in 
> '/<>/resolver-vUSNcr/apt_archive/sbuild-build-depends-libpdl-stats-perl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-libpdl-stats-perl-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-vUSNcr/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-vUSNcr/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-vUSNcr/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-vUSNcr/apt_archive ./ Sources [524 B]
> Get:5 copy:/<>/resolver-vUSNcr/apt_archive ./ Packages [605 B]
> Fetched 2092 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install libpdl-stats-perl build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libpdl-stats-perl-dummy : Depends: pdl (>= 1:2.016) but 
> it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/libpdl-stats-perl_0.75-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871383: marked as done (ruby-gsl: FTBFS: build-dependency not installable: libtamuanova-dev)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871383,
regarding ruby-gsl: FTBFS: build-dependency not installable: libtamuanova-dev
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.)


-- 
871383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gsl
Version: 2.1.0.1+dfsg1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9~), gem2deb, libgsl-dev (>= 2.0), 
> libtamuanova-dev, plotutils, quilt, ruby-narray
> Filtered Build-Depends: debhelper (>= 9~), gem2deb, libgsl-dev (>= 2.0), 
> libtamuanova-dev, plotutils, quilt, ruby-narray
> dpkg-deb: building package 'sbuild-build-depends-ruby-gsl-dummy' in 
> '/<>/resolver-ueqn3b/apt_archive/sbuild-build-depends-ruby-gsl-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-ruby-gsl-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-ueqn3b/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-ueqn3b/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-ueqn3b/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-ueqn3b/apt_archive ./ Sources [540 B]
> Get:5 copy:/<>/resolver-ueqn3b/apt_archive ./ Packages [622 B]
> Fetched 2125 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install ruby-gsl build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-ruby-gsl-dummy : Depends: libtamuanova-dev but it is 
> not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/ruby-gsl_2.1.0.1+dfsg1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871381: marked as done (gyoto: FTBFS: build-dependency not installable: liblorene-dev)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871381,
regarding gyoto: FTBFS: build-dependency not installable: liblorene-dev
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.)


-- 
871381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gyoto
Version: 1.2.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9~), yorick-dev, yorick-yutils, 
> libxerces-c-dev, libcfitsio-dev, libudunits2-dev, automake, libboost-dev (>= 
> 1.53.1), libboost-mpi-dev, dh-autoreconf, mpi-default-dev, dh-python, 
> python-all-dev (>= 2.6.6-3~), python-setuptools, python3-all-dev, 
> python3-setuptools, swig3.0, python-numpy, python3-numpy, doxygen, dh-exec 
> (>= 0.3), pkg-config, liblorene-dev, lorene-codes-src, gfortran, 
> doxygen-latex, texlive-bibtex-extra, texlive-latex-base, texlive-lang-french, 
> tipa
> Filtered Build-Depends: debhelper (>= 9~), yorick-dev, yorick-yutils, 
> libxerces-c-dev, libcfitsio-dev, libudunits2-dev, automake, libboost-dev (>= 
> 1.53.1), libboost-mpi-dev, dh-autoreconf, mpi-default-dev, dh-python, 
> python-all-dev (>= 2.6.6-3~), python-setuptools, python3-all-dev, 
> python3-setuptools, swig3.0, python-numpy, python3-numpy, doxygen, dh-exec 
> (>= 0.3), pkg-config, liblorene-dev, lorene-codes-src, gfortran, 
> doxygen-latex, texlive-bibtex-extra, texlive-latex-base, texlive-lang-french, 
> tipa
> dpkg-deb: building package 'sbuild-build-depends-gyoto-dummy' in 
> '/<>/resolver-2D0FNP/apt_archive/sbuild-build-depends-gyoto-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-gyoto-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-2D0FNP/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-2D0FNP/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-2D0FNP/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-2D0FNP/apt_archive ./ Sources [717 B]
> Get:5 copy:/<>/resolver-2D0FNP/apt_archive ./ Packages [786 B]
> Fetched 2466 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install gyoto build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-gyoto-dummy : Depends: liblorene-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/gyoto_1.2.0-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

Bug#871377: marked as done (pymia: FTBFS: build-dependency not installable: libmia-2.4-dev)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871377,
regarding pymia: FTBFS: build-dependency not installable: libmia-2.4-dev
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.)


-- 
871377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871377
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymia
Version: 0.1.9-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), pkg-config, python-all-dev, 
> python3-all-dev, python-numpy, python3-numpy, python-setuptools, 
> python3-setuptools, libmia-2.4-dev
> Filtered Build-Depends: debhelper (>= 9), pkg-config, python-all-dev, 
> python3-all-dev, python-numpy, python3-numpy, python-setuptools, 
> python3-setuptools, libmia-2.4-dev
> dpkg-deb: building package 'sbuild-build-depends-pymia-dummy' in 
> '/<>/resolver-mI6weo/apt_archive/sbuild-build-depends-pymia-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-pymia-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-mI6weo/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-mI6weo/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-mI6weo/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-mI6weo/apt_archive ./ Sources [536 B]
> Get:5 copy:/<>/resolver-mI6weo/apt_archive ./ Packages [620 B]
> Fetched 2119 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install pymia build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-pymia-dummy : Depends: libmia-2.4-dev but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/pymia_0.1.9-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Bug#871376: marked as done (qtiplot: FTBFS: build-dependency not installable: libtamuanova-dev (>= 0.2-4))

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 20:46:19 +0300
with message-id <20170807174619.pp4t3r6tjcs6va3o@localhost>
and subject line Closing bugs related to temporary libgsl transition problems
has caused the Debian Bug report #871376,
regarding qtiplot: FTBFS: build-dependency not installable: libtamuanova-dev 
(>= 0.2-4)
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.)


-- 
871376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtiplot
Version: 0.9.8.9-15
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dblatex, docbook-utils, doxygen, 
> libgsl-dev, zlib1g-dev, libpng-dev, libgl2ps-dev, libjs-jquery, 
> liborigin2-dev, libmuparser-dev, python-all-dev, python-qt4, python-qt4-dev, 
> python-sip-dev, libqt4-opengl-dev, libboost-thread-dev, libboost-system-dev, 
> libqtassistantclient-dev, libalglib-dev (>= 3.9.0), libtamuanova-dev (>= 
> 0.2-4), libqtexengine-dev, texlive-lang-european, texlive-lang-italian, 
> imagemagick
> Filtered Build-Depends: debhelper (>= 9), dblatex, docbook-utils, doxygen, 
> libgsl-dev, zlib1g-dev, libpng-dev, libgl2ps-dev, libjs-jquery, 
> liborigin2-dev, libmuparser-dev, python-all-dev, python-qt4, python-qt4-dev, 
> python-sip-dev, libqt4-opengl-dev, libboost-thread-dev, libboost-system-dev, 
> libqtassistantclient-dev, libalglib-dev (>= 3.9.0), libtamuanova-dev (>= 
> 0.2-4), libqtexengine-dev, texlive-lang-european, texlive-lang-italian, 
> imagemagick
> dpkg-deb: building package 'sbuild-build-depends-qtiplot-dummy' in 
> '/<>/resolver-Q9Zily/apt_archive/sbuild-build-depends-qtiplot-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-qtiplot-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-Q9Zily/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-Q9Zily/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-Q9Zily/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-Q9Zily/apt_archive ./ Sources [682 B]
> Get:5 copy:/<>/resolver-Q9Zily/apt_archive ./ Packages [761 B]
> Fetched 2406 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install qtiplot build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-qtiplot-dummy : Depends: libtamuanova-dev (>= 0.2-4) 
> but it is not going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/qtiplot_0.9.8.9-15_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
libgsl currently undergoes a (very chaotic) library transition.

These issues are caused by packages temporarily uninstallable during
the transition.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed--- End Message ---

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 871380 src:qtwebengine-opensource-src
Bug #871380 [src:algobox] algobox: FTBFS: build-dependency not installable: 
qtwebengine5-dev
Bug reassigned from package 'src:algobox' to 'src:qtwebengine-opensource-src'.
No longer marked as found in versions algobox/1.0.1+dfsg-1.
Ignoring request to alter fixed versions of bug #871380 to the same values 
previously set
> reassign 871387 src:qtwebengine-opensource-src
Bug #871387 [src:qupzilla] qupzilla: FTBFS: build-dependency not installable: 
qtwebengine5-dev
Bug reassigned from package 'src:qupzilla' to 'src:qtwebengine-opensource-src'.
No longer marked as found in versions qupzilla/2.1.2~dfsg1-2.
Ignoring request to alter fixed versions of bug #871387 to the same values 
previously set
> forcemerge 869008 871380 871387
Bug #869008 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871387 [src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency 
not installable: qtwebengine5-dev
Added indication that 871387 affects src:pyqt5
Marked as found in versions qtwebengine-opensource-src/5.9.0+dfsg-1.
Bug #871380 [src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency 
not installable: qtwebengine5-dev
Added indication that 871380 affects src:pyqt5
Marked as found in versions qtwebengine-opensource-src/5.9.0+dfsg-1.
Bug #869016 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Merged 869008 869016 871064 871380 871387
> affects 869008 src:algobox src:qupzilla
Bug #869008 [src:qtwebengine-opensource-src] qtwebengine-opensource-src: FTBFS: 
unsatisfiable build-dependencies: libqt5opengl5-dev (>= 5.9.0~), 
libqt5webchannel5-dev (>= 5.9.0~), libqt5xmlpatterns5-dev (>= 5.9.0~), 
qtbase5-private-dev (>= 5.9.0~), qtdeclarative5-private-dev (>= 5.9.0~), 
qtscript5-private-dev (>= 5.9.0~), libqt5sql5-sqlite (>= 5.9.0~), 
qtbase5-doc-html (>= 5.9.0~), qttools5-dev-tools (>= 5.9.0~)
Bug #869016 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871064 [src:qtwebengine-opensource-src] pyqt5: FTBFS: build-dependency not 
installable: qtwebengine5-dev (>= 5.7.1+dfsg-3~)
Bug #871380 [src:qtwebengine-opensource-src] algobox: FTBFS: build-dependency 
not installable: qtwebengine5-dev
Bug #871387 [src:qtwebengine-opensource-src] qupzilla: FTBFS: build-dependency 
not installable: qtwebengine5-dev
Added indication that 869008 affects src:algobox and src:qupzilla
Added indication that 869016 affects src:algobox and src:qupzilla
Added indication that 871064 affects src:algobox and src:qupzilla
Added indication that 871380 affects src:algobox and src:qupzilla
Added indication that 871387 affects src:algobox and src:qupzilla
> reassign 871327 texlive-latex-recommended
Bug #871327 [src:kicad] kicad: FTBFS: a2x: ERROR: "dblatex" -t pdf -p 
"/etc/asciidoc/dblatex/asciidoc-dblatex.xsl" -s 
"/etc/asciidoc/dblatex/asciidoc-dblatex.sty" -P latex.output.revhistory=0 -P 
doc.publisher.show=0 -s 
/<>/kicad-4.0.6+dfsg1/doc/CMakeSupport/pdf-cover-dblatex.sty -b xetex 
-p 
/<>/kicad-4.0.6+dfsg1/doc/src/gerbview/../../xsl/dblatex-pdf-ja.xsl 
-o 
/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.pdf  
"/<>/kicad-4.0.6+dfsg1/debian/build/doc/src/gerbview/ja/gerbview.xml" 
returned non-zero exit status 1
Bug reassigned from package 'src:kicad' to 'texlive-latex-recommended'.
No longer marked as found in versions kicad/4.0.6+dfsg1-1.
Ignoring request to alter fixed versions of bug #871327 to the same values 
previously set
> reassign 871067 texlive-latex-recommended
Bug #871067 [src:developers-reference] developers-reference: FTBFS: Error: 
xelatex compilation failed
Bug reassigned from package 'src:developers-reference' to 
'texlive-latex-recommended'.
No longer marked as found in versions developers-reference/3.4.18.
Ignoring request to alter fixed versions of bug #871067 to the same values 
previously set
> forcemerge 870280 871327 871067
Bug #870280 [texlive-latex-recommended] xelatex: Undefined control sequence 
\l__xeCJK_listings_letter_bool
Bug #871092 [texlive-latex-recommended] maint-guide: FTBFS: dh_install: missing 
files, aborting

Bug#871279: libdolfin2016.2: requires rebuild against GCC 7 and symbols/shlibs bump

[Mattia Rizzolo]

On Mon, 7 Aug 2017, 6:57 p.m. Drew Parsons,  wrote:

> > - If your package is about to be renamed due to an upstream SONAME
> bump,
> >   you do not need to add any special symbols handling.
> >
>
>
> dolfin 2017.1 is in the NEW queue, so that upgrade will handle this
> bug.
>

Is the binary you uploaded built with gcc-7?  Otherwise that would not fix
this bug.

Bug#866696: marked as done (src:python-pyeclib: FTBFS on mips64el due to test failures after rebuild with python3.6)

[Debian Bug Tracking System]

Your message dated Mon, 7 Aug 2017 13:38:30 -0400
with message-id 

Bug#779522: marked as done (jitsi uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #760853,
regarding jitsi uninstallable
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.)


-- 
760853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitsi
Version: 2.4.4997-1.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
I tried installing jitsi but got the following error :-

$ sudo aptitude install jitsi libjitsi-jni
The following NEW packages will be installed:
  jitsi libjitsi-jni{b} 
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.5 MB of archives. After unpacking 48.0 MB will be used.
The following packages have unmet dependencies:
 libjitsi-jni : Depends: libavcodec55 (>= 6:10~beta1~) which is a virtual 
package. or
 libavcodec-extra-55 (>= 6:10.1) which is a virtual 
package.
Depends: libavfilter4 (>= 6:10~beta1~) which is a virtual 
package.
Depends: libavformat55 (>= 6:10~beta1~) which is a virtual 
package.
Depends: libavutil53 (>= 6:10~beta1~) which is a virtual 
package.
Depends: libswscale2 (>= 6:10~beta1~) which is a virtual 
package.
The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) jitsi [Not Installed]  
2) libjitsi-jni [Not Installed]   

It can be seen that most of the libav libraries have moved on. 

For e.g. see the info. about libavcodec 

$ aptitude search libavcodec
p   libavcodec-dev  - 
Development files for libavcodec  
p   libavcodec-extra- Libav 
codec library (additional codecs meta-package)  
i   libavcodec-extra-56 - Libav 
codec library (additional codecs)   
p   libavcodec-ffmpeg-dev   - FFmpeg 
library with de/encoders for audio/video codecs - development files
p   libavcodec-ffmpeg56 - FFmpeg 
library with de/encoders for audio/video codecs - runtime files
p   libavcodec56- Libav 
codec library 

Please fix the bug above.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'testing-updates'), (1, 'experimental'), 
(1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jitsi depends on:
ii  default-jre [java6-runtime]2:1.7-52
ii  libbcprov-java 1.51-1
ii  libcommons-codec-java  1.9-1
ii  libcommons-lang3-java  3.3.2-1
ii  libcommons-logging-java1.2-1
ii  libdbus-java   2.8-5
ii  libdnsjava-java2.1.5-0.1
ii  libfelix-framework-java4.4.0-1
ii  libfelix-main-java 4.4.0-1
ii  libhttpclient-java 4.3.5-2
ii  libhttpcore-java   4.3.3-1
ii  libhttpmime-java   4.3.5-2
ii  libjcalendar-java  1.3.3-3
ii  libjgoodies-forms-java 1.6.0-4
ii  libjmdns-java  3.4.1-2
ii  libjna-java4.1.0-1
ii  libjson-simple-java1.1.1-2
ii  libjzlib-java  1.1.3-1
ii  liblaf-widget-java 4.3-2
ii  liblog4j1.2-java   1.2.17-5
ii  libmac-widgets-java0.10.0+svn416-dfsg1-1
ii  libunixsocket-java 0.7.3-1
ii  libxpp3-java   1.1.4c-2
ii  openjdk-7-jre [java6-runtime]  7u75-2.5.4-2

jitsi recommends no packages.

jitsi suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using 

Bug#835688: marked as done (python-riemann-client: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:25:31 +
with message-id 
and subject line Bug#871050: Removed package(s) from unstable
has caused the Debian Bug report #835688,
regarding python-riemann-client: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 2.7 returned exit code 13
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.)


-- 
835688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-riemann-client
Version: 6.3.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/command.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2_py3.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/transport.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/riemann_pb2_py2.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> copying riemann_client/client.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/riemann_client
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html 
> # HTML generator
> Running Sphinx v1.4.6
> making output directory...
> loading pickled environment... not yet created
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 3 source files that are out of date
> updating environment: 3 added, 0 changed, 0 removed
> reading sources... [ 33%] index
> reading sources... [ 66%] riemann_client.client
> reading sources... [100%] riemann_client.transport
> 
> README.rst:71: WARNING: Title underline too short.
> 
> Testing (Linux/OSX)
> ---
> README.rst:71: WARNING: Title underline too short.
> 
> Testing (Linux/OSX)
> ---
> /<>/docs/riemann_client.client.rst:4: WARNING: autodoc: failed 
> to import module u'riemann_client.client'; the following exception was raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
> import_object
> __import__(self.modname)
>   File "/<>/riemann_client/client.py", line 27, in 
> import riemann_client.riemann_pb2
>   File "/<>/riemann_client/riemann_pb2.py", line 10, in 
> from riemann_client.riemann_pb2_py2 import (Event, Msg, Query, Attribute)
>   File "/<>/riemann_client/riemann_pb2_py2.py", line 32, in 
> 
> options=None),
>   File "/usr/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 
> 501, in __new__
> _message.Message._CheckCalledFromGeneratedFile()
> TypeError: Descriptors should not be created directly, but only retrieved 
> from their parent.
> /<>/docs/riemann_client.transport.rst:4: WARNING: autodoc: 
> failed to import module u'riemann_client.transport'; the following exception 
> was raised:
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/sphinx/ext/autodoc.py", line 519, in 
> import_object
> __import__(self.modname)
>   File "/<>/riemann_client/transport.py", line 12, in 
> import riemann_client.riemann_pb2
>   File "/<>/riemann_client/riemann_pb2.py", line 10, in 
> from riemann_client.riemann_pb2_py2 import (Event, Msg, Query, Attribute)
>   File "/<>/riemann_client/riemann_pb2_py2.py", line 32, in 
> 
> options=None),
>   File "/usr/lib/python2.7/dist-packages/google/protobuf/descriptor.py", line 
> 501, in __new__
> _message.Message._CheckCalledFromGeneratedFile()
> TypeError: Descriptors should not be created directly, but only retrieved 
> from their parent.
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [ 33%] index
> writing output... [ 66%] riemann_client.client
> writing output... [100%] riemann_client.transport
> 
> generating indices... genindex
> writing additional pages... search
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en) 

Bug#838897: marked as done (jitsi: Replace the glassfish dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #838897,
regarding jitsi: Replace the glassfish dependencies
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.)


-- 
838897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jitsi
Version: 2.5.5313-1
Severity: important

Dear Maintainer,

jitsi still depends on glassfish-activation and glassfish-mail which are going
to be removed. glassfish-activation can be safely removed (the API has been
integrated to the standard JDK) and glassfish-mail should be replaced by 
libmail-java.

Thank you,

Emmanuel Bourg
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#854737: marked as done (CVE-2017-5603)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #854737,
regarding CVE-2017-5603
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.)


-- 
854737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitsi
Severity: grave
Tags: security

Please see http://seclists.org/oss-sec/2017/q1/373

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#789038: marked as done (jitsi uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #760853,
regarding jitsi uninstallable
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.)


-- 
760853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitsi
Version: 2.5.5313-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
I tried installing jitsi but got the following error :-

[$] sudo aptitude install jitsi=2.5.5313-1 jitsi-jni=2.5.5313-1
libjitsi-jni=2.4.4997-1.2 jitsi-common=2.5.5313-1

The following NEW packages will be installed:
  jitsi{b} jitsi-common jitsi-jni libjitsi-jni{b}
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,530 kB of archives. After unpacking 31.9 MB will be used.
The following packages have unmet dependencies:
 libjitsi-jni : Depends: libavcodec55 (>= 6:10~beta1~) which is a
virtual package. or
 libavcodec-extra-55 (>= 6:10.1) which is a
virtual package.
Depends: libavfilter4 (>= 6:10~beta1~) which is a
virtual package.
Depends: libavformat55 (>= 6:10~beta1~) which is a
virtual package.
Depends: libavutil53 (>= 6:10~beta1~) which is a
virtual package.
Depends: libswscale2 (>= 6:10~beta1~) which is a
virtual package.
 jitsi : Depends: libjitsi (>= 415-0) which is a virtual package.
 Depends: libjitsi-jni (>= 415-0) but 2.4.4997-1.2 is to be installed.

I have used the previous bug #779521 to get info. on the various
depends and have shared them of the package.

-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (1,
'experimental'), (1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages jitsi depends on:
ii  default-jre [java6-runtime]2:1.7-52
ii  libbcprov-java 1.51-1
ii  libcommons-codec-java  1.10-1
ii  libcommons-lang3-java  3.4-1
ii  libcommons-logging-java1.2-1
ii  libdbus-java   2.8-6
ii  libdnsjava-java2.1.7-0.1
ii  libfelix-framework-java4.6.1-1
ii  libfelix-main-java 5.0.0-1
ii  libhttpclient-java 4.4.1-1
ii  libhttpcore-java   4.4.1-1
ii  libhttpmime-java   4.4.1-1
ii  libjcalendar-java  1.3.3-3
ii  libjgoodies-forms-java 1.6.0-4
ii  libjmdns-java  3.4.1-2
ii  libjna-java4.1.0-1
ii  libjson-simple-java1.1.1-3
ii  libjzlib-java  1.1.3-1
ii  liblaf-widget-java 4.3-2
ii  liblog4j1.2-java   1.2.17-5
ii  libmac-widgets-java0.10.0+svn416-dfsg1-1
ii  libunixsocket-java 0.7.3-1
ii  libxpp3-java   1.1.4c-2
ii  openjdk-7-jre [java6-runtime]  7u79-2.5.5-1

jitsi recommends no packages.

jitsi suggests no packages.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#833902: marked as done (jitsi uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #760853,
regarding jitsi uninstallable
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.)


-- 
760853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jitsi
Version: 2.5.5313-1
Justification: renders package unusable
Severity: grave

Dear Maintainer,
Jitsi is still uninstallable on amd64 -

[$] sudo aptitude install jitsi -y

[sudo] password for shirish:
The following NEW packages will be installed:
  jitsi{b} jitsi-common{a} jitsi-jni{a}
0 packages upgraded, 3 newly installed, 0 to remove and 3 not upgraded.
Need to get 8,423 kB of archives. After unpacking 31.5 MB will be used.
The following packages have unmet dependencies:
 jitsi : Depends: libjitsi (>= 415-0) which is a virtual package and
is not provided by any available package

 Depends: libjitsi-jni (>= 415-0) which is a virtual package
and is not provided by any available package

 Depends: libphonenumber6-java which is a virtual package and
is not provided by any available package

The following actions will resolve these dependencies:

 Keep the following packages at their current version:
1) jitsi [Not Installed]

No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.


As far as dependencies are concerned, apart from libjitsi and
libjitsi-jni which probably needs to be provided by jitsi itself ,
libphonenumber6-java has been superseded by libphonenumber7-java so a
rebuild or/and an NMU would be needed to take care of the changed
dependancy.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (1, 'experimental-debug'), (1, 'experimental'), (1,
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#831232: marked as done (jitsi uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #760853,
regarding jitsi uninstallable
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.)


-- 
760853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jitsi
Version: 2.5.5313-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> ┌──┐
> │ Install jitsi build dependencies (apt-based resolver)   
>  │
> └──┘
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-jitsi-dummy : Depends: libjitsi but it is not 
> installable
> Depends: libjitsi-jni but it is not 
> installable
> Depends: libphonenumber6-java but it is 
> not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/14/jitsi_2.5.5313-1_unstable_gcc5.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#760853: marked as done (jitsi uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 07 Aug 2017 17:24:34 +
with message-id 
and subject line Bug#870990: Removed package(s) from unstable
has caused the Debian Bug report #760853,
regarding jitsi uninstallable
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.)


-- 
760853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jitsi
Version: 2.4.4997-1.2
Severity: important

Dear Maintainer,
libavfilter4 is no longer in the archive.

$ apt-show-versions -a libavfilter4
libavfilter4:amd64 6:10.4-1 install ok installed
No testing version
No testing-updates version
No unstable version
No experimental version
libavfilter4:amd64 6:10.4-1 installed: No available version in archive

Because it's function is replicated by libavfilter5.

$ apt-show-versions -a libavfilter5
libavfilter5:amd64 6:11~beta1-2 install ok installed
libavfilter5:amd64 6:11~beta1-2 jessie   debian.ec.as6453.net
No testing-updates version
libavfilter5:amd64 6:11~beta1-2 unstable debian.ec.as6453.net
No experimental version
libavfilter5:amd64/jessie 6:11~beta1-2 uptodate

Now trying to purge libavfilter4 gives me this :-

$ sudo aptitude purge libavfilter4
[sudo] password for shirish:
The following packages will be REMOVED:
  libavfilter4{p}
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 396 kB will be freed.
The following packages have unmet dependencies:
 libjitsi-jni : Depends: libavfilter4 (>= 6:10~beta1~) but it is not
going to be installed.
The following actions will resolve these dependencies:

 Remove the following packages:
1) jitsi
2) libjitsi-jni

Accept this solution? [Y/n/q/?] q
Abandoning all efforts to resolve these dependencies.
Abort.

Could you make a new release of both jitsi and libjitsi-jni which
works with libavfilter5 instead of just libavfilter4.

Looking forward to solution.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'testing-updates'), (1,
'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages jitsi depends on:
ii  default-jre [java6-runtime]2:1.7-52
ii  libbcprov-java 1.49+dfsg-2
ii  libcommons-codec-java  1.9-1
ii  libcommons-lang3-java  3.3.2-1
ii  libcommons-logging-java1.2-1
ii  libdbus-java   2.8-5
ii  libdnsjava-java2.1.5-0.1
ii  libfelix-framework-java4.4.0-1
ii  libfelix-main-java 4.4.0-1
ii  libhttpclient-java 4.3.5-1
ii  libhttpcore-java   4.3.2-2
ii  libhttpmime-java   4.3.5-1
ii  libjcalendar-java  1.3.3-3
ii  libjgoodies-forms-java 1.6.0-4
ii  libjitsi-jni   2.4.4997-1.2
ii  libjmdns-java  3.4.1-2
ii  libjna-java3.2.7-4+b1
ii  libjson-simple-java1.1.1-2
ii  libjzlib-java  1.1.3-1
ii  liblaf-widget-java 4.3-2
ii  liblog4j1.2-java   1.2.17-4
ii  libmac-widgets-java0.9.5+svn369-dfsg1-3
ii  libunixsocket-java 0.7.3-1
ii  libxpp3-java   1.1.4c-2
ii  openjdk-7-jre [java6-runtime]  7u65-2.5.1-4

jitsi recommends no packages.

jitsi suggests no packages.

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Version: 2.5.5313-1+rm

Dear submitter,

as the package jitsi has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/870990

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---