Bug#873372: anything-el: package is outdated and obsolete, removal required

[Lev Lamberov]

Package: anything-el
Severity: grave

Dear Maintainer,

the last upload of the package in question was in Nov 2014 (version
1.287-2.1), which was a NMU upload, but the last maintainer's upload was
in Mar 2011 (version 1.287-2). Since then upstream renamed anything-el
[0] to helm and released 2.8.2 in Aug 2017 [1]. Moreover, since
anything-el was not maintained for a long time, helm was packaged
separately in Feb 2016 using new dh-elpa infrastructure, and currently
is team-maintained by pkg-emacsen [2].

The anything-el package is heavily outdated (as the indication in its
source code says it is tested only with Emacs 22/23, where there's Emacs
25 in stretch, and Emacs 24 will be removed from the archive soon),
don't use the modern Emacs addons infrastructure. Since according to
popcon there are some (47) users of the package [3], it should become a
transitional dummy package, which should depend on elpa-helm, and after
some time should be removed from Debian. Alternative approach would be
to remove anything-el, and build transitional dummy package from helm
source package to allow migrations.

Cheers!
Lev Lamberov

[0] https://www.emacswiki.org/emacs/Anything

[1] https://github.com/emacs-helm/helm

[2] https://tracker.debian.org/pkg/helm

[3] https://qa.debian.org/popcon.php?package=anything-el

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#873370: kmenuedit: All versions in repositories are extremely out of date.

[Brice Hunt]

Package: kmenuedit
Version: 4:5.8.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The out of date kmenuedit saves configuration files in the wrong directories, 
causing most menu edits to be lost.
The newest version in repositories is 4.8.5. The newest version available from 
upstream is 5.10.5. The version of kmenuedit
in the repositories does not work with the version of plasma that is available 
in the repositories.

The recommended solution is to package a more up-to-date version for Debian and 
submit it. 

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
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), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmenuedit depends on:
ii  kio 5.28.0-2
ii  libc6   2.24-11+deb9u1
ii  libkf5completion5   5.28.0-1
ii  libkf5configcore5   5.28.0-2
ii  libkf5configgui55.28.0-2
ii  libkf5configwidgets55.28.0-2
ii  libkf5coreaddons5   5.28.0-2
ii  libkf5dbusaddons5   5.28.0-1
ii  libkf5i18n5 5.28.0-2
ii  libkf5iconthemes5   5.28.0-2
ii  libkf5kdelibs4support5  5.28.0-1
ii  libkf5kiowidgets5   5.28.0-2
ii  libkf5service-bin   5.28.0-1
ii  libkf5service5  5.28.0-1
ii  libkf5sonnetcore5   5.28.0-2
ii  libkf5sonnetui5 5.28.0-2
ii  libkf5widgetsaddons55.28.0-3
ii  libkf5xmlgui5   5.28.0-1
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5xml5  5.7.1+dfsg-3+b1
ii  libstdc++6  6.3.0-18

Versions of packages kmenuedit recommends:
ii  khotkeys  4:5.8.6-1

kmenuedit suggests no packages.

-- no debconf information

Bug#853526: marked as done (llvm-toolchain-4.0: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 03:01:17 +
with message-id 
and subject line Bug#853526: fixed in llvm-toolchain-4.0 1:4.0.1-2
has caused the Debian Bug report #853526,
regarding llvm-toolchain-4.0: 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.)


-- 
853526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-4.0
Version: 1:4.0~+rc1-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/llvm-toolchain-4.0_4.0~+rc1-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

[...]
/usr/bin/ranlib ../../../../../../lib/libclangTidyModernizeModule.a
[ 58%] Building CXX object 
tools/clang/lib/CodeGen/CMakeFiles/clangCodeGen.dir/VarBypassDetector.cpp.o
cd 
"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/tools/clang/lib/CodeGen" 
&& /usr/bin/g++-7   -DCLANG_ENABLE_ARCMT -DCLANG_ENABLE_OBJC_REWRITER 
-DCLANG_ENABLE_STATIC_ANALYZER -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-I"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/tools/clang/lib/CodeGen"
 -I"/<>/llvm-toolchain-4.0-4.0~+rc1/tools/clang/lib/CodeGen" 
-I"/<>/llvm-toolchain-4.0-4.0~+rc1/tools/clang/include" 
-I"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/tools/clang/include" 
-I"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/include" 
-I"/<>/llvm-toolchain-4.0-4.0~+rc1/include"  -std=c++0x -gsplit-dwarf 
-Wl,-fuse-ld=gold -fPIC -fvisibility-inlines-hidden -Wall -W 
-Wno-unused-parameter -Wwrite-strings -Wcast-qual 
-Wno-missing-field-initializers -pedantic -Wno-long-long 
-Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment 
-Werror=date-time -std=c++11 -ffunction-sections -fdata-sect
 ions -fno-common -Woverloaded-virtual -fno-strict-aliasing -O2 -g -DNDEBUG
-fno-exceptions -o CMakeFiles/clangCodeGen.dir/VarBypassDetector.cpp.o -c 
"/<>/llvm-toolchain-4.0-4.0~+rc1/tools/clang/lib/CodeGen/VarBypassDetector.cpp"
[ 58%] Linking CXX static library ../../../../../../lib/libclangTidyMiscModule.a
cd 
"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/tools/clang/tools/extra/clang-tidy/misc"
 && /usr/bin/cmake -P 
CMakeFiles/clangTidyMiscModule.dir/cmake_clean_target.cmake
cd 
"/<>/llvm-toolchain-4.0-4.0~+rc1/build-llvm/tools/clang/tools/extra/clang-tidy/misc"
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/clangTidyMiscModule.dir/link.txt --verbose=1
/usr/bin/ar qc ../../../../../../lib/libclangTidyMiscModule.a  
CMakeFiles/clangTidyMiscModule.dir/ArgumentCommentCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/AssertSideEffectCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/MisplacedConstCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/UnconventionalAssignOperatorCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/BoolPointerImplicitConversionCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/DanglingHandleCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/DefinitionsInHeadersCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/FoldInitTypeCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/ForwardDeclarationNamespaceCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/InaccurateEraseCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/IncorrectRoundings.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/InefficientAlgorithmCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/MacroParenthesesCheck.cpp.o 
CMakeFiles/clangTidyMiscModule.dir/MacroRepeatedSideEffectsCheck.cpp.o 
CMakeFiles/cla
 ngTidyMiscModule.dir/MiscTidyModule.cpp.o 
CMakeFiles/clangT

Bug#873200: marked as done (/usr/bin/llvm-config-4.0: relocation error: /usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 03:01:17 +
with message-id 
and subject line Bug#866354: fixed in llvm-toolchain-4.0 1:4.0.1-2
has caused the Debian Bug report #866354,
regarding /usr/bin/llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
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.)


-- 
866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-4.0-dev
Version: 1:4.0.1-1
Severity: serious
Justification: Breaks compilation of dependent packages on a release 
architecture

Hi,

This error seems to occur on armel only. Affected is the package aspectc++, 
which FTBFS because of this bug.
Please see the buildlog at 
https://buildd.debian.org/status/fetch.php?pkg=aspectc%2B%2B&arch=armel&ver=1%3A2.2%2Bgit20170823-1&stamp=1503642904&raw=0

The relevant part reads like this:

[...]
/usr/bin/make -s -C AspectC++ cleanall FRONTEND=Clang 
LLVMCONF=/usr/bin/llvm-config-4.0
/usr/bin/llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
config/clang.mk:12: *** UNSUPPORTED Clang version '' used -- try 'make -C 
config clang LLVMCONF='.  Stop.
debian/rules:85: recipe for target 'clean' failed
make: *** [clean] Error 2


Thanks for looking into this!
Reinhard
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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: Sat, 26 Aug 2017 17:36:26 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang library
 libclang1-4.0-dbg - clang library
 libfuzzer-4.0-dev - Library for coverage-guided fuzz testing
 liblld-4.0 - LLVM-based linker, library
 liblld-4.0-dbg - LLVM-based linker, debugging libraries
 liblld-4.0-dev - LLVM-based linker, header files
 liblldb-4.0 - Next generation, high-performance debugger, library
 liblldb-4.0-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-4.0-dev - Next generation, high-performance debugger, header files
 libllvm-4.0-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm4.0 - Modular compiler and toolchain technologies, runtime library
 libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lld-4.0- LLVM-based linker
 lldb-4.0   - Next generation, high-performance debugger
 llvm-4.0   - Modular compiler and toolchain technologies
 llvm-4.0-dev - Modular compiler and toolchain technologies, libraries and 
header
 llvm-4.0-doc - Modular compiler and toolchain 

Bug#871591: marked as done ([src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 03:01:17 +
with message-id 
and subject line Bug#871591: fixed in llvm-toolchain-4.0 1:4.0.1-2
has caused the Debian Bug report #871591,
regarding [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect 
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.)


-- 
871591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-snapshot
Version: 1:5.0~svn305653-1
Severity: serious
Tags: patch sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Dear LLVM packagers,

I've noticed that llvm-toolchain-snapshot goes FTBFS because
`debian/rules' in the packge fails to detect gcc-7 (it tries to use
gcc-7.1). The Jenkins builds seem to be failing due to the same bug.
http://llvm-jenkins.debian.net/view/Debian%20unstable/job/llvm-toolchain-binaries/architecture=amd64,distribution=unstable/898/console

Here I send a patch to fix this by ensuring the existence of
/usr/bin/g++-$(GCC_VERSION) on the build system.

Could you take a look at it please?
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/changelog llvm-toolchain-snapshot-5.0~svn305653/debian/changelog
--- llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-08-09 23:32:40.0 +0900
@@ -1,3 +1,10 @@
+llvm-toolchain-snapshot (1:5.0~svn305653-1.1) UNRELEASED; urgency=medium
+
+  * Ensure /usr/bin/g++-$(GCC_VERSION) exists
+
+ -- Katsuhiko Nishimra   Wed, 09 Aug 2017 23:32:40 +0900
+
 llvm-toolchain-snapshot (1:5.0~svn305653-1) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/rules llvm-toolchain-snapshot-5.0~svn305653/debian/rules
--- llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-08-09 23:32:40.0 +0900
@@ -2,9 +2,11 @@
 
 TARGET_BUILD	:= build-llvm
 DEB_INST		:= $(CURDIR)/debian/tmp/
-# The 5|6| in the regexp is a crappy workaround. g++ 5.2 in Debian is not providing a g++-5.2 binary (only g++-5)
-# accomodate that by hardcoding the 5 detection
-GCC_VERSION := $(shell dpkg-query -W -f '$${Version}' g++ | sed -rne 's,^([0-9]+:)?(5|6|[0-9]+\.[0-9]+|[0-9]+).*$$,\2,p')
+
+GXX_VERSIONED_PACKAGE:= $(shell dpkg-query -W -f '$${Depends}' g++ | grep -o 'g++-[0-9][0-9.]*' | tail -n1 )
+GXX_VERSIONED_EXECUTABLE := $(shell dpkg -L $(GXX_VERSIONED_PACKAGE) | grep '/usr/bin/g++-[0-9][0-9.]*' | xargs ls -d | tail -n1 )
+GCC_VERSION  := $(subst /usr/bin/g++-,,$(GXX_VERSIONED_EXECUTABLE))
+
 LLVM_VERSION	:= 5.0
 LLVM_VERSION_FULL := $(LLVM_VERSION).0
 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-2

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-4.0, 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.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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: Sat, 26 Aug 2017 17:36:26 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to fo

Bug#866354: marked as done (armel: symbol _ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in file libstdc++.so.6)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 03:01:17 +
with message-id 
and subject line Bug#866354: fixed in llvm-toolchain-4.0 1:4.0.1-2
has caused the Debian Bug report #866354,
regarding armel: symbol _ZTINSt13__future_base12_Result_baseE, version 
GLIBCXX_3.4.15 not defined in file libstdc++.so.6
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.)


-- 
866354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstdc++6
Version: 7.1.0-7
Severity: serious
Control: affects -1 src:mesa

mesa FTBFS on armel due to:

https://buildd.debian.org/status/fetch.php?pkg=mesa&arch=armel&ver=17.1.3-2&stamp=1498610882&raw=0

...
llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
llvm-config-4.0: relocation error: 
/usr/lib/llvm-4.0/bin/../lib/libLLVM-4.0.so.1: symbol 
_ZTINSt13__future_base12_Result_baseE, version GLIBCXX_3.4.15 not defined in 
file libstdc++.so.6 with link time reference
...


My first guess would be that the #727621 fix might be missing
or broken in GCC 7.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-4.0
Source-Version: 1:4.0.1-2

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-4.0 
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: Sat, 26 Aug 2017 17:36:26 +0200
Source: llvm-toolchain-4.0
Binary: clang-4.0 clang-format-4.0 clang-tidy-4.0 clang-4.0-doc libclang1-4.0 
libclang1-4.0-dbg libclang-4.0-dev libclang-common-4.0-dev libfuzzer-4.0-dev 
python-clang-4.0 clang-4.0-examples libllvm4.0 libllvm4.0-dbg llvm-4.0 
llvm-4.0-runtime llvm-4.0-dev llvm-4.0-tools libllvm-4.0-ocaml-dev llvm-4.0-doc 
llvm-4.0-examples lld-4.0 liblld-4.0 liblld-4.0-dbg liblld-4.0-dev lldb-4.0 
liblldb-4.0 liblldb-4.0-dbg python-lldb-4.0 liblldb-4.0-dev
Architecture: source amd64 all
Version: 1:4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-4.0  - C, C++ and Objective-C compiler (LLVM based)
 clang-4.0-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-4.0-examples - Clang examples
 clang-format-4.0 - Tool to format C/C++/Obj-C code
 clang-tidy-4.0 - clang-based C++ linter tool
 libclang-4.0-dev - clang library - Development package
 libclang-common-4.0-dev - clang library - Common development package
 libclang1-4.0 - C interface to the clang library
 libclang1-4.0-dbg - clang library
 libfuzzer-4.0-dev - Library for coverage-guided fuzz testing
 liblld-4.0 - LLVM-based linker, library
 liblld-4.0-dbg - LLVM-based linker, debugging libraries
 liblld-4.0-dev - LLVM-based linker, header files
 liblldb-4.0 - Next generation, high-performance debugger, library
 liblldb-4.0-dbg - Next generation, high-performance debugger, debugging 
libraries
 liblldb-4.0-dev - Next generation, high-performance debugger, header files
 libllvm-4.0-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm4.0 - Modular compiler and toolchain technologies, runtime library
 libllvm4.0-dbg - Modular compiler and toolchain technologies, debugging 
libraries
 lld-4.0- LLVM-based linker
 lldb-4.0   - Next generation, high-performance debugger
 llvm-4.0   - Modular compiler and toolchain technologies
 llvm-4.0-dev - Modular compiler and toolchain technologies, librar

Bug#871591: marked as done ([src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect gcc-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 02:56:58 +
with message-id 
and subject line Bug#871591: fixed in llvm-toolchain-3.9 1:3.9.1-11
has caused the Debian Bug report #871591,
regarding [src:llvm-toolchain-snapshot] FTBFS: debian/rules fails to detect 
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.)


-- 
871591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-snapshot
Version: 1:5.0~svn305653-1
Severity: serious
Tags: patch sid
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Dear LLVM packagers,

I've noticed that llvm-toolchain-snapshot goes FTBFS because
`debian/rules' in the packge fails to detect gcc-7 (it tries to use
gcc-7.1). The Jenkins builds seem to be failing due to the same bug.
http://llvm-jenkins.debian.net/view/Debian%20unstable/job/llvm-toolchain-binaries/architecture=amd64,distribution=unstable/898/console

