Bug#878542: marked as done (libcloud FTBFS and Debci failure with Python 3.6 as default)

[Debian Bug Tracking System]

Your message dated Thu, 19 Oct 2017 03:48:56 +
with message-id 
and subject line Bug#878542: fixed in libcloud 2.2.1-1
has caused the Debian Bug report #878542,
regarding libcloud FTBFS and Debci failure with Python 3.6 as default
to be marked as done.

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

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


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

https://ci.debian.net/packages/libc/libcloud/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcloud.html

...
==
ERROR: test_deprecated_warning (libcloud.test.test_utils.TestUtils)
--
Traceback (most recent call last):
  File "/build/1st/libcloud-1.5.0/libcloud/test/test_utils.py", line 140, in 
test_deprecated_warning
libcloud.utils.deprecated_warning('test_module')
  File "/build/1st/libcloud-1.5.0/libcloud/utils/__init__.py", line 38, in 
deprecated_warning
category=DeprecationWarning)
  File "/usr/lib/python3.6/warnings.py", line 99, in _showwarnmsg
msg.file, msg.line)
TypeError: show_warning() takes from 4 to 5 positional arguments but 6 were 
given

==
ERROR: test_in_development_warning (libcloud.test.test_utils.TestUtils)
--
Traceback (most recent call last):
  File "/build/1st/libcloud-1.5.0/libcloud/test/test_utils.py", line 153, in 
test_in_development_warning
libcloud.utils.in_development_warning('test_module')
  File "/build/1st/libcloud-1.5.0/libcloud/utils/__init__.py", line 45, in 
in_development_warning
category=FutureWarning)
  File "/usr/lib/python3.6/warnings.py", line 99, in _showwarnmsg
msg.file, msg.line)
TypeError: show_warning() takes from 4 to 5 positional arguments but 6 were 
given

--
Ran 6131 tests in 43.732s

FAILED (errors=2, skipped=18)
debian/rules:10: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: libcloud
Source-Version: 2.2.1-1

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated libcloud 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: Wed, 18 Oct 2017 23:24:15 -0400
Source: libcloud
Binary: python-libcloud python3-libcloud
Architecture: source all
Version: 2.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrew Starr-Bochicchio 
Description:
 python-libcloud - unified Python interface into the cloud
 python3-libcloud - unified Python interface into the cloud (Python3 version)
Closes: 878542
Changes:
 libcloud (2.2.1-1) unstable; urgency=medium
 .
   [ Andrew Starr-Bochicchio ]
   * New upstream release.
