Processed: limit source to php-monolog, tagging 882944

[Debian Bug Tracking System]

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

> limit source php-monolog
Limiting to bugs with field 'source' containing at least one of 'php-monolog'
Limit currently set to 'source':'php-monolog'

> tags 882944 + pending
Bug #882944 [src:php-monolog] php-monolog FTBFS with phpunit 6.4.4-2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: notfixed 909076 in 9.25~dfsg-3, notfound 909076 in 9.20~dfsg-3.2, tagging 909076

[Debian Bug Tracking System]

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

> notfixed 909076 9.25~dfsg-3
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Ignoring request to alter fixed versions of bug #909076 to the same values 
previously set
> notfound 909076 9.20~dfsg-3.2
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Ignoring request to alter found versions of bug #909076 to the same values 
previously set
> # stretch specific regression
> tags 909076 + stretch
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Ignoring request to alter tags of bug #909076 to the same tags previously set
> thanks
Stopping processing here.

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

Processed (with 1 error): archiving 909076

[Debian Bug Tracking System]

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

> archive 909076
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Bug 909076 cannot be archived
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfixed 909076 in 9.25~dfsg-3, notfound 909076 in 9.20~dfsg-3.2, tagging 909076

[Debian Bug Tracking System]

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

> notfixed 909076 9.25~dfsg-3
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
No longer marked as fixed in versions ghostscript/9.25~dfsg-3.
> notfound 909076 9.20~dfsg-3.2
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
No longer marked as found in versions ghostscript/9.20~dfsg-3.2.
> tags 909076 + stretch
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Torrance, Douglas]

On 12/10/18 6:29 AM, Juhani Numminen wrote:
> Control: tags -1 + fixed-upstream
> 
> On Sun, 9 Dec 2018 15:43:14 +0100 Andreas Metzler  wrote:
>> On 2018-12-09 Adrian Bunk  wrote:
>>> Source: wmhdplop
>>> Version: 0.9.10-1
>> [...]
>>
>>> devnames.c: In function 'device_id_from_name':
>>> devnames.c:207:13: warning: implicit declaration of function 'major' 
>>> [-Wimplicit-function-declaration]
>>> *pmajor = major(stat_buf.st_rdev);
>>>   ^
>> [...]
>>
>> Seems to miss a
>> #include 
> 
> Looks like that was indeed added in the upstream repo.
> https://repo.or.cz/dockapps.git/commitdiff/7cf2e5406b9bc98054404c4c0145c2db0c0ef1e8

Indeed.  This (and a couple other commits) hadn't been included in an 
official release yet.  I just fixed this, and version 0.9.11 is now 
available [1].  I'll prepare a new Debian package soon.

Doug

[1] https://www.dockapps.net/wmhdplop

Processed: tagging 913614, found 913614 in 2.1.18-6, found 913453 in 1:0.80-5, tagging 913453, tagging 916079 ...

[Debian Bug Tracking System]

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

> tags 913614 - stretch
Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device 
or address"
Bug #914944 [gnupg] gnupg: importing a key fails when there's no tty 
(regression from 2.1.18-8~deb9u2)
Removed tag(s) stretch.
Removed tag(s) stretch.
> found 913614 2.1.18-6
Bug #913614 [gnupg] gnupg2 fails with "cannot open '/dev/tty': No such device 
or address"
Bug #914944 [gnupg] gnupg: importing a key fails when there's no tty 
(regression from 2.1.18-8~deb9u2)
Marked as found in versions gnupg2/2.1.18-6.
Marked as found in versions gnupg2/2.1.18-6.
> found 913453 1:0.80-5
Bug #913453 {Done: Samuel Thibault } [espeakup] espeakup 
fails install and ends in broken state
Marked as found in versions espeakup/1:0.80-5.
> tags 913453 - stretch
Bug #913453 {Done: Samuel Thibault } [espeakup] espeakup 
fails install and ends in broken state
Removed tag(s) stretch.
> tags 916079 + sid buster
Bug #916079 [src:hyperic-sigar] hyperic-sigar FTBFS with glibc 2.28
Added tag(s) sid and buster.
> tags 916121 + sid buster
Bug #916121 [src:array-info] array-info FTBFS with glibc 2.28
Added tag(s) buster and sid.
> tags 916148 + sid buster
Bug #916148 [src:lpr] lpr FTBFS with glibc 2.28
Added tag(s) buster and sid.
> tags 916161 + sid buster
Bug #916161 [src:mono] mono FTBFS with glibc 2.28
Added tag(s) buster and sid.
> tags 916183 + sid buster
Bug #916183 [src:tetraproc] tetraproc FTBFS due to freetype-config usage
Added tag(s) sid and buster.
> fixed 909076 9.25~dfsg-3
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Marked as fixed in versions ghostscript/9.25~dfsg-3.
> found 909076 9.20~dfsg-3.2
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Marked as found in versions ghostscript/9.20~dfsg-3.2.
> tags 909076 - stretch
Bug #909076 {Done: Salvatore Bonaccorso } [ghostscript] 
ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
Removed tag(s) stretch.
> tags 893077 - stretch
Bug #893077 [src:gnucash] gnucash: FTBFS on Debian 9.4 (freshly installed) 
FAIL: test-report-utilities
Removed tag(s) stretch.
> found 914565 904808
Bug #914565 [libcap-ng] php7.3-intl: Segfaults after apache2 graceful restart
There is no source info for the package 'libcap-ng' at version '904808' with 
architecture ''
Unable to make a source version for version '904808'
Marked as found in versions 904808.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893077
909076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909076
913453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913453
913614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913614
914565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914565
914944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914944
916079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916079
916121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916121
916148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916148
916161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916161
916183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 914565 in 904808, found 914565 in 0.7.9-1

[Debian Bug Tracking System]

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

> notfound 914565 904808
Bug #914565 [libcap-ng] php7.3-intl: Segfaults after apache2 graceful restart
There is no source info for the package 'libcap-ng' at version '904808' with 
architecture ''
Unable to make a source version for version '904808'
No longer marked as found in versions 904808.
> found 914565 0.7.9-1
Bug #914565 [libcap-ng] php7.3-intl: Segfaults after apache2 graceful restart
There is no source info for the package 'libcap-ng' at version '0.7.9-1' with 
architecture ''
Unable to make a source version for version '0.7.9-1'
Marked as found in versions 0.7.9-1.
> thanks
Stopping processing here.

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

Processed: reassign 916029 to src:pyca, tagging 916029

[Debian Bug Tracking System]

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

> reassign 916029 src:pyca 20031119-0
Bug #916029 [src:pycra] RM: pycra -- RoQA, unmaintained, dead-upstream
Warning: Unknown package 'src:pycra'
Bug reassigned from package 'src:pycra' to 'src:pyca'.
Ignoring request to alter found versions of bug #916029 to the same values 
previously set
Ignoring request to alter fixed versions of bug #916029 to the same values 
previously set
Bug #916029 [src:pyca] RM: pycra -- RoQA, unmaintained, dead-upstream
Marked as found in versions pyca/20031119-0.
> tags 916029 + sid buster
Bug #916029 [src:pyca] RM: pycra -- RoQA, unmaintained, dead-upstream
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#916000: [Debian-med-packaging] Bug#916000: ncbi-blast+: FTBFS - Makefile.flat: No such file or directory

[Aaron M. Ucko]

Olivier Sallou  writes:

>> Olivier, will you have time to integrate these changes, or should I?
>
> no time for the moment, if you can do it,  I would appreciate

No problem, I should be able to take cafe of it later this week.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#916184: fswatch FTBFS: symbol differences

[Adrian Bunk]

Source: fswatch
Version: 1.13.0+repack-1
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -O--as-needed
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libfswatch11/DEBIAN/symbols doesn't match 
completely debian/libfswatch11.symbols
--- debian/libfswatch11.symbols (libfswatch11_1.13.0+repack-1_amd64)
+++ dpkg-gensymbolsZqx8uC   2020-01-05 21:58:17.643092338 -1200
@@ -1,6 +1,7 @@
 libfswatch.so.11 libfswatch11 #MINVER#
  FSW_ALL_EVENT_FLAGS@Base 1.11.2
- (optional|c++)"__gnu_cxx::__enable_if::__value, 
bool>::__type std::operator==(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.13.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 1.13.0+repack-1
+#MISSING: 1.13.0+repack-1# 
(optional|c++)"__gnu_cxx::__enable_if::__value, 
bool>::__type std::operator==(std::__cxx11::basic_string, std::allocator > const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.13.0
  (c++)"__gnu_cxx::__normal_iterator > > std::__unique<__gnu_cxx::__normal_iterator > >, 
__gnu_cxx::__ops::_Iter_equal_to_iter>(__gnu_cxx::__normal_iterator > >, __gnu_cxx::__normal_iterator > >, 
__gnu_cxx::__ops::_Iter_equal_to_iter)@Base" 1.10.0
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__ops::_Iter_equals_val, std::allocator > const> 
>(__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__normal_iterator, std::allocator > const*, 
std::vector, 
std::allocator >, std::allocator, std::allocator > > > >, 
__gnu_cxx::__ops::_Iter_equals_val, std::allocator > const>, 
std::random_access_iterator_tag)@Base" 1.10.0
  (c++)"bool std::__detail::_Compiler 
>::_M_expression_term(std::pair&, 
std::__detail::_BracketMatcher, false, 
false>&)@Base" 1.10.0
@@ -243,7 +244,7 @@
  (c++)"std::__detail::_BracketMatcher, true, 
false>::_M_ready()@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
false>::~_BracketMatcher()@Base" 1.10.0
  (optional|c++|arch= arm64 armel armhf mips mips64el mipsel ppc64el s390x 
alpha ia64 powerpc powerpcspe ppc64 riscv64 sparc64 
)"std::__detail::_BracketMatcher, true, 
true>::_M_add_char(char)@Base" 1.12.0
- 
(optional|c++)"std::__detail::_BracketMatcher, 
true, true>::_M_add_character_class(std::__cxx11::basic_string, std::allocator > const&, bool)@Base" 1.12.0
+#MISSING: 1.13.0+repack-1# 
(optional|c++)"std::__detail::_BracketMatcher, 
true, true>::_M_add_character_class(std::__cxx11::basic_string, std::allocator > const&, bool)@Base" 1.12.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::_M_make_range(char, char)@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::_M_ready()@Base" 1.10.0
  (c++)"std::__detail::_BracketMatcher, true, 
true>::~_BracketMatcher()@Base" 1.10.0
@@ -339,7 +340,7 @@
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.10.0
  (optional|c++|arch= armel riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace
 >, std::allocator > >, 
(__gnu_cxx::_Lock_policy)1>@Base" 1.11.2
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace
 >, std::allocator > >, 
(__gnu_cxx::_Lock_policy)2>@Base" 1.10.0
- (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 1.10.0
+#MISSING: 1.13.0+repack-1# (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 
1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, false, 
false>@Base" 1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, false, 
true>@Base" 1.10.0
  (c++)"typeinfo for 
std::__detail::_AnyMatcher, false, true, 
false>@Base" 1.10.0
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:9: binary] Error 2

Bug#916183: tetraproc FTBFS due to freetype-config usage

[Adrian Bunk]

Source: tetraproc
Version: 0.8.2-2
Severity: serious
Tags: ftbfs

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

...
g++  -O3 -Wall -MMD -MP -DVERSION=\"0.8.2\" -DSHARED=\"/usr/share/tetraproc\" 
-g -I/usr/X11R6/include `freetype-config --cflags`  -c -o tetraproc.o 
tetraproc.cc
/bin/sh: 1: freetype-config: not found
In file included from /usr/include/clxclient.h:31,
 from styles.h:26,
 from tetraproc.cc:27:
/usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or 
directory
 #include 
  ^~~~
compilation terminated.
make[1]: *** [: tetraproc.o] Error 1


freetype-config has been removed in Debian in favour of pkg-config.

The package also lacks a direct build dependency on libfreetype6-dev.

Bug#916182: dbacl FTBFS with glibc 2.28

[Adrian Bunk]

Source: dbacl
Version: 1.14.1-1
Severity: serious
Tags: ftbfs

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

...  ^
In file included from dbacl.h:81,
 from bayesol.h:32,
 from risk-lexer.l:24:
/usr/include/wchar.h:475:6: error: unknown type name 'locale_t'; did you mean 
'clockid_t'?
  locale_t __loc) __THROW;
  ^~~~
...

Bug#916181: cpprest: missing build dependency on pkg-config

[Adrian Bunk]

Source: cpprest
Version: 2.10.7-1
Severity: serious
Tags: ftbfs

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

...
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE) 
CMake Error at Release/cmake/cpprest_find_brotli.cmake:13 (find_package):
  By not providing "Findunofficial-brotli.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "unofficial-brotli", but CMake did not find one.

  Could not find a package configuration file provided by "unofficial-brotli"
  with any of the following names:

unofficial-brotliConfig.cmake
unofficial-brotli-config.cmake

  Add the installation prefix of "unofficial-brotli" to CMAKE_PREFIX_PATH or
  set "unofficial-brotli_DIR" to a directory containing one of the above
  files.  If "unofficial-brotli" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  Release/src/CMakeLists.txt:86 (cpprest_find_brotli)

Processed: RE: linux-image-4.18.0-3-amd64: Kernel update makes system unbootable: kernel-oops when loading "i915" module

[Debian Bug Tracking System]

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

> forcemerge 914495 916090
Bug #914495 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915: 
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915 
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux] 
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Bug #916090 [src:linux] linux-image-4.18.0-3-amd64: Kernel update makes system 
unbootable: kernel-oops when loading "i915" module
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=108850'.
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions linux/4.19~rc2-1~exp1.
Marked as found in versions linux/4.18.20-1.
Added tag(s) fixed-upstream.
Bug #914980 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: does not boot here [i915 gen4/gen5]
Bug #915178 {Done: Salvatore Bonaccorso } [src:linux] i915: 
unable to handle kernel NULL pointer dereference at 0008
Bug #915641 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: driver i915 crashed on GM45 chipset.
Bug #915645 {Done: Salvatore Bonaccorso } [src:linux] 
linux-image-4.18.0-3-amd64: Kernel 4.18-0-3 boots to a blank screen
Bug #915674 {Done: Salvatore Bonaccorso } [src:linux] i915 
driver crash on kernel 4.18.0-3 (buster/testing)
Bug #915954 {Done: Salvatore Bonaccorso } [src:linux] 
inteldrmfb: screen black in 4.18.0-3 (works in 4.18.0-2)
Merged 914495 914980 915178 915641 915645 915674 915954 916090
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
914495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914495
914980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914980
915178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915178
915641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915641
915645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915645
915674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915674
915954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915954
916090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#916178: roger-router-cli: missing dependency on cups

[Marc Lehmann]

Package: roger-router-cli
Version: 1.8.14-2+b3
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

roger-router-cli apparently depends on cups-daemon, but has no required
dependency on it. if only cups-client is installed, installation fails
because the daemon is not running:

Setting up roger-router-cli (1.8.14-2+b3) ...
lpadmin: Unable to connect to server: Bad file descriptor
dpkg: error processing package roger-router-cli (--configure):
 subprocess installed post-installation script returned error exit status 1

I *guess* the fix would be to make the dependency on cups optional in the
post-install script somehow.

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), 
(500, 'stable-updates'), (500, 'stable-debug'), (500, 'unstable'), (500, 
'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 4.18.20-041820-generic (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages roger-router-cli depends on:
ii  libasound2  1.1.3-5
ii  libatk1.0-0 2.30.0-1
ii  libc6   2.27-8
ii  libcairo-gobject2   1.16.0-1
ii  libcairo2   1.16.0-1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u2
ii  libgirepository-1.0-1   1.50.0-1+b1
ii  libglib2.0-02.58.1-2
ii  libgssdp-1.0-3  1.0.1-1
ii  libgstreamer-plugins-base1.0-0  1.10.4-1
ii  libgstreamer1.0-0   1.10.4-1
ii  libgtk-3-0  3.24.1-2
ii  libgupnp-1.0-4  1.0.1-1
ii  libpango-1.0-0  1.42.4-4
ii  libpangocairo-1.0-0 1.42.4-4
ii  libpeas-1.0-0   1.20.0-1+b1
ii  libportaudio2   19.6.0-1
ii  libpulse0   10.0-1+deb9u1
ii  libroutermanager0   1.8.14-2+b3
ii  libsecret-1-0   0.18.5-3.1
ii  libsndfile1 1.0.27-3
ii  libsoup2.4-12.64.2-1
ii  libspeex1   1.2~rc1.2-1+b2
ii  libspeexdsp11.2~rc1.2-1+b2
ii  libtiff54.0.8-2+deb9u4
ii  libxml2 2.9.4+dfsg1-2.2+deb9u2

Versions of packages roger-router-cli recommends:
ii  cups-client  2.2.1-8+deb9u2
pn  cups-daemon  
ii  ghostscript  9.26~dfsg-0+deb9u1

roger-router-cli suggests no packages.

-- no debconf information

Bug#899735: marked as done (xfce4-genmon-plugin: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 22:18:32 +
with message-id 
and subject line Bug#899735: fixed in xfce4-genmon-plugin 4.0.1-2
has caused the Debian Bug report #899735,
regarding xfce4-genmon-plugin: Invalid maintainer address 
pkg-xfce-de...@lists.alioth.debian.org
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.)