Here I send a patch to fix this by ensuring the existence of
/usr/bin/g++-$(GCC_VERSION) on the build system.

Could you take a look at it please?
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/changelog llvm-toolchain-snapshot-5.0~svn305653/debian/changelog
--- llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/changelog	2017-08-09 23:32:40.0 +0900
@@ -1,3 +1,10 @@
+llvm-toolchain-snapshot (1:5.0~svn305653-1.1) UNRELEASED; urgency=medium
+
+  * Ensure /usr/bin/g++-$(GCC_VERSION) exists
+
+ -- Katsuhiko Nishimra   Wed, 09 Aug 2017 23:32:40 +0900
+
 llvm-toolchain-snapshot (1:5.0~svn305653-1) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru llvm-toolchain-snapshot-5.0~svn305653/debian/rules llvm-toolchain-snapshot-5.0~svn305653/debian/rules
--- llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-06-09 19:04:56.0 +0900
+++ llvm-toolchain-snapshot-5.0~svn305653/debian/rules	2017-08-09 23:32:40.0 +0900
@@ -2,9 +2,11 @@
 
 TARGET_BUILD	:= build-llvm
 DEB_INST		:= $(CURDIR)/debian/tmp/
-# The 5|6| in the regexp is a crappy workaround. g++ 5.2 in Debian is not providing a g++-5.2 binary (only g++-5)
-# accomodate that by hardcoding the 5 detection
-GCC_VERSION := $(shell dpkg-query -W -f '$${Version}' g++ | sed -rne 's,^([0-9]+:)?(5|6|[0-9]+\.[0-9]+|[0-9]+).*$$,\2,p')
+
+GXX_VERSIONED_PACKAGE:= $(shell dpkg-query -W -f '$${Depends}' g++ | grep -o 'g++-[0-9][0-9.]*' | tail -n1 )
+GXX_VERSIONED_EXECUTABLE := $(shell dpkg -L $(GXX_VERSIONED_PACKAGE) | grep '/usr/bin/g++-[0-9][0-9.]*' | xargs ls -d | tail -n1 )
+GCC_VERSION  := $(subst /usr/bin/g++-,,$(GXX_VERSIONED_EXECUTABLE))
+
 LLVM_VERSION	:= 5.0
 LLVM_VERSION_FULL := $(LLVM_VERSION).0
 


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-3.9
Source-Version: 1:3.9.1-11

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-3.9, 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.
Sylvestre Ledru  (supplier of updated llvm-toolchain-3.9 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Jun 2017 19:12:15 +0200
Source: llvm-toolchain-3.9
Binary: clang-3.9 clang-format-3.9 clang-tidy-3.9 clang-3.9-doc libclang1-3.9 
libclang1-3.9-dbg libclang-3.9-dev libclang-common-3.9-dev libfuzzer-3.9-dev 
python-clang-3.9 clang-3.9-examples libllvm3.9 libllvm3.9-dbg llvm-3.9 
llvm-3.9-runtime llvm-3.9-dev llvm-3.9-tools libllvm-3.9-ocaml-dev llvm-3.9-doc 
llvm-3.9-examples lldb-3.9 liblldb-3.9 liblldb-3.9-dbg python-lldb-3.9 
liblldb-3.9-dev
Architecture: source amd64 all
Version: 1:3.9.1-11
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-3.9  - C, C++ and Objective-C compiler (LLVM based)
 clang-3.9-doc - C, C++ and Objective-C compiler (LLVM based) - Documentation
 clang-3.9-examples - Clang examples
 clang-format-3.9 - Tool to format C/C++/Obj-C code
 clang-tidy-3.9 - clang-

Bug#853524: marked as done (llvm-toolchain-3.9: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 02:56:58 +
with message-id 
and subject line Bug#853524: fixed in llvm-toolchain-3.9 1:3.9.1-11
has caused the Debian Bug report #853524,
regarding llvm-toolchain-3.9: 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.)


-- 
853524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-3.9
Version: 1:3.9.1-3
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/llvm-toolchain-3.9_3.9.1-3_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

[...]
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x5ca0): error: undefined 
reference to 'clang::ObjCMethodDecl::isInstanceMethod() const'
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x7010): error: undefined 
reference to 
'clang::ObjCInterfaceDecl::isVisibleCategory(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x79b0): error: undefined 
reference to 'clang::ObjCPropertyDecl::isInstanceProperty() const'
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x11080): error: undefined 
reference to 'clang::ObjCPropertyDecl::isClassProperty() const'
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x19a88): error: undefined 
reference to 
'clang::ObjCInterfaceDecl::isKnownCategory(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndex.cpp.o(.debug_addr+0x1b228): error: undefined 
reference to 
'clang::ObjCInterfaceDecl::isKnownExtension(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x900): error: 
undefined reference to 
'clang::ObjCInterfaceDecl::isKnownExtension(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0xb98): error: 
undefined reference to 
'clang::ObjCInterfaceDecl::isVisibleExtension(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0xda8): error: 
undefined reference to 'clang::ObjCMethodDecl::isClassMethod() const'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x1028): error: 
undefined reference to 
'clang::ObjCInterfaceDecl::isKnownCategory(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x1100): error: 
undefined reference to 
'clang::ObjCInterfaceDecl::isVisibleCategory(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x1490): error: 
undefined reference to 'clang::ObjCPropertyDecl::isClassProperty() const'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x18f0): error: 
undefined reference to 'clang::ObjCMethodDecl::isInstanceMethod() const'
CMakeFiles/libclang.dir/CIndexCodeCompletion.cpp.o(.debug_addr+0x28c0): error: 
undefined reference to 'clang::ObjCPropertyDecl::isInstanceProperty() const'
CMakeFiles/libclang.dir/CIndexHigh.cpp.o(.debug_addr+0x998): error: undefined 
reference to 
'clang::ObjCInterfaceDecl::isVisibleCategory(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexHigh.cpp.o(.debug_addr+0xb90): error: undefined 
reference to 'clang::ObjCPropertyDecl::isClassProperty() const'
CMakeFiles/libclang.dir/CIndexHigh.cpp.o(.debug_addr+0xf30): error: undefined 
reference to 
'clang::ObjCInterfaceDecl::isVisibleExtension(clang::ObjCCategoryDecl*)'
CMakeFiles/libclang.dir/CIndexHigh.cpp.o(.debug_addr+0x11a8): error: undefined 
reference to 'clang::ObjCMethodDecl::isClassMethod() const'
CMakeFiles/libclang.dir/CIndexHigh.

Bug#873231: marked as done (rapidjson: FTBFS with gcc 7)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 23:50:05 +
with message-id 
and subject line Bug#873231: fixed in rapidjson 1.1.0+dfsg-3
has caused the Debian Bug report #873231,
regarding rapidjson: 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.)


-- 
873231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rapidjson
Version: 1.1.0+dfsg-2
Severity: important
Tags: patch

Dear Maintainer,

rapidjson in experimental fails to build due to stricter checks
introduced in gcc-7.

This has been fixed upstream. Please cherry-pick
https://github.com/miloyip/rapidjson/commit/fe19b7b6016d446722621fb407738209d1a911e8
If you want to be nice to private backporters, please cherry-pick
the follow-up commit
https://github.com/miloyip/rapidjson/commit/cba45fe9de6923b858edb0780e257b7257aa4f7b
as well so the fix will not break builds when using older gcc versions.

Regards,

Christoph



signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: rapidjson
Source-Version: 1.1.0+dfsg-3

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated rapidjson 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: Sat, 26 Aug 2017 16:49:27 +
Source: rapidjson
Binary: rapidjson-dev rapidjson-doc
Architecture: source all
Version: 1.1.0+dfsg-3
Distribution: experimental
Urgency: medium
Maintainer: Rene Engelhard 
Changed-By: Rene Engelhard 
Description:
 rapidjson-dev - fast JSON parser/generator for C++ with SAX/DOM style API
 rapidjson-doc - fast JSON parser/generator for C++ (API documentation)
Closes: 873231
Changes:
 rapidjson (1.1.0+dfsg-3) experimental; urgency=medium
 .
   * add upstream patches to fix build with gcc 7 (closes: #873231)
Checksums-Sha1:
 dbe33e33bf60e119efe5656cf641e98507e7c406 1873 rapidjson_1.1.0+dfsg-3.dsc
 fb881d0f68d8c90d0e56a738a32887beedee98e5 6772 
rapidjson_1.1.0+dfsg-3.debian.tar.xz
 d2a167fca69444b8d909790b86925d5f347c041a 98150 
rapidjson-dev_1.1.0+dfsg-3_all.deb
 9b1eb7da1d01e541525dc2a0c4673064fb8008a8 1007702 
rapidjson-doc_1.1.0+dfsg-3_all.deb
 141b84135390fe68dbeb2f2be49f7151b56e4ab4 7062 
rapidjson_1.1.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 7d3dad16d87659be931f822ba1a1ebf2d50996e49eaf58d47c79ed41ba416303 1873 
rapidjson_1.1.0+dfsg-3.dsc
 0980e44d91cc4a1eb13e9bf4c7b405dd17160e3cf80ee00282d64c3f71ae8f8e 6772 
rapidjson_1.1.0+dfsg-3.debian.tar.xz
 f3c014d7371aa6f95d2f45ebe3db65bb53a6778487191b358c43b0bc7c5b0a8b 98150 
rapidjson-dev_1.1.0+dfsg-3_all.deb
 e2b7653295de14542c66b3593e8196d5de52324b8a733653d170f91c8c80d878 1007702 
rapidjson-doc_1.1.0+dfsg-3_all.deb
 af2fae9d32de4c970390262e10de62ea4a027c48844e8f68beda982f1feff21a 7062 
rapidjson_1.1.0+dfsg-3_amd64.buildinfo
Files:
 a997c84dcebb15052464197d96f53e82 1873 libs optional rapidjson_1.1.0+dfsg-3.dsc
 efa5e0fd8ecb65e75d977283dc51bb63 6772 libs optional 
rapidjson_1.1.0+dfsg-3.debian.tar.xz
 40ebc826f3415f77ca2338bb2fe3a8e8 98150 libdevel optional 
rapidjson-dev_1.1.0+dfsg-3_all.deb
 b44b5f21b3b8611023a3f9ce514854e4 1007702 doc optional 
rapidjson-doc_1.1.0+dfsg-3_all.deb
 1203fa5c3fc139200110028fd9953c14 7062 libs optional 
rapidjson_1.1.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAlmiBqwACgkQCqBFcdA+
PnD39g/8CgZdfRDtFUmAfivL7KLxBNCpKJeeeTpm2gU92+DqeXehuw1R5X+hWLcO
aIkD3LhRWuSHwlBcl8OFjkbxz95MQvyv+ldgeQMmG27iwRlT6VfmKEM0xH6e8/7r
mGqjwxz7yCFp5O7tUI0ycu3aJGzSM57IhWfeoGNtgSGKkCp48s1x79pLRVXOqhvT
B7QhWOa7WeKoanDHjcZ5/aylnsWh1FeYOX42lFkJkIrAm2AgnVC7ywu80GSAMRtv
iyQCLDbZKpUCLWu+PE/wrf3pt2izNYS3Z6wbsE6lGZBq2v05mSIx8D4nyhfdBYpI
jZwUzrCvnW0dqogjcAffdskCGVr58xeYvm0vq6AwG0NdJciv27aahb/pzOylh6Ek
Srj9D0fmaLuat6/9YK0d5rmU5wVanrjXwynJhYEeaDma2Q75LMud8pKM+zRewXU2
rJhKWC6Z1cSxuNxSuTvNjCfvwscj/TR/xFpUQQYdS6gs+2wgdRn1dEnKMRvAGEzV
3Ve13SrcvN9yLQ28KuRW+SmsOmSVBcDQKr6OYCvOvjIB80nB3/h+JrXQhNfkNSO7
hzYcYa1r3AdPweNgQGm1X7Wp6D+Tkyji

Bug#873324: marked as done (minetest FTBFS with luajit 2.1)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 23:04:51 +
with message-id 
and subject line Bug#873324: fixed in minetest 0.4.16+repack-4
has caused the Debian Bug report #873324,
regarding minetest FTBFS with luajit 2.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.)


-- 
873324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minetest
Version: 0.4.16+repack-2
Severity: serious

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

...
In file included from 
/build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
/build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: fatal 
error: lua.h: No such file or directory
 #include 
  ^~~