- Resolves FTBFS with Python 3.6 (Closes: #878542).
   * debian/control: Remove deprecated XS-Testsuite field.
   * Build depend on python{3}-pytest and python{3}-pytest-runner.
   * Bump Standards-Version to 4.1.0.
   * Use PYBUILD_{BEFORE,AFTER}_TEST to avoid overriding
 dh_auto_test and dh_auto_clean.
   * Disable tests that conflict with pybuild's proxy settings.
 .
   [ Hans-Christoph Steiner ]
   * New upstream release from git tag
   * tests now use python-requests-mock
Checksums-Sha1:
 fd6fb2bfdde3c189dfb7449636068a883e77eb42 2668 libcloud_2.2.1-1.dsc
 a59b545a90414f6b2fbc9805bf3ccb4090caef86 1768112 libcloud_2.2.1.orig.tar.gz
 d6f1cbee49cde539b3cfd342a99def5628fe88dd 5624 libcloud_2.2.1-1.debian.tar.xz
 cc4bc6314e1f65cc9a0c446995bce896f54ba661 7876 

Bug#878542: marked as pending

[Andrew Starr-Bochicchio]

tag 878542 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/libcloud.git/commit/?id=89e3f06

---
commit 89e3f06f5213bfe565bd52a9664d863681539767
Author: Andrew Starr-Bochicchio 
Date:   Wed Oct 18 23:23:17 2017 -0400

Resolves FTBFS with Python 3.6 (Closes: #878542).

diff --git a/debian/changelog b/debian/changelog
index b9fe44d..8e04350 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,7 @@ libcloud (2.2.1-1) UNRELEASED; urgency=medium
 
   [ Andrew Starr-Bochicchio ]
   * New upstream release.
+   - Resolves FTBFS with Python 3.6 (Closes: #878542).
   * debian/control: Remove deprecated XS-Testsuite field.
   * Build depend on python{3}-pytest and python{3}-pytest-runner.
   * Bump Standards-Version to 4.1.0.

Processed: Bug#878542 marked as pending

[Debian Bug Tracking System]

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

> tag 878542 pending
Bug #878542 [src:libcloud] libcloud FTBFS and Debci failure with Python 3.6 as 
default
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: forwarded

[Debian Bug Tracking System]

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

> forwarded 878549 https://phabricator.wikimedia.org/T178346
Bug #878549 [src:uprightdiff] uprightdiff FTBFS with OpenCV 3.2
Set Bug forwarded-to-address to 'https://phabricator.wikimedia.org/T178346'.
> thanks
Stopping processing here.

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

Processed: Bug#878883: patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #878883 [src:stoken] stoken FTBFS with libtomcrypt 1.18
Added tag(s) patch.

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

Bug#878883: patch

[Mike Miller]

Control: tags -1 + patch

I have filed a pull request upstream to fix this FTBFS at
https://github.com/cernekee/stoken/pull/38. I am attaching the patch
here for convenience, which can be applied cleanly to the Debian package
to fix this.

-- 
mike
From ad699a86e0f9d8c19eabccba5610b4746a5e00e3 Mon Sep 17 00:00:00 2001
From: Mike Miller 
Date: Wed, 18 Oct 2017 16:10:44 -0700
Subject: [PATCH] stc-tomcrypt: be compatible with libtomcrypt 1.18

In libtomcrypt 1.18 the LTC_LTC_PKCS_1_* constants were renamed to
LTC_PKCS_1_*.  Add an autoconf test for this change and define an alias
to the old name when building against the older API.

Signed-off-by: Mike Miller 
---
 configure.ac   | 8 
 src/stc-tomcrypt.c | 7 ++-
 2 files changed, 14 insertions(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index f198048a29fa..3b93bc781597 100644
--- a/configure.ac
+++ b/configure.ac
@@ -185,6 +185,14 @@ if test "$with_tomcrypt" != no -a "$with_nettle" != yes; then
 		 EXTRA_PC_LIBS="$EXTRA_PC_LIBS $TOMCRYPT_PC_LIBS"],
 		[AC_MSG_RESULT([no])])
 
+	AC_MSG_CHECKING([whether libtomcrypt uses newer LTC_PKCS_1_V1_5 naming convention])
+	AC_COMPILE_IFELSE([AC_LANG_PROGRAM([#include ],
+		[int padding = LTC_PKCS_1_V1_5;])],
+		[AC_MSG_RESULT([yes])],
+		[AC_MSG_RESULT([no])
+		 AC_DEFINE([LIBTOMCRYPT_OLD_PKCS_NAMES], [1],
+			   [libtomcrypt uses the pre-1.18 PKCS #1 constant naming convention])])
+
 	LIBS="$saved_LIBS"
 	CFLAGS="$saved_CFLAGS"
 fi
diff --git a/src/stc-tomcrypt.c b/src/stc-tomcrypt.c
index 45b1bee7faf2..424c7360cd64 100644
--- a/src/stc-tomcrypt.c
+++ b/src/stc-tomcrypt.c
@@ -37,6 +37,11 @@
 #define AES_KEY_SIZE		16
 #define AES256_KEY_SIZE		32
 
+/* Backwards compatibility support for pre-1.18 versions of libtomcrypt */
+#ifdef LIBTOMCRYPT_OLD_PKCS_NAMES
+#define LTC_PKCS_1_V1_5 LTC_LTC_PKCS_1_V1_5
+#endif
+
 int stc_standalone_init(void)
 {
 	/* libtomcrypt init for sdtid BatchSignature generation */
@@ -190,7 +195,7 @@ int stc_rsa_sha1_sign_digest(const uint8_t *privkey_der, size_t privkey_len,
 	if (rsa_import(privkey_der, privkey_len, ) != CRYPT_OK)
 		return ERR_GENERAL;
 	if (rsa_sign_hash_ex(digest, (160 / 8), out, outlen,
-			 LTC_LTC_PKCS_1_V1_5, NULL, 0,
+			 LTC_PKCS_1_V1_5, NULL, 0,
 			 hash_idx, 0, ) != CRYPT_OK)
 		rc = ERR_GENERAL;
 
-- 
2.14.2



signature.asc
Description: PGP signature

Processed: closing 874521

[Debian Bug Tracking System]

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

> close 874521 1.0.0-2
Bug #874521 [fwupd] fwupd segfaults at start
Marked as fixed in versions fwupd/1.0.0-2.
Bug #874521 [fwupd] fwupd segfaults at start
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#874521: closing 874521

[Laurent Bigonville]

close 874521 1.0.0-2
thanks

Hello,

That looks OK now, fwupd is not crashing anymore here

Regards,

Laurent Bigonville

Bug#879071: 0ad FTBFS with on armhf with gcc 7: error: call of overloaded 'abs(unsigned int)' is ambiguous

[Adrian Bunk]

Source: 0ad
Version: 0.0.21-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/0ad.html
https://buildd.debian.org/status/fetch.php?pkg=0ad=armhf=0.0.22-1=1508365643=0

...
../../../source/gui/CDropDown.cpp: In member function 'virtual InReaction 
CDropDown::ManuallyHandleEvent(const SDL_Event_*)':
../../../source/gui/CDropDown.cpp:355:94: error: call of overloaded 
'abs(unsigned int)' is ambiguous
   diff = std::abs(pList->m_Items[i].GetRawString().LowerCase()[j] - 
(int)m_InputBuffer[j]);

  ^
In file included from /usr/include/c++/7/cmath:47:0,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/c++/7/bits/std_abs.h:78:3: note: candidate: constexpr long double 
std::abs(long double)
   abs(long double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:74:3: note: candidate: constexpr float 
std::abs(float)
   abs(float __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:70:3: note: candidate: constexpr double 
std::abs(double)
   abs(double __x)
   ^~~
/usr/include/c++/7/bits/std_abs.h:61:3: note: candidate: long long int 
std::abs(long long int)
   abs(long long __x) { return __builtin_llabs (__x); }
   ^~~
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
In file included from /usr/include/c++/7/bits/std_abs.h:38:0,
 from /usr/include/c++/7/cmath:47,
 from /usr/include/c++/7/math.h:36,
 from ../../../source/lib/posix/posix_types.h:48,
 from ../../../source/lib/precompiled.h:64,
 from ../../../source/pch/gui/precompiled.h:18:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
gui.make:198: recipe for target 'obj/gui_Release/CDropDown.o' failed
make[3]: *** [obj/gui_Release/CDropDown.o] Error 1

Bug#853376: marked as done (dmucs: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 22:19:51 +
with message-id 
and subject line Bug#853376: fixed in dmucs 0.6.1-3
has caused the Debian Bug report #853376,
regarding dmucs: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dmucs
Version: 0.6.1-2.1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/dmucs_0.6.1-2.1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
cc -O -I./HDR   -c -o Smaskwait.o Smaskwait.c
cc -O -I./HDR   -c -o Sread.o Sread.c
cc -O -I./HDR   -c -o Swait.o Swait.c
cc -O -I./HDR   -c -o srmtrblk.o srmtrblk.c
cc -O -I./HDR   -c -o Smkskt.o Smkskt.c
cc -O -I./HDR   -c -o Sreadbytes.o Sreadbytes.c
cc -O -I./HDR   -c -o Swrite.o Swrite.c
cc -O -I./HDR   -c -o stpblk.o stpblk.c
cc -O -I./HDR   -c -o Sopen.o Sopen.c
cc -O -I./HDR   -c -o Srmsrvr.o Srmsrvr.c
cc -O -I./HDR   -c -o error.o error.c
cc -O -I./HDR   -c -o stpnxt.o stpnxt.c
cc -O -I./HDR   -c -o Sopenv.o Sopenv.c
cc -O -I./HDR   -c -o Sscanf.o Sscanf.c
cc -O -I./HDR   -c -o fopenv.o fopenv.c
cc -O -I./HDR   -c -o strnxtfmt.o strnxtfmt.c
cc -O -I./HDR   -c -o Speek.o Speek.c
cc -O -I./HDR   -c -o cprt.o cprt.c
cc -O -I./HDR   -c -o Speername.o Speername.c
cc -O -I./HDR   -c -o Speeraddr.o Speeraddr.c
cc -O -I./HDR   -c -o Sinit.o Sinit.c
ar r simpleskts.a *.o
ar: creating simpleskts.a
finished updating simpleskts.a
make[3]: Leaving directory '/<>/COSMIC'
make[3]: Entering directory '/<>'
g++ -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o dmucs_resolve.o 
dmucs_resolve.cc
g++ -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o gethost.o 
gethost.cc
g++  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -pthread -Wl,-z,relro -o gethost  
dmucs_resolve.o gethost.o COSMIC/simpleskts.a -Wl,-z,relro
g++ -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o loadavg.o 
loadavg.cc
g++  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -pthread -Wl,-z,relro -o loadavg  loadavg.o 
COSMIC/simpleskts.a -Wl,-z,relro
g++ -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o monitor.o 
monitor.cc
g++  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security  -pthread -Wl,-z,relro -o monitor  monitor.o 
COSMIC/simpleskts.a -Wl,-z,relro
g++ -DHAVE_CONFIG_H -I. -I. -I.  -DSYSCONFDIR=\"/etc\" -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o remhost.o 
remhost.cc
remhost.cc: In function 'int main(int, char**)':
remhost.cc:65:25: error: invalid conversion from 'char' to 'char*' 
[-fpermissive]
 char *distingProp = '\0';
 ^~~~
Makefile:361: recipe for target 'remhost.o' failed
make[3]: *** [remhost.o] Error 1

Bug#879069: bind-dyndb-ldap FTBFS with libbind-dev 1:9.10.6+dfsg-1

[Adrian Bunk]

Source: bind-dyndb-ldap
Version: 10.1-2
Severity: serious

https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid

...
../../src/ldap_driver.c:951:1: error: missing initializer for field 'getsize' 
of 'dns_dbmethods_t {aka struct dns_dbmethods}' 
[-Werror=missing-field-initializers]
 };
 ^
In file included from ../../src/ldap_driver.c:16:0:
/usr/include/dns/db.h:198:17: note: 'getsize' declared here
  isc_result_t (*getsize)(dns_db_t *db, dns_dbversion_t *version,
 ^~~

Bug#867340: marked as done (Contains binary files without corresponding source)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 21:34:03 +
with message-id 
and subject line Bug#867340: fixed in intel-vaapi-driver 2.0.0~pre3+dfsg1-1
has caused the Debian Bug report #867340,
regarding Contains binary files without corresponding source
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.)


-- 
867340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: i965-va-driver
Severity: serious

This bug applies to both stretch (1.7.3) and buster/sid (1.8.3).

i965-va-driver contains many binary compiled shaders with no
corresponding source. The Debian package needs to strip them out, which
may require modifying the driver to avoid requiring them.

A quick bit of scripting, to look for files of the form '*.g*b' without
a corresponding '*.asm' or '*.g*a' file, turned up the following list
from 1.8.3:

src/shaders/brc/bsw/hme_downscale_genx_0.g8b
src/shaders/brc/bsw/hme_genx_0.g8b
src/shaders/brc/bsw/vp8_brc_init_genx_0.g8b
src/shaders/brc/bsw/vp8_brc_reset_genx_0.g8b
src/shaders/brc/bsw/vp8_brc_update_genx_0.g8b
src/shaders/brc/bsw/vp8_enc_genx_0.g8b
src/shaders/brc/bsw/vp8_enc_genx_1.g8b
src/shaders/brc/bsw/vp8_enc_genx_2.g8b
src/shaders/brc/bsw/vp8_intra_distortion_genx_0.g8b
src/shaders/brc/bsw/vp8_mpu_genx_0.g8b
src/shaders/brc/bsw/vp8_tpu_genx_0.g8b
src/shaders/brc/skl/hme_downscale_genx_0.g9b
src/shaders/brc/skl/hme_genx_0.g9b
src/shaders/brc/skl/vp8_brc_init_genx_0.g9b
src/shaders/brc/skl/vp8_brc_reset_genx_0.g9b
src/shaders/brc/skl/vp8_brc_update_genx_0.g9b
src/shaders/brc/skl/vp8_enc_genx_0.g9b
src/shaders/brc/skl/vp8_enc_genx_1.g9b
src/shaders/brc/skl/vp8_enc_genx_2.g9b
src/shaders/brc/skl/vp8_intra_distortion_genx_0.g9b
src/shaders/brc/skl/vp8_mpu_genx_0.g9b
src/shaders/brc/skl/vp8_tpu_genx_0.g9b
src/shaders/h264/mc/avc_mc.g4b
src/shaders/post_processing/gen75/sharpening_h_blur.g75b
src/shaders/post_processing/gen75/sharpening_unmask.g75b
src/shaders/post_processing/gen75/sharpening_v_blur.g75b
src/shaders/post_processing/gen8/conv_nv12.g8b
src/shaders/post_processing/gen8/sharpening_h_blur.g8b
src/shaders/post_processing/gen8/sharpening_unmask.g8b
src/shaders/post_processing/gen8/sharpening_v_blur.g8b
src/shaders/post_processing/gen9/conv_nv12.g9b
src/shaders/post_processing/gen9/conv_p010.g9b
src/shaders/post_processing/gen9/pa_to_pa.g9b
src/shaders/post_processing/gen9/pa_to_pl2.g9b
src/shaders/post_processing/gen9/pa_to_pl3.g9b
src/shaders/post_processing/gen9/pl2_to_pa.g9b
src/shaders/post_processing/gen9/pl2_to_pl2.g9b
src/shaders/post_processing/gen9/pl2_to_pl3.g9b
src/shaders/post_processing/gen9/pl2_to_rgbx.g9b
src/shaders/post_processing/gen9/pl3_to_pa.g9b
src/shaders/post_processing/gen9/pl3_to_pl2.g9b
src/shaders/post_processing/gen9/pl3_to_pl3.g9b
src/shaders/post_processing/gen9/rgbx_to_nv12.g9b

1.7.3 contains the following shorter list:

src/shaders/h264/mc/avc_mc.g4b
src/shaders/post_processing/gen75/sharpening_h_blur.g75b
src/shaders/post_processing/gen75/sharpening_unmask.g75b
src/shaders/post_processing/gen75/sharpening_v_blur.g75b
src/shaders/post_processing/gen8/sharpening_h_blur.g8b
src/shaders/post_processing/gen8/sharpening_unmask.g8b
src/shaders/post_processing/gen8/sharpening_v_blur.g8b
src/shaders/post_processing/gen9/pa_to_pa.g9b
src/shaders/post_processing/gen9/pa_to_pl2.g9b
src/shaders/post_processing/gen9/pa_to_pl3.g9b
src/shaders/post_processing/gen9/pl2_to_pa.g9b
src/shaders/post_processing/gen9/pl2_to_pl2.g9b
src/shaders/post_processing/gen9/pl2_to_pl3.g9b
src/shaders/post_processing/gen9/pl2_to_rgbx.g9b
src/shaders/post_processing/gen9/pl3_to_pa.g9b
src/shaders/post_processing/gen9/pl3_to_pl2.g9b
src/shaders/post_processing/gen9/pl3_to_pl3.g9b
src/shaders/post_processing/gen9/rgbx_to_nv12.g9b
--- End Message ---
--- Begin Message ---
Source: intel-vaapi-driver
Source-Version: 2.0.0~pre3+dfsg1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
intel-vaapi-driver package)

(This message was generated automatically at their request; if you
believe that there is a problem with 

Bug#878267: marked as done (sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 21:14:11 +
with message-id 
and subject line Bug#878267: fixed in sdl-image1.2 1.2.12-7
has caused the Debian Bug report #878267,
regarding sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling
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.)


-- 
878267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878267
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsdl2-image
Version: 2.0.1+dfsg-1
Severity: grave
Tags: patch security upstream
Control: clone -1 -2
Control: reassign -2 src:sdl-image1.2
Control: found -2 1.2.12-1
Control: retitle -2 sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling

Hi,

the following vulnerability was published for libsdl2-image.

CVE-2017-2887[0]:
| An exploitable buffer overflow vulnerability exists in the XCF
| property handling functionality of SDL_image 2.0.1. A specially
| crafted xcf file can cause a stack-based buffer overflow resulting in
| potential code execution. An attacker can provide a specially crafted
| XCF file to trigger this vulnerability.

The same is found in sdl-image1.2 afaics, but please double check. I'm
cloning this bug for the second source package.

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-2017-2887
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2887
[1] https://hg.libsdl.org/SDL_image/rev/318484db0705

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sdl-image1.2
Source-Version: 1.2.12-7

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated sdl-image1.2 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: Wed, 18 Oct 2017 22:15:49 +0200
Source: sdl-image1.2
Binary: libsdl-image1.2 libsdl-image1.2-dev
Architecture: source
Version: 1.2.12-7
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Felix Geyer 
Description:
 libsdl-image1.2 - Image loading library for Simple DirectMedia Layer 1.2, 
libraries
 libsdl-image1.2-dev - Image loading library for Simple DirectMedia Layer 1.2, 
developme
Closes: 878267
Changes:
 sdl-image1.2 (1.2.12-7) unstable; urgency=medium
 .
   * Fix CVE-2017-2887: buffer overflow in the XCF property handling.
 (Closes: #878267)
Checksums-Sha1:
 07ed939d5b78a2b6328b0b8d7d864c6500d6660e 2230 sdl-image1.2_1.2.12-7.dsc
 953c0b0aae21972006f8c4ad4f06a0527f622c64 7352 
sdl-image1.2_1.2.12-7.debian.tar.xz
Checksums-Sha256:
 a2cb9a661237c627e570e78048f851d353e55f8fbbe9b826bd8c0e30eae7db5a 2230 
sdl-image1.2_1.2.12-7.dsc
 b3b22c1895c14bc2332f3c960a1715c5b37d9482b66dfe766f7a8847f61ade19 7352 
sdl-image1.2_1.2.12-7.debian.tar.xz
Files:
 f562e1574d2bbf998df6f315adafc0bb 2230 libs optional sdl-image1.2_1.2.12-7.dsc
 a0384544cd63db0c7f2053c0d9e79941 7352 libs optional 
sdl-image1.2_1.2.12-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAlnntxcACgkQ/iLG/YMT
XUXQaA/8DMxkX7rWr9spA+VWoxk3jEHRb9Dt9Sg53HFnEGIVT8nFb6fmYdAoFxlC
K/AU5SySd6+fpjzXaEvM2Inzg3tP9eSiaivcvJyWIXguBKnHu6pBwVWMIusz6Y14
Q5iCEK/4Hi5qqlcVR8CLVMFFFzDOX3OajuNoY7VhaoDmKWQ2YXfAfKw0iqoNofpt
4igsgw/whokwbLu43BYjCQVL5aKDQ+EUfuv4U4/HybEABT0n1zm1bdqmRXYv/SIL
qXUfxfPy8UrwL/ol2m5WXF5b5WuPIGjiREdslEbXDM1wbAtnQjsyeMN+qCB6DNWo
xgC7iwxZnFI8wG3CVr7L3MRbeANYsGFz9lcVdShZXMxdelmO49KRfT4YjIO6G6+4
wo0HZIrqBh7hw0idPVgPGVcH/hU5tv33qYo5p7/+JsTFKADYIfJrcvUsojkzSWZ/
W+7WsVF64MnOTzHpknL8P04dRaBLao8U2STdc9nQVFQqUOdxnhJldaPYdjRlGrml
Y1v51g8Yrd2dx/jrMBvXKdaCvPmZCWNLc7zwWv5QtQDL6qfo7cSfsiQ9WpON5s09
kwhaz3hE1LlvDVdEeEoTPgj+Ct42u7324rFwvNkKc18tedye5H6H7O+hBzTjcN6r

Bug#878264: marked as done (libsdl2: CVE-2017-2888: Integer overflow while creating a new RGB surface)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 21:09:25 +
with message-id 
and subject line Bug#878264: fixed in libsdl2 2.0.6+dfsg1-4
has caused the Debian Bug report #878264,
regarding libsdl2: CVE-2017-2888: Integer overflow while creating a new RGB 
surface
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.)


-- 
878264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsdl2
Version: 2.0.6+dfsg1-2
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for libsdl2.

CVE-2017-2888[0]:
| An exploitable integer overflow vulnerability exists when creating a
| new RGB Surface in SDL 2.0.5. A specially crafted file can cause an
| integer overflow resulting in too little memory being allocated which
| can lead to a buffer overflow and potential code execution. An
| attacker can provide a specially crafted image file to trigger this
| vulnerability.

Upstream patch seem to be [1], but please note that this might not be
enough, cf. https://bugzilla.redhat.com/show_bug.cgi?id=1500623#c2 .

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-2017-2888
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2888
[1] http://hg.libsdl.org/SDL/rev/7e0f1498ddb5

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libsdl2
Source-Version: 2.0.6+dfsg1-4

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated libsdl2 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: Wed, 18 Oct 2017 21:36:23 +0200
Source: libsdl2
Binary: libsdl2-2.0-0 libsdl2-dev libsdl2-doc
Architecture: source
Version: 2.0.6+dfsg1-4
Distribution: unstable
Urgency: high
Maintainer: Debian SDL packages maintainers 

Changed-By: Felix Geyer 
Description:
 libsdl2-2.0-0 - Simple DirectMedia Layer
 libsdl2-dev - Simple DirectMedia Layer development files
 libsdl2-doc - Reference manual for libsdl2
Closes: 878264
Changes:
 libsdl2 (2.0.6+dfsg1-4) unstable; urgency=high
 .
   * Import further upstream patches for CVE-2017-2888.
 The initial fix was incomplete. (Closes: #878264)
 - d/patches/CVE-2017-2888-1.patch
 - d/patches/CVE-2017-2888-2.patch
 - d/patches/CVE-2017-2888-3.patch
Checksums-Sha1:
 abc8dff8b3eb8a17a7207d7b9970583b25066d10 2704 libsdl2_2.0.6+dfsg1-4.dsc
 83b7cd915888dcdd78294de40f8b0dc146fa385c 17208 
libsdl2_2.0.6+dfsg1-4.debian.tar.xz
Checksums-Sha256:
 2235c5b3d41ed91fc00c672efc943bcc368f0f948be85b2e2dfb63f7be99bee0 2704 
libsdl2_2.0.6+dfsg1-4.dsc
 ea496af5d01fb39857468eac23ba2fc23389b6bd3400e363933a8af4cc405507 17208 
libsdl2_2.0.6+dfsg1-4.debian.tar.xz
Files:
 5e9acab97d7e2942f6f1852614e3ae65 2704 libs optional libsdl2_2.0.6+dfsg1-4.dsc
 cdd872476779759cecc3755f17700aee 17208 libs optional 
libsdl2_2.0.6+dfsg1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAlnnsBYACgkQ/iLG/YMT
XUVy5Q//Xr7+AkC+kY4z8pVoj+d+WGbQWMI7zxXA8eV3hgBsqdIDcmPujj10T+Gj
P2lFozBIAyeUTLNWJHQxE0hQeFFJpCprCDD7LfF6NIofGZGr+CG7LdDtWNApuRJw
tBBOMd3RWnW5ecv9gOdYFkp7eeZqqJ0vT311dXkQfcyJ/wAspI/e1lLaghDrjUx1
VoBA8r3RAXVReU/N2Vt8lvPdarYzwlJOKTVt1+/MWyUCew4TzmSDr3uOWS3X6E09
gxtp/RazjmS2pG1YAzIZ/CQXxcxDGP+ayVSP8/Jbz6PNzJeCeDO4Eqg+fpHWQpK0
kyNoKX5StdxFWIe1G1yyf0UtbFL2tw7BImqG1kDyOGx7eg/Ex/O6lmV9Pq0ssKFL
+PvjF9vsz8BDMqTdpBUo5Nj3nTqkQBbwJH+7g73FOiLVfXaZhYq3i/rqHxy5UkVS
4wFb9ixZKaard6ftjZZ5cQ81vi90U5U8h7DLrGWHNfU99VSC2FSnSvh2Xvu200gZ
zmf2jv2UO3e8vlOJEKydj7nGLZAkygfr6n+M4KBrzrI76O7u5Eidu8QBjv098vk6
2qVIUyBAS1Xkia2tcehJ+UG0Fc89xCX7uuLmUswvCc4lfJoUCfaMIh/Eoq7dD9H6

Bug#878266: marked as done (libsdl2-image: CVE-2017-2887: Incorrect XCF property handling)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 21:09:30 +
with message-id 
and subject line Bug#878266: fixed in libsdl2-image 2.0.1+dfsg-4
has caused the Debian Bug report #878266,
regarding libsdl2-image: CVE-2017-2887: Incorrect XCF property handling
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.)


-- 
878266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsdl2-image
Version: 2.0.1+dfsg-1
Severity: grave
Tags: patch security upstream
Control: clone -1 -2
Control: reassign -2 src:sdl-image1.2
Control: found -2 1.2.12-1
Control: retitle -2 sdl-image1.2: CVE-2017-2887: Incorrect XCF property handling

Hi,

the following vulnerability was published for libsdl2-image.

CVE-2017-2887[0]:
| An exploitable buffer overflow vulnerability exists in the XCF
| property handling functionality of SDL_image 2.0.1. A specially
| crafted xcf file can cause a stack-based buffer overflow resulting in
| potential code execution. An attacker can provide a specially crafted
| XCF file to trigger this vulnerability.

The same is found in sdl-image1.2 afaics, but please double check. I'm
cloning this bug for the second source package.

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-2017-2887
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2887
[1] https://hg.libsdl.org/SDL_image/rev/318484db0705

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libsdl2-image
Source-Version: 2.0.1+dfsg-4

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

Debian distribution maintenance software
pp.
Felix Geyer  (supplier of updated libsdl2-image 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: Wed, 18 Oct 2017 22:09:02 +0200
Source: libsdl2-image
Binary: libsdl2-image-2.0-0 libsdl2-image-dev
Architecture: source
Version: 2.0.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian SDL packages maintainers 

Changed-By: Felix Geyer 
Description:
 libsdl2-image-2.0-0 - Image loading library for Simple DirectMedia Layer 2, 
libraries
 libsdl2-image-dev - Image loading library for Simple DirectMedia Layer 2, 
development
Closes: 878266
Changes:
 libsdl2-image (2.0.1+dfsg-4) unstable; urgency=medium
 .
   [ Manuel A. Fernandez Montecelo ]
   * d/copyright: Fix missing "General" in LGPL license
 .
   [ Felix Geyer ]
   * Fix CVE-2017-2887: buffer overflow in the XCF property handling.
 (Closes: #878266)
Checksums-Sha1:
 20dcdae8513e395492d1a41a0c7cccd826706e7e 2265 libsdl2-image_2.0.1+dfsg-4.dsc
 bc91cc8c81f77a58d313bbcf7796a8f2fee01ef4 4656 
libsdl2-image_2.0.1+dfsg-4.debian.tar.xz
Checksums-Sha256:
 2d9f917e45d93b87ebd8c8f9e26f152fd8a659f1dacd9234b5fa1262c864b2dc 2265 
libsdl2-image_2.0.1+dfsg-4.dsc
 7cea0c3d7541ec5195aafabd90deb918b93231dcc2bfb768b42272fe52a9b3b1 4656 
libsdl2-image_2.0.1+dfsg-4.debian.tar.xz
Files:
 b65038241d0e34d333efb318394ba790 2265 libs optional 
libsdl2-image_2.0.1+dfsg-4.dsc
 0de7b4652f246d85e2a2435c685e6660 4656 libs optional 
libsdl2-image_2.0.1+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEFkxwUS95KUdnZKtW/iLG/YMTXUUFAlnntSkACgkQ/iLG/YMT
XUXaAg/9ET3uWHIjF2hmqmoqf2Rb21iPZF7moRnswWHQUg2GuKtIkCZxY05q6sbE
lGO40kirzsTMh12G99Q2BSR5q0e0qCcM0jbwl/GmOPZAkmzq3dExsF7XXfhdZF43
GvXkpVaCshft8ULcr3g+HBJETPEpOz/32u3mufK6xYCO9TBZnSbJF+wi242rbBO7
NNSOxlf9Ub/JZVpH4KPV9GbUGskVwx9v3aMOORt2Mc8MrvuRnPH/dqDNxMU3UpAh
J7CpXt+NcWsoele9S3MhuU5WnUJiqhVjz+vjg2iKKzmBec1zWJ7l9+TtPqdhq4Vq
WlTsE1smESkJYicjlh9NgbiWESJ0kGNfP36+Hs2U8DumgGj4LpQqvkv7ZcSGLQOI
ieDTHD0xzEH41rJDBYTsnkb22mDhYpKmx7BZeFjFLMQdHj3ylTMgcupXSesrnh+v
685HR4fxKupKiBqPOB7DRW0IA0sl/DFNovXhbNgnpn45JqOwEa9XiASThYUMyiIP

Bug#853420: gle-graphics: fix ftbfs with GCC-7

[Slávek Banko]

Tags: + patch

By chance, I encountered the same bug in another project.
I attach a patch here as well.

Cheers
-- 
Slávek
Index: b/src/gle/surface/ffitcontour.cpp
===
--- a/src/gle/surface/ffitcontour.cpp
+++ b/src/gle/surface/ffitcontour.cpp
@@ -43,15 +43,9 @@
 
 /* "f2c.h" defines abs() -- conflict with the definition in  */
 /* changing the order solves the problem */
-#if ( defined(__OS2__) && defined(__EMX__) ) || defined(__WIN32__)
 #include 
 #include 
 #include "f2c.h"
-#else
-#include "f2c.h"
-#include 
-#include 
-#endif
 
 doublereal gutre2_(real* a, real* b);
 void gd_message__(const char *s, int l);

Bug#878901: marked as done (dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch")

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 21:07:16 +
with message-id 
and subject line Bug#878901: fixed in dh-make-perl 0.96
has caused the Debian Bug report #878901,
regarding dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval 
while running with -T switch"
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.)


-- 
878901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-make-perl
Version: 0.95
Severity: serious
Tags: buster sid
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first seen on ci.debian.net, dh-make-perl's test suite fails with
libdpkg-perl 1.19.0 and 1.19.0.1:

Insecure dependency in eval while running with -T switch at 
/usr/share/perl5/Dpkg/Vendor.pm line 164.
Compilation failed in require at /usr/share/perl5/Dpkg/Control/Hash.pm line 25.
BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Control/Hash.pm line 
25.
Compilation failed in require at /usr/share/perl5/Dpkg/Control.pm line 47.
BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Control.pm line 47.
Compilation failed in require at /usr/share/perl5/Dpkg/Source/Package.pm line 
51.
BEGIN failed--compilation aborted at /usr/share/perl5/Dpkg/Source/Package.pm 
line 51.
Compilation failed in require at 
/build/dh-make-perl-0.96/blib/lib/DhMakePerl/Config.pm line 15.
BEGIN failed--compilation aborted at 
/build/dh-make-perl-0.96/blib/lib/DhMakePerl/Config.pm line 15.
Compilation failed in require at 
/build/dh-make-perl-0.96/blib/lib/DhMakePerl.pm line 50.
BEGIN failed--compilation aborted at 
/build/dh-make-perl-0.96/blib/lib/DhMakePerl.pm line 50.
Compilation failed in require at t/debian-version.t line 5.
BEGIN failed--compilation aborted at t/debian-version.t line 5.
t/debian-version.t ..
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run


The -T seems to come from t/debian-version.t itself; no idea yet why
it is a problem now and why it's used here in the first place.


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlnmJVpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgY0HBAAiO0zrOzykMoimHJ7qPtFG/4F4TY1xZu1IpLO9Nf/ey0yTZQx5qCwX7QU
L+sSCHvdjYF4niDS0EgdHhYVB1AC5dAtEwSeeRzC9HQ0xLBtgagjisVmP2QQjfXu
X3hf486O6nxvMeZxdpLV2VzyMSX5kNpEOie4gwgbyYtAUbsmIzLyGgGnjsR/bKJL
N6c9eQmBSmfav6edVzjAf5rPNTA+pASCZ87hCKeaaI7It3KbkimJbhqnpDBkOOn9
5+rbhgkMmdiOSqi0WfJj437XsRyKpAIkPhivjbPUOkqv7gQg9J0JZpEuwkwYzQ4T
dHd+n3jQlvS5PRpfY8PpZ+sUeP+7FETd9oIrFLTTcdMJi0UFZ2Yqp/eljWimgNWY
ovQPuoQ9Fg3ykbPV17AwjJbsA0rr8ges4Vxoj2egAivVKxvdAQrAyLiqlaYdk0+Y
fxRCho3/M29+z1pIhH6zLzlYAS9s26dtcIbJ9EAWCZoGiALXtZRJWp8jFanAK09N
KlMQvUkVUVNPczWdv33eS9rBlqg3lwuAnm0yJHA6DPSxeJFczIUdtD1rugKBMyUx
hTUZg0jEdk7vIEu1wMW52Ef7Py89E1tcoVodVsTlsg7UklrplU9mfUQqvQBi+6eO
g/XATPDOE1/oVOWfr3V4Huc78LKHcKXpH1/yfbZFFYAmwpFYGIw=
=yIT6
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: dh-make-perl
Source-Version: 0.96

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated dh-make-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: SHA256

Format: 1.8
Date: Wed, 18 Oct 2017 20:43:22 +
Source: dh-make-perl
Binary: dh-make-perl libdebian-source-perl
Architecture: source
Version: 0.96
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Closes: 878901
Description: 
 dh-make-perl - helper for creating Debian packages from perl modules
 libdebian-source-perl - collection of Perl modules for handling Debian source 
packages
Changes:
 dh-make-perl (0.96) unstable; urgency=medium
 .
   [ gregor herrmann ]
   * Disable network tests during autopkgtests like during 

Bug#878744: marked as done (All input method failed on Qt-based X program)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 22:48:14 +0200
with message-id <20171018204814.m3mteztjws2fauqm@localhost.localdomain>
and subject line Re: Bug#878744: close request :(
has caused the Debian Bug report #878744,
regarding All input method failed on Qt-based X program
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.)


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

Dear Maintainer:

After last version upgrade(from version 1.8.2-1), I found all input method
(incl
udes ibus, fcitx) were failed on Qt-based X program, but it still works on
GTK-b
ased. It becomes "blind" when my focus was a Qt-based program, it doesn't
answer
any hotkey, and any input (the input will directly send to window).
I'm using KDE, i didn't know if this bug still visible when a Qt-based
program r
uns in GNOME or any other GTK-based desktop env.

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

Kernel: Linux 4.12.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:e
n (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libinput-bin depends on:
ii  libc6  2.24-17
ii  libudev1   235-2
ii  libwacom2  0.26-1

libinput-bin recommends no packages.

libinput-bin suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Oct 18, 2017 at 01:40:39PM +0800, Anthony Lee wrote:
> Sorry...It may not the bug of libinput, i've downgrade my libinput to the
> version 1.8.2-1, but the bug still exists...
> Probably the problem has caughted by KDE, so just close this bug tracking
> for sure ...

Closing.

Thanks,
Andreas


signature.asc
Description: PGP signature
--- End Message ---

Processed: reassign 878851 to libglvnd0-nvidia, forcibly merging 878948 878851

[Debian Bug Tracking System]

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

> reassign 878851 libglvnd0-nvidia
Bug #878851 [libgl1-mesa-dri] libgl1-mesa-dri: after updating the mesa libs 
from 13.0.6 to 17.2.2 X does not start any longer
Bug reassigned from package 'libgl1-mesa-dri' to 'libglvnd0-nvidia'.
No longer marked as found in versions mesa/13.0.6-1.
Ignoring request to alter fixed versions of bug #878851 to the same values 
previously set
> forcemerge 878948 878851
Bug #878948 [libglvnd0-nvidia] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Bug #878968 [libglvnd0-nvidia] libglvnd0-nvidia: undefined symbol: 
_glapi_tls_Current makes system unusable
Bug #878851 [libglvnd0-nvidia] libgl1-mesa-dri: after updating the mesa libs 
from 13.0.6 to 17.2.2 X does not start any longer
Severity set to 'critical' from 'normal'
Marked as found in versions nvidia-graphics-drivers/375.82-5.
Bug #878968 [libglvnd0-nvidia] libglvnd0-nvidia: undefined symbol: 
_glapi_tls_Current makes system unusable
Merged 878851 878948 878968
> thanks
Stopping processing here.

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

Bug#877247: Add net-tools to Depends

[Ludens]

PFA a patch for this bug
diff --git a/debian/changelog b/debian/changelog
index 0bc2791..052eec6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+ucarp (1.5.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add net-tools to Depends (Closes: #877247).
+
+ -- Ludens Snake   Wed, 18 Oct 2017 21:53:10 +0200
+
 ucarp (1.5.2-1) unstable; urgency=low
 
   * New Upstream Version
diff --git a/debian/control b/debian/control
index 85d53ab..7601e6b 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Standards-Version: 3.9.2
 
 Package: ucarp
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}, net-tools (>= 1.60+git20161116.90da8a0-1)
 Recommends: iproute
 Description: user-space replacement to VRRP -- automatic IP fail-over
  UCARP allows a pair of hosts to share common virtual IP addresses in 

Bug#878901: dh-make-perl: FTBFS with dpkg >= 1.19: "Insecure dependency in eval while running with -T switch"

[Damyan Ivanov]

-=| Guillem Jover, 17.10.2017 22:16:31 +0200 |=-
> On Tue, 2017-10-17 at 19:48:07 +0300, Niko Tyni wrote:
> > It looks like Dpkg::Vendor::get_vendor_info() contents have become
> > tainted, probably due to changes in Dpkg::Control::HashCore. It used to
> > dig the values out with regexp captures but now uses split.
> > 
> >  
> > https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?h=sid=9e5e03e9a6ddf74bb22ffc5ea8794a14a592d6b6
> > 
> > A test case is
> > 
> >   perl -T -MDpkg::Vendor=get_vendor_info -MScalar::Util=tainted -e 'die if 
> > tainted get_vendor_info()->{Vendor}'
> > 
> > which dies on libdpkg-perl 1.19.0.1 but not 1.18.24.
> > 
> > I don't know if the earlier untainting was accidental or intended.
> > Copying the dpkg maintainers.
> 
> TBH, I was not aware that anyone was running Dpkg modules in taint
> mode. And I don't think anyone has writen code for the modules with
> that in mind. I'm not sure either how much of it is taint clean, for
> example.
> 
> If people are really running this code in taint mode, I'm willing to
> discuss which parts of the API would make sense to cover or not, and
> what tradeoffs related to performance to take, etc.

I think that using taint mode wasn't justified in that one case, so 
imposing that on Dpkg::* would not be necessary.

During discussion, Matt S. Trout suggested on IRC that the check for 
a valid package name is better written as $input =~ 
/\A([A-Za-z]\w*(?:::\w+)*)\Z/. If no hierarchy is possible, then 
/\A([A-Za-z]\w*/ would be enough.

(Perhaps this belongs to the place where $name is interpreted as 
a module name, not when parsing generic label:value lines).

That may be considered nitpicking, especially without a view on the 
big picture, but I'd rather mention it here in case it is useful.

-- dam

Bug#879063: ipmitool FTBFS with debhelper 10.9.2

[Adrian Bunk]

Source: ipmitool
Version: 1.8.18-4
Severity: serious

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

...
   debian/rules override_dh_systemd_enable
make[1]: Entering directory '/build/1st/ipmitool-1.8.18'
dh_systemd_enable --no-enable ipmievd.service
dh_systemd_enable: Could not find "ipmievd.service" in the /lib/systemd/system 
directory of ipmitool. This could be a typo, or using Also= with a service file 
from another package. Please check carefully that this message is harmless.
dh_systemd_enable: Cannot open(ipmievd.service) to check for [Install]
debian/rules:36: recipe for target 'override_dh_systemd_enable' failed
make[1]: *** [override_dh_systemd_enable] Error 2

Bug#877620: marked as done (pymvpa2: FTBFS: exception: cannot import name make_admonition)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 16:02:40 -0400
with message-id <20171018200240.lab55ks2luyht...@hopa.kiewit.dartmouth.edu>
and subject line Re: Bug#877620: pymvpa2: FTBFS: exception: cannot import name 
make_admonition
has caused the Debian Bug report #877620,
regarding pymvpa2: FTBFS: exception: cannot import name make_admonition
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.)


-- 
877620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pymvpa2
Version: 2.6.1-1
Severity: serious
Justification: fails to build from source

Hi,

pymvpa2 FTBFS in a current sid+experimental environment while building
the documentation. Network access is not permitted during the build:


cd /build/pymvpa2-2.6.1/doc && MVPA_EXTERNALS_RAISE_EXCEPTION=off \
PYTHONPATH=/build/pymvpa2-2.6.1: \
MPLCONFIGDIR=/build/pymvpa2-2.6.1/build HOME=/build/pymvpa2-2.6.1/build 
\
/usr/bin/make html BUILDDIR=/build/pymvpa2-2.6.1/build SPHINXOPTS=""
make[3]: Entering directory '/build/pymvpa2-2.6.1/doc'
# fetch intersphinx objects for explicit intersphinxing
python source/conf.py cache_intersphinx
D: PyMVPA path ['/build/pymvpa2-2.6.1/mvpa2']
D: PYTHONPATHs /build/pymvpa2-2.6.1/doc/source
   /build/pymvpa2-2.6.1
   /build/pymvpa2-2.6.1/doc
   /usr/lib/python2.7
   /usr/lib/python2.7/plat-x86_64-linux-gnu
   /usr/lib/python2.7/lib-tk
   /usr/lib/python2.7/lib-old
   /usr/lib/python2.7/lib-dynload
   /usr/local/lib/python2.7/dist-packages
   /usr/lib/python2.7/dist-packages
D: failed to retrieve from http://docs.python.org//objects.inv: [Errno socket 
error] [Errno 111] Connection refused
D: failed to retrieve from 
http://docs.scipy.org/doc/scipy/reference/objects.inv: [Errno socket error] 
[Errno 111] Connection refused
D: failed to retrieve from http://matplotlib.sourceforge.net//objects.inv: 
[Errno socket error] [Errno 111] Connection refused
D: failed to retrieve from http://nipy.sourceforge.net/nipy/stable/objects.inv: 
[Errno socket error] [Errno 111] Connection refused
D: failed to retrieve from http://docs.scipy.org/doc/numpy//objects.inv: [Errno 
socket error] [Errno 111] Connection refused
D: failed to retrieve from http://nipy.sourceforge.net/nipype/objects.inv: 
[Errno socket error] [Errno 111] Connection refused
D: failed to retrieve from http://docs.h5py.org/en/2.3//objects.inv: [Errno 
socket error] [Errno 111] Connection refused
D: interersphinx_mapping {'http://docs.python.org/': 
'source/intersphinx/docs.python.org_objects.inv', 
'http://docs.scipy.org/doc/scipy/reference': 
'source/intersphinx/docs.scipy.org_objects.inv', 
'http://matplotlib.sourceforge.net/': 
'source/intersphinx/matplotlib.sourceforge.net_objects.inv', 
'http://nipy.sourceforge.net/nipy/stable': 
'source/intersphinx/nipy.sourceforge.net_objects.inv', 
'http://docs.scipy.org/doc/numpy/': 
'source/intersphinx/docs.scipy.org_objects.inv', 
'http://nipy.sourceforge.net/nipype': 
'source/intersphinx/nipy.sourceforge.net_objects.inv', 
'http://docs.h5py.org/en/2.3/': 'source/intersphinx/docs.h5py.org_objects.inv'} 
mkdir -p /build/pymvpa2-2.6.1/build
mkdir -p source/generated
set -e; set -o pipefail; for man in /build/pymvpa2-2.6.1/build/man/pymvpa*; do \
manfile=$(basename ${man}) ; \
cmd=${manfile#pymvpa2-*} ; \
cmd=${cmd%*.1} ; \
man2html ${man} | sed -n '//{:a;n;//b;p;ba}' | sed -n '/ 
source/generated/${manfile}.html ; \
underline="*$(echo ${cmd} | tr A-Za-z0-9 \*)" ; \
printf ".. index:: command line, ${cmd}\n.. 
_chap_cmdline_${cmd}:\n\n${underline}\nMan page for 
\`\`${cmd}\`\`\n${underline}\n\n.. raw:: html\n   :file: ${manfile}.html\n" > 
source/generated/cmd_${cmd}.rst ; \
done
sphinx-build -b html -d /build/pymvpa2-2.6.1/build/doctrees   source 
/build/pymvpa2-2.6.1/build/html
Running Sphinx v1.6.4
D: PyMVPA path ['/build/pymvpa2-2.6.1/mvpa2']
D: PYTHONPATHs /usr/share/sphinx/scripts/python2
   /build/pymvpa2-2.6.1
   /build/pymvpa2-2.6.1/doc
   /usr/lib/python2.7
   /usr/lib/python2.7/plat-x86_64-linux-gnu
   /usr/lib/python2.7/lib-tk
   /usr/lib/python2.7/lib-old
   /usr/lib/python2.7/lib-dynload
   /usr/local/lib/python2.7/dist-packages
   /usr/lib/python2.7/dist-packages
D: interersphinx_mapping {'http://docs.python.org/': 
u'/build/pymvpa2-2.6.1/doc/source/intersphinx/docs.python.org_objects.inv', 
'http://docs.scipy.org/doc/scipy/reference': 
u'/build/pymvpa2-2.6.1/doc/source/intersphinx/docs.scipy.org_objects.inv', 
'http://matplotlib.sourceforge.net/': 

Processed: bug 878264 is forwarded to https://bugzilla.libsdl.org/show_bug.cgi?id=3890

[Debian Bug Tracking System]

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

> forwarded 878264 https://bugzilla.libsdl.org/show_bug.cgi?id=3890
Bug #878264 [src:libsdl2] libsdl2: CVE-2017-2888: Integer overflow while 
creating a new RGB surface
Set Bug forwarded-to-address to 
'https://bugzilla.libsdl.org/show_bug.cgi?id=3890'.
> thanks
Stopping processing here.

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

Bug#879055: mupdf: CVE-2017-15587

[Salvatore Bonaccorso]

Source: mupdf
Version: 1.5-1
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=698605

Hi,

the following vulnerability was published for mupdf.

CVE-2017-15587[0]:
| An integer overflow was discovered in pdf_read_new_xref_section in
| pdf/pdf-xref.c in Artifex MuPDF 1.11.

base64 encoded reproducer for verifying:

JVBERi0wMDAwMDAgMCBvYmo8PC9bXS9JbmRleFsyMTQ3NDgzNjQ3IDFdLyAwIDAgUi8gMC9TaXpl
IDAvV1tdPj5zdHJlYW0Nc3RhcnR4cmVmMTAK

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-2017-15587
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15587
[1] https://bugs.ghostscript.com/show_bug.cgi?id=698605
[2] 
http://git.ghostscript.com/?p=mupdf.git;h=82df2631d7d0446b206ea6b434ea609b6c28b0e8
[3] https://nandynarwhals.org/CVE-2017-15587/

Regards,
Salvatore

Processed: RM: pygoocanvas -- RoQA; unmaintained, obsolete

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 785562
Bug #879053 [ftp.debian.org] RM: pygoocanvas -- RoQA; unmaintained, obsolete
879053 was not blocked by any bugs.
879053 was not blocking any bugs.
Added blocking bug(s) of 879053: 785562

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

Bug#878402: [debian-mysql] Bug#878402: Bug#878402: Security fixes from the October 2017 CPU

[Salvatore Bonaccorso]

Hi lars,

On Wed, Oct 18, 2017 at 03:51:26PM +0200, Lars Tangvald wrote:
> Hi,
> 
> 5.5.58 packages for Debian 7 and 8 are built, and pass the test suite.
> Attached are debdiff files for Wheezy and Jessie (source is also pushed to
> https://anonscm.debian.org/cgit/pkg-mysql/mysql-5.5.git)
> As before, we unfortunately don't have a DD in our team that can sponsor the
> upload, so we need assistance with that.

I will look into it for jessie-security then.

> I'm not sure if the security team still handles Debian8, or if the lts team
> does now?

Yes, Debian 8 Jessie is still yet handled by the security team.

Regards,
Salvatore

Bug#867439: python-mimeparse: diff for NMU version 0.1.4-3.1

[Mathias Ertl]

Hi!

The upload looks fine to me!

Thanks, Mat

On 10/17/2017 08:54 AM, Adrian Bunk wrote:

Control: tags 867439 + pending

Dear maintainer,

I've prepared an NMU for python-mimeparse (versioned as 0.1.4-3.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I should
cancel it.

cu
Adrian

Processed: Re: Bug#878948: Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libglvnd0-nvidia
Bug #878948 [libgl1-mesa-glx] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Bug reassigned from package 'libgl1-mesa-glx' to 'libglvnd0-nvidia'.
No longer marked as found in versions mesa/17.2.2-1.
Ignoring request to alter fixed versions of bug #878948 to the same values 
previously set
> forcemerge 878968 -1
Bug #878968 [libglvnd0-nvidia] libglvnd0-nvidia: undefined symbol: 
_glapi_tls_Current makes system unusable
Bug #878948 [libglvnd0-nvidia] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Severity set to 'critical' from 'serious'
Marked as found in versions nvidia-graphics-drivers/375.82-5.
Merged 878948 878968

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

Bug#878948: Couldn't open libGL.so.1: /usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

[Sven Joachim]

Control: reassign -1 libglvnd0-nvidia
Control: forcemerge 878968 -1

On 2017-10-18 00:31 +0200, Arturo Borrero Gonzalez wrote:

> Package: libgl1-mesa-glx
> Version: 13.0.6-1+b2
> Severity: serious
>
> Dear maintainers,
>
> thanks for your work with the X stack, it's really appreciated :-)
>
> I had today a very disapointing experience with Debian.
> I did the daily aptitude update && aptitude upgrade of testing buster
> in a laptop (XFCE) to find that the system would show no graphical interface
> no longer. In fact, the behaviour is a complete freeze of the machine.
>
> This is what I did to point to libgl1-mesa-glx as the main problem.
>
> 1) I upgraded a bunch of packages, usual daily update:
>
> --- 8< ---
> Aptitude 0.8.9: log report
> Tue, Oct 17 2017 19:26:20 +0200
>
>   IMPORTANT: this log only lists intended actions; actions which fail
>   due to dpkg problems may not be completed.
>
> Will install 50 packages, and remove 1 packages.
> 27.1 MB of disk space will be used
> 
> [REMOVE, NOT USED] libllvm3.9:amd64 1:3.9.1-10
> [INSTALL, DEPENDENCIES] libegl-mesa0:amd64 17.2.2-1
> [INSTALL, DEPENDENCIES] libegl1:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libgl1:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libgles2:amd64 0.2.999+git20170802-5
> [INSTALL, DEPENDENCIES] libglvnd0-nvidia:amd64 375.82-5

This is the problem, why did aptitude not install the libglvnd0 package
instead?  The libglvnd0-nvidia package is hardly the right one if you
have a Radeon card.

Cheers,
   Sven

Bug#876033: primusrun doesn't find libGL.so.1

[devfra]

On 18/10/17 13:09:06 CEST, Luca Boccassi wrote:
> On Wed, 2017-10-18 at 13:18 +0200, devfra wrote:
> > On 18/10/17 10:58:08 CEST, Luca Boccassi wrote:
> > > I think there's a couple missing i386 packages, try to install the
> > > nvidia-driver-libs:i386 metapackage to pull them in
> > 
> > Installing nvidia-driver-libs:i386 causes dependencies issues
> 
> What are the dependency issues?

The nvidia related packages on my systems are those pulled in by:
$ sudo apt install bumblebee-nvidia primus primus-libs:i386

Now, having just the packages above and their dependencies installed, if I try 
to install nvidia-driver-libs:i386 I obtain this output [0] from apt and 
aptitude. I pasted a couple of resolutions proposed by aptitude but, as I said 
in the previous message, I solved my issue by installing just the
libgl1-nvidia-glx:i386 package.

Thanks!

[0] https://paste.debian.net/hidden/26a0487a/

Bug#879045: xracer: Fatal error: function not implemented

[Andrej Mernik]

Package: xracer
Version: 0.96.9.1-8+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after completing the three laps of the inbuilt track, the game stops with
error:

xracer:player.c:201: fatal error: function not implemented
Received user signal.
Received child termination signal.

At this point it just hangs and never exits. Unfortunately it also doesn't
release the mouse. To exit, you have to switch to a virtual terminal and kill
it.

This hang might pose a big problem for unexperienced users.

Best Regards,
Andrej Mernik



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages xracer depends on:
ii  freeglut3 2.8.1-3
ii  libc6 2.24-11+deb9u1
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libice6   2:1.0.9-2
ii  libjpeg62-turbo   1:1.5.1-2
ii  libsm62:1.2.2-1+b3
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxi62:1.7.9-1
ii  libxmu6   2:1.1.2-2
ii  netpbm2:10.0-15.3+b2

xracer recommends no packages.

Versions of packages xracer suggests:
pn  xracer-tools  

-- no debconf information

Bug#879043: dahdi-linux No longer compiled with m-a as of 4.13: unknown field ‘dev_attrs’

[Tzafrir Cohen]

Package: Justin Hallett 
Version: 1:2.11.1.0.20170917~dfsg-1
Flags: patch upstream
Forwarded: https://issues.asterisk.org/jira/browse/DAHLIN-356
Severity: grave

As of kernel 4.13, build fails with the following error:

  CC [M]  /usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.o
/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:2: error: unknown field 
‘dev_attrs’ specified in initializer
  .dev_attrs = span_dev_attrs,
  ^
/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:15: error: 
initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  .dev_attrs = span_dev_attrs,
   ^~
/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:273:15: note: (near 
initialization for ‘spans_bus_type.probe’)
/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:711:2: error: unknown field 
‘dev_attrs’ specified in initializer
  .dev_attrs = dahdi_device_attrs,
  ^
/usr/src/modules/dahdi/drivers/dahdi/dahdi-sysfs.c:711:15: error: 
initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  .dev_attrs = dahdi_device_attrs,
   ^~

-- 
   Tzafrir Cohen
+972-50-7952406   mailto:tzafrir.co...@xorcom.com
http://www.xorcom.com

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 879039 https://github.com/ldc-developers/ldc/issues/2357
Bug #879039 [ldc] Crash via "Assertion `decl->ir->irGlobal != NULL' failed"
Set Bug forwarded-to-address to 
'https://github.com/ldc-developers/ldc/issues/2357'.
> forwarded 879040 https://github.com/ldc-developers/ldc/issues/2356
Bug #879040 [ldc] ldc2 fails to run simple main example on ppc64el
Set Bug forwarded-to-address to 
'https://github.com/ldc-developers/ldc/issues/2356'.
> affects 879039 sambamba
Bug #879039 [ldc] Crash via "Assertion `decl->ir->irGlobal != NULL' failed"
Added indication that 879039 affects sambamba
>
End of message, stopping processing here.

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

Bug#879040: ldc2 fails to run simple main example on ppc64el

[Matthias Klumpp]

Package: ldc
Version: 1:1.4.0-3
Severity: serious

Building a simple D example with an empty `void main () {}` function
makes LDC crash on ppc64el.

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#879039: Crash via "Assertion `decl->ir->irGlobal != NULL' failed"

[Matthias Klumpp]

Package: ldc
Version: 1:1.4.0-3
Severity: serious

When building dertain D code, LDC crashes with a "Crash via "Assertion
`decl->ir->irGlobal != NULL' failed"" message.

This affects Sambamba in Debian.

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed

[Ben Hutchings]

On Thu, 2017-10-19 at 00:46 +0800, Liang Guo wrote:
> On Wed, Oct 18, 2017 at 9:25 PM, Ben Hutchings  wrote:
> > On Wed, 2017-10-18 at 14:21 +0200, Alexander Kurtz wrote:
> > > Ok, that's what I figured. Is there at least a solution to the "if the
> > > user has the standard, most recent, Debian kernel running, make sure
> > > the corresponding headers are installed" problem? I.e. something like
> > > Ubuntu's "linux-{image,headers}-generic" packages?
> > 
> > No, there is no common metapackage name that is available on all Debian
> > architectures.  (I don't think those metapackages are available on all
> > Ubuntu architectures either.)
> 
> Is it possible for kernel to provide a package , such as linux-full, depends 
> on
> the exact version of linux-image and linux-header. When  the same linux-image
>  and linux-header are needed, this package can be put on depends field.

I've given my answer.  I'm going to be ignoring further questions on
this.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



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

Bug#877945: marked as done (dm-writeboost-dkms: module FTBFS for Linux 4.13: error: 'struct bio' has no member named 'bi_error')

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 16:49:21 +
with message-id 
and subject line Bug#877945: fixed in dm-writeboost 2.2.8-1
has caused the Debian Bug report #877945,
regarding dm-writeboost-dkms: module FTBFS for Linux 4.13: error: 'struct bio' 
has no member named 'bi_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.)


-- 
877945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dm-writeboost-dkms
Version: 2.2.7-1
Severity: serious
Justification: fails to build from source

Hi,

dm-writeboost-dkms fails to build a kernel module for the latest kernel
in sid:

   gcc-6 
-Wp,-MD,/var/lib/dkms/dm-writeboost/2.2.7/build/.dm-writeboost-target.o.d  
-nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/6/include 
-I/usr/src/linux-headers-4.13.0-1-common/arch/x86/include 
-I./arch/x86/include/generated  
-I/usr/src/linux-headers-4.13.0-1-common/include -I./include 
-I/usr/src/linux-headers-4.13.0-1-common/arch/x86/include/uapi 
-I./arch/x86/include/generated/uapi 
-I/usr/src/linux-headers-4.13.0-1-common/include/uapi 
-I./include/generated/uapi -include 
/usr/src/linux-headers-4.13.0-1-common/include/linux/kconfig.h  
-I/var/lib/dkms/dm-writeboost/2.2.7/build 
-I/var/lib/dkms/dm-writeboost/2.2.7/build -D__KERNEL__ -Wall -Wundef 
-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common 
-fshort-wchar -Werror-implicit-function-declaration -Wno-format-security 
-std=gnu89 -fno-PIE -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -m64 
-falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 
-mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mn
 o-red-zone -mcmodel=kernel -funit-at-a-time -DCONFIG_X86_X32_ABI 
-DCONFIG_AS_CFI=1 -DCONFIG_AS_CFI_SIGNAL_FRAME=1 -DCONFIG_AS_CFI_SECTIONS=1 
-DCONFIG_AS_FXSAVEQ=1 -DCONFIG_AS_SSSE3=1 -DCONFIG_AS_CRC32=1 -DCONFIG_AS_AVX=1 
-DCONFIG_AS_AVX2=1 -DCONFIG_AS_AVX512=1 -DCONFIG_AS_SHA1_NI=1 
-DCONFIG_AS_SHA256_NI=1 -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables 
-fno-delete-null-pointer-checks -Wno-frame-address -O2 
--param=allow-store-data-races=0 -DCC_HAVE_ASM_GOTO -Wframe-larger-than=2048 
-fstack-protector-strong -Wno-unused-but-set-variable 
-Wno-unused-const-variable -fno-var-tracking-assignments -g -pg -mfentry 
-DCC_USING_FENTRY -Wdeclaration-after-statement -Wno-pointer-sign 
-fno-strict-overflow -fconserve-stack -Werror=implicit-int 
-Werror=strict-prototypes -Werror=date-time -Werror=incompatible-pointer-types 
-Werror=designated-init  -DMODULE  -DKBUILD_BASENAME='"dm_writeboost_target"'  
-DKBUILD_MODNAME='"dm_writeboost"' -c -o 
/var/lib/dkms/dm-writeboost/2.2.7/build/.tmp_dm-wri
 teboost-target.o /var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c
/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c: In function 
'bio_endio_compat':
/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:116:5: error: 
'struct bio' has no member named 'bi_error'; did you mean 'bi_iter'?
  bio->bi_error = error;
 ^~
/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c: At top level:
/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:1946:12: error: 
initialization from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  .end_io = writeboost_end_io,
^
/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.c:1946:12: note: 
(near initialization for 'writeboost_target.end_io')
cc1: some warnings being treated as errors
/usr/src/linux-headers-4.13.0-1-common/scripts/Makefile.build:307: recipe for 
target '/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.o' failed
make[4]: *** [/var/lib/dkms/dm-writeboost/2.2.7/build/dm-writeboost-target.o] 
Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: dm-writeboost
Source-Version: 2.2.8-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated dm-writeboost package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed

[Liang Guo]

On Wed, Oct 18, 2017 at 9:25 PM, Ben Hutchings  wrote:
> On Wed, 2017-10-18 at 14:21 +0200, Alexander Kurtz wrote:

>> Ok, that's what I figured. Is there at least a solution to the "if the
>> user has the standard, most recent, Debian kernel running, make sure
>> the corresponding headers are installed" problem? I.e. something like
>> Ubuntu's "linux-{image,headers}-generic" packages?
>
> No, there is no common metapackage name that is available on all Debian
> architectures.  (I don't think those metapackages are available on all
> Ubuntu architectures either.)
Is it possible for kernel to provide a package , such as linux-full, depends on
the exact version of linux-image and linux-header. When  the same linux-image
 and linux-header are needed, this package can be put on depends field.

-- 
Liang Guo
http://guoliang.me/

Bug#878837: sambamba: FTBFS with ldc 1.4.0

[Matthias Klumpp]

2017-10-18 9:52 GMT+02:00 Andreas Tille :
> Hi Matthias,
>
> as usual I do not have the slightest idea what to do.  Could I again ask
> for your kind help?  Feel free to commit right to Git if you have any
> patch.

As usual, this is a LLVM/LDC bug, I will file the bugs in Debian's
bugtracker soon and tag this one accordingly.
Thanks for pinging me, I almost forgot to do that.

Cheers,
Matthias


> On Tue, Oct 17, 2017 at 12:42:28PM +0900, Nobuhiro Iwamatsu wrote:
>> Package: sambamba
>> Version: 0.6.6-1
>> Severity: serious
>> Tags: buster sid
>> Justification: FTBFS on amd64
>>
>> Hi,
>>
>> Dear Maintainer,
>>
>> sambamba FTBFS with ldc 1.4.0 on sid.
>>
>> https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.6.6-1%2Bb1=1507088043=0
>>
>> -
>> [1/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
>> -I/usr/include/htslib -enable-color -O3 -g -release  -of
>> 'sambamba@exe/main.d.o' -c ../main.d
>> ../sambamba/utils/common/readstorage.d(22): Deprecation: module
>> std.c.stdlib is deprecated - Import core.stdc.stdlib or
>> core.sys.posix.stdlib instead
>> ../sambamba/utils/common/readstorage.d(23): Deprecation: module
>> std.c.string is deprecated - Import core.stdc.string instead
>> ../sambamba/sort.d(45): Deprecation: module std.c.stdlib is deprecated
>> - Import core.stdc.stdlib or core.sys.posix.stdlib instead
>> ../sambamba/sort.d(46): Deprecation: module std.c.string is deprecated
>> - Import core.stdc.string instead
>> ../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
>> deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
>> ../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
>> is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
>> instead
>> ../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
>> is deprecated, use "not duplicate and " ~ "not failed_quality_control"
>> instead
>> [2/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
>> -I/usr/include/htslib -enable-color -O3 -g -release  -of
>> 'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
>> [3/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
>> -I/usr/include/htslib -enable-color -O3 -g -release  -of
>> 'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
>> FAILED: sambamba@exe/sambamba_depth.d.o
>> ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
>> -enable-color -O3 -g -release  -of 'sambamba@exe/sambamba_depth.d.o'
>> -c ../sambamba/depth.d
>> ../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
>> is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
>> instead
>> ../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
>> is deprecated, use "not duplicate and " ~ "not failed_quality_control"
>> instead
>> ldc2: /build/ldc-1.4.0/ir/irvar.cpp:44: IrGlobal*
>> getIrGlobal(VarDeclaration*, bool): Assertion `decl->ir->irGlobal !=
>> NULL' failed.
>> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x1a)[0x7f4948132cea]
>> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x56)[0x7f4948130fd6]
>> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(+0x86e0f3)[0x7f49481310f3]
>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f49472ab0c0]
>> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f494647bfff]
>> /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f494647d42a]
>> /lib/x86_64-linux-gnu/libc.so.6(+0x2be67)[0x7f4946474e67]
>> /lib/x86_64-linux-gnu/libc.so.6(+0x2bf12)[0x7f4946474f12]
>> -
>>
>> Perhaps this is not a problem with this package, but I think it is a
>> problem of Dlang.
>> Please forward if necessary.
>>  https://github.com/ldc-developers/ldc/issues/2357
>>
>> Best regards,
>>   Nobuhiro
>>
>>
>> --
>> Nobuhiro Iwamatsu
>>iwamatsu at {nigauri.org / debian.org}
>>GPG ID: 40AD1FA6
>>
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>>
>
> --
> http://fam-tille.de



-- 
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/

Processed: bug 878870 is not forwarded

[Debian Bug Tracking System]

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

> notforwarded 878870
Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering
Bug #878834 [libfreetype6] freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
Unset Bug forwarded-to-address
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Bug#871078: marked as done (gitlab-ci-multi-runner: FTBFS: Test failures)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 16:34:05 +
with message-id 
and subject line Bug#871078: fixed in gitlab-ci-multi-runner 1.11.4+dfsg-2
has caused the Debian Bug report #871078,
regarding gitlab-ci-multi-runner: 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.)


-- 
871078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab-ci-multi-runner
Version: 1.11.4+dfsg-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/sets
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/validation
>[no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/validation/field
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/wait
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/wsstream
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/util/yaml
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/version
>[no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/watch
>  [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/pkg/watch/versioned
>[no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/plugin/pkg/client/auth
> [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/plugin/pkg/client/auth/gcp
> [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/plugin/pkg/client/auth/oidc
>[no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/third_party/forked/reflect
> [no test files]
> ? 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/vendor/k8s.io/kubernetes/third_party/golang/netutil
> [no test files]
> dh_auto_test: go test -v -p 1 -ldflags "-X 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/common.NAME=gitlab-ci-multi-runner
>  -X gitlab.com/gitlab-org/gitlab-ci-multi-runner/common.REVISION=1.11.4" 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/apps/gitlab-runner-helper 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/commands 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/commands/helpers 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/common 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/docker 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/docker/machine 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/kubernetes 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/parallels 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/shell 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/ssh 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/executors/virtualbox 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/archives 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/cli 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/docker 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/formatter 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/parallels 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/prometheus 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/sentry 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/service 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/service/mocks 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/ssh 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/timeperiod 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/url 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/helpers/virtualbox 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/network 
> gitlab.com/gitlab-org/gitlab-ci-multi-runner/shells 
> 

Processed (with 1 error): merging with a duplicate bug

[Debian Bug Tracking System]

Processing control commands:

> forcemerge -1 878851
Bug #878948 [libgl1-mesa-glx] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
Unable to merge bugs because:
package of #878851 is 'libgl1-mesa-dri' not 'libgl1-mesa-glx'
Failed to forcibly merge 878948: Did not alter merged bugs.


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

Bug#878948: merging with a duplicate bug

[Lorenzo Pinelli]

Control: forcemerge -1 878851

Dear Arturo,

I think the problem is the one described in bug #878851

I'm therefore merging the two bugs.


Regards,
Lorenzo Pinelli

Processed: reassign 878834 to libfreetype6, forcibly merging 878870 878834

[Debian Bug Tracking System]

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

> reassign 878834 libfreetype6
Bug #878834 [src:freetype] freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
Bug reassigned from package 'src:freetype' to 'libfreetype6'.
No longer marked as found in versions freetype/2.8.1-0.1.
Ignoring request to alter fixed versions of bug #878834 to the same values 
previously set
> forcemerge 878870 878834
Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering
Bug #878834 [libfreetype6] freetype: Upgrade to 2.8.1 breaks font rendering in 
various applications
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1409188'.
Severity set to 'serious' from 'important'
Added indication that 878834 affects thunderbird
Marked as found in versions freetype/2.8.1-0.1.
Added tag(s) fixed-upstream, upstream, and patch.
Merged 878834 878870
> thanks
Stopping processing here.

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

Bug#876570: marked as done (libctypes-ocaml is not installable on debian unstable)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 18:55:15 +0300
with message-id <20171018155515.ltvn26fxret4e6km@localhost>
and subject line libctypes-ocaml is installable again
has caused the Debian Bug report #876570,
regarding libctypes-ocaml is not installable on debian unstable
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.)


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

Dear Maintainer,

I have some CI depending on libctypes-ocaml, however, since september 14, it
isn't installable:

0 packages upgraded, 155 newly installed, 0 to remove and 0 not upgraded.
Need to get 98.9 MB/147 MB of archives. After unpacking 571 MB will be used.
The following packages have unmet dependencies:
 libctypes-ocaml : Depends: ocaml-base-nox-4.02.3 which is a virtual package 
and is not provided by any available package

 libctypes-ocaml-dev : Depends: ocaml-nox-4.02.3 which is a virtual package and 
is not provided by any available package

Unable to resolve dependencies!  Giving up...

Thanks
S


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

Kernel: Linux 4.9.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)

Versions of packages libctypes-ocaml depends on:
ii  libc6   2.24-12
ii  libffi6 3.2.1-6
ii  ocaml-base-nox [ocaml-base-nox-4.02.3]  4.02.3-9

libctypes-ocaml recommends no packages.

libctypes-ocaml suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
libctypes-ocaml has been binNMU'ed and is installable again.

cu
Adrian

-- 

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

Bug#878316: marked as done (haskell-servant FTBFS: test/doctests.hs:16:1: error: Failed to load interface for ‘Build_doctests’)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 15:34:07 +
with message-id 
and subject line Bug#878316: fixed in haskell-servant 0.11-2
has caused the Debian Bug report #878316,
regarding haskell-servant FTBFS: test/doctests.hs:16:1: error: Failed to load 
interface for ‘Build_doctests’
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.)


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

https://buildd.debian.org/status/package.php?p=haskell-servant=sid

...
Linking dist-ghc/build/spec/spec ...
Preprocessing test suite 'doctests' for servant-0.11...
[1 of 1] Compiling Main ( test/doctests.hs, 
dist-ghc/build/doctests/doctests-tmp/Main.o )

test/doctests.hs:16:1: error:
Failed to load interface for ‘Build_doctests’
Use -v to see a list of the files searched for.
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-servant
Source-Version: 0.11-2

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-servant 
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: Wed, 18 Oct 2017 17:55:21 +0300
Source: haskell-servant
Binary: libghc-servant-dev libghc-servant-prof libghc-servant-doc
Architecture: source
Version: 0.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Description:
 libghc-servant-dev -
 libghc-servant-doc -
 libghc-servant-prof -
Closes: 878316
Changes:
 haskell-servant (0.11-2) unstable; urgency=medium
 .
   * Add missing build dependency on libghc-cabal-doctest-dev (Closes: #878316)
Checksums-Sha1:
 66453472b1cc4b73d549f6802f54e9b03ac156ef 4243 haskell-servant_0.11-2.dsc
 a159d5d32adddacf390986c9a38dd63fbbaba024 3076 
haskell-servant_0.11-2.debian.tar.xz
 a4fcacf78643c2a29b1d2a344eb95c910612d74d 11500 
haskell-servant_0.11-2_amd64.buildinfo
Checksums-Sha256:
 84ab2102daa9eb42a915db5e63deba5ef8a25f3d095fef7ce56cb4a8e394d112 4243 
haskell-servant_0.11-2.dsc
 b1d80a97eabadc2fbba9a0f8ee6fbd56d8e6d5cf9d45fff5985d7102492a8005 3076 
haskell-servant_0.11-2.debian.tar.xz
 29d16231185a84e2b48404d4f4185745ed2ebd51d8095c375710b398c3e5fce2 11500 
haskell-servant_0.11-2_amd64.buildinfo
Files:
 1626141b8afbe585a30d251a828c 4243 haskell extra haskell-servant_0.11-2.dsc
 76c4e6f15a03b091e1468f4df1cf48cb 3076 haskell extra 
haskell-servant_0.11-2.debian.tar.xz
 84df9cdfe910b6c5d6cb019cacd4fb54 11500 haskell extra 
haskell-servant_0.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAlnnbQgUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDyZhhAApcnC6KGLxxrRgKE3mNF1Cx1ufw9b
GkvKDTZEt1N6TCI6Bw3RQZS8kTOQYnctlu4uF+NKV6rpU3PL9efC7C3KzoycBt3N
Ct3YWSD4b+uxrqmZSfW9vBszrDGBWU7fNnokhgZS/VbP2/V0fafhwbwzljH4jR05
FX2/Xtp+CiQdQJu7Zr4HVY6FvXJmLzszdN4HnJvlNNP8m7YrBeDPCm0Ne+U1ZL0/
3qgi3i5ZRsKfBeKJHA8qvZEwceH0nDzI8K1tbTw+fo8i8i+umdnVWo5CFat0oBLo
tDQMkdfzDhls+Ah2nMx7y60XiXMOklwZFuA5XhKDmoR5l46JSiwcXFUanzHpi4yL
wUMpy5J898N8b9ugTzypPSQVQ52UMGhaVHly/727Yc3iWLPyf6cPh+azdT14s0tl
J2Q0Btx0hXtdnfY+/voHTjUSzOQczqKOnZVUkwFbL4pFRhQhThh5ZQCjDSrXgun7
nu980IB9G12XxHzdTT8UmG1oXSk8nQqu5KkD1JrCKiv7eucOWOI+zY9ZU696i5di
Frwc5TmXEFPrPEAIUHJ+XrgTXEwaj2vYG1fJLaeFgw1/+RRvvXpJLd3ikJ6DA+KF
Q5j6OPpTXIuOpIyeXrKGsN3Oxub9m1c15oJxGVG4wU2+o0RGVtoc+D9RrYvyzaE4
mUfP1gxmKf8uQx4=
=JLEv
-END PGP SIGNATURE End Message ---

Bug#876315: marked as done (CVE-2017-14339)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 15:15:20 +
with message-id 
and subject line Bug#876315: fixed in yadifa 2.2.6-1
has caused the Debian Bug report #876315,
regarding CVE-2017-14339
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.)


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

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14339

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: yadifa
Source-Version: 2.2.6-1

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

Debian distribution maintenance software
pp.
Markus Schade  (supplier of updated yadifa 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: Thu, 21 Sep 2017 11:59:20 +0200
Source: yadifa
Binary: yadifa libyadifa-dev
Architecture: source
Version: 2.2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Markus Schade 
Changed-By: Markus Schade 
Description:
 libyadifa-dev - development libraries and header files for YADIFA
 yadifa - Internet Domain Name Server
Closes: 876315
Changes:
 yadifa (2.2.6-1) unstable; urgency=medium
 .
   * New upstream version 2.2.6
 Closes: #876315, CVE-2017-14339
   * Refreshed no-compiledate patches
   * Update build dependency for debhelper
Checksums-Sha1:
 b27890a41c8a1757cbbd0efba34a65f411ff0eaf 1852 yadifa_2.2.6-1.dsc
 a6639bde95d7d4f7a9a04ae98d7031e85af7372c 3674737 yadifa_2.2.6.orig.tar.gz
 ca9dd82f4ac95f98deeeaf8c58de8d2ed70017d6 16856 yadifa_2.2.6-1.debian.tar.xz
Checksums-Sha256:
 4bf81b34ddabf4153478fcd495c20fcc99a6b20e496e30173ed29562319c0f61 1852 
yadifa_2.2.6-1.dsc
 d7c42e42a24b613a8a028bb746e45e5c588ac53a35cc7e91655c7c595c192a10 3674737 
yadifa_2.2.6.orig.tar.gz
 b2d9e2a97aeb41c4e96bf04cd05fec015c329e78acb81dadc16ca24acf9aefbf 16856 
yadifa_2.2.6-1.debian.tar.xz
Files:
 ad19acd7d94e6e6325dc9fac12982122 1852 net optional yadifa_2.2.6-1.dsc
 efd0ac059358ac01a6f508288df01a61 3674737 net optional yadifa_2.2.6.orig.tar.gz
 33a137775e10d0740caec4be88a60e0c 16856 net optional 
yadifa_2.2.6-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZ5151AAoJEPNPCXROn13Z+W8QAJyPjZkIQj4PiUtujqX1FQ13
d3Y+//4uuFdhCpxgfBE8HrC+VS9loDrlW6Dv/CIp4sGqZ3zxKNbeSBSWgYB3YSHx
ImI7LFRzezmYxP1Ow6JN/Dv8o4fqjGn36SsbSRf8LNL3i+JpM90lq/hvYknuDUOD
TVl1HmdOwlLo36DhIr5Nb6uKl5mOjjPaMLXQ37vRZEYi6A4Z95L2uWVarX70Y1zR
4NB4ZyeYd7Z2FeUQEw/aEqu4oD1STXe/VaBG18UaR262vzXlL5Ci1uzuW47ZVxtk
AObRjBVPjPEc0nljV9CqE+IPVXWUp/gKjc8gZnK8V6oLJELkb5p5f8M+NbLitJ2F
bg0UvMAc3okVVSpS7dbhOWo10fcvbrwDSH/vQzMlFSsTqO2HVi3hkSL4NRa7bMDy
2DA7Q6409ul6WXeo/CiU+Ecjm9RBb2RbtFY4IMVETLUn+XQHLat599T/5+MLKR5Q
/kjkjTqP/oH2AuIFeQxkTlZtdAzJC5EIPWaunnEd1yPrWRmCtsJheyxFUqm0kef5
MRBTLUNsizcd1bZ9vBk7TVoVlqQJYOVbZ4vcPwGU2rGWh9piZzGEKpXVmyqOXhE2
TVGR61LT6l8jQlEOLLFfnH4bTAZmFvml52Y6RkSqPn1zDrTZeIT/SUl5NtiahVVk
WemhsmzyK10VWmkXWEww
=vKis
-END PGP SIGNATURE End Message ---

Bug#875969: marked as done (libopenshot: FTBFS: Timeline_Tests.cpp:158:1: error: Failure in Timeline_Check_Two_Track_Video)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 15:00:23 +
with message-id 
and subject line Bug#875969: fixed in libopenshot 0.1.8+ds1-1
has caused the Debian Bug report #875969,
regarding libopenshot: FTBFS: Timeline_Tests.cpp:158:1: error: Failure in 
Timeline_Check_Two_Track_Video
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.)


-- 
875969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenshot
Version: 0.1.7+ds1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

libopenshot FTBFS on amd64 with test failures:

https://buildd.debian.org/status/fetch.php?pkg=libopenshot=amd64=0.1.7%2Bds1-1%2Bb1=1502819536=0


 RUNNING ALL TESTS

[AudioData @ 0x7ffc51a8b0a0] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[AudioData @ 0x7fe633ffe450] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[AudioData @ 0x7ffc51a8ba40] invalid NULL pointer for src[0]
[libvpx @ 0x5634b47db880] v1.6.1
[webm @ 0x5634b45be660] Using AVStream.codec.time_base as a timebase hint to 
the muxer is deprecated. Set AVStream.time_base instead.
[webm @ 0x5634b45be660] Using AVStream.codec to pass codec parameters to muxers 
is deprecated, use AVStream.codecpar instead.
[webm @ 0x5634b45be660] Using AVStream.codec.time_base as a timebase hint to 
the muxer is deprecated. Set AVStream.time_base instead.
[webm @ 0x5634b45be660] Using AVStream.codec to pass codec parameters to muxers 
is deprecated, use AVStream.codecpar instead.
[AudioData @ 0x7fe633ffe630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe6337fd630] invalid NULL pointer for src[0]
[AudioData @ 0x7fe6037fd450] invalid NULL pointer for src[0]
[AudioData @ 0x7fe602ffc450] invalid NULL pointer for src[0]
/<>/libopenshot-0.1.7+ds1/tests/Timeline_Tests.cpp:158:1: error: 
Failure in Timeline_Check_Two_Track_Video: Expected 23 but was 0
/<>/libopenshot-0.1.7+ds1/tests/Timeline_Tests.cpp:159:1: error: 
Failure in Timeline_Check_Two_Track_Video: Expected 190 but was 0
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
FAILURE: 1 out of 79 tests failed (2 failures).
Test time: 8.28 seconds.



Andreas
--- End Message ---
--- Begin Message ---
Source: libopenshot
Source-Version: 0.1.8+ds1-1

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated libopenshot 
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, 26 Sep 2017 16:55:53 +0200
Source: libopenshot
Binary: libopenshot13 libopenshot-dev libopenshot-doc python3-openshot
Architecture: source amd64 all
Version: 0.1.8+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Dr. Tobias Quathamer 
Description:
 libopenshot-dev - development files for the OpenShot video library
 libopenshot-doc - documentation for the OpenShot video library
 libopenshot13 - library for high-quality video editing
 python3-openshot - OpenShot video library bindings for Python 3
Closes: 872904 875969
Changes:
 libopenshot (0.1.8+ds1-1) unstable; urgency=medium
 .
   * New upstream version 0.1.8+ds1
 - Fix FTBFS due to failing tests. Closes: #875969
   * Refresh patches
   * Bump soversion to 13
   * Adopt package. (Closes: #872904)
   * Update Standards-Version to 4.1.0
Checksums-Sha1:
 2ecff89f1912e51a28d020ffb4f2b3258650c2b5 2563 libopenshot_0.1.8+ds1-1.dsc
 ec706d534847ac8691c0fae6a1559279dd05d99f 

Bug#876315: CVE-2017-14339

[Gianfranco Costamagna]

On Wed, 20 Sep 2017 23:23:29 +0200 Moritz Muehlenhoff  wrote:
> Source: yadifa
> Severity: grave
> Tags: security
> 
> Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14339
> 
> Cheers,
> Moritz
> 
> 

fixed in unstable, and preparing right now the security upload

G.



signature.asc
Description: OpenPGP digital signature

Bug#878751: expeyes FTBFS: recipe for target 'microhope.pdf' failed

[Aaron M. Ucko]

Source: expeyes
Followup-For: Bug #878751

Error 127 generally means "command not found", and is happening for
automatic builds in minimal environments geared for building only
expeyes's architecture-dependent binary packages.  Please either
arrange to prepare the documentation only under build-indep, or move
any needed packages back from Build-Depends-Indep into the main
Build-Depends.

Thanks!

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

Processed: found 878999 in 3.0.0-9

[Debian Bug Tracking System]

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

> # already seen in previous versions
> # also not really reproducible, built on i386 after a gb
> found 878999 3.0.0-9
Bug #878999 [src:protobuf] protobuf FTBFS on armhf/i386: testMergeFrom 
(google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault
Marked as found in versions protobuf/3.0.0-9.
> thanks
Stopping processing here.

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

Bug#866632: [Pkg-crosswire-devel] Bug#866632: Reported upstream

[Roberto C . Sánchez]

forwarded 866632 https://github.com/postiffm/bibledit-desktop/issues/37
thanks

Hi Teus,

The above command to the BTS control server [0] annotates the bug's
metadata with the URL of the upstream bug report.  That causes it to
show up at the top of the bug's status page and makes the information
accessible through the BTS API.  I have added the control address to the
BCC of this message so that it will already be accomplished by me
sending this message and there is no need for you to take any action.
However, you may want to review the BTS control server page to see what
other mechanisms are available.  You can also issue the same commands
using the reportbug command-line utility.

Regards,

-Roberto

[0] https://www.debian.org/Bugs/server-control#forwarded

On Wed, Oct 18, 2017 at 12:56:20PM +, Teus Benschop wrote:
>This bug report has been forwarded to the upstream developer @ github.
>Here is the link to the issue on github:
>[1]https://github.com/postiffm/bibledit-desktop/issues/37
> 
> References
> 
>Visible links
>1. https://github.com/postiffm/bibledit-desktop/issues/37

> ___
> Pkg-crosswire-devel mailing list
> pkg-crosswire-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel


-- 
Roberto C. Sánchez

Processed: Re: [Pkg-crosswire-devel] Bug#866632: Reported upstream

[Debian Bug Tracking System]

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

> forwarded 866632 https://github.com/postiffm/bibledit-desktop/issues/37
Bug #866632 [src:bibledit-gtk] bibledit-gtk: depends on libwebkitgtk-1.0-0 
which is deprecated
Set Bug forwarded-to-address to 
'https://github.com/postiffm/bibledit-desktop/issues/37'.
> thanks
Stopping processing here.

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

Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed

[Ben Hutchings]

On Wed, 2017-10-18 at 14:21 +0200, Alexander Kurtz wrote:
> On Wed, 2017-10-18 at 13:02 +0100, Ben Hutchings wrote:
> > > Please comment on bug #877925 [4] and/or #878922 [3] regarding on how
> > > to solve the "this package needs the current kernel's headers
> > > installed" problem!
> > 
> > You cannot use package dependencies to do this.  It has to be a run-
> > time check.
> 
> Ok, that's what I figured. Is there at least a solution to the "if the
> user has the standard, most recent, Debian kernel running, make sure
> the corresponding headers are installed" problem? I.e. something like
> Ubuntu's "linux-{image,headers}-generic" packages?

No, there is no common metapackage name that is available on all Debian
architectures.  (I don't think those metapackages are available on all
Ubuntu architectures either.)

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



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

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

> Please attach the full report by running
>
> reportbug --template nvidia-driver

I am not sure this helps, but here you go. This is the result
that ``reportbug --template nvidia-driver'' saved in /tmp:

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Hendrik Tews 
To: Debian Bug Tracking System 
Subject: nvidia-driver: none

Package: nvidia-driver
Severity: wishlist

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

Kernel: Linux 4.13.0-1-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)

Bug#866632: Reported upstream

[Teus Benschop]

This bug report has been forwarded to the upstream developer @ github.

Here is the link to the issue on github:

https://github.com/postiffm/bibledit-desktop/issues/37

Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot

[Phil Susi]

On 10/18/2017 3:54 AM, Bernhard Schmidt wrote:
> Accessing /home leads to a blocked process. The reason is that (for
> numerous years, due to reasons I don't remember) I had
> x-systemd.automount in my fstab for /home

That makes sense.  Now I wonder why is fsck trying to open /home?  You
run it on the block device; it should not know or care that the
filesystem is normally mounted in /home.

Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed

[Alexander Kurtz]

On Wed, 2017-10-18 at 13:02 +0100, Ben Hutchings wrote:
> > Please comment on bug #877925 [4] and/or #878922 [3] regarding on how
> > to solve the "this package needs the current kernel's headers
> > installed" problem!
> 
> You cannot use package dependencies to do this.  It has to be a run-
> time check.

Ok, that's what I figured. Is there at least a solution to the "if the
user has the standard, most recent, Debian kernel running, make sure
the corresponding headers are installed" problem? I.e. something like
Ubuntu's "linux-{image,headers}-generic" packages?

Best regards

Alexander Kurtz

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

Bug#876033: primusrun doesn't find libGL.so.1

[Luca Boccassi]

On Wed, 2017-10-18 at 13:18 +0200, devfra wrote:
> On 18/10/17 10:58:08 CEST, Luca Boccassi wrote:
> > I think there's a couple missing i386 packages, try to install the
> > nvidia-driver-libs:i386 metapackage to pull them in
> 
> Installing nvidia-driver-libs:i386 causes dependencies issues but
> easily 
> resolvable. However I solved my issue by installing just
> libgl1-nvidia-glx:i386.

What are the dependency issues?

> Could it be useful to add this package as a dependency of primus-
> libs:i386? 
> Having the latter installed I do not expect to install other
> packages.
> 
> Thank you for your help!

Unfortunately we can't as Primus is in MAIN but nvidia-driver is in
NON-FREE. And more importantly Primus can work with Nouveau as well.

The nvidia-driver-libs metapackage is the right entry point, installing
the i386 version is the supported to way to run 32bit applications, as
they might be using not only GLX but also EGL and so on.

-- 
Kind regards,
Luca Boccassi

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

Bug#878935: libbpfcc needs a way to ensure the current kernel's headers are installed

[Ben Hutchings]

On Tue, 2017-10-17 at 21:37 +0200, Alexander Kurtz wrote:
> Hi!
> 
> (Applications linked against) libbpfcc will dynamically compile and
> load C source code into eBPF byte code at runtime and load the result
> into the kernel for various purposes (e.g. socket filtering, tracing,
> etc.).
> 
> For this to work, it needs the kernel headers of the *currently running
> kernel* [0,1]. Therefore, the maintainer of libbpfcc in Debian added a
> corresponding dependency [2] which unfortunately breaks everything but
> amd64 [3] and does also not quite fix the original bug [4].
> 
> Please comment on bug #877925 [4] and/or #878922 [3] regarding on how
> to solve the "this package needs the current kernel's headers
> installed" problem!

You cannot use package dependencies to do this.  It has to be a run-
time check.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.



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

Bug#879002: Should the package be removed?

[Emmanuel Bourg]

Upstream has moved to GitHub [1] and the last update was released in
2014 but the security issue is still not fixed [2].

This was a dependency of Jenkins which is now gone. There is a slim
chance that this package could be useful again in the future since it's
a dependency of some Apache projects (Zeppelin, Atlas, Ranger and Knox).

Emmanuel Bourg

[1] https://github.com/kohsuke
[2] https://github.com/kohsuke/libpam4j/issues/18

Bug#879006: gnome-software FTBFS with fwupd 1.0.0-1

[Michael Biebl]

We probably need to cherry-pick this commit from master:

https://git.gnome.org/browse/gnome-software/commit/?id=781c81721964e841fd35a0cd7a10c8ed51afa339

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#876033: primusrun doesn't find libGL.so.1

[devfra]

On 18/10/17 10:58:08 CEST, Luca Boccassi wrote:
> I think there's a couple missing i386 packages, try to install the
> nvidia-driver-libs:i386 metapackage to pull them in

Installing nvidia-driver-libs:i386 causes dependencies issues but easily 
resolvable. However I solved my issue by installing just
libgl1-nvidia-glx:i386.

Could it be useful to add this package as a dependency of primus-libs:i386? 
Having the latter installed I do not expect to install other packages.

Thank you for your help!

Bug#877590: Please help upgrading htsjdk (Was: Bug#877590: FTBFS: error: package org.testng does not exist)

[olivier sallou]

Hi,
I have added a patch (and updated one) to use base testing instead of using
scalatest library, as it is not available in debian.
I also disabled scala related tests (as scalatest not available).

With this, the package builds fine. I do not checked how it *works*...
Compilation is fine but is seems that no test is executed (non scala ones).
I don't understand why. Test step is executed, but no test inside...
I think it still needs some investigation, will let you know

Anyway I pushed my modifications to git repo

Olivier


>
> Le mer. 11 oct. 2017 11:23, Andreas Tille  a écrit :
>
>> Hi folks,
>>
>> it seems no-one of the Java-competent uploaders cared for this in the
>> first place and so I gave the new version a shot in Git.  It seems
>> to be a usual pattern that we need to adapt several patches which I
>> hopefully managed correctly.  Its also a usual pattern that each new
>> version simply fails to build and I need some help of people more
>> comfortable with Java and here we are:
>>
>> build for version:2.12.0
>> Adding task debianMavenPom to project 'htsjdk'
>> Failed to notify ProjectEvaluationListener.afterEvaluate(), but primary
>> configuration failure takes precedence.
>> org.gradle.api.ProjectConfigurationException: A problem occurred
>> configuring root project 'htsjdk'.
>> at
>> org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:79)
>> at
>> org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:57)
>> at
>> org.gradle.api.internal.project.DefaultProject.evaluate(DefaultProject.java:573)
>> ...
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
>> at
>> org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
>> at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
>> Caused by: org.gradle.api.GradleScriptException: A problem occurred
>> evaluating root project 'htsjdk'.
>> at
>> org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:92)
>> at
>> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:176)
>> at
>> org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
>> at
>> org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:181)
>> at
>> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38)
>> at
>> org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:25)
>> at
>> org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
>> at
>> org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
>> ... 44 more
>> Caused by:
>> org.gradle.internal.metaobject.AbstractDynamicObject$CustomMessageMissingMethodException:
>> Could not find method tags() for arguments
>> [build_1mvn7vlj67avyewsbb9yibyt$_run_closure6$_closure19@2abc8034] o
>> n task ':test' of type org.gradle.api.tasks.testing.Test.
>> at
>> org.gradle.internal.metaobject.AbstractDynamicObject.methodMissingException(AbstractDynamicObject.java:182)
>> at
>> org.gradle.internal.metaobject.ConfigureDelegate.invokeMethod(ConfigureDelegate.java:89)
>> at
>> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeOnDelegationObjects(ClosureMetaClass.java:430)
>> at
>> org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:369)
>> at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1028)
>> ...
>> at
>> org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:69)
>> at
>> org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:52)
>> at
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:154)
>> at
>> org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:166)
>> at
>> build_1mvn7vlj67avyewsbb9yibyt.run(/build/htsjdk-2.12.0+dfsg/build.gradle:82)
>> at
>> org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:90)
>> ... 51 more
>>
>> FAILURE: Build failed with an exception.
>>
>>