-- 
899735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xfce4-genmon-plugin
Version: 4.0.1-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of xfce4-genmon-plugin,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package xfce4-genmon-plugin since the list address
pkg-xfce-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-xfce-de...@lists.alioth.debian.org is 55.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: xfce4-genmon-plugin
Source-Version: 4.0.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-genmon-plugin 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Dec 2018 22:41:04 +0100
Source: xfce4-genmon-plugin
Binary: xfce4-genmon-plugin
Architecture: source
Version: 4.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 xfce4-genmon-plugin - Generic Monitor for the Xfce4 panel
Closes: 899735
Changes:
 xfce4-genmon-plugin (4.0.1-2) unstable; urgency=medium
 .
   * Moved the package to git on salsa.debian.org
   * Updated the maintainer address to debian-x...@lists.debian.org
 closes: #899735
   * d/gbp.conf added, following DEP-14
   * d/watch: use HTTPS protocol
   * d/control: drop Lionel from uploaders, thanks!
   * d/control: update standards version to 4.2.1
   * New upstream version 4.0.1
   * update debhelper compat to 10
Checksums-Sha1:
 c1b889640b3413877986f69c80688df9f6d68034 1807 xfce4-genmon-plugin_4.0.1-2.dsc
 40a68fde705851b1290870198b3f5bb8f6852eb9 3080 
xfce4-genmon-plugin_4.0.1-2.debian.tar.xz
 666b1aadd658c4d8dc53db87281a3bf194eda118 14846 
xfce4-genmon-plugin_4.0.1-2_amd64.buildinfo
Checksums-Sha256:
 0daeb9088861f1a96f7dcc9630fae8cc8abd6988544aca0b6677be9

Bug#916177: i2p: FTBFS with Jetty 9.4

[Emmanuel Bourg]

Source: i2p
Severity: serious
Tags: patch sid buster
Justification: FTBFS

Hi,

The jetty9 package has been updated to the version 9.4 and it breaks i2p.
Could you pleased review and apply the patch attached? It fixes the build
failure but it's untested at run time.

Thank you,