compilation terminated.
src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
make[3]: *** [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] 
Error 1
--- End Message ---
--- Begin Message ---
Source: minetest
Source-Version: 0.4.16+repack-4

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated minetest 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: Sat, 26 Aug 2017 23:50:33 +0200
Source: minetest
Binary: minetest minetest-server minetest-data
Architecture: source
Version: 0.4.16+repack-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 minetest   - Multiplayer infinite-world block sandbox
 minetest-data - Multiplayer infinite-world block sandbox (data files)
 minetest-server - Multiplayer infinite-world block sandbox (server)
Closes: 873324
Changes:
 minetest (0.4.16+repack-4) unstable; urgency=medium
 .
   * Add luajit-2.1.patch and patch the FindLuaJIT cmake module to detect
 version 2.1. (Closes: #873324)
Checksums-Sha1:
 edbfe1791acf00a609214128aa0643a39929ceb7 2741 minetest_0.4.16+repack-4.dsc
 608cbc65729563bda72fa3f61dccfc130b65caf5 37516 
minetest_0.4.16+repack-4.debian.tar.xz
 ebc9a96072b09a38f332411632295d4a19d363ba 11656 
minetest_0.4.16+repack-4_amd64.buildinfo
Checksums-Sha256:
 d72812d4acae8b38b1547aead4e1ab071ac72571bcc34ae2d12c9b5d54697a63 2741 
minetest_0.4.16+repack-4.dsc
 6f6f0cb9a277895289041f3ec3d7947b02690d7429c38f13261bc7fe15ed91b0 37516 
minetest_0.4.16+repack-4.debian.tar.xz
 8007bcef65a9a6853613ccdcd56c17524e8a7aca84caf2578c3f8267334979df 11656 
minetest_0.4.16+repack-4_amd64.buildinfo
Files:
 99a115a917cbd2bbcbb62072c90b0ba5 2741 games optional 
minetest_0.4.16+repack-4.dsc
 d3019ca43ac7b40d5931b19fd1d4cf60 37516 games optional 
minetest_0.4.16+repack-4.debian.tar.xz
 fcf3a42df30119fa16cd19611c6e89f6 11656 games optional 
minetest_0.4.16+repack-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlmh+UBfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk16QQAMQj3mqmpftaZwDZED+vAKDDVMzn+vSlLs6R
GSDY4NK1jrkCgV/TDDFuT8OBh+g71HNyaoQpuVL388zvWA0hRFfcOxFsP+qOejBI
taNCN+aHTfBeCgeFQYZyxJxy9bVBC/60zIC0A0AoVK+Sk8qFUnaKvntoI/1lHjn4
w36UZbBP6mmG7uWprhk20mQcntrFGa7ZLpsOcaNXpJ/auzNWxq9OSYW6OLEGYhXG
qh9FXM8ZKrAXeZIY2R3rkdxEb+u07xIV3nzhzUZvazBHRXasBtB7vaHmfJCZgpYM
MziiCYlk6ukHhUFcEptJsA57Os5GJaUotxWiif+4YUtHsAQaKwywzIPdh5+h/+Uv
50ip4DbDRtL0VQPbmUXRHKXq2iHPD+a1X0IqdTPhv2VhLAZMHNtry4NwRlP9HrAQ
GEY68AblvoUP92+f05X3THpmRszNdaFDgKdX+SWISAVOxIIixENdT4KIzngP7Sz1
gESWRSaMmXevpQMpTpFjuI1amLP/3pZVM6pa5LN7iLL/HkQOfMdX9SQqJ8D1ZUtd
5Q/EWohlkGCi18T16PbMfIeQsgw48EDGw136IG7U4vk7+v4/ZNLMLPVKogYT8ZpH
uE7nyrYFX0ZA83dzUHFaHPD7J0I8OK6kjHRKcwXnp8ZAeUmD20ba9rIXQTdYMYNk
msuVeEQC
=mabY
-END PGP SIGNATURE End Message ---

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Rene Engelhard]

Package: coinor-libcoinutils3v5
Version: 2.10.14+repack1-1
Severity: serious

Hi,

LOs unit tests fail (don't get confused by the name, also tests the CoinMP
based solver) since the last updates in sid:

build CUT] sccomp_lpsolver
S=/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2 && 
I=$S/instdir && W=$S/workdir &&mkdir -p $W/CppunitTest/ && rm -fr 
$W/CppunitTest/sccomp_lpsolver.test.user && mkdir 
$W/CppunitTest/sccomp_lpsolver.test.user &&rm -fr 
$W/CppunitTest/sccomp_lpsolver.test.core && mkdir 
$W/CppunitTest/sccomp_lpsolver.test.core && cd 
$W/CppunitTest/sccomp_lpsolver.test.core && (   
LD_LIBRARY_PATH=${LD_LIBRARY_PATH:+$LD_LIBRARY_PATH:}"$I/program:$I/program":$W/UnpackedTarball/cppunit/src/cppunit/.libs
   MALLOC_CHECK_=2 MALLOC_PERTURB_=153  
$W/LinkTarget/Executable/cppunittester 
$W/LinkTarget/CppunitTest/libtest_sccomp_lpsolver.so --headless 
"-env:BRAND_BASE_DIR=file://$S/instdir" "-env:BRAND_SHARE_SUBDIR=share" 
"-env:UserInstallation=file://$W/CppunitTest/sccomp_lpsolver.test.user"   
"-env:CONFIGURATION_LAYERS=xcsxcu:file://$I/share/registry 
xcsxcu:file://$W/unittest/registry"  
"-env:UNO_TYPES=file://$I/program/types.rdb file://$I/program/types/offapi.rdb" 
 "-env:UNO_SERVICES=file://$W/Rdb/ure/services.rdb file://$W/Rdb/services.rdb"  
-env:URE_INTERNAL_LIB_DIR=file://$I/program -env:LO_LIB_DIR=file://$I/program 
-env:LO_JAVA_DIR=file://$I/program/classes --protector 
$W/LinkTarget/Library/unoexceptionprotector.so unoexceptionprotector 
--protector $W/LinkTarget/Library/unobootstrapprotector.so 
unobootstrapprotector   --protector 
$W/LinkTarget/Library/libvclbootstrapprotector.so vclbootstrapprotector   
"-env:CPPUNITTESTTARGET=$W/CppunitTest/sccomp_lpsolver.test"   )  > 
$W/CppunitTest/sccomp_lpsolver.test.log 2>&1 || ( RET=$?; 
$S/solenv/bin/gdb-core-bt.sh $W/LinkTarget/Executable/cppunittester 
$W/CppunitTest/sccomp_lpsolver.test.core $RET >> 
$W/CppunitTest/sccomp_lpsolver.test.log 2>&1; cat 
$W/CppunitTest/sccomp_lpsolver.test.log; 
$S/solenv/gbuild/platform/unittest-failed-default.sh Cppunit sccomp_lpsolver)
Segmentation fault (core dumped)
(anonymous namespace)::LpSolverTest::testLpSolver finished in: 579ms

It looks like 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/LinkTarget/Executable/cppunittester
 generated a core file at 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/CppunitTest/sccomp_lpsolver.test.core/core
Backtraces:
[New LWP 11917]
[New LWP 11918]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by 
`/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/workdir/Li'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f6dca552b9e in CoinMessageHandler::internalPrint() () from 
/usr/lib/x86_64-linux-gnu/libCoinUtils.so.3
[Current thread is 1 (Thread 0x7f6de7e2e740 (LWP 11917))]
warning: File 
"/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_sal.so.3-gdb.py"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path 
/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_sal.so.3-gdb.py
line to your configuration file "/tmp/tmp.Aw8SthVoRj/.gdbinit".
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/tmp/tmp.Aw8SthVoRj/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
warning: File 
"/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libuno_cppu.so.3-gdb.py"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
warning: File 
"/data/rene/Debian/Pakete/LibreOffice/libreoffice/libreoffice-5.4.1.2/instdir/program/libmergedlo.so-gdb.py"
 auto-loading has been declined by your `auto-load safe-path' set to 
"$debugdir:$datadir/auto-load".
rax0x0  0
rbx0x55fce8a092d0   94544722957008
rcx0x55fce8a094f8   94544722957560
rdx0x30 48
rsi0x0  0
rdi0x55fce8a092d0   94544722957008
rbp0x55fce8a092d0   0x55fce8a092d0
rsp0x7ffe59817bc0   0x7ffe59817bc0
r8 0x4  4
r9 0x4  4
r100x0  0
r110x1  1
120x0  0
r130x1  1
r140x7ffe59818020   140730400079904
r150x0  0
rip0x7f6dca552b9e   0x7f6dca552b9e 

eflags 0x10212  [ AF IF RF ]
cs 0x33 51
ss 0x2b 43
ds 0x0  0
es 0x0  0
fs 0x0

Bug#873275: always segfaults at start due to QSslSocket

[積丹尼 Dan Jacobson]

Glad to have found the bug for you early.

I only use qgis offline, so was dismayed that I couldn't even start it
even if never planning to use SSL over the network.

I mean even researchers in some offline arctic lab will find the copy of
qgis they brought with them is unusable even without ever having
attempted to make a http, (not even https) connection.

There should be some fallback mode available.

Bug#853375: marked as done (disulfinder: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 22:34:02 +
with message-id 
and subject line Bug#853375: fixed in disulfinder 1.2.11-7
has caused the Debian Bug report #853375,
regarding disulfinder: 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.)


-- 
853375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:disulfinder
Version: 1.2.11-6
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/disulfinder_1.2.11-6_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

[...]
BRNN/RNNs/StructureSearch.h:980:7: warning: unused variable 'num_nodes' 
[-Wunused-variable]
   int num_nodes = _toNodes.size();
   ^
In file included from BRNN/rnn_util.cpp:5:0:
BRNN/RNNs/RecursiveNN.h: In instantiation of 'void RecursiveNN::fPropagateInput(std::vector&, const DPAG&) [with 
HA_Function = TanH; OA_Function = Sigmoid; EMP = MGradientDescent; DPAG = 
boost::adjacency_list, 
boost::property >]':
BRNN/RNNs/RecursiveNN.h:1356:18:   required from 'void RecursiveNN::propagateStructuredInput(std::vector&, const 
std::pair, 
boost::property >, 
boost::adjacency_list, 
boost::property > >&) [with HA_Function = 
TanH; OA_Function = Sigmoid; EMP = MGradientDescent]'
BRNN/rnn_util.cpp:99:47:   required from here
BRNN/RNNs/RecursiveNN.h:1390:16: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
 require(_n == toNodes[t]->_encodedInput.size(), "Error in input dim!");
 ~~~^~~
BRNN/RNNs/RecursiveNN.h:1415:38: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
out_i!=out_end && edge_id[*out_i] < _v; ++out_i) {
BRNN/RNNs/RecursiveNN.h:1418:38: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
  for(int i=_n + edge_id[*out_i]*_m; i<_n + _m*(edge_id[*out_i] + 1); i++) {
 ~^~
BRNN/RNNs/RecursiveNN.h:1384:12: warning: variable 'vertex_id' set but not used 
[-Wunused-but-set-variable]
   VertexId vertex_id = boost::get(boost::vertex_index, sdag);
^
BRNN/RNNs/RecursiveNN.h: In instantiation of 'void RecursiveNN::bPropagateInput(std::vector&, const DPAG&) [with 
HA_Function = TanH; OA_Function = Sigmoid; EMP = MGradientDescent; DPAG = 
boost::adjacency_list, 
boost::property >]':
BRNN/RNNs/RecursiveNN.h:1359:34:   required from 'void RecursiveNN::propagateStructuredInput(std::vector&, const 
std::pair, 
boost::property >, 
boost::adjacency_list, 
boost::property > >&) [with HA_Function = 
TanH; OA_Function = Sigmoid; EMP = MGradientDescent]'
BRNN/rnn_util.cpp:99:47:   required from here
BRNN/RNNs/RecursiveNN.h:1470:17: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
   for(int t=0; t_encodedInput.size(), "Error!");
 ~~~^~~