Bug#875399: marked as done (AttributeError: type object 'Theme' has no attribute 'themes')

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 11:04:56 +
with message-id 
and subject line Bug#875399: fixed in sphinx-testing 0.7.2-0.1
has caused the Debian Bug report #875399,
regarding AttributeError: type object 'Theme' has no attribute 'themes'
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.)


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

Hi,

after upgrade to Sphinx 1.6, this package is not working:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx_testing/util.py", line 151, in 
decorator
app.cleanup()
  File "/usr/lib/python2.7/dist-packages/sphinx_testing/util.py", line 96, in 
cleanup
Theme.themes.clear()
AttributeError: type object 'Theme' has no attribute 'themes'

Version 0.7.2 should fix this, see 
https://github.com/sphinx-doc/sphinx-testing/commit/5e09ddb5989e77ddf84f2be919ce5ece7413c0ce

Thanks for fixing.

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

Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sphinx-testing
Source-Version: 0.7.2-0.1

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated sphinx-testing 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: Wed, 11 Oct 2017 09:46:31 +
Source: sphinx-testing
Binary: python-sphinx-testing python3-sphinx-testing
Architecture: source all
Version: 0.7.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Kouhei Maeda 
Changed-By: Thomas Goirand 
Description:
 python-sphinx-testing - testing utility for Sphinx extensions
 python3-sphinx-testing - testing utility for Sphinx extensions for Python3
