Bug#914674: gnucash not building on armel anymore because of guile-2.2

[Laurent Bigonville]

Source: gnucash
Version: 1:3.3-2
Severity: serious

Hi,

The guile-2.* packages are not built on the armel architecture anymore
(see #883778) that means that gnucash cannot be built and this blocks
the transition to testing.

To fix this, gnucash should either drop the build-dependency against
guile-2.* (quickly looking at the build system this doesn't look
possible) or the binaries needs to be removed from that architecture.

Could you please have a look?

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-2-amd64 (SMP w/8 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

Processed: tagging 893077

[Debian Bug Tracking System]

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

> tags 893077 + stretch
Bug #893077 [src:gnucash] gnucash: FTBFS on Debian 9.4 (freshly installed) 
FAIL: test-report-utilities
Added tag(s) stretch.
> thanks
Stopping processing here.

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

Bug#912451: staden-io-lib FTBFS on !x86: test failures

[Andreas Tille]

Control: tags -1 forwarded James Bonfield 

Hi James,

version 1.14.11 of staden-io-lib creates an error in the test suite for non x86
architectures.  Here you have an easy overview what architectures are affected:

   https://buildd.debian.org/status/package.php?p=staden-io-lib&suite=sid

and this is basically the failure.  Do you have any idea how to fix this?

...
FAIL: scram
===

Loading ce.fa
Generating ce#sorted.sam
Generating ce#unsorted.sam
=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble  ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble  -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble  ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble  test.out/c1#bounds.full.cram > test.out/c1#bounds.full.sam
 ../progs/scramble  -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble  test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram.test (exit status: 1)

FAIL: scram_mt
==

=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble -t4 ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble -t4 -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble -t4 ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble -t4 test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.sam
 ../progs/scramble -t4 -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble -t4 test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram_mt.test (exit status: 1)


Testsuite summary for io_lib 1.14.11

# TOTAL: 9
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log

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



Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#914667: performous FTBFS on armel/mips/mipsel: undefined reference to `__atomic_load_8'

[Adrian Bunk]

Source: performous
Version: 1.1+git20181118-1
Severity: serious
Tags: ftbfs patch

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

...
/usr/bin/c++  -std=c++14 -Wall -Wextra -fcx-limited-range -g -O2 
-fdebug-prefix-map=/<>/performous-1.1+git20181118=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread  -Wl,-z,relro -Wl,--as-needed -pthread -rdynamic 
CMakeFiles/performous.dir/3dobject.cc.o CMakeFiles/performous.dir/audio.cc.o 
CMakeFiles/performous.dir/backgrounds.cc.o CMakeFiles/performous.dir/cache.cc.o 
CMakeFiles/performous.dir/color.cc.o 
CMakeFiles/performous.dir/configuration.cc.o 
CMakeFiles/performous.dir/controllers-joystick.cc.o 
CMakeFiles/performous.dir/controllers-keyboard.cc.o 
CMakeFiles/performous.dir/controllers-midi.cc.o 
CMakeFiles/performous.dir/controllers.cc.o 
CMakeFiles/performous.dir/dancegraph.cc.o 
CMakeFiles/performous.dir/database.cc.o CMakeFiles/performous.dir/dialog.cc.o 
CMakeFiles/performous.dir/engine.cc.o CMakeFiles/performous.dir/execname.cc.o 
CMakeFiles/performous.dir/ffmpeg.cc.o CMakeFiles/performous.dir/fs.cc.o 
CMakeFiles/performous.dir/game.cc.o CMakeFiles/performous.dir/glshader.cc.o 
CMakeFiles/performous.dir/glutil.cc.o 
CMakeFiles/performous.dir/guitargraph.cc.o 
CMakeFiles/performous.dir/hiscore.cc.o CMakeFiles/performous.dir/image.cc.o 
CMakeFiles/performous.dir/instrumentgraph.cc.o 
CMakeFiles/performous.dir/layout_singer.cc.o CMakeFiles/performous.dir/log.cc.o 
CMakeFiles/performous.dir/main.cc.o CMakeFiles/performous.dir/menu.cc.o 
CMakeFiles/performous.dir/midifile.cc.o 
CMakeFiles/performous.dir/musicalscale.cc.o 
CMakeFiles/performous.dir/notegraph.cc.o CMakeFiles/performous.dir/notes.cc.o 
CMakeFiles/performous.dir/opengl_text.cc.o CMakeFiles/performous.dir/pitch.cc.o 
CMakeFiles/performous.dir/platform.cc.o CMakeFiles/performous.dir/player.cc.o 
CMakeFiles/performous.dir/players.cc.o CMakeFiles/performous.dir/playlist.cc.o 
CMakeFiles/performous.dir/progressbar.cc.o 
CMakeFiles/performous.dir/requesthandler.cc.o 
CMakeFiles/performous.dir/screen_audiodevices.cc.o 
CMakeFiles/performous.dir/screen_intro.cc.o 
CMakeFiles/performous.dir/screen_paths.cc.o 
CMakeFiles/performous.dir/screen_players.cc.o 
CMakeFiles/performous.dir/screen_playlist.cc.o 
CMakeFiles/performous.dir/screen_practice.cc.o 
CMakeFiles/performous.dir/screen_sing.cc.o 
CMakeFiles/performous.dir/screen_songs.cc.o CMakeFiles/performous.dir/song.cc.o 
CMakeFiles/performous.dir/songitems.cc.o 
CMakeFiles/performous.dir/songparser-ini.cc.o 
CMakeFiles/performous.dir/songparser-mid.cc.o 
CMakeFiles/performous.dir/songparser-sm.cc.o 
CMakeFiles/performous.dir/songparser-txt.cc.o 
CMakeFiles/performous.dir/songparser-xml.cc.o 
CMakeFiles/performous.dir/songparser.cc.o CMakeFiles/performous.dir/songs.cc.o 
CMakeFiles/performous.dir/svg.cc.o CMakeFiles/performous.dir/texture.cc.o 
CMakeFiles/performous.dir/theme.cc.o CMakeFiles/performous.dir/unicode.cc.o 
CMakeFiles/performous.dir/util.cc.o CMakeFiles/performous.dir/video.cc.o 
CMakeFiles/performous.dir/video_driver.cc.o 
CMakeFiles/performous.dir/webcam.cc.o CMakeFiles/performous.dir/webserver.cc.o  
-o ../performous -lboost_program_options -lboost_filesystem -lboost_iostreams 
-lboost_system -lboost_locale -lboost_regex -licuuc -licudata -licui18n -licuio 
-lepoxy -Wl,-Bstatic -lSDL2main -Wl,-Bdynamic -lSDL2 -lpangocairo-1.0 
-lpango-1.0 -lcairo -lfreetype -lglib-2.0 -lgobject-2.0 -lrsvg-2 -lcairo 
-lfreetype -lgdk_pixbuf-2.0 -lxml++-2.6 -lxml2 -lglibmm-2.4 -lglib-2.0 
-lsigc-2.0 -lavformat -lavcodec -lavutil -lswresample -lavutil -lswscale 
-lavutil -lz -ljpeg -lpng -lz -lportaudio -lfontconfig -lportmidi 
-lboost_chrono -lboost_thread -lboost_system -lboost_date_time -lboost_atomic 
-lpthread -lcpprest -lcrypto -lssl ../lib/libced.a -lboost_locale -lboost_regex 
-licuuc -licudata -licui18n -licuio -lepoxy -Wl,-Bstatic -lSDL2main 
-Wl,-Bdynamic -lSDL2 -lpangocairo-1.0 -lpango-1.0 -lcairo -lfreetype -lglib-2.0 
-lgobject-2.0 -lrsvg-2 -lgdk_pixbuf-2.0 -lxml++-2.6 -lxml2 -lglibmm-2.4 
-lsigc-2.0 -lavformat -lavcodec -lavutil -lswresample -lswscale -lz -ljpeg 
-lpng -lportaudio -lfontconfig -lportmidi -lboost_chrono -lboost_thread 
-lboost_date_time -lboost_atomic -lpthread -lcpprest -lcrypto -lssl 
/usr/bin/ld: CMakeFiles/performous.dir/ffmpeg.cc.o: in function 
`FFmpeg::seek_internal()':
/usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:239: undefined reference to 
`__atomic_store_8'
/usr/bin/ld: CMakeFiles/performous.dir/ffmpeg.cc.o: in function 
`FFmpeg::seek(double, bool)':
/usr/include/c++/8/atomic:239: undefined reference to `__atomic_store_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/

Bug#912113: marked as done (harvest-tools: frequent parallel FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 26 Nov 2018 07:04:26 +
with message-id 
and subject line Bug#912113: fixed in harvest-tools 1.3-3
has caused the Debian Bug report #912113,
regarding harvest-tools: frequent parallel FTBFS
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.)


-- 
912113: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: harvest-tools
Version: 1.3-2
Severity: serious
Tags: ftbfs patch

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/harvest-tools.html

...
   dh_auto_build
make -j8
make[1]: Entering directory '/build/1st/harvest-tools-1.3'
cd src; /usr/bin/protoc --cpp_out . harvest/pb/harvest.proto
cd src/harvest/capnp;export 
PATH=/usr/bin/:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp compile -I 
/usr/include -oc++ harvest.capnp
cd src; /usr/bin/protoc --cpp_out . harvest/pb/harvest.proto
cd src/harvest/capnp;export 
PATH=/usr/bin/:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games;capnp compile -I 
/usr/include -oc++ harvest.capnp
[libprotobuf WARNING google/protobuf/compiler/parser.cc:562] No syntax 
specified for the proto file: harvest/pb/harvest.proto. Please use 'syntax = 
"proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to 
proto2 syntax.)
[libprotobuf WARNING google/protobuf/compiler/parser.cc:562] No syntax 
specified for the proto file: harvest/pb/harvest.proto. Please use 'syntax = 
"proto2";' or 'syntax = "proto3";' to specify a syntax version. (Defaulted to 
proto2 syntax.)
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/capnp/harvest.capnp.o src/harvest/capnp/harvest.capnp.c++
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/pb/harvest.pb.o src/harvest/pb/harvest.pb.cc
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/AnnotationList.o src/harvest/AnnotationList.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/harvest.o src/harvest/harvest.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/HarvestIO.o src/harvest/HarvestIO.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/LcbList.o src/harvest/LcbList.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/parse.o src/harvest/parse.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/PhylogenyTree.o src/harvest/PhylogenyTree.cpp
g++ -c -g -O2 -ffile-prefix-map=/build/1st/harvest-tools-1.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Isrc 
-I/usr/include -I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2 -o 
src/harvest/PhylogenyTreeNode.o src/harvest/PhylogenyTreeNode.cpp
src/harvest/capnp/harvest.capnp.c++:850:28: error: expected primary-expression 
at end of input
   8,   0,   0,   0,   0,   0,   0,   0,
^
src/harvest/capnp/harvest.capnp.c++:850:28: error: expected '}' at end of input
src/harvest/capnp/harvest.capnp.c++:719:3: note: to match this '{'
   {   0,   0,   0,   0,   5,   0,   6,   0,
   ^
src/harvest/capnp/harvest.capnp.c++:850:28: error: expected '}' at end of input
   8,   0,   0,   0,   0,   0,   0,   0,
^
src/harvest/capnp/harvest.capnp.c++:718:64: note: to match this '{'
 static const ::capnp::_::AlignedData<134> b_c4df8e4ba28721bc = {

Bug#912113: harvest-tools: diff for NMU version 1.3-2.1

[Andreas Tille]

Hi Adrian,

thanks for the patch.  I'm now back from VAC and uploaded including other
pending changes from Git.  In general feel free to choose way shorter term
NMUs since the Debian Med team has a low NMU threshold.

On Sun, Nov 25, 2018 at 06:50:55PM +0200, Adrian Bunk wrote:
> I've prepared an NMU for harvest-tools (versioned as 1.3-2.1) and 
> uploaded it to DELAYED/14. Please feel free to tell me if I should 
> cancel it.

Overridden by recent upload - thanks for all your QA work

 Andreas.

-- 
http://fam-tille.de

Bug#911898: marked as done (firefox-esr: SIGSEGV on startup on ppc64el)

[Debian Bug Tracking System]

Your message dated Mon, 26 Nov 2018 06:40:13 +
with message-id 
and subject line Bug#911898: fixed in firefox-esr 60.3.0esr-2
has caused the Debian Bug report #911898,
regarding firefox-esr: SIGSEGV on startup on ppc64el
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.)


-- 
911898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 60.3.0esr-1~deb9u1
Severity: important

This is essentially a downstream bug report of bz#1477176 (
https://bugzilla.mozilla.org/show_bug.cgi?id=1477176 ).

firefox-esr currently segfaults right on startup on ppc64le during the first
memory allocation call.


I cannot provide a useful backtrace because firefox-esr-dbgsym is not available
(not even in stretch-proposed-updates, you should upload the package there)
since security doesn't have a dbgsym archive (#894081).


A workaround for this issue is to build firefox with (moz)jemalloc disabled. I'd
suggest to do this for any non-x86-based architecture like RHEL does, because
(moz)jemalloc doesn't seem to be too stable on exotic architectures.

Appending

%if DEB_HOST_ARCH != amd64 && DEB_HOST_ARCH != i386
ac_add_options --disable-jemalloc
%endif

to debian/browser.mozconfig.in just about does the trick.



Mihai



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: firefox-esr
Source-Version: 60.3.0esr-2

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox-esr 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, 26 Nov 2018 10:42:42 +0900
Source: firefox-esr
Binary: firefox-esr firefox-esr-l10n-all firefox-esr-l10n-ach 
firefox-esr-l10n-af firefox-esr-l10n-an firefox-esr-l10n-ar firefox-esr-l10n-as 
firefox-esr-l10n-ast firefox-esr-l10n-az firefox-esr-l10n-be 
firefox-esr-l10n-bg firefox-esr-l10n-bn-bd firefox-esr-l10n-bn-in 
firefox-esr-l10n-br firefox-esr-l10n-bs firefox-esr-l10n-ca 
firefox-esr-l10n-cak firefox-esr-l10n-cs firefox-esr-l10n-cy 
firefox-esr-l10n-da firefox-esr-l10n-de firefox-esr-l10n-dsb 
firefox-esr-l10n-el firefox-esr-l10n-en-gb firefox-esr-l10n-en-za 
firefox-esr-l10n-eo firefox-esr-l10n-es-ar firefox-esr-l10n-es-cl 
firefox-esr-l10n-es-es firefox-esr-l10n-es-mx firefox-esr-l10n-et 
firefox-esr-l10n-eu firefox-esr-l10n-fa firefox-esr-l10n-ff firefox-esr-l10n-fi 
firefox-esr-l10n-fr firefox-esr-l10n-fy-nl firefox-esr-l10n-ga-ie 
firefox-esr-l10n-gd firefox-esr-l10n-gl firefox-esr-l10n-gn 
firefox-esr-l10n-gu-in firefox-esr-l10n-he firefox-esr-l10n-hi-in 
firefox-esr-l10n-hr firefox-esr-l10n-hsb firefox-esr-l10n-hu
 firefox-esr-l10n-hy-am firefox-esr-l10n-ia firefox-esr-l10n-id 
firefox-esr-l10n-is firefox-esr-l10n-it firefox-esr-l10n-ja firefox-esr-l10n-ka 
firefox-esr-l10n-kab firefox-esr-l10n-kk firefox-esr-l10n-km 
firefox-esr-l10n-kn firefox-esr-l10n-ko firefox-esr-l10n-lij 
firefox-esr-l10n-lt firefox-esr-l10n-lv firefox-esr-l10n-mai 
firefox-esr-l10n-mk firefox-esr-l10n-ml firefox-esr-l10n-mr firefox-esr-l10n-ms 
firefox-esr-l10n-my firefox-esr-l10n-nb-no firefox-esr-l10n-ne-np 
firefox-esr-l10n-nl firefox-esr-l10n-nn-no firefox-esr-l10n-oc 
firefox-esr-l10n-or firefox-esr-l10n-pa-in firefox-esr-l10n-pl 
firefox-esr-l10n-pt-br firefox-esr-l10n-pt-pt firefox-esr-l10n-rm 
firefox-esr-l10n-ro firefox-esr-l10n-ru firefox-esr-l10n-si firefox-esr-l10n-sk 
firefox-esr-l10n-sl firefox-esr-l10n-son firefox-esr-l10n-sq 
firefox-esr-l10n-sr firefox-esr-l10n-sv-se firefox-esr-l10n-ta 
firefox-esr-l10n-te firefox-esr-l10n-th firefox-esr-l10n-tr firefox-esr-l10n-uk 
firefox-esr-l10n-ur
 firefox-esr-l10n-uz firefox-esr-l10n-vi firefox-esr-l10n-xh 
firefox-esr-l10n-zh-cn
 firefox-esr-l10n-zh-tw
Architecture: source
Version: 60.3.0esr-2
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 firefox-esr - Mozilla Firefox web 

Processed: severity of 914320 is normal, severity of 911363 is normal, tagging 911363

[Debian Bug Tracking System]

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

> severity 914320 normal
Bug #914320 [ftp.debian.org] RM: moblin-menus -- ROM; dead upstream
Severity set to 'normal' from 'wishlist'
> severity 911363 normal
Bug #911363 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: patchelf [mips64el] -- ROM; ANAIS; Does not work
Severity set to 'normal' from 'serious'
> tags 911363 - ftbfs
Bug #911363 {Done: Debian FTP Masters } 
[ftp.debian.org] RM: patchelf [mips64el] -- ROM; ANAIS; Does not work
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#914663: gxtuner does not trap errors from make

[Helmut Grohne]

Source: gxtuner
Version: 3.0-1
Severity: serious
Justification: policy 4.6

gxtuner's upstream Makefile does not trap errors from the compiler. Most
compiler invocations carry a "-" prefix used for ignoring errors. That
prefix violates policy section 4.6. It also makes debugging build
failures unnecessarily hard and facilitates misbuilds.

Helmut

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

[TS]

Amy Kos schrieb/wrote:
> Could be graphics related, boot stops at:
> 
>  fb: switching to inteldrmfb from EFI VGA
> 
> Disabling kernel mode setting with parameter nomodeset boots to tty.
> 

confirming, adding 'nomodeset' to linux boot options lets
linux-image-4.18.0-3-amd64 boot. Thanks Amy for the hint.

HTH



kind regards,

 Thilo

Processed: Re: Bug#914646: piuparts: failed-testing with no prpblem listed

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 sslsplit 0.5.4-1
Bug #914646 [piuparts] piuparts: failed-testing with no prpblem listed
Bug reassigned from package 'piuparts' to 'sslsplit'.
No longer marked as found in versions piuparts/0.94.
Ignoring request to alter fixed versions of bug #914646 to the same values 
previously set
Bug #914646 [sslsplit] piuparts: failed-testing with no prpblem listed
Marked as found in versions sslsplit/0.5.4-1.
> retitle -1 sslsplit: ships /var/run/sslsplit
Bug #914646 [sslsplit] piuparts: failed-testing with no prpblem listed
Changed Bug title to 'sslsplit: ships /var/run/sslsplit' from 'piuparts: 
failed-testing with no prpblem listed'.
> severity -1 serious
Bug #914646 [sslsplit] sslsplit: ships /var/run/sslsplit
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#914657: Acknowledgement (stdout is flodded with debug messages)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 missing snmp.conf triggers flood of error messages
Bug #914657 [libsnmp30] stdout is flodded with debug messages
Changed Bug title to 'missing snmp.conf triggers flood of error messages' from 
'stdout is flodded with debug messages'.
> severity -1 serious
Bug #914657 [libsnmp30] missing snmp.conf triggers flood of error messages
Severity set to 'serious' from 'important'

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

Bug#914465: marked as done (missing dependencies on pkg-resources, procps)

[Debian Bug Tracking System]

Your message dated Mon, 26 Nov 2018 00:19:31 +
with message-id 
and subject line Bug#914465: fixed in px 1.0.12-2
has caused the Debian Bug report #914465,
regarding missing dependencies on pkg-resources, procps
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.)