BRNN/RNNs/RecursiveNN.h:1492:38: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
out_i!=out_end && edge_id[*out_i] < _v; ++out_i) {
BRNN/RNNs/RecursiveNN.h:1495:38: warning: comparison between signed and 
unsigned integer expressions [-Wsign-compare]
  for(int i=_n + edge_id[*out_i]*_m; i<_n + _m*(edge_id[*out_i] + 1); i++) {
 ~^~
BRNN/RNNs/RecursiveNN.h:1465:12: warning: variable 'vertex_id' set but not

Processed: fixed 784511 in 4:4.14.3-2+deb9u1

[Debian Bug Tracking System]

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

> fixed 784511 4:4.14.3-2+deb9u1
Bug #784511 [src:pykde4] [pykde4] Qt4's WebKit removal
Marked as fixed in versions pykde4/4:4.14.3-2+deb9u1.
> thanks
Stopping processing here.

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

Bug#871558: marked as done (echolot: pingd fail to start)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 22:14:41 +
with message-id 
and subject line Bug#873337: Removed package(s) from unstable
has caused the Debian Bug report #871558,
regarding echolot: pingd fail to start
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.)


-- 
871558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: echolot
Version: 2.1.9-1.1
Severity: grave
Tags: patch

Dear Maintainer,

pingd refuse to start with an error:
Unescaped left brace in regex is illegal here in regex; marked by <--
HERE in m/^\s*  \$remailer{ <-- HERE "(.*)"}  \s*=\s*  "<(.*@.*)>.*";

Furthermore the GPG output changed slightly and pingd is not able to
extract the address of a key any more.

Some WORKS-4-ME changes attached.

Regards
Benediff -ruNp echolot-2.1.9.orig/debian/.debhelper/generated/echolot/installed-by-dh_installdocs echolot-2.1.9/debian/.debhelper/generated/echolot/installed-by-dh_installdocs
diff -ruNp echolot-2.1.9.orig/debian/.debhelper/generated/echolot/installed-by-dh_installman echolot-2.1.9/debian/.debhelper/generated/echolot/installed-by-dh_installman
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/conffiles echolot-2.1.9/debian/echolot/DEBIAN/conffiles
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/control echolot-2.1.9/debian/echolot/DEBIAN/control
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/md5sums echolot-2.1.9/debian/echolot/DEBIAN/md5sums
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/postinst echolot-2.1.9/debian/echolot/DEBIAN/postinst
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/postrm echolot-2.1.9/debian/echolot/DEBIAN/postrm
diff -ruNp echolot-2.1.9.orig/debian/echolot/DEBIAN/prerm echolot-2.1.9/debian/echolot/DEBIAN/prerm
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/default/echolot echolot-2.1.9/debian/echolot/etc/default/echolot
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/pingd.conf echolot-2.1.9/debian/echolot/etc/echolot/pingd.conf
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/clist.html echolot-2.1.9/debian/echolot/etc/echolot/templates/clist.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/echolot.css echolot-2.1.9/debian/echolot/etc/echolot/templates/echolot.css
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/echolot.html echolot-2.1.9/debian/echolot/etc/echolot/templates/echolot.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/fromlinesindex.html echolot-2.1.9/debian/echolot/etc/echolot/templates/fromlinesindex.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/mlist2.html echolot-2.1.9/debian/echolot/etc/echolot/templates/mlist2.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/mlist.html echolot-2.1.9/debian/echolot/etc/echolot/templates/mlist.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist2-clear.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist2-clear.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist2-dsa.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist2-dsa.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist2.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist2.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist2-rsa.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist2-rsa.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist-clear.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist-clear.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist-dsa.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist-dsa.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/rlist-rsa.html echolot-2.1.9/debian/echolot/etc/echolot/templates/rlist-rsa.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/thesaurusindex.html echolot-2.1.9/debian/echolot/etc/echolot/templates/thesaurusindex.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/v1legend.html echolot-2.1.9/debian/echolot/etc/echolot/templates/v1legend.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/echolot/templates/v2legend.html echolot-2.1.9/debian/echolot/etc/echolot/templates/v2legend.html
diff -ruNp echolot-2.1.9.orig/debian/echolot/etc/init.d/echolot echolot-2.1.9

Bug#831360: marked as done (/usr/bin/lush must not link libbfd-*-system.so dynamically)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 22:12:56 +
with message-id 
and subject line Bug#873146: Removed package(s) from unstable
has caused the Debian Bug report #831360,
regarding /usr/bin/lush must not link libbfd-*-system.so dynamically
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.)


-- 
831360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lush
Version: 1.2.1-9+cvs20110227+nmu1+b4
Severity: grave

/usr/bin/lush currently links libbfd dynamically. Since binutils 2.26.1,
that library went away but lush's dependency is still satisfied
resulting in a broken binary. Dynamically linking libbfd is not allowed
(see package description of binutils-dev).

Helmut
--- End Message ---
--- Begin Message ---
Version: 1.2.1-9+cvs20110227+nmu1.1+rm

Dear submitter,

as the package lush 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/873146

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#866639: marked as done (gnome-web-photo: depends on libwebkitgtk-3.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 22:11:28 +
with message-id 
and subject line Bug#873015: Removed package(s) from unstable
has caused the Debian Bug report #866639,
regarding gnome-web-photo: depends on libwebkitgtk-3.0-0 which 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.)


-- 
866639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-web-photo
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

gnome-web-photo depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
gnome-web-photo should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

If you have any question don't hesitate to ask.

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.10.6-1+rm

Dear submitter,

as the package gnome-web-photo 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/873015

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#666847: marked as done (mod-spamhaus: sourceful transition towards Apache 2.4)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 22:09:06 +
with message-id 
and subject line Bug#870996: Removed package(s) from unstable
has caused the Debian Bug report #666847,
regarding mod-spamhaus: sourceful transition towards Apache 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.)


-- 
666847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666847
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mod-spamhaus
Severity: important
User: debian-apa...@lists.debian.org
Usertags: apache24transition

Dear maintainer,

your package mod-spamhaus is provding an Apache2 web server module.
We're upgrading Apache to the new upstream version 2.4 [1] (tracked
as transition bug #661958). This requires all modules to be rebuilt
due to ABI changes.  Thus, you need to rebuild and reupload your
Apache2 module package in a version compatible to our new package
available in experimental [2].  Please note it is not enough to
simply rebuild the module - it needs some adaptions in the module
package metadata. We have written packaging guidelines for our
reverse dependencies [3]. Please read it carefully, it should be able
to answer most of your questions. Do also look at dh_apache2
(available through the dh-apache2 package) which can simplify
packaging Apache2 modules.  In short, we want to highlight these
changes you need to be aware of.

* APIs changed for some cases [3]. Chances are your module needs some
  adaptions, please get in touch with upstream or us if you need help
  to port your module to Apache 2.4.

* MPM packages are gone. You cannot depend or conflict with a
  particular MPM anymore. If your module does not work with a
  particular module, make sure to make it abort with an error if
  loaded together with an incompatible MPM. You can use our
  apache2-maintscript-helper [4] to switch to the MPM of your choice
  in your maintainer scripts. 

* Do not build-depend on apache2-threaded-dev or apache2-prefork-dev
  anymore. Just like MPMs are gone, are our MPM -dev packages as
  well. All modules need to simply build-depend on apache2-dev. 

* Do NOT depend on apache2, apache2-common or any other real apache2
  package in your binary module package. Depend on our virtual
  apache2-api-20120211 package only!

* Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our
  apache2-maintscript-helper [3] instead. This is required to get a
  uniform and stateful handling of all Apache2 modules.


You can look at our Apache 2.4 packaging hints [5] for hands-on
tutorials.  Please note: This bug is filed as "important" for now. As
the time goes by we plan make it a release critical severity. In the
consequences your module either needs an update or is going to be
removed from Wheezy. For the time being please tag the bug as pending
as soon as you have a package ready. We strongly recommend that at
least maintainers of complex module packages make an upload to
experimental as well. Of course, uploading simple modules to
experimental is welcome, too.