Closes: 875399
Changes:
 sphinx-testing (0.7.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release:
 - Fix issue with Sphinx 1.6 (Closes: #875399).
   * Added debian/source/options to allow ignoring generated egg-info folder,
 which makes it possible to build the package twice in a raw.
Checksums-Sha1:
 1235ee51e9331fa5734759d0d4ac9db461258bf8 2149 sphinx-testing_0.7.2-0.1.dsc
 054e1572057f36018fa9a3297cf04c0855115860 10704 sphinx-testing_0.7.2.orig.tar.gz
 f2dc6a4ed9412d7906b48f68b2c2b79bea69cbe8 3476 
sphinx-testing_0.7.2-0.1.debian.tar.xz
 615ab38018f61ca164399730775eec1e4d705f7c 7720 
python-sphinx-testing_0.7.2-0.1_all.deb
 65fe9feecb42fe8b55ee4e143335a43c021e7fe8 7508 
python3-sphinx-testing_0.7.2-0.1_all.deb
 501e2271d33bf6f22b35e31cdb9d0ac529698a24 8643 
sphinx-testing_0.7.2-0.1_amd64.buildinfo
Checksums-Sha256:
 9e602c3ab1cc37100e6c4428b356d401b9e423fa7112b1f931afdd2596784abc 2149 
sphinx-testing_0.7.2-0.1.dsc
 3531f4a1f870a85c3084347326c792e274c9d9f129864e6d054841d77e6f20cd 10704 
sphinx-testing_0.7.2.orig.tar.gz
 c637539c0347e73d075dcdb7d01bd2ef587edcccd1f16b79d67210ba2ee3db7e 3476 
sphinx-testing_0.7.2-0.1.debian.tar.xz
 887b4966cee1231c124fb2bab5a1b88497da9cae503aa11c2aa0832fac41aa3a 7720 
python-sphinx-testing_0.7.2-0.1_all.deb
 2886559ae05332513ab9682e1ff6c4ff892c1668f9fdc178251ce34efe86ff65 7508 
python3-sphinx-testing_0.7.2-0.1_all.deb
 0ff4b6ccfe3729f07a61972a4206c826d56791a1ea67635378ab5bd06fc833ab 8643 
sphinx-testing_0.7.2-0.1_amd64.buildinfo
Files:
 e3eebb2c205b989f7c40f59f81a11265 2149 python optional 
sphinx-testing_0.7.2-0.1.dsc
 2ebd24b0d9cb5f81769dd28d08c2b65e 10704 python optional 
sphinx-testing_0.7.2.orig.tar.gz
 

Processed: reassign 878870 to libfreetype6, affects 878870

[Debian Bug Tracking System]

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

> reassign 878870 libfreetype6 2.8.1-0.1
Bug #878870 [thunderbird,libfreetype6] freetype 2.8.1 breaks font rendering
Bug reassigned from package 'thunderbird,libfreetype6' to 'libfreetype6'.
No longer marked as found in versions libfreetype6/2.8.1-0.1 and 
thunderbird/1:52.3.0-4.
Ignoring request to alter fixed versions of bug #878870 to the same values 
previously set
Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering
Marked as found in versions freetype/2.8.1-0.1.
> affects 878870 thunderbird
Bug #878870 [libfreetype6] freetype 2.8.1 breaks font rendering
Added indication that 878870 affects thunderbird
> thanks
Stopping processing here.

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

Processed: unarchiving 200262, notfound 200262 in 1.81-3, notfound 200262 in units/2.14-1, archiving 200262

[Debian Bug Tracking System]

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

> unarchive 200262
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 {Done: j...@dhh.gt.org (John Hasler)} [units] units: Unknown units: 
Fahrenheit, Celsius, Kelvin
Unarchived Bug 200262
Unarchived Bug 878903
> notfound 200262 1.81-3
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 {Done: j...@dhh.gt.org (John Hasler)} [units] units: Unknown units: 
Fahrenheit, Celsius, Kelvin
There is no source info for the package 'units' at version '1.81-3' with 
architecture ''
Unable to make a source version for version '1.81-3'
No longer marked as found in versions 1.81-3.
No longer marked as found in versions 1.81-3.
> notfound 200262 units/2.14-1
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 {Done: j...@dhh.gt.org (John Hasler)} [units] units: Unknown units: 
Fahrenheit, Celsius, Kelvin
No longer marked as found in versions units/2.14-1.
No longer marked as found in versions units/2.14-1.
> archive 200262
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 {Done: j...@dhh.gt.org (John Hasler)} [units] units: Unknown units: 
Fahrenheit, Celsius, Kelvin
archived 200262 to archive/62 (from 200262)
archived 878903 to archive/03 (from 200262)
> thanks
Stopping processing here.

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

Processed: unarchiving 200262, forcibly merging 200262 878903, archiving 200262

[Debian Bug Tracking System]

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

> unarchive 200262
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Unarchived Bug 200262
> forcemerge 200262 878903
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 [units] units: Unknown units: Fahrenheit, Celsius, Kelvin
Severity set to 'grave' from 'normal'
Marked Bug as done
There is no source info for the package 'units' at version '1.81-3' with 
architecture ''
Unable to make a source version for version '1.81-3'
Marked as found in versions 1.81-3.
Added tag(s) upstream.
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
There is no source info for the package 'units' at version '1.81-3' with 
architecture ''
Unable to make a source version for version '1.81-3'
Marked as found in versions units/2.14-1.
Merged 200262 878903
> archive 200262
Bug #200262 {Done: j...@dhh.gt.org (John Hasler)} [units] units: temperature 
conversion is drastically wrong!
Bug #878903 {Done: j...@dhh.gt.org (John Hasler)} [units] units: Unknown units: 
Fahrenheit, Celsius, Kelvin
archived 200262 to archive/62 (from 200262)
archived 878903 to archive/03 (from 200262)
> thanks
Stopping processing here.

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

Bug#879006: gnome-software FTBFS with fwupd 1.0.0-1

[Adrian Bunk]

Source: gnome-software
Version: 3.26.1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=gnome-software=sid

...
FAILED: plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o 
cc  -Iplugins/fwupd/gs_plugin_fwupd@sha -Iplugins/fwupd -I../plugins/fwupd 
-Iplugins/fwupd/../.. -I../plugins/fwupd/../.. -Iplugins/fwupd/../../lib 
-I../plugins/fwupd/../../lib -I/usr/include/libappstream-glib 
-I/usr/include/uuid -I/usr/include/libgcab-1.0 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0/ -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/json-glib-1.0 
-I/usr/include/libsoup-2.4 -I/usr/include/libxml2 -I/usr/include/fwupd-1 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -std=c99 
-fstack-protector-strong -Waggregate-return -Warray-bounds -Wcast-align 
-Wclobbered -Wdeclaration-after-statement -Wempty-body -Wex
 tra -Wformat=2 -Wformat-nonliteral -Wformat-security -Wformat-signedness 
-Wignored-qualifiers -Wimplicit-function-declaration -Winit-self -Winline 
-Wmissing-declarations -Wmissing-format-attribute -Wmissing-include-dirs 
-Wmissing-noreturn -Wmissing-parameter-type -Wmissing-prototypes 
-Wnested-externs -Wno-discarded-qualifiers -Wno-missing-field-initializers 
-Wno-strict-aliasing -Wno-suggest-attribute=format -Wno-unused-parameter 
-Wold-style-definition -Woverride-init -Wpacked -Wpointer-arith 
-Wredundant-decls -Wreturn-type -Wshadow -Wsign-compare -Wstrict-aliasing 
-Wstrict-prototypes -Wswitch-default -Wtype-limits -Wundef -Wuninitialized 
-Wunused-but-set-variable -Wwrite-strings -D_XOPEN_SOURCE=500 
-DI_KNOW_THE_PACKAGEKIT_GLIB2_API_IS_SUBJECT_TO_CHANGE 
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread 
'-DG_LOG_DOMAIN="GsPluginFwupd"
 ' '-DLOCALPLUGINDIR="/<>/obj-x86_64-linux-gnu/plugins/fwupd"' 
-MMD -MQ 'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o' -MF 
'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o.d' -o 
'plugins/fwupd/gs_plugin_fwupd@sha/gs-plugin-fwupd.c.o' -c 
../plugins/fwupd/gs-plugin-fwupd.c
../plugins/fwupd/gs-plugin-fwupd.c:153:8: error: unknown type name 
'FwupdResult'; did you mean 'FwupdRemote'?
FwupdResult *res,
^~~
FwupdRemote
../plugins/fwupd/gs-plugin-fwupd.c: In function 'gs_plugin_fwupd_setup_remote':
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: implicit declaration of 
function 'fwupd_remote_get_filename_asc'; did you mean 
'fwupd_remote_get_filename_cache'? [-Wimplicit-function-declaration]
   fwupd_remote_get_filename_asc (remote),
   ^
   fwupd_remote_get_filename_cache
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: nested extern declaration 
of 'fwupd_remote_get_filename_asc' [-Wnested-externs]
../plugins/fwupd/gs-plugin-fwupd.c:252:11: warning: passing argument 2 of 
'gs_utils_get_cache_filename' makes pointer from integer without a cast 
[-Wint-conversion]
In file included from ../plugins/fwupd/../../lib/gnome-software.h:36:0,
 from ../plugins/fwupd/gs-plugin-fwupd.c:31:
../plugins/fwupd/../../lib/gs-utils.h:59:9: note: expected 'const gchar * {aka 
const char *}' but argument is of type 'int'
 gchar  *gs_utils_get_cache_filename (const gchar *kind,
 ^~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:28:0,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/fwupd-1/libfwupd/fwupd-client.h:25,
 from /usr/include/fwupd-1/fwupd.h:32,
 from ../plugins/fwupd/gs-plugin-fwupd.c:24:
../plugins/fwupd/gs-plugin-fwupd.c: In function 'gs_plugin_setup':
../plugins/fwupd/gs-plugin-fwupd.c:315:18: error: 
'gs_plugin_fwupd_device_changed_cb' undeclared (first use in this function); 
did you mean 'gs_plugin_fwupd_changed_cb'?
  G_CALLBACK (gs_plugin_fwupd_device_changed_cb), plugin);
  ^
/usr/include/glib-2.0/gobject/gsignal.h:475:60: note: in definition of macro 
'g_signal_connect'
 g_signal_connect_data ((instance), (detailed_signal), (c_handler), (data), 
NULL, (GConnectFlags) 0)
^
../plugins/fwupd/gs-plugin-fwupd.c:315:6: note: in expansion of macro 
'G_CALLBACK'
  G_CALLBACK (gs_plugin_fwupd_device_changed_cb), plugin);
  ^~