Emmanuel Bourg
--- a/apps/jetty/java/src/net/i2p/jetty/JettyXmlConfigurationParser.java
+++ b/apps/jetty/java/src/net/i2p/jetty/JettyXmlConfigurationParser.java
@@ -43,9 +43,9 @@
 private static XmlParser initParser()
 {
 XmlParser parser = new XmlParser();
-URL config60 = Loader.getResource(XmlConfiguration.class, 
"org/eclipse/jetty/xml/configure_6_0.dtd");
-URL config76 = 
Loader.getResource(XmlConfiguration.class,"org/eclipse/jetty/xml/configure_7_6.dtd");
-URL config90 = 
Loader.getResource(XmlConfiguration.class,"org/eclipse/jetty/xml/configure_9_0.dtd");
+URL config60 = 
Loader.getResource("org/eclipse/jetty/xml/configure_6_0.dtd");
+URL config76 = 
Loader.getResource("org/eclipse/jetty/xml/configure_7_6.dtd");
+URL config90 = 
Loader.getResource("org/eclipse/jetty/xml/configure_9_0.dtd");
 parser.redirectEntity("configure.dtd",config90);
 parser.redirectEntity("configure_1_0.dtd",config60);
 parser.redirectEntity("configure_1_1.dtd",config60);
--- a/apps/jetty/java/src/net/i2p/servlet/I2PDefaultServlet.java
+++ b/apps/jetty/java/src/net/i2p/servlet/I2PDefaultServlet.java
@@ -132,7 +132,6 @@
  *
  * Get the resource list as a HTML directory listing.
  */
-@Override
 protected void sendDirectory(HttpServletRequest request,
 HttpServletResponse response,
 Resource resource,
--- a/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java
+++ b/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java
@@ -317,7 +317,7 @@
 buf.append(request.getMethod());
 buf.append(' ');
 
-request.getUri().writeTo(u8buf);
+u8buf.append(request.getHttpURI().toString());
 
 buf.append(' ');
 buf.append(request.getProtocol());
--- a/apps/routerconsole/java/src/net/i2p/router/web/HostCheckHandler.java
+++ b/apps/routerconsole/java/src/net/i2p/router/web/HostCheckHandler.java
@@ -15,7 +15,7 @@
 import net.i2p.util.PortMapper;
 
 import org.eclipse.jetty.server.Request;
-import org.eclipse.jetty.servlets.gzip.GzipHandler;
+import org.eclipse.jetty.server.handler.gzip.GzipHandler;
 
 /**
  * Block certain Host headers to prevent DNS rebinding attacks.
--- a/apps/routerconsole/java/src/net/i2p/router/web/RouterConsoleRunner.java
+++ b/apps/routerconsole/java/src/net/i2p/router/web/RouterConsoleRunner.java
@@ -22,6 +22,7 @@
 import java.util.SortedSet;
 import java.util.StringTokenizer;
 import java.util.concurrent.LinkedBlockingQueue;
+import javax.servlet.ServletRequest;
 
 import net.i2p.I2PAppContext;
 import net.i2p.app.ClientAppManager;
@@ -46,6 +47,7 @@
 import org.eclipse.jetty.security.HashLoginService;
 import org.eclipse.jetty.security.ConstraintMapping;
 import org.eclipse.jetty.security.ConstraintSecurityHandler;
+import org.eclipse.jetty.security.UserStore;
 import org.eclipse.jetty.security.authentication.DigestAuthenticator;
 import org.eclipse.jetty.server.AbstractConnector;
 import org.eclipse.jetty.server.ConnectionFactory;
@@ -932,6 +934,8 @@
 } else {
 HashLoginService realm = new 
CustomHashLoginService(JETTY_REALM, context.getContextPath(),
 
ctx.logManager().getLog(RouterConsoleRunner.class));
+UserStore userStore = new UserStore();
+realm.setUserStore(userStore);
 sec.setLoginService(realm);
 sec.setAuthenticator(authenticator);
 String[] role = new String[] {JETTY_ROLE};
@@ -939,7 +943,7 @@
 String user = e.getKey();
 String pw = e.getValue();
 Credential cred = 
Credential.getCredential(MD5_CREDENTIAL_TYPE + pw);
-realm.putUser(user, cred, role);
+userStore.addUser(user, cred, role);
 Constraint constraint = new Constraint(user, JETTY_ROLE);
 constraint.setAuthenticate(true);
 ConstraintMapping cm = new ConstraintMapping();
@@ -959,7 +963,7 @@
 try {
 // each char truncated to 8 bytes
 String user2 = new String(b2, "ISO-8859-1");
-realm.putUser(user2, cred, role);
+userStore.addUser(user2, cred, role);
 constraint = new Constraint(user2, JETTY_ROLE);
 constraint.setAuthenticate(true);
 cm = new ConstraintMapping();
@@ -970,7 +974,7 @@

Bug#905254: Relations to other packages

[Paul Gevers]

On Mon, 10 Dec 2018 14:13:42 +0100 Cyrille Bollu  wrote:
> Cacti:
> 
> 
> Latest version of cacti upstream still uses PHPMailer 5.2.x.
> 
> I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206

I am packaging the upcoming cacti in experimental already, so when Cacti
upstream fixes this issue, I can move forward swiftly.

Paul
PS: I am subscribing to this bug, no need to CC me.



signature.asc
Description: OpenPGP digital signature

Bug#914058: marked as done (cupt FTBFS when binNMU'ed)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 21:39:41 +
with message-id 
and subject line Bug#914058: fixed in cupt 2.10.3
has caused the Debian Bug report #914058,
regarding cupt FTBFS when binNMU'ed
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.)


-- 
914058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cupt
Version: 2.10.2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=cupt&suite=sid

...
#   Failed test 'executable version'
#   at tt/version.t line 11.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^executable: (?^:2\.\d+\.\d+~?)$)'

#   Failed test 'library version'
#   at tt/version.t line 12.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^library: (?^:2\.\d+\.\d+~?)$)'
# Looks like you failed 2 tests of 4.

#   Failed test 'invoking via version'
#   at tt/version.t line 15.

#   Failed test 'executable version'
#   at tt/version.t line 11.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^executable: (?^:2\.\d+\.\d+~?)$)'

#   Failed test 'library version'
#   at tt/version.t line 12.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^library: (?^:2\.\d+\.\d+~?)$)'
# Looks like you failed 2 tests of 4.

#   Failed test 'invoking via -v'
#   at tt/version.t line 15.

#   Failed test 'executable version'
#   at tt/version.t line 11.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^executable: (?^:2\.\d+\.\d+~?)$)'

#   Failed test 'library version'
#   at tt/version.t line 12.
#   'executable: 2.10.2+b1
# library: 2.10.2+b1
# '
# doesn't match '(?^m:^library: (?^:2\.\d+\.\d+~?)$)'
# Looks like you failed 2 tests of 4.

#   Failed test 'invoking via --version'
#   at tt/version.t line 15.
# Looks like you failed 3 tests of 3.
[09:07:26] tt/version.t 
...
 
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/3 subtests 
[09:07:26]

Test Summary Report
---
tt/version.t
 (Wstat: 768 Tests: 3 Failed: 3)
  Failed tests:  1-3
  Non-zero exit status: 3
Files=181, Tests=2072, 124 wallclock secs ( 2.19 usr  0.54 sys + 79.92 cusr 
17.00 csys = 99.65 CPU)
Result: FAIL
make[4]: *** [test/CMakeFiles/test.dir/build.make:60: test/CMakeFiles/test] 
Error 1
--- End Message ---
--- Begin Message ---
Source: cupt
Source-Version: 2.10.3

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

Debian distribution maintenance software
pp.
Eugene V. Lyubimkin  (supplier of updated cupt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 21:20:34 +0100
Source: cupt
Binary: cupt-dbg libcupt4-2 libcupt-common libcupt4-dev libcupt4-doc cupt 
libcupt4-2-downloadmethod-curl libcupt4-2-downloadmethod-wget
Architecture: source amd64 all
Version: 2.10.3
Distribution: unstable
Urgency: low
Maintainer: Eugene V. Lyubimkin 
Changed-By: Eugene V. Lyubimkin 
Description:
 cupt   - flexible package manager -- console interface
 cupt-dbg   - flexible package manager -- debugging symbols
 libcupt-common - flexible package manager -- runtime library (support files)
 libcupt4-2 - flexible package manager -- runtime library
 libcupt4-2-downloadmethod-curl - flexible package manager -- libcurl download 
method
 libcupt4-2-downloadmethod-wget - flexible package manager -- wget download 
method
 libcupt4-dev - flexible package manager -- development files
 libcupt4-doc - flexible package manager -- library documentation
Closes: 914058
Changes:
 cupt (2.10.3) unstable; urgency=low

Bug#916173: granite-demo: crashes with missing io.elementary.desktop.wingpanel.datetime schema

[Jeremy Bicha]

Package: granite-demo
Version: 5.2.1-1
Severity: serious
X-Debbugs-CC: by...@debian.org

granite-demo crashes when I try to run it because it can't find the
io.elementary.desktop.wingpanel.datetime gsettings schema.

This is a regression since 5.1.0-2.

I see this change in the code. Maybe we should change it back in Debian?

diff -Nru granite-5.1.0/lib/DateTime.vala granite-5.2.1/lib/DateTime.vala
--- granite-5.1.0/lib/DateTime.vala 2018-08-23 23:54:44.0 +
+++ granite-5.2.1/lib/DateTime.vala 2018-11-07 19:18:54.0 +
@@ -110,7 +110,7 @@
  * @return true if the clock format is 12h based, false otherwise.
  */
 private static bool is_clock_format_12h () {
-var h24_settings = new Settings ("org.gnome.desktop.interface");
+var h24_settings = new Settings
("io.elementary.desktop.wingpanel.datetime");
 var format = h24_settings.get_string ("clock-format");
 return (format.contains ("12h"));
 }

Thanks,
Jeremy Bicha

Processed: severity of 916145 is serious

[Debian Bug Tracking System]

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

> severity 916145 serious
Bug #916145 [closure-compiler] closure-compiler: Not working with recent JS code
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: tagging 916145

[Debian Bug Tracking System]

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

> tags 916145 + buster sid
Bug #916145 [closure-compiler] closure-compiler: Not working with recent JS code
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#915334: Upstream icon 3.5.1 seems to have this fixed

[Étienne Mollier]

On Mon, 10 Dec 2018 19:02:28 +0100 =?UTF-8?Q?=c3=89tienne_Mollier?= 
 wrote:
> Please disregard this patch, it seems the proper change has been
> brought upstream, in icon version 3.5.1, to take in account the
> necessary change for GlibC 2.28:
> 
>   http://www2.cs.arizona.edu/icon/current/

I'm wrong, it will be part of the next version probably, but not
icon 3.5.1.  The patch may help finally.

Sorry for the confusion,
-- 
Étienne Mollier 

Bug#915582: Acknowledgement (Installs non-free binaries from cisco and google again)

[Ingo Saitz]

After setting the options in my previous mail to false i found
firefox still was downloading binaries of libgmpopenh264.so and
libwidevinecdm.so.

I looked into the firefox sources (64.0~b12-2), and the installation
seems to be done by
toolkit/mozapps/extensions/internal/ProductAddonChecker.jsm by
ProductAddonChecker.getProductAddonList(). There is a config option
GMPPrefs.KEY_UPDATE_ENABLED to disable this, which is defined in
toolkit/modules/GMPUtils.jsm line 118. Setting this to false seems to
disable the binary blob downloads.

So in /etc/firefox/firefox.js (debian/browser.js.in in the source), the
option

pref("media.gmp-gmpopenh264.enabled", false);

should be changed to

pref("media.gmp-manager.updateEnabled", false);

Users needing to enable the EME and OpenH264 binaries can still change
this option in about:config.

Ingo
-- 
 ╭─╮  Kennedy's Lemma:
╭│───╮  If you can parse Perl, you can solve the Halting Problem.
│╰─│─╯
╰──╯  http://www.perlmonks.org/?node_id=663393

Bug#916155: marked as done (qbs FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 20:49:37 +
with message-id 
and subject line Bug#916155: fixed in qbs 1.12.2+dfsg-1
has caused the Debian Bug report #916155,
regarding qbs FTBFS: symbol differences
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.)


-- 
916155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbs
Version: 1.12.1+dfsg-2
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqbscore1.12/DEBIAN/symbols doesn't match 
completely debian/libqbscore1.12.symbols
--- debian/libqbscore1.12.symbols (libqbscore1.12_1.12.1+dfsg-2_amd64)
+++ dpkg-gensymbolssPd2Tz   2018-12-08 18:31:54.047343402 -1200
@@ -1555,7 +1555,7 @@
  
(arch=!armel)_ZTISt15_Sp_counted_ptrIPN3qbs8Internal8ItemPoolELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  (arch=armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 
1.10.0
  (arch=!armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
1.10.0
- _ZTISt19_Sp_make_shared_tag@Base 1.10.0
+#MISSING: 1.12.1+dfsg-2# _ZTISt19_Sp_make_shared_tag@Base 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceIN3qbs8Internal16ProjectBuildDataESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
  
(arch=!armel)_ZTISt23_Sp_counted_ptr_inplaceIN3qbs8Internal16ProjectBuildDataESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceINSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEESaIS5_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
@@ -1674,6 +1674,7 @@
  
(optional=templinst)_ZZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE10_M_is_wordEcE3__s@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE10_M_is_wordEcE3__s@Base
 1.10.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 1.12.1+dfsg-2
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::accept(qbs::Internal::BuildGraphVisitor*)@Base" 1.10.0
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::load(qbs::Internal::PersistentPool&)@Base" 1.10.0
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::onChildDisconnected(qbs::Internal::BuildGraphNode*)@Base"
 1.10.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqbsqtprofilesetup1.12/DEBIAN/symbols 
doesn't match completely debian/libqbsqtprofilesetup1.12.symbols
--- debian/libqbsqtprofilesetup1.12.symbols 
(libqbsqtprofilesetup1.12_1.12.1+dfsg-2_amd64)
+++ dpkg-gensymbolsNYohk6   2018-12-08 18:31:54.523320423 -1200
@@ -222,7 +222,7 @@
  (arch=!armel)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 1.10.0
  (arch=armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 
1.10.0
  (arch=!armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
1.10.0
- _ZTISt19_Sp_make_shared_tag@Base 1.10.0
+#MISSING: 1.12.1+dfsg-2# _ZTISt19_Sp_make_shared_tag@Base 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
  
(arch=!armel)_ZTISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  _ZTSN3qbs9ErrorInfoE@Base 1.2.1
@@ -260,3 +260,4 @@
  
(optional=templinst)_ZZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE10_M_is_wordEcE3__s@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE10_M_is_wordEcE3

Bug#916171: uml-utilities FTBFS with glibc 2.28

[Adrian Bunk]

Source: uml-utilities
Version: 20070815.1-3
Severity: serious
Tags: ftbfs

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

...
host.c: In function 'mk_node':
host.c:215:51: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
   return(mknod(devname, S_IFCHR|S_IREAD|S_IWRITE, makedev(major, minor)));
   ^~~
...
cc -g -Wall -DTUNTAP -o uml_net ethertap.o host.o output.o slip.o uml_net.o 
tuntap.o
/usr/bin/ld: host.o: in function `mk_node':
/build/1st/uml-utilities-20070815.1/uml_net/host.c:215: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:18: uml_net] Error 1

Bug#916170: umview FTBFS with glibc 2.28

[Adrian Bunk]

Source: umview
Version: 0.8.2-1.1
Severity: serious
Tags: ftbfs buster sid

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

...
In file included from unreal.c:39:
../include/libummod.h:44:5: error: conflicting types for 'fcntl64'
 int fcntl64(int fd, int cmd, long arg);
 ^~~
In file included from unreal.c:27:
/usr/include/fcntl.h:157:12: note: previous declaration of 'fcntl64' was here
 extern int fcntl64 (int __fd, int __cmd, ...);
^~~
make[3]: *** [Makefile:363: unreal.lo] Error 1

Bug#916155: Bug #916155 in qbs marked as pending

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #916155 in qbs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/qt/qbs/commit/9cd92d0816dcb6358d9b960ee912c07246daf134


Update symbols files.

Closes: #916155.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/916155

Processed: Bug #916155 in qbs marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #916155 [src:qbs] qbs FTBFS: symbol differences
Added tag(s) pending.

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

Bug#916168: python3-sphinx-autorun: pycon calls "python" - not "python3"

[cholm]

Package: python3-sphinx-autorun
Version: 1.1.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The extension called as

.. runblock pycon:



always executes  with the interpreter "python" rather than the 
expect

"python3" for this build (python3-sphinx-autorun) of the package.

The problem is in line 28 of

  /usr/lib/python3/dist-packages/sphinx_autorun/__init__.py

where the code reads

  config = dict(
  pycon='python ' + pycon,
  ...

where it _should_ be

  config = dict(
  pycon='python3 ' + pycon,
  ...

Exactly how to fix this, is not clear to me.

There is a workaround by defining the autorun languages in the conf.py 
file


  import sphinx_autorun
  import inspect

  pycon = inspect.getfile(sphinx_autorun).replace("__init__","pycon")
  autorun_languages = dict(pycon='python3 ' + pycon,
   pycon_prefix_chars=4,
   pycon_show_source=False,
   console='bash',
   console_prefix_chars=1)

but it's a bit of a hack I think.

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-sphinx-autorun depends on:
ii  python3 3.7.1-2
ii  python3-sphinx  1.7.9-1

python3-sphinx-autorun recommends no packages.

python3-sphinx-autorun suggests no packages.

-- no debconf information


--
Christian Holm Christensen 
-

 Niels Bohr Institute, Blegdamsvej 17, DK-2100 Copenhagen
 http://cern.ch/cholm, +4524618591

Bug#916139: marked as done (trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package hplip 3.17.10+repack0-7)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 19:49:52 +
with message-id 
and subject line Bug#916139: fixed in hplip 3.18.12+dfsg0-2
has caused the Debian Bug report #916139,
regarding trying to overwrite '/usr/lib/cups/filter/hpps', which is also in 
package hplip 3.17.10+repack0-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.)


-- 
916139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916139
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: printer-driver-postscript-hp
Version: 3.18.12+dfsg0-1
Severity: serious

Hi,

When upgrading a old VM, I got the following error:

Unpacking printer-driver-postscript-hp (3.18.12+dfsg0-1) over 
(3.17.10+repack0-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package 
hplip 3.17.10+repack0-7
Errors were encountered while processing:
 /var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looks like the Breaks/Replaces against hplip should be bumped.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages printer-driver-postscript-hp depends on:
ii  libc6 2.28-2
ii  libcups2  2.2.10-1
ii  python3   3.7.1-2
ii  xz-utils  5.2.2-1.3

printer-driver-postscript-hp recommends no packages.

Versions of packages printer-driver-postscript-hp suggests:
ii  hplip  3.18.12+dfsg0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: hplip
Source-Version: 3.18.12+dfsg0-2

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated hplip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Dec 2018 20:12:18 +0100
Source: hplip
Binary: hplip hplip-data printer-driver-postscript-hp hplip-gui hplip-doc 
hpijs-ppds printer-driver-hpijs printer-driver-hpcups libhpmud0 libhpmud-dev 
libsane-hpaio
Architecture: source
Version: 3.18.12+dfsg0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Description:
 hpijs-ppds - HP Linux Printing and Imaging - HPIJS PPD files
 hplip  - HP Linux Printing and Imaging System (HPLIP)
 hplip-data - HP Linux Printing and Imaging - data files
 hplip-doc  - HP Linux Printing and Imaging - documentation
 hplip-gui  - HP Linux Printing and Imaging - GUI utilities (Qt-based)
 libhpmud-dev - HP Multi-Point Transport Driver (hpmud) development libraries
 libhpmud0  - HP Multi-Point Transport Driver (hpmud) run-time libraries
 libsane-hpaio - HP SANE backend for multi-function peripherals
 printer-driver-hpcups - HP Linux Printing and Imaging - CUPS Raster driver 
(hpcups)
 printer-driver-hpijs - HP Linux Printing and Imaging - printer driver (hpijs)
 printer-driver-postscript-hp - HP Printers PostScript Descriptions
Closes: 916139
Changes:
 hplip (3.18.12+dfsg0-2) unstable; urgency=medium
 .
   * printer-driver-postscript-hp: Bump Breaks/Replaces against hplip
 (Closes: #916139)
   * Trim trailing whitespace
   * Re-export upstream signing key without extra signatures
Checksums-Sha1:
 9721344e58be14215733103f2aef039765c74217 2993 hplip_3.18.12+dfsg0-2.dsc
 c52f3a15428a1715f1c5a1b2d77e4f132cb6b196 107552 
hplip_3.18.12+dfsg0-2.debian.tar.xz
Checksums-Sha256:
 15e31e8dd7061a660cbf180cd24e2e3ad209189fd9115bd24051b00cc893e501 2993 
hplip_3.18.12+dfsg0-2.

Bug#913502: marked as done (deepin-music FTBFS with libdtkwidget-dev 2.0.9.9-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 19:49:21 +
with message-id 
and subject line Bug#913502: fixed in deepin-music 3.1.11+ds-1
has caused the Debian Bug report #913502,
regarding deepin-music FTBFS with libdtkwidget-dev 2.0.9.9-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.)


-- 
913502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-music
Version: 3.1.8.3+ds-1
Severity: serious
Tags: ftbfs

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

...
view/musiclistwidget.cpp:35:10: fatal error: dcombobox.h: No such file or 
directory
 #include 
  ^
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: deepin-music
Source-Version: 3.1.11+ds-1

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated deepin-music package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Dec 2018 14:10:00 -0500
Source: deepin-music
Binary: deepin-music
Architecture: source
Version: 3.1.11+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang 
Description:
 deepin-music - music player with brilliant and tweakful UI
Closes: 913502
Changes:
 deepin-music (3.1.11+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release 3.1.11.
   * debian/patches: Refresh all patches.
   * debian/control:
 + Build-depend on debhelper-compat (= 11) instead of using old
   debian/compat file.
 + R³: Use Rules-Requires-Root: no.
 + tighten up versioned build-dependency libdtkwidget-dev (>= 2.0.9.10~)
   to fix FTBFS. (Closes: #913502)
 + Bump Standards-Version to 4.2.1.
Checksums-Sha1:
 e059fc054a39e3486a6abee08231544ae456e5a4 2247 deepin-music_3.1.11+ds-1.dsc
 506ed1e79b2fdc1a371ccc6dbb1a075864944054 1509313 
deepin-music_3.1.11+ds.orig.tar.gz
 99a3894070d2ababa905b28a58b359ece6daf978 3612 
deepin-music_3.1.11+ds-1.debian.tar.xz
 2f9ad334474faca20c86251d1c2bcafbcd486ef2 15153 
deepin-music_3.1.11+ds-1_amd64.buildinfo
Checksums-Sha256:
 cb4d7adade6783616efc075bd1ad10dd71d89066372af64251cbf8943d0947be 2247 
deepin-music_3.1.11+ds-1.dsc
 5d20b54cad0e7d581b2a4ee47c9be0a173596dfb38d87d98d4a188fc9051bd96 1509313 
deepin-music_3.1.11+ds.orig.tar.gz
 c1b7de7df2436cf02ae41c4d1141df4d281cb6f4d13fae63c758a3a362afec57 3612 
deepin-music_3.1.11+ds-1.debian.tar.xz
 738a89a5cc213b8c4cf41f4c98fb5800897534eab134a73c08fd6e821aa1c8c9 15153 
deepin-music_3.1.11+ds-1_amd64.buildinfo
Files:
 8b68e3f2cd975fe3c67ad2b81086bf63 2247 sound optional 
deepin-music_3.1.11+ds-1.dsc
 bc0aba394ea22182974d8827eb6705fc 1509313 sound optional 
deepin-music_3.1.11+ds.orig.tar.gz
 d090d47a00f5aa5dbd5634bdcf2ed236 3612 sound optional 
deepin-music_3.1.11+ds-1.debian.tar.xz
 d3847c51984ec0787d98eee03dcfd267 15153 sound optional 
deepin-music_3.1.11+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAlwOvVQACgkQwpPntGGC
Ws6N9w//cGwiIvyDiZtXdIgadZUdavIwGgUnqtoYiR/jmf1Vv5zFkeA7tunWqAsU
D5gUNwPi9JmBA7JuoekKGS4EZyKW27y84zRY6TVHY9WXj5tqwWMPJf4T5aEC0zim
gfkoHizlFkPU5KgB6+s1fU03xibHX285p4aHR4Lo5TFzj2CYbEWwyulc7H/wL4sY
ucGicGl68P0/7CxjNBn169AJrVs+iCRypV2jleiuG87yjpirkVW/5au1EXF260FW
Uu266vUL/StKmxAK6BYqSF2QMlk2NA96SemmgTw3+2kpK9X4/lr/KFrKsdlN4Fqs
SMBfiPkT/pARLs08a0+no7AA1QVphrmDKVJv/QtDq51DEHFdbA4M0EW7uHGyjc99
e/MU3QcONuT36UoWCvfBOCjnPJDGQtECA82me/tiB/PGtHGKcE5tJ0KyCvGldNKH
LG61ibXJH1A/AFnadPLB++4iLIEf856lONGP9czIanhyOMfrG2ccdPNJc5EPrJpe
qlPLVkAJelDznJGfDr4ry5HUgJpgliqAtAa0Qwp7r6wE50Gjf0XdUbAZMj2yZDy2
2mlLzn9amT7UBZWhGX37C6fztYvTR6C8YOtArd7e0IJrceMgWc1g706+TW2oYVoO
MqT7toQoUtO97FhOkH9kstTp5P6UsPuPoNIP7MRNWHzLZhPkfaY=
=DJqj
-END PGP SIGNATURE End Message ---

Bug#915666: linux: data corruption with blk-mq

[Ben Caradoc-Davies]

Comments on the upstream bug 
 indicate that fixes 
have been released in Linux 4.20-rc6 and 4.19.8.


Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#916166: reiserfsprogs FTBFS with glibc 2.28

[Adrian Bunk]

Source: reiserfsprogs
Version: 1:3.6.27-2
Severity: serious
Tags: ftbfs

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

...
In file included from parse_time.c:7:
../include/misc.h:76:26: error: unknown type name 'loff_t'; did you mean 
'off_t'?
 int valid_offset(int fd, loff_t offset);
  ^~
  off_t
In file included from parse_time.c:8:
../include/reiserfs_lib.h:300:55: error: unknown type name 'loff_t'; did you 
mean 'off_t'?
 void set_offset(int format, struct reiserfs_key *key, loff_t offset);
   ^~
   off_t
../include/reiserfs_lib.h:301:64: error: unknown type name 'loff_t'; did you 
mean 'off_t'?
 void set_type_and_offset(int format, struct reiserfs_key *key, loff_t offset,
^~

Bug#916163: ppp FTBFS with glibc 2.28

[Adrian Bunk]

Source: ppp
Version: 2.4.7-2+4
Severity: serious
Tags: ftbfs

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

...
pppcrypt.c: In function 'DesSetkey':
pppcrypt.c:122:2: warning: implicit declaration of function 'setkey'; did you 
mean 'DesSetkey'? [-Wimplicit-function-declaration]
  setkey((const char *)crypt_key);
  ^~
  DesSetkey
pppcrypt.c: In function 'DesEncrypt':
pppcrypt.c:137:2: warning: implicit declaration of function 'encrypt'; did you 
mean 'crypt'? [-Wimplicit-function-declaration]
  encrypt((char *)des_input, 0);
  ^~~
...
cc -Wl,-z,relro -Wl,-z,now -Wl,-E -o pppd main.o magic.o fsm.o lcp.o ipcp.o 
upap.o chap-new.o ccp.o ecp.o auth.o options.o demand.o utils.o sys-linux.o 
ipxcp.o tty.o eap.o chap-md5.o session.o chap_ms.o eap-tls.o pppcrypt.o 
multilink.o tdb.o spinlock.o ipv6cp.o eui64.o cbcp.o -lcrypto -lssl -lcrypt 
-lutil -lpam -ldl -ldl -lpcap \
-Wl,-soname,pppd.so.2.4.7
/usr/bin/ld: pppcrypt.o: in function `DesSetkey':
./pppd/pppcrypt.c:122: undefined reference to `setkey'
/usr/bin/ld: pppcrypt.o: in function `DesEncrypt':
./pppd/pppcrypt.c:137: undefined reference to `encrypt'
/usr/bin/ld: pppcrypt.o: in function `DesDecrypt':
./pppd/pppcrypt.c:153: undefined reference to `encrypt'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:227: pppd] Error 1

Bug#916165: purelibc FTBFS with glibc 2.28

[Adrian Bunk]

Source: purelibc
Version: 0.4.1-1
Severity: serious
Tags: ftbfs buster sid

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

...
syscalls.c:54:10: fatal error: ustat.h: No such file or directory
 #include 
  ^
compilation terminated.
make[2]: *** [Makefile:390: libpurelibc_la-syscalls.lo] Error 1

Bug#915686: marked as done (src:bmap-tools: FTBFS with Python 3.7 as default)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 18:51:32 +
with message-id 
and subject line Bug#915686: fixed in bmap-tools 3.5-2
has caused the Debian Bug report #915686,
regarding src:bmap-tools: FTBFS with Python 3.7 as default
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.)


-- 
915686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bmap-tools
Version: 3.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

bmap-tools fails to build from source with the new Python 3.7 default.
You can see the Ubuntu build failure (which I was able to reproduce in a clean
sid chroot) here. [1]

The tests are failing with this error:
RuntimeError: generator raised StopIteration

Thanks,
Logan

[1] 
https://launchpadlibrarian.net/399583193/buildlog_ubuntu-disco-amd64.bmap-tools_3.5-1_BUILDING.txt.gz

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic-updates
  APT policy: (500, 'cosmic-updates'), (500, 'cosmic-security'), (500, 
'cosmic'), (400, 'cosmic-proposed'), (100, 'cosmic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-11-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: bmap-tools
Source-Version: 3.5-2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated bmap-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 15:43:52 +
Source: bmap-tools
Binary: bmap-tools
Architecture: source
Version: 3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Simon McVittie 
Changed-By: Simon McVittie 
Description:
 bmap-tools - tool to flash image files to block devices using the block map
Closes: 915686
Changes:
 bmap-tools (3.5-2) unstable; urgency=medium
 .
   * d/p/Filemap-catch-StopIteration-from-next-iterator.patch:
 Fix FTBFS with Python 3.7 (Closes: #915686)
Checksums-Sha1:
 2c595657559ad5a49e771891b85b9f766d66f7df 1983 bmap-tools_3.5-2.dsc
 e2165ec6ca7b3bd5e6dd8d8db378e5ae92876c16 6804 bmap-tools_3.5-2.debian.tar.xz
 f2064b20b02c13b8944b20c701f0a3160516a02b 5527 bmap-tools_3.5-2_source.buildinfo
Checksums-Sha256:
 4a551cbb5c82cbecc674dcd50b4313e91428900abbffd9cbe92d9ff2dc83f643 1983 
bmap-tools_3.5-2.dsc
 f14d0fb88237f909bd0c1d78127c84c7d5c6089dc6c8e8ad9f982fd961210fd1 6804 
bmap-tools_3.5-2.debian.tar.xz
 562cb2f3097b8f7cad538da621163eef23ddc4959b09f55a8700d8b8bde2437a 5527 
bmap-tools_3.5-2_source.buildinfo
Files:
 9ada4da76515fcd44c9773faad034a91 1983 utils optional bmap-tools_3.5-2.dsc
 8faffb80a3d2b9479385a12e11be0f35 6804 utils optional 
bmap-tools_3.5-2.debian.tar.xz
 d50ee4828378c40cb7defb80686aec25 5527 utils optional 
bmap-tools_3.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAlwOr2AACgkQ4FrhR4+B
TE+5ZBAAk385u2MQ1rhRafmKVgjG+K2xy2zCJIUnjBu1rFJbF+qszvxUBjiZfWlG
zeqtu7QfsbumxvyXvnY5PxvyvWAjM7YoqUg9JU0RGul+Dop+Ja5uhEaQVb3u7oN8
S7v5GLS6OE8EVPGTOjas4I0ZyS1jts9JDNEbWUQkLfic1IknOI9FDKLBaVMMUcf/
t8ZRnwBAgxdy2XZPj/OEy+uZQzmp3/3a7Vsbs23DeFGifo2Pp0f0ExvBOlGsXspO
3K8yKso2V6pJZWiMcU4J0u6tyVnE4p1We7376+QaL0lvKlGwc2TEMdC/FA+pJQTQ
arMYWWjlTw4WtC6t1WrxQUTTC+nLOyF/k/AJN4hxfv/I92+5E5SKn1CygO8naFrl
KDDk2B5gK+rN8CzMKugsY1KiV8m9a0wzNzdLyIij5gVvd85B+88s27FqDtNRxgt6
9R1DB/H8UfCz2OG9GVlXArv12wDVLOw5lPSXqCmxVVgCU35WuA0iVkuudB1gAxOn
TZiMB4WcaWRWRvikc05vma46G66ZTKda9SXQS047LxouN+8fEQgZSx7KYai2EKuT
Dg+Y9kfVkMPPx9ITqloswM7pAlJMMmjl9hcskN4aa54K4jp+qiqfe7Rab9yj/u0s
5fSr6BQwFEfNaCGiCtRcKNSDo6mbMPEr/7wkpGDa54iAXhaOQrs=
=pNq9
-END PGP SIGNATURE End Message ---

Processed (with 2 errors): Re: Bug#914565: php7.3-intl: Segfaults after apache2 graceful restart

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libcap-ng
Bug #914565 [php7.3-intl] php7.3-intl: Segfaults after apache2 graceful restart
Bug reassigned from package 'php7.3-intl' to 'libcap-ng'.
No longer marked as found in versions php7.3/7.3.0~rc5-2.
Ignoring request to alter fixed versions of bug #914565 to the same values 
previously set
> forcemerge 904808 -1
Bug #904808 [libcap-ng0] libcap-ng0: libcap-ng's use of pthread_atfork causes 
segfaults
Unable to merge bugs because:
package of #914565 is 'libcap-ng' not 'libcap-ng0'
Failed to forcibly merge 904808: Did not alter merged bugs.

> affects 904808 libapache2-mod-php7.3
Failed to mark 904808 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/904808 -- Unable to lock 
/org/bugs.debian.org/spool/lock/904808 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /org/bugs.debian.org/spool/lock/904808 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.


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

Bug#914565: php7.3-intl: Segfaults after apache2 graceful restart

[Ondřej Surý]

Control: reassign -1 libcap-ng
Control: forcemerge 904808 -1
Control: affects 904808 libapache2-mod-php7.3

Thanks Bernhard, that’s a very good catch!

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 10 Dec 2018, at 18:12, Bernhard Übelacker  wrote:
> 
> While looking into #915642 I found that this bug might just
> be another case of bug #904808.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808
> 
> Kind regards,
> Bernhard
> 

Bug#916161: mono FTBFS with glibc 2.28

[Adrian Bunk]

Source: mono
Version: 4.6.2.7+dfsg-1
Severity: serious
Tags: ftbfs

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

...
processes.c: In function 'load_modules':
processes.c:1653:12: error: implicit declaration of function 'makedev' 
[-Werror=implicit-function-declaration]
   device = makedev ((int)maj_dev, (int)min_dev);
^~~

Bug#916160: lsof FTBFS with glibc 2.28

[Adrian Bunk]

Source: lsof
Version: 4.89+dfsg-0.1
Severity: serious
Tags: ftbfs buster sid

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

...
LTlib.c: In function 'ConvLsofDev':
LTlib.c:231:25: warning: implicit declaration of function 'major'; did you mean 
'major_X'? [-Wimplicit-function-declaration]
 #define major_X(dp, em) major(x2dev(dp, em))
 ^
LTlib.c:360:31: note: in expansion of macro 'major_X'
 ldev->maj = (unsigned int)major_X(dp, &em);
   ^~~
LTlib.c:235:25: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
 #define minor_X(dp, em) minor(x2dev(dp, em))
 ^
LTlib.c:363:31: note: in expansion of macro 'minor_X'
 ldev->min = (unsigned int)minor_X(dp, &em);
   ^~~
`cat config.cc`  -I. -I.. `cat config.cflags` LTbasic.c \
LTlib.o `cat config.xobj` -o LTbasic
/usr/bin/ld: LTlib.o: in function `ConvLsofDev':
LTlib.c:(.text+0x102): undefined reference to `major'
/usr/bin/ld: LTlib.c:(.text+0x138): undefined reference to `minor'
/usr/bin/ld: LTlib.o: in function `ConvStatDev':
LTlib.c:(.text+0x1a5): undefined reference to `major'
/usr/bin/ld: LTlib.c:(.text+0x1c1): undefined reference to `minor'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:75: LTbasic] Error 1

Bug#916158: libfm-qt FTBFS: symbol differences

[Adrian Bunk]

Source: libfm-qt
Version: 0.13.1-9
Severity: serious
Tags: ftbfs

Some recent change in unstable makes libfm-qt FTBFS:

https://tests.reproducible-builds.org/debian/history/libfm-qt.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libfm-qt.html

...
   dh_makeshlibs -O--buildsystem=cmake
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libfm-qt5/DEBIAN/symbols doesn't match 
completely debian/libfm-qt5.symbols
--- debian/libfm-qt5.symbols (libfm-qt5_0.13.1-9_amd64)
+++ dpkg-gensymbolsN4ByOk   2020-01-12 12:43:01.058509823 -1200
@@ -1051,6 +1051,7 @@
  (c++)"Fm::uidFromName(QString)@Base" 0.10.0
  (c++)"Fm::uidToName(unsigned int)@Base" 0.10.0
  (c++)"Fm::uriExists(char const*)@Base" 0.10.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 0.13.1-9
  (c++)"non-virtual thunk to 
Fm::AppChooserComboBox::~AppChooserComboBox()@Base" 0.10.0
  (c++)"non-virtual thunk to Fm::AppChooserDialog::~AppChooserDialog()@Base" 
0.10.0
  (c++)"non-virtual thunk to Fm::AppMenuView::~AppMenuView()@Base" 0.10.0
@@ -1350,7 +1351,7 @@
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, (__gnu_cxx::_Lock_policy)2>@Base" 0.12.0
  (optional|c++|arch=  armel  riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, 
std::allocator >, std::allocator, std::allocator > >, 
(__gnu_cxx::_Lock_policy)1>@Base" 0.12.0
  (optional|c++|arch= !armel !riscv64 )"typeinfo for 
std::_Sp_counted_ptr_inplace, 
std::allocator >, std::allocator, std::allocator > >, 
(__gnu_cxx::_Lock_policy)2>@Base" 0.12.0
- (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 0.12.0
+#MISSING: 0.13.1-9# (c++)"typeinfo for std::_Sp_make_shared_tag@Base" 0.12.0
  (c++)"typeinfo name for Fm::AppChooserComboBox@Base" 0.10.0
  (c++)"typeinfo name for Fm::AppChooserDialog@Base" 0.10.0
  (c++)"typeinfo name for Fm::AppMenuView@Base" 0.10.0
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:9: binary] Error 2

Bug#912099: marked as done (gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 0xc2)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 18:19:47 +
with message-id 
and subject line Bug#912099: fixed in itstool 2.0.5-2
has caused the Debian Bug report #912099,
regarding gnumeric: FTBFS with itstool 2.0.4: 'ascii' codec can't decode byte 
0xc2
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.)


-- 
912099: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912099
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnumeric
Version: 1.12.43-1 
Severity: serious
Tags: ftbfs
Control: block 902557 with -1
X-Debbugs-Cc: itst...@packages.debian.org

As seen at

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

gnumeric fails to build on current sid/amd64. It seems to have broken
with itstool 2.0.4 in early October or so. From the build log:

  if test -f "${mo}"; then mo="../${mo}"; else 
mo="/build/1st/gnumeric-1.12.43/doc/${mo}"; fi; \
  (cd "cs/" && itstool -m "${mo}" ${d}/C/gnumeric.xml) && \
  touch "cs/cs.stamp"
  Warning: Could not merge cs translation for msgid:
  The chapters of this version of the Gnumeric 
manual are organized as follows: <_:itemizedlist-1/>
[...]
  Error: Could not merge translations:
  'ascii' codec can't decode byte 0xc2 in position 97: ordinal not in range(128)
  make[3]: *** [Makefile:1414: cs/cs.stamp] Error 1
  
This seems to be the same issue as

  https://bugzilla.redhat.com/show_bug.cgi?id=1604169

  https://github.com/itstool/itstool/issues/22

  https://gitlab.gnome.org/GNOME/gnumeric/issues/331

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: itstool
Source-Version: 2.0.5-2

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

Debian distribution maintenance software
pp.
Tanguy Ortolo  (supplier of updated itstool package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Dec 2018 18:42:09 +0100
Source: itstool
Binary: itstool
Architecture: source all
Version: 2.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Tanguy Ortolo 
Description:
 itstool- tool for translating XML documents with PO files
Closes: 912099
Changes:
 itstool (2.0.5-2) unstable; urgency=medium
 .
   * debian/patches/fix_crash_912099.patch: fix a further similar crash.
 (Closes: #912099)
Checksums-Sha1:
 ce21bf82d32670b0c6cdcf6c31e36d42f4e6d8db 1961 itstool_2.0.5-2.dsc
 71552382b8ea025f3c0edbd5168210a84c6553bb 4176 itstool_2.0.5-2.debian.tar.xz
 b911ebdb850ecc984148ba4f1138e6f1e3c8a1c2 41060 itstool_2.0.5-2_all.deb
 111ff60db49b77dce8d462aa21a0d0dfc45d6231 6232 itstool_2.0.5-2_amd64.buildinfo
Checksums-Sha256:
 5c6b2c55bedb4516f1a4ae8c7c45362573bffb5a5290436dc706c7defab46500 1961 
itstool_2.0.5-2.dsc
 46a901811eed0fbc2935d96bebcbe03286ab6d7b5b0ed121eb19953d9a831e91 4176 
itstool_2.0.5-2.debian.tar.xz
 9dbdcce8d8b815a5793b9e992ddaceac09d5897e8e3b8e085803afdfbc91d96b 41060 
itstool_2.0.5-2_all.deb
 9a1f823745e42b4f9985be799e4c2bea2ad88cbfb549ebe0e84e83c5ec56c1f5 6232 
itstool_2.0.5-2_amd64.buildinfo
Files:
 902d55c58489ea5c8b8f329949f0edb6 1961 text optional itstool_2.0.5-2.dsc
 b7922ca7656a94a118c8c33cf5873699 4176 text optional 
itstool_2.0.5-2.debian.tar.xz
 3727c20c0491f2da2439f69e21c303d9 41060 text optional itstool_2.0.5-2_all.deb
 3ec18d94ba8a2808e0933d1dd0d45e6a 6232 text optional 
itstool_2.0.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEC1QNJk2lrQnjLj0t6vLNUcUAaBkFAlwOqgwACgkQ6vLNUcUA
aBlBMw//QfOAcmTAQe3Jv1Tf8+Yrb3ReF1I/XhhhOuNBq2GrXl64HmAHKEl78kOZ
GUvTOZpm3uH7+pJSiO8L6OgJ77wQGx0QNHyUbctwbEi+J2WoMYGyKcuYHG0Cf2R/
HDksrPt23KB5g/mKqRrwYMSE/U+D1x8aCOlxPLZgaSsiedZyWmY5n2JHmrDDXhbQ
naURmyGUnWMxGj6RuAJLiF5DFJQyDsYsYJSKS1YhFwMHa4IKK6dQA/oF7L8ten2F
/G8rtNIUBK7kZs2eR3rVPFb9QUYasxNofpbhHCMevPBl+0r2MKf4L+VycsvTHbJz
Gg1T8hK5NvlsR80KLdqwqtMQnrmoJDON6WzB01r9brlGmNa2ZrHy5my0yi/XSexJ
zF7fXZurY/vMZrek3nSNcHOYJIfkCxqyomF1BnN4VCCii0/QsGBCpgcONomXvhLG
YRECXH1dZrGQjpyP4Uv469HKiIhrQ4intKbxF+YBZqCKVObjYgZz2dSCSsq36PBl
N8mG9euDtLg9bP1NnzwaA8hCEJz+WA7SH9zPhOdrYQs6znXbRdf/9Lr

Processed: affects 915345

[Debian Bug Tracking System]

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

> affects 915345 src:roarplaylistd
Bug #915345 [src:roaraudio] roaraudio FTBFS with glibc 2.28
Added indication that 915345 affects src:roarplaylistd
> thanks
Stopping processing here.

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

Bug#916156: extsmail FTBFS with glibc 2.28

[Adrian Bunk]

Source: extsmail
Version: 2.0-2.1
Severity: serious
Tags: ftbfs

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

...
In file included from externals_tokenizer.l:30:
/usr/include/time.h:113:5: error: unknown type name 'locale_t'; did you mean 
'clock_t'?
 locale_t __loc) __THROW;
 ^~~~
 clock_t
make[1]: *** [: externals_tokenizer.o] Error 1

Bug#915334: Upstream icon 3.5.1 seems to have this fixed

[Étienne Mollier]

Please disregard this patch, it seems the proper change has been
brought upstream, in icon version 3.5.1, to take in account the
necessary change for GlibC 2.28:

http://www2.cs.arizona.edu/icon/current/

Said patch on upstream repository, for information:


https://github.com/gtownsend/icon/commit/bfc4a6004d0d3984c8066289b8d8e563640c4ddd

Kind Regards,
-- 
Étienne Mollier 

Bug#916155: qbs FTBFS: symbol differences

[Adrian Bunk]

Source: qbs
Version: 1.12.1+dfsg-2
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqbscore1.12/DEBIAN/symbols doesn't match 
completely debian/libqbscore1.12.symbols
--- debian/libqbscore1.12.symbols (libqbscore1.12_1.12.1+dfsg-2_amd64)
+++ dpkg-gensymbolssPd2Tz   2018-12-08 18:31:54.047343402 -1200
@@ -1555,7 +1555,7 @@
  
(arch=!armel)_ZTISt15_Sp_counted_ptrIPN3qbs8Internal8ItemPoolELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  (arch=armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 
1.10.0
  (arch=!armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
1.10.0
- _ZTISt19_Sp_make_shared_tag@Base 1.10.0
+#MISSING: 1.12.1+dfsg-2# _ZTISt19_Sp_make_shared_tag@Base 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceIN3qbs8Internal16ProjectBuildDataESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
  
(arch=!armel)_ZTISt23_Sp_counted_ptr_inplaceIN3qbs8Internal16ProjectBuildDataESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceINSt7__cxx1118basic_stringstreamIcSt11char_traitsIcESaIcEEESaIS5_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
@@ -1674,6 +1674,7 @@
  
(optional=templinst)_ZZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE10_M_is_wordEcE3__s@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE10_M_is_wordEcE3__s@Base
 1.10.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 1.12.1+dfsg-2
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::accept(qbs::Internal::BuildGraphVisitor*)@Base" 1.10.0
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::load(qbs::Internal::PersistentPool&)@Base" 1.10.0
  (c++)"non-virtual thunk to 
qbs::Internal::Artifact::onChildDisconnected(qbs::Internal::BuildGraphNode*)@Base"
 1.10.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqbsqtprofilesetup1.12/DEBIAN/symbols 
doesn't match completely debian/libqbsqtprofilesetup1.12.symbols
--- debian/libqbsqtprofilesetup1.12.symbols 
(libqbsqtprofilesetup1.12_1.12.1+dfsg-2_amd64)
+++ dpkg-gensymbolsNYohk6   2018-12-08 18:31:54.523320423 -1200
@@ -222,7 +222,7 @@
  (arch=!armel)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 1.10.0
  (arch=armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 
1.10.0
  (arch=!armel)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
1.10.0
- _ZTISt19_Sp_make_shared_tag@Base 1.10.0
+#MISSING: 1.12.1+dfsg-2# _ZTISt19_Sp_make_shared_tag@Base 1.10.0
  
(arch=armel)_ZTISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 1.10.0
  
(arch=!armel)_ZTISt23_Sp_counted_ptr_inplaceINSt8__detail4_NFAINSt7__cxx1112regex_traitsIcSaIS5_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 1.10.0
  _ZTSN3qbs9ErrorInfoE@Base 1.2.1
@@ -260,3 +260,4 @@
  
(optional=templinst)_ZZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE10_M_is_wordEcE3__s@Base
 1.10.0
  
(optional=templinst)_ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE10_M_is_wordEcE3__s@Base
 1.10.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 1.12.1+dfsg-2
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:14: binary] Error 2

Bug#916154: kactivities-kf5 FTBFS: symbol differences

[Adrian Bunk]

Source: kactivities-kf5
Version: 5.51.0-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes kactivities-kf5 FTBFS:

https://tests.reproducible-builds.org/debian/history/kactivities-kf5.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kactivities-kf5.html

...
   dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5activities5/DEBIAN/symbols doesn't match 
completely debian/libkf5activities5.symbols
--- debian/libkf5activities5.symbols (libkf5activities5_5.51.0-1_amd64)
+++ dpkg-gensymbolsu32sH6   2020-01-11 00:48:10.987456520 -1200
@@ -113,9 +113,9 @@
  _ZNK11KActivities8Consumer15currentActivityEv@Base 4.96.0
  _ZNK11KActivities8Consumer17runningActivitiesEv@Base 5.23.0
  
(optional=templinst|arch=armel)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base
 5.14.0
- (optional=templinst|arch=!armel 
!riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 5.13.0
+#MISSING: 5.51.0-1# (optional=templinst|arch=!armel 
!riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 5.13.0
  
(optional=templinst|arch=armel)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base
 5.11.0
- (optional=templinst|arch=!armel 
!riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 4.98.0
+#MISSING: 5.51.0-1# (optional=templinst|arch=!armel 
!riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 4.98.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base
 5.21.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base
 5.21.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE14_M_get_deleterERKSt9type_info@Base
 5.21.0
@@ -138,7 +138,7 @@
  (arch=!armel !riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
4.98.0
  (arch=armel 
riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.44.0-1
  (arch=!armel 
!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 4.98.0
- _ZTISt19_Sp_make_shared_tag@Base 5.21.0
+#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.21.0
  (arch=armel 
riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.44.0-1
  (arch=!armel 
!riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.21.0
  _ZTSN11KActivities10ControllerE@Base 4.96.0
@@ -161,3 +161,4 @@
  _ZTVN11KActivities8ConsumerE@Base 4.96.0
  (arch=armel 
riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.44.0-1
  (arch=!armel 
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities4InfoESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.21.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 2

Processed: Re: Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 python3-matplotlib-dbg: missing Breaks+Replaces: 
> python-matplotlib-dbg (<< 2.2.3-3)
Bug #916140 [python3-matplotlib-dbg] python3-matplotlib-dbg: missing 
Breaks+Replaces: python-matplotlib-dbg (<< 3)
Changed Bug title to 'python3-matplotlib-dbg: missing Breaks+Replaces: 
python-matplotlib-dbg (<< 2.2.3-3)' from 'python3-matplotlib-dbg: missing 
Breaks+Replaces: python-matplotlib-dbg (<< 3)'.

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

Bug#916153: kdeclarative FTBFS: symbol differences

[Adrian Bunk]

Source: kdeclarative
Version: 5.51.0-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes kdeclarative FTBFS:

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

...
   dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5declarative5/DEBIAN/symbols doesn't 
match completely debian/libkf5declarative5.symbols
--- debian/libkf5declarative5.symbols (libkf5declarative5_5.51.0-1_amd64)
+++ dpkg-gensymbolsVWAQmL   2020-01-11 00:50:03.685630585 -1200
@@ -90,7 +90,7 @@
  (arch=!armel !riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 
5.12.0
  (arch=armel 
riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.12.0
  (arch=!armel 
!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.12.0
- _ZTISt19_Sp_make_shared_tag@Base 5.12.0
+#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.12.0
  (arch=armel 
riscv64)_ZTISt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.12.0
  (arch=!armel 
!riscv64)_ZTISt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.12.0
  _ZTSN12KDeclarative17ConfigPropertyMapE@Base 4.96.0
@@ -109,3 +109,4 @@
  _ZTVN12KDeclarative9QmlObjectE@Base 4.96.0
  (arch=armel 
riscv64)_ZTVSt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.12.0
  (arch=!armel 
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceI10QQmlEngineSaIS0_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.12.0
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 2

Bug#916152: kactivities-stats FTBFS: symbol differences

[Adrian Bunk]

Source: kactivities-stats
Version: 5.51.0-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes kactivities-stats FTBFS:

https://tests.reproducible-builds.org/debian/history/kactivities-stats.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kactivities-stats.html

...
   dh_makeshlibs -Xusr/lib/libkdeinit5_\* -O--buildsystem=kf5
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5activitiesstats1/DEBIAN/symbols doesn't 
match completely debian/libkf5activitiesstats1.symbols
--- debian/libkf5activitiesstats1.symbols 
(libkf5activitiesstats1_5.51.0-1_amd64)
+++ dpkg-gensymbolsdpqfZX   2018-12-08 18:30:20.653794179 -1200
@@ -197,7 +197,7 @@
  (optional=gccinternal|arch=!armel 
!riscv64)_ZTISt11_Mutex_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.20
  (optional=gccinternal|arch=armel 
riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE@Base 5.22.0
  (optional=gccinternal|arch=!armel 
!riscv64)_ZTISt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE@Base 5.20
- _ZTISt19_Sp_make_shared_tag@Base 5.20
+#MISSING: 5.51.0-1# _ZTISt19_Sp_make_shared_tag@Base 5.20
  (optional=templinst|arch=armel 
riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.22.0
  (optional=templinst|arch=!armel 
!riscv64)_ZTISt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.20
  _ZTSN11KActivities5Stats11ResultModelE@Base 5.20
@@ -214,6 +214,7 @@
  _ZTVN11KActivities5Stats13ResultWatcherE@Base 5.20
  (optional=templinst|arch=armel 
riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE1EE@Base
 5.22.0
  (optional=gccinternal|arch=!armel 
!riscv64)_ZTVSt23_Sp_counted_ptr_inplaceIN11KActivities8ConsumerESaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base
 5.20
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 5.51.0-1
  _Zls6QDebugRKN11KActivities5Stats5QueryE@Base 5.20
  _Zls6QDebugRKN11KActivities5Stats5Terms3UrlE@Base 5.20
  _Zls6QDebugRKN11KActivities5Stats5Terms4TypeE@Base 5.20
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:7: binary] Error 2

Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Andreas Beckmann]

Control: retitle -1 python3-matplotlib-dbg: missing Breaks+Replaces: 
python-matplotlib-dbg (<< 2.2.3-3)

On 2018-12-10 17:47, Sandro Tosi wrote:
> On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann  wrote:
>  is this right approach? there is a new src:matplotlib2 in experimetal
> NEW to drop py3k packages (so src:matplotlib2 will only ship python2
> and src:matplotlib will only ship py3k package), so that should remove
> the incompatibility?

This will probably not change anything, but lets see what happens once 
they clear new.

>> Why is there python3.6 stuff in python-matplotlib-dbg?
> 
> no idea, it looks like it's like that even on stretch! sigh

There is *.cpython-3[67]d{,m}-x86_64-linux-gnu.so in python-matplotlib-dbg
in sid, so for a clean upgrade path you will need the versioned breaks, 
but with an adjusted version. (Assuming the package built from
src:matplotlib2 no longer ships these conflicting files.)


Andreas

Bug#916150: sketch FTBFS: sketch.texi: Dimension too large

[Adrian Bunk]

Source: sketch
Version: 1:0.3.7-9
Severity: serious
Tags: ftbfs

Some recent change in unstable makes sketch FTBFS:

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

...
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=etex)
 restricted \write18 enabled.
entering extended mode
(./sketch.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
Loading texinfo [version 2018-01-09.11]: pdf, fonts, markup, glyphs,
page headings, tables, conditionals, indexing, sectioning, toc, environments,
defuns, macros, cross references, insertions,
(/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
This is `epsf.tex' v2.7.4 <14 February 2011>
) localization, formatting, and turning on texinfo input format.)
(/build/1st/sketch-0.3.7/Doc/version.texi)
Writing index file sketch.sx
[1] [2] [-1] Chapter 1
Writing index file sketch.cp
(ex000.eps
)
./sketch.texi:257: Dimension too large.
 @epsfxsize 
   
@epsfspecial #1->@epsftmp =10@epsfxsize 
@divide @epsftmp by @pspoints @ifnum...

@epsfsetgraph ... to @epsfxsize {@epsfspecial {#1}
  @hfil }@else @vfil @hbox t...

@imagexxx ...ysize =#3@relax @fi @epsfbox {#1.eps}
  @else @doxeteximage {#1}{#...

@image ...true @fi @else @imagexxx #1,@finish 
  @fi 
 @hfil @ignorespaces @image {ex000}
 @unskip @hfil 
...
l.257 @center @image{ex000}
   
? 
./sketch.texi:257: Emergency stop.
 @epsfxsize 
   
@epsfspecial #1->@epsftmp =10@epsfxsize 
@divide @epsftmp by @pspoints @ifnum...

@epsfsetgraph ... to @epsfxsize {@epsfspecial {#1}
  @hfil }@else @vfil @hbox t...

@imagexxx ...ysize =#3@relax @fi @epsfbox {#1.eps}
  @else @doxeteximage {#1}{#...

@image ...true @fi @else @imagexxx #1,@finish 
  @fi 
 @hfil @ignorespaces @image {ex000}
 @unskip @hfil 
...
l.257 @center @image{ex000}
   
Output written on sketch.dvi (3 pages, 2088 bytes).
Transcript written on sketch.log.
/usr/bin/texi2dvi: etex exited with bad status, quitting.
Died at make.pl line 87,  line 3335.
make[1]: *** [debian/rules:28: override_dh_auto_build] Error 1

Bug#916151: kopete FTBFS with glibc 2.28

[Adrian Bunk]

Source: kopete
Version: 4:17.08.3-2
Severity: serious
Tags: ftbfs

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

...
/build/1st/kopete-17.08.3/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc:
 In member function 'virtual bool cricket::V4LLookup::CheckIsV4L2Device(const 
string&)':
/build/1st/kopete-17.08.3/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc:38:7:
 error: 'major' was not declared in this scope
   if (major(s.st_rdev) == 81) {
   ^
Generating icecomponent.moc
/build/1st/kopete-17.08.3/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc:39:17:
 error: 'minor' was not declared in this scope
 dev_t num = minor(s.st_rdev);
 ^
...

Processed: [bts-link] source package src:ruby-globalid

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:ruby-globalid
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #906625 (http://bugs.debian.org/906625)
> # Bug title: ruby-globalid: FTBFS in buster/sid (failing tests)
> #  * https://github.com/rails/globalid/issues/112
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 906625 + fixed-upstream
Bug #906625 [src:ruby-globalid] ruby-globalid: FTBFS in buster/sid (failing 
tests)
Added tag(s) fixed-upstream.
> usertags 906625 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#905254:

[Cyrille Bollu]

Cacti:


Latest version of cacti upstream still uses PHPMailer 5.2.x.

I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206

tt-rss:


It seems like latest version don't necessarily use phpmailer anymore:

(https://git.tt-rss.org/fox/tt-rss/src/master)

>commit 57932e183745bada9c6183056597cb5276f68d10
>Author: Andrew Dolgov 
>Date:   Thu Nov 22 14:45:14 2018 +0300
>
>remove PHPMailer and related directives from config.php-dist; add
pluggable Mailer class
>

maybe tt-rss maintainer should be asked to update to latest upstream
version?

wordpress:


I haven't understand what should be done

ocsinventory-server & ocsinventory-reports:
=

Newest upstream version (2.5) will depend on PHPMailer 6.x

Not upgrading libphp-phpmailer  blocks upgrade to newest upstream versions
of these packages (which also somehow blocks #905396 and CVE-2018-14473).

I'll try to create the link between those bugs (#905254 block #905396)

Br,

Cyrille

Bug#913501: marked as done (deepin-deb-installer FTBFS with libdtkwidget-dev 2.0.9.9-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 19:34:04 +0200
with message-id <20181210173404.GE5270@localhost>
and subject line Seems to be fixed in 1.2.9-1
has caused the Debian Bug report #913501,
regarding deepin-deb-installer FTBFS with libdtkwidget-dev 2.0.9.9-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.)


-- 
913501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-deb-installer
Version: 1.2.5-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deepin-deb-installer.html

...
/build/1st/deepin-deb-installer-1.2.5/filechoosewidget.cpp: In constructor 
'FileChooseWidget::FileChooseWidget(QWidget*)':
/build/1st/deepin-deb-installer-1.2.5/filechoosewidget.cpp:45:88: error: no 
matching function for call to 'Dtk::Widget::DSvgRenderer::render(const char 
[18], const QSize)'
 QPixmap iconPix = DSvgRenderer::render(":/images/icon.svg", QSize(140, 
140) * ratio);

^
In file included from /usr/include/libdtk-2.0.9/DCore/../DWidget/DSvgRenderer:1,
 from 
/build/1st/deepin-deb-installer-1.2.5/filechoosewidget.cpp:37:
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:60:10: note: 
candidate: 'void Dtk::Widget::DSvgRenderer::render(QPainter*)'
 void render(QPainter *p);
  ^~
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:60:10: note:   
candidate expects 1 argument, 2 provided
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:61:10: note: 
candidate: 'void Dtk::Widget::DSvgRenderer::render(QPainter*, const QRectF&)'
 void render(QPainter *p, const QRectF &bounds);
  ^~
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:61:10: note:   no 
known conversion for argument 1 from 'const char [18]' to 'QPainter*'
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:63:10: note: 
candidate: 'void Dtk::Widget::DSvgRenderer::render(QPainter*, const QString&, 
const QRectF&)'
 void render(QPainter *p, const QString &elementId,
  ^~
/usr/include/libdtk-2.0.9/DCore/../DWidget/dsvgrenderer.h:63:10: note:   no 
known conversion for argument 1 from 'const char [18]' to 'QPainter*'
make[3]: *** [CMakeFiles/deepin-deb-installer.dir/build.make:104: 
CMakeFiles/deepin-deb-installer.dir/filechoosewidget.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Version: 1.2.9-1

This seems to be fixed in 1.2.9-1:
https://buildd.debian.org/status/package.php?p=deepin-deb-installer

cu
Adrian

-- 

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

Bug#916147: Bug #916147: rng-tools: replaced with inferior version

[Thorsten Glaser]

Putting the Launchpad bug into Cc.

-- Forwarded message --
Message-ID: 
Date: Mon, 10 Dec 2018 18:23:56 +0100 (CET)
Subject: rng-tools: replaced with inferior version

Source: rng-tools
Version: 5-1
Severity: serious
Justification: breaks existing uses of this package

This is the same as Launchpad bug #1333293 now arrived
in Debian itself.

The options (at least) -B, -H, -T, -t are gone, which
breaks my application using rngd.

I had to create this…
https://launchpad.net/~mirabilos/+archive/ubuntu/ppa/+sourcepub/4628516/+listing-archive-extra
… in order to be able to continue using rngd as before.

Will we be reintroducing rng-tools 2.x as rng-tools-debian
into Debian buster/sid? Otherwise, support for all those
missing functionality and options MUST be added to the
new rng-tools package.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#916148: lpr FTBFS with glibc 2.28

[Adrian Bunk]

Source: lpr
Version: 1:2008.05.17.2
Severity: serious
Tags: ftbfs

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

...
lpr.c: In function 'main':
lpr.c:336:32: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
^~~
lpr.c:336:41: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
 ^
lpr.c:336:62: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
  ^
...
cc -o lpr lpr.o ../common_source/startdaemon.o ../common_source/common.o 
../common_source/common_vars.o ../common_source/getcap.o 
../common_source/strlcpy.o ../common_source/strlcat.o
/usr/bin/ld: lpr.o: in function `main':
/build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to `minor'
/usr/bin/ld: /build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to 
`major'
/usr/bin/ld: /build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile.in:8: lpr] Error 1

Bug#916147: rng-tools: replaced with inferior version

[Thorsten Glaser]

Source: rng-tools
Version: 5-1
Severity: serious
Justification: breaks existing uses of this package

This is the same as Launchpad bug #1333293 now arrived
in Debian itself.

The options (at least) -B, -H, -T, -t are gone, which
breaks my application using rngd.

I had to create this…
https://launchpad.net/~mirabilos/+archive/ubuntu/ppa/+sourcepub/4628516/+listing-archive-extra
… in order to be able to continue using rngd as before.

Will we be reintroducing rng-tools 2.x as rng-tools-debian
into Debian buster/sid? Otherwise, support for all those
missing functionality and options MUST be added to the
new rng-tools package.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Processed: [bts-link] source package src:linux

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #915666 (http://bugs.debian.org/915666)
> # Bug title: linux: data corruption with blk-mq
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=201685
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 915666 + fixed-upstream
Bug #915666 [src:linux] linux: data corruption with blk-mq
Added tag(s) fixed-upstream.
> usertags 915666 + status-RESOLVED resolution-CODE-FIX
There were no usertags set.
Usertags are now: resolution-CODE-FIX status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:supertuxkart

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:supertuxkart
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #915453 (http://bugs.debian.org/915453)
> # Bug title: supertuxkart FTBFS with glew 2.1.0
> #  * https://github.com/supertuxkart/stk-code/issues/3557
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 915453 + fixed-upstream
Bug #915453 [src:supertuxkart] supertuxkart FTBFS with glew 2.1.0
Added tag(s) fixed-upstream.
> usertags 915453 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#914565: php7.3-intl: Segfaults after apache2 graceful restart

[Bernhard Übelacker]

While looking into #915642 I found that this bug might just
be another case of bug #904808.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808

Kind regards,
Bernhard

Bug#915642: AuthBasicProvider PAM crashes apache

[Bernhard Übelacker]

Dear Maintainer,
I just tried to reproduce and found it crash on service startup when
using the given /etc/apache2/sites-enabled/default.conf.

It looks like here the apache2 process wants to fork and calls the
fork_handlers. Unfortunately one of them belongs to an unloaded module.
Therefore we end up trying to execute unmapped memory.

>From the similar offset I would expect that the first fork_handler belong
to function deinit from libcap-ng.so.0.
The first one 0x7f50c8e0e660 points to the current location of libcap-ng.so.0.
But the second 0x7f50c8e12660 looks like pointing to an unloaded location of 
libcap-ng.so.0.

This situation looks quite similar to what I tried to collect in bug #914565.
And now that I looked up the bugs for libcap-ng0 this one seems related: 
#904808.

Kind regards,
Bernhard


#914565 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914565
#904808 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904808


(gdb) bt
#0  0x7f50c8e12660 in ?? ()
#1  0x7f50c921470e in __libc_fork () at ../sysdeps/nptl/fork.c:204
#2  0x7f50c9357875 in apr_proc_detach (daemonize=daemonize@entry=1) at 
./threadproc/unix/procsup.c:31
#3  0x7f50c8b93fc5 in event_pre_config (pconf=0x7f50c90b8028, 
plog=0x7f50c908c028, ptemp=) at event.c:3416
#4  0x55e968fd81be in ap_run_pre_config (pconf=0x7f50c90b8028, 
plog=0x7f50c908c028, ptemp=0x7f50c9090028) at config.c:89
#5  0x55e968fb3e5f in main (argc=, argv=) at 
main.c:775

(gdb) up
#2  0x7f50c9357875 in apr_proc_detach (daemonize=daemonize@entry=1) at 
./threadproc/unix/procsup.c:31
31  if ((x = fork()) > 0) {

(gdb) print *__fork_handlers
$1 = {next = 0x7f50c9309998 , prepare_handler = 0x0, 
parent_handler = 0x0, child_handler = 0x7f50c8e0e660 , dso_handle = 
0x7f50c93282a0, refcntr = 2, need_signal = 0}
(gdb) print *__fork_handlers->next
$2 = {next = 0x7f50c9309968 , prepare_handler = 0x0, 
parent_handler = 0x0, child_handler = 0x7f50c8e12660, dso_handle = 
0x7f50c93282a0, refcntr = 2, need_signal = 0}
(gdb) print *__fork_handlers->next->next
$3 = {next = 0x0, prepare_handler = 0x0, parent_handler = 0x0, child_handler = 
0x7f50c93133d0 <__reclaim_stacks>, dso_handle = 0x0, refcntr = 1, need_signal = 
0}

(gdb) info share
>FromTo  Syms Read   Shared Object Library
...
0x7f50c8e0e560  0x7f50c8e10419  Yes 
/lib/x86_64-linux-gnu/libcap-ng.so.0
...

Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Sandro Tosi]

On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann  wrote:
>
> Package: python3-matplotlib-dbg
> Version: 3.0.2-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

 is this right approach? there is a new src:matplotlib2 in experimetal
NEW to drop py3k packages (so src:matplotlib2 will only ship python2
and src:matplotlib will only ship py3k package), so that should remove
the incompatibility?

> Why is there python3.6 stuff in python-matplotlib-dbg?

no idea, it looks like it's like that even on stretch! sigh

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#916046: marked as done (libsqlite3-0 might need Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~))

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 16:49:48 +
with message-id 
and subject line Bug#916046: fixed in sqlite3 3.26.0-3
has caused the Debian Bug report #916046,
regarding libsqlite3-0 might need Breaks: python-migrate (<< 0.11.0-4~), 
python3-migrate (<< 0.11.0-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.)


-- 
916046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsqlite3-0
Version: 3.26.0-1
Severity: serious
Control: block -1 by 915938

  Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)
(assuming #915938 will be fixed in version 0.11.0-4)
might be correct to prevent people using testing or stretch-backports
to end up using a problematic combination of packages.
--- End Message ---
--- Begin Message ---
Source: sqlite3
Source-Version: 3.26.0-3

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated sqlite3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 14:41:05 +
Source: sqlite3
Binary: lemon sqlite3 sqlite3-doc libsqlite3-0 libsqlite3-dev libsqlite3-tcl
Architecture: source
Version: 3.26.0-3
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 lemon  - LALR(1) Parser Generator for C or C++
 libsqlite3-0 - SQLite 3 shared library
 libsqlite3-dev - SQLite 3 development files
 libsqlite3-tcl - SQLite 3 Tcl bindings
 sqlite3- Command line interface for SQLite 3
 sqlite3-doc - SQLite 3 documentation
Closes: 916046
Changes:
 sqlite3 (3.26.0-3) unstable; urgency=medium
 .
   * Declare that SQLite3 version 3.26.0 breaks unfixed python{,3}-migrate
 (closes: #916046).
Checksums-Sha1:
 dfe234af402f502ab49c1fd6d8fd0b1b990e90a8 2397 sqlite3_3.26.0-3.dsc
 c5e540a6faebfd85a4c8cc96a4bd472c26fb28c6 18984 sqlite3_3.26.0-3.debian.tar.xz
 444c6979a0bd24f8c483e892a9b27aad564cc656 9071 sqlite3_3.26.0-3_amd64.buildinfo
Checksums-Sha256:
 ef8779a2e3f2c7e2669c4009514af2dde10dbedb961d5dac33d3075f577cdf2d 2397 
sqlite3_3.26.0-3.dsc
 bc1b0bb37ba1e9af32065cb42e0a6d890a5794063efcbcff9e974692590bee25 18984 
sqlite3_3.26.0-3.debian.tar.xz
 936ffcc11bfb9d9ba19f95233d9d7fb3dadfadc4ea63dea6c31730c4dd501fb1 9071 
sqlite3_3.26.0-3_amd64.buildinfo
Files:
 438afcf068d23b83a1533c1b83d2641d 2397 devel optional sqlite3_3.26.0-3.dsc
 d27f2f5e936b4c9ac5d67bd8ad4298e0 18984 devel optional 
sqlite3_3.26.0-3.debian.tar.xz
 1c21e986bd694da1e8f1c2127012fd59 9071 devel optional 
sqlite3_3.26.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlwOk58ACgkQ3OMQ54ZM
yL8jRA//eA8v0BMDqNGN2V5t5fCqRxDhe8gsvxzNyMsHxH310R0zVc10CbyW/OzS
OP2s6p/EfNOjFBgSvIqjhoyZtcw+/4aQVON8kNcL+QzEqnsB7wzaLiM9g97GBP01
K+gKA6WqljUpD8LwfmcFYNJvT6vlctzceNJ1Ot1ZWjQb7ATpcfJ9C/hB0ZFW0mcP
zr0bls9tjbxLFCInsDgFPclNxQaGiWkGcdK/dgQb8kAu11fyu/tdQ/UCBJG7UICf
nF0Xp6cRtvuaO2tpxv1GrbdT63pIzbh9oqseUlvfLzCRgA5iCqtZGvOtLSlOc//a
SrKvlX3Hzxh2xJaMIqvH67KPhphmgrMFvtQiPSRs+/dd7+1ZS8bfD6kvpmThXOJV
+RXW9ods2ijMUm/HV8EdcaKckjUOKu7XozQDtjJ51ejl0aKsoe5kP0A6Yebuu4xx
B/gFu0cMHIyHBAUvAQeyLUd5BWt694VSYFvPNypUEMdGBdWqJiXAzN/5dUR5ecR1
dyoY7FW9GRnPymI7Sjj1cZvBuTedWQt1xhTJcChHYN7rEALkMf2MtcfPdR7eNfoP
D2N2dgJUFZogWvfQZZoqA+/DVjQl8mr3jANtosiw3vz+gLvmPqdC4lVdR7p50U7V
YHQoc0ebB2YzVW/uuaokHJKu/J7YFrWY3QnKK2X/4Kq+lGJLucM=
=EGXq
-END PGP SIGNATURE End Message ---

Bug#904396: marked as done (foma: fails to upgrade from 'sid' - trying to overwrite /usr/bin/cgflookup)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 16:20:29 +
with message-id 
and subject line Bug#904396: fixed in foma 1:0.9.18+r243-4
has caused the Debian Bug report #904396,
regarding foma: fails to upgrade from 'sid' - trying to overwrite 
/usr/bin/cgflookup
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.)


-- 
904396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: foma
Version: 1:0.9.18~r248-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../foma_1%3a0.9.18~r248-1_amd64.deb ...
  Unpacking foma (1:0.9.18~r248-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/cgflookup', which is also in package foma-bin 
0.9.18+r243-1+b3
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/foma_1%3a0.9.18~r248-1_amd64.deb


cheers,

Andreas


foma-bin=0.9.18+r243-1+b3_foma=1%0.9.18~r248-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: foma
Source-Version: 1:0.9.18+r243-4

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated foma package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 20:31:04 +0530
Source: foma
Binary: foma libfoma0 libfoma0-dev foma-bin libfoma-dev
Architecture: source all amd64
Version: 1:0.9.18+r243-4
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 foma   - Tools for constructing various finite-state automata
 foma-bin   - Transitional package for foma
 libfoma-dev - Transitional package for libfoma0-dev
 libfoma0   - Foma runtime libraries
 libfoma0-dev - Foma development files
Closes: 904396
Changes:
 foma (1:0.9.18+r243-4) unstable; urgency=low
 .
   * debian/control:
 + Added old packages as transitional packages to fix upgrade.
   (Closes: #904396)
 + Readded Timo Jyrinki  as Maintainer, was
   dropped by mistake!
Checksums-Sha1:
 0902f042848f2e7a9902912ce04c353e5552a776 2284 foma_0.9.18+r243-4.dsc
 e5197a0ccafaf73271d13257d8201439dba6ebff 3028 foma_0.9.18+r243-4.debian.tar.xz
 effe253906383251391caecfc2b9e89935c8af98 6032 foma-bin_0.9.18+r243-4_all.deb
 a09e11260f60e565461c3e352db3e95fcb71252b 628524 
foma-dbgsym_0.9.18+r243-4_amd64.deb
 f6d885086dfe94a882195df272b8a382cb8ff08c 7243 
foma_0.9.18+r243-4_amd64.buildinfo
 fd1991b6e41cc4552b3fe6784190e6b655761e59 187628 foma_0.9.18+r243-4_amd64.deb
 4f2e18e90c1a91bec0cc97e814a39f32edb83808 6040 libfoma-dev_0.9.18+r243-4_all.deb
 38c9160d431eb8fc0869932743889683d5a1ded2 244028 
libfoma0-dbgsym_0.9.18+r243-4_amd64.deb
 2007209cc305ef6719bdcbc97d30f17331b2fd68 12256 
libfoma0-dev_0.9.18+r243-4_amd64.deb
 15a841b9b868f031e50b5d65a972b339c6040550 109768 
libfoma0_0.9.18+r243-4_amd64.deb
Checksums-Sha256:
 d8e3eef1888de905718b1f2736e67c033c5cc3ce3db3876465e5cfbb5ae4a1f3 2284 
foma_0.9.18+r243-4.dsc
 b5a58aaf7ec218769babeb82cbb9aa8622c491821918b1babc8ccf2ec83c4902 3028 
foma_0.9.18+r243-4.debian.tar.xz
 88e37b8b6cf5eb0eeec5d0011a2f634364111913976bc0a7751754324ae971b5 6032 
foma-bin_0.9.18+r243-4_all.deb
 22f303888c729b0d0e975c407cc66d074ca9cef405da453e2a30303c5bdb39a4 628524 
foma-dbgsym_0.9.18+r243-4_amd64.deb
 cf148d0c1c7039ae6f685291a22aa5da9f0a1cd9c179adc937699571dcab9bdd 7243 
foma_0.9.18+r243-4_amd64.buildinfo
 a4d49b049429a36fee76b936cae5cb9e

Bug#880393: nmuing cyrus-sasl2

[deb251]

On Sat, 29 Sep 2018 12:23:05 +0200 Helmut Grohne  wrote:

Control: tags 792851 + pending
Control: tags 880393 + pending patch

Dear cyrus-sasl2 maintainers,

I have prepared a NMU fixing the following bugs:

 * #792851: FTCBFS

   This one already had a patch since ages.

 * #880393: libsasl2-modules-gssapi-heimdal linked against mit krb5

   Actually, libgssapiv2.so is built against heimdal correctly. It just
   happens that the dh_auto_install overwrites the heimdal version with
   the mit version. Putting the relevant dh_install between the two
   dh_auto_install fixes the issue.

You can find a .debdiff attached. I'll be uploading it to delayed/10
later today.  Please let me know if I should delay it any longer.

Helmut


This problem is causing us serious heartburn. Is there a way to get the 
corrected stretch .deb file so we can move ahead with our upgrade to 
stretch?


Adam

Bug#916140: python3-matplotlib-dbg: missing Breaks+Replaces: python-matplotlib-dbg (<< 3)

[Andreas Beckmann]

Package: python3-matplotlib-dbg
Version: 3.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-matplotlib-dbg_3.0.2-1_amd64.deb ...
  Unpacking python3-matplotlib-dbg (3.0.2-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-matplotlib-dbg_3.0.2-1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/debug/usr/lib/python3/dist-packages/matplotlib/_contour.cpython-36dm-x86_64-linux-gnu.so',
 which is also in package python-matplotlib-dbg 2.2.3-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-matplotlib-dbg_3.0.2-1_amd64.deb


Why is there python3.6 stuff in python-matplotlib-dbg?


cheers,

Andreas


python-matplotlib-dbg=2.2.3-2_python3-matplotlib-dbg=3.0.2-1.log.gz
Description: application/gzip

Bug#916139: trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package hplip 3.17.10+repack0-7

[Laurent Bigonville]

Package: printer-driver-postscript-hp
Version: 3.18.12+dfsg0-1
Severity: serious

Hi,

When upgrading a old VM, I got the following error:

Unpacking printer-driver-postscript-hp (3.18.12+dfsg0-1) over 
(3.17.10+repack0-7) ...
dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/lib/cups/filter/hpps', which is also in package 
hplip 3.17.10+repack0-7
Errors were encountered while processing:
 /var/cache/apt/archives/printer-driver-postscript-hp_3.18.12+dfsg0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Looks like the Breaks/Replaces against hplip should be bumped.

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages printer-driver-postscript-hp depends on:
ii  libc6 2.28-2
ii  libcups2  2.2.10-1
ii  python3   3.7.1-2
ii  xz-utils  5.2.2-1.3

printer-driver-postscript-hp recommends no packages.

Versions of packages printer-driver-postscript-hp suggests:
ii  hplip  3.18.12+dfsg0-1

-- no debconf information

Bug#915686: Bug #915686 in bmap-tools marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #915686 in bmap-tools reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/bmap-tools/commit/f6f937e8036115454f9e997a04a21b730e2e3cb5


Fix FTBFS with Python 3.7

Closes: #915686


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/915686

Processed: Bug #915686 in bmap-tools marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #915686 [src:bmap-tools] src:bmap-tools: FTBFS with Python 3.7 as default
Added tag(s) pending.

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

Processed: found 915805 in 3.0.4-1, tagging 915733

[Debian Bug Tracking System]

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

> found 915805 3.0.4-1
Bug #915805 [src:swift-im] Should this package be removed?
Marked as found in versions swift-im/3.0.4-1.
> tags 915733 + experimental
Bug #915733 {Done: Adrian Bunk } [src:gcc-mingw-w64] 
gcc-mingw-w64 is still based on GCC 7
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: tagging 892348

[Debian Bug Tracking System]

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

> tags 892348 + ftbfs buster sid
Bug #892348 [src:xmlroff] xmlroff: Please use 'pkg-config' to find FreeType 2
Added tag(s) sid, ftbfs, and buster.
> thanks
Stopping processing here.

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

Processed: severity of 892348 is serious

[Debian Bug Tracking System]

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

> severity 892348 serious
Bug #892348 [src:xmlroff] xmlroff: Please use 'pkg-config' to find FreeType 2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#915998: marked as done (tcplay FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 15:14:45 +
with message-id 
and subject line Bug#915998: fixed in tcplay 1.1-6
has caused the Debian Bug report #915998,
regarding tcplay FTBFS with glibc 2.28
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.)


-- 
915998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcplay
Version: 1.1-5
Severity: serious
Tags: ftbfs

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

...
/build/1st/tcplay-1.1/tcplay.c: In function 'xlate_maj_min':
/build/1st/tcplay-1.1/tcplay.c:1339:14: warning: implicit declaration of 
function 'makedev' [-Wimplicit-function-declaration]
  dev_t dev = makedev(maj, min);
  ^~~
...
/usr/bin/ar qc libtcplay.a  CMakeFiles/tcplay-static.dir/tcplay_api.c.o 
CMakeFiles/tcplay-static.dir/tcplay.c.o CMakeFiles/tcplay-static.dir/crc32.c.o 
CMakeFiles/tcplay-static.dir/safe_mem.c.o CMakeFiles/tcplay-static.dir/io.c.o 
CMakeFiles/tcplay-static.dir/hdr.c.o CMakeFiles/tcplay-static.dir/humanize.c.o 
CMakeFiles/tcplay-static.dir/crypto.c.o 
CMakeFiles/tcplay-static.dir/generic_xts.c.o 
CMakeFiles/tcplay-static.dir/crypto-gcrypt.c.o 
CMakeFiles/tcplay-static.dir/pbkdf2-gcrypt.c.o
/usr/bin/ranlib libtcplay.a
/usr/bin/ld: CMakeFiles/tcplay-bin.dir/tcplay.c.o: in function `xlate_maj_min':
./obj-x86_64-linux-gnu/./tcplay.c:1339: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[4]: Leaving directory '/build/1st/tcplay-1.1/obj-x86_64-linux-gnu'
make[4]: *** [CMakeFiles/tcplay-bin.dir/build.make:237: tcplay] Error 1
--- End Message ---
--- Begin Message ---
Source: tcplay
Source-Version: 1.1-6

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated tcplay package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 10 Dec 2018 14:17:16 +
Source: tcplay
Binary: tcplay libtcplay libtcplay-dev
Architecture: source
Version: 1.1-6
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 libtcplay  - Free and simple TrueCrypt Implementation based on dm-crypt
 libtcplay-dev - Free and simple TrueCrypt Implementation based on dm-crypt
 tcplay - Free and simple TrueCrypt Implementation based on dm-crypt
Closes: 915998
Changes:
 tcplay (1.1-6) unstable; urgency=medium
 .
   * Update Standards-Version to 4.2.1 .
 .
   [ Alon Bar-Lev  ]
   * Include sys/sysmacros.h for recent glibc (closes: #915998).
Checksums-Sha1:
 5d27df48829dcf4bd321388245c67280180f0978 1897 tcplay_1.1-6.dsc
 b9f6371924f362da5917b10e7005498424c687a4 7264 tcplay_1.1-6.debian.tar.xz
 a181c2ee08512545944a192c76746d3d0fc8bf08 8746 tcplay_1.1-6_amd64.buildinfo
Checksums-Sha256:
 d538b825bdfba585bcb580297ddd2028c2fcaedd78be3ff241e68a66b67b4107 1897 
tcplay_1.1-6.dsc
 a39458d3672b603426d6b8df3c307136e504cd7db23cc5bd35a2b50a4675d851 7264 
tcplay_1.1-6.debian.tar.xz
 0724f5cb5e1e53f2535038071dbfb0f13e2a34539383b09f9e05629b67b9eb2c 8746 
tcplay_1.1-6_amd64.buildinfo
Files:
 721ce1d1c5ccd3da0245e1514f0aae53 1897 admin optional tcplay_1.1-6.dsc
 557a1693b75d425b73de0a51bb5a58c3 7264 admin optional tcplay_1.1-6.debian.tar.xz
 963936bf5465a40eb56ebea085649667 8746 admin optional 
tcplay_1.1-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlwOerAACgkQ3OMQ54ZM
yL+SfhAAjaRYg97EAtTmXSSC36tF37U7DUJWbzTcEzc65uhVCiUkgCyZea9ouY1C
NP+kQDIH3PQ8/piZXtkIRF/r9gnzIKegMklG7x4XHeyYhxnRNc9+Wad+0+dOKfSu
Xe1wy0p9+k44xorZKPIiMBmQB7SaezR1iQdLCbZHeHj3e3wujAcJK8NCX9MgHtBt
J5ls2SRLvcafq2HUcbDdNrk34eC//NEfzOjuSqOVwKVYQo4F1NzVMe0hF1X6CvtP
xVw1S3wYdH3vQA7p03NjZy4UMZbM1k1FRKkySdUTqYhUdA0EYfCnYP4/Sd+jMHKO
KuBZLfbtuFZaZGbQpw6qGxt+jc0q6RhviKzaRZMJwwhgW04mKcjSrCp1UTylLJGd
YuMk2BUthdoZiIvDOvxGYroYAezewGnD0NqLlrgK6daO5GqLTuMJhzAHE2DzB0Il
48lWzSgtnxSoZU+SS1/up0AxN0zx3JsJbNOCNRVQAO2YwNldWQfr5ogrYwYfULy8
o1h2y6K9/OfPm1Ty66Ejh

Bug#916133: xmlcopyeditor: missing build dependency on pkg-config

[Adrian Bunk]

Source: xmlcopyeditor
Version: 1.2.1.3-2
Severity: serious
Tags: ftbfs

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

...
dh_autoreconf
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:43: error: possibly undefined macro: AC_MSG_RESULT
  If this token and others are legitimate, please use m4_pattern_allow.
  See the Autoconf documentation.
configure.ac:46: error: possibly undefined macro: AC_MSG_ERROR
configure.ac:109: error: possibly undefined macro: AC_CHECK_HEADER
autoreconf: /usr/bin/autoconf failed with exit status: 1
dh_autoreconf: autoreconf -f -i returned exit code 1
make: *** [debian/rules:25: config-stamp] Error 2

Bug#916132: hepmc FTBFS: FAIL testWeights

[Adrian Bunk]

Source: hepmc
Version: 2.06.09-3
Severity: serious
Tags: ftbfs

Some recent change in unstable makes hepmc FTBFS:

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

...
make  check-TESTS
make[3]: Entering directory '/build/1st/hepmc-2.06.09/test'
make[4]: Entering directory '/build/1st/hepmc-2.06.09/test'
PASS: testSimpleVector
PASS: testUnits
PASS: testHepMC.sh
PASS: testHepMCIteration.sh
PASS: testMass.sh
PASS: testFlow.sh
PASS: testStreamIO.sh
PASS: testPrintBug.sh
PASS: testMultipleCopies
PASS: testPolarization.sh
../test-driver: line 107: 52027 Segmentation fault  "$@" > $log_file 2>&1
FAIL: testWeights

   HepMC 2.06.09: test/test-suite.log


# TOTAL: 11
# PASS:  10
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: testWeights
=

FAIL testWeights (exit status: 139)


Testsuite summary for HepMC 2.06.09

# TOTAL: 11
# PASS:  10
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to https://savannah.cern.ch/projects/hepmc/

make[4]: *** [Makefile:881: test-suite.log] Error 1



Backtrace:

Core was generated by `/tmp/hepmc-2.06.09/test/.libs/testWeights'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x7fc39a374474 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x7fc39a4ddc08 in 
std::_Rb_tree_iterator, std::allocator > const, unsigned long> 
>::operator++ (this=)
at /usr/include/c++/8/bits/stl_tree.h:285
#2  HepMC::WeightContainer::pop_back (this=this@entry=0x7ffdd7410790)
at WeightContainer.cc:56
#3  0x55e8672df5ab in main () at testWeights.cc:36

Bug#911708: marked as done (scikit-learn breaks astroml autopkgtest: ImportError: cannot import name 'GMM')

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 14:44:12 +
with message-id 
and subject line Bug#911708: fixed in astroml 0.3-8
has caused the Debian Bug report #911708,
regarding scikit-learn breaks astroml autopkgtest: ImportError: cannot import 
name 'GMM'
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.)


-- 
911708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scikit-learn, astroml
Control: found -1 scikit-learn/0.20.0+dfsg-1
Control: found -1 astroml/0.3-7
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of scikit-learn the autopkgtest of astroml fails in
testing when that autopkgtest is run with the binary packages of
scikit-learn from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
scikit-learn   from testing0.20.0+dfsg-1
astromlfrom testing0.3-7
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
of scikit-learn to testing [1]. Due to the nature of this issue, I filed
this bug report against both packages. Can you please investigate the
situation and reassign the bug to the right package? If needed, please
change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=scikit-learn

https://ci.debian.net/data/autopkgtest/testing/amd64/a/astroml/1196880/log.gz

autopkgtest [04:37:20]: test command2: [---
/usr/lib/python3/dist-packages/astroML/time_series/periodogram.py:8:
UserWarning: Using slow version of lomb_scargle. Install astroML_addons
to use an optimized version
  warnings.warn("Using slow version of lomb_scargle. Install
astroML_addons "
/usr/lib/python3/dist-packages/astroML/dimensionality/iterative_pca.py:136:
RuntimeWarning: invalid value encountered in true_divide
  ratio_i = X[i][notM[i]] / X_recons[i][notM[i]]
.E../usr/lib/python3/dist-packages/astroML/stats/_binned_statistic.py:323:
RuntimeWarning: invalid value encountered in true_divide
  result[a] /= flatcount
/usr/lib/python3/dist-packages/numpy/core/fromnumeric.py:2957:
RuntimeWarning: Mean of empty slice.
  out=out, **kwargs)
/usr/lib/python3/dist-packages/numpy/core/_methods.py:80:
RuntimeWarning: invalid value encountered in double_scalars
  ret = ret.dtype.type(ret / rcount)
..
==
ERROR: Failure: ImportError (cannot import name 'GMM')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File "/usr/lib/python3/dist-packages/nose/loader.py", line 417, in
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 47, in
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python3/dist-packages/nose/importer.py", line 94, in
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/usr/lib/python3.6/imp.py", line 245, in load_module
return load_package(name, filename)
  File "/usr/lib/python3.6/imp.py", line 217, in load_package
return _load(spec)
  File "", line 684, in _load
  File "", line 665, in _load_unlocked
  File "", line 678, in exec_module
  File "", line 219, in
_call_with_frames_removed
  File
"/usr/lib/python3/dist-packages/astroML/classification/__init__.py",
line 1, in 
from .gmm_bayes import GMMBayes
  File
"/usr/lib/python3/dist-packages/astroML/classification/gmm_bayes.py",
line 8, in 
from sklearn.mixture import GMM
ImportError: cannot import name 'GMM'

==
ERROR: Failure: ImportError (cannot import name 'GMM')
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 39, in runTest
raise self.exc_val.wi

Processed: retitle 916129 to zita-rev1 FTBFS due to freetype-config usage

[Debian Bug Tracking System]

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

> retitle 916129 zita-rev1 FTBFS due to freetype-config usage
Bug #916129 [src:zita-rev1] zita-rev1 FTBFS
Changed Bug title to 'zita-rev1 FTBFS due to freetype-config usage' from 
'zita-rev1 FTBFS'.
> thanks
Stopping processing here.

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

Bug#905254: Relations to other packages

[Cyrille Bollu]

Cacti:


Latest version of cacti upstream still uses PHPMailer 5.2.x.

I've created a bug upstream: https://github.com/Cacti/cacti/issues/2206

tt-rss:


It seems like latest version don't necessarily use phpmailer anymore:

(https://git.tt-rss.org/fox/tt-rss/src/master)

>commit 57932e183745bada9c6183056597cb5276f68d10
>Author: Andrew Dolgov 
>Date:   Thu Nov 22 14:45:14 2018 +0300
>
>remove PHPMailer and related directives from config.php-dist; add
pluggable Mailer class
>

maybe tt-rss maintainer should be asked to update to latest upstream
version?

wordpress:


I haven't understand what should be done

ocsinventory-server & ocsinventory-reports:
=

Newest upstream version (2.5) will depend on PHPMailer 6.x

Not upgrading libphp-phpmailer  blocks upgrade to newest upstream versions
of these packages (which also somehow blocks #905396 and CVE-2018-14473).

I'll try to create the link between those bugs (#905254 block #905396)

Br,

Cyrille

Bug#913645: Oldstable also affected

[Bastian Neuburger]

Dear Maintainer,

since upstream was able to reproduce the problem and locate the commits 
that cause it I did no further tests.


It seems like they will undo two commits in order to solve the problem, 
hopefully not too many people get bit by this.


Cheers,

Bastian

On 12/3/18 12:58 PM, Bastian Neuburger wrote:

Hi Carsten,

I forgot to report back, but I also created Upstream bug 1510212 
(https://bugzilla.mozilla.org/show_bug.cgi?id=1510212). As I stated 
there it might take a while until I can test migration again, since I 
reinstalled my test machine with Buster and thus have no test 
environment with Jessie or Stretch right now.


I'll report back to upstream how this goes.

Bug#916064: marked as done (ext4magic FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 14:14:24 +
with message-id 
and subject line Bug#916064: fixed in ext4magic 0.3.2-11
has caused the Debian Bug report #916064,
regarding ext4magic FTBFS with glibc 2.28
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.)


-- 
916064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ext4magic
Version: 0.3.2-10
Severity: serious
Tags: ftbfs

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

...
recover.c: In function 'recover_file':
recover.c:478:35: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
retval = mknod(helpname, type ,makedev(major, minor));
   ^~~
...
libtool: link: gcc -O2 -g -D_FILE_OFFSET_BITS=64 -g -O2 
-ffile-prefix-map=/build/1st/ext4magic-0.3.2=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ext4magic 
ext4magic-block.o ext4magic-dir_list.o ext4magic-ext4magic.o 
ext4magic-extent_db.o ext4magic-file_type.o ext4magic-hard_link_stack.o 
ext4magic-imap_search.o ext4magic-inode.o ext4magic-journal.o 
ext4magic-lookup_local.o ext4magic-magic_block_scan.o ext4magic-recover.o 
ext4magic-ring_buf.o ext4magic-util.o  -le2p -luuid -lblkid -lz -lbz2 -lmagic 
-lext2fs
/usr/bin/ld: ext4magic-recover.o: in function `recover_file':
./src/recover.c:478: undefined reference to `makedev'
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:449: ext4magic] Error 1
--- End Message ---
--- Begin Message ---
Source: ext4magic
Source-Version: 0.3.2-11

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

Debian distribution maintenance software
pp.
Joao Eriberto Mota Filho  (supplier of updated ext4magic 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 10 Dec 2018 10:13:29 -0200
Source: ext4magic
Binary: ext4magic
Architecture: source
Version: 0.3.2-11
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Joao Eriberto Mota Filho 
Description:
 ext4magic  - recover deleted files from ext3 or ext4 partitions
Closes: 916064
Changes:
 ext4magic (0.3.2-11) unstable; urgency=medium
 .
   * Team upload.
   * debian/control: bumped Standards-Version to 4.2.1.
   * debian/copyright:
   - Added rights for Hilko Bengen and Raphaël Hertzog.
   - Updated packaging copyright years.
   * debian/patches/:
   - fix-FTBFS-with-glibc-2.28.patch: added to fix a FTBFS. (Closes: 
#916064)
   - fix-spelling.patch: added to fix a wrong word shown in screen.
   * debian/source/include-binaries: added to control debian/tests/test.img.
   * debian/tests/*: created to provide trivial tests.
Checksums-Sha1:
 8046f8e71066d73d05d6b6564ca58b9b6e0c4700 2039 ext4magic_0.3.2-11.dsc
 403bda943eb0058cbfb4f99f0ee27914edd91461 173796 
ext4magic_0.3.2-11.debian.tar.xz
 e86a845182aedbb5a3b97a98831cfd816ce6060c 5190 
ext4magic_0.3.2-11_source.buildinfo
Checksums-Sha256:
 cf8480316065d491b8e8f7419c348e655790f94aaec8439ea9a50c2494908c40 2039 
ext4magic_0.3.2-11.dsc
 01cb2a6dcf408694be0427f9d522259cf41a93148c15128dc69e55315033d663 173796 
ext4magic_0.3.2-11.debian.tar.xz
 bae5663b9fade786d76f7168bb45ef984f3b44bce10457bb11e2a3feb55e3159 5190 
ext4magic_0.3.2-11_source.buildinfo
Files:
 44cb0ea2769c1dcfebfbaa34fd74235f 2039 utils optional ext4magic_0.3.2-11.dsc
 8bd43f3536b63c848d915e84508fc574 173796 utils optional 
ext4magic_0.3.2-11.debian.tar.xz
 d620637c70bfe0f4d4dd2b2bddc4698f 5190 utils optional 
ext4magic_0.3.2-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAlwObPUACgkQ3mO5xwTr
6e8KCA//aBgoZ4uaNl4Da9em7e4dXugN5FExQeUocQtSZklux3ZGRmYVL8dOdXqk
Ti+gIG66QLettoPtvOaa6au8dA0l6fISC66AgwZ/laQ5NhfiAKHhza5hqtAC4vJc
XA1nT5+BerU2cWGAGmTElPfIaTty2AU7/GFgwupLXABxUMlrGIovvS3Q9T1JA86P
BK5I8IOoxzifo8gocNd11mn5hyF+LFB6tu2CizAUANLN1zlIb5k69RinZIfUsBej
TwVQneQegpz0BHQXZ8El9SOGhRqp1D9HBfIRCGGSFcE4h2vQSxCy5Pqy

Processed: affects 915636

[Debian Bug Tracking System]

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

> affects 915636 src:python-cffi
Bug #915636 [python3-virtualenv] python3-virtualenv: incompatible with 
python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0
Added indication that 915636 affects src:python-cffi
> thanks
Stopping processing here.

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

Bug#916130: zita-bls1 FTBFS due to freetype-config usage

[Adrian Bunk]

Source: zita-bls1
Version: 0.1.0-3
Severity: serious
Tags: ftbfs buster sid

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

...
g++ -g -O2 -ffile-prefix-map=/build/1st/zita-bls1-0.1.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -O2 -ffast-math -Wall 
-MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -DVERSION=\"0.1.0\" 
-DSHARED=\"/usr/share/zita-bls1\" -I/usr/X11R6/include `freetype-config 
--cflags`  -c -o shuffler.o shuffler.cc
/bin/sh: 1: freetype-config: not found
In file included from /usr/include/clxclient.h:31,
 from styles.h:25,
 from styles.cc:22:
/usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or 
directory
 #include 
  ^~~~
compilation terminated.


freetype-config has been removed in Debian in favour of pkg-config.

The package also lacks a direct build dependency on libfreetype6-dev.

Bug#916129: zita-rev1 FTBFS

[Adrian Bunk]

Source: zita-rev1
Version: 0.2.1-5
Severity: serious
Tags: ftbfs buster sid

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

...
g++ -g -O2 -ffile-prefix-map=/build/1st/zita-rev1-0.2.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O2 -ffast-math -Wall -MMD -MP -DVERSION=\"0.2.1\" 
-DSHARED=\"/usr/share/zita-rev1\" -I/usr/X11R6/include `freetype-config 
--cflags`  -c -o pareq.o pareq.cc
/bin/sh: 1: freetype-config: not found
In file included from /usr/include/clxclient.h:31,
 from styles.h:25,
 from styles.cc:22:
/usr/include/X11/Xft/Xft.h:39:10: fatal error: ft2build.h: No such file or 
directory
 #include 
  ^~~~
compilation terminated.
make[1]: *** [: styles.o] Error 1


freetype-config has been removed in Debian in favour of pkg-config.

The package also lacks a direct build dependency on libfreetype6-dev.

Bug#915112: pymol: FTBFS with glew 2.1

[Andreas Beckmann]

On Fri, 7 Dec 2018 09:47:33 +0200 Juhani Numminen
 wrote:
> Indeed it seems that the patch didn't affect glew.h. I don't know the package
> too well but that's a >1 MB header that cannot be found in upstream git, and
> I get the impression that it is generated using auto/Makefile.
> 
> The debian build logs don't contain "Creating glew.h" so I believe the 
> original
> upstream-distributed include/GL/glew.h is shipped.

The generation of the headers seems to be "special". It starts with
cloning a git repository (RC bug? does not include source to regenerate
the headers) and quickly fails with

bash: bin/update_ext.sh: /bin/bash^M: bad interpreter: No such file
or directory

where I stopped trying to understand what's happening.

You should probably just apply the patch additionally to the shipped
include/GL/glew.h


Andreas

Processed: block 905396 with 905254

[Debian Bug Tracking System]

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

> block 905396 with 905254
Bug #905396 [src:ocsinventory-server] ocsinventory-server: CVE-2018-12482 
CVE-2018-12483 CVE-2018-14473
905396 was blocked by: 906668
905396 was not blocking any bugs.
Added blocking bug(s) of 905396: 905254
> thanks
Stopping processing here.

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

Bug#916128: coyim FTBFS: test failure

[Adrian Bunk]

Source: coyim
Version: 0.3.8+ds-5
Severity: serious
Tags: ftbfs

Some recent change in unstable makes coyim FTBFS:

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

...
FAIL: connection_policy_test.go:161: 
ConnectionPolicySuite.Test_buildProxyChain_Returns

connection_policy_test.go:181:
c.Check(chain, DeepEquals, expectedProxy)
... obtained *socks.Dialer = &socks.Dialer{cmd:1, proxyNetwork:"tcp", 
proxyAddress:"proxy.local", ProxyDial:(func(context.Context, string, string) 
(net.Conn, error))(0x678b20), AuthMethods:[]socks.AuthMethod(nil), 
Authenticate:(func(context.Context, io.ReadWriter, socks.AuthMethod) 
error)(nil)}
... expected *socks.Dialer = &socks.Dialer{cmd:1, proxyNetwork:"tcp", 
proxyAddress:"proxy.local", ProxyDial:(func(context.Context, string, string) 
(net.Conn, error))(0x678b20), AuthMethods:[]socks.AuthMethod(nil), 
Authenticate:(func(context.Context, io.ReadWriter, socks.AuthMethod) 
error)(nil)}

OOPS: 31 passed, 1 FAILED
--- FAIL: Test (5.08s)
...

Bug#914953: marked as done (FTBFS with Python 3.7 on many architectures)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 12:04:04 +
with message-id 
and subject line Bug#914953: fixed in libarcus 3.3.0-2
has caused the Debian Bug report #914953,
regarding FTBFS with Python 3.7 on many architectures
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.)


-- 
914953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libarcus
Version: 3.3.0-1+b1
Severity: serious
Tags: ftbfs

Hi,

for the Python 3.7 default transition, libarcus was binNMUed against
Python 3.7, but FTBFS on at least amd64, arm64, i386, mips, ppc64el
and s390x:

https://buildd.debian.org/status/package.php?p=libarcus&suite=unstable

So far it only build fine only on these release architectures" armel,
armhf, mipsel64.

Probably relevant log excerpt on amd64:

dpkg-gensymbols -plibarcus3 -Idebian/libarcus3.symbols -Pdebian/libarcus3 
-edebian/libarcus3/usr/lib/x86_64-linux-gnu/libArcus.so.1.1.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libarcus3/DEBIAN/symbols doesn't match 
completely debian/libarcus3.symbols
--- debian/libarcus3.symbols (libarcus3_3.3.0-1+b2_amd64)
+++ dpkg-gensymbolsiZ3ci6   2018-11-28 18:20:30.346117939 +
@@ -29,12 +29,12 @@
  (c++)"Arcus::Private::PlatformSocket::flush()@Base" 2.3.1
  (c++)"Arcus::Private::PlatformSocket::getNativeErrorCode()@Base" 2.3.1
  (c++)"Arcus::Private::PlatformSocket::listen(int)@Base" 2.3.1
- (c++|optional)"Arcus::Private::PlatformSocket::readBytes(unsigned int, 
char*)@Base" 3.0.3
+#MISSING: 3.3.0-1+b2# 
(c++|optional)"Arcus::Private::PlatformSocket::readBytes(unsigned int, 
char*)@Base" 3.0.3
  (c++|optional)"Arcus::Private::PlatformSocket::readBytes(unsigned long, 
char*)@Base" 2.3.1
  (c++)"Arcus::Private::PlatformSocket::readUInt32(unsigned int*)@Base" 2.5.0
  (c++)"Arcus::Private::PlatformSocket::setReceiveTimeout(int)@Base" 2.3.1
  
(c++)"Arcus::Private::PlatformSocket::shutdown(Arcus::Private::PlatformSocket::ShutdownDirection)@Base"
 2.3.1
- (c++|optional)"Arcus::Private::PlatformSocket::writeBytes(unsigned int, char 
const*)@Base" 3.0.3
+#MISSING: 3.3.0-1+b2# 
(c++|optional)"Arcus::Private::PlatformSocket::writeBytes(unsigned int, char 
const*)@Base" 3.0.3
  (c++|optional)"Arcus::Private::PlatformSocket::writeBytes(unsigned long, char 
const*)@Base" 2.3.1
  (c++)"Arcus::Private::PlatformSocket::writeUInt32(unsigned int)@Base" 2.5.0
  (c++)"Arcus::Private::PlatformSocket::~PlatformSocket()@Base" 2.3.1
@@ -65,83 +65,88 @@
  (c++)"Arcus::SocketListener::setSocket(Arcus::Socket*)@Base" 2.3.1
  (c++)"ErrorCollector::AddError(std::__cxx11::basic_string, std::allocator > const&, int, int, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 2.3.1
  (c++)"ErrorCollector::~ErrorCollector()@Base" 2.3.1
+ 
_ZNSt10_HashtableIPKN6google8protobuf10DescriptorESt4pairIKS4_jESaIS7_ENSt8__detail10_Select1stESt8equal_toIS4_ESt4hashIS4_ENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNS9_10_Hash_nodeIS7_Lb0EEEm@Base
 3.3.0-1+b2
+ 
_ZNSt10_HashtableIjSt4pairIKjPKN6google8protobuf7MessageEESaIS7_ENSt8__detail10_Select1stESt8equal_toIjESt4hashIjENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNS9_10_Hash_nodeIS7_Lb0EEEm@Base
 3.3.0-1+b2
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 3.3.0-1+b2
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 3.3.0-1+b2
+ _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 3.3.0-1+b2
  (c++)"createAddress(std::__cxx11::basic_string, 
std::allocator > const&, int)@Base" 2.3.1
  
(c++)"google::protobuf::compiler::MultiFileErrorCollector::AddWarning(std::__cxx11::basic_string, std::allocator > const&, int, int, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 2.3.1
- (c++|optional)"google::protobuf::internal::pLinuxKernelCmpxchg@Base" 3.0.3
- (c++|optional)"google::protobuf::internal::pLinuxKernelMemoryBarrier@Base" 
3.0.3
+#MISSING: 3.3.0-1+b2# 
(c++|optional)"google::protobuf::internal::pLinuxKernelCmpxchg@Base" 3.0.3
+#MISSING: 3.3.0-1+b2# 
(c++|optional)"google::protobuf::internal::pLinuxKernelMemoryBarrier@Base" 3.0.3
  (c++)"hash(std::__cxx11::basic_strin

Processed: forwarded

[Debian Bug Tracking System]

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

> forwarded 916104 https://github.com/markfasheh/duperemove/pull/169
Bug #916104 [src:duperemove] duperemove FTBFS with glibc 2.28
Set Bug forwarded-to-address to 
'https://github.com/markfasheh/duperemove/pull/169'.
>
End of message, stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 916064 https://sourceforge.net/p/ext4magic/tickets/4/
Bug #916064 [src:ext4magic] ext4magic FTBFS with glibc 2.28
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/ext4magic/tickets/4/'.
>
End of message, stopping processing here.

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

Bug#916109: marked as done (osmium-tool FTBFS with libosmium2-dev 2.15.0-1)

[Debian Bug Tracking System]

Your message dated Mon, 10 Dec 2018 11:49:26 +
with message-id 
and subject line Bug#916109: fixed in osmium-tool 1.9.1-2
has caused the Debian Bug report #916109,
regarding osmium-tool FTBFS with libosmium2-dev 2.15.0-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.)


-- 
916109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmium-tool
Version: 1.9.1-1
Severity: serious
Tags: ftbfs

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

...
cd /build/1st/osmium-tool-1.9.1/obj-x86_64-linux-gnu/test && /usr/bin/c++  
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-I/build/1st/osmium-tool-1.9.1/obj-x86_64-linux-gnu/src 
-I/build/1st/osmium-tool-1.9.1/test/include 
-I/build/1st/osmium-tool-1.9.1/test/../src 
-I/build/1st/osmium-tool-1.9.1/test/../src/extract 
-I/build/1st/osmium-tool-1.9.1/test/../include -isystem 
/build/1st/osmium-tool-1.9.1/include  -g -O2 
-ffile-prefix-map=/build/1st/osmium-tool-1.9.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -std=c++11 
-Wall -Wextra -pedantic -Wredundant-decls -Wdisabled-optimization 
-Wctor-dtor-privacy -Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo 
-Wold-style-cast -pthread -o CMakeFiles/unit_tests.dir/__/src/util.cpp.o -c 
/build/1st/osmium-tool-1.9.1/src/util.cpp
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:27:
/usr/include/osmium/tags/tags_filter.hpp:157:44: error: conflicting declaration 
'using TagsFilter = class osmium::TagsFilterBase'
 using TagsFilter = TagsFilterBase;
^
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:24:
/build/1st/osmium-tool-1.9.1/src/util.hpp:37:11: note: previous declaration as 
'class osmium::TagsFilter'
 class TagsFilter;
   ^~
In file included from /build/1st/osmium-tool-1.9.1/src/util.cpp:33:
/usr/include/c++/8/iostream:60:10: error: 'istream' does not name a type
   extern istream cin;  /// Linked to standard input
  ^~~
/usr/include/c++/8/iostream:61:10: error: 'ostream' does not name a type
   extern ostream cout;  /// Linked to standard output
  ^~~
/usr/include/c++/8/iostream:62:10: error: 'ostream' does not name a type
   extern ostream cerr;  /// Linked to standard error (unbuffered)
  ^~~
/usr/include/c++/8/iostream:63:10: error: 'ostream' does not name a type
   extern ostream clog;  /// Linked to standard error (buffered)
  ^~~
/usr/include/c++/8/iostream:66:10: error: 'wistream' does not name a type
   extern wistream wcin;  /// Linked to standard input
  ^~~~
/usr/include/c++/8/iostream:67:10: error: 'wostream' does not name a type
   extern wostream wcout; /// Linked to standard output
  ^~~~
/usr/include/c++/8/iostream:68:10: error: 'wostream' does not name a type
   extern wostream wcerr; /// Linked to standard error (unbuffered)
  ^~~~
/usr/include/c++/8/iostream:69:10: error: 'wostream' does not name a type
   extern wostream wclog; /// Linked to standard error (buffered)
  ^~~~
/usr/include/c++/8/iostream:74:10: error: 'ios_base' does not name a type
   static ios_base::Init __ioinit;
  ^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 'void 
osmium::warning(const char*)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10: error: 'cerr' is not a member 
of 'std'
 std::cerr << "WARNING: " << text;
  ^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10: note: 'std::cerr' is defined 
in header ''; did you forget to '#include '?
/build/1st/osmium-tool-1.9.1/src/util.cpp:34:1:
+#include 
 #include 
/build/1st/osmium-tool-1.9.1/src/util.cpp:62:10:
 std::cerr << "WARNING: " << text;
  ^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 'void 
osmium::warning(const string&)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:66:10: error: 'cerr' is not a member 
of 'std'
 std::cerr << "WARNING: " << text;
  ^~~~
/build/1st/osmium-tool-1.9.1/src/util.cpp:66:10: note: 'std::cerr' is defined 
in header ''; did you forget to '#include '?
/build/1st/osmium-tool-1.9.1/src/util.cpp: In function 
'std::pair > 
osmium::get_filter_expression(const string&)':
/build/1st/osmium-tool-1.9.1/src/util.cpp:113:48: error: call of overloaded 
'get_types(std::__cxx11::basic_string)' is ambiguous
 entities = get_types(str.substr(0, pos));
^
In file included from /buil

Bug#915334: Details on faulty code section + proposal

[Étienne Mollier]

Good Day,

It seems that, since GlibC 2.28, a hack in ipl/cfuncs/fpoll.c
fails to detect the newer level of Gnu operating system, as the
definition of _STDIO_USES_IOSTREAM seems to be have been
dropped.  The following patch completely drops support for older
Gnu libraries:

--- icon-9.4.3.orig/ipl/cfuncs/fpoll.c
+++ icon-9.4.3/ipl/cfuncs/fpoll.c
@@ -59,12 +59,9 @@ int fpoll(int argc, descriptor *argv)/*

/* check for data already in buffer */
/* there's no legal way to do this in C; we cheat */
-#if defined(__GLIBC__) && defined(_STDIO_USES_IOSTREAM)/* new GCC 
library */
+#if defined(__GLIBC__)
if (f->_IO_read_ptr < f->_IO_read_end)
   RetArg(1);
-#elif defined(__GLIBC__)   /* old GCC library */
-   if (f->__bufp < f->__get_limit)
-  RetArg(1);
 #elif defined(_FSTDIO) /* new BSD library */
if (f->_r > 0)
   RetArg(1);

I have no idea if this is a good course of action, and am not
exactly happy with my patch, but it does fix the build in
Unstable without breaking Stable or Testing, according to my few
tests.

Haven't had much issues rebuilding my Noweb documents/programs
afterwards, but I have just the "iconx" package installed.

I hope this helps,
-- 
Étienne Mollier 

Bug#915476: ledmon FTBFS with glibc 2.28

[Juhani Numminen]

On Tue, 04 Dec 2018 01:44:28 +0200 Adrian Bunk  wrote:
> Source: ledmon
> Version: 0.79-2
> Severity: serious
> Tags: ftbfs buster sid
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ledmon.html
> 
> ...
> smp.c: In function '_open_smp_device':
> smp.c:301:46: warning: implicit declaration of function 'makedev' 
> [-Wimplicit-function-declaration]
>   if (mknod(buf, S_IFCHR | S_IRUSR | S_IWUSR, makedev(dmaj, dmin)) < 0)
>   ^~~
> ...
> ./src/smp.c:301: undefined reference to `makedev'

This will likely just require a including sys/sysmacros.h i.e. this commit
https://github.com/intel/ledmon/commit/e51e1a855df80e34e166984373dce7d765d61d52

Quoting https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html:
"The macros 'major', 'minor', and 'makedev' are now only available from
the header "

--
Juhani

Processed: Re: Bug#916008: wmhdplop FTBFS with glibc 2.28

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + fixed-upstream
Bug #916008 [src:wmhdplop] wmhdplop FTBFS with glibc 2.28
Added tag(s) fixed-upstream.

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

Bug#916008: wmhdplop FTBFS with glibc 2.28

[Juhani Numminen]

Control: tags -1 + fixed-upstream

On Sun, 9 Dec 2018 15:43:14 +0100 Andreas Metzler  wrote:
> On 2018-12-09 Adrian Bunk  wrote:
> > Source: wmhdplop
> > Version: 0.9.10-1
> [...]
> 
> > devnames.c: In function 'device_id_from_name':
> > devnames.c:207:13: warning: implicit declaration of function 'major' 
> > [-Wimplicit-function-declaration]
> >*pmajor = major(stat_buf.st_rdev);
> >  ^
> [...]
> 
> Seems to miss a 
> #include 

Looks like that was indeed added in the upstream repo.
https://repo.or.cz/dockapps.git/commitdiff/7cf2e5406b9bc98054404c4c0145c2db0c0ef1e8

--
Juhani

Processed: upstream tickets

[Debian Bug Tracking System]

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

> forwarded 916007 https://github.com/IgnorantGuru/spacefm/issues/727
Bug #916007 [src:spacefm] spacefm FTBFS with glibc 2.28
Set Bug forwarded-to-address to 
'https://github.com/IgnorantGuru/spacefm/issues/727'.
> forwarded 915998 https://github.com/bwalex/tc-play/pull/72
Bug #915998 [src:tcplay] tcplay FTBFS with glibc 2.28
Set Bug forwarded-to-address to 'https://github.com/bwalex/tc-play/pull/72'.
>
End of message, stopping processing here.

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

Processed: found 916116 in 0.9.5-1

[Debian Bug Tracking System]

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

> found 916116 0.9.5-1
Bug #916116 [src:diceware] diceware hard-codes python3.6 for the build
Marked as found in versions diceware/0.9.5-1.
> thanks
Stopping processing here.

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

Bug#915344: openfoam FTBFS with glibc 2.28

[Juhani Numminen]

On Sun, 02 Dec 2018 23:37:05 +0200 Adrian Bunk  wrote:
> Source: openfoam
> Version: 4.1+dfsg1-2.2
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openfoam.html
> 
> ...
> fileStat.C: In member function 'bool Foam::fileStat::sameDevice(const 
> Foam::fileStat&) const':
> fileStat.C:78:13: error: 'major' was not declared in this scope
>  major(status_.st_dev) == major(stat2.status().st_dev)
>  ^
> fileStat.C:79:13: error: 'minor' was not declared in this scope
>   && minor(status_.st_dev) == minor(stat2.status().st_dev)

Hi,

This is most likely fixed by this commit
https://github.com/OpenFOAM/OpenFOAM-dev/commit/3fba921563fdb4436f73ace89fe9762474907953

The FTBFS is due to glibc changes,
https://lists.gnu.org/archive/html/info-gnu/2018-08/msg0.html:
"The macros 'major', 'minor', and 'makedev' are now only available from
the header "


Regards,
Juhani