[1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html
[2] 
http://packages.debian.org/search?keywords=apache2&searchon=sourcenames&exact=1&suite=all§ion=all
[3] 
http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next
[4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html
[5] http://wiki.debian.org/Apache/PackagingFor24




--- End Message ---
--- Begin Message ---
Version: 0.7-1.1+rm

Dear submitter,

as the package mod-spamhaus 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/870996

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#784511: [pykde4] Qt4's WebKit removal

[Scott Kitterman]

On Wed, 6 May 2015 15:26:52 +0200 Ana Guerrero Lopez  wrote:
> Source: pykde4
> Version: 4:4.14.0-1
> Severity: wishlist
> User: debian-qt-...@lists.debian.org
> Usertags: qt4webkit-removal
> 
> Dear Debian Qt/KDE Maintainers ,
> 
> As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
> as announced in [announce].
> 
> [announce] 
> 
> 
> Basically we are about to get the latest Qt4 point release and upstream is
> migrating from WebKit to Bing in the Qt5 series, so we won't have much 
upstream
> support for maintaining Qt4's WebKit.
> 
> In order to make this move, all packages directly or indirectly depending on
> the Qt4's WebKit library have to either get ported to Qt5 or eventually get
> removed from the Debian repositories.
> 
Fixed in 4:4.14.3-3

Processed: fixed 784511 in 4:4.14.3-3

[Debian Bug Tracking System]

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

> fixed 784511 4:4.14.3-3
Bug #784511 [src:pykde4] [pykde4] Qt4's WebKit removal
Marked as fixed in versions pykde4/4:4.14.3-3.
> thanks
Stopping processing here.

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

Bug#872688: marked as done (galpy, hardcoded dependency on obsolete package libgsl2)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 21:49:43 +
with message-id 
and subject line Bug#872688: fixed in galpy 1.2-2
has caused the Debian Bug report #872688,
regarding galpy, hardcoded dependency on obsolete package libgsl2
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.)


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

Package: galpy
Version: 1.2-1
Severity: serious

After rebuilding for the libgsl transition python-galpy and python3-galpy now 
depend on both libgsl2 and libgsl23 due to a hardcoded dependency.

Removing the hardcoded dependency from the packaging is trivial and a quick 
grep of the source didn't show up any hardcoded references in the source tree 
itself but it would be good if someone who actually uses the package could 
check things out.
--- End Message ---
--- Begin Message ---
Source: galpy
Source-Version: 1.2-2

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

Debian distribution maintenance software
pp.
Josue Ortega  (supplier of updated galpy 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: Sat, 26 Aug 2017 13:24:52 -0600
Source: galpy
Binary: python-galpy python3-galpy
Architecture: source amd64
Version: 1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Josue Ortega 
Description:
 python-galpy - Python 2 package for galactic dynamics
 python3-galpy - Python 3 package for galactic dynamics
Closes: 872688
Changes:
 galpy (1.2-2) unstable; urgency=medium
 .
   * debian/control:
 - Removes unused dependency on libgsl2 (Closes: #872688).
 - Bumps Standards-Version to 4.0.1, no changes required.
Checksums-Sha1:
 101be85d9635aafbdbaf9f7972e736eda67103a2 2340 galpy_1.2-2.dsc
 2883e59b6bf0a6befd6657f330087e409123c0e4 2264 galpy_1.2-2.debian.tar.xz
 6309403dc348ca276f9c48171c9ce3561307351d 10180 galpy_1.2-2_amd64.buildinfo
 36005c3323709c30d09859ce5190884c07240017 118730 
python-galpy-dbgsym_1.2-2_amd64.deb
 ac227fef4f909d9cf5c6e854414f7cffb0b3a20c 291894 python-galpy_1.2-2_amd64.deb
 746d5615c6f81c16f042b25dff1b059ab7756477 118616 
python3-galpy-dbgsym_1.2-2_amd64.deb
 3481369c065bdec358647ad62206e3977d2c99e4 291958 python3-galpy_1.2-2_amd64.deb
Checksums-Sha256:
 10f26d38c071020342f0fbefc20c13245204e28cb4dc9980385e48c2f36ee0f1 2340 
galpy_1.2-2.dsc
 387055425fb5209e48dc1a33d94c40878e9fe49f41c9e3af7da182061112dcd1 2264 
galpy_1.2-2.debian.tar.xz
 ea98f21976f8d4b3711f249bde14e953a9cfa81a2719a7ec7ad16467f42ce760 10180 
galpy_1.2-2_amd64.buildinfo
 bad7c2946cf3b3346d0a166f3d9fd2ef9caad33860241f378227a3c1e4ed6f9e 118730 
python-galpy-dbgsym_1.2-2_amd64.deb
 739d6d09dbd9cd3f670788766ecc1d2457605d5be17565a83ced4bf8428eb0c6 291894 
python-galpy_1.2-2_amd64.deb
 85a060a6cb88dd21dff86fef9cad3e9d96d25d142137c4a8eb5d414a401adc04 118616 
python3-galpy-dbgsym_1.2-2_amd64.deb
 c46c0e0387a1395591ac3742917213089224ccc8ad3b830b610900e317b75bf8 291958 
python3-galpy_1.2-2_amd64.deb
Files:
 544e365dcd8ab79a63674830c6d2a0ff 2340 python optional galpy_1.2-2.dsc
 58b2ebf35d446df6a3a4610fb8a6a434 2264 python optional galpy_1.2-2.debian.tar.xz
 0d1038af59aacc81891b80b5882a7b8c 10180 python optional 
galpy_1.2-2_amd64.buildinfo
 32ddcf7f62be41b29198df1a74f80702 118730 debug extra 
python-galpy-dbgsym_1.2-2_amd64.deb
 0c11e8f8bb002e37bddb81e910ba3cf1 291894 python optional 
python-galpy_1.2-2_amd64.deb
 eb8ad28760ae33579ecac2482cbea4b0 118616 debug extra 
python3-galpy-dbgsym_1.2-2_amd64.deb
 8282527b89a83a02df2b8fc66608c778 291958 python optional 
python3-galpy_1.2-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAlmh40MRHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T+N0g/7BFQMr7PYF3ecu24ucH1jaMmAn9BqaYmk
zIRKuGT23DDWtOC54pNl6BRPVc+INSAJzQLAtIaal3T5oRw+sBbAjAM2NOyrr1ha
XKNzpw5QKw92QdlvtDrMSsI8iVFKVWJgIVjd+Q8i5X0RqRWiJ3NyBhtKfJGVNTO8
tvHp915M9eByj49LaRa3TDnASQHlmkzIdP+wLw1KiyAJ/MzAZU/25e39V8NtHoYT
7Hptzuv2Ez9+c1UNVWEYicJbyeqCzxc1lEqdLKV8G1Lnr+jBBG200f2JpaYXpBQG
MQ/

Bug#873357: marked as done (libluajit-5.1-dev: 2.1 update breaks r-deps includedir in pkgconfig file points to non-existent directory)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 23:37:21 +0200
with message-id 
and subject line Re: Bug#873324: minetest FTBFS with luajit 2.1
has caused the Debian Bug report #873357,
regarding libluajit-5.1-dev: 2.1 update breaks r-deps includedir in pkgconfig 
file points to non-existent directory
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.)


-- 
873357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libluajit-5.1-dev
Version: 2.1.0~beta3+dfsg-2
Severity: serious

Hi,

the recent upload of version 2.1 breaks reverse-dependencies due to a
non-existent includedir in the pkgconfig file. For instance see
#873324 and #873329.

includedir=${prefix}/include/luajit-${majver}.${minver}

=> /usr/include/luajit-2.1/

However the header files are installed under /usr/include/luajit-2.0/
and cannot be found anymore which causes the FTBFS in
reverse-dependencies. I suggest to install the header files into
/usr/include/luajit-2.1/ instead.

Regards,

Markus
--- End Message ---
--- Begin Message ---
Am 26.08.2017 um 23:30 schrieb Adrian Bunk:
> On Sat, Aug 26, 2017 at 11:14:33PM +0200, Markus Koschany wrote:
>> Am 26.08.2017 um 17:34 schrieb Adrian Bunk:
>>> Source: minetest
>>> Version: 0.4.16+repack-2
>>> Severity: serious
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minetest.html
>>>
>>> ...
>>> In file included from 
>>> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
>>> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: 
>>> fatal error: lua.h: No such file or directory
>>>  #include 
>>>   ^~~
>>> compilation terminated.
>>> src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
>>> 'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
>>> make[3]: *** 
>>> [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] Error 1
>>>
>>
>> Thank you for the report. These issues are caused by a
>> non-existent/wrong include directory in libluajit-5.1-dev though.
>> I have filed [1] a few minutes ago.
>>
>> [1] https://bugs.debian.org/873357
> 
> Can you double-check what you wrote in that bug?
> 
> For me (on amd64) lua.h is already correctly under 
> /usr/include/luajit-2.1 and "pkg-config --cflags luajit"
> gives the right flag.
> 
> minetest hardcoding include/luajit-2.0 is the actual bug.

It seems this page [1] is outdated hence the wrong conclusion. Closing
#873357 again.

[1] https://packages.debian.org/sid/amd64/libluajit-5.1-dev/filelist






signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#873324: minetest FTBFS with luajit 2.1

[Markus Koschany]

Am 26.08.2017 um 23:30 schrieb Adrian Bunk:
> On Sat, Aug 26, 2017 at 11:14:33PM +0200, Markus Koschany wrote:
>> Am 26.08.2017 um 17:34 schrieb Adrian Bunk:
>>> Source: minetest
>>> Version: 0.4.16+repack-2
>>> Severity: serious
>>>
>>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minetest.html
>>>
>>> ...
>>> In file included from 
>>> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
>>> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: 
>>> fatal error: lua.h: No such file or directory
>>>  #include 
>>>   ^~~
>>> compilation terminated.
>>> src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
>>> 'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
>>> make[3]: *** 
>>> [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] Error 1
>>>
>>
>> Thank you for the report. These issues are caused by a
>> non-existent/wrong include directory in libluajit-5.1-dev though.
>> I have filed [1] a few minutes ago.
>>
>> [1] https://bugs.debian.org/873357
> 
> Can you double-check what you wrote in that bug?
> 
> For me (on amd64) lua.h is already correctly under 
> /usr/include/luajit-2.1 and "pkg-config --cflags luajit"
> gives the right flag.
> 
> minetest hardcoding include/luajit-2.0 is the actual bug.

It seems this page [1] is outdated hence the wrong conclusion. Closing
#873357 again.

[1] https://packages.debian.org/sid/amd64/libluajit-5.1-dev/filelist






signature.asc
Description: OpenPGP digital signature

Processed: Not relevant for jessie or stretch

[Debian Bug Tracking System]

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

> tags 784448 buster sid
Bug #784448 [src:amarok] [amarok] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784449 buster sid
Bug #784449 [src:acetoneiso] [acetoneiso] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784451 buster sid
Bug #784451 [src:ball] [ball] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784453 buster sid
Bug #784453 [src:brewtarget] [brewtarget] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784462 buster sid
Bug #784462 [src:fcitx-libpinyin] [fcitx-libpinyin] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784464 buster sid
Bug #784464 [src:freecad] [freecad] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784468 buster sid
Bug #784468 [src:goldendict] [goldendict] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784475 buster sid
Bug #784475 [src:kbibtex] [kbibtex] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784476 buster sid
Bug #784476 [src:kchmviewer] [kchmviewer] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784477 buster sid
Bug #784477 [src:kde-runtime] [kde-runtime] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784480 buster sid
Bug #784480 [src:kdepim4] [kdepim4] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784486 buster sid
Bug #784486 [src:krecipes] [krecipes] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784487 buster sid
Bug #784487 [src:ktorrent] [ktorrent] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784490 buster sid
Bug #784490 [src:kvirc] [kvirc] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784501 buster sid
Bug #784501 [src:nmapsi4] [nmapsi4] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784505 buster sid
Bug #784505 [src:paraview] [paraview] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784509 buster sid
Bug #784509 [src:postbooks-updater] [postbooks-updater] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784510 buster sid
Bug #784510 [src:psi-plus] [psi-plus] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784511 buster sid
Bug #784511 [src:pykde4] [pykde4] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 784512 buster sid
Bug #784512 [src:pyside] [pyside] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784518 buster sid
Bug #784518 [src:qtscriptgenerator] [qtscriptgenerator] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784524 buster sid
Bug #784524 [src:robojournal] [robojournal] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 784560 buster sid
Bug #784560 [src:webkitkde] [webkitkde] Qt4's WebKit removal
Added tag(s) buster and sid.
> tags 816804 buster sid
Bug #816804 [src:bibletime] [bibletime] Qt4's WebKit removal
Added tag(s) sid and buster.
> tags 867306 buster sid
Bug #867306 [src:gambas3] gambas3: spurious libqtwebkit-dev build dependency
Added tag(s) sid and buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
784448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784448
784449: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784449
784451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784451
784453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784453
784462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784462
784464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784464
784468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784468
784475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784475
784476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784476
784477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784477
784480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784480
784486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784486
784487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784487
784490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784490
784501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784501
784505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784505
784509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784509
784510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784510
784511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784511
784512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784512
784518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784518
784524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784524
784560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784560
816804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816804
867306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#873324: minetest FTBFS with luajit 2.1

[Adrian Bunk]

On Sat, Aug 26, 2017 at 11:14:33PM +0200, Markus Koschany wrote:
> Am 26.08.2017 um 17:34 schrieb Adrian Bunk:
> > Source: minetest
> > Version: 0.4.16+repack-2
> > Severity: serious
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minetest.html
> > 
> > ...
> > In file included from 
> > /build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
> > /build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: 
> > fatal error: lua.h: No such file or directory
> >  #include 
> >   ^~~
> > compilation terminated.
> > src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
> > 'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
> > make[3]: *** 
> > [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] Error 1
> > 
> 
> Thank you for the report. These issues are caused by a
> non-existent/wrong include directory in libluajit-5.1-dev though.
> I have filed [1] a few minutes ago.
> 
> [1] https://bugs.debian.org/873357

Can you double-check what you wrote in that bug?

For me (on amd64) lua.h is already correctly under 
/usr/include/luajit-2.1 and "pkg-config --cflags luajit"
gives the right flag.

minetest hardcoding include/luajit-2.0 is the actual bug.

> Regards,
> 
> Markus

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

Bug#873324: minetest FTBFS with luajit 2.1

[Markus Koschany]

Am 26.08.2017 um 17:34 schrieb Adrian Bunk:
> Source: minetest
> Version: 0.4.16+repack-2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minetest.html
> 
> ...
> In file included from 
> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
> /build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: fatal 
> error: lua.h: No such file or directory
>  #include 
>   ^~~
> compilation terminated.
> src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
> 'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
> make[3]: *** 
> [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] Error 1
> 

Thank you for the report. These issues are caused by a
non-existent/wrong include directory in libluajit-5.1-dev though.
I have filed [1] a few minutes ago.

[1] https://bugs.debian.org/873357

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#853375: C++ help needed (Was: Bug#853375: disulfinder: ftbfs with GCC-7)

[Christian Seiler]

Hi Andreas,

On 08/26/2017 10:08 PM, Andreas Tille wrote:
> I moved disulfinder to Git[1] and tried to track down this issue with my
> limited C++ knowledge but failed.  The issue is
> 
> ...
> make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/build/disulfinder-1.2.11=. -fstack-protector-strong 
> -Wformat -Werror=format-security -DDEFAULT_PKGDATADIR=\"/usr/share/disulfind
> In file included from Input/utils.h:1:0,
>  from Input/GlobalDescriptor.cpp:3:
> Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
> DATATYPE*)':
> Input/../Common/Matrix.h:208:3: error: 'Exception' has not been declared
>Exception::Assert(nrows>0 && ncols>0,"construction of empty matrix");
>^
> Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
> const DATATYPE&)':
> Input/../Common/Matrix.h:221:3: error: 'Exception' has not been declared
>Exception::Assert(nrows>0 && ncols>0,"construction of empty matrix");
>^
> Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
> DATATYPE**)':
> Input/../Common/Matrix.h:232:3: error: 'Exception' has not been declared
>Exception::Assert(nrows>0 && ncols>0, "construction of empty matrix");
>^
> Input/../Common/Matrix.h: In member function 'void 
> Matrix::Resize(int, int)':
> Input/../Common/Matrix.h:288:3: error: 'Exception' has not been declared
>Exception::Assert(nrows>0 && ncols>0, "construction of empty matrix");
>^
> ...
> 
> 
> As far as I can see Exception is declared in
>disulfind/src/Common/Exception.h
> which is also included in Matrix.h.
> 
> Any hint what might be wrong here?

Common/Exception.h uses __EXCEPTION_H as its include guard macro name (so
that it's included only once) - unfortunately  from
GCC7 uses the same guard macro name. Hence Common/Exception.h is not
actually processed in your case.

The bug is in your package, see
https://stackoverflow.com/a/228797
for a summary of the rules regarding identifiers in C++; the guard macro
name clearly intrudes on the namespace reserved for the compiler.

Change the guard macro name to something else, e.g.

#ifndef DISULFIND_COMMON_EXCEPTION_H
#define DISULFIND_COMMON_EXCEPTION_H

and then it should work again in GCC7.

Regards,
Christian

Bug#873357: libluajit-5.1-dev: 2.1 update breaks r-deps includedir in pkgconfig file points to non-existent directory

[Markus Koschany]

Package: libluajit-5.1-dev
Version: 2.1.0~beta3+dfsg-2
Severity: serious

Hi,

the recent upload of version 2.1 breaks reverse-dependencies due to a
non-existent includedir in the pkgconfig file. For instance see
#873324 and #873329.

includedir=${prefix}/include/luajit-${majver}.${minver}

=> /usr/include/luajit-2.1/

However the header files are installed under /usr/include/luajit-2.0/
and cannot be found anymore which causes the FTBFS in
reverse-dependencies. I suggest to install the header files into
/usr/include/luajit-2.1/ instead.

Regards,

Markus

Bug#853375: C++ help needed (Was: Bug#853375: disulfinder: ftbfs with GCC-7)

[Andreas Tille]

Hi,

I moved disulfinder to Git[1] and tried to track down this issue with my
limited C++ knowledge but failed.  The issue is

...
make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/build/disulfinder-1.2.11=. -fstack-protector-strong 
-Wformat -Werror=format-security -DDEFAULT_PKGDATADIR=\"/usr/share/disulfind
In file included from Input/utils.h:1:0,
 from Input/GlobalDescriptor.cpp:3:
Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
DATATYPE*)':
Input/../Common/Matrix.h:208:3: error: 'Exception' has not been declared
   Exception::Assert(nrows>0 && ncols>0,"construction of empty matrix");
   ^
Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
const DATATYPE&)':
Input/../Common/Matrix.h:221:3: error: 'Exception' has not been declared
   Exception::Assert(nrows>0 && ncols>0,"construction of empty matrix");
   ^
Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
DATATYPE**)':
Input/../Common/Matrix.h:232:3: error: 'Exception' has not been declared
   Exception::Assert(nrows>0 && ncols>0, "construction of empty matrix");
   ^
Input/../Common/Matrix.h: In member function 'void 
Matrix::Resize(int, int)':
Input/../Common/Matrix.h:288:3: error: 'Exception' has not been declared
   Exception::Assert(nrows>0 && ncols>0, "construction of empty matrix");
   ^
...


As far as I can see Exception is declared in
   disulfind/src/Common/Exception.h
which is also included in Matrix.h.

Any hint what might be wrong here?

Kind regards

   Andreas.


[1] https://anonscm.debian.org/git/debian-med/disulfinder.git

-- 
http://fam-tille.de

Bug#853375: C++ help needed (Was: Bug#853375: disulfinder: ftbfs with GCC-7)

[James Cowgill]

Hi,

On 26/08/17 21:08, Andreas Tille wrote:
> Hi,
> 
> I moved disulfinder to Git[1] and tried to track down this issue with my
> limited C++ knowledge but failed.  The issue is
> 
> ...
> make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/build/disulfinder-1.2.11=. -fstack-protector-strong 
> -Wformat -Werror=format-security -DDEFAULT_PKGDATADIR=\"/usr/share/disulfind
> In file included from Input/utils.h:1:0,
>  from Input/GlobalDescriptor.cpp:3:
> Input/../Common/Matrix.h: In constructor 'Matrix::Matrix(int, int, 
> DATATYPE*)':
> Input/../Common/Matrix.h:208:3: error: 'Exception' has not been declared
>Exception::Assert(nrows>0 && ncols>0,"construction of empty matrix");
>^

The problem is the include guard in Exception.h.

Common/Exception.h:
#define __EXCEPTION_H

By luck, this happens to collide with the include guard used by gcc-7's
exception.h header which is pulled in by some standard library includes.

/usr/include/c++/7/bits/exception.h:
#define __EXCEPTION_H 1

This means that nothing from Exception.h ever gets defined if
exception.h gets included first. disulfind is wrong here because the C++
standard explicitly states that all identifiers beginning with two
underscores are reserved.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#873318: marked as done (jellyfish does not actually disable parallel building)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 20:50:55 +
with message-id 
and subject line Bug#873318: fixed in jellyfish 2.2.6-3
has caused the Debian Bug report #873318,
regarding jellyfish does not actually disable parallel building
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.)


-- 
873318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jellyfish
Version: 2.2.6-2
Severity: serious

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

...
lib/.libs/jsoncpp.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:1193: recipe for target 'libjellyfish-2.0.la' failed
make[2]: *** [libjellyfish-2.0.la] Error 1



 jellyfish (2.2.6-2) unstable; urgency=medium
...
   * debhelper 10
   * Parallel builds seem to cause problems - use --no-parallel



%:
dh $@ --with autoreconf,python3 #--parallel