../plugins/fwupd/gs-plugin-fwupd.c:315:18: note: each undeclared identifier is 
reported only once for each 

Bug#879002: Should the package be removed?

[Raphael Hertzog]

Source: libpam4j
Severity: serious

Hello,

I just came across libpam4j while handlinge CVE-2017-12197 and I noticed
that:
- the package has not seen an update since 2012
- the package has no reverse dependency in Debian
- upstream seems to have disappeared (the current Homepage URL is dead
  and I could not find any other upstream code repository)

So I would suggest to drop this package from Debian. If you agree, please
reassign the bug to ftp.debian.org and retitle it into "RM: libpam4j --
ROM; unmaintained, no reverse dependency"

Thank you.
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#879001: CVE-2017-12197: libpam4j: Account check bypass

[Raphael Hertzog]

Source: libpam4j
Version: 1.4-2
Severity: grave
Tags: security

Hi,

the following vulnerability was published for libpam4j.

CVE-2017-12197[0]: libpam4j: Account check bypass

PAM.authentication() does not call pam_acct_mgmt(). As a consequence, the
PAM account is not properly verified. Any user with a valid password but
with deactivated or disabled account is able to log in.

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

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-2017-12197
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12197

Please adjust the affected versions in the BTS as needed.



-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#878999: protobuf FTBFS on armhf/i386: testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... Segmentation fault

