Bug#924010: wmbiff: Built without TLS support

[Yavor Doganov]

On Fri, Mar 08, 2019 at 07:21:22PM +0100, Andreas Metzler wrote:
> On 2019-03-08 Yavor Doganov  wrote:
> > | checking for gzopen in -lz... no
> > | GNUTLS support requires libz.a and libgdbm.a
> 
> Actually ./configure seems to wrong, GNUTLS suppport does not require
> libz.a and libgdbm.a (anymore).

Thanks; here is a better patch.
>From da55170615c095d2076a839d335f1071ceb8f906 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Sat, 9 Mar 2019 08:30:55 +0200
Subject: [PATCH] debian/patches: (gnutls-detection.patch) Detect GNUTLS
 unconditionally.

---
 debian/patches/gnutls-detection.patch | 40 +++
 debian/patches/series |  1 +
 2 files changed, 41 insertions(+)
 create mode 100644 debian/patches/gnutls-detection.patch
 create mode 100644 debian/patches/series

diff --git a/debian/patches/gnutls-detection.patch b/debian/patches/gnutls-detection.patch
new file mode 100644
index 000..acb58bb
--- /dev/null
+++ b/debian/patches/gnutls-detection.patch
@@ -0,0 +1,40 @@
+Description: Detect GNUTLS unconditionally.
+Author: Yavor Doganov 
+Debian-Bug: https://bugs.debian.org/924010
+Forwarded: no
+Last-Update: 2019-03-09
+---
+
+--- wmbiff.orig/configure.ac
 wmbiff/configure.ac