dh compat 10 does default to parallel,
explicit --no-parallel is required.
--- End Message ---
--- Begin Message ---
Source: jellyfish
Source-Version: 2.2.6-3

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated jellyfish package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Aug 2017 21:53:10 +0200
Source: jellyfish
Binary: jellyfish libjellyfish-2.0-2 libjellyfish-2.0-dev python3-dna-jellyfish 
libjellyfish-perl jellyfish-examples
Architecture: source amd64
Version: 2.2.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 jellyfish  - count k-mers in DNA sequences
 jellyfish-examples - count k-mers in DNA sequences (examples for testing)
 libjellyfish-2.0-2 - count k-mers in DNA sequences (dynamic library of 
jellyfish)
 libjellyfish-2.0-dev - count k-mers in DNA sequences (development files of 
jellyfish)
 libjellyfish-perl - count k-mers in DNA sequences (Perl bindings of jellyfish)
 python3-dna-jellyfish - count k-mers in DNA sequences (Python bindings of 
jellyfish)
Closes: 873318
Changes:
 jellyfish (2.2.6-3) unstable; urgency=medium
 .
   * Explicitly disable parallel building
 Closes: #873318
Checksums-Sha1:
 f63f3eb1b24784566165b246d6d971e4a00f1913 2589 jellyfish_2.2.6-3.dsc
 a1a298a08074ae792d6f6a62bd7d26dd2deebd9a 11872 jellyfish_2.2.6-3.debian.tar.xz
 fcfff48e9922470a9b6a5c1e786a97d08896bfd3 1286630 
jellyfish-dbgsym_2.2.6-3_amd64.deb
 64df59609a26016513d091a1158959e831e6dc69 4704650 
jellyfish-examples-dbgsym_2.2.6-3_amd64.deb
 1cc0cdf549b985873272a06d7b3a7ed7499f34fc 489900 
jellyfish-examples_2.2.6-3_amd64.deb
 5a8e8524067fdad121132b6ac9a1d2c57999eec5 10228 
jellyfish_2.2.6-3_amd64.buildinfo
 9b001830e9e7797c0c05be415419a7958e3b7e7f 358710 jellyfish_2.2.6-3_amd64.deb
 0bde2bdef0c5f6d916931b174602d2aca5925220 420528 
libjellyfish-2.0-2-dbgsym_2.2.6-3_amd64.deb
 855077f4fc0f7034803265a32130fae866b5bfde 63022 
libjellyfish-2.0-2_2.2.6-3_amd64.deb
 c8a140d8569fc164b8fa8ea2bc47d0fb0821067a 129696 
libjellyfish-2.0-dev_2.2.6-3_amd64.deb
 a74e31acaac47d9c370b719bc57ef0f38a8dd10d 288622 
libjellyfish-perl-dbgsym_2.2.6-3_amd64.deb
 814131611dfdfd4b213fd409c55a8d1810379ee9 55124 
libjellyfish-perl_2.2.6-3_amd64.deb
 837c875ab9bba5b8aad3132ecae863bc04f2491b 482666 
python3-dna-jellyfish-dbgsym_2.2.6-3_amd64.deb
 627e43efc15b2a6a5aa952303bb6717fe4fdd809 51418 
python3-dna-jellyfish_2.2.6-3_amd64.deb
Checksums-Sha256:
 ead35579e42edb7fa91b929d985b62ea0f425f9126b6e11581f4ae28ee30fc68 2589 
jellyfish_2.2.6-3.dsc
 9f6278d9586fe3a2523d0634807600759423920ec54c910fa256870150da90d0 11872 
jellyfish_2.2.6-3.debian.tar.xz
 8b2a0a027835ecc7ce2d40ae5b3e44b2055ae422cd8dfa876e7872c5732be85c 1286630 
jellyfish-dbgsym_2.2.6-3_amd64.deb
 65b5c2944ef4c6c46bfda9060c9fe9a0cefee499a6b3d01a1bc506d714cfc33c 4704650 
jellyfish-examples-dbgsym_2.2.6-3_amd64.deb
 78a421b20635c6e5c86e2c1249d878eb350ab633a7999a6e9185d80f3372c717 489900 
jellyfish-examples_2.2.6

Bug#868854: marked as pending

[Fabian Greffrath]

tag 868854 pending
thanks

Hello,

Bug #868854 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://anonscm.debian.org/git/pkg-multimedia/faad2.git/commit/?id=8d60f32

---
commit 8d60f326aa15111f433ca194ee5b31883160d5fd
Author: Fabian Greffrath 
Date:   Wed Aug 2 20:47:26 2017 +0200

update debian/changelog