[Adrian Bunk]

Source: protobuf
Version: 3.0.0-9.1
Severity: serious

protobuf FTBFS on armhf/i386:

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

...
testMapIterationClearMessage (google.protobuf.internal.message_test.Proto3Test) 
... ok
testMapValidAfterFieldCleared 
(google.protobuf.internal.message_test.Proto3Test) ... ok
testMapsAreMapping (google.protobuf.internal.message_test.Proto3Test) ... ok
testMergeFrom (google.protobuf.internal.message_test.Proto3Test) ... 
Segmentation fault
debian/rules:74: recipe for target 'override_dh_auto_test-arch' failed
make[1]: *** [override_dh_auto_test-arch] Error 139


In reproducible builds the same segfault happens on armhf, but not on i386:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/protobuf.html

Bug#878968:

[Giacomo Graziosi]

I can confirm both the bug and the workaround.

Bug#876033: primusrun doesn't find libGL.so.1

[Luca Boccassi]

On Tue, 2017-10-17 at 22:43 +0200, devfra wrote:
> On martedì 17 ottobre 2017 20:53:49 CEST Luca Boccassi wrote:
> > What's the output of:
> > 
> > dpkg -l | grep 375.82-5
> 
> $ dpkg -l | grep 375.82-5
> ii  libegl-nvidia0:amd64375.82-5   amd64   NVIDIA binary EGL
> library
> ii  libegl-nvidia0:i386 375.82-5   i386NVIDIA binary EGL
> library
> ii  libgl1-nvidia-glx:amd64 375.82-5   amd64   NVIDIA binary
> OpenGL/GLX...
> ii  libglx-nvidia0:amd64375.82-5   amd64   NVIDIA binary GLX
> library
> ii  libglx-nvidia0:i386 375.82-5   i386NVIDIA binary GLX
> library
> ii  libnvidia-eglcore:amd64 375.82-5   amd64   NVIDIA binary EGL
> core l...
> ii  libnvidia-eglcore:i386  375.82-5   i386NVIDIA binary EGL
> core l...
> ii  libnvidia-glcore:amd64  375.82-5   amd64   NVIDIA binary
> OpenGL/GLX...
> ii  libnvidia-glcore:i386   375.82-5   i386NVIDIA binary
> OpenGL/GLX...
> ii  libnvidia-ml1:amd64 375.82-5   amd64   NVIDIA Management
> Librar...
> ii  nvidia-alternative  375.82-5   amd64   allows the
> selection of ...
> ii  nvidia-egl-common   375.82-5   amd64   NVIDIA binary EGL
> driver...
> ii  nvidia-egl-icd:amd64375.82-5   amd64   NVIDIA EGL
> installable c...
> ii  nvidia-egl-icd:i386 375.82-5   i386NVIDIA EGL
> installable c...
> ii  nvidia-kernel-dkms  375.82-5   amd64   NVIDIA binary
> kernel mod...
> ii  nvidia-kernel-support   375.82-5   amd64   NVIDIA binary
> kernel mod...
> ii  nvidia-legacy-check 375.82-5   amd64   check for NVIDIA
> GPUs re...
> ii  nvidia-vdpau-driver:amd64   375.82-5   amd64   Video Decode and
> Present...
> ii  xserver-xorg-video-nvidia   375.82-5   amd64   NVIDIA binary Xorg
> driver
> 
> Thanks.