-- 
914465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: px
Version: 1.0.12-1
Severity: important

Hi!

I have found that px does not properly depend on packages it requires
at runtime. It misses at least a hard Depends on python3-pkg-resources
and procps. In a clean sbuild sid chroot:

(unstable-amd64-sbuild)root@angela:~# px
Traceback (most recent call last):
  File "/usr/bin/px", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

Once python3-pkg-resources is installed by hand, I then get this:

(unstable-amd64-sbuild)root@angela:~# px
Traceback (most recent call last):
  File "/usr/bin/px", line 11, in 
load_entry_point('pxpx==0.0.0', 'console_scripts', 'px')()
  File "/usr/lib/python3/dist-packages/px/px.py", line 92, in main
procs = px_process.get_all()
  File "/usr/lib/python3/dist-packages/px/px_process.py", line 286, in get_all
ps_lines = call_ps()
  File "/usr/lib/python3/dist-packages/px/px_process.py", line 169, in call_ps
env=env)
  File "/usr/lib/python3.7/subprocess.py", line 769, in __init__
restore_signals, start_new_session)
  File "/usr/lib/python3.7/subprocess.py", line 1516, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'ps': 'ps'

Finally, running `px ` yields the following warning:

2018-11-23T16:37:16.688223: Now invoking lsof, this can take over a minute on a 
big system...
Can't list IPC / network sockets, make sure "lsof" is installed and in your 
$PATH

... which leads me to believe lsof could be in Recommends as well.

Great package, thanks for adding this to Debian! :)

-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages px depends on:
ii  python3   3.5.3-1
ii  python3-dateutil  2.5.3-2
ii  python3-docopt0.6.2-1

px recommends no packages.

px suggests no packages.
--- End Message ---
--- Begin Message ---
Source: px
Source-Version: 1.0.12-2