diff --git a/debian/changelog b/debian/changelog
index 7987cb6..9a589b3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+faad2 (2.8.1-2) unstable; urgency=medium
+
+  * Set the FAAD2_VERSION macro back to the version string,
+thanks Adrian Bunk (Closes: #868854).
++ In the next upstream release this macro will read "unknown version"
+  and an API will be provided to retrieve the actual library version
+  at run-time.
+
+ -- Fabian Greffrath   Wed, 02 Aug 2017 20:46:57 +0200
+
 faad2 (2.8.1-1) unstable; urgency=medium
 
   * New upstream version 2.8.1.

Bug#873345: bugwarrior: Fix hard-coded reference to python3.5

[Steve Langasek]

Package: bugwarrior
Version: 1.5.1-1
Severity: serious
Tags: patch
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

bugwarrior 1.5.1-1 has a hard-coded reference to python3.5 in debian/rules. 
The transition to python3.6 is already in progress in Debian unstable, and
this will imminently become a build failure in unstable because python3-all
will no longer depend on python3.5.

   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir test_home
HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3.5 -m nose
/bin/sh: 1: python3.5: not found
debian/rules:11: recipe for target 'override_dh_auto_test' failed

python3.5 has already been dropped from Ubuntu, so I've applied the attached
patch and uploaded there.

Since bugwarrior does build-depend on python3-all rather than on python3,
it's possible you want to do something with py3versions here instead in
order to test against all currently supported versions of python3.  However,
this is only relevant a small percentage of the release cycle, so is IMHO of
lesser importance than just making the package buildable.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru bugwarrior-1.5.1/debian/rules bugwarrior-1.5.1/debian/rules
--- bugwarrior-1.5.1/debian/rules   2017-08-21 03:40:46.0 -0700
+++ bugwarrior-1.5.1/debian/rules   2017-08-26 13:24:00.0 -0700
@@ -9,7 +9,7 @@
 
 override_dh_auto_test:
mkdir test_home
-   HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3.5 -m nose
+   HOME=`pwd`/test_home LC_ALL=C.UTF-8 python3 -m nose
 
 override_dh_auto_clean:
-rm -rf test_home

Processed: Bug#868854 marked as pending

[Debian Bug Tracking System]

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

> tag 868854 pending
Bug #868854 {Done: Fabian Greffrath } [libfaad-dev] 
libfaad-dev: neaacdec.h contains PACKAGE_VERSION instead of the actual version
Bug #868915 {Done: Fabian Greffrath } [libfaad-dev] gpac: 
FTBFS: faad_dec.c:408:35: error: expected ';' before 'PACKAGE_VERSION'
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784612 [src:anki] [anki] Qt4's WebKit removal
Severity set to 'serious' from 'grave'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784518 [src:qtscriptgenerator] [qtscriptgenerator] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784615 [src:ninja-ide] [ninja-ide] Qt4's WebKit removal
Ignoring request to change severity of Bug 784615 to the same value.

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #816808 [src:gpsbabel] [gpsbabel] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Bug#784612: Qt4 WebKit removal: raising severity to serious

[Dmitry Shachnev]

Control: severity -1 serious

Dear maintainer(s),

As recently announced [1], we are going to remove not only Qt 4 WebKit, but
Qt 4 as a whole in Buster. As removing Qt 4 WebKit is the first step, I am
raising the severity of this bug to serious.

Please port your package to Qt 5 if you do not want to get it removed from
Debian. In Qt 5, the WebKit module is supported, and we are currently
preparing a major update based on 5.212 branch [2].

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
[2]: https://code.qt.io/cgit/qt/qtwebkit.git/log/?h=5.212

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784559 [src:webkit-image] [webkit-image] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784524 [src:robojournal] [robojournal] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #816804 [src:bibletime] [bibletime] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784502 [src:openms] [openms] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784477 [src:kde-runtime] [kde-runtime] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784509 [src:postbooks-updater] [postbooks-updater] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784476 [src:kchmviewer] [kchmviewer] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784490 [src:kvirc] [kvirc] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #867306 [src:gambas3] gambas3: spurious libqtwebkit-dev build dependency
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784510 [src:psi-plus] [psi-plus] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784560 [src:webkitkde] [webkitkde] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784512 [src:pyside] [pyside] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784511 [src:pykde4] [pykde4] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784501 [src:nmapsi4] [nmapsi4] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784487 [src:ktorrent] [ktorrent] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784505 [src:paraview] [paraview] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784486 [src:krecipes] [krecipes] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784475 [src:kbibtex] [kbibtex] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784453 [src:brewtarget] [brewtarget] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784471 [src:k3b] [k3b] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784468 [src:goldendict] [goldendict] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784480 [src:kdepim4] [kdepim4] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784462 [src:fcitx-libpinyin] [fcitx-libpinyin] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784450 [src:arc-gui-clients] [arc-gui-clients] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784479 [src:kde4libs] [kde4libs] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784448 [src:amarok] [amarok] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784449 [src:acetoneiso] [acetoneiso] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784451 [src:ball] [ball] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Processed: Qt4 WebKit removal: raising severity to serious

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #784464 [src:freecad] [freecad] Qt4's WebKit removal
Severity set to 'serious' from 'important'

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

Bug#870253: clamav-milter: disengaging debconf management destroys config

[Sebastian Andrzej Siewior]

On 2017-08-22 21:21:14 [+0200], To Marc Dequènes wrote:
> @team: any opinion here?

I am going to drop that part where the debconf created file gets
overwritten with the sample file. Need to test before I commit it…

Sebastian

Bug#873275: always segfaults at start due to QSslSocket

[Lisandro Damián Nicanor Pérez Meyer]

On sábado, 26 de agosto de 2017 17:39:28 -03 Sebastiaan Couwenberg wrote:
[snip] 
> > Sebastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is
> > the qt5 port going?
> 
> Qt5 support will be available in QGIS 3.0.0 due in November this year,
> the 3.x release will need some time to mature to a long term release
> we'll include in Debian. The QGIS 3.4 LTR is due in November 2018. [0]
> 
> We could include QGIS 3.0.0 in Debian in the mean time and switch back
> to the LTR releases a year later to not hold up to Qt4 removal too much.
> Although I'd rather stick to the LTR releases in Debian.

That sounds truly achievable. I really don't think we would be able to remove 
Qt4 this year *but* I can't control OpenSSL 1.0 removal. If that happens I 
have no other choice than removing SSL support.

Cheers!

-- 
  "Waaah! Debian never keeps its release schedules!"
Okay, lets make a Debian-like distribution that hits its schedules and is
close to bleeding edge.
  "Waaah! Ubuntu ships buggy stuff!"
Grr.
(Not aimed at jwb in particular, BTW. Just pointing out that there's always
going to be some disappointed people.)
  vmole (subscriber, #111) - http://lwn.net/Articles/279111/

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#873341: SBT is uninstallable; depends on nonexistent packages

[David Starner]

Package: sbt
Version: 0.13.13-2
Severity: serious

sbt is not installable; it depends on various packages like
sbt-test-interface that only exist in experimental.

Bug#817643: qingy: Removal of debhelper compat 4

[Steve Langasek]

Package: qingy
Followup-For: Bug #817643
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hello,

Attached is the trivial patch to qingy to fix it for this serious bug. 
Since qingy needed to be rebuilt for the libdirectfb transition, I have
uploaded this change to Ubuntu.

Of course, this is not the only part of qingy's packaging which is quite
outdated; lintian turns up quite a few other issues that are worth looking at:

$ lintian -I qingy*changes
W: qingy source: dh-clean-k-is-deprecated
W: qingy source: useless-autoreconf-build-depends autotools-dev
I: qingy source: missing-debian-source-format
W: qingy source: debian-rules-missing-recommended-target build-indep
W: qingy source: debian-rules-missing-recommended-target build-arch
W: qingy source: ancient-standards-version 3.8.0 (current is 4.0.0)
I: qingy source: testsuite-autopkgtest-missing
I: qingy: hardening-no-bindnow usr/lib/qingy/libqingy-0.9.7.so
I: qingy: hardening-no-bindnow usr/lib/qingy/screensavers/photos.qss
I: qingy: hardening-no-bindnow usr/lib/qingy/screensavers/pixel.qss
I: qingy: hardening-no-bindnow ... use --no-tag-display-limit to see all (or 
pipe to a file/program)
I: qingy: font-in-non-font-package usr/share/qingy/themes/default/decker.ttf
E: qingy: non-empty-dependency_libs-in-la-file usr/lib/qingy/libqingy.la
$

Updating the packaging to use dh(1) would address many of these.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -u qingy-0.9.7/debian/compat qingy-0.9.7/debian/compat
--- qingy-0.9.7/debian/compat
+++ qingy-0.9.7/debian/compat
@@ -1 +1 @@
-4
+10
diff -u qingy-0.9.7/debian/control qingy-0.9.7/debian/control
--- qingy-0.9.7/debian/control
+++ qingy-0.9.7/debian/control
@@ -2,7 +2,7 @@
 Section: admin
 Priority: optional
 Maintainer: Riccardo Stagni 
-Build-Depends: debhelper (>= 4.0.0), autotools-dev, libdirectfb-dev, 
libncurses5-dev, libpam0g-dev, pkg-config, x11proto-scrnsaver-dev, libxss-dev, 
xinit
+Build-Depends: debhelper (>= 10), autotools-dev, libdirectfb-dev, 
libncurses5-dev, libpam0g-dev, pkg-config, x11proto-scrnsaver-dev, libxss-dev, 
xinit
 Standards-Version: 3.8.0
 Homepage: http://qingy.sourceforge.net/
 

Processed: Justification for severity 'grave'?

[Debian Bug Tracking System]

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

> severity 872555 important
Bug #872555 [fcitx] fcitx: 在gnome不能切换输入法，在xfce可以
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#873231: rapidjson: FTBFS in experimental

[Rene Engelhard]

On Fri, Aug 25, 2017 at 06:47:10PM +0200, Christoph Biedl wrote:
> This has been fixed upstream. Please cherry-pick
> https://github.com/miloyip/rapidjson/commit/fe19b7b6016d446722621fb407738209d1a911e8
> If you want to be nice to private backporters, please cherry-pick
> the follow-up commit
> https://github.com/miloyip/rapidjson/commit/cba45fe9de6923b858edb0780e257b7257aa4f7b
> as well so the fix will not break builds when using older gcc versions.

While these upstream commits work, imho they are only a bit correct.
A correct fix would be to disable -Werror alltogether.
That "fix" above is just "do not emit a warning for this" anyway.

That would also help for future changes... :)

Regards,

Rene

Bug#873275: always segfaults at start due to QSslSocket

[Sebastiaan Couwenberg]

On 08/26/2017 03:28 PM, Lisandro Damián Nicanor Pérez Meyer wrote:
> On sábado, 26 de agosto de 2017 15:50:14 -03 Adrian Bunk wrote:
>> On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez 
> Meyer wrote:
>>> First of all sorry for the top posting. Actually this is not a bug in qt4,
>>> OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.
>>
>> That's clear.
>>
>>> I uploaded
>>> to experimental for people to check, so actually this should be an
>>> important bug against qgis. If necessary I'll explain more with a more
>>> comfortable mail client at hand.
>>
>> The problem as reported by Dan and reproduced by me is:
> [snip] 
>> To me this looks like qt4 built with OpenSSL 1.1 trying to use functions
>> that were removed in OpenSSL 1.1, example:
>>
>>   /usr/include/openssl/ssl.h:#define SSLv23_client_method   
>> TLS_client_method
>>
>>
>> In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this
>> from libssl.so.1.1 cannot work.
> 
> Indeed, so the upload did work after all: we now know that the proposed patch 
> is not enough.
> 
> Sebastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is the 
> qt5 port going?

Qt5 support will be available in QGIS 3.0.0 due in November this year,
the 3.x release will need some time to mature to a long term release
we'll include in Debian. The QGIS 3.4 LTR is due in November 2018. [0]

We could include QGIS 3.0.0 in Debian in the mean time and switch back
to the LTR releases a year later to not hold up to Qt4 removal too much.
Although I'd rather stick to the LTR releases in Debian.

[0]
http://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



signature.asc
Description: OpenPGP digital signature

Bug#873327: aegisub FTBFS with luajit 2.1

[Adrian Bunk]

Source: aegisub
Version: 3.2.2+dfsg-3
Severity: serious
Tags: buster sid

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

...
/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.c:2337:24: error: 
array type has incomplete element type 'struct luaL_reg'
 static struct luaL_reg pattreg[] = {
^~~
/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.c:2363:24: error: 
array type has incomplete element type 'struct luaL_reg'
 static struct luaL_reg metapattreg[] = {
^~~
/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.c:2363:24: warning: 
'metapattreg' defined but not used [-Wunused-variable]
/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.c:2337:24: warning: 
'pattreg' defined but not used [-Wunused-variable]
 static struct luaL_reg pattreg[] = {
^~~
Makefile.target:99: recipe for target 
'/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.o' failed
make[1]: *** [/build/1st/aegisub-3.2.2+dfsg/libaegisub/lua/modules/lpeg.o] 
Error 1

Bug#873328: trafficserver FTBFS with luajit 2.1

[Adrian Bunk]

Source: trafficserver
Version: 7.0.0-5
Severity: serious
Tags: buster sid

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

...
In file included from repl.cc:25:0:
bindings.h:65:67: error: 'luaL_reg' does not name a type; did you mean 
'luaL_ref'?
   static void register_metatable(lua_State *, const char *, const luaL_reg *);
   ^~~~
   luaL_ref
Makefile:716: recipe for target 'repl.lo' failed
make[4]: *** [repl.lo] Error 1

Bug#873329: love FTBFS with luajit 2.1

[Adrian Bunk]

Source: love
Version: 0.9.1-4
Severity: serious
Tags: buster sid

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

...
In file included from libraries/luasocket/libluasocket/udp.c:12:0:
libraries/luasocket/libluasocket/auxiliar.h:38:61: error: unknown type name 
'luaL_reg'; did you mean 'luaL_Reg'?
 void auxiliar_newclass(lua_State *L, const char *classname, luaL_reg *func);
 ^~~~
 luaL_Reg

Bug#873326: sysdig FTBFS with luajit 2.1

[Adrian Bunk]

Source: sysdig
Version: 0.17.0-1
Severity: serious

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

...
-- Could NOT find Lua51 (missing: LUA_LIBRARIES LUA_INCLUDE_DIR) 
CMake Error at CMakeLists.txt:117 (message):
  Couldn't find system LuaJIT or Lua


-- Configuring incomplete, errors occurred!

Bug#873325: fastnetmon FTBFS with luajit 2.1

[Adrian Bunk]

Source: fastnetmon
Version: 1.1.3+dfsg-2
Severity: serious

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

...
In file included from /build/1st/fastnetmon-1.1.3+dfsg/src/fast_library.cpp:3:0:
/build/1st/fastnetmon-1.1.3+dfsg/src/fast_library.h:28:10: fatal error: 
luajit-2.0/lua.hpp: No such file or directory
 #include 
  ^~~~
compilation terminated.
CMakeFiles/fast_library.dir/build.make:65: recipe for target 
'CMakeFiles/fast_library.dir/fast_library.cpp.o' failed

Bug#873324: minetest FTBFS with luajit 2.1

[Adrian Bunk]

Source: minetest
Version: 0.4.16+repack-2
Severity: serious

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

...
In file included from 
/build/1st/minetest-0.4.16+repack/src/script/common/c_content.cpp:19:0:
/build/1st/minetest-0.4.16+repack/src/script/common/c_content.h:32:10: fatal 
error: lua.h: No such file or directory
 #include 
  ^~~
compilation terminated.
src/CMakeFiles/minetestserver.dir/build.make:161: recipe for target 
'src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o' failed
make[3]: *** [src/CMakeFiles/minetestserver.dir/script/common/c_content.cpp.o] 
Error 1

Bug#873322: bpfcc FTBFS with luajit 2.1

[Adrian Bunk]

Source: bpfcc
Version: 0.3.0-1
Severity: serious

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

...
-- Could NOT find LuaJIT (missing: LUAJIT_INCLUDE_DIR) 
CMake Warning at tests/python/CMakeLists.txt:6 (message):
  Recommended test program 'arping' not found


CMake Warning at tests/python/CMakeLists.txt:10 (message):
  Recommended test program 'netperf' not found


CMake Warning at tests/python/CMakeLists.txt:14 (message):
  Recommended test program 'iperf' not found


CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
LUAJIT_INCLUDE_DIR (ADVANCED)
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua
   used as include directory in directory /build/1st/bpfcc-0.3.0/src/lua

-- Configuring incomplete, errors occurred!

Bug#873321: wrk FTBFS with luajit 2.1

[Adrian Bunk]

Source: wrk
Version: 4.0.2-2
Severity: serious

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

...
CC src/wrk.c
In file included from /usr/include/pthread.h:21:0,
 from src/wrk.h:5,
 from src/wrk.c:3:
/usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
 # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
   ^~~
In file included from src/wrk.c:3:0:
src/wrk.h:13:10: fatal error: luajit-2.0/lua.h: No such file or directory
 #include 
  ^~
compilation terminated.
Makefile:58: recipe for target 'obj/wrk.o' failed
make[2]: *** [obj/wrk.o] Error 1

Bug#873319: nginx FTBFS with luajit 2.1

[Adrian Bunk]

Source: nginx
Version: 1.13.3-1
Severity: serious

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

...
checking for PCRE JIT support ...checking for PCRE library ... found
 + ngx_nchan_module was configured
adding module in /build/1st/nginx-1.13.3/debian/modules/nginx-lua
checking for Lua library ... not found
checking for Lua library in /usr/local/ ... found
 found
checking for OpenSSL library ...checking for PCRE JIT support ... not found
checking for Lua library in /usr/local/ ... not found
checking for Lua library in /usr/pkg/ ... found
checking for OpenSSL library ... not found
checking for Lua library in /opt/local/ ... not found
checking for Lua library in /usr/local/*/lua51/ ... not found
checking for Lua library in /usr/ ... not found
checking for LuaJIT library in /usr/local/ ... not found
checking for LuaJIT library in /usr/ ... found
 not found
checking for zlib library ...checking for LuaJIT library in /usr/ ... not found
 ./configure: error: ngx_http_lua_module requires the Lua library.
debian/rules:183: recipe for target 'config.arch.extras' failed
make[1]: *** [config.arch.extras] Error 1

Bug#873320: ettercap FTBFS with luajit 2.1

[Adrian Bunk]

Source: ettercap
Version: 1:0.8.2-6
Severity: serious
Tags: buster sid

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

...
-- Couldn't find a suitable system-provided version of LuaJIT
CMake Error at cmake/Modules/EttercapLuajit.cmake:30 (message):
  Could not find LUAJIT!
Call Stack (most recent call first):
  CMakeLists.txt:138 (include)


-- Configuring incomplete, errors occurred!

Bug#818968: Long live Oysttyer

[Thorsten Alteholz]

Hi,

I just wanted to tell everybody that oysttyer just entered unstable.

 Thorsten

Bug#853446: Patch

[Hilko Bengen]

Control: tag -1 patch

GCC-7 recognizes patches that contain the word "fallthrough" (and some
variants thereof), but not misspellings. This patch fixes that.

Cheers,
-Hilko
Index: http-parser/http_parser.c
===
--- http-parser.orig/http_parser.c
+++ http-parser/http_parser.c
@@ -2092,7 +2092,7 @@ http_parser_parse_url(const char *buf, s
   case s_req_server_with_at:
 found_at = 1;
 
-  /* FALLTROUGH */
+  /* FALLTHROUGH */
   case s_req_server:
 uf = UF_HOST;
 break;

Processed: Patch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #853446 [src:http-parser] http-parser: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#873318: jellyfish does not actually disable parallel building

[Adrian Bunk]

Source: jellyfish
Version: 2.2.6-2
Severity: serious

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

...
lib/.libs/jsoncpp.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:1193: recipe for target 'libjellyfish-2.0.la' failed
make[2]: *** [libjellyfish-2.0.la] Error 1



 jellyfish (2.2.6-2) unstable; urgency=medium
...
   * debhelper 10
   * Parallel builds seem to cause problems - use --no-parallel



%:
dh $@ --with autoreconf,python3 #--parallel



dh compat 10 does default to parallel,
explicit --no-parallel is required.

Processed: bug 873097 is forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=21508

[Debian Bug Tracking System]

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

> forwarded 873097 https://sourceware.org/bugzilla/show_bug.cgi?id=21508
Bug #873097 {Done: Aurelien Jarno } [src:glibc] glibc: 
FTBFS on *all* architectures except m68k, powerpcspe, sh4
Set Bug forwarded-to-address to 
'https://sourceware.org/bugzilla/show_bug.cgi?id=21508'.
> thanks
Stopping processing here.

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

Bug#873275: always segfaults at start due to QSslSocket

[Lisandro Damián Nicanor Pérez Meyer]

On sábado, 26 de agosto de 2017 15:50:14 -03 Adrian Bunk wrote:
> On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
> > First of all sorry for the top posting. Actually this is not a bug in qt4,
> > OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.
> 
> That's clear.
> 
> > I uploaded
> > to experimental for people to check, so actually this should be an
> > important bug against qgis. If necessary I'll explain more with a more
> > comfortable mail client at hand.
> 
> The problem as reported by Dan and reproduced by me is:
[snip] 
> To me this looks like qt4 built with OpenSSL 1.1 trying to use functions
> that were removed in OpenSSL 1.1, example:
> 
>   /usr/include/openssl/ssl.h:#define SSLv23_client_method   
> TLS_client_method
> 
> 
> In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this
> from libssl.so.1.1 cannot work.

Indeed, so the upload did work after all: we now know that the proposed patch 
is not enough.

Sebbastiaan: we might need to remove SSL support in Qt4 I'm afraid. How is the 
qt5 port going?

-- 
En los momentos de crisis, la imaginación es mas importante que el
conocimiento.
 Albert Einstein

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Processed: baresip: diff for NMU version 0.5.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 872406 + patch
Bug #872406 [src:baresip] baresip FTBFS: error: storage size of 'timeout' isn't 
known
Added tag(s) patch.
> tags 872406 + pending
Bug #872406 [src:baresip] baresip FTBFS: error: storage size of 'timeout' isn't 
known
Added tag(s) pending.

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

Bug#872406: baresip: diff for NMU version 0.5.4-1.1

[Sebastian Ramacher]

Control: tags 872406 + patch
Control: tags 872406 + pending

Dear maintainer,

I've prepared an NMU for baresip (versioned as 0.5.4-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru baresip-0.5.4/debian/changelog baresip-0.5.4/debian/changelog
--- baresip-0.5.4/debian/changelog	2017-07-03 12:57:00.0 +0200
+++ baresip-0.5.4/debian/changelog	2017-08-26 11:41:57.0 +0200
@@ -1,3 +1,12 @@
+baresip (0.5.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  
+  [ Steve Langasek ]
+  * Build with -D_GNU_SOURCE to fix FTBFS with GCC 7. (Closes: #872406)
+
+ -- Sebastian Ramacher   Sat, 26 Aug 2017 11:41:57 +0200
+
 baresip (0.5.4-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru baresip-0.5.4/debian/patches/gcc-7-compat.patch baresip-0.5.4/debian/patches/gcc-7-compat.patch
--- baresip-0.5.4/debian/patches/gcc-7-compat.patch	1970-01-01 01:00:00.0 +0100
+++ baresip-0.5.4/debian/patches/gcc-7-compat.patch	2017-08-26 11:40:58.0 +0200
@@ -0,0 +1,20 @@
+Description: Use -D_GNU_SOURCE for gcc-7 compatibility
+ baresip fails to build with gcc-7 because libdirectfb-dev needs to know
+ the size of struct timespec, which is an opaque type unless we're using
+ GNU extensions, but libre-dev sets -std=c99.  Adjust cflags to enable
+ _GNU_SOURCE.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/872406
+
+Index: baresip-0.5.4/Makefile
+===
+--- baresip-0.5.4.orig/Makefile
 baresip-0.5.4/Makefile
+@@ -49,6 +49,7 @@
+ CFLAGS+= -I. -Iinclude -I$(LIBRE_INC) -I$(SYSROOT)/include
+ CFLAGS+= -I$(LIBREM_PATH)/include
+ CFLAGS+= -I$(SYSROOT)/local/include/rem -I$(SYSROOT)/include/rem
++CFLAGS+= -D_GNU_SOURCE
+ 
+ CXXFLAGS  += -I. -Iinclude -I$(LIBRE_INC)
+ CXXFLAGS  += -I$(LIBREM_PATH)/include
diff -Nru baresip-0.5.4/debian/patches/series baresip-0.5.4/debian/patches/series
--- baresip-0.5.4/debian/patches/series	2017-07-03 12:04:40.0 +0200
+++ baresip-0.5.4/debian/patches/series	2017-08-26 11:40:58.0 +0200
@@ -1 +1,2 @@
 2001_drop_libre_so_check.patch
+gcc-7-compat.patch


signature.asc
Description: PGP signature

Bug#871709: mercurial: CVE-2017-1000115: path traversal via symlink

[Salvatore Bonaccorso]

Hi

On Fri, Aug 25, 2017 at 11:52:45AM -0700, Peter Linss wrote:
> Any chance of getting this fix backported to stretch?

Yes, this is beeing worked on (and as well for jessie).

Regards,
Salvatore

Bug#873275: always segfaults at start due to QSslSocket

[Adrian Bunk]

On Sat, Aug 26, 2017 at 09:31:01AM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
> First of all sorry for the top posting. Actually this is not a bug in qt4,
> OpenSSL 1.0 Is getting removed and qt4 *needs* to switch to 1.1.

That's clear.

> I uploaded
> to experimental for people to check, so actually this should be an
> important bug against qgis. If necessary I'll explain more with a more
> comfortable mail client at hand.

The problem as reported by Dan and reproduced by me is:

$ qgis
Warning: QSslSocket: cannot resolve CRYPTO_num_locks
Warning: QSslSocket: cannot resolve CRYPTO_set_id_callback
Warning: QSslSocket: cannot resolve CRYPTO_set_locking_callback
Warning: QSslSocket: cannot resolve sk_free
Warning: QSslSocket: cannot resolve sk_num
Warning: QSslSocket: cannot resolve sk_pop_free
Warning: QSslSocket: cannot resolve sk_value
Warning: QSslSocket: cannot resolve SSL_library_init
Warning: QSslSocket: cannot resolve SSL_load_error_strings
Warning: QSslSocket: cannot resolve X509_get_notAfter
Warning: QSslSocket: cannot resolve X509_get_notBefore
Warning: QSslSocket: cannot resolve SSLv2_client_method
Warning: QSslSocket: cannot resolve SSLv23_client_method
Warning: QSslSocket: cannot resolve SSLv2_server_method
Warning: QSslSocket: cannot resolve SSLv23_server_method
Warning: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
Warning: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
Warning: QSslSocket: cannot resolve SSLeay
Warning: QSslSocket: cannot call unresolved function SSL_library_init
Warning: QSslSocket: cannot call unresolved function SSLv23_client_method
Warning: QSslSocket: cannot call unresolved function sk_num
Warning: QSslSocket: cannot call unresolved function X509_get_notBefore
Warning: QSslSocket: cannot call unresolved function X509_get_notAfter
Segmentation fault


To me this looks like qt4 built with OpenSSL 1.1 trying to use functions 
that were removed in OpenSSL 1.1, example:

  /usr/include/openssl/ssl.h:#define SSLv23_client_methodTLS_client_method


In OpenSSL 1.0.2 this was a proper function, but qt4 trying to load this 
from libssl.so.1.1 cannot work.


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

Bug#853472: marked as done (kde4libs: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 12:49:06 +
with message-id 
and subject line Bug#853472: fixed in kde4libs 4:4.14.35-1
has caused the Debian Bug report #853472,
regarding kde4libs: 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.)


-- 
853472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kde4libs
Version: 4:4.14.26-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/kde4libs_4.14.26-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

[...]
/<>/obj-x86_64-linux-gnu/kdeui/karrowbutton.moc: In member 
function 'virtual void* KArrowButton::qt_metacast(const char*)':
/<>/obj-x86_64-linux-gnu/kdeui/karrowbutton.moc:80:59: warning: 
'KArrowButton' is deprecated [-Wdeprecated-declarations]
 return static_cast(const_cast< KArrowButton*>(this));
   ^
In file included from /<>/kdeui/widgets/karrowbutton.cpp:19:0:
/<>/kdeui/widgets/karrowbutton.h:41:31: note: declared here
 class KDEUI_EXPORT_DEPRECATED KArrowButton : public QPushButton
   ^~~~
/<>/kdeui/windowmanagement/netwm.cpp: In member function 'void 
NETWinInfo::update(const long unsigned int*)':
/<>/kdeui/windowmanagement/netwm.cpp:4371:48: error: ISO C++ 
forbids comparison between pointer and integer [-fpermissive]
 p->blockCompositing = (data_ret != None);
^~~~
kdeui/CMakeFiles/kdeui.dir/build.make:6067: recipe for target 
'kdeui/CMakeFiles/kdeui.dir/windowmanagement/netwm.cpp.o' failed
make[4]: *** [kdeui/CMakeFiles/kdeui.dir/windowmanagement/netwm.cpp.o] Error 1
make[4]: *** Waiting for unfinished jobs
/<>/kdeui/windowmanagement/kwindowsystem_x11.cpp: In static member 
function 'static QRect KWindowSystem::workArea(const QList&, 
int)':
/<>/kdeui/windowmanagement/kwindowsystem_x11.cpp:867:9: warning: 
this 'for' clause does not guard... [-Wmisleading-indentation]
 for( ; it2 != s_d->strutWindows.end(); ++it2 )
 ^~~
/<>/kdeui/windowmanagement/kwindowsystem_x11.cpp:871:13: note: 
...this statement, but the latter is misleadingly indented as if it were 
guarded by the 'for'
 if( it2 != s_d->strutWindows.end()) {
 ^~
/<>/kdeui/util/kwallet.cpp: In member function 'void 
KWallet::Wallet::slotCollectionStatusChanged(int)':
/<>/kdeui/util/kwallet.cpp:530:46: warning: unused parameter 
'status' [-Wunused-parameter]
 void Wallet::slotCollectionStatusChanged(int status)
  ^~
In file included from /usr/include/qt4/QtCore/QObject:1:0,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:14,
 from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:
/usr/include/qt4/QtCore/qobject.h:121:18: warning: 'virtual bool 
QObject::event(QEvent*)' was hidden [-Woverloaded-virtual]
 virtual bool event(QEvent *);
  ^
In file included from 
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.cpp:12:0:
/<>/obj-x86_64-linux-gnu/kdeui/knotify_interface.h:46:35: warning: 
  by 'QDBusPendingReply OrgKdeKNotifyInterface::event(const QString&, 
const QString&, const QVariantList&, const QString&, const QString&, const 
QByteArray&, const QStringList&, int, qlonglong)' [-Woverloaded-virtual]
 inline QDBusPendingReply event(const QString &event, const QStrin

Bug#870068: marked as done (kde4libs FTBFS with cmake 3.9.0)

[Debian Bug Tracking System]

Your message dated Sat, 26 Aug 2017 12:49:06 +
with message-id 
and subject line Bug#870068: fixed in kde4libs 4:4.14.35-1
has caused the Debian Bug report #870068,
regarding kde4libs FTBFS with cmake 3.9.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.)


-- 
870068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kde4libs
Version: 4:4.14.26-2
Severity: serious
Tags: buster sid fixed-upstream patch

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

...
CMake Error at kdeui/CMakeLists.txt:316 (else):
  A duplicate ELSE command was found inside an IF block.


-- Configuring incomplete, errors occurred!



Fixed upstream in:
https://cgit.kde.org/kdelibs.git/commit/?h=KDE/4.14&id=57eaf65accb8d058644dc8eee7332e0ec0c1952f
--- End Message ---
--- Begin Message ---
Source: kde4libs
Source-Version: 4:4.14.35-1

We believe that the bug you reported is fixed in the latest version of
kde4libs, 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.
Pino Toscano  (supplier of updated kde4libs 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: Sat, 26 Aug 2017 14:33:15 +0200
Source: kde4libs
Binary: libkdecore5 libkdeui5 libkpty4 libkdesu5 libkjsapi4 libkjsembed4 
libkio5 libkntlm4 libsolid4 libkde3support4 libkfile4 libknewstuff2-4 
libknewstuff3-4 libkparts4 libkutils4 libthreadweaver4 libkhtml5 libkimproxy4 
libkmediaplayer4 libktexteditor4 libknotifyconfig4 libkdnssd4 libkrosscore4 
libkrossui4 libnepomuk4 libnepomukutils4 libnepomukquery4a libplasma3 
libkunitconversion4 libkdewebkit5 libkcmutils4 libkemoticons4 libkidletime4 
libkprintutils4 libkdeclarative5 kdelibs-bin kdelibs5-plugins kdelibs5-data 
kdoctools kdelibs5-dev
Architecture: source
Version: 4:4.14.35-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Description:
 kdelibs-bin - core executables for KDE Applications
 kdelibs5-data - core shared data for all KDE Applications
 kdelibs5-dev - development files for the KDE Development Platform libraries
 kdelibs5-plugins - core plugins for KDE Applications
 kdoctools  - various tools for accessing application documentation
 libkcmutils4 - utility classes for using KCM modules
 libkde3support4 - KDE 3 Support Library for the KDE 4 Platform
 libkdeclarative5 - declarative library for plasma
 libkdecore5 - KDE Platform Core Library
 libkdesu5  - Console-mode Authentication Library for the KDE Platform
 libkdeui5  - KDE Platform User Interface Library
 libkdewebkit5 - KDE WebKit Library
 libkdnssd4 - DNS-SD Protocol Library for the KDE Platform
 libkemoticons4 - utility classes to deal with emoticon themes
 libkfile4  - File Selection Dialog Library for KDE Platform
 libkhtml5  - KHTML Web Content Rendering Engine
 libkidletime4 - library to provide information about idle time
 libkimproxy4 - Instant Messaging Interface Library for the KDE Platform
 libkio5- Network-enabled File Management Library for the KDE Platform
 libkjsapi4 - KJS API Library for the KDE Development Platform
 libkjsembed4 - library for binding JavaScript objects to QObjects
 libkmediaplayer4 - KMediaPlayer Interface for the KDE Platform
 libknewstuff2-4 - "Get Hot New Stuff" v2 Library for the KDE Platform
 libknewstuff3-4 - "Get Hot New Stuff" v3 Library for the KDE Platform
 libknotifyconfig4 - library for configuring KDE Notifications
 libkntlm4  - NTLM Authentication Library for the KDE Platform
 libkparts4 - Framework for the KDE Platform Graphical Components
 libkprintutils4 - utility classes to deal with printing
 libkpty4   - Pseudo Terminal Library for the KDE Platform
 libkrosscore4 - Kross Core Library
 libkrossui4 - Kross UI Library
 libktexteditor4 - KTextEditor interfaces for the KDE Platform
 libkunitconversion4 - Unit Conversion library for the KDE Platform
 libkutils4 - dummy transitional library
 libnepomuk4 - Nepomuk Meta Data Library
 libnepomukquery4a - Nepomuk Query Library for the KDE Platform
 libn

Bug#873312: python-simpy3-doc and python-simpy-doc: error when trying to install together

[Ralf Treinen]

Package: python-simpy-doc,python-simpy3-doc
Version: python-simpy-doc/2.3.1+dfsg-1
Version: python-simpy3-doc/3.0.10-2
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-08-26
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:


Selecting previously unselected package libjs-jquery.
(Reading database ... 11002 files and directories currently installed.)
Preparing to unpack .../libjs-jquery_3.1.1-2_all.deb ...
Unpacking libjs-jquery (3.1.1-2) ...
Selecting previously unselected package libjs-underscore.
Preparing to unpack .../libjs-underscore_1.8.3~dfsg-1_all.deb ...
Unpacking libjs-underscore (1.8.3~dfsg-1) ...
Selecting previously unselected package libjs-sphinxdoc.
Preparing to unpack .../libjs-sphinxdoc_1.5.6-2_all.deb ...
Unpacking libjs-sphinxdoc (1.5.6-2) ...
Selecting previously unselected package python3.5-doc.
Preparing to unpack .../python3.5-doc_3.5.4-2_all.deb ...
Unpacking python3.5-doc (3.5.4-2) ...
Selecting previously unselected package python3-doc.
Preparing to unpack .../python3-doc_3.5.3-3_all.deb ...
Unpacking python3-doc (3.5.3-3) ...
Selecting previously unselected package python-simpy-doc.
Preparing to unpack .../python-simpy-doc_2.3.1+dfsg-1_all.deb ...
Unpacking python-simpy-doc (2.3.1+dfsg-1) ...
Selecting previously unselected package python-simpy3-doc.
Preparing to unpack .../python-simpy3-doc_3.0.10-2_all.deb ...
Unpacking python-simpy3-doc (3.0.10-2) ...
dpkg: error processing archive 
/var/cache/apt/archives/python-simpy3-doc_3.0.10-2_all.deb (--unpack):
 trying to overwrite '/usr/share/doc-base/python-simpy', which is also in 
package python-simpy-doc 2.3.1+dfsg-1
Errors were encountered while processing:
 /var/cache/apt/archives/python-simpy3-doc_3.0.10-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/share/doc-base/python-simpy

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Processed: severity of 863783 is serious

[Debian Bug Tracking System]

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

> severity 863783 serious
Bug #863783 [src:libproxy] libproxy: Please drop dependency against mozjs 1.8.5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 863787 is serious

[Debian Bug Tracking System]

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

> severity 863787 serious
Bug #863787 [src:couchdb] couchdb: Please drop dependency against mozjs 1.8.5
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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