I think there's a couple missing i386 packages, try to install the
nvidia-driver-libs:i386 metapackage to pull them in

-- 
Kind regards,
Luca Boccassi

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

Bug#878980: belenios FTBFS with OCaml 4.05.0

[Adrian Bunk]

Source: belenios
Version: 1.4+dfsg-2
Severity: serious

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

...
ocamlfind ocamlopt -c -g -annot -safe-string -w A-4-6-29-44-48 -package uuidm 
-package atdgen -package yojson -I src/lib -o src/lib/election.cmx 
src/lib/election.ml
+ ocamlfind ocamlopt -c -g -annot -safe-string -w A-4-6-29-44-48 -package uuidm 
-package atdgen -package yojson -I src/lib -o src/lib/election.cmx 
src/lib/election.ml
File "src/lib/election.ml", line 1:
Error: The implementation src/lib/election.ml
   does not match the interface src/lib/election.cmi:
   ...
   At position module MakeSimpleMonad(G) : 
   Values do not match:
 val fold : (unit -> '_a -> 'b -> unit -> 'b) -> 'b -> unit -> 'b
   is not included in
 val fold : (unit -> elt -> 'a -> 'a t) -> 'a -> 'a t
   File "src/lib/election.ml", line 55, characters 6-10:
 Actual declaration
Command exited with code 2.
Makefile:2: recipe for target 'minimal' failed
make[2]: *** [minimal] Error 10

Bug#878983: cduce FTBFS with OCaml 4.05.0

[Adrian Bunk]

Source: cduce
Version: 0.6.0-5
Severity: serious
Tags: buster sid

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

...
Build types/atoms.cmx
Build types/normal.cmi
Build types/normal.cmx
File "types/normal.ml", line 1:
Error: The implementation types/normal.ml
   does not match the interface types/normal.cmi:
   ...
   At position module Make(X1)(X2) : 
   Values do not match:
 val pi1 : (X1.t * '_a) list -> X1.t
   is not included in
 val pi1 : t -> X1.t
   File "types/normal.ml", line 80, characters 6-9: Actual declaration
Makefile.distrib:317: recipe for target 'types/normal.cmx' failed
make[2]: *** [types/normal.cmx] Error 2

Bug#878398: [debian-mysql] Bug#878398: Security fixes from the October 2017 CPU

[Lars Tangvald]

CVE List for 5.7:

CVE-2017-3731
CVE-2017-10155
CVE-2017-10165
CVE-2017-10167
CVE-2017-10227
CVE-2017-10268
CVE-2017-10276
CVE-2017-10279
CVE-2017-10283
CVE-2017-10284
CVE-2017-10286
CVE-2017-10294
CVE-2017-10296
CVE-2017-10311
CVE-2017-10313
CVE-2017-10314
CVE-2017-10320
CVE-2017-10365
CVE-2017-10379
CVE-2017-10384

--
Lars

On 13. okt. 2017 12:34, Norvald H. Ryeng wrote:

Source: mysql-5.7
Version: 5.7.18-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2017 will be released on
Tuesday, October 17. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.7.20.

The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.alioth.debian.org_cgi-2Dbin_mailman_listinfo_pkg-2Dmysql-2Dmaint=DwICAg=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=HPjEzLhETPj8fl9HCxxISaaV3f5tXDpGXDR3R2IELxg=7DikT9z1InjqtpgXAqPEvoncum9MvgyB0I0VEBgUepI=tXNrK89Tn-ffN2T5k0Ak03vcAwEkRO5OD3F-IEB8PjU=

Bug#878817: luajit: Please drop mips64el again

[James Cowgill]

Control: affects -1 - src:knot-resolver

Hi,

On 16/10/17 21:23, Adrian Bunk wrote:
> Source: luajit
> Version: 2.1.0~beta3+dfsg-5
> Severity: serious
> Control: affects -1 src:neovim src:knot-resolver
> 
> neovim and knot-resolver FTBFS with luajit 2.1.0~beta3+dfsg-5:
> https://buildd.debian.org/status/logs.php?pkg=neovim=mips64el
> https://buildd.debian.org/status/logs.php?pkg=knot-resolver=mips64el
> 
> knot-resolver FTBFS on the buildd, but builds for me on eller.
> 
> 21:10 < jcowgill> bunk: not sure, but i notice both failed on loongsons
> 21:10 < jcowgill> gcc has a few workarounds disabling some instructions since 
> loongson doesn't quite implement the mips isa properly
> 21:14 < bunk> jcowgill: that sounds like possibly related to a jit failing on 
> this hw
> 
> Instead of shipping code that is strongly suspected to be nonworking
> on part of the supported hardware of mips64el, it is IMHO better to
> disable luajit on mips64el again.

It turns out the knot-resolver build failure had nothing to do with
luajit (see #878976). I haven't investigated the neovim failure
thoroughly yet.

James



signature.asc
Description: OpenPGP digital signature

Bug#867560: further investigation results

[gustavo panizzo]

Hi

I did investigate more about this bug, and I found that if I preload the
modules that iptables needs the firewall is always setup correctly.

--
IRC: gfa
GPG: 0X44BB1BA79F6C6333

Bug#878972: gitsome build depends on python3 (< 3.6) but 3.6.3-1 is to be installed 收件匣 x

[林上智]

Hi,

Thank you for reporting the issue.

Since upstream of gitsome [1] did not support python 3.6, I will
co-work with them to figure out the solution.

ref:
[1] https://github.com/donnemartin/gitsome/issues/105

--

SZ Lin (林上智) , http://people.debian.org/~szlin

Debian Developer, debian.org.tw Administrator

4096R/ 178F 8338 B314 01E3 04FC 44BA A959 B38A 9561 F3F9

Processed: Re: Bug#878817: luajit: Please drop mips64el again

[Debian Bug Tracking System]

Processing control commands:

> affects -1 - src:knot-resolver
Bug #878817 [src:luajit] luajit: Please drop mips64el again
Removed indication that 878817 affects src:knot-resolver

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

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Luca Boccassi]

On 18 October 2017 07:32:41 BST, Hendrik Tews  wrote:
>Package: libglvnd0-nvidia
>Version: 375.82-5
>Severity: critical
>
>Dear Maintainer,
>
>after updating some packages this morning, X11 did not come up
>any more and the system was completely unusable. Apparently gdm
>was restarting continuously, making it impossible to enter
>anything in a terminal window. I needed to boot in recovery mode
>to get access again.
>
>The syslog contains
>
>/usr/lib/gdm3/gdm-x-session[2703]: (EE) Failed to load
>/usr/lib/xorg/modules/extensions/libglx.so:
>/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol:
>_glapi_tls_Current
>
>and I get the same undefined symbol error when I try startx.
>
>After installing libglvnd0 (and purging libglvnd0-nvidia)
>everything is fine again. In contrast to what is reported in
>https://lists.debian.org/debian-kde/2017/10/msg00028.html, the
>problem appears again, when I reinstall libglvnd0-nvidia.
>
>Bye,
>
>Hendrik

Hi,

Please attach the full report by running

reportbug --template nvidia-driver

 On the affected machine and pasting the output.

Kind regards,
Luca Boccassi



signature.asc
Description: PGP signature

Processed: bug 875396 is forwarded to https://github.com/haskell/vector/issues/186

[Debian Bug Tracking System]

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

> forwarded 875396 https://github.com/haskell/vector/issues/186
Bug #875396 [src:haskell-vector] haskell-vector: FTBFS on any-i386
Set Bug forwarded-to-address to 'https://github.com/haskell/vector/issues/186'.
> thanks
Stopping processing here.

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

Bug#878972: gitsome build depends on python3 (< 3.6) but 3.6.3-1 is to be installed

[Adrian Bunk]

Source: gitsome
Version: 0.7.0-1
Severity: serious

The following packages have unmet dependencies:
 builddeps:gitsome : Depends: python3 (< 3.6) but 3.6.3-1 is to be installed

Processed: Remove incorrect found version

[Debian Bug Tracking System]

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

> notfound 878948 13.0.6-1
Bug #878948 [libgl1-mesa-glx] Couldn't open libGL.so.1: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current
No longer marked as found in versions mesa/13.0.6-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#877075: sikulix: hard coded dependency on libopencv2.4-java

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 sikulix: hard coded dependency on libopencv3.2-java
Bug #877075 [libsikulixapi-java] sikulix: hard coded dependency on 
libopencv2.4-java
Changed Bug title to 'sikulix: hard coded dependency on libopencv3.2-java' from 
'sikulix: hard coded dependency on libopencv2.4-java'.
> unblock 841733 by -1
Bug #841733 [release.debian.org] transition: opencv
841733 was blocked by: 878793 841411 865831 841246 841416 861122 861270 841413 
841370 841407 841287 861194 841245 841408 877075 878549 812032 841412 841410 
841406 841405 877073 841409
841733 was not blocking any bugs.
Removed blocking bug(s) of 841733: 877075
> severity -1 normal
Bug #877075 [libsikulixapi-java] sikulix: hard coded dependency on 
libopencv3.2-java
Severity set to 'normal' from 'serious'

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

Bug#878843: util-linux: fsck on btrfs /home hangs, stalling boot

[Bernhard Schmidt]

Am 17.10.2017 um 18:10 schrieb Michael Biebl:

Hi Michael,

> Bernhard, could you try to run a git bisect to find the relevant change
> which broke fsck for you.
> https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/log/disk-utils/fsck.c?h=stable/v2.30
> 
> There aren't that many changes for fsck.

There are only two commits over 2.29 and they don't look related at all.
Maybe in a library. I'll try to find time to bisect it on the weekend or
at least try to make a testcase on a fresh VM.

I did some more tests today and found the reason.

util-linux 2.29 + systemd 234-3: works fine
util-linux 2.29 + systemd 235-2: works fine
util-linux 2.30 + systemd 234-3: boot stalls completely
util-linux 2.30 + systemd 235-2: login prompt eventually appears, root
login is possible, user login hangs

Accessing /home leads to a blocked process. The reason is that (for
numerous years, due to reasons I don't remember) I had
x-systemd.automount in my fstab for /home

/dev/mapper/homecrypt  /home   btrfs   relatime,x-systemd.automount0
  2

so at this point /home is already "mounted" with autofs.

systemd-1 on /home type autofs
(rw,relatime,fd=45,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=12282)

but access is blocked until the real fs is mounted. Which will only
happen after the fsck has completed, which is blocked open()ing the
mountpoint.

Removing x-systemd.automount fixes this behaviour.

Bernhard

Bug#877075: sikulix: hard coded dependency on libopencv2.4-java

[Gilles Filippini]

Control: retitle -1 sikulix: hard coded dependency on libopencv3.2-java
Control: unblock 841733 by -1
Control: severity -1 normal

On Wed, 18 Oct 2017 01:16:53 +0200 Gilles Filippini  wrote:
> Mattia Rizzolo a écrit le 18/10/2017 à 01:11 :
> > On Wed, Oct 18, 2017 at 12:58:32AM +0200, Gilles Filippini wrote:
> >> On Tue, 17 Oct 2017 12:48:29 +0200 Mattia Rizzolo  
> >> wrote:
> >>> On Tue, Oct 17, 2017 at 10:26:11AM +0200, Gilles Filippini wrote:
>  How about mavenizing OpenCV Java lib so that ${maven:Depends} would find
>  out the right libopencvX.Y-java dependency?
> >>>
> >>> I'll happily accept patches for that.
> >>
> >> Attached.
> > 
> > Thank you!
> > 
> > It will definitely be part of the next upload, although I'd like to
> > avoid to do a 4th upload in just 3 days… OpenCV is not exactly light,
> > there are several architectures where it takes more than 12h to build.
> > Could you consider keeping the hardconded lib just a little longer and
> > bump the version?
> 
> Will do it by tomorrow.

Done.

_g.



signature.asc
Description: OpenPGP digital signature

Bug#878837: sambamba: FTBFS with ldc 1.4.0

[Andreas Tille]

Hi Matthias,

as usual I do not have the slightest idea what to do.  Could I again ask
for your kind help?  Feel free to commit right to Git if you have any
patch.

Thanks a lot

 Andreas.

On Tue, Oct 17, 2017 at 12:42:28PM +0900, Nobuhiro Iwamatsu wrote:
> Package: sambamba
> Version: 0.6.6-1
> Severity: serious
> Tags: buster sid
> Justification: FTBFS on amd64
> 
> Hi,
> 
> Dear Maintainer,
> 
> sambamba FTBFS with ldc 1.4.0 on sid.
> 
> https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.6.6-1%2Bb1=1507088043=0
> 
> -
> [1/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
> -I/usr/include/htslib -enable-color -O3 -g -release  -of
> 'sambamba@exe/main.d.o' -c ../main.d
> ../sambamba/utils/common/readstorage.d(22): Deprecation: module
> std.c.stdlib is deprecated - Import core.stdc.stdlib or
> core.sys.posix.stdlib instead
> ../sambamba/utils/common/readstorage.d(23): Deprecation: module
> std.c.string is deprecated - Import core.stdc.string instead
> ../sambamba/sort.d(45): Deprecation: module std.c.stdlib is deprecated
> - Import core.stdc.stdlib or core.sys.posix.stdlib instead
> ../sambamba/sort.d(46): Deprecation: module std.c.string is deprecated
> - Import core.stdc.string instead
> ../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
> deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
> ../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
> is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
> instead
> ../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
> is deprecated, use "not duplicate and " ~ "not failed_quality_control"
> instead
> [2/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
> -I/usr/include/htslib -enable-color -O3 -g -release  -of
> 'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
> [3/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
> -I/usr/include/htslib -enable-color -O3 -g -release  -of
> 'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
> FAILED: sambamba@exe/sambamba_depth.d.o
> ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
> -enable-color -O3 -g -release  -of 'sambamba@exe/sambamba_depth.d.o'
> -c ../sambamba/depth.d
> ../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
> is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
> instead
> ../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
> is deprecated, use "not duplicate and " ~ "not failed_quality_control"
> instead
> ldc2: /build/ldc-1.4.0/ir/irvar.cpp:44: IrGlobal*
> getIrGlobal(VarDeclaration*, bool): Assertion `decl->ir->irGlobal !=
> NULL' failed.
> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys15PrintStackTraceERNS_11raw_ostreamE+0x1a)[0x7f4948132cea]
> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(_ZN4llvm3sys17RunSignalHandlersEv+0x56)[0x7f4948130fd6]
> /usr/lib/x86_64-linux-gnu/libLLVM-5.0.so.1(+0x86e0f3)[0x7f49481310f3]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x110c0)[0x7f49472ab0c0]
> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcf)[0x7f494647bfff]
> /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f494647d42a]
> /lib/x86_64-linux-gnu/libc.so.6(+0x2be67)[0x7f4946474e67]
> /lib/x86_64-linux-gnu/libc.so.6(+0x2bf12)[0x7f4946474f12]
> -
> 
> Perhaps this is not a problem with this package, but I think it is a
> problem of Dlang.
> Please forward if necessary.
>  https://github.com/ldc-developers/ldc/issues/2357
> 
> Best regards,
>   Nobuhiro
> 
> 
> -- 
> Nobuhiro Iwamatsu
>iwamatsu at {nigauri.org / debian.org}
>GPG ID: 40AD1FA6
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#877073: marked as done (sikulix: FTBFS with OpenCV 3.2)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 07:49:51 +
with message-id 
and subject line Bug#877073: fixed in sikulix 1.1.1-3
has caused the Debian Bug report #877073,
regarding sikulix: FTBFS with OpenCV 3.2
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.)


-- 
877073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sikulix
Version: 1.1.1-1
Severity: important
Control: block 841733 by -1

Dear maintainer,

sikulix fails to build with OpenCV 3.2 (as found in experimental).
Note that the previous version of sikulix (1.1.0-2) builds just fine
with OpenCV 3.2.

[INFO] --- exec-maven-plugin:1.6.0:exec (make-all) @ sikulixlibslux ---
make[1]: Entering directory 
'/build/sikulix-1.1.1/Libslux/src/main/resources/srcnativelibs/Vision'
/bin/bash ./libtool  --tag=CXX   --mode=compile x86_64-linux-gnu-g++ 
-DPACKAGE_NAME=\"sikulix-vision-proxy\" 
-DPACKAGE_TARNAME=\"sikulix-vision-proxy\" -DPACKAGE_VERSION=\"1.0.1\" 
-DPACKAGE_STRING=\"sikulix-vision-proxy\ 1.0.1\" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
-DLT_OBJDIR=\".libs/\" -DPACKAGE=\"sikulix-vision-proxy\" -DVERSION=\"1.0.1\" 
-DHAVE_TESSERACT_CAPI_H=1 -DHAVE_LIBTESSERACT=1 -I.  
-I"/usr/lib/jvm/java-8-openjdk-amd64"/include -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/lib/jvm/default-java/include/linux  -g -O2 
-fdebug-prefix-map=/build/sikulix-1.1.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -MT libVisionProxy_la-cvgui.lo -MD -MP -MF 
.deps/libVisionProxy_la-cvgui.Tpo -c -o libVisionProxy_la-cvgui.lo `test -f 
'cvgui.cpp' || echo './'`cvgui.cpp
libtool: compile:  x86_64-linux-gnu-g++ -DPACKAGE_NAME=\"sikulix-vision-proxy\" 
-DPACKAGE_TARNAME=\"sikulix-vision-proxy\" -DPACKAGE_VERSION=\"1.0.1\" 
"-DPACKAGE_STRING=\"sikulix-vision-proxy 1.0.1\"" -DPACKAGE_BUGREPORT=\"\" 
-DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 
-DLT_OBJDIR=\".libs/\" -DPACKAGE=\"sikulix-vision-proxy\" -DVERSION=\"1.0.1\" 
-DHAVE_TESSERACT_CAPI_H=1 -DHAVE_LIBTESSERACT=1 -I. 
-I/usr/lib/jvm/java-8-openjdk-amd64/include -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/lib/jvm/default-java/include/linux -g -O2 
-fdebug-prefix-map=/build/sikulix-1.1.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -MT libVisionProxy_la-cvgui.lo -MD -MP -MF 
.deps/libVisionProxy_la-cvgui.Tpo -c cvgui.cpp  -fPIC -DPIC -o 
.libs/libVisionProxy_la-cvgui.o
cvgui.cpp: In static member function 'static void 
cvgui::linkLineBlobsIntoPagagraphBlobs(std::vector&, 
std::vector&)':
cvgui.cpp:392:30: error: no matching function for call to 
'sort(std::vector&, bool (&)(Blob, Blob))'
sort(blobs, sort_blob_by_y);
  ^
In file included from /usr/include/opencv2/core/core.hpp:48:0,
 from opencv.hpp:9,
 from cvgui.h:9,
 from cvgui.cpp:6:
/usr/include/opencv2/core.hpp:1823:19: note: candidate: void 
cv::sort(cv::InputArray, cv::OutputArray, int)
 CV_EXPORTS_W void sort(InputArray src, OutputArray dst, int flags);
   ^~~~
/usr/include/opencv2/core.hpp:1823:19: note:   candidate expects 3 arguments, 2 
provided
In file included from /usr/include/c++/7/algorithm:62:0,
 from /usr/include/opencv2/core/base.hpp:55,
 from /usr/include/opencv2/core.hpp:54,
 from /usr/include/opencv2/core/core.hpp:48,
 from opencv.hpp:9,
 from cvgui.h:9,
 from cvgui.cpp:6:
/usr/include/c++/7/bits/stl_algo.h:4856:5: note: candidate: template void std::sort(_RAIter, _RAIter, _Compare)
 sort(_RandomAccessIterator __first, _RandomAccessIterator __last,
 ^~~~
/usr/include/c++/7/bits/stl_algo.h:4856:5: note:   template argument 
deduction/substitution failed:
cvgui.cpp:392:30: note:   deduced conflicting types for parameter '_RAIter' 
('std::vector' and 'bool (*)(Blob, Blob)')
sort(blobs, sort_blob_by_y);
  ^
In file included from /usr/include/c++/7/algorithm:62:0,
 from /usr/include/opencv2/core/base.hpp:55,
 from /usr/include/opencv2/core.hpp:54,
 from 

Bug#877824: marked as done (gcc-snapshot build depends on removed transitional package realpath)

[Debian Bug Tracking System]

Your message dated Wed, 18 Oct 2017 10:38:03 +0300
with message-id <20171018073802.p2pp3ohegae7xo4u@localhost>
and subject line Fixed in 20171017-1
has caused the Debian Bug report #877824,
regarding gcc-snapshot build depends on removed transitional package realpath
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.)


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

gcc-snapshot build depends on the transitional package realpath, 
removed in coreutils 8.28-1.

The realpath program is part of the
(essential) coreutils package.
--- End Message ---
--- Begin Message ---
Version: 20171017-1

20171017-1 has
  coreutils (>= 2.26) | realpath (>= 1.9.12)

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: resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #869404 [src:resiprocate] resiprocate: CVE-2017-11521: Adding too many 
media connections may lead to memory exhaustion
Added tag(s) patch.

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

Bug#869404: resiprocate: CVE-2017-11521: Adding too many media connections may lead to memory exhaustion

[Petter Reinholdtsen]

Control: tags -1 + patch

This issue has caused resiprocate to be thrown out of testing.  This is
unfortunate, as it is used by the FreedomBox, and thus it is no
longer possible to set up a Buster based Freedombox with SIP support.

According to the upstream git repo, the 5 line patch in
https://github.com/resiprocate/resiprocate/commit/881cb0c80e23193ea2bdaf720de9b3310f52a0a6
 >
solve the problem.  Perhaps it should be pulled from upstream
until they find time to make a new release?

-- 
Happy hacking
Petter Reinholdtsen

Bug#878288: electrum: AssertionError when trying to open my wallet

[Kiko Piris]

I guess this bug is the same one than #878288.  And, as Juhapekka
Tolvanen points out, it is related to segwit.

I second his petition: Please update the package to the latest upstream
version.

Thanks.

-- 
Kiko

Bug#878968: libglvnd0-nvidia: undefined symbol: _glapi_tls_Current makes system unusable

[Hendrik Tews]

Package: libglvnd0-nvidia
Version: 375.82-5
Severity: critical

Dear Maintainer,

after updating some packages this morning, X11 did not come up
any more and the system was completely unusable. Apparently gdm
was restarting continuously, making it impossible to enter
anything in a terminal window. I needed to boot in recovery mode
to get access again.

The syslog contains

/usr/lib/gdm3/gdm-x-session[2703]: (EE) Failed to load 
/usr/lib/xorg/modules/extensions/libglx.so: 
/usr/lib/x86_64-linux-gnu/libGL.so.1: undefined symbol: _glapi_tls_Current

and I get the same undefined symbol error when I try startx.

After installing libglvnd0 (and purging libglvnd0-nvidia)
everything is fine again. In contrast to what is reported in
https://lists.debian.org/debian-kde/2017/10/msg00028.html, the
problem appears again, when I reinstall libglvnd0-nvidia.

Bye,

Hendrik


-- Package-specific info:
uname -a:
Linux cert 4.13.0-1-amd64 #1 SMP Debian 4.13.4-1 (2017-10-01) x86_64 GNU/Linux

/proc/version:
Linux version 4.13.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
6.4.0 20170920 (Debian 6.4.0-7)) #1 SMP Debian 4.13.4-1 (2017-10-01)

lspci 'VGA compatible controller [0300]':
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 
[8086:191b] (rev 06) (prog-if 00 [VGA controller])
Subsystem: Lenovo HD Graphics 530 [17aa:5056]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Oct 17 21:58 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Oct 17 21:58 /dev/dri/renderD128

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Oct 17 21:58 pci-:00:02.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Oct 17 21:58 pci-:00:02.0-render -> ../renderD128
video:x:44:tews

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root 15 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1 -> libEGL.so.1.0.0
-rw-r--r-- 1 root root  76344 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libEGL.so.1.0.0
lrwxrwxrwx 1 root root 14 Sep 28 22:04 /usr/lib/x86_64-linux-gnu/libGL.so.1 
-> libGL.so.1.0.0
-rw-r--r-- 1 root root 567624 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
lrwxrwxrwx 1 root root 18 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2 -> libGLESv2.so.2.0.0
-rw-r--r-- 1 root root  55616 Sep 28 22:04 
/usr/lib/x86_64-linux-gnu/libGLESv2.so.2.0.0
-rw-r--r-- 1 root root 29 Jul  7 07:31 
/usr/lib/xorg/modules/extensions/libglx.so
-rw-r--r-- 1 root root   5883 Oct 17 09:07 /var/log/Xorg.0.log

/etc/modprobe.d:
total 24
drwxr-xr-x   2 root root  4096 Sep 18 13:14 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   154 Nov 30  2016 amd64-microcode-blacklist.conf
-rw-r--r--   1 root root   154 Nov  9  2016 intel-microcode-blacklist.conf


/etc/modules-load.d:
-rw-r--r-- 1 root root  195 Mar  1  2017 /etc/modules

/etc/modules-load.d/:
total 20
drwxr-xr-x   2 root root  4096 Oct 17 08:42 .
drwxr-xr-x 162 root root 12288 Oct 17 21:55 ..
-rw-r--r--   1 root root   119 Jan 19  2017 cups-filters.conf
lrwxrwxrwx   1 root root10 Oct 11 00:46 modules.conf -> ../modules


Files from nvidia-installer:

Config and logfiles:

<< /home/tews/.local/share/xorg/Xorg.0.log >>
[32.985] 
X.Org X Server 1.19.3
Release Date: 2017-03-15
[32.991] X Protocol Version 11, Revision 0
[32.992] Build Operating System: Linux 4.9.0-3-amd64 x86_64 Debian
[32.994] Current Operating System: Linux cert 4.13.0-1-amd64 #1 SMP Debian 
4.13.4-1 (2017-10-01) x86_64
[32.994] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.13.0-1-amd64 
root=/dev/mapper/cert--vg-root1 ro single
[32.998] Build Date: 07 July 2017  06:22:09AM
[33.000] xorg-server 2:1.19.3-2 (https://www.debian.org/support) 
[33.001] Current version of pixman: 0.34.0
[33.005]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[33.005] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[33.012] (==) Log file: "/home/tews/.local/share/xorg/Xorg.0.log", Time: 
Tue Oct 17 21:58:39 2017
[33.019] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[33.024] (==) No Layout section.  Using the first Screen section.
[33.024] (==) No screen section available. Using defaults.
[33.024] (**) |-->Screen "Default Screen Section" (0)
[33.024] (**) |   |-->Monitor ""
[33.024] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[33.024] (==) Automatically adding devices
[33.024] (==) Automatically enabling 

Bug#877322: git-buildpackage autoremoval

[Guido Günther]

Hi,
On Tue, Oct 17, 2017 at 10:27:03PM +0100, Ian Jackson wrote:
> Guido Günther writes ("Re: Bug#877322: git-buildpackage autoremoval"):
> > On Tue, Oct 17, 2017 at 02:57:33PM +0100, Ian Jackson wrote:
> > > This bug means that the autoremoval robot wants to remove
> > > git-buildpackage.  I'm getting mails about it planning to remove dgit,
> > > to clear the way.
> > > 
> > > Do you intend to upload the docs change to sid soon ?
> > 
> > Yes, before the autoremoval for sure. Sorry for being a pain here but I
> > wanted to give gbp as much exposure as possible in experimental.
> 
> OK, fine.  Thanks for the reassurance.  If the deadline gets closer I
> may ping you again :-).

Sure. I have 1 more bug to go that affects 0.9.x but not 0.8.x that I
want to get done before moving to sid.
Cheers,
 -- Guido

Bug#878935: Unsatisfiable dependencies on !amd64

[Ritesh Raj Sarraf]

Thanks for reporting this bug.

On Tue, 2017-10-17 at 21:23 +0200, Alexander Kurtz wrote:
> Package: libbpfcc
> Version: 0.3.0-3
> Severity: serious
> Justification: Makes the package uninstallable on most architectures
> 
> Hi!
> 
> As [0] shows, libbpfcc has unsatisfiable dependencies on everything
> but
> amd64. This is because [1] is inherently wrong, "linux-headers-amd64"
> is of course only available on amd64, the other architectures have
> their own meta-packages [2]. Unfortunately there is (AFAIK) no good
> way
> to properly solve the "this package needs the current kernel headers
> installed" problem in Debian because
> 
>1. There are no (real or virtual) "linux-{image,headers}-
>   generic" packages (like in Ubuntu [3,4]) which have the same
> name on
>   all architectures.
>2. Even if there were such packages, there's no guarantee that
> "linux-
>   headers-generic" would point to the headers matching the
> *currently
>   running* kernel (which is what libbcc needs). In fact, with
> partial
>   upgrades, migrations from unstable to testing, upgraded-but-
> not-yet-
>   rebooted machines, etc., it is quite likely that libbpfcc will
> be
>   broken even if all its dependencies are fulfilled.
> 
> I therefore ask you to
> 
>1. Revert [1].
>2. Reopen [5] and put a note regarding the requirements of the
> kernel
>   headers in README.Debian and/or the package description.
>3. Talk to the Debian Linux maintainers to find a proper solution
> to
>   this problem. It's probably not going to be easy, but these
> kinds of
>   problems really deserve to be fixed properly.
> 

Yes. My bad. I completely missed about the dependency's limitation
across architectures. I'll fix it soon.

README.Debian is the wise way to deal with it. There were similar
situation with systemtap too.

> Yes, this sucks. I have run into #877925 myself and also thought that
> this should be simply solvable with a dependency. Oh, well, at least
> you may take comfort in the fact that others [6] have also run into
> this problem... ;-)
> 
> Best regards
> 
> Alexander Kurtz
> 
> [0] https://tracker.debian.org/pkg/bpfcc
> [1] https://anonscm.debian.org/git/collab-maint/bpfcc.git/commit/?id=
> f73049e48fd98dd01d4475f88f6b490e6a1b34bb
> [2] https://packages.debian.org/source/sid/linux
> [3] https://packages.ubuntu.com/artful/linux-image-generic
> [4] https://packages.ubuntu.com/artful/linux-headers-generic
> [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877925
> [6] https://anonscm.debian.org/git/pkg-dkms/dkms.git/tree/debian/cont
> rol#n24
-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System

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

Bug#878966: nagios-plugins-contrib FTBFS with libvarnishapi-dev 5.2.0-1

[Adrian Bunk]

Source: nagios-plugins-contrib
Version: 21.20170222
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/nagios-plugins-contrib.html

...
check_varnish.c: In function 'check_stats_cb':
check_varnish.c:193:33: error: 'const struct VSC_point' has no member named 
'section'
  assert(sizeof(tmp) > (strlen(pt->section->fantom->type) + 1 +
 ^
check_varnish.c:194:19: error: 'const struct VSC_point' has no member named 
'section'
  strlen(pt->section->fantom->ident) + 1 +
   ^
check_varnish.c:195:21: error: 'const struct VSC_point' has no member named 
'desc'; did you mean 'sdesc'?
  strlen(pt->desc->name) + 1));
 ^
...

Bug#878402: [debian-mysql] Bug#878402: Security fixes from the October 2017 CPU

[Lars Tangvald]

CVE List for 5.5:

CVE-2017-10268
CVE-2017-10378
CVE-2017-10379
CVE-2017-10384

--
Lars

On 13. okt. 2017 12:34, Norvald H. Ryeng wrote:

Source: mysql-5.5
Version: 5.5.57-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for October 2017 will be released on
Tuesday, October 17. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.5.58.

The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1] http://www.oracle.com/technetwork/security-advisory/cpuoct2017-3236626.html

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@lists.alioth.debian.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.alioth.debian.org_cgi-2Dbin_mailman_listinfo_pkg-2Dmysql-2Dmaint=DwICAg=RoP1YumCXCgaWHvlZYR8PQcxBKCX5YTpkKY057SbK10=HPjEzLhETPj8fl9HCxxISaaV3f5tXDpGXDR3R2IELxg=dEyRpHvFwIr1RTEceqC6iy_yrzTaCF3pVSkZ3JFfOe4=0PVa9j2CKG1CAypoPA9B0-RLcMLbS5ifPg3jULC2EMw=