We believe that the bug you reported is fixed in the latest version of
px, 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.
Josue Ortega  (supplier of updated px 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: Sun, 25 Nov 2018 17:39:29 -0600
Source: px
Binary: px
Architecture: source all
Version: 1.0.12-2
Distribution: unstable
Urgency: medium
Maintainer: Josue Ortega 
Changed-By: Josue Ortega 
Description:
 px - ps and top for human beings
Closes: 914394 914465
Changes:
 px (1.0.12-2) unstable; urgency=medium
 .
   * debian/control:
 - Fix typo at package description (Closes: #914394)
 - Add python3-pkg-resources, lsof, procps as dependencies (Closes: #914465)
Checksums-Sha1:
 6bceb63f17639d0b475f9ea7fd26b77cca9fbdcb 1880 px_1.0.12-2.dsc
 821734a9fe2aef2ebc1b4c471de4ecb47bd79c76 2592 px_1.0.12-2.debian.tar.xz
 2aa642ca3d754d6efaa9be92f924ff81dab64377 29684 px_1.0.12-2_all.deb
 e7f15c6d9b8250bf57da20f0172125d6d2f816ee 6601 px_1.0.12-2_amd64.buildinfo
Checksums-Sha256:
 b3d39443a747e05534fd9726ebd0b83019974d5abf103b8d528971209bd3abf6 1880 
px_1.0.12-2.dsc
 64d24b2539bd10f4b3f0318341a59cb557992cc75228d92ffc2b7ad17ebe6abe 2592 
px_1.0.12-2.debian.tar.xz
 93ef0680394a3f11b4c9e0947f7d2f8a08a8149d643e47f45aaa813b4b700ef9 29684 
px_1.0.12-2_all.deb
 268330e246b84aa3e7f7351a1ef6287bdc4b9da29c707d8ae683cbdfc2a5eacd 6601 
px_1.0.1

Bug#912516: marked as done (libcommons-lang3-java FTBFS with easymock 4.0)

[Debian Bug Tracking System]

Your message dated Mon, 26 Nov 2018 00:05:09 +
with message-id 
and subject line Bug#912516: fixed in libcommons-lang3-java 3.8-2
has caused the Debian Bug report #912516,
regarding libcommons-lang3-java FTBFS with easymock 4.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
912516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcommons-lang3-java
Version: 3.8-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-lang3-java.html

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/libcommons-lang3-java-3.8/src/test/java/org/apache/commons/lang3/concurrent/BasicThreadFactoryTest.java:[120,55]
 incompatible types: java.lang.Object cannot be converted to 
java.util.concurrent.ThreadFactory
[ERROR] 
/build/1st/libcommons-lang3-java-3.8/src/test/java/org/apache/commons/lang3/event/EventListenerSupportTest.java:[144,60]
 incompatible types: java.lang.Object cannot be converted to 
java.beans.VetoableChangeListener
[INFO] 2 errors 
--- End Message ---
--- Begin Message ---
Source: libcommons-lang3-java
Source-Version: 3.8-2

We believe that the bug you reported is fixed in the latest version of
libcommons-lang3-java, 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.
Emmanuel Bourg  (supplier of updated libcommons-lang3-java 
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, 26 Nov 2018 00:50:10 +0100
Source: libcommons-lang3-java
Binary: libcommons-lang3-java libcommons-lang3-java-doc
Architecture: source
Version: 3.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libcommons-lang3-java - Apache Commons Lang utility classes
 libcommons-lang3-java-doc - Apache Commons Lang utility classes (documentation)
Closes: 912516
Changes:
 libcommons-lang3-java (3.8-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Easymock 4 (Closes: #912516)
Checksums-Sha1:
 4b8b0f26ee158c8f0dcd523bc50c29aa7aa6658f 2355 libcommons-lang3-java_3.8-2.dsc
 e7424b4637cb3937e3312b2740c85ab595b72c5a 5968 
libcommons-lang3-java_3.8-2.debian.tar.xz
 316288b0964dcdd437957ece70aa7ad3c40adf58 14542 
libcommons-lang3-java_3.8-2_source.buildinfo
Checksums-Sha256:
 79e03a05ded7b1f9e2a8663e032d69b902ce1e6c4becee1dd4422f8e6f25c9ac 2355 
libcommons-lang3-java_3.8-2.dsc
 11df75c75d2c8068e8a357b35b0c9da6371b0b3adfd6ccab69346286944f0f74 5968 
libcommons-lang3-java_3.8-2.debian.tar.xz
 45036b1268c44f042a77a71e4251659dfc25e0b9162f41511cca4146bc00ac20 14542 
libcommons-lang3-java_3.8-2_source.buildinfo
Files:
 52710a806467067e4dd86a9930abf296 2355 java optional 
libcommons-lang3-java_3.8-2.dsc
 5c60c00723c3c15f7f547869bde22d37 5968 java optional 
libcommons-lang3-java_3.8-2.debian.tar.xz
 67ad35dd5464967b8e9131f0c3cdc1cd 14542 java optional 
libcommons-lang3-java_3.8-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlv7NVESHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCshg4P/2OfLD8VRCmwZh/+5BfQkXGaOuS9D5HC
jhc/IaTkmdGPkB3E1oEz7MiQ6KQ5cRQaFSzKMHfxqqemjnfr2eC0Fk2dOrrmm+Sq
fPtqmrG6+b8s9I7O3idBKYAMpN8qtioH1XZiseqM01rIF3KYMrSflTdDyx5ngbku
KA3Pp1sIPCFcLpf2w8iJJJdt+fW67jQGRxODvEc3gOXR0WqkEScAuxu8+RfyE0OI
IQ+TcnFkF3v4hXcuX58t5mO25+rZqdzD41gKa0rPk50mj7iggixhaxEUgT01GbQZ
jOm0+O4gMJX23UOk4x1G+BWviMBxuO6DSTQjkRyr3Zvl+Tjdz9i7ua+W66cTI2Zd
98Th65m4C9VpdZLE26MavYXkURBmzXqecWIs0tDkPSswkfM+6oOaUVxm/1S7WM8t
rBB7GFX1C+OD4+LHbNnyqFL6FV5ztjjxAlzDhjyRLF/nyV85IOGec/1AI7zvu44Z
6UWhnHyj6xGi2509jOyVJ24hPUEFCv3dQqifI73ad9RBKD4SUFc9W54Xo9VtBfJr
Ny125erY6jCYuPuiKn7gfW7V0sATs66AriB0b60LUUnlkBFAsjBYHPLy4jpSQccK
R8aS0SZvsECcutwoMJ9TTncKFNXl56eE8Ou1mo9/GcRDNQXL1Km/wKURj98rH9Cd
pjHJM3k2SurB
=ZKu6
-END PGP SIGNATURE End Message ---

Processed: Bug #912516 in libcommons-lang3-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912516 [src:libcommons-lang3-java] libcommons-lang3-java FTBFS with 
easymock 4.0
Added tag(s) pending.

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

Bug#912516: Bug #912516 in libcommons-lang3-java marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

Bug #912516 in libcommons-lang3-java 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/java-team/libcommons-lang3-java/commit/a4ae5511deb7028b4d43da4e6520093005a49761


Fixed the build failure with Easymock 4 (Closes: #912516)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912516

Bug#913953: marked as done (qbittorrent crashes when starting talks of symbol lookup error)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 23:34:56 +
with message-id 
and subject line Bug#913953: fixed in qbittorrent 4.1.4-1
has caused the Debian Bug report #913953,
regarding qbittorrent crashes when starting talks of symbol lookup error
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.)


-- 
913953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qbittorrent
Version: 4.1.3-1
Severity: grave

Dear Maintainer,
Qbittorrent crashes and cites symbol lookup error for the crash.

$ qbittorrent
qbittorrent: symbol lookup error: qbittorrent: undefined symbol:
_ZN10libtorrent7session5startEiRKNS_13settings_packEPN5boost4asio10io_serviceE

I tried putting it through gdb but got the same error, no stacktrace.

$ gdb qbittorrent
GNU gdb (Debian 8.1-4+b1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from qbittorrent...Reading symbols from
/usr/lib/debug/.build-id/e1/d01f10049deb8021b73114692d536dd0ea8ff8.debug...done.
done.
(gdb) set pagination 0
(gdb) set logging on
Copying output to gdb.txt.
(gdb) run
Starting program: /usr/bin/qbittorrent
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x71078700 (LWP 3212)]
[New Thread 0x7fffebfff700 (LWP 3213)]
[New Thread 0x7fffeb7fe700 (LWP 3214)]
/usr/bin/qbittorrent: symbol lookup error: /usr/bin/qbittorrent:
undefined symbol:
_ZN10libtorrent7session5startEiRKNS_13settings_packEPN5boost4asio10io_serviceE
[Thread 0x7fffeb7fe700 (LWP 3214) exited]
[Thread 0x7fffebfff700 (LWP 3213) exited]
[Thread 0x71078700 (LWP 3212) exited]
[Inferior 1 (process 3208) exited with code 0177]
(gdb) bt
No stack.

This has happened after libboost-system1.67.0 entered testing.

Probably will be fixed when qbittorrent is rebuilt with
libboost-system1.67.0[1]

1 . https://release.debian.org/transitions/html/boost1.67.html


$ aptitude search libboost-system1.6
p   libboost-system1.62-dev   -
Operating system (e.g. diagnostics support) library
i A libboost-system1.62.0 -
Operating system (e.g. diagnostics support) library
p   libboost-system1.62.0-dbgsym  - debug
symbols for libboost-system1.62.0
p   libboost-system1.63-dev   -
Operating system (e.g. diagnostics support) library
p   libboost-system1.63.0 -
Operating system (e.g. diagnostics support) library
p   libboost-system1.63.0-dbgsym  - debug
symbols for libboost-system1.63.0
p   libboost-system1.67-dev   -
Operating system (e.g. diagnostics support) library
i A libboost-system1.67.0 -
Operating system (e.g. diagnostics support) library
i   libboost-system1.67.0-dbgsym  - debug
symbols for libboost-system1.67.0

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

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

Versions of packages qbittorrent depends on:
ii  geoip-database 20181108-1
ii  libboost-system1.62.0  1.62.0+dfsg-10
ii  libc6  2.27-8
ii  libgcc11:8.2.0-9
ii  libqt5core5a   5.11.2+dfsg-5+b1
ii  libqt5dbus55.11.2+dfsg-5+b1
ii  libqt5gui5 5.11.2+dfsg-5+b1
ii  libqt5network5 5.11.2+dfsg-5+b1
ii  libqt5widgets5 5.11.2+dfsg-5+b1
ii  libqt5xml5 5.11.2+dfsg-5+b1
ii 

Bug#914649: libvigraimpex: FTBFS against boost1.67: undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.4'

[Gilles Filippini]

Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-6
Severity: serious
Tags: patch ftbfs
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

libvigraimpex FTBFS against boost1.67 on armel [1]:

[ 19%] Linking CXX executable test_blockwisewatersheds
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/blockwisealgorithms
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/test_blockwisewatersheds.dir/link.txt --verbose=1
/usr/bin/c++  -W -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare 
-Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -rdynamic 
CMakeFiles/test_blockwisewatersheds.dir/test_watersheds.cxx.o 
CMakeFiles/test_blockwisewatersheds.dir/testsuccess.cxx.o  -o 
test_blockwisewatersheds -lboost_thread -lboost_system -lboost_date_time 
-lboost_chrono 
/usr/bin/ld: CMakeFiles/test_blockwisewatersheds.dir/test_watersheds.cxx.o: 
undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.4'
/usr/bin/ld: //lib/arm-linux-gnueabi/libpthread.so.0: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex&arch=armel&ver=1.10.0%2Bgit20160211.167be93%2Bdfsg-6%2Bb2&stamp=1542723257&raw=0

Not sure about the Good Way of solving this, but the attached patch is 
successful as a workaround (tested on armel and amd64).

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlv7H6QACgkQ7+hsbH/+
z4O6EQf/XBfegp9DOLxippoKKUv0XBuUI89BY3GwMbH5hYJBB1kCSaSE4t0gJxqs
dPel3rXn+O3uQVtNjzKNFYEfjU5cq2mT2vT5lSxPkUroA/XXhwZa+UTxYW76Mphr
J7FzfZAp+/d0tKW0Y1gzp1D6w5F7mNA9vw+SyhAUe0QTlNOEFZmAKsg73gc34pWe
x3n8sK8KWHlfo7HsFYmvq2CbIHbCZ/4FJ1k07GjRMCzTqQL5dT6itRbeXA/ly+Co
KYGx3NJYvioRRHkoGm/FKzrgWP7PhofKTgwMVZ6UQq4wTjjpjltUU72I52+Gfnb3
zjpEO/8tROT9uSJAFTEBVpsLT6Qzkg==
=Lpjx
-END PGP SIGNATURE-
diff -Nru libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog
--- libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog  
2018-08-11 06:20:04.0 +0200
+++ libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog  
2018-11-25 20:43:26.0 +0100
@@ -1,3 +1,10 @@
+libvigraimpex (1.10.0+git20160211.167be93+dfsg-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch link-with-pthread.patch to fix FTBFS against boost1.67 on armel
+
+ -- Gilles Filippini   Sun, 25 Nov 2018 20:43:26 +0100
+
 libvigraimpex (1.10.0+git20160211.167be93+dfsg-6) unstable; urgency=medium
 
   * add multi_convolution_fix_incomplete_template_paramater.patch
diff -Nru 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
--- 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
1970-01-01 01:00:00.0 +0100
+++ 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
2018-11-25 20:43:26.0 +0100
@@ -0,0 +1,13 @@
+Index: 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/config/VigraConfigureThreading.cmake
+===
+--- 
libvigraimpex-1.10.0+git20160211.167be93+dfsg.orig/config/VigraConfigureThreading.cmake
 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/config/VigraConfigureThreading.cmake
+@@ -9,7 +9,7 @@ macro(VIGRA_CONFIGURE_THREADING)
+ set(THREADING_FOUND 1)
+ if(THREADING_IMPLEMENTATION MATCHES "boost")
+ include_directories(${Boost_INCLUDE_DIR})
+-set(THREADING_LIBRARIES ${Boost_THREAD_LIBRARY} 
${Boost_SYSTEM_LIBRARY} ${Boost_DATE_TIME_LIBRARY} ${Boost_CHRONO_LIBRARY})
++set(THREADING_LIBRARIES ${Boost_THREAD_LIBRARY} 
${Boost_SYSTEM_LIBRARY} ${Boost_DATE_TIME_LIBRARY} ${Boost_CHRONO_LIBRARY} 
pthread)
+ elseif(THREADING_IMPLEMENTATION MATCHES "std")
+ # Great, we can use the std library.  Nothing to do here...
+ elseif(THREADING_IMPLEMENTATION MATCHES "none")
diff -Nru libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series
--- libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
2018-08-11 06:18:32.0 +0200
+++ libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
2018-11-25 20:43:26.00

Bug#912143: fixed upstream

[Daniel Pocock]

https://github.com/resiprocate/resiprocate/commit/9a3abc0118e40805dd93a9ab2e6852ea640a0f64


Need to add a macro (upstream) to support backport builds on Debian
systems running stretch / asio 1.10

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Stefan Fritsch]

How long is the timeout after which it is killed? What is the status of 
systemd-random-seed.service in that case? I don't see why it should take so 
long for the random number generator to initialize. But maybe apache2 needs to 
add a dependency.

Please provide the output of

journalctl -b UNIT=apache2.service + UNIT=systemd-random-seed.service + 
_TRANSPORT=kernel|grep -i -e apache -e random

when apache2 has failed to start.

Bug#899629: marked as done (openvanilla-modules: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 22:04:09 +
with message-id 
and subject line Bug#899629: fixed in openvanilla-modules 0.9.0a1.3+dfsg1-3
has caused the Debian Bug report #899629,
regarding openvanilla-modules: Invalid maintainer address 
pkg-ime-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.)


-- 
899629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openvanilla-modules
Version: 0.9.0a1.3+dfsg1-2.2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of openvanilla-modules,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package openvanilla-modules since the list address
pkg-ime-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-ime-de...@lists.alioth.debian.org is 68.

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: openvanilla-modules
Source-Version: 0.9.0a1.3+dfsg1-3

We believe that the bug you reported is fixed in the latest version of
openvanilla-modules, 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.
Boyuan Yang  (supplier of updated openvanilla-modules 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: Sun, 25 Nov 2018 16:48:35 -0500
Source: openvanilla-modules
Binary: openvanilla-imgeneric openvanilla-imgeneric-data-all 
openvanilla-imgeneric-data-ja openvanilla-imgeneric-data-ko 
openvanilla-imgeneric-data-th openvanilla-imgeneric-data-vi 
openvanilla-imgeneric-data-zh-cn openvanilla-imgeneric-data-zh-hk 
openvanilla-imgeneric-data-zh-tw
Architecture: source
Version: 0.9.0a1.3+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 openvanilla-imgeneric - libraries of openvanilla input method
 openvanilla-imgeneric-data-all - libraries of openvanilla input method - data 
files meta package
 openvanilla-imgeneric-data-ja - libraries of openvanilla input method - 
Japanese data files
 openvanilla-imgeneric-data-ko - libraries of openvanilla input method - Korean 
data files
 openvanilla-imgeneric-data-th - libraries of openvanilla input method - Thai 
data files
 openvanilla-imgeneric-data-vi - libraries of openvanilla input method - 
Vietnamese data files
 openvanilla-imgeneric-data-zh-cn - libraries of openvanilla input method - 
Chinese (Simplified) data
 openvanilla-im

Processed: piuparts: failed-testing with no prpblem listed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:sslsplit sslsplit
Bug #914646 [piuparts] piuparts: failed-testing with no prpblem listed
Added indication that 914646 affects src:sslsplit and sslsplit
> block 912052 by -1
Bug #912052 {Done: Hilko Bengen } [src:sslsplit] sslsplit: 
FTBFS: Failure in test -r session.pem
912052 was not blocked by any bugs.
912052 was not blocking any bugs.
Added blocking bug(s) of 912052: 914646

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

Bug#914585: marked as done (mathgl: qtwebengine5-dev is not available on all architectures)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 21:50:15 +
with message-id 
and subject line Bug#914585: fixed in mathgl 2.4.2.1-4
has caused the Debian Bug report #914585,
regarding mathgl: qtwebengine5-dev is not available on all 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.)


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

qtwebengine5-dev is only available on the following architectures:
  amd64 arm64 armhf i386 mipsel

mathgl tries qtwebengine5-dev first with a fallback to libqt5webkit5-dev,
which gives two possible solutions:

1. If using qtwebengine5-dev instead of libqt5webkit5-dev does
   not bring any significant improvements, it would be easiest
   to go back to using libqt5webkit5-dev on all architectures.

OR

2. Use qtwebengine5-dev where available and libqt5webkit5-dev
   everywhere else, by changing the build dependency to
 qtwebengine5-dev [amd64 arm64 armhf i386 mipsel]
--- End Message ---
--- Begin Message ---
Source: mathgl
Source-Version: 2.4.2.1-4

We believe that the bug you reported is fixed in the latest version of
mathgl, 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.
Dimitrios Eftaxiopoulos  (supplier of updated mathgl 
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: Sun, 25 Nov 2018 22:19:06 +0200
Source: mathgl
Binary: mathgl udav libmgl7.5.0 libmgl-mpi7.5.0 libmgl-wnd7.5.0 
libmgl-glut7.5.0 libmgl-qt5-7.5.0 libmgl-fltk7.5.0 libmgl-wx7.5.0 libmgl-data 
libmgl-dev python-mathgl python3-mathgl
Architecture: source all amd64
Version: 2.4.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Dimitrios Eftaxiopoulos 
Description:
 libmgl-data - library for scientific graphs (data files)
 libmgl-dev - library for scientific graphs (development files)
 libmgl-fltk7.5.0 - library for scientific graphs (fltk interface for windows)
 libmgl-glut7.5.0 - library for scientific graphs (glut interface for windows)
 libmgl-mpi7.5.0 - library for scientific graphs (mpi enhanced runtime library)
 libmgl-qt5-7.5.0 - library for scientific graphs (Qt interface for windows)
 libmgl-wnd7.5.0 - library for scientific graphs (windows runtime library)
 libmgl-wx7.5.0 - library for scientific graphs (wx interface for windows)
 libmgl7.5.0 - library for scientific graphs (main runtime library)
 mathgl - library for scientific graphs (utilities and examples)
 python-mathgl - library for scientific graphs (Python v.2 module)
 python3-mathgl - library for scientific graphs (Python v.3 module)
 udav   - library for scientific graphs (window interface)
Closes: 914585
Changes:
 mathgl (2.4.2.1-4) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Trim trailing whitespace. Fixed-Lintian-Tags:
 file-contains-trailing-whitespace
   * Use secure copyright file specification URI. Fixed-Lintian-Tags:
 insecure-copyright-format-uri
 .
   [ Dimitrios Eftaxiopoulos ]
   * Restrict qtwebengine5-dev B-D to the arches where it is available
 (Closes: #914585)
Checksums-Sha1:
 a408bbcfa599e46287de4050c10a277b64fd5f46 3228 mathgl_2.4.2.1-4.dsc
 939750462874192c5fd05e16e4af24533203aca9 13832 mathgl_2.4.2.1-4.debian.tar.xz
 a36833ba4e177cdcd18c551a93b50caf96134efa 7170784 libmgl-data_2.4.2.1-4_all.deb
 0a41adbde2682fc6be4185e20fdc8030e3122a59 1337964 libmgl-dev_2.4.2.1-4_amd64.deb
 56f89db3b550c15ad6ba51834ca00f38fcff0234 278172 
libmgl-fltk7.5.0-dbgsym_2.4.2.1-4_amd64.deb
 627851cd165a1a0a2774268a13d3bdc7c970be0e 73180 
libmgl-fltk7.5.0_2.4.2.1-4_amd64.deb
 c9f9ad07f4adc876842d391c287e92ab08234e73 83760 
libmgl-glut7.5.0-dbgsym_2.4.2.1-4_amd64.deb
 cad04f5965eef3af2802f22dcca9b2db9b4ebd89 27932 
libmgl-glut7.5.0_2.4.2.1-4_amd64.deb
 73587ff6cbb6c59b55d3ca320337f733c92082d9 114660 
libmgl-mpi7.5.0-dbgsym_2.4.2.1-4_amd64.deb
 cb0cc6fa93545cc99d41be50b324bafb28837aec 34468 
libmgl-mpi7.5.0_2.4.2.1-4_amd64.deb
 e327c1302f76dc06383148d6e202f94d953037c2 77665

Processed: tagging 914638

[Debian Bug Tracking System]

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

> tags 914638 + buster sid
Bug #914638 [src:ambdec] ambdec FTBFS: freetype-config not found
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: found 913775 in 7.3.0~rc4-1

[Debian Bug Tracking System]

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

> found 913775 7.3.0~rc4-1
Bug #913775 [php7.3-imap] php7.3-imap: CVE-2018-19518: imap_open() function 
command injection
Marked as found in versions php7.3/7.3.0~rc4-1.
> thanks
Stopping processing here.

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

Bug#909857: marked as done (pspp FTBFS on i386: test failure)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 21:19:33 +
with message-id 
and subject line Bug#909857: fixed in pspp 1.2.0-1
has caused the Debian Bug report #909857,
regarding pspp FTBFS on i386: test failure
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.)


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/pspp.html

...
## - ##
## Test results. ##
## - ##

ERROR: All 1163 tests were run,
1 failed unexpectedly.

##  ##
## Summary of the failures. ##
##  ##
Failed tests:
GNU PSPP 1.0.1 test suite test groups:

 NUM: FILE-NAME:LINE TEST-GROUP-NAME
  KEYWORDS

 343: sort-variables.at:19 SORT VARIABLES

## -- ##
## Detailed failed tests. ##
## -- ##

# -*- compilation -*-
343. sort-variables.at:19: testing SORT VARIABLES ...
./sort-variables.at:37: pspp -O format=csv sort-variables.sps
./sort-variables.at:37: pspp -O format=csv sort-variables.sps
./sort-variables.at:37: pspp -O format=csv sort-variables.sps
./sort-variables.at:37: pspp -O format=csv sort-variables.sps
--- -   2019-10-26 04:11:07.573599261 -1200
+++ /build/1st/pspp-1.0.1/tests/testsuite.dir/at-groups/343/stdout  
2019-10-26 04:11:07.568119454 -1200
@@ -1,10 +1,10 @@
 Variable
-b
 c
+b
 a
 
 Variable
 a
-c
 b
+c
 
343. sort-variables.at:19: 343. SORT VARIABLES (sort-variables.at:19): FAILED 
(sort-variables.at:37)
...
--- End Message ---
--- Begin Message ---
Source: pspp
Source-Version: 1.2.0-1

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

Debian distribution maintenance software
pp.
Friedrich Beckmann  (supplier of updated pspp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 6 Nov 2018 08:50:21 +0200
Source: pspp
Binary: pspp
Architecture: source i386
Version: 1.2.0-1
Distribution: unstable
Urgency: low
Maintainer: Friedrich Beckmann 
Changed-By: Friedrich Beckmann 
Description:
 pspp   - Statistical analysis tool
Closes: 909857
Changes:
 pspp (1.2.0-1) unstable; urgency=low
 .
   * New upstream release 1.2.0
   * New experimental command SAVE DATA COLLECTION to save MDD files.
   * MTIME and YMDHMS variable formats now supported.
   * Build changes:
 - zlib is now a required dependency.  (Previously it was optional.)
 - Gtk+3.18.0 or later must now be used when building.
 - The code implementing the sheet rendering has been removed.  Instead we
   use a third party library: spread-sheet-widget.
   * The "NOMISSING" keyword when generating syntax for piecharts in the
 frequencies command was omitted.  This has been corrected.
   * Regresssion fixed.
 Closes: #909857
Checksums-Sha1:
 0a0cf3adcbc44a75afec73df96eee45cf318ba22 2417 pspp_1.2.0-1.dsc
 963f6f5a5459a35c53989b2666b5cc1450fd1750 7213194 pspp_1.2.0.orig.tar.gz
 cf2ff73011c3901e66f4027d4027de6733995858 833 pspp_1.2.0.orig.tar.gz.asc
 3bb0716677d98d063fb2966b165354a46a6e7a8c 26220 pspp_1.2.0-1.debian.tar.xz
 d66e6d964f08b5d4bd110586d734853a5d9666c0 3328064 pspp-dbgsym_1.2.0-1_i386.deb
 1ef4d74c39818a2317d62f639c3f3882a47d85cc 17841 pspp_1.2.0-1_i386.buildinfo
 d666d56d5a1c733007d6cd54cf3165c8b15a67fc 3918204 pspp_1.2.0-1_i386.deb
Checksums-Sha256:
 5333c51525820d30ab75c180b653eb006a9a8e2345f24369f54f43716e158d29 2417 
pspp_1.2.0-1.dsc
 a50e437974cff8d57f41ba87026509c9c383474e52717944ea6565e6ff11f71e 7213194 
pspp_1.2.0.orig.tar.gz
 e9133ea42bb27ab44f5f44e5a531d4f4b51895a1f76da3c4b0d4bed46934e796 833 
pspp_1.2.0.orig.tar.gz.asc
 3eef4c45dafb0a382bd9aedf6967bbafd778f7bbb7eec5d63f18373d1611d62a 26220 
pspp_1.2.0-1.debian.tar.xz
 1c3b03c57bfb4010a947a11c097c088e3caafe2f3c5d778b29131e144e4c9e10 3328064 
pspp-dbgsym_1.2.0-1_i386.deb
 bc694fcd00c3a845d52ad2b89364c47009468caa9a8813de19ebc6e284a47cbe 17841 
pspp_1.2.0-1_i386.buildinf

Bug#914645: zita-at1 FTBFS: freetype-config not found

[Helmut Grohne]

Source: zita-at1
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

zita-at1 fails to build from source, because freetype-config cannot be
found. freetype-config was removed from Debian and one is supposed to
use pkg-config now.

Helmut

Bug#911985: libvoikko FTBFS with hfst-ospell 0.5.0

[John Paul Adrian Glaubitz]

Package: src:libvoikko
Followup-For: Bug #911985

Hi!

I just uploaded an updated version (4.2) of libvoikko to
DELAYED/7 which fixes this bug.

Please let me know whether this acceptable or not. If not, I
will remove the upload from the queue again, of course.

I have taken action in this case because this particular package
keeps back a lot of KDE packages in the Debian Ports architectures
like riscv64.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#914640: supercollider FTBFS on amd64/i386 with boost 1.67

[Adrian Bunk]

Source: supercollider
Version: 1:3.8.0~repack-2
Severity: serious
Tags: ftbfs

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

...
In file included from 
/<>/server/supernova/sc/../server/synth.hpp:29,
 from /<>/server/supernova/sc/sc_synth.hpp:31,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/<>/server/supernova/./utilities/time_tag.hpp: In member function 
'boost::posix_time::ptime nova::time_tag::to_ptime() const':
/<>/server/supernova/./utilities/time_tag.hpp:233:102: error: no 
matching function for call to 
'boost::date_time::subsecond_duration::subsecond_duration(double)'
 time_duration offset = seconds(get_secs() - ntp_offset) + 
microseconds(get_nanoseconds()/1000);

  ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:12,
 from /usr/include/boost/thread/thread_time.hpp:11,
 from /usr/include/boost/thread/lock_types.hpp:18,
 from /usr/include/boost/thread/pthread/mutex.hpp:16,
 from /usr/include/boost/thread/mutex.hpp:16,
 from /usr/include/boost/thread/pthread/shared_mutex.hpp:14,
 from /usr/include/boost/thread/shared_mutex.hpp:28,
 from 
/<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:27,
 from 
/<>/server/supernova/./utilities/named_hash_entry.hpp:27,
 from /<>/server/supernova/sc/sc_synthdef.hpp:30,
 from 
/<>/server/supernova/sc/sc_synth_definition.hpp:24,
 from /<>/server/supernova/sc/sc_synth.hpp:29,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/usr/include/boost/date_time/time_duration.hpp:285:14: note: candidate: 
'template boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if, void>::type*)'
 explicit subsecond_duration(T const& ss,
  ^~
/usr/include/boost/date_time/time_duration.hpp:285:14: note:   template 
argument deduction/substitution failed:
/usr/include/boost/date_time/time_duration.hpp: In substitution of 
'template 
boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if, void>::type*) [with T = double]':
/<>/server/supernova/./utilities/time_tag.hpp:233:102:   required 
from here
/usr/include/boost/date_time/time_duration.hpp:285:14: error: no type named 
'type' in 'struct boost::enable_if, void>'
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:12,
 from /usr/include/boost/thread/thread_time.hpp:11,
 from /usr/include/boost/thread/lock_types.hpp:18,
 from /usr/include/boost/thread/pthread/mutex.hpp:16,
 from /usr/include/boost/thread/mutex.hpp:16,
 from /usr/include/boost/thread/pthread/shared_mutex.hpp:14,
 from /usr/include/boost/thread/shared_mutex.hpp:28,
 from 
/<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:27,
 from 
/<>/server/supernova/./utilities/named_hash_entry.hpp:27,
 from /<>/server/supernova/sc/sc_synthdef.hpp:30,
 from 
/<>/server/supernova/sc/sc_synth_definition.hpp:24,
 from /<>/server/supernova/sc/sc_synth.hpp:29,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(const 
boost::date_time::subsecond_duration&)'
   class BOOST_SYMBOL_VISIBLE subsecond_duration : public base_duration
  ^~
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 'const 
boost::date_time::subsecond_duration&'
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(boost::date_time::subsecond_duration&&)'
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 
'boost::date_time::subsecond_duration&&'
make[3]: *** [server/supernova/CMakeFiles/libsupernova.dir/build.make:66: 
server/supernova/CMakeFiles/libsupernova.dir/sc/sc_synth_definition.cpp.o] 
Error 1

Bug#914639: gpsshogi FTBFS with boost 1.67

[Adrian Bunk]

Source: gpsshogi
Version: 0.7.0-2
Severity: serious
Tags: ftbfs

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

...
/usr/bin/ld: gpsusi.o: in function `makePlayer(osl::Player, osl::SimpleState 
const&, std::ostream&)':
./bin/gpsusi.cc:1412: undefined reference to 
`osl::search::UsiMonitor::setUdpLogging(std::__cxx11::basic_string, std::allocator >&, 
boost::asio::basic_datagram_socket*, 
boost::asio::ip::basic_endpoint*)'
collect2: error: ld returned 1 exit status
make[1]: *** [: gpsusi] Error 1

Bug#914638: ambdec FTBFS: freetype-config not found

[Helmut Grohne]

Source: ambdec
Version: 0.5.1-5
Severity: serious
Tags: ftbfs

ambdec fails to build from source, because it uses freetype-config,
which got removed from Debian. Please use pkg-config instead.

Helmut

Bug#914636: stringencoder FTFBS: CC_FOR_BUILD turns out to be empty

[Helmut Grohne]

Source: stringencoders
Version: 3.10.3+git20180306-1
Severity: serious
Tags: ftbfs

stringencoders fails to build from source on the buildds (e.g.
https://buildd.debian.org/status/fetch.php?pkg=stringencoders&arch=arm64&ver=3.10.3%2Bgit20180306-1&stamp=1542718062&raw=0).
It seems that the variable CC_FOR_BUILD turns out to be empty. I guess
that the AC_ARG_VAR overrides the previous value and thus makes the
native build fail.

Helmut

Bug#914635: woo FTBFS with boost 1.67

[Adrian Bunk]

Source: woo
Version: 1.0+dfsg1-3
Severity: serious
Tags: ftbfs

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

...
In file included from build-src-tree/woo/lib/base/openmp-accu.hpp:5,
 from build-src-tree/woo/core/EnergyTracker.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:1,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
build-src-tree/woo/lib/base/Math.hpp:71:37: error: expected identifier before 
'!' token
  #define likely(x) __builtin_expect(!!(x),1)
 ^
build-src-tree/woo/lib/base/Math.hpp:71:37: error: expected ',' or '...' before 
'!' token
In file included from /usr/include/boost/date_time/format_date_parser.hpp:17,
 from /usr/include/boost/date_time/date_generator_parser.hpp:20,
 from /usr/include/boost/date_time/date_facet.hpp:25,
 from 
/usr/include/boost/date_time/gregorian/gregorian_io.hpp:16,
 from /usr/include/boost/date_time/gregorian/gregorian.hpp:31,
 from 
/usr/include/boost/date_time/posix_time/time_formatters.hpp:12,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:24,
 from build-src-tree/woo/core/Master.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:2,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
/usr/include/boost/date_time/special_values_parser.hpp: In static member 
function 'static bool boost::date_time::special_values_parser::__builtin_expect(int)':
/usr/include/boost/date_time/special_values_parser.hpp:107:18: error: 
overloaded function with no contextual type information
 if (!str.empty()) {
  ^
/usr/include/boost/date_time/special_values_parser.hpp:108:26: error: invalid 
types '[int]' for array subscript
 switch (str[0]) {
  ^
In file included from build-src-tree/woo/lib/base/openmp-accu.hpp:5,
 from build-src-tree/woo/core/EnergyTracker.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:1,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
/usr/include/boost/date_time/time_parsing.hpp: In function 'time_type 
boost::date_time::parse_iso_time(const string&, char)':
build-src-tree/woo/lib/base/Math.hpp:71:38: error: no match for 'operator!' 
(operand type is 'const string' {aka 'const std::__cxx11::basic_string'})
  #define likely(x) __builtin_expect(!!(x),1)
  ^~~~
build-src-tree/woo/lib/base/Math.hpp:71:38: note: candidate: 'operator!(bool)' 

build-src-tree/woo/lib/base/Math.hpp:71:38: note:   no known conversion for 
argument 1 from 'const string' {aka 'const std::__cxx11::basic_string'} 
to 'bool'
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25


The Ubuntu diff seems to contain a fix.

Bug#914419: debhelper mustn't set pass V to make

[Adrian Bunk]

On Sun, Nov 25, 2018 at 07:21:17PM +, Luca Boccassi wrote:
>...
> In general, I realise that not every makefile might implement
> VERBOSE/V, but I think it's the most common pattern, so I think it's
> the best chance we have to support it automagically via debhelper. If
> some package uses a different set of variables for verbosity (or none
> at all), then they'll have to use overrides, but they'd be no worse
> than now - of course unless there are more breakages, in which case we
> can revert/use a compat level. Does this sound like a plan?
>...

The problem is not about finding the correct variable for verbosity.

The problem is that Makefiles are allowed to use variables like V or 
VERBOSE for whatever purpose they want, and with whatever values they 
want.

It is not even clear that all breakages are FTBFS,
we might end up with misbuilt packages due to that.

> Kind regards,
> Luca Boccassi

cu
Adrian

-- 

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

Bug#914419: debhelper mustn't set pass V to make

[Luca Boccassi]

On Sun, 2018-11-25 at 14:12 +0200, Adrian Bunk wrote:
> On Sun, Nov 25, 2018 at 11:58:57AM +, Luca Boccassi wrote:
> > On Sun, 25 Nov 2018, 11:30 Niels Thykier  > 
> > > Adrian Bunk:
> > > > Package: debhelper
> > > > Version: 11.5.2
> > > > Severity: serious
> > > > 
> > > > 
> > > 
> > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd6
> > > 4/apcupsd.html
> > > > 
> > > > ...
> > > > dh clean --with autoreconf
> > > >    dh_auto_clean
> > > >   make V=1 -j16 clean
> > > > make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
> > > > 1find . -depth \
> > > >   \( -name  -o -name  -o -name \*.a \) \
> > > >   -exec  "  CLEAN" \{\} \; -exec  \{\} \;
> > > > /bin/sh: 1: 1find: not found
> > > > make[1]: *** [autoconf/targets.mak:98: clean] Error 127
> > > > 
> > > > 
> > > > 
> > > 
> > > https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets
> > > .mak/#L98
> > > > 
> > > > 
> > > > Using V=1 for getting verbose build output is a relatively
> > > > recent convention followed by some software.
> > > > 
> > > > It is not something that is safe to use everywhere.
> > > > 
> > > 
> > > Hi,
> > > 
> > > Adding Luca to this report as it affect a change by Luca.
> > > 
> > > @Luca: What is your take on this?  Should we roll back on this,
> > > guard it
> > > by a compat level or something else?
> > > 
> > > Thanks,
> > > ~Niels
> > > 
> > 
> > Hi Niels and Adrian,
> 
> Hi Luca,
> 
> > Before considering other options, would using VERBOSE=1 instead of
> > V=1
> > work? I'm afk until later today so I can't check right now if gmake
> > accepts
> > it, iirc it does but I could be confusing it with other tools.
> 
> make happily accepts them, but this misses the problem.
> 
> None of these options is supported directly by make.
> 
> make just passes such options to the package-specific
> Makefile that might do something or nothing with them.

Sorry, was on the phone and didn't properly read the snippet nor the
link, thought it was make itself complaining (for some reasons - it
didn't make much sense actually).

Still, looking at that makefile, it would seem that using VERBOSE would
do the right thing:

https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets.mak/#L20

It would seem less likely, intuitively, that VERBOSE would be used in 
a similar way that would break the build if set to 1/0, so perhaps it's
still the right fix? It does work with apcupsd for example, just tested
it. iproute2, which is the package I added this for originally, works
just fine likewise.

In general, I realise that not every makefile might implement
VERBOSE/V, but I think it's the most common pattern, so I think it's
the best chance we have to support it automagically via debhelper. If
some package uses a different set of variables for verbosity (or none
at all), then they'll have to use overrides, but they'd be no worse
than now - of course unless there are more breakages, in which case we
can revert/use a compat level. Does this sound like a plan?

If so, here's the MR:

https://salsa.debian.org/debian/debhelper/merge_requests/16

-- 
Kind regards,
Luca Boccassi

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

Bug#914537: openmw: segfault at start

[bret curtis]

Thanks Fred!

We're tracking it upstream. Will keep this bug posted with results.

https://gitlab.com/OpenMW/openmw/issues/4737

Cheers,
Bret

Bug#912181: marked as done (python-jedi FTBFS: error: [Errno 36] File name too long)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 19:05:19 +
with message-id 
and subject line Bug#912181: fixed in python-jedi 0.12.0-1.1
has caused the Debian Bug report #912181,
regarding python-jedi FTBFS: error: [Errno 36] File name too long
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.)


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

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

...
Copying jedi.egg-info to 
/build/1st/python-jedi-0.12.0/debian/tmp/usr/lib/python3.7/dist-packages/jedi-_Jedi.is.a.static.analysis.tool.for.Python.that.can.be.used.in.IDEs_editors..Its_historic.focus.is.autocompletion_.but.does.static.analysis.for.now.as.well._Jedi.is.fast.and.is.very.well.tested..It.understands.Python.on.a.deeper.level_than.all.other.static.analysis.frameworks.for.Python._Jedi.has.support.for.two.different.goto.functions..It_s.possible.to.search.for_related.names.and.to.list.all.names.in.a.Python.file.and.infer.them..Jedi_understands.docstrings.and.you.can.use.Jedi.autocompletion.in.your.REPL.as_well._Jedi.uses.a.very.simple.API.to.connect.with.IDE_s..There_s.a.reference_implementation.as.a._VIM_Plugin._https_github.com_davidhalter_jedi_vim_which.uses.Jedi_s.autocompletion...We.encourage.you.to.use.Jedi.in.your.IDEs._It_s.really.easy._To.give.you.a.simple.example.how.you.can.use.the.Jedi.library_.here.is.an_example.for.the.autocompletion.feature_.import.jedi_.source._._import.datetime_datetime.da_.script._.jedi.Script_source_.3_.len_datetime.da_._example.py_.script_Script_._example.py_.completions._.script.completions_.completions._doctest_._ELLIPSIS_Completion_.date_._Completion_.datetime__.print_completions_0_.complete_te_.print_completions_0_.name_date_As.you.see.Jedi.is.pretty.simple.and.allows.you.to.concentrate.on.writing.a_good.text.editor_.while.still.having.very.good.IDE.features.for.Python._.egg-info
Skipping SOURCES.txt
error: [Errno 36] File name too long: 
'/build/1st/python-jedi-0.12.0/debian/tmp/usr/lib/python3.7/dist-packages/jedi-_Jedi.is.a.static.analysis.tool.for.Python.that.can.be.used.in.IDEs_editors..Its_historic.focus.is.autocompletion_.but.does.static.analysis.for.now.as.well._Jedi.is.fast.and.is.very.well.tested..It.understands.Python.on.a.deeper.level_than.all.other.static.analysis.frameworks.for.Python._Jedi.has.support.for.two.different.goto.functions..It_s.possible.to.search.for_related.names.and.to.list.all.names.in.a.Python.file.and.infer.them..Jedi_understands.docstrings.and.you.can.use.Jedi.autocompletion.in.your.REPL.as_well._Jedi.uses.a.very.simple.API.to.connect.with.IDE_s..There_s.a.reference_implementation.as.a._VIM_Plugin._https_github.com_davidhalter_jedi_vim_which.uses.Jedi_s.autocompletion...We.encourage.you.to.use.Jedi.in.your.IDEs._It_s.really.easy._To.give.you.a.simple.example.how.you.can.use.the.Jedi.library_.here.is.an_example.for.the.autocompletion.feature_.import.jedi_.source._._import.datetime_datetime.da_.script._.jedi.Script_source_.3_.len_datetime.da_._example.py_.script_Script_._example.py_.completions._.script.completions_.completions._doctest_._ELLIPSIS_Completion_.date_._Completion_.datetime__.print_completions_0_.complete_te_.print_completions_0_.name_date_As.you.see.Jedi.is.pretty.simple.and.allows.you.to.concentrate.on.writing.a_good.text.editor_.while.still.having.very.good.IDE.features.for.Python._.egg-info'
E: pybuild pybuild:338: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3.7 setup.py install --root 
/build/1st/python-jedi-0.12.0/debian/tmp 
dh_auto_install: pybuild --install --test-pytest -i python{version} -p "3.7 
3.6" --dest-dir /build/1st/python-jedi-0.12.0/debian/tmp returned exit code 13
make: *** [debian/rules:6: binary] Error 25
--- End Message ---
--- Begin Message ---
Source: python-jedi
Source-Version: 0.12.0-1.1

We believe that the bug you reported is fixed in the latest version of
python-jedi, 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 mainte

Bug#909558: marked as done (libapache2-mod-shib2: Installation fails because of unmet dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 18:49:48 +
with message-id 
and subject line Bug#909558: fixed in shibboleth-sp 3.0.2+dfsg1-2
has caused the Debian Bug report #909558,
regarding libapache2-mod-shib2: Installation fails because of unmet dependencies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
909558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libapache2-mod-shib2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

the installation of this package fails with the following message:

8<8<
# apt install libapache2-mod-shib2 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libapache2-mod-shib2 : Depends: libshibsp-plugins (= 2.6.1+dfsg1-2) but it is 
not going to be installed
Depends: shibboleth-sp2-utils (>= 2.6) but it is not 
going to be installed
Depends: libshibsp7 but it is not going to be installed
Depends: libxmltooling7 (>= 1.6.0-5) but it is not 
going to be installed
E: Unable to correct problems, you have held broken packages.
8<8<

Unlike stated in the error message there are no "held broken packages" on this 
system.

With best regards,

Michail Bachmann


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

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

Versions of packages libapache2-mod-shib2 depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.34-1
ii  libc6   2.27-6
ii  libgcc1 1:8.2.0-7
ii  libgssapi-krb5-21.16-2
pn  libshibsp-plugins   
pn  libshibsp7  
ii  libstdc++6  8.2.0-7
ii  libxerces-c3.2  3.2.2+debian-1
pn  libxmltooling7  
pn  shibboleth-sp2-utils

libapache2-mod-shib2 recommends no packages.

libapache2-mod-shib2 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: shibboleth-sp
Source-Version: 3.0.2+dfsg1-2

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated shibboleth-sp 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: Sun, 25 Nov 2018 18:27:46 +0100
Source: shibboleth-sp
Binary: libapache2-mod-shib libshibsp8 libshibsp-plugins libshibsp-dev 
libshibsp-doc shibboleth-sp-common shibboleth-sp-utils libapache2-mod-shib2 
shibboleth-sp2-common shibboleth-sp2-utils
Architecture: source
Version: 3.0.2+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Shib Team 
Changed-By: Ferenc Wágner 
Description:
 libapache2-mod-shib - Federated web single sign-on system (Apache module)
 libapache2-mod-shib2 - transitional package
 libshibsp-dev - Federated web single sign-on system (development)
 libshibsp-doc - Federated web single sign-on system (API docs)
 libshibsp-plugins - Federated web single sign-on system (plugins)
 libshibsp8 - Federated web single sign-on system (runtime)
 shibboleth-sp-common - Federated web single sign-on system (common files)
 shibboleth-sp-utils - Federated web single sign-on system (daemon and 
utilities)
 shibboleth-sp2-common - transitional package
 shibboleth-sp2-utils - transitional 

Bug#914618: godot: Let dpkg-shlibdeps generate the library dependencies

[Jeremy Bicha]

Patch attached.

Federico, see also https://bugs.debian.org/914617 and
https://bugs.debian.org/914618 since I didn't specifically CC you on
those bugs.

Thanks,
Jeremy Bicha
From df724dc73ce1550e24f00ff42457676168d50be8 Mon Sep 17 00:00:00 2001
From: Jeremy Bicha 
Date: Sun, 25 Nov 2018 11:54:52 -0500
Subject: [PATCH] Let dpkg-shlibdeps generate the library dependencies

Closes: #914618
---
 debian/control | 51 --
 1 file changed, 51 deletions(-)

diff --git a/debian/control b/debian/control
index cadabfe..fcaaa48 100644
--- a/debian/control
+++ b/debian/control
@@ -41,23 +41,6 @@ Package: godot3
 Architecture: amd64 arm64 armel armhf i386
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libasound2,
- libfreetype6,
- libgcc1,
- libgl1-mesa-glx,
- libopus0,
- libopusfile0,
- libpng16-16,
- libpulse0,
- libtheora0,
- libvorbis0a,
- libvpx4,
- libwebp6,
- libx11-6,
- libxcursor1,
- libxinerama1,
- libxrandr2,
- zlib1g
 Description: Full 2D and 3D game engine with editor
  Godot is an advanced, feature packed, multi-platform 2D and 3D game engine.
  It provides a huge set of common tools, so you can just focus on making
@@ -67,23 +50,6 @@ Package: godot3-runner
 Architecture: amd64 arm64 armel armhf i386
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libasound2,
- libfreetype6,
- libgcc1,
- libgl1-mesa-glx,
- libopus0,
- libopusfile0,
- libpng16-16,
- libpulse0,
- libtheora0,
- libvorbis0a,
- libvpx4,
- libwebp6,
- libx11-6,
- libxcursor1,
- libxinerama1,
- libxrandr2,
- zlib1g
 Description: Godot game engine run-time
  Godot is an advanced, feature packed, multi-platform 2D and 3D game engine.
  This package allows games to be run from source or data-pack.
@@ -92,23 +58,6 @@ Package: godot3-server
 Architecture: amd64 arm64 armel armhf i386
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libasound2,
- libfreetype6,
- libgcc1,
- libgl1-mesa-glx,
- libopus0,
- libopusfile0,
- libpng16-16,
- libpulse0,
- libtheora0,
- libvorbis0a,
- libvpx4,
- libwebp6,
- libx11-6,
- libxcursor1,
- libxinerama1,
- libxrandr2,
- zlib1g
 Description: Headless Godot game engine run-time
  Godot is an advanced, feature packed, multi-platform 2D and 3D game engine.
  This package provides a command-line only version of the program.
-- 
2.19.1

Bug#914618: godot: Let dpkg-shlibdeps generate the library dependencies

[Jeremy Bicha]

Source: godot
Version: 3.0.6-1
Severity: serious
Tags: patch

The binary packages generated by godot have a hard-coded list of
library dependencies.

This is a violation of Debian Policy § 8.6.1

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#generating-dependencies-on-shared-libraries

The dpkg-shlibdep system automatically generates the dependencies
which allows for smooth library transitions. For instance, godot will
not migrate to Testing now because it depends on libvpx4 but Testing
has now switched to libvpx5.

I will attach a patch to fix this in my follow-up email.

Thanks,
Jeremy Bicha

Bug#879034: pdfshuffler: port to gir1.2-poppler-0.18

[Jerome Robert]

On 25/11/2018 18:58, Jonas Smedegaard wrote:
> Seems upstream don't expect a new stable release soon, and explicilty 
> recommends distributions to rather drop the package: 
> https://github.com/jeromerobert/pdfarranger/issues/9#issuecomment-427656602

I forked pdfshuffler to pdfarranger and will release a 
gir1.2-poppler-0.18+python3 version soon (next week).

Regards,

Jerome



signature.asc
Description: OpenPGP digital signature

Bug#914616: [ring-daemon] Crashes because of segmentation fault

[Bruno Kleinert]

Package: ring-daemon
Version: 20181001.4.a99aaec~ds6-2
Severity: grave

--- Please enter the report below this line. ---
Hi,

dring dies with a segmentation fault when gnome-ring is starting up. I
attached a backtrace. To capture the backtrace, I started
/usr/lib/ring/dring before starting gnome-ring.

The crash causes gnome-ring to not load a users's profile as expected,
but presents a setup dialog to create a new profile instead.

Rebuilding ring without any modifications works as a temporary
workaround. When I installed the rebuilt packages, the dependency
libyaml-cpp0.5v5 got replaced by libyaml-cpp0.5d1.

Cheers - Bruno

--- System information. ---
Architecture: 
Kernel:   Linux 4.18.0-2-amd64

Debian Release: buster/sid
  500 unstable-debug  deb.debian.org 
  500 unstabledeb.debian.org 
1 experimental-debug deb.debian.org 
1 experimentaldeb.debian.org 

--- Package information. ---
Depends(Version) | Installed
-+-===
libargon2-1  (>= 0~20171227) | 0~20171227-0.1
libasound2   (>= 1.0.16) | 1.1.7-1
libavcodec58  (>= 7:4.0) | 7:4.0.3-1
libavdevice58 (>= 7:4.0) | 7:4.0.3-1
libavfilter7  (>= 7:4.0) | 7:4.0.3-1
libavformat58 (>= 7:4.0) | 7:4.0.3-1
libavutil56   (>= 7:4.0) | 7:4.0.3-1
libc6  (>= 2.15) | 2.27-8
libdbus-1-3  (>= 1.9.14) | 1.12.10-1
libdbus-c++-1-0v5| 0.9.0-8.1
libgcc1   (>= 1:3.0) | 1:8.2.0-10
libgnutls30   (>= 3.5.6) | 3.5.19-1+b1
libixml10   (>= 1:1.8.0) | 1:1.8.4-2
libjsoncpp1   (>= 1.7.4) | 1.7.4-3
libnatpmp1 (>= 20150609) | 20150609-5
libnettle6   | 3.4-1
libopus0(>= 1.1) | 1.3~beta+20180518-1
libpcre3 | 2:8.39-11
libpulse0(>= 0.99.1) | 12.2-2
librestbed0  | 4.0~dfsg1-5
libsecp256k1-0 (>= 0.1~20160216) | 0.1~20170810-2
libspeexdsp1  (>= 1.2~beta3.2-1) | 1.2~rc1.2-1+b2
libssl1.1 (>= 1.1.0) | 1.1.1a-1
libstdc++6(>= 7) | 8.2.0-10
libswresample3(>= 7:4.0) | 7:4.0.3-1
libswscale5   (>= 7:4.0) | 7:4.0.3-1
libudev1(>= 183) | 239-13
libupnp13   (>= 1:1.8.3) | 1:1.8.4-2
libuuid1   (>= 2.16) | 2.32.1-0.2
libva-drm2(>= 1.1.0) | 2.3.0-2
libva-x11-2   (>= 1.0.3) | 2.3.0-2
libva2(>= 1.0.3) | 2.3.0-2
libvdpau1   (>= 0.2) | 1.1.1-8
libx11-6 | 2:1.6.7-1
libyaml-cpp0.5v5 | 0.5.3-0.1
zlib1g(>= 1:1.2.3.3) | 1:1.2.11.dfsg-1


Package's Recommends field is empty.

Package's Suggests field is empty.




GNU gdb (Debian 8.1-4+b1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/ring/dring...Reading symbols from 
/usr/lib/debug/.build-id/e4/5f98aba716efc2d8806329ea78fc8ab00437b1.debug...done.
done.
[New LWP 7249]
[New LWP 7250]
[New LWP 7283]
[New LWP 7958]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/ring/dring'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x561dfe99b7c1 in 
YAML::detail::node_data::get, std::allocator > > (pMemory=..., 
key=..., this=) at /usr/include/c++/8/bits/stl_tree.h:984

warning: Source file is more recent than executable.
984   end() _GLIBCXX_NOEXCEPT
[Current thread is 1 (Thread 0x7ff5b5b73c80 (LWP 7249))]
(gdb) bt full
#0  0x561dfe99b7c1 in 
YAML::detail::node_data::get, std::allocator > 
>(std::__cxx11::basic_string, std::allocator 
> const&, boost::shared_ptr) (pMemory=..., 
key="name", this=) at /usr/include/c++/8/bits/stl_tree.h:984
it = non-dereferenceable iterator for associative container
k = 
v = 
value = 
#1  0x561dfe99b7c1 in 
YAML::detail::node_ref::get, std::allocator > 
>(std::__cxx11::basic_string, std::allocator 
> const&, boost::shared_ptr) 

Bug#879034: pdfshuffler: port to gir1.2-poppler-0.18

[Jonas Smedegaard]

Seems upstream don't expect a new stable release soon, and explicilty 
recommends distributions to rather drop the package: 
https://github.com/jeromerobert/pdfarranger/issues/9#issuecomment-427656602


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#913979: marked as done (librdf-linkeddata-perl FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 17:50:01 +
with message-id 
and subject line Bug#913979: fixed in librdf-linkeddata-perl 1.940-1
has caused the Debian Bug report #913979,
regarding librdf-linkeddata-perl FTBFS: test failures
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.)


-- 
913979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librdf-linkeddata-perl
Version: 1.02-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes librdf-linkeddata-perl FTBFS:

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

...
Test Summary Report
---
t/10-basic.t(Wstat: 512 Tests: 21 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/20-psgi-basic.t   (Wstat: 2048 Tests: 60 Failed: 8)
  Failed tests:  31, 34-35, 40-41, 43-45
  Non-zero exit status: 8
Files=11, Tests=316, 20 wallclock secs ( 0.14 usr  0.06 sys + 17.57 cusr  1.86 
csys = 19.63 CPU)
Result: FAIL
Failed 2/11 test programs. 8/316 subtests failed.
make[1]: *** [Makefile:906: test_dynamic] Error 255
--- End Message ---
--- Begin Message ---
Source: librdf-linkeddata-perl
Source-Version: 1.940-1

We believe that the bug you reported is fixed in the latest version of
librdf-linkeddata-perl, 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.
Jonas Smedegaard  (supplier of updated librdf-linkeddata-perl 
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: Sun, 25 Nov 2018 18:34:02 +0100
Source: librdf-linkeddata-perl
Binary: librdf-linkeddata-perl
Architecture: source all
Version: 1.940-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Jonas Smedegaard 
Description:
 librdf-linkeddata-perl - simple Linked Data implementation
Closes: 913979
Changes:
 librdf-linkeddata-perl (1.940-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release(s):
 + Add a possible controls type.
 + Add auth_required method to check if an operation requires
   authentication.
 + Allow a class config option that can add functionality.
 + Check for RDF::LinkedData::RWHypermedia if writes are enabled.
 + Document read-write features.
 + Implement functionality to check if a read operation is given.
 + Improve handling of configuration options.
 + Fix return 404 if controls are requested with no writes.
 + Add support for new RDFa generator.
 + Change name of method to check read operations.
 + Make sure end tags are added to HTML output.
 Closes: Bug#913979. Thanks to Adrian Bunk.
 .
   [ Damyan Ivanov ]
   * declare conformance with Policy 4.1.3 (no changes needed)
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * debian/*: update URLs from {search,www}.cpan.org to MetaCPAN.
   * debian/*: update GitHub URLs to use HTTPS.
 .
   [ Jonas Smedegaard ]
   * Simplify rules:
 + Stop resolve build-dependencies in rules file.
 + Use short-form dh sequencer (not cdbs).
   Stop build-depend on cdbs.
   * Skip testsuite build-dependencies when bootstrapping.
   * Wrap and sort control file.
   * Stop build-depend on dh-buildinfo.
   * Declare compliance with Debian Policy 4.2.1.
   * Update watch file: Fix typo in usage comment.
   * Tighten lintian overrides regarding License-Reference.
   * Update copyright info:
 + Extend coverage of packaging.
 + Extend coverage for main upstream author.
   * Update package relations:
 + Tighten to (build-)depend versioned on librdf-rdfa-generator-perl.
 + (Build-)depend on librdf-trine-serializer-rdfa-perl
   librdf-trinex-compatibility-attean-perl.
   * Set Rules-Requires-Root: no.
Checksums-Sha1:
 f545ffb15b9fcc2943f4a5f34ed20d51cf2d0707 2890 
librdf-linkeddata-perl_1.940-1.dsc
 56f54a95d21f6083416c7df6d7d94e77ff5f1790 51700 
librdf-linkeddata-perl_1.940.ori

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

[Frank Heckenbach]

Hi,

coming back to my own mail, after thinking about it some more:

: > And I think that the default would have to be the old behaviour, yes,
: > because after many years behaving in that way the applications must
: > have learned to adapt or cope, and no one knows that they have to use
: > a different flag or invoke the method with an extra parameter.
:
: For some value of "the applications". You're talking about Debian
: only again, of course, but there are other applications that have
: come to expect the new behaviour (obviously at least mine and the
: patch author's ones, possibly more -- there's a number of forks of
: FTGL on github, probably by people who use(d) it).
:
: > I realise that maybe this is not what you like because applications
: > will ever remain buggy, but reallistically,
:
: The same applies vice-versa for applications that rely on the new
: behaviour if we make the old one the default.
:
: The problem is we have different semantics already (and for almost
: 10 years apparently).
:
: Perhaps the only sane way out is to add *two* new versions of each
: rendering function, one with each behaviour, and deprecate the old
: ones entirely. This will require changes in all applications (if
: only to select the correct one of the two which should be easy if
: ones knows which branch of the library they used before), but at
: least it will be clear at compile time.

That seems to me the best solution indeed. So I can offer this:

- I add these two new versions for all functions involved (quite a
  few); we'd just need to agree about naming ("old" and "new" won't
  do, since in this complicated situation it's not even clear which
  one is old and which one is new; different users will view it
  differently, just like in special relativity ;), also "old" and
  "new" in function names always sounds silly; so perhaps something
  like "RenderBasic" and "RenderDefault" or so ...).

- I deprecate the "Render" functions, adding a special README to
  explain things.

- I change my sources to use "RenderBasic" (or whatever it'll be
  called) and test them. Other users of this fork will have to do
  the same (hopefully after seeing the deprecation warnings and
  reading that README).

- I release 2.4.0 with those changes.

- You put 2.4.0 in Debian. Applications using it will get the
  deprecation warnings, but should otherwise work.

- A bit later, I remove the deprecated functions and release 3.0.0.

- After the release of Buster, you put 3.0.0 in Debian with the
  required transitions.

- Applications using it will break, but fixing them will only
  require changing "Render" to "RenderDefault" in some places
  (which are found by compiler errors). This can also be done before
  you upload 3.0.0 (as "RenderDefault" will be available in 2.4.0
  already), so the transition can be smoohter.

Does this sound like a viable plan?

Cheers,
Frank

Processed: severity of 914565 is serious

[Debian Bug Tracking System]

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

> severity 914565 serious
Bug #914565 [php7.3-intl] php7.3-intl: Segfaults after apache2 graceful restart
Severity set to 'serious' from 'important'
> 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: severity of 914297 is serious

[Debian Bug Tracking System]

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

> severity 914297 serious
Bug #914297 [apache2] apache2: getrandom call blocks on first startup, systemd 
kills with timeout
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 914387 is serious

[Debian Bug Tracking System]

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

> severity 914387 serious
Bug #914387 [python3-pip] python3-pip: cannot import name 'main' from 'pip'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 914441 is serious

[Debian Bug Tracking System]

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

> severity 914441 serious
Bug #914441 [kamoso] kamoso: no user interface is shown: qrc:/qml/Main.qml:7 
module "org.kde.kirigami" is not installed
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: severity of 914481 is serious

[Debian Bug Tracking System]

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

> severity 914481 serious
Bug #914481 [python3-pylxd] [bank] python3-pylxd: Python3-pylxd is not Python3 
compatible
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 914465 is serious

[Debian Bug Tracking System]

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

> severity 914465 serious
Bug #914465 [px] missing dependencies on pkg-resources, procps
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#914547: marked as done (virtualbox is not installable. Depends: python3 (< 3.7) but 3.7.1-2 is to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 19:02:39 +0200
with message-id <20181125170239.GA17495@localhost>
and subject line Re: Bug#914547: virtualbox is not installable. Depends: 
python3 (< 3.7) but 3.7.1-2 is to be installed
has caused the Debian Bug report #914547,
regarding virtualbox is not installable. Depends: python3 (< 3.7) but 3.7.1-2 
is to be installed
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.)


-- 
914547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: virtualbox
Version: 5.2.20-dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

 Dist-upgrade on sid/unstable introduced an unmet python3 dependency. 
Virtualbox
 depends on version < 3.7 but python3 is currently installed with version 
3.7.1-2

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 Performed a dist-upgrade on sid/unstable 

   * What was the outcome of this action?

 The package got removed due to the unmet dependency.

   * What outcome did you expect instead?

 Expected the package to be kept installed.

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 virtualbox depends on:
ii  adduser   3.118
ii  iproute2  4.18.0-2
ii  libc6 2.27-8
ii  libcurl3-gnutls   7.62.0-1
ii  libdevmapper1.02.12:1.02.145-4.1
ii  libgcc1   1:8.2.0-10
pn  libgsoap-2.8.60   
ii  libpng16-16   1.6.34-2
ii  libpython3.6  3.6.7-1
ii  libsdl1.2debian   1.2.15+dfsg2-4
ii  libssl1.1 1.1.1a-1
ii  libstdc++68.2.0-10
pn  libvncserver1 
ii  libx11-6  2:1.6.7-1
ii  libxcursor1   1:1.1.15-2
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-7+b2
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  python3   3.7.1-2
ii  python3.6 3.6.7-1
ii  virtualbox-dkms [virtualbox-modules]  5.2.22-dfsg-1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages virtualbox recommends:
ii  libgl1  1.1.0-1
ii  libqt5core5a5.11.2+dfsg-7
ii  libqt5opengl5   5.11.2+dfsg-7
ii  libqt5widgets5  5.11.2+dfsg-7
pn  virtualbox-qt   

Versions of packages virtualbox suggests:
pn  vde2
pn  virtualbox-guest-additions-iso  
--- End Message ---
--- Begin Message ---
On Sat, Nov 24, 2018 at 06:43:27PM +0100, Robert Ulrich wrote:
> Package: virtualbox
> Version: 5.2.20-dfsg-3
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> 
>  Dist-upgrade on sid/unstable introduced an unmet python3 dependency. 
> Virtualbox
>  depends on version < 3.7 but python3 is currently installed with version 
> 3.7.1-2
>...

Thanks for your report.

The rebuild scheduling will be handled in #913069.

cu
Adrian

-- 

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

Processed: severity of 914524 is serious

[Debian Bug Tracking System]

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

> severity 914524 serious
Bug #914524 [sogo] sogo: SSL problem(?) causes 'An error occurred during object 
publishing' in webmail
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#911957: [src:rquantlib] FTBFS with boost1.67

[Dirk Eddelbuettel]

On 28 October 2018 at 09:31, Dirk Eddelbuettel wrote:
| 
| On 26 October 2018 at 17:13, Giovanni Mascellani wrote:
| | Package: src:rquantlib
| | Version: 0.4.5-1
| | Severity: wishlist
| | Tags: patch
| | User: team+bo...@tracker.debian.org
| | Usertags: boost1.67
| | 
| | Dear Maintainer,
| | 
| | your package fails to build with boost1.67. You can find a build log
| | attached. If you want to attempt the build yourself, an updated version
| | of boost-defaults which brings in boost1.67 dependencies can be found
| | adding this line to your sources.list file:
| | 
| |   deb https://people.debian.org/~gio/reprepro unstable main
| | 
| | This bug has severity whishlist for the moment, but it will raised to RC
| | as soon as version 1.67 of Boost is promoted to default.
| | 
| | More specifically, your package fails building because
| | boost::posix_time::minutes and similar calls now require an integral
| | argument. The attached patch should fix this issue.
| | 
| | Please consider applying the attached patch as soon as boost1.67 is made
| | default in order to avoid FTBFS.
| 
| Patch works great, thank you. I tested under your Boost 1.67 as well as the
| standard older Boost packages and applied it to my upstream repo. I will cut
| a new release of this R package in the next few days and then also update the
| Debian package.

Package is now on CRAN, Debian upload to follow.

Dirk

| 
| Thanks again,  Dirk
|  
| | Thanks and all the best, Giovanni.
| | -- 
| | Giovanni Mascellani 
| | Postdoc researcher - Université Libre de Bruxelles
| | x[DELETED ATTACHMENT 0001-Fix-build-with-Boost-1.67.patch, text/x-patch]
| | x[DELETED ATTACHMENT build-rquantlib.log, text/x-log]
| | x[DELETED ATTACHMENT signature.asc, application/pgp-signature]
| 
| -- 
| http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#912113: harvest-tools: diff for NMU version 1.3-2.1

[Adrian Bunk]

Control: tags 912113 + pending

Dear maintainer,

I've prepared an NMU for harvest-tools (versioned as 1.3-2.1) and 
uploaded it to DELAYED/14. Please feel free to tell me if I should 
cancel it.

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

diff -Nru harvest-tools-1.3/debian/changelog harvest-tools-1.3/debian/changelog
--- harvest-tools-1.3/debian/changelog	2018-07-17 18:00:34.0 +0300
+++ harvest-tools-1.3/debian/changelog	2018-11-25 18:48:23.0 +0200
@@ -1,3 +1,10 @@
+harvest-tools (1.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix a frequent parallel FTBFS. (Closes: #912113)
+
+ -- Adrian Bunk   Sun, 25 Nov 2018 18:48:23 +0200
+
 harvest-tools (1.3-2) unstable; urgency=medium
 
   [ Steffen Moeller ]
diff -Nru harvest-tools-1.3/debian/patches/parallel.patch harvest-tools-1.3/debian/patches/parallel.patch
--- harvest-tools-1.3/debian/patches/parallel.patch	1970-01-01 02:00:00.0 +0200
+++ harvest-tools-1.3/debian/patches/parallel.patch	2018-10-28 12:51:06.0 +0200
@@ -0,0 +1,22 @@
+Description: Fix a frequent parallel FTBFS
+Author: Adrian Bunk 
+
+--- harvest-tools-1.3.orig/Makefile.in
 harvest-tools-1.3/Makefile.in
+@@ -37,10 +37,14 @@ harvesttools : $(OBJECTS)
+ %.o : %.cc
+ 	$(CXX) -c $(CXXFLAGS) $(CPPFLAGS) -o $@ $<
+ 
+-src/harvest/pb/harvest.pb.cc src/harvest/pb/harvest.pb.h : src/harvest/pb/harvest.proto
++src/harvest/pb/harvest.pb.cc : src/harvest/pb/harvest.pb.h
++
++src/harvest/pb/harvest.pb.h : src/harvest/pb/harvest.proto
+ 	cd src; @protobuf@/bin/protoc --cpp_out . harvest/pb/harvest.proto
+ 
+-src/harvest/capnp/harvest.capnp.c++ src/harvest/capnp/harvest.capnp.h : src/harvest/capnp/harvest.capnp
++src/harvest/capnp/harvest.capnp.c++ : src/harvest/capnp/harvest.capnp.h
++
++src/harvest/capnp/harvest.capnp.h : src/harvest/capnp/harvest.capnp
+ 	cd src/harvest/capnp;export PATH=@capnp@/bin/:${PATH};capnp compile -I @capnp@/include -oc++ harvest.capnp
+ 
+ install : harvesttools
diff -Nru harvest-tools-1.3/debian/patches/series harvest-tools-1.3/debian/patches/series
--- harvest-tools-1.3/debian/patches/series	2018-07-17 18:00:34.0 +0300
+++ harvest-tools-1.3/debian/patches/series	2018-10-28 12:50:02.0 +0200
@@ -2,3 +2,4 @@
 dynamic_linking.patch
 hardening.patch
 remove_memwrap.patch
+parallel.patch

Processed: harvest-tools: diff for NMU version 1.3-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 912113 + pending
Bug #912113 [src:harvest-tools] harvest-tools: frequent parallel FTBFS
Added tag(s) pending.

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

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

[Amy Kos]

Could be graphics related, boot stops at:

 fb: switching to inteldrmfb from EFI VGA

Disabling kernel mode setting with parameter nomodeset boots to tty.

Bug#914061: marked as done (performous FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 16:21:06 +
with message-id 
and subject line Bug#914061: fixed in performous 1.1+git20181118-1
has caused the Debian Bug report #914061,
regarding performous FTBFS with boost 1.67
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.)


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

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

...
/<>/game/audio.cc: In static member function 'static 
boost::posix_time::time_duration AudioClock::getDuration(double)':
/<>/game/audio.cc:80:86: error: no matching function for call to 
'boost::date_time::subsecond_duration::subsecond_duration(double)'
  static time_duration getDuration(double seconds) { return microseconds(1e6 * 
seconds); }

  ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:15,
 from /usr/include/boost/date_time/local_time/local_time.hpp:11,
 from /usr/include/boost/date_time.hpp:15,
 from /<>/game/audio.hh:3,
 from /<>/game/audio.cc:1:
/usr/include/boost/date_time/time_duration.hpp:285:14: note: candidate: 
'template boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if, void>::type*)'
 explicit subsecond_duration(T const& ss,
  ^~
/usr/include/boost/date_time/time_duration.hpp:285:14: note:   template 
argument deduction/substitution failed:
/usr/include/boost/date_time/time_duration.hpp: In substitution of 
'template 
boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if >::type*) [with T = double]':
/<>/game/audio.cc:80:86:   required from here
/usr/include/boost/date_time/time_duration.hpp:285:14: error: no type named 
'type' in 'struct boost::enable_if, void>'
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:15,
 from /usr/include/boost/date_time/local_time/local_time.hpp:11,
 from /usr/include/boost/date_time.hpp:15,
 from /<>/game/audio.hh:3,
 from /<>/game/audio.cc:1:
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(const 
boost::date_time::subsecond_duration&)'
   class BOOST_SYMBOL_VISIBLE subsecond_duration : public base_duration
  ^~
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 'const 
boost::date_time::subsecond_duration&'
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(boost::date_time::subsecond_duration&&)'
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 
'boost::date_time::subsecond_duration&&'
/<>/game/audio.cc: In member function 
'boost::posix_time::time_duration Music::durationOf(int64_t) const':
/<>/game/audio.cc:152:99: error: no matching function for call to 
'boost::date_time::subsecond_duration::subsecond_duration(double)'
  time_duration durationOf(int64_t samples) const { return microseconds(1e6 * 
samples / srate / 2.0); }

   ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:15,
 from /usr/include/boost/date_time/local_time/local_time.hpp:11,
 from /usr/include/boost/date_time.hpp:15,
 

Bug#914607: plaso depends on cruft package python-dfwinreg

[peter green]

Package: plaso
Version: 1.5.1+dfsg-4
Severity: serious

plaso depends on python-dfwinreg which is no longer built by the dfwinreg 
source package.

Processed: Bug #914061 in performous marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914061 [src:performous] performous FTBFS with boost 1.67
Added tag(s) pending.

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

Bug#914061: Bug #914061 in performous marked as pending

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #914061 in performous 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/games-team/performous/commit/160cce889fb4db7ec32b04f46804143772a86864


Import Debian changes 1.1+git20181118-1

performous (1.1+git20181118-1) unstable; urgency=medium

  * New upstream version 1.1+git20181118.
- Fix FTBFS with Boost 1.67. (Closes: #914061)
  Thanks to Adrian Bunk for the report.
- See README.source how the original tarball was created.
  The www directory contained Javascript files without source and was
  removed.
  * Drop deprecated menu file and xpm icon.
  * Update README.Debian
  * Switch to compat level 11.
  * Declare compliance with Debian Policy 4.2.1.
  * Tighten B-D on libboost-all-dev.
  * Build-depend on libglm-dev and libcpprest-dev.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914061

Bug#910731: kaddressbook: crashes at startup

[Bernhard Übelacker]

Hello Francesco,
can you still observe the crash, or got it fixed by updates
in mid October? (Like mentioned in #910581)

If it is fixed that bug might be closed.

Kind regards,
Bernhard

Bug#910731: kaddressbook: crashes at startup

[Bernhard Übelacker]

Hello Francesco,
can you still observe the crash, or got it fixed by updates
in mid October? (Like mentioned in #910581)

If it is fixed that bug might be closed.

Kind regards,
Bernhard

Bug#911760: marked as done (lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 16:25:05 +0100
with message-id 
and subject line Re: Bug#911760: lightdm-gtk-greeter segfault, lightdm restart 
too fast, can't login to desktop (Bug #911760)
has caused the Debian Bug report #911760,
regarding lightdm-gtk-greeter segfault, lightdm restart too fast, can't login 
to desktop
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.)


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

Dear Maintainer,

   * What led up to the situation?

A system upgrade, a list of the packages upgraded should be attached, I don't 
see any relation with lightdm but I could be missing something

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

apt update
apt upgrade
reboot

   * What was the outcome of this action?

lightdm doesn't start, segfault and restart until systemd stop it

   * What outcome did you expect instead?

the usual login dialog

Attached there should be the `journal -xe` segfault, the list of the packages 
installed by the upgrade, the backtrace of a `gdb lighdm --debug` session.
Please let me know how/if I can help with more logs.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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 lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  debconf [debconf-2.0]  1.5.69
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libgcrypt201.8.3-1
ii  libglib2.0-0   2.58.1-2
ii  libpam-systemd 239-10
ii  libpam0g   1.1.8-3.8
ii  libxcb11.13.1-1
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.5-1
ii  lsb-base   9.20170808

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
pn  accountsservice  
ii  upower   0.99.8-2
ii  xserver-xephyr   2:1.20.1-5

-- Configuration Files:
/etc/lightdm/lightdm.conf changed:
[LightDM]
[Seat:*]
[XDMCPServer]
[VNCServer]


-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
Starting program: /usr/sbin/lightdm --debug --test-mode
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.03s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=2132
[+0.05s] DEBUG: Loading configuration dirs from 
/usr/share/lightdm/lightdm.conf.d
[+0.07s] DEBUG: Loading configuration from 
/usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.10s] DEBUG: Loading configuration dirs from 
/usr/local/share/lightdm/lightdm.conf.d
[+0.12s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.14s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.16s] DEBUG: Registered seat module local
[+0.19s] DEBUG: Registered seat module xremote
[+0.21s] DEBUG: Registered seat module unity
[+0.23s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[New Thread 0x76714700 (LWP 2136)]
[New Thread 0x75f13700 (LWP 2137)]
[New Thread 0x756cc700 (LWP 2138)]
[+0.36s] DEBUG: Monitoring logind for seats
[+0.38s] DEBUG: New seat added from logind: seat0
[+0.40s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.42s] DEBUG: Seat seat0: Starting
[+0.44s] DEBUG: Seat seat0: Creating greeter session
[+0.46s] DEBUG: Seat seat0: Creating display server of type x
[+0.48s] DEBUG: posix_spawn avoided (fd close requested)
[+0.49s] DEBUG: Could not run plymouth --ping: Failed to execute child process 
?plymouth? (No such file or directory)
[+0.51s] DEBUG: Using VT 7
[+0.53s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.55s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.57s] DEBUG: XServer 0: Writing X server authority to 

Processed: Re: Bug#911760: lightdm-gtk-greeter segfault, lightdm restart too fast, can't login to desktop (Bug #911760)

[Debian Bug Tracking System]

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

> reassign 911760 libatspi2.0-0 2.30.0-3
Bug #911760 [lightdm] lightdm-gtk-greeter segfault, lightdm restart too fast, 
can't login to desktop
Bug reassigned from package 'lightdm' to 'libatspi2.0-0'.
No longer marked as found in versions lightdm/1.26.0-3.
Ignoring request to alter fixed versions of bug #911760 to the same values 
previously set
Bug #911760 [libatspi2.0-0] lightdm-gtk-greeter segfault, lightdm restart too 
fast, can't login to desktop
Marked as found in versions at-spi2-core/2.30.0-3.
> fixed 911760 2.30.0-4
Bug #911760 [libatspi2.0-0] lightdm-gtk-greeter segfault, lightdm restart too 
fast, can't login to desktop
Marked as fixed in versions at-spi2-core/2.30.0-4.
> affects 911760 + lightdm
Bug #911760 [libatspi2.0-0] lightdm-gtk-greeter segfault, lightdm restart too 
fast, can't login to desktop
Added indication that 911760 affects lightdm
>
End of message, stopping processing here.

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

Bug#914175: marked as done (lightning is not installable after binNMUs)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 15:01:29 +
with message-id 
and subject line Bug#914175: fixed in thunderbird 1:60.3.1-1
has caused the Debian Bug report #914175,
regarding lightning is not installable after binNMUs
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.)


-- 
914175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lightning
Version: 1:60.3.0-1
Severity: serious

 thunderbird : Breaks: lightning (< 1:60.3.0-1+b1) but 1:60.3.0-1 is to be 
installed

lightning is binary-all, ${source:Version} should be used
for Breaks and Recommends.
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.3.1-1

We believe that the bug you reported is fixed in the latest version of
thunderbird, 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.
Carsten Schoenert  (supplier of updated thunderbird 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Nov 2018 10:02:50 +0100
Source: thunderbird
Binary: thunderbird lightning calendar-google-provider thunderbird-l10n-all 
thunderbird-l10n-ar thunderbird-l10n-ast thunderbird-l10n-be 
thunderbird-l10n-bg thunderbird-l10n-br thunderbird-l10n-ca thunderbird-l10n-cs 
thunderbird-l10n-cy thunderbird-l10n-da thunderbird-l10n-de 
thunderbird-l10n-dsb thunderbird-l10n-el thunderbird-l10n-en-gb 
thunderbird-l10n-es-ar thunderbird-l10n-es-es thunderbird-l10n-et 
thunderbird-l10n-eu thunderbird-l10n-fi thunderbird-l10n-fr 
thunderbird-l10n-fy-nl thunderbird-l10n-ga-ie thunderbird-l10n-gd 
thunderbird-l10n-gl thunderbird-l10n-he thunderbird-l10n-hr 
thunderbird-l10n-hsb thunderbird-l10n-hu thunderbird-l10n-hy-am 
thunderbird-l10n-id thunderbird-l10n-is thunderbird-l10n-it thunderbird-l10n-ja 
thunderbird-l10n-kab thunderbird-l10n-kk thunderbird-l10n-ko 
thunderbird-l10n-lt thunderbird-l10n-ms thunderbird-l10n-nb-no 
thunderbird-l10n-nl thunderbird-l10n-nn-no thunderbird-l10n-pl 
thunderbird-l10n-pt-br thunderbird-l10n-pt-pt
 thunderbird-l10n-rm thunderbird-l10n-ro thunderbird-l10n-ru 
thunderbird-l10n-si thunderbird-l10n-sk thunderbird-l10n-sl thunderbird-l10n-sq 
thunderbird-l10n-sr thunderbird-l10n-sv-se thunderbird-l10n-tr 
thunderbird-l10n-uk thunderbird-l10n-vi thunderbird-l10n-zh-cn 
thunderbird-l10n-zh-tw lightning-l10n-ar lightning-l10n-ast lightning-l10n-be 
lightning-l10n-bg lightning-l10n-br lightning-l10n-ca lightning-l10n-cs 
lightning-l10n-cy lightning-l10n-da lightning-l10n-de lightning-l10n-dsb 
lightning-l10n-el lightning-l10n-es-ar lightning-l10n-es-es 
lightning-l10n-en-gb lightning-l10n-et lightning-l10n-eu lightning-l10n-fi 
lightning-l10n-fr lightning-l10n-fy-nl lightning-l10n-ga-ie lightning-l10n-gd 
lightning-l10n-gl lightning-l10n-he lightning-l10n-hr lightning-l10n-hsb 
lightning-l10n-hu lightning-l10n-hy-am lightning-l10n-id lightning-l10n-is 
lightning-l10n-it lightning-l10n-ja lightning-l10n-kab lightning-l10n-kk 
lightning-l10n-ko lightning-l10n-ms lightning-l10n-lt
 lightning-l10n-nb-no lightning-l10n-nl lightning-l10n-nn-no lightning-l10n-pl 
lightning-l10n-pt-br lightning-l10n-pt-pt lightning-l10n-rm lightning-l10n-ro 
lightning-l10n-ru lightning-l10n-si lightning-l10n-sk lightning-l10n-sl 
lightning-l10n-sr lightning-l10n-sq lightning-l10n-sv-se lightning-l10n-tr 
lightning-l10n-uk lightning-l10n-vi lightning-l10n-zh-cn
 lightning-l10n-zh-tw
Architecture: source
Version: 1:60.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Carsten Schoenert 
Changed-By: Carsten Schoenert 
Description:
 calendar-google-provider - Google Calendar support for lightning
 lightning  - Calendar Extension for Thunderbird
 lightning-l10n-ar - Arabic language package for lightning - Transitional 
package
 lightning-l10n-ast - Asturian language package for lightning - Transitional 
package
 lightning-l10n-be - Belarusian language package for lightning - Transitional 
package
 lightning-l10n-bg - Bulgarian language package for lightning - Transitional 
package
 lightning-l10n-br - Breton language package for

Bug#914557: marked as done (thunderbird: Version 1:60.3.0-1+b1 is not installable (breaks lightning and various calendar))

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 15:01:29 +
with message-id 
and subject line Bug#914175: fixed in thunderbird 1:60.3.1-1
has caused the Debian Bug report #914175,
regarding thunderbird: Version 1:60.3.0-1+b1 is not installable (breaks 
lightning and various calendar)
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.)


-- 
914175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: thunderbird
Version: 1:60.3.0-1+b1
Severity: important

LANG=C apt-get -s install thunderbird
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Recommended packages:
  lightning
The following packages will be REMOVED:
  calendar-exchange-provider calendar-google-provider lightning
The following packages will be upgraded:
  thunderbird
1 upgraded, 0 newly installed, 3 to remove and 5 not upgraded.
Remv calendar-exchange-provider [5.0.0~alpha1-1]
Remv calendar-google-provider [1:60.3.0-1]
Remv lightning [1:60.3.0-1]
Inst thunderbird [1:60.3.0-1] (1:60.3.0-1+b1 Debian:unstable [amd64])
Conf thunderbird (1:60.3.0-1+b1 Debian:unstable [amd64])

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

Kernel: Linux 4.14.83 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunderbird depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.1-2
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.28-0experimental1
ii  libcairo-gobject2 1.16.0-1
ii  libcairo2 1.16.0-1
ii  libdbus-1-3   1.13.6-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.1-2
ii  libfreetype6  2.9.1-3
ii  libgcc1   1:8.2.0-10
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-6
ii  libgtk-3-03.24.1-2
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.6-0 1.6.2-2
ii  libicu60  60.2-6
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.39-1
ii  libpango-1.0-01.42.4-4
ii  libpangocairo-1.0-0   1.42.4-4
ii  libpangoft2-1.0-0 1.42.4-4
ii  libsqlite3-0  3.25.3-2
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-10
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.7-1
ii  libx11-xcb1   2:1.6.7-1
ii  libxcb-shm0   1.13.1-1
ii  libxcb1   1.13.1-1
ii  libxext6  2:1.3.3-1+b2
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  psmisc23.2-1
ii  x11-utils 7.7+4
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1
ii  hunspell-fr-classical [hunspell-dictionary]  1:6.3-1
ii  lightning1:60.3.0-1

Versions of packages thunderbird suggests:
ii  apparmor  2.13.1-3+b1
ii  fonts-lyx 2.3.1-2-2
ii  libgssapi-krb5-2  1.16.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: thunderbird
Source-Version: 1:60.3.1-1

We believe that the bug you reported is fixed in the latest version of
thunderbird, 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.
Carsten Schoenert  (supplier of updated thunderbird 
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

Bug#914596: python-casacore ftbfs with new casacore

[Matthias Klose]

Package: src:python-casacore
Version: 2.2.1-1
Severity: serious
Tags: sid buster

different error on amd64:

see
https://buildd.debian.org/status/fetch.php?pkg=python-casacore&arch=amd64&ver=2.2.1-1%2Bb2&stamp=1542542922&raw=0

pybuild --test -i python{version} -p "3.7 3.6"
I: pybuild base:217: cd /<>/.pybuild/cpython3_3.7_casacore/build;
python3.7 -m unittest discover -v
Segmentation fault
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=139: cd
/<>/.pybuild/cpython3_3.7_casacore/build; python3.7 -m unittest
discover -v
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:8: build-arch] Error 25


all others:

powerpc64le-linux-gnu-g++ -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-wz4KDq/python2.7-2.7.15=.
-fstack-protector-strong -Wformat -Werror=format-security -fexceptions
-Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 build/temp.linux-ppc64el-2.7/src/fit.o
build/temp.linux-ppc64el-2.7/src/fitting.o -lcasa_scimath -lcasa_scimath_f
-lboost_python-py27 -lcasa_python -o
/<>/.pybuild/cpython2_2.7_casacore/build/casacore/fitting/_fitting.so
/usr/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
error: command 'powerpc64le-linux-gnu-g++' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1:
/usr/bin/python setup.py build
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:8: build-arch] Error 25

Bug#904000: marked as done (audacious: Opening URL fails)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 15:14:25 +0100
with message-id 
and subject line Re: audacious: Opening URL fails
has caused the Debian Bug report #904000,
regarding audacious: Opening URL fails
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.)


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

Dear Maintainer,

-- System Information:
Debian Release: 9.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Audacious suddendly does no more acctept standard URLs like this: 
http://servername:port/file.

In my case it was "http://relay.publicdomainproject.org:80/modern_jazz.aac";.

This worked fine for a while - same on all other media players, 
because it's a real trivial pointer to some source.

Then I just checked out the audacious features, playing around all the 
multiple options. I really can not remember what I tried all - but 
suddendly the above mentioned URL failes with the error 
message "Unknown URI scheme".

How can this be???

I "purged" audacious with the apt-tool, then reinstalled it, 
but the problem persists.
--- End Message ---
--- Begin Message ---
Closing, since this has been marked as fixed, and there have been no
news in a long time.

-- 
Cheers,
  Andrej--- End Message ---

Processed: Bug #914483 in gdcm marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914483 [src:gdcm] gdcm: ABI break
Bug #914482 [src:gdcm] gdcm: ABI break
Added tag(s) pending.
Added tag(s) pending.

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

Bug#914483: Bug #914483 in gdcm marked as pending

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #914483 in gdcm 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/med-team/gdcm/commit/8c016cd6bb268fadf5011f06ef4ec63c2b3238f3


Rename the libvtkgdcm2.8 package to libvtkgdcm2.8a, following the ABI break 
happened in version 2.8.7-2.

Closes: #914483
Signed-off-by: Mattia Rizzolo 



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914483

Bug#914587: blueman: broken package

[Adrian Bunk]

On Sun, Nov 25, 2018 at 01:17:57PM +0100, Stephan Lachnit wrote:
> Package: blueman
> Version: 2.0.6-1
> Severity: grave
> Tags: newcomer
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> this package has wrong python dependencies. It should depend on the python3.6
> package or python3 (< 3.7), because it doesn't install on latest Debian Sid
> (unstable).

Thanks for your report.

The rebuild scheduling will be handled in #913069.

cu
Adrian

-- 

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

Bug#914582: liblingua-en-fathom-perl: Fails to build due to unmet build dependecies

[gregor herrmann]

Control: tag -1 + pending

On Sun, 25 Nov 2018 11:46:25 +0100, Hans Joachim Desserud wrote:

> When attempting to build this package, installing build dependencies fails
> because liblingua-en-sentence-perl doesn't seem to exist in Debian.

It's already in the NEW queue, waiting for ftp-master approval:
https://ftp-master.debian.org/new/liblingua-en-sentence-perl_0.31-1.html
 
Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Bettina Wegner: Der Fuehrer


signature.asc
Description: Digital Signature

Bug#914587: marked as done (blueman: broken package)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 15:44:57 +0200
with message-id <20181125134213.GA528@localhost>
and subject line Re: Bug#914587: blueman: broken package
has caused the Debian Bug report #914587,
regarding blueman: broken package
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.)


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

Dear Maintainer,

this package has wrong python dependencies. It should depend on the python3.6
package or python3 (< 3.7), because it doesn't install on latest Debian Sid
(unstable).



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blueman depends on:
ii  bluez 5.50-1
ii  bluez-obexd   5.50-1
ii  dbus  1.12.10-1
ii  dbus-user-session [default-dbus-session-bus]  1.12.10-1
ii  dbus-x11 [dbus-session-bus]   1.12.10-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-1
pn  gir1.2-appindicator3-0.1  
ii  gir1.2-gdkpixbuf-2.0  2.38.0+dfsg-6
ii  gir1.2-glib-2.0   1.58.0-1
ii  gir1.2-gtk-3.03.24.1-2
ii  gir1.2-notify-0.7 0.7.7-3
ii  gir1.2-pango-1.0  1.42.4-4
ii  gnome-icon-theme  3.12.0-3
ii  libbluetooth3 5.50-1
ii  libc6 2.27-8
ii  libglib2.0-0  2.58.1-2
ii  libpulse-mainloop-glib0   12.2-2
ii  libpython3.6  3.6.7-1
ii  librsvg2-common   2.44.9-1
ii  notification-daemon   3.20.0-3
ii  python3   3.7.1-2
ii  python3-cairo 1.16.2-1+b1
ii  python3-dbus  1.2.8-2+b1
ii  python3-gi3.30.2-1
ii  python3-gi-cairo  3.30.2-1
ii  xfce4-notifyd [notification-daemon]   0.4.2-1

Versions of packages blueman recommends:
ii  policykit-1  0.105-21
ii  pulseaudio-module-bluetooth  12.2-2

blueman suggests no packages.
--- End Message ---
--- Begin Message ---
On Sun, Nov 25, 2018 at 01:17:57PM +0100, Stephan Lachnit wrote:
> Package: blueman
> Version: 2.0.6-1
> Severity: grave
> Tags: newcomer
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> this package has wrong python dependencies. It should depend on the python3.6
> package or python3 (< 3.7), because it doesn't install on latest Debian Sid
> (unstable).

Thanks for your report.

The rebuild scheduling will be handled in #913069.

cu
Adrian

-- 

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

Processed: Re: Bug#914582: liblingua-en-fathom-perl: Fails to build due to unmet build dependecies

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #914582 [liblingua-en-fathom-perl] liblingua-en-fathom-perl: Fails to build 
due to unmet build dependecies
Added tag(s) pending.

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

Processed: severity of 913896 is minor

[Debian Bug Tracking System]

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

> severity 913896 minor
Bug #913896 [src:libbson] libbson: CVE-2018-16790: heap-based buffer over-read 
via a crafted bson buffer
Severity set to 'minor' from 'grave'
> thanks
Stopping processing here.

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

Bug#913963: marked as done (libbson: CVE-2018-16790: heap-based buffer over-read via a crafted bson buffer)

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 13:34:29 +
with message-id 
and subject line Bug#913963: fixed in mongo-c-driver 1.13.0-1
has caused the Debian Bug report #913963,
regarding libbson: CVE-2018-16790: heap-based buffer over-read via a crafted 
bson buffer
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.)


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

Please see https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16790

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: mongo-c-driver
Source-Version: 1.13.0-1

We believe that the bug you reported is fixed in the latest version of
mongo-c-driver, 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.
Roberto C. Sanchez  (supplier of updated mongo-c-driver 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Nov 2018 15:01:25 -0500
Source: mongo-c-driver
Binary: libmongoc-dev libmongoc-1.0-0 libmongoc-doc libbson-dev libbson-1.0-0 
libbson-doc
Architecture: source
Version: 1.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: Mongo C Driver Team 
Changed-By: Roberto C. Sanchez 
Description:
 libbson-1.0-0 - Library to parse and generate BSON documents - runtime files
 libbson-dev - Library to parse and generate BSON documents - dev files
 libbson-doc - Library to parse and generate BSON documents - documentation
 libmongoc-1.0-0 - MongoDB C client library - runtime files
 libmongoc-dev - MongoDB C client library - dev files
 libmongoc-doc - MongoDB C client library - documentation
Closes: 913963
Changes:
 mongo-c-driver (1.13.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #913963)
   * Update maintainer to team address
   * Update to Standards-Version 4.2.1 (no changes)
Checksums-Sha1:
 a9a393e4ef659f8098f7c6198b83845604fe5397 2514 mongo-c-driver_1.13.0-1.dsc
 7f1ed2e2d40dac0d5c4137d8f48151207d8b4b4e 5168399 
mongo-c-driver_1.13.0.orig.tar.gz
 ed034b12e7c68ee1a8908a45c39269f0d4b6ea46 12368 
mongo-c-driver_1.13.0-1.debian.tar.xz
 1c7fe1c807a23b7fb45f01258b75f8f17a1976cc 10805 
mongo-c-driver_1.13.0-1_amd64.buildinfo
Checksums-Sha256:
 90c3c7398fb90d137a74c238e0bb8a22bf327df92b01a2c8f57d2eaf1d5c9092 2514 
mongo-c-driver_1.13.0-1.dsc
 81d2c325bd50f98e2fe7a8bb21c9975c5e105c1a197ed817ad28fc8cd3cb0fb5 5168399 
mongo-c-driver_1.13.0.orig.tar.gz
 f474e4ecb7af676e5b8327d65b6680ae621de06a91479cbac4ee8e7a65c9acf9 12368 
mongo-c-driver_1.13.0-1.debian.tar.xz
 286bbde236757e66cbcb988c5d806b335cc9b493d0fc972529fef56416219f1d 10805 
mongo-c-driver_1.13.0-1_amd64.buildinfo
Files:
 829552f88549ad53de1fa87f5787a000 2514 libs optional mongo-c-driver_1.13.0-1.dsc
 056ed35d40315c96745c83635de89803 5168399 libs optional 
mongo-c-driver_1.13.0.orig.tar.gz
 c2ee69f44ea75f721a9f5bba2c49a4c5 12368 libs optional 
mongo-c-driver_1.13.0-1.debian.tar.xz
 0fcb81d827d36357633b880a1c21a580 10805 libs optional 
mongo-c-driver_1.13.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEz9ERzDttUsU/BH8iLNd4Xt2nsg8FAlv6oiAACgkQLNd4Xt2n
sg9yBRAAkzI240LmRRvum7i2UE4lSIcFqicNVQ/M/zqL57QjlHnqPsZajZY+fzwk
126wgaaX7OcIt07LPtHxef98COx8yCmytfH32MwSaRkNVa9WRKXNzhRaak2EmrwL
U0S3fpINeKhgwz837vEh4hN0Gkf/tGB/SOgMlYTCFfVcTuLJNF/O9+/g56p47X2H
4zvakwUHbqo1MiVaFWhov5tU5kKVuhsGOxUffUFkROLafHE2i4tyzEnVPcoMlHPK
/b7f1Pq5hhizC672s7LP5LkAJdJDeTtTgtDgR5YcZKFyNxm8UzPTxJJx+cw/QWpH
0JFEvSIwHu9pQISw+eYg8OpOr/jOgeadLAnAF1l+a7p6lhNIphZKHrAIDlmcdswu
V6Py9LlQY2bJ47L35ARDlCJt57F2InYSVX62fo6xp6bdDzdIFQ9kMCfc7bmN4i38
2gjEeyhV2Cb35z3IIXZrT1QnOv3/pR1M7KyYI2zCgOazfS5afBAvupjEmedZ55T5
Rm4ZHXGaGpPuLa4FQa2M20+pf32nR4M313rGp6dQnVxnpmDBZnDW/5dlpYh8kUUx
ZbnDl4xDAm83TgX4Elo3k8V9V2bPattYOT6rwsMTgQI683g47IojfbgT6HGl5gx5
7i+BKGMkXEiGiyr9/6fXMatoX5yVEs1TyKs0ZN4O7pyc806WoHc=
=n44A
-END PGP SIGNATURE End Message ---

Processed: retitle 913775 to php7.3-imap: CVE-2018-19518: imap_open() function command injection ...

[Debian Bug Tracking System]

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

> retitle 913775 php7.3-imap: CVE-2018-19518: imap_open() function command 
> injection
Bug #913775 [php7.3-imap] php7.3-imap: imap_open() function command injection
Changed Bug title to 'php7.3-imap: CVE-2018-19518: imap_open() function command 
injection' from 'php7.3-imap: imap_open() function command injection'.
> retitle 913835 php7.2-imap: CVE-2018-19518: imap_open() function command 
> injection
Bug #913835 [php7.2-imap] php7.2-imap: imap_open() function command injection
Changed Bug title to 'php7.2-imap: CVE-2018-19518: imap_open() function command 
injection' from 'php7.2-imap: imap_open() function command injection'.
> retitle 913836 php7.0-imap: CVE-2018-19518: imap_open() function command 
> injection
Bug #913836 [php7.0-imap] php7.0-imap: imap_open() function command injection
Changed Bug title to 'php7.0-imap: CVE-2018-19518: imap_open() function command 
injection' from 'php7.0-imap: imap_open() function command injection'.
> thanks
Stopping processing here.

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

Bug#880047: postgrey: Regression - Postgrey doesn't start after installing new stable proposed-update

[Adrian Bunk]

On Sat, Nov 10, 2018 at 01:37:20PM +, Roger Lynn wrote:
> On 08/11/18 19:34, Adrian Bunk wrote:
> > Tanks a lot for trying stretch-proposed-updates and reproting bugs you find!
> > 
> > This is a regression that is also in 1.36-5 in unstable.
> > 
> > The proposed 1.36-3+deb9u1 update has now been dropped from the upcoming
> > stretch point release.
> 
> Thank you for your work on this package. I think the reason my system was
> badly affected by the new release is because I had used the example unix
> socket location given in /usr/share/doc/postgrey/README.exim, which
> conflicted with the new directory created in the init script (although to be
> fair, the README does warn that the socket location might need to be
> changed).

I'd guess for stretch this just means that I'll prepare a 1.36-3+deb9u2
update that will revert to the situation 1.36-3 - I don't see any way
to make this change in a safe way for stable then.

> Regards,
> 
> Roger

Thanks again for reporting this issue
Adrian

-- 

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

Bug#914554: clxclient FTBFS: freetype-config not found

[Mattia Rizzolo]

On Sun, Nov 25, 2018 at 10:51:22AM +, Hugh McMaster wrote:
> clxclient (build-)depends on libxft-dev, which depends on libfreetype6-dev.
> So, it looks like clxclient used the secondary dependency to
> get access to freetype-config.

Even so, it tries to use stuff provided by libfreetype6-dev
directly, so it also should have a direct build-depdency.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#914587: blueman: broken package

[Stephan Lachnit]

Package: blueman
Version: 2.0.6-1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

this package has wrong python dependencies. It should depend on the python3.6
package or python3 (< 3.7), because it doesn't install on latest Debian Sid
(unstable).



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages blueman depends on:
ii  bluez 5.50-1
ii  bluez-obexd   5.50-1
ii  dbus  1.12.10-1
ii  dbus-user-session [default-dbus-session-bus]  1.12.10-1
ii  dbus-x11 [dbus-session-bus]   1.12.10-1
ii  dconf-gsettings-backend [gsettings-backend]   0.30.1-1
pn  gir1.2-appindicator3-0.1  
ii  gir1.2-gdkpixbuf-2.0  2.38.0+dfsg-6
ii  gir1.2-glib-2.0   1.58.0-1
ii  gir1.2-gtk-3.03.24.1-2
ii  gir1.2-notify-0.7 0.7.7-3
ii  gir1.2-pango-1.0  1.42.4-4
ii  gnome-icon-theme  3.12.0-3
ii  libbluetooth3 5.50-1
ii  libc6 2.27-8
ii  libglib2.0-0  2.58.1-2
ii  libpulse-mainloop-glib0   12.2-2
ii  libpython3.6  3.6.7-1
ii  librsvg2-common   2.44.9-1
ii  notification-daemon   3.20.0-3
ii  python3   3.7.1-2
ii  python3-cairo 1.16.2-1+b1
ii  python3-dbus  1.2.8-2+b1
ii  python3-gi3.30.2-1
ii  python3-gi-cairo  3.30.2-1
ii  xfce4-notifyd [notification-daemon]   0.4.2-1

Versions of packages blueman recommends:
ii  policykit-1  0.105-21
ii  pulseaudio-module-bluetooth  12.2-2

blueman suggests no packages.

Bug#914419: debhelper mustn't set pass V to make

[Adrian Bunk]

On Sun, Nov 25, 2018 at 11:58:57AM +, Luca Boccassi wrote:
> On Sun, 25 Nov 2018, 11:30 Niels Thykier  
> > Adrian Bunk:
> > > Package: debhelper
> > > Version: 11.5.2
> > > Severity: serious
> > >
> > >
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apcupsd.html
> > >
> > > ...
> > > dh clean --with autoreconf
> > >dh_auto_clean
> > >   make V=1 -j16 clean
> > > make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
> > > 1find . -depth \
> > >   \( -name  -o -name  -o -name \*.a \) \
> > >   -exec  "  CLEAN" \{\} \; -exec  \{\} \;
> > > /bin/sh: 1: 1find: not found
> > > make[1]: *** [autoconf/targets.mak:98: clean] Error 127
> > >
> > >
> > >
> > https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets.mak/#L98
> > >
> > >
> > > Using V=1 for getting verbose build output is a relatively
> > > recent convention followed by some software.
> > >
> > > It is not something that is safe to use everywhere.
> > >
> >
> > Hi,
> >
> > Adding Luca to this report as it affect a change by Luca.
> >
> > @Luca: What is your take on this?  Should we roll back on this, guard it
> > by a compat level or something else?
> >
> > Thanks,
> > ~Niels
> >
> 
> Hi Niels and Adrian,

Hi Luca,

> Before considering other options, would using VERBOSE=1 instead of V=1
> work? I'm afk until later today so I can't check right now if gmake accepts
> it, iirc it does but I could be confusing it with other tools.

make happily accepts them, but this misses the problem.

None of these options is supported directly by make.

make just passes such options to the package-specific
Makefile that might do something or nothing with them.

> Kind regards,
> Luca Boccassi

cu
Adrian

-- 

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

Bug#914585: mathgl: qtwebengine5-dev is not available on all architectures

[Adrian Bunk]

Source: mathgl
Version: 2.4.2.1-2
Severity: serious
Tags: ftbfs

qtwebengine5-dev is only available on the following architectures:
  amd64 arm64 armhf i386 mipsel

mathgl tries qtwebengine5-dev first with a fallback to libqt5webkit5-dev,
which gives two possible solutions:

1. If using qtwebengine5-dev instead of libqt5webkit5-dev does
   not bring any significant improvements, it would be easiest
   to go back to using libqt5webkit5-dev on all architectures.

OR

2. Use qtwebengine5-dev where available and libqt5webkit5-dev
   everywhere else, by changing the build dependency to
 qtwebengine5-dev [amd64 arm64 armhf i386 mipsel]

Bug#914419: debhelper mustn't set pass V to make

[Luca Boccassi]

On Sun, 25 Nov 2018, 11:30 Niels Thykier  Adrian Bunk:
> > Package: debhelper
> > Version: 11.5.2
> > Severity: serious
> >
> >
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apcupsd.html
> >
> > ...
> > dh clean --with autoreconf
> >dh_auto_clean
> >   make V=1 -j16 clean
> > make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
> > 1find . -depth \
> >   \( -name  -o -name  -o -name \*.a \) \
> >   -exec  "  CLEAN" \{\} \; -exec  \{\} \;
> > /bin/sh: 1: 1find: not found
> > make[1]: *** [autoconf/targets.mak:98: clean] Error 127
> >
> >
> >
> https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets.mak/#L98
> >
> >
> > Using V=1 for getting verbose build output is a relatively
> > recent convention followed by some software.
> >
> > It is not something that is safe to use everywhere.
> >
>
> Hi,
>
> Adding Luca to this report as it affect a change by Luca.
>
> @Luca: What is your take on this?  Should we roll back on this, guard it
> by a compat level or something else?
>
> Thanks,
> ~Niels
>

Hi Niels and Adrian,

Before considering other options, would using VERBOSE=1 instead of V=1
work? I'm afk until later today so I can't check right now if gmake accepts
it, iirc it does but I could be confusing it with other tools.

Kind regards,
Luca Boccassi

>

Bug#914521: marked as done (cdo FTBFS on 32bit: undefined reference to `pstreamInqGRIBinfo(int, int*, float*, long*)')

[Debian Bug Tracking System]

Your message dated Sun, 25 Nov 2018 11:49:25 +
with message-id 
and subject line Bug#914521: fixed in cdo 1.9.6~rc4-2
has caused the Debian Bug report #914521,
regarding cdo FTBFS on 32bit: undefined reference to `pstreamInqGRIBinfo(int, 
int*, float*, long*)'
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.)


-- 
914521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cdo
Version: 1.9.6~rc4-1
Severity: serious
Tags: ftbfs

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

...
/usr/bin/ld: cdo-Gradsdes.o: in function `Gradsdes(void*)':
./src/Gradsdes.cc:1293: undefined reference to `pstreamInqGRIBinfo(int, int*, 
float*, long*)'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:1079: cdo] Error 1
--- End Message ---
--- Begin Message ---
Source: cdo
Source-Version: 1.9.6~rc4-2

We believe that the bug you reported is fixed in the latest version of
cdo, 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.
Alastair McKinstry  (supplier of updated cdo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Nov 2018 11:04:06 +
Source: cdo
Binary: cdo libcdi0 libcdi-dev
Architecture: source amd64
Version: 1.9.6~rc4-2
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 cdo- Climate Data Operators
 libcdi-dev - Development files for the climate data interface library
 libcdi0- Climate Data Interface (cdi) library
Closes: 914521
Changes:
 cdo (1.9.6~rc4-2) unstable; urgency=medium
 .
   * Fix FTBFS on 32-bit systems. Closes: #914521
   * Drop obsolete lintian-overrides
   * Drop redundant "Priority" fields in d/control
   * Check DEB_BUILD_OPTIONS in test
Checksums-Sha1:
 33d121947ec0e5b105093d1932c5725eaf4706a5 2242 cdo_1.9.6~rc4-2.dsc
 6ab30319cdeb574bd6fa652dbde035f89b263e0a 10204 cdo_1.9.6~rc4-2.debian.tar.xz
 e075bb10da50eafe45a2a924a61d5a5193630bfe 27672696 
cdo-dbgsym_1.9.6~rc4-2_amd64.deb
 2db2bf3ae51be838c8e41ef3366f835ea69830b4 14357 cdo_1.9.6~rc4-2_amd64.buildinfo
 f1a6c713102e6a85ca9a7df8cf9a5236e35cb134 1872068 cdo_1.9.6~rc4-2_amd64.deb
 d1070f7eb155dba65a251279a7905b206320b7f0 460588 
libcdi-dev_1.9.6~rc4-2_amd64.deb
 f7391ab786e798b734175a3f21148a40ebf2 1072536 
libcdi0-dbgsym_1.9.6~rc4-2_amd64.deb
 65a361ea6bc7abbb0e0fd2fd865aab9df7bb8a38 381256 libcdi0_1.9.6~rc4-2_amd64.deb
Checksums-Sha256:
 c4c3b8066208f6acd3e6ca05f4e894c4805a32bd51a6023c1dd83963c0529ed9 2242 
cdo_1.9.6~rc4-2.dsc
 718b0754ccfec10624dab5ec7a309b8355b4100f40650acf5d59ff13535d7e1b 10204 
cdo_1.9.6~rc4-2.debian.tar.xz
 2bd08f8f17ecbe660cfeedc321db3c419c3769dd0adbb60da1e6a2af0e2d1e1c 27672696 
cdo-dbgsym_1.9.6~rc4-2_amd64.deb
 14a3fdac9c460e0be628debcdd4ce516a8ba04ab9322230a756caa784925b2fb 14357 
cdo_1.9.6~rc4-2_amd64.buildinfo
 7af42c3e42b360002061a1689009ed40782b0549157ad8422900c6cab6e49948 1872068 
cdo_1.9.6~rc4-2_amd64.deb
 62357513550ea24eacaaa7a81519fed74fa83a4e5bce8ae99c655fae77ad5337 460588 
libcdi-dev_1.9.6~rc4-2_amd64.deb
 baac0a4875989e907fde305f0a7c6906170ffd6ae09754c5877eab053ba4a38c 1072536 
libcdi0-dbgsym_1.9.6~rc4-2_amd64.deb
 c8538579b872061241d89e8513e8c3a9064ec9e1855bc39697ed08214980d9b2 381256 
libcdi0_1.9.6~rc4-2_amd64.deb
Files:
 32c8fb9a0169068f0fd94a286c1acc91 2242 utils optional cdo_1.9.6~rc4-2.dsc
 dc14e5915ad95c691d56892dd59a882d 10204 utils optional 
cdo_1.9.6~rc4-2.debian.tar.xz
 dbcfc6bc6a2ab3353f3ab47912c7073e 27672696 debug optional 
cdo-dbgsym_1.9.6~rc4-2_amd64.deb
 e8bbd966a94d66b871b23efec4f66126 14357 utils optional 
cdo_1.9.6~rc4-2_amd64.buildinfo
 7754f6b997ad4fc3e86dba9ffa901a27 1872068 utils optional 
cdo_1.9.6~rc4-2_amd64.deb
 dad53ece633a3fa59f8415932f30cc17 460588 libdevel optional 
libcdi-dev_1.9.6~rc4-2_amd64.deb
 b0facf366c83abc5aea109ed9baa 1072536 debug optional 
libcdi0-dbgsym_1.9.6~rc4-2_amd64.deb
 33eb3b49233b1f730336a64f080f3a5e 381256 libs optional 
libcdi0_1.9.6~rc4-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGi

Bug#914419: debhelper mustn't set pass V to make

[Niels Thykier]

Adrian Bunk:
> Package: debhelper
> Version: 11.5.2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apcupsd.html
> 
> ...
> dh clean --with autoreconf
>dh_auto_clean
>   make V=1 -j16 clean
> make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
> 1find . -depth \
>   \( -name  -o -name  -o -name \*.a \) \
>   -exec  "  CLEAN" \{\} \; -exec  \{\} \;
> /bin/sh: 1: 1find: not found
> make[1]: *** [autoconf/targets.mak:98: clean] Error 127
> 
> 
> https://sources.debian.org/src/apcupsd/3.14.14-2/autoconf/targets.mak/#L98
> 
> 
> Using V=1 for getting verbose build output is a relatively
> recent convention followed by some software.
> 
> It is not something that is safe to use everywhere.
> 

Hi,

Adding Luca to this report as it affect a change by Luca.

@Luca: What is your take on this?  Should we roll back on this, guard it
by a compat level or something else?

Thanks,
~Niels

Bug#914582: liblingua-en-fathom-perl: Fails to build due to unmet build dependecies

[Hans Joachim Desserud]

Package: liblingua-en-fathom-perl
Version: 1.22-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

When attempting to build this package, installing build dependencies 
fails

because liblingua-en-sentence-perl doesn't seem to exist in Debian.

$ sudo apt build-dep liblingua-en-fathom-perl
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:liblingua-en-fathom-perl : Depends: 
liblingua-en-sentence-perl but it is not installable

E: Unable to correct problems, you have held broken packages.


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 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

--
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#914580: wsjtx: binary-any FTBFS

[Adrian Bunk]

Source: wsjtx
Version: 1.8.0+repack-1
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_installdocs
make[1]: Entering directory '/<>/wsjtx-1.8.0+repack'
# Fix font-awesome from cloudflare
sed -i -e 
's/https:\/\/cdnjs.cloudflare.com\/ajax\/libs\/font-awesome\/4.7.0\/css\/font-awesome.min.css/\/usr\/share\/fonts-font-awesome\/css\/font-awesome.min.css/g'
 \
debian/wsjtx-doc/usr/share/doc/wsjtx/wsjtx-main-1.8.0.html
sed: can't read debian/wsjtx-doc/usr/share/doc/wsjtx/wsjtx-main-1.8.0.html: No 
such file or directory
make[1]: *** [debian/rules:33: override_dh_installdocs] Error 2


This can be reproduced with
  dpkg-buildpackage -B

Bug#912779: [src:mumble] FTBFS with boost1.67

[Adrian Bunk]

Control: forwarded -1 https://github.com/mumble-voip/mumble/issues/3281
Control: fixed -1 1.3.0~2868~g44b9004+dfsg-1

On Wed, Nov 07, 2018 at 07:47:00AM +, Chris Knadle wrote:
> Giovanni Mascellani:
> > Dear Maintainer,
> > 
> > your package fails to build with boost1.67. You can find a build log
> > attached. If you want to attempt the build yourself, an updated version
> > of boost-defaults which brings in boost1.67 dependencies can be found
> > adding this line to your sources.list file:
> > 
> >   deb https://people.debian.org/~gio/reprepro unstable main
> > 
> > This bug has severity whishlist for the moment, but it will raised to RC
> > as soon as version 1.67 of Boost is promoted to default.
> > 
> > I have to say I do not completely understand why the package built fine
> > with previous version of boost (1.62): it seems to me that the problem
> > the attached patch fixes (the use of std::abs as a templated name, see
> > the path description for more details) should not depend at all from
> > boost. However, at least on my computer, the package builds with
> > boost1.62, fails with boost1.67 and build with boost1.67 and this patch.
> > 
> > Please consider applying the attached patch as soon as boost1.67 is made
> > default in order to avoid FTBFS.
> > 
> > Thanks and all the best, Giovanni.
> 
> Hello, Giovanni.
> 
> Thank you very much for your detailed bug report that includes build logs and 
> a
> patch.  :)
> 
> I reviewed the build logs and the patch.  I took some time to understand what
> static_cast does in the patch, because I think I haven't seen that 
> before.
> 
>https://stackoverflow.com/questions/28002/regular-cast-vs-static-cast-vs-
> dynamic-cast
>https://en.cppreference.com/w/cpp/language/static_cast
> 
> At least initially the patch looks right to me.  I'll include this patch in 
> the
> next upload.  Thanks.

The upstream fix for this bug is
https://github.com/mumble-voip/mumble/commit/ea861fe86743c8402bbad77d8d1dd9de8dce447e

>-- Chris

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

Processed: Re: Bug#912779: [src:mumble] FTBFS with boost1.67

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/mumble-voip/mumble/issues/3281
Bug #912779 [src:mumble] [src:mumble] FTBFS with boost1.67
Set Bug forwarded-to-address to 
'https://github.com/mumble-voip/mumble/issues/3281'.
> fixed -1 1.3.0~2868~g44b9004+dfsg-1
Bug #912779 [src:mumble] [src:mumble] FTBFS with boost1.67
Marked as fixed in versions mumble/1.3.0~2868~g44b9004+dfsg-1.

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

Processed: closing 914550

[Debian Bug Tracking System]

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

> close 914550
Bug #914550 [borgbackup] borgbackup needs to be rebuilt for python 3.7
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#914550: borgbackup needs to be rebuilt for python 3.7

[Adrian Bunk]

On Sat, Nov 24, 2018 at 08:21:21PM +0100, Albert Dengg wrote:
> Package: borgbackup
> Version: 1.1.7-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> since the update to python 3.7 in debian unstable, borg is uninstable.
> 
> a simple rebuild of the package seems to be enough to get a working
> package.

Thanks for your report.

The rebuild scheduling will be handled in #913069.

> regards,
> albert dengg

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