+@@ -58,11 +58,7 @@
+ AC_CHECK_LIB(resolv, herror)
+ 
+ dnl Pre-gnutls.
+-gnutls="ok"
+ gcrypt="ok"
+-AC_CHECK_LIB(z, gzopen, [], [gnutls="nope"]) dnl GNUTLS seems to need libz; fail here if it's missing.
+-dnl perhaps not required anymore:
+-dnl AC_CHECK_LIB(gdbm, dbminit, [], [gnutls="nope"]) dnl GNUTLS seems to need libgdbm; fail here if it's missing.
+ 
+ dnl Parameter is minimum version
+ dnl TODO: fix so that GCRYPT is tested only if GNUTLS fails; the dependence
+@@ -76,17 +72,13 @@
+ 
+ 
+ GNUTLS_MAN_STATUS="This copy of WMBiff was not compiled with GNUTLS."
+-if test "$gnutls" = "ok"; then
+- PKG_CHECK_MODULES([LIBGNUTLS], [gnutls > 2.2.0], [LIBS="$LIBS $LIBGNUTLS_LIBS"
++PKG_CHECK_MODULES([LIBGNUTLS], [gnutls > 2.2.0], [LIBS="$LIBS $LIBGNUTLS_LIBS"
+   CFLAGS="$CFLAGS $LIBGNUTLS_CFLAGS"
+  CPPFLAGS="$CPPFLAGS $LIBGNUTLS_CFLAGS"
+  GNUTLS_COMMON_O="gnutls-common.o"
+  GNUTLS_MAN_STATUS="This copy of WMBiff was compiled with GNUTLS."
+  AC_CHECK_HEADERS(gnutls/gnutls.h) ],
+  [ echo GNUTLS can be found at ftp://gnutls.hellug.gr/pub/gnutls ])
+-else
+- AC_MSG_RESULT(GNUTLS support requires libz.a and libgdbm.a, so will be disabled)
+-fi
+ 
+ GCRYPT_MAN_STATUS="This copy of WMBiff was not compiled with gcrypt."
+ if test "$gcrypt" = "ok"; then
diff --git a/debian/patches/series b/debian/patches/series
new file mode 100644
index 000..99fe75a
--- /dev/null
+++ b/debian/patches/series
@@ -0,0 +1 @@
+gnutls-detection.patch
-- 
2.20.1

Bug#922390: marked as done (hydroffice.bag: FTBFS (Could not import extension sphinx.ext.pngmath))

[Debian Bug Tracking System]

Your message dated Sat, 09 Mar 2019 06:34:08 +
with message-id 
and subject line Bug#922390: fixed in hydroffice.bag 0.2.15-2
has caused the Debian Bug report #922390,
regarding hydroffice.bag: FTBFS (Could not import extension sphinx.ext.pngmath)
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.)


-- 
922390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hydroffice.bag
Version: 0.2.15-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice
copying hydroffice/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/uncertainty.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/helper.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/base.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/elevation.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/meta.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/bbox.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/tracklist.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
copying hydroffice/bag/bag.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_tracklist.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_bbox.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_elevation.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/__init__.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_validate.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_metadata.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
copying hydroffice/bag/tools/bag_uncertainty.py -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/tools
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/favicon.png -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/hyo_button.png -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/BAG.ico -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
copying hydroffice/bag/media/BAG.icns -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/media
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/bagCodelists.xml -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/extension.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
copying hydroffice/bag/iso19139/bag/bag.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/bag
creating 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/gcoBase.xsd -> 
/<>/.pybuild/cpython2_2.7_hydroffice.bag/build/hydroffice/bag/iso19139/gco
copying hydroffice/bag/iso19139/gco/basicTypes.xsd -> 

Bug#921738: Not in the README?

[Jason Lingohr]

Thanks for the instructions on how to get this to work, but why is this 
not in the README?!?

Bug#924061: ceph-osd: ceph-volume@.service missing

[Bernd Zeimetz]

Package: ceph-osd
Version: 12.2.11+dfsg1-2
Severity: grave

Hi,

unfortunately the ceph-volume@.service systemd template is missing,
which basically breaks the activation of OSDs.

Sounds like
http://tracker.ceph.com/issues/21011

As this basically breaks the usage of bluestore volumes, I think grave
is the appropriate severity, especially as - looking at the ceph bug
tracker - this might have been working before.

Thanks for fixing,

Bernd


-- 
 Bernd ZeimetzDebian GNU/Linux Developer
 http://bzed.dehttp://www.debian.org
 GPG Fingerprint: ECA1 E3F2 8E11 2432 D485  DD95 EB36 171A 6FF9 435F

Bug#923889: google-compute-image-packages - DoS via serial console write

[Ross Vandegrift]

On Fri, Mar 08, 2019 at 10:59:33AM +0100, Bastian Blank wrote:
> In normal operation, the rate limit of journald might make sure it does
> not come to really blocking.

Ahh, that would do it, thanks.

> What happens for use cases where you need to disable this rate limit?
> Mail servers which Postfix, which exclusively uses syslog that is
> redirected to the journal, need this, or they will loose logs.
> 
> On Azure we tried the same for a short time period.  It got quiet messy
> and also triggered bugs in the platform.

For sure - I wasn't defending the change, just surprised when I couldn't
reproduce the problem.

> I assume the initial goal was to get the log output of the provisioning
> daemons on the serial console.  This goal was also mentioned in the
> formerly shipped rsyslog config snippet.
>
> Forwarding all log traffic there completely destroys that ability, as it
> will be drowned by irrelevant log traffic.  Also the log buffer is
> limited in size.

Yep, agreed.

Ross

Bug#923467: marked as done (libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmath))

[Debian Bug Tracking System]

Your message dated Fri, 08 Mar 2019 21:04:24 +
with message-id 
and subject line Bug#923467: fixed in libvigraimpex 
1.10.0+git20160211.167be93+dfsg1-2
has caused the Debian Bug report #923467,
regarding libvigraimpex: FTBFS (Could not import extension sphinx.ext.pngmath)
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.)


-- 
923467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
make: Nothing to be done for 'build-indep'.
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
/usr/bin/make -f debian/rules doc/vigra/build-stamp
make[1]: Entering directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1'
mkdir -p obj/
cd obj/ && cmake .. -DCMAKE_INSTALL_PREFIX=/usr 
-DLIB_SUFFIX="/x86_64-linux-gnu/" -DCMAKE_VERBOSE_MAKEFILE=ON -DWITH_OPENEXR=ON 
-DCMAKE_C_FLAGS_RELEASE="-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2" -DCMAKE_CXX_FLAGS_RELEASE="-g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2" -DCMAKE_SHARED_LINKER_FLAGS_RELEASE="-Wl,-z,relro 
-Wl,--as-needed -Wl,-z,now"  -DPYTHON_EXECUTABLE=/usr/bin/python 
-DWITH_VIGRANUMPY=0
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]

/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1VolumeExportInfo.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1HDF5Handle.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/ErrorReporting.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__StandardImageTypes.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/NumericPromotionTraits.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/group__NonLinearDiffusion.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1SIFImportInfo-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1GaborFilterFamily-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/classvigra_1_1acc_1_1Central_3_01PowerSum_3_012_01_4_01_4-members.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/Tutorial.html
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/PromoteTraits.html
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_directory 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/documents 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_if_different 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../LICENSE.txt
 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/LICENSE.txt
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/docsrc
 && /usr/bin/cmake -E copy_if_different 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/docsrc/../src/matlab/doc/tutorial_reference.pdf
 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/doc/vigra/documents/tutorial_reference.pdf
make[5]: Leaving directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
[100%] Built target doc_cpp
/usr/bin/make -f vigranumpy/docsrc/CMakeFiles/doc_python.dir/build.make 
vigranumpy/docsrc/CMakeFiles/doc_python.dir/depend
make[5]: Entering directory 
'/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7'
cd /<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 
&& /usr/bin/cmake -E cmake_depends "Unix Makefiles" 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/vigranumpy/docsrc 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg1/obj.python2.7/vigranumpy/docsrc
 

Processed: tagging 924044

[Debian Bug Tracking System]

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

> tags 924044 + fixed-upstream
Bug #924044 [smcroute] init script does not stop the daemon
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#923609: proposed solution

[Niko Tyni]

On Fri, Mar 08, 2019 at 02:39:53PM +, Dmitry Bogatov wrote:
 
> I believe this patch would somewhat solve issue. Dear submitter, can you
> please apply this patch, build package and check, that `gdbm_load-nolfs'
> binary from created bin:gdbmtool does sensible thing?

Thanks. It doesn't quite work as-is, because 'future=+all' in
DEB_BUILD_MAINT_OPTIONS still pulls the LFS flags in the build. But if
I take that away, it works at least for my trivial databases (both GDBM
and NDBM). I'll try to test a bit more later.

It would make sense to limit this to 32-bit architectures as I believe the
64-bit architectures always have LFS support no matter the build flags.

Shipping these -nolfs binaries and including instructions for upgrading
databases in the Buster release notes would be an acceptable fix for
this issue IMO.

> By the way, can I somehow help to make autopkgtests on !amd64 happen?

I don't know; the debian-ci@ldo list is probably the best contact for that.

Thanks again,
-- 
Niko

Bug#924047: FTBFS: package don't build successful after new GCC version

[Carsten Schoenert]

Package: src:systemc
Version: 2.3.3-1
Severity: grave

Hello Ahmed,

the systemc package is currently failing to build from source basically
related due a newer GCC version and changed symbols introduced by the
newer GCC.

I've fixed the reason of the FTBFS by modifying and adopting the
symbols file so the package is building again on all RC platforms. I've
pushed the adopted symbols file to Salsa after I've tested the builds.

If you can also have a look on a update of Standards-Version to 4.3.0 and
prepare a new changelog entry I can offer a sponsored upload.

I see no problem with a later unblock request so the updated package can
go into the Buster release.

Regards
Carsten

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

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

Processed: Re: Bug#921577: smcroute autopkgtests fail consistently

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #921577 [src:smcroute] smcroute autopkgtests fail consistently
Severity set to 'serious' from 'normal'

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

Bug#924044: init script does not stop the daemon

[Micha Lenk]

Package: smcroute
Version: 2.4.2-3
Severity: serious
Tags: patch upstream
Control: forwarded -1 https://github.com/troglobit/smcroute/pull/108

I am filing this bug on behalf of the current maintainer and upstream author of
smcroute, Joachim Nilsson, to create the necessary visibility for an issue
considered worth to be fixed for the Debian buster release. It was initially
filed by Hajo Noerenberg on upstream's Github repository as pull request 108.

> I'm using SMCRoute v2.4.2 (debian testing).
>
> The init script does not stop the daemon, an error is reported instead:
>
> # /etc/init.d/smcroute stop
> Stopping static multicast router daemon: smcrouted /usr/sbin/smcrouted: 
> invalid option -- 'k'
>
> I think one should use smcroutectl to stop the daemon.

The pull request is merged already, so the change is already part of the
upstream release 2.4.4.

Micha
commit 6f4e2c1ce8e0f6821e5254000ed43a4fd7744782
Author: hn 
Date:   Mon Jan 28 09:56:33 2019 +0100

fix init script 'stop' command

diff --git a/smcroute.init b/smcroute.init
old mode 100644
new mode 100755
index 00411b8..d0c7752
--- a/smcroute.init
+++ b/smcroute.init
@@ -18,6 +18,7 @@
 
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
 DAEMON=/usr/sbin/smcrouted
+DAEMONCTL=/usr/sbin/smcroutectl
 DAEMON_OPTS=
 NAME=smcrouted
 DESC="static multicast router daemon"
@@ -50,7 +51,7 @@ stop() {
local error
local result
log_begin_msg "Stopping $DESC: $NAME"
-   error=$($DAEMON -k 2>&1)
+   error=$($DAEMONCTL kill 2>&1)
result=$?
log_progress_msg ${error#ERRO: }
log_end_msg $result

Processed: init script does not stop the daemon

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/troglobit/smcroute/pull/108
Bug #924044 [smcroute] init script does not stop the daemon
Set Bug forwarded-to-address to 
'https://github.com/troglobit/smcroute/pull/108'.

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

Bug#924042: tomb: Multiple package relations for optionally used tools are missing (steghide, dcfldd, gettext-base, qrencode, unoconv, lsof, swish-e)

[Axel Beckert]

Package: tomb
Version: 2.5+dfsg1-2
Severity: serious

tomb's exhume subcommand calls steghide:

~ → tomb exhume /tmp/example.jpg
tomb [E] Steghide not installed: cannot exhume keys from images.
~ → dgrep steghide tomb
/usr/bin/tomb:  _deps=(gettext dcfldd shred steghide)
/usr/bin/tomb:  # Check for steghide
/usr/bin/tomb:  command -v steghide 1>/dev/null 2>/dev/null || STEGHIDE=0
/usr/bin/tomb:# Requires steghide(1) to be installed
/usr/bin/tomb:  | steghide embed --embedfile - --coverfile ${imagefile} 
\
/usr/bin/tomb:  _warning "Encoding error: steghide reports problems."
/usr/bin/tomb:  TOMBKEY=$(steghide extract -sf $imagefile -p $tombpass 
-xf -)
/usr/bin/tomb:  steghide extract -sf $imagefile -p ${tombpass} -xf $destkey

But steghide is neither in a Recommends or Suggests header.

And when looking at that grep output above, it becomes clear that there
are even more optional dependencies missing. Citing from tomb's source
code:

_list_optional_tools() {
typeset -a _deps
_deps=(gettext dcfldd shred steghide)
_deps+=(resize2fs tomb-kdb-pbkdf2 qrencode swish-e unoconv lsof)
for d in $_deps; do
_print "`which $d`"
done
return 0
}

So the following packages are missing in tomb's package relations. I
leave the package maintainers to decide, which of them go into Suggests
and which into Recommends:

* gettext-base: /usr/bin/gettext
* dcfldd: /usr/bin/dcfldd
* steghide: /usr/bin/steghide
* qrencode: /usr/bin/qrencode
* unoconv: /usr/bin/unoconv
* lsof: /usr/bin/lsof
* swish-e: /usr/bin/swish-e

Will file a separate bug report for the missing tomb-kdb-pbkdf2 binary.

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

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages tomb depends on:
ii  cryptsetup-bin  2:2.1.0-2
ii  e2fsprogs   1.44.6-1
ii  gnupg   2.2.13-1
ii  pinentry-curses [pinentry]  1.1.0-1+b1
ii  pinentry-fltk [pinentry]1.1.0-1+b1
ii  pinentry-gnome3 [pinentry]  1.1.0-1+b1
ii  pinentry-gtk2 [pinentry]1.1.0-1+b1
ii  pinentry-qt [pinentry]  1.1.0-1+b1
ii  pinentry-tty [pinentry] 1.1.0-1+b1
ii  sudo1.8.27-1
ii  zsh 5.7.1-1

tomb recommends no packages.

tomb suggests no packages.

-- no debconf information

Bug#924010: wmbiff: Built without TLS support

[Andreas Metzler]

On 2019-03-08 Yavor Doganov  wrote:
> Package: wmbiff
> Version: 0.4.33-1
> Severity: serious
> Tags: patch

> IMHO any sane mail checker should support TLS:

> $ wmbiff
> This copy of wmbiff was not compiled with gnutls;
> imaps is unavailable.  Exiting to protect your
> passwords and privacy.

> Looking at the build log:

> | checking for gzopen in -lz... no
> | GNUTLS support requires libz.a and libgdbm.a

> The attached trivial patch fixes it.
[...]

Actually ./configure seems to wrong, GNUTLS suppport does not require
libz.a and libgdbm.a (anymore).

cu Andreas

Bug#849308: state of wireguard mainline inclusion?

[Daniel Kahn Gillmor]

Hi Mika--

On Thu 2019-03-07 16:16:40 +0100, Michael Prokop wrote:
> So sadly wireguard didn't make it into buster. :(

yep, frustrating.  but that was by design -- it isn't clear to me that
the ecosystem will be happy with having a wide distribution of an
outdated (2019) version running in 2021 :/, depending on what happens
with the upstream inclusion work (which i can't currently predict).

> Are there any plans for providing backports for stretch and/or buster?

I do plan for putting wireguard into buster-backports, since i expect
the upstream inclusion issues to be resolved one way or another by the
time of bullseye release.  If anyone wants to help out by adding it to
stretch-backports-sloppy, i would welcome that.

  --dkg


signature.asc
Description: PGP signature

Bug#923957: marked as done (/lib/runit/run_sysv_scripts shouldn't use 'sh -e')

[Debian Bug Tracking System]

Your message dated Fri, 08 Mar 2019 16:19:54 +
with message-id 
and subject line Bug#923957: fixed in runit 2.1.2-24
has caused the Debian Bug report #923957,
regarding /lib/runit/run_sysv_scripts shouldn't use 'sh -e'
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.)


-- 
923957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: runit-init
Version: 2.1.2-22
Severity: critical

Hi,

The supplied "/etc/runit/1" calls "/lib/runit/run_sysv_scripts /etc/rcS.d"
during boot.

/lib/runit/run_sysv_scripts runs under "sh -eu", which has the effect that
if any initscript exits unsuccesfully, all subsequent scripts are skipped.

This can lead to, for example, the "networking" initscript not being
started, which then results in no connectivity for the box and thus no way
to log in remotely. (This is my justification for the 'critical' severity:
"breaks the entire system".)

I think runit-init should do what /etc/init.d/rc does: log failures and
continue.

Thanks,

András

-- 
  It's not enough to have no opinion. You must also be unable to express it.
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-24

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated runit 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: Fri, 08 Mar 2019 15:29:32 +
Source: runit
Architecture: source
Version: 2.1.2-24
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Closes: 914788 916697 923957
Changes:
 runit (2.1.2-24) unstable; urgency=medium
 .
   * Remove `set -e' from `run_sysv_scripts' to ensure behaviour
 similar to `/etc/init.d/rc' -- failure of one script in `/etc/rcS.d'
 does not prevent other from running. (Closes: #923957)
 .
 runit (2.1.2-23) experimental; urgency=medium
 .
   * Disable getty-tty services if tty device is missing (Closes: #914788)
   * Create specialized interpreter for runscripts (Closes: #916697)
Checksums-Sha1:
 6703b97c77b5af7d9c84fbf45f48df92aca7e393 2152 runit_2.1.2-24.dsc
 0be4e561de94e560bcbecca211fce828a3d52b95 27972 runit_2.1.2-24.debian.tar.xz
 b4c557df8f778fb9347d0c8f5ade0acfa34cb2c3 5289 runit_2.1.2-24_source.buildinfo
Checksums-Sha256:
 f15d397ec2564bba3a62638756971f5859946f79b7b53f8cbd18b5faf40cc8a9 2152 
runit_2.1.2-24.dsc
 c8e362df7d23331b33b92a8a2a285b0a724d4c5b62fdbe3787e288f5723f3b0d 27972 
runit_2.1.2-24.debian.tar.xz
 568abe538f688acb4f14f2662ecce473779b7d0ec3b45f4a15ca33810daa8668 5289 
runit_2.1.2-24_source.buildinfo
Files:
 90fbf9033bbcf9449b76f369bba993ea 2152 admin optional runit_2.1.2-24.dsc
 0702035f9059b2b982fe0b9d8d0080bb 27972 admin optional 
runit_2.1.2-24.debian.tar.xz
 d4505f836bd73818089392797ad54764 5289 admin optional 
runit_2.1.2-24_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlyCkMcTHGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5pSxD/4w5qCd/ZViHdE+R7/yk8zoSiFWD297
acYLHfuMt5CdvMQTUfMgWj+GN6f0sxWXA91rr7jXQdpqS3od4wfIC0Axf031eWon
jEpADwHX31FiSq5Gc6khHqJ/8KkWz/05pQZllbN+AmL5wtNsIJQmaoXf8WdcW+K8
PMM406mb8FEbOKjM5pFjqWiJBPzmtLOLW0VBpZSUG3VLqv0tE6AVotzziCingB/J
cuVzU9yEIrfyeV6QprpQEWJzYza6TASmQqrv0miX4OFZAz7SVfavdOUUDt3UeE2g
R9nu9NgDMb6Q7DGbh5aBzqSy2DIHM+Jz+/TMdgk+n3KPATa+6YuKg0tpKvc+xAuT
+BDNwBtYIfjQ0Y+uWxkcD0OuK2iLoeJQOgz4G+SOMk9umfsT2RQN3ABCzKDItRkR
j3mGI0IOPwzd+Ud1lzrURzq6tbJamByYrEcD04Ye2SLkJ5vfEAEyZYVerjDloSKG
dF++CoH3y5L3QytOVtMyvVwpTZTpFo7Qq1SsyzYVze8qOYQ2KkWgBodU0tdsKNPQ
WIgZLuCHVIYGhwIpslmg1Mo7L3J7qjtVyhCsh6HTW1hxPrthE5E3T0cLuFSvy7Rp
UkQHAAFC7R0NE8BpVx+qAOwsrAwKnUL08NYpx8hK/Dl+GFsZHnw1TmBfDfyN8nU4
xW8kjz4w+NkTUw==
=eXos
-END PGP SIGNATURE End Message ---

Bug#917408: marked as done (jupyter-notebook: CVE-2018-19352)

[Debian Bug Tracking System]

Your message dated Fri, 8 Mar 2019 16:08:12 +0100
with message-id <18ce3d64-aead-fefc-7040-9bbc44970...@debian.org>
and subject line Re: jupyter-notebook: CVE-2018-19352
has caused the Debian Bug report #917408,
regarding jupyter-notebook: CVE-2018-19352
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.)


-- 
917408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-notebook
Version: 5.4.1-1
Severity: important
Tags: patch security upstream

Hi,

The following vulnerability was published for jupyter-notebook.

CVE-2018-19352[0]:
| Jupyter Notebook before 5.7.2 allows XSS via a crafted directory name
| because notebook/static/tree/js/notebooklist.js handles certain URLs
| unsafely.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-19352
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19352
[1] 
https://github.com/jupyter/notebook/commit/288b73e1edbf527740e273fcc69b889460871648

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
This was fixed by updating to jupyter-notebook 5.7.4.

Best,

Tobias--- End Message ---

Processed: found 923930 in 7.5.0+dfsg-2.1, tagging 899010, tagging 899007

[Debian Bug Tracking System]

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

> found 923930 7.5.0+dfsg-2.1
Bug #923930 [src:heimdal] FTBFS: FAIL test_chain (exit status: 1)
Marked as found in versions heimdal/7.5.0+dfsg-2.1.
> tags 899010 + sid buster
Bug #899010 [python-ckanclient] python-ckanclient: Depends on unmaintained 
python-gdata
Added tag(s) buster and sid.
> tags 899007 + sid buster
Bug #899007 [bauble] bauble: Depends on unmaintained python-gdata
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Bug#924032: mpqc3: FTBFS: Could NOT find MPI

[Andreas Beckmann]

Source: mpqc3
Version: 0.0~git20170114-4.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

mpqc3 FTBFS in sid and buster with

[...]
-- Detecting Fortran/C Interface
-- Detecting Fortran/C Interface - Found GLOBAL and MODULE mangling
-- Verifying Fortran/CXX Compiler Compatibility
-- Verifying Fortran/CXX Compiler Compatibility - Success
-- Found PAPI: /usr/lib/x86_64-linux-gnu/libpapi.a  
-- Found MPI_C: /usr/lib/x86_64-linux-gnu/libmpich.so (found version "3.1") 
-- Could NOT find MPI_CXX (missing: MPI_CXX_WORKS) 
-- Found MPI_Fortran: /usr/lib/x86_64-linux-gnu/libmpichfort.so (found version 
"3.1") 
-- Could NOT find MPI (missing: MPI_CXX_FOUND) (found version "3.1")
CMake Error at external/MPI:36 (message):
  MPI not found
Call Stack (most recent call first):
  external/External:8 (include)
  CMakeLists.txt:330 (include)


-- Configuring incomplete, errors occurred!


Andreas

BTW, why does it link statically against papi?


mpqc3.buster.build.gz
Description: application/gzip

Bug#923609: proposed solution

[Dmitry Bogatov]

I believe this patch would somewhat solve issue. Dear submitter, can you
please apply this patch, build package and check, that `gdbm_load-nolfs'
binary from created bin:gdbmtool does sensible thing?

By the way, can I somehow help to make autopkgtests on !amd64 happen?

From dbbe906795dd977ed16cccaa7b0385ce8654c8a5 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Thu, 7 Mar 2019 20:19:11 +
Subject: [PATCH] Provide version with LFS support disabled

---
 debian/rules | 4 
 1 file changed, 4 insertions(+)

diff --git a/debian/rules b/debian/rules
index fce1572..03b6242 100755
--- a/debian/rules
+++ b/debian/rules
@@ -39,17 +39,21 @@ ifeq ($(HAVE_DIETLIBC),yes)
CC='diet gcc' CPPFLAGS='-UHAVE_MMAP'
 endif
dh_auto_configure -B glibc-build -- --enable-libgdbm-compat
+   dh_auto_configure -B glibc-nolfs-build -- \
+   CFLAGS='-static' --program-suffix=-nolfs --disable-largefile
 
 override_dh_auto_build:
 ifeq ($(HAVE_DIETLIBC),yes)
dh_auto_build -B diet-build
 endif
dh_auto_build -B glibc-build
+   dh_auto_build -B glibc-nolfs-build
 
 override_dh_auto_install:
 ifeq ($(HAVE_DIETLIBC),yes)
dh_auto_install -B diet-build
 endif
+   dh_auto_install -B glibc-nolfs-build
dh_auto_install -B glibc-build
 
 ifeq ($(HAVE_DIETLIBC),yes)
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --


pgp49H8gGpqHE.pgp
Description: PGP signature

Bug#923905: libdbd-pg-perl: FTBFS (failing tests)

[gregor herrmann]

On Fri, 08 Mar 2019 15:27:25 +0100, Christoph Berg wrote:

> Re: gregor herrmann 2019-03-08 <20190308142308.gu...@jadzia.comodo.priv.at>
> > I'm happy to upload, just wanted to wait in case you're working on
> > the package as well and/or want to take a look.
> Please go ahead, I was just lurking on #postgresql-lounge where the
> issue was discussed as well.

Thanks; uploaded.


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: Beatles


signature.asc
Description: Digital Signature

Bug#923905: libdbd-pg-perl: FTBFS (failing tests)

[Christoph Berg]

Re: gregor herrmann 2019-03-08 <20190308142308.gu...@jadzia.comodo.priv.at>
> Control: tag -1 + fixed-upstream patch pending
> 
> On Fri, 08 Mar 2019 15:10:48 +0100, Christoph Berg wrote:
> 
> > Upstream fix: 
> > https://github.com/bucardo/dbdpg/commit/2b60151aea6f03ac7e846aae0d21e7f335cad99c
> 
> Ha, I just found the same commit and I've added it as a patch to the
> git repo of our package.
> 
> I'm happy to upload, just wanted to wait in case you're working on
> the package as well and/or want to take a look.

Please go ahead, I was just lurking on #postgresql-lounge where the
issue was discussed as well.

Thanks,
Christoph

Bug#923905: libdbd-pg-perl: FTBFS (failing tests)

[gregor herrmann]

Control: tag -1 + fixed-upstream patch pending

On Fri, 08 Mar 2019 15:10:48 +0100, Christoph Berg wrote:

> Upstream fix: 
> https://github.com/bucardo/dbdpg/commit/2b60151aea6f03ac7e846aae0d21e7f335cad99c

Ha, I just found the same commit and I've added it as a patch to the
git repo of our package.

I'm happy to upload, just wanted to wait in case you're working on
the package as well and/or want to take a look.


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: James Taylor: Mexico


signature.asc
Description: Digital Signature

Bug#923905: Bug #923905 in libdbd-pg-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #923905 in libdbd-pg-perl 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/perl-team/modules/packages/libdbd-pg-perl/commit/a0bd994a0e726e28051d5ca215e1ae53195d0d90


Add patch from upstream Git to fix test failure with

client_min_messages=FATAL.

Closes: #923905


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923905

Processed: Bug #923905 in libdbd-pg-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923905 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS (failing tests)
Ignoring request to alter tags of bug #923905 to the same tags previously set

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

Processed: Re: Bug#923905: libdbd-pg-perl: FTBFS (failing tests)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + fixed-upstream patch pending
Bug #923905 [src:libdbd-pg-perl] libdbd-pg-perl: FTBFS (failing tests)
Added tag(s) fixed-upstream, pending, and patch.

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

Bug#923905: libdbd-pg-perl: FTBFS (failing tests)

[Christoph Berg]

Upstream fix: 
https://github.com/bucardo/dbdpg/commit/2b60151aea6f03ac7e846aae0d21e7f335cad99c

Christoph

Bug#923904: marked as done (libcec: FTBFS (dh_makeshlibs fails))

[Debian Bug Tracking System]

Your message dated Fri, 08 Mar 2019 13:49:21 +
with message-id 
and subject line Bug#923904: fixed in libcec 4.0.4+dfsg1-2
has caused the Debian Bug report #923904,
regarding libcec: FTBFS (dh_makeshlibs 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.)


-- 
923904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcec
Version: 4.0.4+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh  build-arch --with python2
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/libcec-4.0.4+dfsg1'
ln -s /usr/include/cec-platform include/platform && \
dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu \
-DHAVE_EXYNOS_API=1 \
-DHAVE_AOCEC_API=1
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DCMAKE_BUILD_TYPE=Release -DBUILD_SHARED_LIBS=1 
-DCMAKE_INSTALL_LIBDIR=/usr/lib/x86_64-linux-gnu -DHAVE_EXYNOS_API=1 
-DHAVE_AOCEC_API=1 ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works

[... snipped ...]

  
(optional=templinst)_ZN10P8PLATFORM12SyncedBufferIPN3CEC13CCallbackWrapEED0Ev@Base
 3.1.0
  
(optional=templinst)_ZN10P8PLATFORM12SyncedBufferIPN3CEC13CCallbackWrapEED1Ev@Base
 3.1.0
  
(optional=templinst)_ZN10P8PLATFORM12SyncedBufferIPN3CEC13CCallbackWrapEED2Ev@Base
 3.1.0
@@ -391,8 +391,8 @@
  _ZN3CEC13CCECTypeUtils8ToStringENS_10cec_opcodeE@Base 2.1.4
  _ZN3CEC13CCECTypeUtils8ToStringENS_19cec_logical_addressE@Base 2.1.4
  _ZN3CEC13CCECTypeUtils8ToStringENS_21cec_user_control_codeE@Base 3.0.1
- _ZN3CEC13CCallbackWrapD1Ev@Base 4.0.3+dfsg1-1~
- _ZN3CEC13CCallbackWrapD2Ev@Base 4.0.3+dfsg1-1~
+#MISSING: 4.0.4+dfsg1-1# _ZN3CEC13CCallbackWrapD1Ev@Base 4.0.3+dfsg1-1~
+#MISSING: 4.0.4+dfsg1-1# _ZN3CEC13CCallbackWrapD2Ev@Base 4.0.3+dfsg1-1~
  _ZN3CEC15CAdapterFactory11GetInstanceEPKct@Base 2.1.4
  _ZN3CEC15CAdapterFactory12FindAdaptersEPNS_11cec_adapterEhPKc@Base 2.1.4
  
_ZN3CEC15CAdapterFactory14DetectAdaptersEPNS_22cec_adapter_descriptorEhPKc@Base 
2.1.4
@@ -1011,7 +1011,8 @@
  _ZNK3CEC7CLibCEC18GetAdapterVendorIdEv@Base 2.1.4
  _ZNK3CEC7CLibCEC19GetAdapterProductIdEv@Base 2.1.4
  _ZNKSt5ctypeIcE8do_widenEc@Base 4.0.2
- 
(optional=templinst|subst)_ZNSt11_Deque_baseIN3CEC11cec_commandESaIS1_EE17_M_initialize_mapE{size_t}@Base
 4.0.3+dfsg1-1~
+ _ZNSt11_Deque_baseIN3CEC11cec_commandESaIS1_EE17_M_initialize_mapEm@Base 
4.0.4+dfsg1-1
+#MISSING: 4.0.4+dfsg1-1# 
(optional=templinst|subst)_ZNSt11_Deque_baseIN3CEC11cec_commandESaIS1_EE17_M_initialize_mapE{size_t}@Base
 4.0.3+dfsg1-1~
  (optional=templinst|arch=armel 
riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base
 3.1.0
  (optional=templinst|arch=!armel 
!riscv64)_ZNSt15_Sp_counted_ptrIDnLN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 3.0.1
  (optional=templinst|arch=armel 
riscv64)_ZNSt15_Sp_counted_ptrIPN3CEC10CCECClientELN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base
 3.1.0
@@ -1053,14 +1054,15 @@
  
(optional=templinst)_ZNSt8_Rb_treeIN3CEC10cec_opcodeESt4pairIKS1_St6vectorINS0_11cec_commandESaIS5_EEESt10_Select1stIS8_ESt4lessIS1_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 2.1.4
  
(optional=templinst)_ZNSt8_Rb_treeIN3CEC19cec_logical_addressESt4pairIKS1_PNS0_13CCECBusDeviceEESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE17_M_emplace_uniqueIJS2_IS1_S5_S2_ISt17_Rb_tree_iteratorIS6_EbEDpOT_@Base
 4.0.3+dfsg1-1~
  
(optional=templinst)_ZNSt8_Rb_treeIN3CEC19cec_logical_addressESt4pairIKS1_PNS0_13CCECBusDeviceEESt10_Select1stIS6_ESt4lessIS1_ESaIS6_EE8_M_eraseEPSt13_Rb_tree_nodeIS6_E@Base
 2.1.4
- 
(optional=templinst)_ZNSt8_Rb_treeIN3CEC19cec_logical_addressESt4pairIKS1_St10shared_ptrINS0_10CCECClientEEESt10_Select1stIS7_ESt4lessIS1_ESaIS7_EE17_M_emplace_uniqueIJS2_IS1_S6_S2_ISt17_Rb_tree_iteratorIS7_EbEDpOT_@Base
 4.0.3+dfsg1-1~
+#MISSING: 4.0.4+dfsg1-1# 

Processed: Re: Bug#923750: gdcm: FTBFS in buster/sid

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #923750 [src:gdcm] gdcm: FTBFS in buster/sid
Severity set to 'important' from 'serious'

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

Bug#923750: gdcm: FTBFS in buster/sid

[Mathieu Malaterre]

Control: severity -1 important

On Tue, Mar 5, 2019 at 8:24 AM Mathieu Malaterre  wrote:
>
> On Tue, Mar 5, 2019 at 1:21 AM Santiago Vila  wrote:
> > make[2]: *** [Makefile:6: refman.pdf] Error 1
>
> That must be a regression in one of the tex (sid) packages. I can
> build the pdf documentation just fine from my jessie Debian system:
>
> https://sourceforge.net/projects/gdcm/files/gdcm%202.x/GDCM%202.8.9/gdcm-2.8.9.pdf
>
> I'll check pdf build ASAP.

Odd gdcm arch-indep does not FTBFS from buildd:

https://buildd.debian.org/status/fetch.php?pkg=gdcm=all=2.8.8-7=1552044907=0

lowering severity.

Bug#918387: marked as done (lua-sql FTBFS with MariaDB 10.3)

[Debian Bug Tracking System]

Your message dated Fri, 8 Mar 2019 13:59:17 +0100
with message-id <1cad8453-ffdd-dfae-6c51-306a0ef3c...@debian.org>
and subject line Re: lua-sql FTBFS with MariaDB 10.3
has caused the Debian Bug report #918387,
regarding lua-sql FTBFS with MariaDB 10.3
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.)


-- 
918387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-sql
Version: 2.3.4-1
Severity: serious
Tags: ftbfs buster sid

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

...
src/ls_mysql.c: In function 'luaopen_luasql_mysql':
src/ls_mysql.c:605:25: error: expected ')' before 'MYSQL_SERVER_VERSION'
 lua_pushliteral (L, MYSQL_SERVER_VERSION);
 ^~~~
--- End Message ---
--- Begin Message ---
On Thu, 17 Jan 2019 17:51:55 -0300 Faustin Lammler  wrote:
> > this looks like a bug. MYSQL_SERVER_VERSION is documented here:
> > https://dev.mysql.com/doc/refman/5.5/en/c-api-server-client-versions.html

This was fixed in mariadb-10.3 1:10.3.13-1 and lua-sql has now been
given back.


Andreas--- End Message ---

Bug#923750: gdcm: FTBFS in buster/sid

[Gert Wollny]

I can't reproduce this in current sid. I've did a new upload with a
minior unrelated fix incorporated by Gianfranco. If this passed on the
build servers, I'm going to close the bug, 

best, 
Gert 

Bug#924013: unmotivated b-d on libubsan0 (GCC 7)

[Matthias Klose]

Source: ricochet-im
Version: 1.1.4-2
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: gcc-7-rm

ricochet-im build-depends on GCC 7 (libubsan0). Please just drop that bogus
build dependency.

Bug#923889: google-compute-image-packages - DoS via serial console write

[Bastian Blank]

On Thu, Mar 07, 2019 at 02:25:12PM -0800, Ross Vandegrift wrote:
> On Wed, Mar 06, 2019 at 07:49:38PM +0100, Bastian Blank wrote:
> > This package instructs journald to duplicate everything sent to the
> > journal to the serial console.  The serial console is a pretty rate
> > limited log output device and blocking there will make all software with
> > any log output block.
> This doesn't seem to affect all software - I tried to reproduce with
> logger, but it doesn't block.  Maybe this only affects some logging
> transports?

In normal operation, the rate limit of journald might make sure it does
not come to really blocking.

What happens for use cases where you need to disable this rate limit?
Mail servers which Postfix, which exclusively uses syslog that is
redirected to the journal, need this, or they will loose logs.

On Azure we tried the same for a short time period.  It got quiet messy
and also triggered bugs in the platform.

> I agree it's a problematic default - GCE serial console data is
> currently stored unencrypted.  That could be an unpleasent surprise.

I assume the initial goal was to get the log output of the provisioning
daemons on the serial console.  This goal was also mentioned in the
formerly shipped rsyslog config snippet.

Forwarding all log traffic there completely destroys that ability, as it
will be drowned by irrelevant log traffic.  Also the log buffer is
limited in size.

Regards,
Bastian

-- 
Women professionals do tend to over-compensate.
-- Dr. Elizabeth Dehaver, "Where No Man Has Gone Before",
   stardate 1312.9.

Bug#924010: wmbiff: Built without TLS support

[Yavor Doganov]

Package: wmbiff
Version: 0.4.33-1
Severity: serious
Tags: patch

IMHO any sane mail checker should support TLS:

$ wmbiff
This copy of wmbiff was not compiled with gnutls;
imaps is unavailable.  Exiting to protect your
passwords and privacy.

Looking at the build log:

| checking for gzopen in -lz... no
| GNUTLS support requires libz.a and libgdbm.a

The attached trivial patch fixes it.

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

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

Versions of packages wmbiff depends on:
ii  libc62.28-8
ii  libgcrypt20  1.8.4-5
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  libxpm4  1:3.5.12-1

wmbiff recommends no packages.

Versions of packages wmbiff suggests:
ii  ruby 1:2.5.1
ii  ssh-askpass-gnome [ssh-askpass]  1:7.9p1-9

-- no debconf information
>From 6c6acf935e8fa7679537c0b34dcf535853a7a5c1 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Fri, 8 Mar 2019 11:59:31 +0200
Subject: [PATCH] debian/control: Add zlib1g-dev to Build-Depends.

---
 debian/control | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 690b8c8..bba64de 100644
--- a/debian/control
+++ b/debian/control
@@ -9,7 +9,8 @@ Build-Depends: debhelper (>= 11),
libx11-dev,
libxext-dev,
libxpm-dev,
-   pkg-config
+   pkg-config,
+   zlib1g-dev
 Standards-Version: 4.3.0
 Rules-Requires-Root: no
 Homepage: https://www.dockapps.net/wmbiff
-- 
2.20.1

Bug#923226: marked as done (openarena: startup fails on Intel Ironlake Mobile: Couldn't compile shader)

[Debian Bug Tracking System]

Your message dated Fri, 08 Mar 2019 10:04:20 +
with message-id 
and subject line Bug#923226: fixed in ioquake3 1.36+u20181222.e5da13f~dfsg-2
has caused the Debian Bug report #923226,
regarding openarena: startup fails on Intel Ironlake Mobile: Couldn't compile 
shader
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.)


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

Package: openarena
Version: 0.8.8+dfsg-2
Severity: grave

Hi,

openarena doesn't work anymore because it doesn't manage to compile its 
shaders.


jpuydt on irc.debian.org
ioq3 1.36+u20181222.e5da13f~dfsg-1/Debian linux-x86_64 Jan 14 2019
SSE instruction set enabled
- FS_Startup -
We are looking in the current search path:
/home/jpuydt/.openarena/baseoa
/usr/lib/openarena/baseoa
/usr/lib/openarena/baseoa/z_oacmp-volume1-v3.pk3 (370 files)
/usr/lib/openarena/baseoa/pak6-patch088.pk3 (711 files)
/usr/lib/openarena/baseoa/pak6-patch085.pk3 (559 files)
/usr/lib/openarena/baseoa/pak6-misc.pk3 (229 files)
/usr/lib/openarena/baseoa/pak5-TA.pk3 (139 files)
/usr/lib/openarena/baseoa/pak4-textures.pk3 (1753 files)
/usr/lib/openarena/baseoa/pak2-players.pk3 (669 files)
/usr/lib/openarena/baseoa/pak2-players-mature.pk3 (231 files)
/usr/lib/openarena/baseoa/pak1-maps.pk3 (100 files)
/usr/lib/openarena/baseoa/pak0.pk3 (1042 files)

--
5803 files in pk3 files
execing default.cfg
couldn't exec q3config.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
- Client Initialization -
Couldn't read q3history.
- Initializing Renderer 
Trying to load "renderer_opengl2_x86_64.so" from "/usr/lib/ioquake3"...
---
QKEY found.
- Client Initialization Complete -
- R_Init -
SDL using driver "x11"
Initializing OpenGL display
Display aspect: 1.600
...setting mode 3: 640 480
Trying to get an OpenGL 3.2 core context
SDL_GL_CreateContext failed: Could not create GL context: GLXBadFBConfig
Reverting to default context
Using 24 color bits, 24 depth, 8 stencil display.
Available modes: '640x400 720x450 840x525 960x600 1280x800 800x512 700x450 
680x384 320x180 432x243 480x270 512x288 640x360 720x405 800x450 864x486 960x540 
1024x576 1280x720 360x202 684x384 320x240 400x300 512x384 576x432 640x480 
700x525 800x600 896x672 928x696 960x720 1024x768 640x512'
GL_RENDERER: Mesa DRI Intel(R) Ironlake Mobile 
Initializing OpenGL extensions
...ignoring GL_EXT_texture_compression_s3tc
...ignoring GL_S3_s3tc
...ignoring GL_EXT_texture_filter_anisotropic
...using GL_ARB_framebuffer_object
...using GL_ARB_vertex_array_object
...using GL_ARB_texture_float
...using GL_ARB_depth_clamp
...ignoring GL_ARB_seamless_cube_map
...using GLSL version 1.20
...GL_NVX_gpu_memory_info not found
...GL_ATI_meminfo not found
...ignoring GL_ARB_texture_compression_rgtc
...GL_ARB_texture_compression_bptc not found
...GL_EXT_direct_state_access not found
--- FBO_Init ---
--- GLSL_InitGPUShaders ---
Shader source:
#version 120
#define shadow2D(a,b) shadow2D(a,b).r 
#ifndef M_PI
#define M_PI 3.14159265358979323846
#endif
#ifndef deformGen_t
#define deformGen_t
#define DGEN_WAVE_SIN 1
#define DGEN_WAVE_SQUARE 2
#define DGEN_WAVE_TRIANGLE 3
#define DGEN_WAVE_SAWTOOTH 4
#define DGEN_WAVE_INVERSE_SAWTOOTH 5
#define DGEN_BULGE 7
#define DGEN_MOVE 8
#endif
#ifndef tcGen_t
#define tcGen_t
#define TCGEN_LIGHTMAP 2
#define TCGEN_TEXTURE 3
#define TCGEN_ENVIRONMENT_MAPPED 4
#define TCGEN_FOG 5
#define TCGEN_VECTOR 6
#endif
#ifndef colorGen_t
#define colorGen_t
#define CGEN_LIGHTING_DIFFUSE 11
#endif
#ifndef alphaGen_t
#define alphaGen_t
#define AGEN_LIGHTING_SPECULAR 6
#define AGEN_PORTAL 8
#endif
#ifndef r_FBufScale
#define r_FBufScale vec2(0.001563, 0.002083)
#endif
#line 0
uniform sampler2D u_DiffuseMap;

#if defined(USE_LIGHTMAP)
uniform sampler2D u_LightMap;
#endif

#if defined(USE_NORMALMAP)
uniform sampler2D u_NormalMap;
#endif

#if defined(USE_DELUXEMAP)
uniform sampler2D u_DeluxeMap;
#endif

#if defined(USE_SPECULARMAP)
uniform sampler2D u_SpecularMap;
#endif

#if defined(USE_SHADOWMAP)
uniform sampler2D u_ShadowMap;
#endif

#if defined(USE_CUBEMAP)
uniform samplerCube u_CubeMap;
#endif

#if defined(USE_NORMALMAP) || defined(USE_DELUXEMAP) || 
defined(USE_SPECULARMAP) || defined(USE_CUBEMAP)
// y = deluxe, w = cube
uniform vec4  u_EnableTextures; 
#endif

#if defined(USE_PRIMARY_LIGHT) || defined(USE_SHADOWMAP)
uniform vec3  u_PrimaryLightColor;
uniform vec3  u_PrimaryLightAmbient;
#endif

#if defined(USE_LIGHT) && 

Processed: tagging 923226, bug 923226 is forwarded to https://github.com/ioquake/ioq3/pull/400

[Debian Bug Tracking System]

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

> tags 923226 + patch upstream
Bug #923226 [ioquake3] openarena: startup fails on Intel Ironlake Mobile: 
Couldn't compile shader
Added tag(s) upstream and patch.
> forwarded 923226 https://github.com/ioquake/ioq3/pull/400
Bug #923226 [ioquake3] openarena: startup fails on Intel Ironlake Mobile: 
Couldn't compile shader
Set Bug forwarded-to-address to 'https://github.com/ioquake/ioq3/pull/400'.
> thanks
Stopping processing here.

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

Bug#923226: Bug #923226 in ioquake3 marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #923226 in ioquake3 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/ioquake3/commit/15f912f630806ca99edf1768a8c675504f7c6586


Fix shader compilation on hardware that doesn't support GLSL 1.30

In particular this affects pre-2011 Intel GPUs (5th generation,
"Ironlake", or older). It also affects Nvidia hardware older than Geforce
8xxx and AMD/ATI Radeon hardware older than Radeon HD, but those are
from 2006 and 2007 respectively, so older generations are probably no
longer relevant.

Closes: #923226


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923226

Processed: Bug #923226 in ioquake3 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923226 [ioquake3] openarena: startup fails on Intel Ironlake Mobile: 
Couldn't compile shader
Added tag(s) pending.

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

Bug#924007: python-dmidecode: FTBFS in sid in several ways

[Santiago Vila]

Package: src:python-dmidecode
Version: 3.12.2-8
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid with "dpkg-buildpackage -A" but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
set -e ;\
for python in python2.7 python3.7; do \
/usr/bin/make PY_BIN=$python ; \
/usr/bin/make PY_BIN=$python-dbg ; \
done

[... snipped ...]

In file included from /usr/include/python3.7dm/Python.h:118,
 from src/dmidecodemodule.c:42:
/usr/include/python3.7dm/pycapsule.h:28:24: note: expected 
'PyCapsule_Destructor' {aka 'void (*)(struct _object *)'} but argument is of 
type 'void (*)(void *)'
 PyAPI_FUNC(PyObject *) PyCapsule_New(
^
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/util.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/util.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmioem.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmioem.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmidecode.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmidecode.o
src/dmidecode.c: In function 'dmi_additional_info':
src/dmidecode.c:3907:42: warning: variable 'str_n' set but not used 
[-Wunused-but-set-variable]
 xmlNode *data_n = NULL, *str_n = NULL, *val_n = NULL;
  ^
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmixml.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmixml.o
src/dmixml.c: In function 'dmixml_buildstr':
src/dmixml.c:68:33: warning: pointer targets in passing argument 3 of 
'xmlStrVPrintf' differ in signedness [-Wpointer-sign]
 xmlStrVPrintf(ret, len, xmlfmt, ap);
 ^~
In file included from /usr/include/libxml2/libxml/tree.h:18,
 from src/dmixml.c:40:
/usr/include/libxml2/libxml/xmlstring.h:103:17: note: expected 'const char *' 
but argument is of type 'xmlChar *' {aka 'unsigned char *'}
 xmlStrVPrintf(xmlChar *buf,
 ^
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmierror.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmierror.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmilog.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmilog.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/xmlpythonizer.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/xmlpythonizer.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/efi.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/efi.o
x86_64-linux-gnu-gcc -pthread -g -Og -Wall -std=gnu89 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -UNDEBUG -I/usr/include/libxml2 
-I/usr/include/python3.7dm -c src/dmidump.c -o 
build/temp.linux-x86_64-3.7-pydebug/src/dmidump.o
creating build/lib.linux-x86_64-3.7-pydebug
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,relro -std=gnu89 -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-x86_64-3.7-pydebug/src/dmidecodemodule.o 
build/temp.linux-x86_64-3.7-pydebug/src/util.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmioem.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmidecode.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmixml.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmierror.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmilog.o 
build/temp.linux-x86_64-3.7-pydebug/src/xmlpythonizer.o 
build/temp.linux-x86_64-3.7-pydebug/src/efi.o 
build/temp.linux-x86_64-3.7-pydebug/src/dmidump.o 
-L/usr/lib/python3/dist-packages -L/usr/lib/pymodules/python3.7 -lxml2 -o 
build/lib.linux-x86_64-3.7-pydebug/dmidecodemod.cpython-37dm-x86_64-linux-gnu.so
creating /<>/debian/python3-dmidecode-dbg
creating /<>/debian/python3-dmidecode-dbg/usr
creating 

Bug#923226: Compiling shader doesn't work - game doesn't work

[Julien Puydt]

Hi,

Le 08/03/2019 à 09:48, Simon McVittie a écrit :


Please try the attached patch, also available at
. If that
works, I think it or something similar is going to be the best solution.
Test binaries: 


ioquake3_1.36+u20181222.e5da13f~dfsg-2~1+1+g15f912f6_amd64.deb works.

jpuydt on irc.debian.org

Bug#923226: Compiling shader doesn't work - game doesn't work

[Simon McVittie]

On Fri, 08 Mar 2019 at 08:34:06 +0100, Julien Puydt wrote:
> OpenGL version string: 2.1 Mesa 18.3.4
> OpenGL shading language version string: 1.20

OK, so your GLSL version is indeed capped at the one corresponding to
your OpenGL version, even though your version of Mesa is new enough to
understand newer versions of GLSL on other hardware (like mine).

The opengl2 renderer seems to be meant to work on GLSL 1.20, or at least
it has code to deal with GLSL 1.20 and it worked on your machine until
recently, but a GLSL 1.30 requirement seems to have crept in between
the two versions you mentioned.

Please try the attached patch, also available at
. If that
works, I think it or something similar is going to be the best solution.
Test binaries: 

I'm not really in favour of using opengl1 forever, since upstream changed
the default to opengl2 back in 2016; but if we can't get the offending
shader to work on your hardware, going back to opengl1 might be reasonable
as a temporary solution for buster (Debian 10).

By the time bullseye (Debian 11) is released, the affected hardware
generation will be more than 10 years old, at which point it might be
rather less relevant.

smcv

Bug#923457: test_likelihood_nh (Failed)

[Julien Y. Dutheil]

Dear Andreas,

Will give it a look asap.

Best,

Julien.

On Fri, Mar 8, 2019 at 9:34 AM Julien Yann Dutheil <
julien.duth...@univ-montp2.fr> wrote:

> Dear Andreas,
>
> Will give it a look asap.
>
> Best,
>
> Julien.
>
> On Fri, Mar 8, 2019 at 6:30 AM Andreas Tille  wrote:
>
>> Hi Julien,
>>
>> after fixing bug #923457 I realised that the package does not
>> build on all architectures[1]. S390x fails with[2]
>>
>>  4/14 Test  #5: test_likelihood_nh ...***Failed2.44 sec
>>
>> / 1
>> - 2
>> \ 3
>> - 4
>> / 5
>> - 6
>> \ 7
>> - 8
>> / 9
>> - 10
>> \ 11 nodes loaded.
>> Theta0 set to 0.444785
>> Theta1 set to 0.137341
>> Theta2 set to 0.219281
>> Theta3 set to 0.759382
>> Theta4 set to 0.549516
>> Theta5 set to 0.925583
>> Theta6 set to 0.527333
>> Theta7 set to 0.891561
>> Theta8 set to 0.331932
>> Theta9 set to 0.523327
>> Initializing data structure: Done.
>> Number of distinct sites...: 363
>> Initializing data structure: Done.
>> Number of distinct sites...: 363
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>>
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>>
>> 15: 5347.92 15: 5347.92
>> 0.516673 0.516673
>> 0.184681 0.184681
>> 0.209158 0.209158
>> 0.795359 0.795359
>> 0.489372 0.489372
>> 0.918414 0.918414
>> 0.489537 0.489537
>> 0.913968 0.913968
>> 0.180359 0.180359
>> 0.797456 0.797456
>> Initializing data structure: Done.
>> Number of distinct sites...: 365
>> Initializing data structure: Done.
>> Number of distinct sites...: 365
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>> Optimizing... \ 15
>> Optimizing... - 16
>> Optimizing... / 17
>>
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>> Optimizing... \ 15
>> Optimizing... - 16
>> Optimizing... / 17
>>
>> 18: 5391.43 18: 5391.43
>> 0.60777 0.60777
>> 0.127151 0.127151
>> 0.189039 0.189039
>> 0.788612 0.788612
>> 0.564763 0.564763
>> 0.941319 0.941319
>> 0.565297 0.565297
>> 0.844854 0.844854
>> 0.357532 0.357532
>> 0.717998 0.717998
>> Initializing data structure: Done.
>> Number of distinct sites...: 375
>> Initializing data structure: Done.
>> Number of distinct sites...: 375
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>>
>>
>> Optimizing... / 1
>> Optimizing... - 2
>> Optimizing... \ 3
>> Optimizing... - 4
>> Optimizing... / 5
>> Optimizing... - 6
>> Optimizing... \ 7
>> Optimizing... - 8
>> Optimizing... / 9
>> Optimizing... - 10
>> Optimizing... \ 11
>> Optimizing... - 12
>> Optimizing... / 13
>> Optimizing... - 14
>>
>> 15: 5401.83 15: 5401.83
>> 0.419181 0.419181
>> 0.140299 0.140299
>> 0.295 0.295
>> 0.900203 0.900203
>> 0.411605 0.411605
>> 0.919716 0.919716
>> 0.563041 0.563041
>> 0.813833 0.813833
>> 0.194868 0.194868
>> 0.801315 0.801315
>> 0.444785 0.514541 0.514541
>> 0.137341 0.15071 0.15071
>> 0.219281 0.231066 0.231066
>> 0.759382 0.828058 0.828058
>> 0.549516 0.48858 0.48858
>> 0.925583 0.926483 0.926483
>> 0.527333 0.539292 0.539292
>> 0.891561 0.857552 0.857552
>> 0.331932 0.244253 0.244253
>> 0.523327 0.772256 0.772256
>>
>>
>> ...
>>
>> 93% tests passed, 1 tests failed out of 14
>>
>> Total Test time (real) =  31.15 sec
>>
>> The following tests FAILED:
>>5 - test_likelihood_nh (Failed)
>>
>>
>> I remember that I once had even a test failure on my local amd64 - so
>> this test might be a bit undetermined.  Please confirm this and I'd be
>> happy if you could send an *as simple as possible* patch or simply
>> deactivate the patch.  We are in deep freeze and need to find a quick
>> and also simple solution.
>>
>> Kind regards
>>
>>Andreas.
>>
>>
>> [1] 

Processed: Bug #923427 in devscripts marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923427 [devscripts] mergechanges: Regression: --indep/source breaks 
multi-line Binary fields
Ignoring request to alter tags of bug #923427 to the same tags previously set

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

Bug#923427: Bug #923427 in devscripts marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #923427 in devscripts 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/yadd/devscripts/commit/19141f29b6f649ab5107dbd5f1b3ff76c5a9536c


mergechanges: Use Dpkg::Control to extract fields

This makes mergechanges support a multi-line Binary field.

Signed-off-by: Simon McVittie 
Closes: #923427


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923427

Processed: Bug #923427 in devscripts marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #923427 [devscripts] mergechanges: Regression: --indep/source breaks 
multi-line Binary fields
Ignoring request to alter tags of bug #923427 to the same tags previously set

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

Bug#923427: Bug #923427 in devscripts marked as pending

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #923427 in devscripts 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/yadd/devscripts/commit/19141f29b6f649ab5107dbd5f1b3ff76c5a9536c


mergechanges: Use Dpkg::Control to extract fields

This makes mergechanges support a multi-line Binary field.

Signed-off-by: Simon McVittie 
Closes: #923427


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/923427