Bug#878674: marked as done (nodejs segfaults when building d3-* with webpack)

[Debian Bug Tracking System]

Your message dated Sun, 7 Jan 2018 12:53:48 +0530
with message-id 
and subject line Re: Bug#878674: [Pkg-javascript-devel] Bug#878674: Bug#878674: 
nodejs segfaults when building d3-* with webpack
has caused the Debian Bug report #878674,
regarding nodejs segfaults when building d3-* with webpack
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.)


-- 
878674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: nodejs
version: 6.11.4~dfsg-1
severity: serious

I have noticed this failure when building multiple node-d3-* packages
(node-d3-zoom for example) and also installing gitlab 9.5 using webpack.

When building the same node-d3-zoom with nodejs
7.10.1-2nodesource1~stretch1 the build passed. Tried both in local
installation and using sbuild.

Also tested the same on my laptop and on a vm

babeljs src -d lib
src/constant.js -> lib/constant.js
src/event.js -> lib/event.js
src/noevent.js -> lib/noevent.js
src/transform.js -> lib/transform.js
src/zoom.js -> lib/zoom.js
babeljs index.js -d lib
index.js -> lib/index.js
sed -i 's/.\/src/./' lib/index.js
webpack --config debian/webpack.config.js index.js build/d3-zoom.js
--target=web --output-library=d3-zoom --output-library-target=umd
--module-bind 'js=babel-loader'
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Segmentation fault
make[1]: Leaving directory '/<>'
debian/rules:9: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Since babel and other dependencies are still in NEW, I have setup a repo
for packages still in NEW.

I have /usr/local/bin/sbuild-babel,
sbuild -A -s -d unstable --extra-repository='deb
https://people.debian.org/~praveen/babel sid main'
--extra-repository-key=/home/pravi/forge/debian/babel/repo/praveen.key.asc
$@

With nodejs from nodesource.com, the build passes, both locally and in
sbuild. For sbuild I have to pass --extra-package option and in
debian/rules, I have to add export NODE_PATH=/usr/lib/nodejs

node-d3-geo, node-d3-scale are other packages that segfaults.

All node-d3-* packages are in pkg-javascript team repo in alioth.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Thu, 4 Jan 2018 17:01:12 +0100 Mattia Rizzolo  wrote:
> This bug should probably also be closed at some point.

closing



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

Bug#866458: Please update Git repository mentioned in VCS fields

[Andreas Tille]

Hi,

I'd volunteer to work on this bug but the repository specified in
the VCS fields is not up to date.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#866435: I'd volunteer to fix this bug and would move the packaging to Git

[Andreas Tille]

Hi Steve,

it seems this package is not yet in Git.  I'd volunteer to move it
to Git and fix the bug.  Is this OK for you?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#866480: Bug was closed in 0.13.1-1

[Andreas Tille]

This bug was closed in the upload of 0.13.1-1 - no idea why it was not closed.

-- 
http://fam-tille.de

Bug#866446: What branch of the git repository is featuring the latest packaging

[Andreas Tille]

Hi,

I would volunteer to fix this bug but I do not understand the repository
layout.  It would be helpful if you would consider some standard layout
or at least drop some description which one is the recent packaging
branch.  Somehow debian-release looks promising but this is way out of
date.

Thanks for the enlightenment

  Andreas.

-- 
http://fam-tille.de

Bug#886518: debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?

[Helmut Grohne]

Package: debhelper
Version: 11.1
Severity: serious
Control: affects -1 + src:file
User: helm...@debian.org
Usertags: rebootstrap

Building file started to fail tonight. The new error comes from
debhelper and debhelper was the thing that was uploaded. Very likely,
debhelper is the culprit, but it might as well be wrong. You'll figure
out. :) Log below.

Helmut

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
Need to get 618 kB of source archives.
Get:1 http://proxy:/debian sid/main file 1:5.32-1 (dsc) [2124 B]
Get:2 http://proxy:/debian sid/main file 1:5.32-1 (tar) [584 kB]
Get:3 http://proxy:/debian sid/main file 1:5.32-1 (diff) [31.9 kB]
Fetched 618 kB in 0s (21.9 MB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'build/file-LiRAUZ/file-5.32' with 
'<>'
I: NOTICE: Log filtering will replace 'build/file-LiRAUZ' with '<>'

+--+
| Install build-essential  |
+--+


Setup apt archive
-

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in 
'/<>/resolver-tKaY3Y/apt_archive/sbuild-build-depends-core-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy
dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
Ign:1 copy:/<>/resolver-tKaY3Y/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-tKaY3Y/apt_archive ./ Release [957 B]
Ign:3 copy:/<>/resolver-tKaY3Y/apt_archive ./ Release.gpg
Get:4 copy:/<>/resolver-tKaY3Y/apt_archive ./ Sources [349 B]
Get:5 copy:/<>/resolver-tKaY3Y/apt_archive ./ Packages [433 B]
Fetched 1739 B in 0s (159 kB/s)
Reading package lists...
Reading package lists...

Install core build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 856 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 copy:/<>/resolver-tKaY3Y/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [856 B]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 856 B in 0s (0 B/s)
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 9824 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy_0.invalid.0_amd64.deb 
...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...

+--+
| Check architectures  |
+--+

Arch check ok (amd64 included in any all)

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper (>= 9.20141010~), dpkg-dev (>= 1.17.14~), 
dh-autoreconf, zlib1g-dev
Filtered Build-Depends: debhelper (>= 9.20141010~), dpkg-dev (>= 1.17.14~), 
dh-autoreconf, zlib1g-dev
dpkg-deb: building package 'sbuild-build-depends-file-dummy' in 
'/<>/resolver-tKaY3Y/apt_archive/sbuild-build-depends-file-dummy.deb'.
dpkg-scanpackages: warning: Packages in archive but missing from override file:
dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
sbuild-build-depends-file-dummy
dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
Ign:1 copy:/<>/resolver-tKaY3Y/apt_archive ./ InRelease
Get:2 copy:/<>/resolver-tKaY3Y/apt_archive ./ Release [963 B]
Ign:3 copy:/<>/resolver-tKaY3Y/apt_archive ./ Release.gpg
Get:4 copy:/<>/resolver-tKaY3Y/apt_archive ./ Sources [531 B]
Get:5 copy:/<>/resolver-tKaY3Y/apt_archive ./ Packages [604 B]
Fetched 2098 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install file build dependencies (apt-based resolver)


Installing build

Processed: debhelper makes packages FTBFS: dh: Internal error: debian/rules install-arch is a rules target, but it is not supported to be!?

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:file
Bug #886518 [debhelper] debhelper makes packages FTBFS: dh: Internal error: 
debian/rules install-arch is a rules target, but it is not supported to be!?
Added indication that 886518 affects src:file

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

Processed: affects 886474

[Debian Bug Tracking System]

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

> # See #886512 and #886510
> affects 886474 + nvidia-legacy-304xx-kernel-dkms broadcom-sta-dkms dkms
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Added indication that 886474 affects nvidia-legacy-304xx-kernel-dkms, 
broadcom-sta-dkms, and dkms
Added indication that 886510 affects nvidia-legacy-304xx-kernel-dkms, 
broadcom-sta-dkms, and dkms
> thanks
Stopping processing here.

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

Bug#886512: broadcom-sta-dkms: Should depends on libelf-devr

[Axel Beckert]

Control: retitle -1 broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:
Control: severity -1 important

Hi,

Yao Wei wrote:
> After I updated the kernel to 4.14.0, I found that the wl.ko is gone,
> and I tried to rebuild manually by dpkg-reconfigure which triggers dkms
> build.
> 
> But dkms logged the following error:
> 
> DKMS make.log for broadcom-sta-6.30.223.271 for kernel 4.14.0-3-amd64 (x86_64)
> Sun Jan  7 12:16:26 CST 2018
> /bin/sh: 1: [: Illegal number: 
> /bin/sh: 1: [: Illegal number: 

These errors do not cause the build to fail, but should be fixed
anyways.

> make[1]: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
> /usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot generate ORC 
> metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel 
> or elfutils-libelf-devel".  Stop.
[...]
> It seems libelf-dev is missing from the dependency.  IMHO this does not
> affect this dkms alone.

It indeed affects most or perhaps even all dkms-based packages.

> If any maintainer discovered this happens in all dkms modules,
> please reassign this bug to dkms or any suitable package.

It is already reported against linux-headers-4.14.0-3-amd64:
https://bugs.debian.org/886474

Since there actually two issues in this bug report, I do not reassign
and merge this bug report with #886474. Instead I retitle it to focus
on the other, non-release-critical issue and downgrade the severity
accordingly.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#886512: broadcom-sta-dkms: Should depends on libelf-devr

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:
Bug #886512 [broadcom-sta-dkms] broadcom-sta-dkms: Should depends on libelf-dev
Changed Bug title to 'broadcom-sta-dkms: /bin/sh: 1: [: Illegal number:' from 
'broadcom-sta-dkms: Should depends on libelf-dev'.
> severity -1 important
Bug #886512 [broadcom-sta-dkms] broadcom-sta-dkms: /bin/sh: 1: [: Illegal 
number:
Severity set to 'important' from 'grave'

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

Bug#886512: broadcom-sta-dkms: Should depends on libelf-dev

[魏銘廷]

Package: broadcom-sta-dkms
Version: 6.30.223.271-7
Severity: grave
Justification: renders package unusable

Hi,

After I updated the kernel to 4.14.0, I found that the wl.ko is gone,
and I tried to rebuild manually by dpkg-reconfigure which triggers dkms
build.

But dkms logged the following error:

DKMS make.log for broadcom-sta-6.30.223.271 for kernel 4.14.0-3-amd64 (x86_64)
Sun Jan  7 12:16:26 CST 2018
/bin/sh: 1: [: Illegal number: 
/bin/sh: 1: [: Illegal number: 
Wireless Extension is the only possible API for this kernel version
Using Wireless Extension API
KBUILD_NOPEDANTIC=1 make -C /lib/modules/4.14.0-3-amd64/build M=`pwd`
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
make[1]: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
/usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot generate ORC 
metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel".  Stop.
Makefile:146: recipe for target 'sub-make' failed
make[2]: *** [sub-make] Error 2
Makefile:8: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-4.14.0-3-amd64'
Makefile:177: recipe for target 'all' failed
make: *** [all] Error 2

It seems libelf-dev is missing from the dependency.  IMHO this does not
affect this dkms alone.  If any maintainer discovered this happens in
all dkms modules, please reassign this bug to dkms or any suitable
package.

Best regards,
Yao Wei

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

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

Versions of packages broadcom-sta-dkms depends on:
ii  dkms  2.3-3

Versions of packages broadcom-sta-dkms recommends:
ii  wireless-tools  30~pre9-12+b1

broadcom-sta-dkms suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#862851: marked as done (vblade-persist: Please switch to iproute2 package)

[Debian Bug Tracking System]

Your message dated Sun, 07 Jan 2018 04:19:05 +
with message-id 
and subject line Bug#862851: fixed in vblade-persist 0.6-3
has caused the Debian Bug report #862851,
regarding vblade-persist: Please switch to iproute2 package
to be marked as done.

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

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


-- 
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vblade-persist
Version: 0.6-2
Severity: normal
User: ah-ipro...@debian.org
Usertags: rm-transitional-iproute

Dear Maintainer,

Please update the vblade-persist package dependencies to use
'iproute2' instead of the transitional package 'iproute'.

The transition from the old iproute package name to iproute2 happened
in Debian Jessie, so the transitional package is now ready to be
removed.

Please be sure to update your package during the buster release cycle
so that transitional package can finally be removed.

Regards,

Laurent Bigonville 
--- End Message ---
--- Begin Message ---
Source: vblade-persist
Source-Version: 0.6-3

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated vblade-persist package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 07 Jan 2018 04:42:08 +0100
Source: vblade-persist
Binary: vblade-persist
Architecture: source
Version: 0.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 vblade-persist - create/manage supervised AoE exports
Closes: 862851
Changes:
 vblade-persist (0.6-3) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Luca Boccassi ]
   * Recommend iproute2 instead of transitional package iproute.
 (Closes: #862851)
 .
   [ Adam Borowski ]
   * Set maintainer to the QA group.
   * dh 11.
   * R³.
Checksums-Sha1:
 fb2f3016f9d3ba756f843a6d08af4addc26cec16 1770 vblade-persist_0.6-3.dsc
 b210bb678cd62acebd91ad65d699c420eaafe083 2328 vblade-persist_0.6-3.diff.gz
 116d436213b831e5a065ee332badc2ee280d718d 5346 
vblade-persist_0.6-3_source.buildinfo
Checksums-Sha256:
 1ba0e657c0a161e6c9e202ffdaf499cc9b298ae1c235383ee4f1a665033234a3 1770 
vblade-persist_0.6-3.dsc
 1d580c1610db9637348ba14e0a76c41d3ca6db2551069691c4071def7c922d26 2328 
vblade-persist_0.6-3.diff.gz
 b9e2173c5846bb72b7a7f2125653b3b380c43f8d506db1641e72f07e04d3cc2c 5346 
vblade-persist_0.6-3_source.buildinfo
Files:
 f61476a5492e4043aa34bb421cf696dc 1770 admin optional vblade-persist_0.6-3.dsc
 c81aaf355b01eefa492b8bd0d05c15cd 2328 admin optional 
vblade-persist_0.6-3.diff.gz
 290431bdff264026bbfe25a4fa1e461e 5346 admin optional 
vblade-persist_0.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlpRl4IUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH5F8xAAyy8ioMAaPXECLDxm1Yx9pq9F7Bdd
FtDEF9y7yHXFR98QP1uk/kgoGfsxN/75/ylcOwBvGpNPTXMr99eG+v/W4/2qRHxS
7jNDfSQ8+DJWILOSzsmO6K3X+DxdjKLMorrKBxub05A7AjCiRXD07s131x/kORtK
IgOSrMYucFMcU4csuQAOcWWhRtyeupFatUZmcG7jiCOsqZygz48coV54bzwSu2C8
rhBA6Bnq0qJj7Ix4AAzAhX4qbLBLthhjYU+gWZGX5ZcwNArEd7bHq0nRqLI8auq7
Vt4NimbBKxbaQLW2gWFsvcKCaLFGkG8j5RcrE92+Xb22D0rxCSsYPRzw1tZg8hDz
pZSuDdJY7Gbn3ZejrY5CBF6r41P5jQNmo/5+Hg1R6UjhZfIBnGqXZvXCwxbTUb9o
AQpUCPxcfYq1ji5F0fgnddQai3/5NBDBSlQkxZoSOtJ/yzgJDrqn1PQqagF6B47Q
PqON9ek6zKApolR5tn1ZiJ4CzlNDWHq7mycz3syWULvZnmh3QGhzn5Mxz/ci/sWd
IzPNuIu9Gc8j7zh84vhfkms6m2oQ1oitXuf6WwBzxT+GkNAY/vYpQZUfgsQfiPII
ZCvdoVjh2RKiT5w3ffVs94m3Ac7UhyCFqThiUUYUuS/Sfu2KpBhKE3PE1Q228rr1
xSsmIoCx8wsLZMc=
=eYWC
-END PGP SIGNATURE End Message ---

Bug#886510: OK now I installed libelf-dev, but...

[積丹尼 Dan Jacobson]

OK now I did,

# aptitude install libelf-dev
The following NEW packages will be installed:
  libelf-dev
The following packages will be REMOVED:
  linux-headers-4.14.0-1-amd64{pu}  linux-headers-4.14.0-1-common{pu} (D: 
linux-headers-4.14.0-1-amd64)

And now the error is gone,

# aptitude reinstall linux-image-4.14.0-3-amd64
The following packages will be REINSTALLED:
  linux-image-4.14.0-3-amd64
Preparing to unpack .../linux-image-4.14.0-3-amd64_4.14.12-2_amd64.deb ...
Unpacking linux-image-4.14.0-3-amd64 (4.14.12-2) over (4.14.12-2) ...
Setting up linux-image-4.14.0-3-amd64 (4.14.12-2) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-4.14.0-3-amd64

But I didn't see and nvidia-legacy-304xx-kernel-dkms related messages...
so maybe I have wiped that component out in the process, ruining the
whole purpose?

Processed: Re: Bug#886510: Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 linux-headers-4.14.0-3-amd64
Bug #886510 [nvidia-legacy-304xx-kernel-dkms] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Bug reassigned from package 'nvidia-legacy-304xx-kernel-dkms' to 
'linux-headers-4.14.0-3-amd64'.
No longer marked as found in versions 
nvidia-graphics-drivers-legacy-304xx/304.137-3.
Ignoring request to alter fixed versions of bug #886510 to the same values 
previously set
> forcemerge 886474 -1
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Bug #886510 [linux-headers-4.14.0-3-amd64] Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel
Severity set to 'grave' from 'normal'
Marked as found in versions linux/4.14.12-2.
Merged 886474 886510

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

Processed: Add affects

[Debian Bug Tracking System]

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

> affects 885965 src:distro-info
Bug #885965 [pylint3] FTBFS: Test: Run pylint on Python source code ... FAIL
Added indication that 885965 affects src:distro-info
> thanks
Stopping processing here.

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

Processed: severity of 886474 is grave

[Debian Bug Tracking System]

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

> severity 886474 grave
Bug #886474 [linux-headers-4.14.0-3-amd64] linux-headers-4.14.0-3-amd64: 
missing dependency on libelf-dev
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

[Vincent Lefevre]

On 2018-01-06 23:29:01 +, Luca Boccassi wrote:
> Same as 886470 and 886495, fixed in 384.111.

OK. The build error was a bit invisible. :(

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

[Benjamin Drung]

reassign 885965 pylint3 1.7.4-2
thanks

Am Montag, den 01.01.2018, 01:36 +0100 schrieb Adam Borowski:
> Source: distro-info
> Version: 0.17
> Severity: serious
> Justification: fails to build from source (but built successfully in
> the past)
> 
> Hi!
> I'm afraid your package fails to build with:
> 
> Test: Run pylint on Python source code ... FAIL
> 
> ==
> FAIL: test_pylint (distro_info_test.test_pylint.PylintTestCase)
> Test: Run pylint on Python source code
> 
> [...]
> (unused-variable)" is not false : pylint3 found errors:
> * Module distro_info_test.test_help
> W: 30, 0: Unused variable '__class__' (unused-variable)
> W: 30, 0: Unused variable '__class__' (unused-variable)
> * Module distro_info_test.test_pylint
> W: 26, 0: Unused variable '__class__' (unused-variable)
> * Module distro_info_test.test_flake8
> W: 23, 0: Unused variable '__class__' (unused-variable)
> * Module distro_info_test.test_distro_info
> W: 25, 0: Unused variable '__class__' (unused-variable)
> W: 25, 0: Unused variable '__class__' (unused-variable)
> W: 25, 0: Unused variable '__class__' (unused-variable)
> 
> Tested on armhf amd64.  Log attached.

Thanks for reporting it. This is a bug in pylint which reports this
false-positive: Unused variable '__class__'

-- 
Benjamin Drung
Debian & Ubuntu Developer

Processed: Re: Bug#885965: FTBFS: Test: Run pylint on Python source code ... FAIL

[Debian Bug Tracking System]

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

> reassign 885965 pylint3 1.7.4-2
Bug #885965 [src:distro-info] FTBFS: Test: Run pylint on Python source code ... 
FAIL
Bug reassigned from package 'src:distro-info' to 'pylint3'.
No longer marked as found in versions distro-info/0.17.
Ignoring request to alter fixed versions of bug #885965 to the same values 
previously set
Bug #885965 [pylint3] FTBFS: Test: Run pylint on Python source code ... FAIL
Marked as found in versions pylint/1.7.4-2.
> thanks
Stopping processing here.

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

Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

[Harlan Lieberman-Berg]

On Sat, Jan 6, 2018 at 12:45 PM, Antoine Beaupré
 wrote:
> I'm fine with you pushing to collab-maint - this is what it's for after
> all. :)

Still, didn't want you to get surprised if you were working on it at
the same time!

> So even after this you still FTBFS? Did you report that issue upstream
> as well?

Right now, it's FTBFS because of an inappropriate dependency in the
setuptools config of one of the libraries, txtorcon.  They've merged
my PR, but they haven't cut a new release yet.  If you want, I can
open a bug over with the Privacy Tools team and see if they'd be
willing to take the patch out of the release cycle.

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman

Bug#886417: linux-source-4.9: Kernel sources do not compile

[Robert Senger]

Package: linux-source-4.9
Followup-For: Bug #886417

I am also using a custom config, trying to build a kernel for a old AMD Geode
i386 machine (inside a i386 systemd-nspawn container running on a amd64
machine).




-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-source-4.9 depends on:
ii  binutils  2.28-5
ii  xz-utils  5.2.2-1.2+b1

Versions of packages linux-source-4.9 recommends:
ii  bc1.06.95-9+b3
ii  gcc   4:6.3.0-4
ii  libc6-dev [libc-dev]  2.24-11+deb9u1
ii  make  4.1-9.1

Versions of packages linux-source-4.9 suggests:
pn  libncurses-dev | ncurses-dev  
pn  libqt4-dev
ii  pkg-config0.29-4+b1
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 4.9.65-1-geode Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_MMU=y
CONFIG_ARCH_MMAP_RND_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_BITS_MAX=16
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8
CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16
CONFIG_NEED_SG_DMA_LENGTH=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_ARCH_HAS_CPU_RELAX=y
CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y
CONFIG_HAVE_SETUP_PER_CPU_AREA=y
CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y
CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y
CONFIG_ARCH_HIBERNATION_POSSIBLE=y
CONFIG_ARCH_SUSPEND_POSSIBLE=y
CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y
CONFIG_ARCH_WANT_GENERAL_HUGETLB=y
CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y
CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y
CONFIG_ARCH_SUPPORTS_UPROBES=y
CONFIG_FIX_EARLYCON_MEM=y
CONFIG_DEBUG_RODATA=y
CONFIG_PGTABLE_LEVELS=2
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_IRQ_WORK=y
CONFIG_BUILDTIME_EXTABLE_SORT=y
CONFIG_THREAD_INFO_IN_TASK=y

#
# General setup
#
CONFIG_BROKEN_ON_SMP=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_CROSS_COMPILE=""
# CONFIG_COMPILE_TEST is not set
CONFIG_LOCALVERSION=""
# CONFIG_LOCALVERSION_AUTO is not set
CONFIG_HAVE_KERNEL_GZIP=y
CONFIG_HAVE_KERNEL_BZIP2=y
CONFIG_HAVE_KERNEL_LZMA=y
CONFIG_HAVE_KERNEL_XZ=y
CONFIG_HAVE_KERNEL_LZO=y
CONFIG_HAVE_KERNEL_LZ4=y
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
CONFIG_KERNEL_XZ=y
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_DEFAULT_HOSTNAME="(none)"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
CONFIG_POSIX_MQUEUE_SYSCTL=y
CONFIG_CROSS_MEMORY_ATTACH=y
CONFIG_FHANDLE=y
CONFIG_USELIB=y
CONFIG_AUDIT=y
CONFIG_HAVE_ARCH_AUDITSYSCALL=y
CONFIG_AUDITSYSCALL=y
CONFIG_AUDIT_WATCH=y
CONFIG_AUDIT_TREE=y

#
# IRQ subsystem
#
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_IRQ_SHOW=y
CONFIG_IRQ_DOMAIN=y
CONFIG_IRQ_DOMAIN_HIERARCHY=y
CONFIG_GENERIC_MSI_IRQ=y
CONFIG_GENERIC_MSI_IRQ_DOMAIN=y
# CONFIG_IRQ_DOMAIN_DEBUG is not set
CONFIG_IRQ_FORCED_THREADING=y
CONFIG_SPARSE_IRQ=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y
CONFIG_GENERIC_CMOS_UPDATE=y

#
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
CONFIG_NO_HZ_COMMON=y
# CONFIG_HZ_PERIODIC is not set
CONFIG_NO_HZ_IDLE=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y

#
# CPU/Task time and stats accounting
#
CONFIG_TICK_CPU_ACCOUNTING=y
# CONFIG_IRQ_TIME_ACCOUNTING is not set
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
CONFIG_TASK_XACCT=y
CONFIG_TASK_IO_ACCOUNTING=y

#
# RCU Subsystem
#
CONFIG_TINY_RCU=y
# CONFIG_RCU_EXPERT is not set
CONFIG_SRCU=y
# CONFIG_TASKS_RCU is not set
# CONFIG_RCU_STALL_COMMON is not set
# CONFIG_TREE_RCU_TRACE is not set
# CONFIG_RCU_EXPEDITE_BOOT is not set
CONFIG_BUILD_BIN2C=y
CONFIG_IKCONFIG=m
# CONFIG_IKCONFIG_PROC is not set
CONFIG_LOG_BUF_SHIFT=17
CONFIG_NMI_LOG_BUF_SHIFT=13
CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
CONFIG_CGROUPS=y
CONFIG_PAGE_COUNTER=y
CONFIG_MEMCG=y
CONFIG_MEMCG_SWAP=y
# CONFIG_MEMCG_SWAP_ENABLED is not set
CONFIG_BLK_CGROUP=y
# CONFIG_DEBUG_BLK_CGROUP is not set
CONFIG_CGROUP_WRITEBACK=y
CONFIG_CGROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_CFS_BANDWIDTH is not set
# CONFIG_RT_GROUP_SCHED is not set
# CONFIG_CGROUP_PIDS is not set
CONFIG_CGROUP_FREEZER=y
# CONFIG_CGROUP_HUGETLB is not set
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

[Luca Boccassi]

On Sat, 6 Jan 2018 23:48:07 +0100 Vincent Lefevre 
wrote:
> Package: nvidia-kernel-dkms
> Version: 384.98-3
> Severity: grave
> Justification: renders package unusable
> 
> I get the following error when I want to start X:
> 
> [89.841] (EE) NVIDIA: Failed to initialize the NVIDIA kernel
module. Please see the
> [89.841] (EE) NVIDIA: system's kernel log for additional
error messages and
> [89.841] (EE) NVIDIA: consult the NVIDIA README for details.
> [89.841] (EE) No devices detected.
> [89.841] (EE) 
> Fatal server error:
> [89.841] (EE) no screens found(EE) 
> [89.841] (EE) 
> 
> According to the kernel log, there is no attempt to load the kernel
> module.

Same as 886470 and 886495, fixed in 384.111.

-- 
Kind regards,
Luca Boccassi

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

Processed: merge 886470 886505

[Debian Bug Tracking System]

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

> close 886505
Bug #886505 [nvidia-kernel-dkms] nvidia-kernel-dkms: fails to work with 
linux-image-4.14.0-3-amd64
Marked Bug as done
> merge 886470 886505
Bug #886470 {Done: Luca Boccassi } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: FTBFS against linux 4.14.12-2
Bug #886495 {Done: Luca Boccassi } [nvidia-kernel-dkms] 
nvidia-driver: Fails to build against 4.14.0-3
Bug #886505 {Done: Luca Boccassi } [nvidia-kernel-dkms] 
nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64
The source nvidia-graphics-drivers and version 384.111-1 do not appear to match 
any binary packages
Marked as fixed in versions nvidia-graphics-drivers/384.111-1.
Bug #886495 {Done: Luca Boccassi } [nvidia-kernel-dkms] 
nvidia-driver: Fails to build against 4.14.0-3
Merged 886470 886495 886505
>
End of message, stopping processing here.

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

Processed: Close the bug

[Debian Bug Tracking System]

Processing control commands:

> fixed 883526 1:1.4-3
Bug #883526 [src:geeqie] geeqie build does not trap errors from make
Marked as fixed in versions geeqie/1:1.4-3.

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

Bug#883526: Close the bug

[Andreas Ronnquist]

Control: fixed 883526 1:1.4-3
thanks

Note to self: "Closing" doesn't close a bug, it must be "Closes".

-- Andreas Rönnquist
gus...@debian.org

Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

[Bob Proulx]

severity 885989 wishlist
tags 885989 + wontfix
thanks

TemTem wrote:
> A large portion of websites are being (willingly) attacked by
> man-in-the-middles (MitM) such as Cloudflare.

When someone commissions a service provider such as CloudFlare to host
their web site CloudFlare then of course CloudFlare hosts their web
site.  Since CloudFlare is hosting then of course they are also
terminating the TLS endpoint connection.  That is inherently how
things work.

The decision is made by the web site owner.  It is their choice.  They
can choose host at CloudFlare or at another hosting provider or they
can build up their own infrastructure.  It is their decision.

> Chromium aims to provide a SAFER web browsing experience, but it
> fails to do that by not preventing users from being attacked by a
> MitM.

It is not an attack when it has been explicitly chosen by the web site
to host their web server.

> TLS is designed to protect against MitM attacks by providing
> an end-to-end encrypted connection between the client and the
> server.

And so it does here.  Here end to end is between the client and the
server.  The server is a CloudFlare server.  They are being
commissioned to host the web site.  They are therefore terminating the
TLS connection endpoint.  Since they are the web site server.

> Cloudflare and other similar services undermines TLS by decrypting
> the connection, which is a very grave security and privacy concern,
> especially for Tor users. If passwords are entered in a such service
> pwned site, whether you are using TLS or not, the password (and any
> other sensitive data) would be known by an unintended third-party.

When CloudFlare is commissioned to host a web site then they host that
web site.  They are not "unintended".  It is no different from any
other web site.

> How can Chromium know that the user is visiting a MitM-ed site?
> Let's look at Cloudflare. Cloudflare uses a "cf-ray:" HTTP
> header. Similar services probably has a similar kind to the
> "cf-ray:" header too. Use those headers and whatever kind which will
> identify that the site is pwned.

If you do not trust the server site then you also cannot trust headers
that it is sending.  And just from a practical perspective those
headers might not exist at all or might be different for every hosting
provider or might be changing very frequently.  All of those things
make using such headers problematic.

Bob


signature.asc
Description: PGP signature

Processed: Re: Bug#885989: chromium: MitM-ed TLS sites are being recognized as secure even though they are not

[Debian Bug Tracking System]

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

> severity 885989 wishlist
Bug #885989 [chromium] chromium: MitM-ed TLS sites are being recognized as 
secure even though they are not
Severity set to 'wishlist' from 'grave'
> tags 885989 + wontfix
Bug #885989 [chromium] chromium: MitM-ed TLS sites are being recognized as 
secure even though they are not
Added tag(s) wontfix.
> thanks
Stopping processing here.

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

Bug#886505: nvidia-kernel-dkms: fails to work with linux-image-4.14.0-3-amd64

[Vincent Lefevre]

Package: nvidia-kernel-dkms
Version: 384.98-3
Severity: grave
Justification: renders package unusable

I get the following error when I want to start X:

[89.841] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please 
see the
[89.841] (EE) NVIDIA: system's kernel log for additional error messages 
and
[89.841] (EE) NVIDIA: consult the NVIDIA README for details.
[89.841] (EE) No devices detected.
[89.841] (EE) 
Fatal server error:
[89.841] (EE) no screens found(EE) 
[89.841] (EE) 

According to the kernel log, there is no attempt to load the kernel
module.

-- Package-specific info:
uname -a:
Linux zira 4.14.0-2-amd64 #1 SMP Debian 4.14.7-1 (2017-12-22) x86_64 GNU/Linux

/proc/version:
Linux version 4.14.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.2.0 (Debian 7.2.0-18)) #1 SMP Debian 4.14.7-1 (2017-12-22)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.98  Thu Oct 26 15:16:01 PDT 
2017
GCC version:  gcc version 7.2.0 (Debian 7.2.0-18) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208GLM [Quadro 
K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:2254]
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: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 2018-01-06 23:36:39 /dev/dri/card0
crw-rw+ 1 root video 226, 128 2018-01-06 23:36:39 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 2018-01-06 23:36:41 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 2018-01-06 23:36:40 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 2018-01-06 23:36:40 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 2018-01-06 23:36:39 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 2018-01-06 23:36:39 pci-:01:00.0-render -> 
../renderD128
video:x:44:vinc17

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 2017-09-28 18:33:15 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 2016-04-11 21:40:32 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   51 2017-09-28 18:33:15 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   50 2017-09-28 18:33:15 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 2017-09-28 18:33:15 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 2017-09-28 18:33:15 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   50 2017-09-28 18:33:15 
/etc/alternatives/glx--libGLESv1_CM.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   54 2017-09-28 18:33:15 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 2017-09-28 18:33:15 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 2017-09-28 18:33:15 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 2017-09-28 18:33:15 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 2017-09-28 18:33:15 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 2017-09-28 18:33:15 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 2017-09-28 18:33:15 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 2017-0

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Hans van Kranenburg]

Hi Christian and everyone else,

Ack on reassign to Xen.

On 01/06/2018 04:11 PM, Yves-Alexis Perez wrote:
> control: reassign -1 xen-hypervisor-4.8-amd64
> 
> On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote:
>> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
>>> According to that link, the fix seems to be configuration rather than
>>> code.
>>> Does this mean this bug against the kernel should be closed?
>>
>> Yes, the problem seems to be in the Xen hypervisor and not the Linux
>> kernel itself.  The default value for the gnttab_max_frames parameter
>> needs to be increased to avoid domU disk IO hangs, for example:
>>
>>   GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256"
>>
>> So either close the bug or reassign it to xen-hypervisor package so
>> they can increase the default value for this parameter in the
>> hypervisor code.
>>
> Ok, I'll reassign and let the Xen maintainers handle that (maybe in a stable
> update).
> 
> @Xen maintainers: see the complete bug log for more information, but basically
> it seems that a domu freezes happens with the “new” multi-queue xen blk
> driver, and the fix is to increase a configuration value. Valentin suggests
> adding that to the default.

The dom0 gnttab_max_frames boot setting is about how many pages are
allocated to fill with 'grants'. The grant concept is related to sharing
information between the dom0 and domU.

It allows memory pages to be shared back and forth, so that e.g. a domU
can fill a page with outgoing network packets or disk writes. Then the
dom0 can take over ownership of the memory page and read the contents
and do its trick with it. In this way, zero-copy IO is implemented.

When running xen domUs, the total amount of network interfaces and block
devices that are attached to all of the domUs that are running (and,
apparently, how heavy they are used) cause the usage of these grant guys
to increase. At some point you run out of grants because all of the
pages are filled.

I agree that the upstream default, 32 is quite low. This is indeed a
configuration issue. I myself ran into this years ago with a growing
number of domUs and network interfaces in use. We have been using
gnttab_max_nr_frames=128 for a long time already instead.

I was tempted to reassign src:xen, but in the meantime, this option has
already been removed again, so this bug does not apply to unstable
(well, as soon as we get something new in there) any more (as far as I
can see quickly now).

https://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=18b1be5e324bcbe2f10898b116db641d404b3d30

Including a better default for gnttab_max_nr_frames in the grub config
in the debian xen package in stable sounds reasonable from a best
practices point of view.

But, I would be interested in learning more about the relation with
block mq although. Does using newer linux kernels (like from
stretch-backports) for the domU always put a bigger strain on this? Or,
is it just related to the overall number of network devices and block
devices you are adding to your domUs in your specific own situation, and
did you just trip over the default limit?

In any case, the grub option thing is a conffile, so any user upgrading
has to accept/merge the change, so we won't cause a stable user to just
run out of memory because of a few extra kilobytes of memory usage
without notice.

Hans van Kranenburg

P.S. Debian Xen team is in the process of being "rebooted" while the
current shitstorm about meltdown/spectre is going on, so don't hold your
breath. :)



signature.asc
Description: OpenPGP digital signature

Processed: forcemerge

[Debian Bug Tracking System]

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

> unarchive 853462
Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs 
with GCC-7
Unarchived Bug 853462
> forcemerge 853462 886489
Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs 
with GCC-7
Bug #853462 {Done: Matthias Klose } [src:json-c] json-c: ftbfs 
with GCC-7
Marked as found in versions json-c/0.12.1-1.
Bug #886489 [src:json-c] FTBFS: json_object.c:554:5: error: this statement may 
fall through [-Werror=implicit-fallthrough=]
Marked Bug as done
Marked as fixed in versions json-c/0.12.1-1.2.
Marked as found in versions json-c/0.12.1-1.1.
Added tag(s) sid, buster, and patch.
Merged 853462 886489
> thanks
Stopping processing here.

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

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

[Jonas Meurer]

Control: forcemerge 853462 886489

Hey again,

apparently I made a stupid mistake. This bug had already been filed and
fixed some months ago:

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

Since the NMU that fixed the bug had not been pushed to the packaging
Git repo, I didn't spot it when trying to build json-c.

Closing this bug as a duplicate of #853462.

Cheers
 jonas

Am 06.01.2018 um 18:41 schrieb Jonas Meurer:
> Source: json-c
> Version: 0.12.1-1
> Severity: serious
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> json-c fails to build from source due to a potential implicit
> fall-through in function json_object_get_int64() from json_object.c:
> 
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
> -Wall -Werror -Wno-error=deprecated-declarations 
> -Wno-error=unused-but-set-variable -Wextra -Wwrite-strings 
> -Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE -D_REENTRANT -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c json_object.c  -fPIC -DPIC -o .libs/json_object.o
> json_object.c: In function 'json_object_get_int64':
> json_object.c:554:5: error: this statement may fall through 
> [-Werror=implicit-fallthrough=]
>   if (json_parse_int64(jso->o.c_string.str, &cint) == 0) return cint;
>  ^
> json_object.c:555:3: note: here
>default:
>^~~
> cc1: all warnings being treated as errors
> Makefile:578: recipe for target 'json_object.lo' failed
> make[3]: *** [json_object.lo] Error 1
> make[3]: Leaving directory '/<>'
> 
> 
> A quick look at the latest upstream release gave me the impression that
> his might have been fixed upstream in release 0.13:
> 
> https://github.com/json-c/json-c/blob/json-c-0.13-20171207/json_object.c#L697-L703
> 
> Cheers
>  jonas
> 
> -- System Information:
> Debian Release: 9.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: 
> LC_ALL set to en_US.UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 




signature.asc
Description: OpenPGP digital signature

Bug#884242: gdb-mingw-w64: diff for NMU version 10.4+nmu1

[Adrian Bunk]

Control: tags 884242 + patch
Control: tags 884242 + pending

Dear maintainer,

I've prepared an NMU for gdb-mingw-w64 (versioned as 10.4+nmu1) and 
uploaded it to DELAYED/5. Please feel free to tell me if I should
cancel it.

cu
Adrian

-- 

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

diff -Nru gdb-mingw-w64-10.4/debian/changelog gdb-mingw-w64-10.4+nmu1/debian/changelog
--- gdb-mingw-w64-10.4/debian/changelog	2016-09-19 21:36:37.0 +0300
+++ gdb-mingw-w64-10.4+nmu1/debian/changelog	2018-01-07 00:00:08.0 +0200
@@ -1,3 +1,11 @@
+gdb-mingw-w64 (10.4+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * hardening=-format, to avoid FTBFS caused by the combination
+of -Werror=format-security and -Wno-format. (Closes: #884242)
+
+ -- Adrian Bunk   Sun, 07 Jan 2018 00:00:08 +0200
+
 gdb-mingw-w64 (10.4) unstable; urgency=medium
 
   * Disable package mangling in Launchpad.
diff -Nru gdb-mingw-w64-10.4/debian/rules gdb-mingw-w64-10.4+nmu1/debian/rules
--- gdb-mingw-w64-10.4/debian/rules	2016-09-19 21:36:12.0 +0300
+++ gdb-mingw-w64-10.4+nmu1/debian/rules	2018-01-06 23:48:23.0 +0200
@@ -41,7 +41,7 @@
 
 # Windows targets don't support stackprotector, relro, bindnow or pie
 # We disable PE timestamps to build reproducibly
-dpkg_buildflags_indep = DEB_BUILD_MAINT_OPTIONS="hardening=-stackprotector,-relro,-bindnow,-pie" DEB_LDFLAGS_MAINT_APPEND="-Xlinker --no-insert-timestamp" dpkg-buildflags
+dpkg_buildflags_indep = DEB_BUILD_MAINT_OPTIONS="hardening=-stackprotector,-relro,-bindnow,-pie,-format" DEB_LDFLAGS_MAINT_APPEND="-Xlinker --no-insert-timestamp" dpkg-buildflags
 
 DEB_BUILD_GNU_TYPE := $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE)
 

Processed: gdb-mingw-w64: diff for NMU version 10.4+nmu1

[Debian Bug Tracking System]

Processing control commands:

> tags 884242 + patch
Bug #884242 [src:gdb-mingw-w64] gdb-mingw-w64 FTBFS with g++-mingw-w64 
7.2.0-16+20
Added tag(s) patch.
> tags 884242 + pending
Bug #884242 [src:gdb-mingw-w64] gdb-mingw-w64 FTBFS with g++-mingw-w64 
7.2.0-16+20
Added tag(s) pending.

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

Bug#884185: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 22:05:02 +
with message-id 
and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5
has caused the Debian Bug report #883987,
regarding FTBFS error: partial specialization ... after instantiation ... (with 
patch)
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.)


-- 
883987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgal-dev
Version: 4.11-2
Severity: grave
Justification: renders package unusable
Tags: upstream newcomer

Dear Maintainer,

Boost-1.62 fails to compile the following c++ file :

g++ pair_tst.cc -o pair_tst.cc

in sid and buster (testing) with g++ 7.2.
The output is:
In file included from 
/usr/include/boost/container/detail/flat_tree.hpp:29:0,
 from /usr/include/boost/container/flat_map.hpp:29,
 from pair_tst.cc:16:
/usr/include/boost/container/detail/pair.hpp:433:8: error: partial 
specialization of ‘struct boost::is_enum >’ after 
instantiation of ‘struct boost::is_enum >’ [-fpermissive]
struct is_enum< ::std::pair >
^~~~

See the "pair_tst.cc" file in attachment for reproducing this bug.
This bug actually causes some debian package build to fail in sid
and testing (see e.g. bug: #883987 ).

The bug has already be identified in the upstream version of Boost :
  https://svn.boost.org/trac10/ticket/12534
and it is now fixed in boost-dev 1.65:
  
https://github.com/boostorg/container/commit/5e4a107e82ab3281688311d22d2bfc2fddcf84a3
The fix simply consists of removing from line 431 to 460
in file include/boost/container/detail/pair.hpp
See also the "pair_tst.patch" file in attachment.

Could you please includes this patch in the debianization of
the Boost package ?

Best regards,

Pierre Saramito

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/32 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 libcgal-dev depends on:
ii  libboost-dev  1.62.0.1
ii  libboost-program-options-dev  1.62.0.1
ii  libboost-system-dev   1.62.0.1
ii  libboost-thread-dev   1.62.0.1
ii  libcgal13 4.11-2
ii  libgmp-dev [libgmp10-dev] 2:6.1.2+dfsg-1.1
ii  libmpfr-dev   3.1.6-1
ii  zlib1g-dev1:1.2.8.dfsg-5

libcgal-dev recommends no packages.

Versions of packages libcgal-dev suggests:
pn  libmpfi-dev  
pn  libntl-dev   
pn  libtbb-dev   

-- no debconf information

--
pierre.saram...@imag.fr
Directeur de Recherche CNRS
Laboratoire Jean Kuntzmann, Grenoble, France
http://ljk.imag.fr/membres/Pierre.Saramito// bug description
// https://svn.boost.org/trac10/ticket/12534
// and its fix in boost-dev 1.65:
// https://github.com/boostorg/container/commit/5e4a107e82ab3281688311d22d2bfc2fddcf84a3
// i.e. remove from line 431 to 460 in include/boost/container/detail/pair.hpp

#undef FIX_BUG
#ifdef  FIX_BUG
#include 
#endif // FIX_BUG

#include 

static const bool is_enum = boost::is_enum >::value;

#include 

boost::container::flat_map m;

int main() {}
*** /usr/include/boost/container/detail/pair.hpp.orig	Tue Dec 12 12:15:26 2017
--- /usr/include/boost/container/detail/pair.hpp	Tue Dec 12 12:41:22 2017
***
*** 416,451 
  }  //namespace container_detail {
  }  //namespace container {
  
- 
- //Without this specialization recursive flat_(multi)map instantiation fails
- //because is_enum needs to instantiate the recursive pair, leading to a compilation error).
- //This breaks the cycle clearly stating that pair is not an enum avoiding any instantiation.
- template
- struct is_enum;
- 
- template
- struct is_enum< ::boost::container::container_detail::pair >
- {
-static const bool value = false;
- };
- 
- template
- struct is_enum< ::std::pair >
- {
-static const bool value = false;
- };
- 
- template 
- struct is_class;
- 
- //This specialization is needed to avoid instantiation of pair in
- //is_class, and allow recursive maps.
- template 
- struct is_class< ::boost::container::container_detail::pair >
- {
-static const bool value = true;
- };
- 
  #ifdef BOOST_NO_CXX11_RVALUE_REFERENCES
  
  template
--- 416,421 
--- End Message ---
--- Begin Message ---
Source: boost1.6

Bug#883987: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 22:05:02 +
with message-id 
and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5
has caused the Debian Bug report #883987,
regarding FTBFS error: partial specialization ... after instantiation ... (with 
patch)
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.)


-- 
883987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rheolef
Version: 6.7-4
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

rheolef did FTBFS during the binNMU against the new cgal:

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

>From the amd64 log:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../config -I../../util/qd 
-I../../include -I/usr/include/openmpi -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c++11 -Wall -Wno-unused -Wno-strict-aliasing 
-Wno-literal-suffix -Wno-deprecated-declarations -O3 -MT point_predicate.lo -MD 
-MP -MF .deps/point_predicate.Tpo -c point_predicate.cc  -fPIC -DPIC -o 
.libs/point_predicate.o
In file included from /usr/include/boost/container/detail/flat_tree.hpp:29:0,
 from /usr/include/boost/container/flat_map.hpp:29,
 from /usr/include/CGAL/config.h:123,
 from /usr/include/CGAL/basic.h:29,
 from /usr/include/CGAL/Cartesian/Cartesian_base.h:28,
 from /usr/include/CGAL/Cartesian.h:28,
 from ../../include/rheolef/cgal_kernel.h:42,
 from ../../include/rheolef/cgal_traits.h:24,
 from point_predicate.cc:34:
/usr/include/boost/container/detail/pair.hpp:433:8: error: partial 
specialization of 'struct boost::is_enum >' after 
instantiation of 'struct boost::is_enum >' [-fpermissive]
 struct is_enum< ::std::pair >
^~~~
Makefile:1130: recipe for target 'point_predicate.lo' failed
make[4]: *** [point_predicate.lo] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-5

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated boost1.62 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Jan 2018 14:44:32 -0600
Source: boost1.62
Binary: libboost1.62-dev libboost1.62-tools-dev libboost1.62-all-dev 
libboost1.62-doc libboost-atomic1.62.0 libboost-atomic1.62-dev 
libboost-chrono1.62.0 libboost-chrono1.62-dev libboost-context1.62.0 
libboost-context1.62-dev libboost-coroutine1.62.0 libboost-coroutine1.62-dev 
libboost-date-time1.62.0 libboost-date-time1.62-dev libboost-exception1.62-dev 
libboost-fiber1.62.0 libboost-fiber1.62-dev libboost-filesystem1.62.0 
libboost-filesystem1.62-dev libboost-graph1.62.0 libboost-graph1.62-dev 
libboost-graph-parallel1.62.0 libboost-graph-parallel1.62-dev 
libboost-iostreams1.62.0 libboost-iostreams1.62-dev libboost-locale1.62.0 
libboost-locale1.62-dev libboost-log1.62.0 libboost-log1.62-dev 
libboost-math1.62.0 libboost-math1.62-dev libboost-mpi1.62.0 
libboost-mpi1.62-dev libboost-mpi-python1.62.0 libboost-mpi-python1.62-dev 
libboost-program-options1.62.0 libboost-program-options1.62-dev 
libboost-python1.62.0 libboost-python1.62-dev libboost-random1.62.0
 libboost-random1.62-dev libboost-regex1.62.0 libboost-regex1.62-dev 
libboost-serialization1.62.0 libboost-serialization1.62-dev 
libboost-signals1.62.0 libboost-signals1.62-dev libboost-system1.62.0 
libboost-system1.62-dev libboost-test1.62.0 libboost-test1.62-dev 
libboost-thread1.62.0 libboost-thread1.62-dev libboost-timer1.62.0 
libboost-timer1.62-dev libboost-type-erasure1.62.0 
libboost-type-erasure1.62-dev libboost-wave1.62.0
 libboost-wave1.62-dev
Architecture: source
Version: 1.62.0+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: 

Bug#869994: proposed fix

[Stephen Schmiechen]

Greetings all using FindBin and adding the current directory everywhere
sql-ledger calls perl should fix the issue in all versions.
An example perl script would be:

perl -0777 -i.original -pe 's/(#!\/usr\/bin\/perl)/$1\n#perl 5.25 Fix:\nuse
FindBin qw\(\$Bin\);\nuse lib \"\$Bin\"\;/igs' *.pl

Cheers
Turtle

Bug#884184: marked as done (FTBFS error: partial specialization ... after instantiation ... (with patch))

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 22:05:02 +
with message-id 
and subject line Bug#883987: fixed in boost1.62 1.62.0+dfsg-5
has caused the Debian Bug report #883987,
regarding FTBFS error: partial specialization ... after instantiation ... (with 
patch)
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.)


-- 
883987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcgal-dev
Version: 4.11-2
Severity: grave
Justification: renders package unusable
Tags: upstream newcomer

Dear Maintainer,

Boost-1.62 fails to compile the following c++ file :

g++ pair_tst.cc -o pair_tst.cc

in sid and buster (testing) with g++ 7.2.
The output is:
In file included from 
/usr/include/boost/container/detail/flat_tree.hpp:29:0,
 from /usr/include/boost/container/flat_map.hpp:29,
 from pair_tst.cc:16:
/usr/include/boost/container/detail/pair.hpp:433:8: error: partial 
specialization of ‘struct boost::is_enum >’ after 
instantiation of ‘struct boost::is_enum >’ [-fpermissive]
struct is_enum< ::std::pair >
^~~~

See the "pair_tst.cc" file in attachment for reproducing this bug.
This bug actually causes some debian package build to fail in sid
and testing (see e.g. bug: #883987 ).

The bug has already be identified in the upstream version of Boost :
  https://svn.boost.org/trac10/ticket/12534
and it is now fixed in boost-dev 1.65:
  
https://github.com/boostorg/container/commit/5e4a107e82ab3281688311d22d2bfc2fddcf84a3
The fix simply consists of removing from line 431 to 460
in file include/boost/container/detail/pair.hpp
See also the "pair_tst.patch" file in attachment.

Could you please includes this patch in the debianization of
the Boost package ?

Best regards,

Pierre Saramito

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

Kernel: Linux 4.13.0-1-amd64 (SMP w/32 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 libcgal-dev depends on:
ii  libboost-dev  1.62.0.1
ii  libboost-program-options-dev  1.62.0.1
ii  libboost-system-dev   1.62.0.1
ii  libboost-thread-dev   1.62.0.1
ii  libcgal13 4.11-2
ii  libgmp-dev [libgmp10-dev] 2:6.1.2+dfsg-1.1
ii  libmpfr-dev   3.1.6-1
ii  zlib1g-dev1:1.2.8.dfsg-5

libcgal-dev recommends no packages.

Versions of packages libcgal-dev suggests:
pn  libmpfi-dev  
pn  libntl-dev   
pn  libtbb-dev   

-- no debconf information

--
pierre.saram...@imag.fr
Directeur de Recherche CNRS
Laboratoire Jean Kuntzmann, Grenoble, France
http://ljk.imag.fr/membres/Pierre.Saramito
--- End Message ---
--- Begin Message ---
Source: boost1.62
Source-Version: 1.62.0+dfsg-5

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

Debian distribution maintenance software
pp.
Steve M. Robbins  (supplier of updated boost1.62 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Jan 2018 14:44:32 -0600
Source: boost1.62
Binary: libboost1.62-dev libboost1.62-tools-dev libboost1.62-all-dev 
libboost1.62-doc libboost-atomic1.62.0 libboost-atomic1.62-dev 
libboost-chrono1.62.0 libboost-chrono1.62-dev libboost-context1.62.0 
libboost-context1.62-dev libboost-coroutine1.62.0 libboost-coroutine1.62-dev 
libboost-date-time1.62.0 libboost-date-time1.62-dev libboost-exception1.62-dev 
libboost-fiber1.62.0 libboost-fiber1.62-dev libboost-filesystem1.62.0 
libboost-filesystem1.62-dev libboost-graph1.62.0 libboost-graph1.62-dev 
libboost-graph-parallel1.62.0 libboost-graph-parallel1.62-dev 
libboost-iostreams1.62.0 libboost-iostreams1.62-dev libboost-locale1.62.0 
libboost-locale1.62-dev libboost-log1.62.0 libbo

Processed: xpuzzles: diff for NMU version 7.7.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 856094 + patch
Bug #856094 [src:xpuzzles] xpuzzles: Please drop the (build-)dependency against 
esound
Added tag(s) patch.
> tags 856094 + pending
Bug #856094 [src:xpuzzles] xpuzzles: Please drop the (build-)dependency against 
esound
Added tag(s) pending.

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

Bug#856094: xpuzzles: diff for NMU version 7.7.1-1.1

[Adrian Bunk]

Control: tags 856094 + patch
Control: tags 856094 + pending

Dear maintainer,

I've prepared an NMU for xpuzzles (versioned as 7.7.1-1.1) and uploaded 
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru xpuzzles-7.7.1/debian/changelog xpuzzles-7.7.1/debian/changelog
--- xpuzzles-7.7.1/debian/changelog	2013-08-11 08:24:44.0 +0300
+++ xpuzzles-7.7.1/debian/changelog	2018-01-06 23:19:27.0 +0200
@@ -1,3 +1,12 @@
+xpuzzles (7.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build without support for the obsolete esound. (Closes: #856094)
+  * Remove no longer correct comment about being compiled with
+lesstif2 from the xmpuzzles package description.
+
+ -- Adrian Bunk   Sat, 06 Jan 2018 23:19:27 +0200
+
 xpuzzles (7.7.1-1) unstable; urgency=low
 
   * New upstream release
diff -Nru xpuzzles-7.7.1/debian/control xpuzzles-7.7.1/debian/control
--- xpuzzles-7.7.1/debian/control	2013-08-11 08:24:44.0 +0300
+++ xpuzzles-7.7.1/debian/control	2018-01-06 23:19:15.0 +0200
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Varun Hiremath 
-Build-Depends: debhelper (>= 7), libesd0-dev, libxpm-dev, libxt-dev,
+Build-Depends: debhelper (>= 7), libxpm-dev, libxt-dev,
  libmotif-dev, libglu1-mesa-dev, autotools-dev, libaudiofile-dev
 Standards-Version: 3.9.4
 Homepage: http://www.tux.org/~bagleyd/puzzles.html
@@ -36,6 +36,5 @@
   - Sliding Block Puzzles: xmcubes, xmtriangles, xmhexagons, xmpanex
   - Combination: xmbarrel, xmmlink
  .
- This is the Motif version which shows additional functionality. It was
- compiled with lesstif2. Motif is a GUI widget library for the X Window
- system.
+ This is the Motif version which shows additional functionality.
+ Motif is a GUI widget library for the X Window  system.
diff -Nru xpuzzles-7.7.1/debian/rules xpuzzles-7.7.1/debian/rules
--- xpuzzles-7.7.1/debian/rules	2013-08-11 08:24:44.0 +0300
+++ xpuzzles-7.7.1/debian/rules	2018-01-06 23:18:25.0 +0200
@@ -12,7 +12,7 @@
 
 CONFIGURE_FLAGS := --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \
 			--prefix=/usr --bindir=\$${prefix}/games --mandir=\$${prefix}/share/man \
-			--with-x --with-xpm --without-rplay --with-esound --without-nas
+			--with-x --with-xpm --without-rplay --without-esound --without-nas
 
 CFLAGS = -Wall -g
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

[Benjamin Lorenz]

On 01/06/2018 08:08 PM, Niko Tyni wrote:
> Running polymake currently fails with
>
>   $ polymake
>   Can't locate loadable object for module Polymake::Ext in @INC
>
> Apparently this is because it was built with Perl 5.26.0, but
> we've since moved to 5.26.1.
>
> I see two better alternatives:
>
> 1) [preferrable] fix polymake not to install its extensions in a
>   versioned directory (currently /usr/lib/polymake/perlx/5.26.0).

This would work for minor updates (5.26.0 -> 5.26.1 seems to work) but
the extension does depend heavily on the major version, so I dont think
this is a good idea.

> I note that the confusing @INC list above (it has
> /usr/lib/polymake/perlx/5.26.0 so it looks like it should work) is
> because "use lib" will add versioned subdirectories to @INC if it
> finds any, but will apparently *not* add arch-specific subdirectories
> (like /usr/lib/polymake/perlx/5.26.0/x86_64-linux-gnu-thread-multi)
> under those, and that's what would be needed here. I'm not quite sure
> if this is a glitch in lib.pm's handling of binary-compatible versions
> ($Config{inc_version_list}).

This is a good point, it looks like the Config.pm contains:
inc_version_list => '5.26.0',

but the perl INSTALL file states:

> If you do want to use modules from some previous perl versions, the
> variable must contain a space separated list of directories under the
> site_perl directory, and has to include architecture-dependent
> directories separately, eg.
>
>   sh Configure -Dinc_version_list="5.16.0/x86_64-linux 5.16.0" ...

It seems the perl Configure script tries to generate this list
automatically (probably from $sitelib=/usr/local/share/perl/5.26.1) but
failed to pick up the arch-specific directory because it might not exist?

I dont have such an installation at hand but this could be tested by
adding the arch-specific path for inc_version_list in
'/usr/lib/x86_64-linux-gnu/perl/5.26.1/Config.pm' manually first. If
this helps, the Configure command for perl should probably get an extra
-Dinc_version_list=.

Best,
Benjamin



signature.asc
Description: OpenPGP digital signature

Bug#886382: Coming updates for meltdown/spectre

[Henrique de Moraes Holschuh]

Hi Louis-Philippe!

On Fri, 05 Jan 2018, Louis-Philippe Véronneau wrote:

> > No, we don't know if they will release it *only* to vendors for a
> > firmware update, or also for operating system updates.  Also, for Zen
> > and later one cannot just hope to update microcode through the operating
> > system, often it requires such an early update that it has to be done by
> > the firmware itself.
> 
> https://lists.opensuse.org/opensuse-security-announce/2018-01/msg4.html
> 
> It seems AMD just released a microcode update to disable branch
> prediction on its Zen architecture.

Indeed.  Also needs a kernel patch to accept microcode updates on Zen
(hopefully we have that one already...).

Let's see if I can source the microcode update datafile...

-- 
  Henrique Holschuh

Bug#856075: basilisk2: diff for NMU version 0.9.20120331-4.1

[Jonas Smedegaard]

Quoting Adrian Bunk (2018-01-06 21:02:02)
> I've prepared an NMU for basilisk2 (versioned as 0.9.20120331-4.1) and 
> uploaded it to DELAYED/5. Please feel free to tell me if I should 
> cancel it.

Excellent. Thanks a lot!

 - Jonas

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

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


signature.asc
Description: signature

Processed: bug 883987 is forwarded to https://svn.boost.org/trac10/ticket/12534

[Debian Bug Tracking System]

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

> forwarded 883987 https://svn.boost.org/trac10/ticket/12534
Bug #883987 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884184 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Bug #884185 [src:boost1.62] FTBFS error: partial specialization ... after 
instantiation ... (with patch)
Set Bug forwarded-to-address to 'https://svn.boost.org/trac10/ticket/12534'.
Set Bug forwarded-to-address to 'https://svn.boost.org/trac10/ticket/12534'.
Set Bug forwarded-to-address to 'https://svn.boost.org/trac10/ticket/12534'.
> thanks
Stopping processing here.

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

Bug#883987: [pkg-boost-devel] Bug#883987: boost1.62: FTBFS error: partial specialization ... after instantiation ... (with patch)

[Steve Robbins]

On Saturday, January 6, 2018 5:25:28 AM CST Pierre Saramito wrote:
> Hi all,
> 
> Any news from the boost package maintainers for this bug ?
> 
> A patch is available for this bug (see attachement)
> and it should be easy to fix it now.

Appreciate the reminder.  I should be able to upload today.

-Steve


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

Processed: found 874727 in 3.1.4~abc9f50+dfsg3-2, notfound 874727 in 3.1.4-abc9f50+dfsg3-2

[Debian Bug Tracking System]

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

> found 874727 3.1.4~abc9f50+dfsg3-2
Bug #874727 [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other 
library that uses lebexpat1 segfaults.
Marked as found in versions coin3/3.1.4~abc9f50+dfsg3-2.
> notfound 874727 3.1.4-abc9f50+dfsg3-2
Bug #874727 [libcoin80v5] libcoin80v5: Program using libcoin80v5 and any other 
library that uses lebexpat1 segfaults.
There is no source info for the package 'libcoin80v5' at version 
'3.1.4-abc9f50+dfsg3-2' with architecture ''
Unable to make a source version for version '3.1.4-abc9f50+dfsg3-2'
No longer marked as found in versions 3.1.4-abc9f50+dfsg3-2.
> thanks
Stopping processing here.

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

Bug#856098: gnuboy: diff for NMU version 1.0.3-7.1

[Adrian Bunk]

Control: tags 856098 + patch
Control: tags 856098 + pending
Control: tags 857666 + patch
Control: tags 857666 + pending

Dear maintainer,

I've prepared an NMU for gnuboy (versioned as 1.0.3-7.1) and uploaded
it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -u gnuboy-1.0.3/debian/control gnuboy-1.0.3/debian/control
--- gnuboy-1.0.3/debian/control
+++ gnuboy-1.0.3/debian/control
@@ -2,7 +2,7 @@
 Section: contrib/games
 Priority: optional
 Maintainer: Davide Puricelli (evo) 
-Build-Depends: debhelper (>> 5), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaudiofile-dev, libaa1-dev, libesd0-dev, libncurses5-dev  
+Build-Depends: debhelper (>> 5), libx11-dev, libxext-dev, libxt-dev, x11proto-xext-dev, libsdl1.2-dev, libaa1-dev, libncurses5-dev  
 Standards-Version: 3.8.3.0
 
 Package: gnuboy-sdl
diff -u gnuboy-1.0.3/debian/changelog gnuboy-1.0.3/debian/changelog
--- gnuboy-1.0.3/debian/changelog
+++ gnuboy-1.0.3/debian/changelog
@@ -1,3 +1,11 @@
+gnuboy (1.0.3-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove the unused libaudiofile-dev and libesd0-dev
+build dependencies. (Closes: #856098, #857666)
+
+ -- Adrian Bunk   Sat, 06 Jan 2018 22:04:05 +0200
+
 gnuboy (1.0.3-7) unstable; urgency=low
 
   * Acknowledging previous NMUs, thanks Moritz! closes: #72. 

Processed: gnuboy: diff for NMU version 1.0.3-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 856098 + patch
Bug #856098 [src:gnuboy] gnuboy: Please drop the (build-)dependency against 
esound
Added tag(s) patch.
> tags 856098 + pending
Bug #856098 [src:gnuboy] gnuboy: Please drop the (build-)dependency against 
esound
Added tag(s) pending.
> tags 857666 + patch
Bug #857666 [src:gnuboy] gnuboy: unused B-D on libaudiofile-dev
Added tag(s) patch.
> tags 857666 + pending
Bug #857666 [src:gnuboy] gnuboy: unused B-D on libaudiofile-dev
Added tag(s) pending.

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

Processed: basilisk2: diff for NMU version 0.9.20120331-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 856075 + patch
Bug #856075 [src:basilisk2] basilisk2: Please drop the (build-)dependency 
against esound
Added tag(s) patch.
> tags 856075 + pending
Bug #856075 [src:basilisk2] basilisk2: Please drop the (build-)dependency 
against esound
Added tag(s) pending.
> tags 865145 + pending
Bug #865145 [src:basilisk2] basilisk2: please build-depend on automake, not 
obsolete automake1.11
Added tag(s) pending.

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

Bug#856075: basilisk2: diff for NMU version 0.9.20120331-4.1

[Adrian Bunk]

Control: tags 856075 + patch
Control: tags 856075 + pending
Control: tags 865145 + pending

Dear maintainer,

I've prepared an NMU for basilisk2 (versioned as 0.9.20120331-4.1) and 
uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru basilisk2-0.9.20120331/debian/changelog basilisk2-0.9.20120331/debian/changelog
--- basilisk2-0.9.20120331/debian/changelog	2015-09-21 21:52:57.0 +0300
+++ basilisk2-0.9.20120331/debian/changelog	2018-01-06 21:36:30.0 +0200
@@ -1,3 +1,11 @@
+basilisk2 (0.9.20120331-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build without support for the obsolete esound. (Closes: #856075)
+  * Use automake instead of automake1.11. (Closes: #865145)
+
+ -- Adrian Bunk   Sat, 06 Jan 2018 21:36:30 +0200
+
 basilisk2 (0.9.20120331-4) unstable; urgency=low
 
   [ Giulio Paci ]
diff -Nru basilisk2-0.9.20120331/debian/control basilisk2-0.9.20120331/debian/control
--- basilisk2-0.9.20120331/debian/control	2015-09-21 21:50:05.0 +0300
+++ basilisk2-0.9.20120331/debian/control	2018-01-06 21:36:30.0 +0200
@@ -9,12 +9,11 @@
 Build-Depends: cdbs,
  autotools-dev,
  devscripts,
- automake1.11,
+ automake,
  autoconf,
  debhelper,
  dh-buildinfo,
  libgtk2.0-dev,
- libesd0-dev,
  libsdl-dev,
  libxxf86dga-dev,
  libxxf86vm-dev
diff -Nru basilisk2-0.9.20120331/debian/rules basilisk2-0.9.20120331/debian/rules
--- basilisk2-0.9.20120331/debian/rules	2015-09-21 21:47:18.0 +0300
+++ basilisk2-0.9.20120331/debian/rules	2018-01-06 21:36:30.0 +0200
@@ -24,7 +24,7 @@
 # add JIT compiler when supported
 DEB_MAKE_FLAVORS += $(if $(filter amd64 i386,$(DEB_HOST_ARCH)),jit)
 
-DEB_AUTO_UPDATE_ACLOCAL = 1.11
+DEB_AUTO_UPDATE_ACLOCAL = ,
 DEB_ACLOCAL_ARGS = -I m4
 DEB_AUTO_UPDATE_AUTOHEADER = 2.68
 DEB_AUTO_UPDATE_AUTOCONF = 2.68
@@ -72,4 +72,4 @@
 	rm -f  src/Unix/aclocal.m4 src/Unix/config.h.in src/Unix/configure
 
 # Needed by upstream build process
-CDBS_BUILD_DEPENDS += , libgtk2.0-dev, libesd0-dev, libsdl-dev, libxxf86dga-dev, libxxf86vm-dev
+CDBS_BUILD_DEPENDS += , libgtk2.0-dev, libsdl-dev, libxxf86dga-dev, libxxf86vm-dev

Processed: merge 886470 886495

[Debian Bug Tracking System]

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

> reassign 886495 nvidia-kernel-dkms
Bug #886495 [nvidia-driver] nvidia-driver: Fails to build against 4.14.0-3
Bug reassigned from package 'nvidia-driver' to 'nvidia-kernel-dkms'.
No longer marked as found in versions nvidia-graphics-drivers/384.98-3.
Ignoring request to alter fixed versions of bug #886495 to the same values 
previously set
> merge 886470 886495
Bug #886470 [nvidia-kernel-dkms] nvidia-kernel-dkms: FTBFS against linux 
4.14.12-2
Bug #886495 [nvidia-kernel-dkms] nvidia-driver: Fails to build against 4.14.0-3
Marked as found in versions nvidia-graphics-drivers/384.98-3.
Added tag(s) pending.
Merged 886470 886495
> thanks
Stopping processing here.

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

Bug#886494: polymake: Can't locate loadable object for module Polymake::Ext in @INC

[Niko Tyni]

Package: polymake
Version: 3.1-5
Severity: grave
X-Debbugs-Cc: p...@packages.debian.org

Running polymake currently fails with

  $ polymake
  Can't locate loadable object for module Polymake::Ext in @INC (@INC contains: 
/usr/share/polymake/perllib /usr/lib/polymake/perlx/5.26.0 
/usr/lib/polymake/perlx /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 
/usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/share/polymake/perllib/Polymake/Namespaces.pm line 17.
  Compilation failed in require at 
/usr/share/polymake/perllib/Polymake/Namespaces.pm line 17.
  BEGIN failed--compilation aborted at 
/usr/share/polymake/perllib/Polymake/Namespaces.pm line 17.
  Compilation failed in require at /usr/share/polymake/perllib/Polymake.pm line 
27.
  BEGIN failed--compilation aborted at /usr/share/polymake/perllib/Polymake.pm 
line 27.
  Compilation failed in require at /usr/bin/polymake line 162.
  BEGIN failed--compilation aborted at /usr/bin/polymake line 162.
 
Apparently this is because it was built with Perl 5.26.0, but
we've since moved to 5.26.1.

There's an open binnmu request at #883933 but I don't think that's the
correct way to fix this as it makes no provisions for partial upgrades.

I see two better alternatives:

1) [preferrable] fix polymake not to install its extensions in a
  versioned directory (currently /usr/lib/polymake/perlx/5.26.0).
  This may be as simple as

--- a/lib/core/src/perl/Makefile.PL
+++ b/lib/core/src/perl/Makefile.PL
@@ -140,7 +140,7 @@ WriteMakefile(
 LIBS=> "$libpaths $AddLibs",
 DEFINE  => "-DPerlVersion=$numvers -Wno-nonnull".($coverage && ' 
-DPMCollectCoverage=1'),
 INC => "-I$TOP/include/core",
-LIB => "\$(InstallDir)/perlx/$Config::Config{version}",
+LIB => "\$(InstallDir)/perlx",
 MAN3PODS=> { },
 @optimize,
 );

but I haven't tested that (the package is huge...)

2) [less preferrable] add binnmu-safe strict dependencies on the current
   Perl version. See for instance libdevel-cover-perl for an example of
   how to do this. If you do this, please let p...@packages.debian.org know
   so we can update
 https://wiki.debian.org/PerlMaintenance#New_upstream_release_checklist
   (and/or feel free to add to it yourself.)

I note that the confusing @INC list above (it has
/usr/lib/polymake/perlx/5.26.0 so it looks like it should work) is
because "use lib" will add versioned subdirectories to @INC if it
finds any, but will apparently *not* add arch-specific subdirectories
(like /usr/lib/polymake/perlx/5.26.0/x86_64-linux-gnu-thread-multi)
under those, and that's what would be needed here. I'm not quite sure
if this is a glitch in lib.pm's handling of binary-compatible versions
($Config{inc_version_list}).

Hope this helps a bit,
-- 
Niko

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

> Try also booting without 'quiet' and with 'debug earlyprintk'.

Happy to try, but not sure how to do that - do I edit
/boot/config-4.9.0-5-686-pae ?  Couldn't see "QUIET" in there?

> If you manage to get a kernel log (using a
> serial port or maybe netconsole if it's not too early in the boot) it'd
> help I guess.

The box has a serial port, but not sure I've got anything to plug into it!
I might have an old Debian box somewhere... :)

Thanks,
LJ

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[Yves-Alexis Perez]

On Sat, 2018-01-06 at 18:04 +, LJ wrote:
> > Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> > you
> > could provide your full /proc/cpuinfo?
> 
> Hi, sure...

Thanks
> 
> root@sam:~# cat /proc/cpuinfo
> processor   : 0
> vendor_id   : GenuineIntel
> cpu family  : 6
> model   : 60
> model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz

So definitely not a Xeon E3, but Haswell generation.

> flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
> rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
> aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
> sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
> xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> tsc_adjust erms invpcid xsaveopt dtherm arat pln pts

So with pcid/invpcid.

Right now I'm unsure what to do. If you manage to get a kernel log (using a
serial port or maybe netconsole if it's not too early in the boot) it'd help I
guess.

Try also booting without 'quiet' and with 'debug earlyprintk'.

If you have the possibility to build a 4.9.75 kernel and try booting it might
help (at one point I might have a Debian build for you but that's not the case
right now).

Regards,
-- 
Yves-Alexis

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

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

> Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> you
> could provide your full /proc/cpuinfo?

Hi, sure...

root@sam:~# cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping: 3
microcode   : 0x22
cpu MHz : 1097.680
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs:
bogomips: 5587.41
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Celeron(R) CPU G1840 @ 2.80GHz
stepping: 3
microcode   : 0x22
cpu MHz : 1199.877
cache size  : 2048 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fdiv_bug: no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc
aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer
xsave rdrand lahf_lm abm tpr_shadow vnmi flexpriority ept vpid fsgsbase
tsc_adjust erms invpcid xsaveopt dtherm arat pln pts
bugs:
bogomips: 5587.41
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

Thanks,
LJ

Bug#885793: marked as done (tldr-py,tldr: File collision when installing together: /usr/bin/tldr (and maybe further files))

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 18:20:08 +
with message-id 
and subject line Bug#885793: fixed in haskell-tldr 0.2.3-2
has caused the Debian Bug report #885793,
regarding tldr-py,tldr: File collision when installing together: /usr/bin/tldr 
(and maybe further files)
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.)


-- 
885793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tldr-py,tldr
Severity: serious
Control: found -1 tldr-py/0.7.0-1
Control: found -1 haskell-tldr/0.2.3-1

Hi,

installing tldr when tldr-py is already installed fails as follows since
both packages ship /usr/bin/tldr (and maybe further files like e.g. man
pages. etc.):

Preparing to unpack .../tldr_0.2.3-1_amd64.deb ...
Unpacking tldr (0.2.3-1) ...
dpkg: error processing archive /var/cache/apt/archives/tldr_0.2.3-1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/bin/tldr', which is also in package tldr-py 0.7.0-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/tldr_0.2.3-1_amd64.deb

Please either conflict with each other or both start using
update-alternatives (if suitable wrt. commandline options, etc.) to
choose between the different implementations.

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

Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: haskell-tldr
Source-Version: 0.2.3-2

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-tldr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 13:03:43 -0500
Source: haskell-tldr
Binary: libghc-tldr-dev libghc-tldr-prof libghc-tldr-doc tldr
Architecture: source
Version: 0.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-tldr-dev -
 libghc-tldr-doc -
 libghc-tldr-prof -
 tldr   -
Closes: 885793
Changes:
 haskell-tldr (0.2.3-2) unstable; urgency=medium
 .
   * Manage /usr/bin/tldr and /usr/share/man/man1/tldr.1 with
 alternatives.  closes: #885793 .
   * Patch tldr to not initialize ~/.tldr if the user is just doing
 a --help or --version.
   * Generate man page with help2man.
Checksums-Sha1:
 d723b1f4ad9e9f86c5341ab24e88fb3a41d79891 2577 haskell-tldr_0.2.3-2.dsc
 a9ecfe6e090fe5cbee55db5a323dcf90e1162854 4170 haskell-tldr_0.2.3.orig.tar.gz
 3f9be4bdda0934089508d68e0955fd4bce90db04 2936 
haskell-tldr_0.2.3-2.debian.tar.xz
 5bc5069834872e06a8382c4478bda48385634872 8105 
haskell-tldr_0.2.3-2_source.buildinfo
Checksums-Sha256:
 6e5b43e071e8cd036cd6db15354c96868544a565819d76255ea576c670b2315b 2577 
haskell-tldr_0.2.3-2.dsc
 f24cd350fc9ee15ff533acf5c14af20d17c38244324f4e10817cbba5c44aaf87 4170 
haskell-tldr_0.2.3.orig.tar.gz
 fa53226159645738d763bff4bca346b09acb0434f2879321395e8652a397ae50 2936 
haskell-tldr_0.2.3-2.debian.tar.xz
 93e5660b05002ad8c53f057e40468653c5c773286bcf4efa87a896d5d63324af 8105 
haskell-tldr_0.2.3-2_source.buildinfo
Files:
 bafcc1de9e5dbe56d797ee50fcb7e795 2577 haskell optional haskell-tldr_0.2.3-2.dsc
 916c76a08904feaab31c92a93b13998d 4170 haskell optional 
haskell-tldr_0.2.3.orig.tar.gz
 2871757581a295b2a886eec8decec363 2936 haskell optional 
haskell-tldr_0.2.3-2.debian.tar.xz
 a23763c7f5848101efd8bdc167736686 8105 haskell optional 
haskell-tldr_0.2.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian!

iQKlBAEBCgCPFiEEdYHsh0BT5sgHeRubVZIzHhmdOKg

Bug#885282: gameclock: Depends on unmaintained pygtk

[Antoine Beaupré]

Control: forwarded -1 https://gitlab.com/anarcat/gameclock/issues/1

Understood.

Processed: Re: Bug#885282: gameclock: Depends on unmaintained pygtk

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/anarcat/gameclock/issues/1
Bug #885282 [src:gameclock] gameclock: Depends on unmaintained pygtk
Set Bug forwarded-to-address to 'https://gitlab.com/anarcat/gameclock/issues/1'.

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

Processed: Re: Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +patch
Bug #880246 [src:magic-wormhole] magic-wormhole: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 3.6 returned exit code 13
Added tag(s) patch.

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

Bug#880246: magic-wormhole: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13

[Antoine Beaupré]

Control: tags -1 +patch

On 2018-01-01 23:24:14, Harlan Lieberman-Berg wrote:
> Hello Antoine,
>
> I ran into this recently, so I thought I'd take a quick whack at
> seeing if I can fix it by updating to the latest version of
> magic-wormhole.  Unfortunately, that FTBFS as well, due to a bunch of
> problems (including with some of its dependencies).  I've poked at a
> couple of the upstreams, but still waiting for them to merge stuff.
> (https://github.com/meejah/txtorcon/issues/247 causes test failures;
> waiting on the author to merge my PR).
>
> I've attached my work thus far as patches, so you have them.  I can
> also push them up directly to collab-maint, if you prefer.

I'm fine with you pushing to collab-maint - this is what it's for after
all. :)

So even after this you still FTBFS? Did you report that issue upstream
as well?

A.

-- 
L'ennui avec la grande famille humaine, c'est que tout le monde veut
en être le père.
- Mafalda

Bug#886489: FTBFS: json_object.c:554:5: error: this statement may fall through [-Werror=implicit-fallthrough=]

[Jonas Meurer]

Source: json-c
Version: 0.12.1-1
Severity: serious
Justification: fails to build from source

Dear Maintainer,

json-c fails to build from source due to a potential implicit
fall-through in function json_object_get_int64() from json_object.c:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -Werror -Wno-error=deprecated-declarations 
-Wno-error=unused-but-set-variable -Wextra -Wwrite-strings 
-Wno-unused-parameter -std=gnu99 -D_GNU_SOURCE -D_REENTRANT -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c json_object.c  -fPIC -DPIC -o .libs/json_object.o
json_object.c: In function 'json_object_get_int64':
json_object.c:554:5: error: this statement may fall through 
[-Werror=implicit-fallthrough=]
  if (json_parse_int64(jso->o.c_string.str, &cint) == 0) return cint;
 ^
json_object.c:555:3: note: here
   default:
   ^~~
cc1: all warnings being treated as errors
Makefile:578: recipe for target 'json_object.lo' failed
make[3]: *** [json_object.lo] Error 1
make[3]: Leaving directory '/<>'


A quick look at the latest upstream release gave me the impression that
his might have been fixed upstream in release 0.13:

https://github.com/json-c/json-c/blob/json-c-0.13-20171207/json_object.c#L697-L703

Cheers
 jonas

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

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

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[Yves-Alexis Perez]

On Sat, 2018-01-06 at 15:46 +, LJ wrote:
> Booting in recovery mode the final lines are:
> 
> [   0.058600] x86: Booting SMP configuration:
> [   0.058632]  node  #0, CPUs:  :1
> 
> The cursor is flashing after the "#1" and the system hangs at that point.
> 
> I have video and a screenshot of boot if that helps.

Looking at the lspci output you have a Xeon E3 from the 1200 series, but you
could provide your full /proc/cpuinfo?

You're running the system in 32bit mode, which KAISER/KPTI doesn't touch (so
meltdown is *not* fixed), so I guess it comes from the preparation patches for
 KAISER rather than KAISER itself.

Regards,
-- 
Yves-Alexis

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

Processed: tagging 886485, affects 886485

[Debian Bug Tracking System]

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

> tags 886485 - security
Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " 
node  #0, CPUs:#1"
Removed tag(s) security.
> affects 886485 + security.debian.org
Bug #886485 [src:linux] linux-image-4.9.0-5-686-pae: Hangs on boot at " 
node  #0, CPUs:#1"
Added indication that 886485 affects security.debian.org
> thanks
Stopping processing here.

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

Bug#886485: linux-image-4.9.0-5-686-pae: Hangs on boot at ".... node #0, CPUs: #1"

[LJ]

Package: src:linux
Version: 4.9.65-3+deb9u2
Severity: critical
Tags: security
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
Updated the system as requested in Debian Security Advisory DSA-4078-1

Booting in recovery mode the final lines are:

[   0.058600] x86: Booting SMP configuration:
[   0.058632]  node  #0, CPUs:  :1

The cursor is flashing after the "#1" and the system hangs at that point.

I have video and a screenshot of boot if that helps.

Thanks,
LJ


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM 
Controller [8086:0c00] (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM 
Controller [1458:5000]
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: hsw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th 
Gen Core Processor Integrated Graphics Controller [8086:0402] (rev 06) (prog-if 
00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <1us, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-
 Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, 
EqualizationComplete-, EqualizationPhase1-
 EqualizationPhase2-, EqualizationPhase3-, 
LinkEqualizationRequest-
Capabilities: [80] MSI: Enable- Count=1/1 Maskable- 64bit-
Address:   Data: 
Capabilities: [90] Subsystem: Gigabyte Technology Co., Ltd 8 
Series/C220 Series Chipset Family PCI Express Root Port [1458:5001]
Capabilities: [a0] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset 
Family PCI Express Root Port #3 [8086:8c14] (rev d5) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
 

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 862847 buster sid
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Added tag(s) sid and buster.
> tags 824678 buster sid
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Added tag(s) sid and buster.
Added tag(s) buster and sid.
> tags 824679 buster sid
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Added tag(s) buster and sid.
> tags 753723 buster sid
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Added tag(s) sid and buster.
Added tag(s) sid and buster.
> tags 862851 buster sid
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Added tag(s) sid and buster.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886470: nvidia-kernel-dkms: FTBFS against linux 4.14.12-2

[Luca Boccassi]

Control: tags -1 pending

On Sat, 6 Jan 2018 14:51:40 +0100 Sebastian Ramacher  wrote:
> Package: nvidia-kernel-dkms
> Version: 384.98-3
> Severity: grave
> Justification: renders package unusable
> 
> The build of kernel module fails against linux 4.14.12-2:
> | make: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
> | /usr/src/linux-headers-4.14.0-3-common/Makefile:947: *** "Cannot
generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-
dev, libelf-devel or elfutils-libelf-devel".  Stop.

See #886474 - I have added the dependency to the dkms packages as a
workaround.


> After installing libelf-dev, it fails further down:
> |gcc-7 -Wp,-MD,/var/lib/dkms/nvidia-current/384.98/build/nvidia-
uvm/.uvm8_pte_batch.o.d  -nostdinc -isystem /usr/lib/gcc/x86_64-linux-
gnu/7/include -I/usr/src/linux-headers-4.14.0-3-common/arch/x86/include 
-I./arch/x86/include/generated  -I/usr/src/linux-headers-4.14.0-3-
common/include -I./include -I/usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/uapi -I./arch/x86/include/generated/uapi
-I/usr/src/linux-headers-4.14.0-3-common/include/uapi
-I./include/generated/uapi -include /usr/src/linux-headers-4.14.0-3-
common/include/linux/kconfig.h  -I/var/lib/dkms/nvidia-
current/384.98/build -I/var/lib/dkms/nvidia-current/384.98/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 -mno-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 -Wno-format-truncation -Wno-
format-overflow -Wno-int-in-bool-context -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
-fno-stack-check -fconserve-stack -Werror=implicit-int -Werror=strict-
prototypes -Werror=date-time -Werror=incompatible-pointer-types
-Werror=designated-init  -I/var/lib/dkms/nvidia-
current/384.98/build/common/inc  -I/var/lib/dkms/nvidia-
current/384.98/build -Wall -MD -Wsign-compare -Wno-cast-qual -Wno-error 
-D__KERNEL__ -DMODULE -DNVRM -DNV_VERSION_STRING=\"384.98\" -Wno-
unused-function -Wuninitialized -fno-strict-aliasing -mno-red-zone
-mcmodel=kernel -DNV_UVM_ENABLE -Wno-sign-compare -Wno-format-extra-
args -Werror=undef -O2 -DNVIDIA_UVM_ENABLED
-DNVIDIA_UNDEF_LEGACY_BIT_MACROS -DLinux -D__linux__  -
I/var/lib/dkms/nvidia-current/384.98/build/nvidia-uvm  -DMODULE  -
DKBUILD_BASENAME='"uvm8_pte_batch"'  -DKBUILD_MODNAME='"nvidia_uvm"' -c
-o /var/lib/dkms/nvidia-current/384.98/build/nvidia-
uvm/.tmp_uvm8_pte_batch.o /var/lib/dkms/nvidia-
current/384.98/build/nvidia-uvm/uvm8_pte_batch.c
> | In file included from /usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/asm/cpufeature.h:5:0,
> |  from /usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/asm/thread_info.h:53,
> |  from /usr/src/linux-headers-4.14.0-3-
common/include/linux/thread_info.h:38,
> |  from /usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/asm/preempt.h:7,
> |  from /usr/src/linux-headers-4.14.0-3-
common/include/linux/preempt.h:81,
> |  from /usr/src/linux-headers-4.14.0-3-
common/include/linux/spinlock.h:51,
> |  from /var/lib/dkms/nvidia-
current/384.98/build/common/inc/nv-lock.h:16,
> |  from /var/lib/dkms/nvidia-
current/384.98/build/common/inc/nv-linux.h:19,
> |  from /var/lib/dkms/nvidia-
current/384.98/build/nvidia-uvm/uvm_linux.h:39,
> |  from /var/lib/dkms/nvidia-
current/384.98/build/nvidia-uvm/uvm8_va_block.c:24:
> | /var/lib/dkms/nvidia-current/384.98/build/nvidia-
uvm/uvm8_va_block.c: In function ‘block_cpu_fault_locked’:
> | /usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/asm/processor.h:826:39: error: implicit
declaration of function ‘task_stack_page’; did you mean
‘task_stack_vm_area’? [-Werror=implicit-function-declaration]
> |   unsigned long __ptr = (unsigned long)task_stack_page(task); \
> |^
> | /usr/src/linux-headers-4.14.0-3-
common/arch/x86/include/asm/processor.h:909:26: note: in expansion of
macro ‘task_pt_regs’
> |  #define KSTK_EIP(task)  (task_pt_regs(task)->ip)
> | 

Processed: Re: nvidia-kernel-dkms: FTBFS against linux 4.14.12-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #886470 [nvidia-kernel-dkms] nvidia-kernel-dkms: FTBFS against linux 
4.14.12-2
Added tag(s) pending.

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

Processed: Re: Bug#878338: gcc-defaults FTBFS with debhelper 10.9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #878338 [src:gcc-defaults] gcc-defaults FTBFS with debhelper 10.9
Added tag(s) pending.

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

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

[Matthias Klose]

Control: tags -1 + pending

fixed in the packaging VCS

On 06.01.2018 14:09, John Paul Adrian Glaubitz wrote:
>> dh_compress: unknown option or error during option parsing; aborting
>> debian/rules:1354: recipe for target 'binary-native' failed
>> make: *** [binary-native] Error 25
> 
> I'm running into this on ia64 now but I'm not sure whom to blame.
> 
> "Unknown option or error" doesn't make it seem that debhelper is
> working as expected, is it? At least there should be a comprehensible
> error message.
> 
> Adrian
> 

Processed: Re: Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xen-hypervisor-4.8-amd64
Bug #880554 [linux-image-4.9.0-4-amd64] xen domu freezes with kernel 
linux-image-4.9.0-4-amd64
Bug reassigned from package 'linux-image-4.9.0-4-amd64' to 
'xen-hypervisor-4.8-amd64'.
No longer marked as found in versions linux/4.9.51-1.
Ignoring request to alter fixed versions of bug #880554 to the same values 
previously set

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

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Yves-Alexis Perez]

control: reassign -1 xen-hypervisor-4.8-amd64

On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote:
> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> > According to that link, the fix seems to be configuration rather than
> > code.
> > Does this mean this bug against the kernel should be closed?
> 
> Yes, the problem seems to be in the Xen hypervisor and not the Linux
> kernel itself.  The default value for the gnttab_max_frames parameter
> needs to be increased to avoid domU disk IO hangs, for example:
> 
>   GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256"
> 
> So either close the bug or reassign it to xen-hypervisor package so
> they can increase the default value for this parameter in the
> hypervisor code.
> 
Ok, I'll reassign and let the Xen maintainers handle that (maybe in a stable
update).

@Xen maintainers: see the complete bug log for more information, but basically
it seems that a domu freezes happens with the “new” multi-queue xen blk
driver, and the fix is to increase a configuration value. Valentin suggests
adding that to the default.

Regards,
-- 
Yves-Alexis

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

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Valentin Vidic]

On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> According to that link, the fix seems to be configuration rather than code.
> Does this mean this bug against the kernel should be closed?

Yes, the problem seems to be in the Xen hypervisor and not the Linux
kernel itself.  The default value for the gnttab_max_frames parameter
needs to be increased to avoid domU disk IO hangs, for example:

  GRUB_CMDLINE_XEN="dom0_mem=10240M gnttab_max_frames=256"

So either close the bug or reassign it to xen-hypervisor package so
they can increase the default value for this parameter in the
hypervisor code.

-- 
Valentin

Processed: still using transitional package dependency, will become uninstallable

[Debian Bug Tracking System]

Processing control commands:

> severity 753723 serious
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Ignoring request to change severity of Bug 753723 to the same value.
Ignoring request to change severity of Bug 862853 to the same value.
> severity 841001 serious
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Ignoring request to change severity of Bug 841001 to the same value.
Ignoring request to change severity of Bug 824678 to the same value.
> severity 824679 serious
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Ignoring request to change severity of Bug 824679 to the same value.
> severity 862847 serious
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Ignoring request to change severity of Bug 862847 to the same value.
> severity 862851 serious
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Ignoring request to change severity of Bug 862851 to the same value.

-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: still using transitional package dependency, will become uninstallable

[Debian Bug Tracking System]

Processing control commands:

> severity 753723 serious
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Ignoring request to change severity of Bug 753723 to the same value.
Ignoring request to change severity of Bug 862853 to the same value.
> severity 841001 serious
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Ignoring request to change severity of Bug 841001 to the same value.
Ignoring request to change severity of Bug 824678 to the same value.
> severity 824679 serious
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Ignoring request to change severity of Bug 824679 to the same value.
> severity 862847 serious
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Ignoring request to change severity of Bug 862847 to the same value.
> severity 862851 serious
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Ignoring request to change severity of Bug 862851 to the same value.

-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: still using transitional package dependency, will become uninstallable

[Debian Bug Tracking System]

Processing control commands:

> severity 753723 serious
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Ignoring request to change severity of Bug 753723 to the same value.
Ignoring request to change severity of Bug 862853 to the same value.
> severity 841001 serious
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Ignoring request to change severity of Bug 841001 to the same value.
Ignoring request to change severity of Bug 824678 to the same value.
> severity 824679 serious
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Ignoring request to change severity of Bug 824679 to the same value.
> severity 862847 serious
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Ignoring request to change severity of Bug 862847 to the same value.
> severity 862851 serious
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Ignoring request to change severity of Bug 862851 to the same value.

-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#824679: still using transitional package dependency, will become uninstallable

[Luca Boccassi]

Control: severity 753723 serious
Control: severity 841001 serious
Control: severity 824679 serious
Control: severity 862847 serious
Control: severity 862851 serious

Apparently gedit (without closing the window after save) + mutt is not
a good combination...

The uploads are to DELAYED/5.

Kind regards,
Luca Boccassi

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

Processed: still using transitional package dependency, will become uninstallable

[Debian Bug Tracking System]

Processing control commands:

> severity 753723 serious
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> severity 841001 serious
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 824679 serious
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Severity set to 'serious' from 'important'
> severity 862847 serious
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Severity set to 'serious' from 'important'
> severity 862851 serious
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Severity set to 'serious' from 'normal'

-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: still using transitional package dependency, will become uninstallable

[Debian Bug Tracking System]

Processing control commands:

> severity 753723 serious
Bug #753723 [lsat] lsat: please suggest iproute2 instead of iproute 
transitional package
Bug #862853 [lsat] lsat: Please switch to iproute2 package
Ignoring request to change severity of Bug 753723 to the same value.
Ignoring request to change severity of Bug 862853 to the same value.
> severity 841001 serious
Bug #841001 [arno-iptables-firewall] arno-iptables-firewall: Depend on iproute2 
rather then iproute?
Bug #824678 [arno-iptables-firewall] arno-iptables-firewall: please depend on 
iproute2 instead of iproute transitional package
Ignoring request to change severity of Bug 841001 to the same value.
Ignoring request to change severity of Bug 824678 to the same value.
> severity 824679 serious
Bug #824679 [ipkungfu] ipkungfu: please depend on iproute2 instead of iproute 
transitional package
Ignoring request to change severity of Bug 824679 to the same value.
> severity 862847 serious
Bug #862847 [apf-firewall] apf-firewall: Please switch to iproute2 package
Ignoring request to change severity of Bug 862847 to the same value.
> severity 862851 serious
Bug #862851 [vblade-persist] vblade-persist: Please switch to iproute2 package
Ignoring request to change severity of Bug 862851 to the same value.

-- 
753723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753723
824678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824678
824679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824679
841001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841001
862847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862847
862851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862851
862853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#886476: caja-seahorse: Depends on deprecated libgnome-keyring

[Jeremy Bicha]

Source: caja-seahorse
Version: 1.18.3-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs libgnome-keyring-removal

Hi,

The libgnome-keyring library is deprecated and its usage is strongly
discouraged [1].

Your package caja-seahorse declares a build-dependency on
libgnome-keyring-dev or links against libgnome-keyring0.

Please update your application to use libsecret instead [2].
Such a port should ideally happen with upstream being involved.

On behalf of the Debian GNOME team,
Jeremy Bicha

[1] https://git.gnome.org/browse/libgnome-keyring/commit/?id=6a5adea4aec93
[2] https://wiki.gnome.org/Projects/Libsecret

Processed: ucarp: diff for NMU version 1.5.2-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 753719 + patch
Bug #753719 [ucarp] ucarp: please recommend iproute2 instead of iproute 
transitional package
Bug #862852 [ucarp] ucarp: Please switch to iproute2 package
Added tag(s) patch.
Added tag(s) patch.
> tags 753719 + pending
Bug #753719 [ucarp] ucarp: please recommend iproute2 instead of iproute 
transitional package
Bug #862852 [ucarp] ucarp: Please switch to iproute2 package
Added tag(s) pending.
Added tag(s) pending.
> severity -1 serious
Bug #753719 [ucarp] ucarp: please recommend iproute2 instead of iproute 
transitional package
Bug #862852 [ucarp] ucarp: Please switch to iproute2 package
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'

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

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

[Niko Tyni]

On Sat, Jan 06, 2018 at 02:03:21PM +0100, Axel Beckert wrote:

> Yes, indeed, that looks much more sane now. Might be related to this
> bug fix in expat 2.2.5:
> 
>#137 #138  Fix a case of mistakenly reported parsing success where
> XML_StopParser was called from an element handler

Yes. The relevant change seems to be

 
https://github.com/libexpat/libexpat/commit/718d51a66b0d69f3b8c5ff63d044c36dd5314232

as reverting that made the error go away for me.

Changing the libnih test suite to accomodate the expat fix seems correct
to me too fwiw. Thanks for your work on this!
-- 
Niko Tyni   nt...@debian.org

Bug#880554: xen domu freezes with kernel linux-image-4.9.0-4-amd64

[Yves-Alexis Perez]

On Fri, 2017-11-17 at 07:39 +0100, Valentin Vidic wrote:
> Hi,
> 
> The problem seems to be caused by the new multi-queue xen blk driver
> and I was advised by the Xen devs to increase the gnttab_max_frames=256
> parameter for the hypervisor.  This has solved the blocking issue
> for me and it has been running without problems for a few months now.

I'm not really fluent in Xen, but does this relate to the kernel in dom0 or
one of the domU then? 
> 
> I/O to LUNs hang / stall under high load when using xen-blkfront
> https://www.novell.com/support/kb/doc.php?id=7018590

According to that link, the fix seems to be configuration rather than code.
Does this mean this bug against the kernel should be closed?

Regards,
-- 
Yves-Alexis

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

Bug#886416: marked as done (libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line numbering)" and is now uninstallable due now failing BinNMU)

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 13:49:28 +
with message-id 
and subject line Bug#886416: fixed in libnih 1.0.3-10
has caused the Debian Bug report #886416,
regarding libnih: FTBFS with expat 2.2.5: "FAIL test_parse (unexpected line 
numbering)" and is now uninstallable due now failing BinNMU
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.)


-- 
886416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnih
Version: 1.0.3-9
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Affects: systemd-shim

libnih was made uninstallable by the glibc 2.26 transition, because it
uses internal glibc symbols. Normally this would be handled by a simple
rebuild. However, the recent binNMU of libnih against glibc 2.26 failed:

> Testing parse_xml()
> ...
> BAD: wrong content in file 0x13be5e730 (output), expected 'test:foo:2:0: 
> Invalid object path in  name attribute
> ' got 'test:foo:1:36: Invalid object path in  name attribute
> '
>at tests/test_parse.c:7954 (test_parse_xml).
> FAIL test_parse (exit status: 134)

I don't know whether the test failure is triggered by glibc 2.26, or by
something else that changed since November.

This is particularly nasty because the missing binNMU makes libnih
(and hence systemd-shim) uninstallable; and until #883569 and #883573
are resolved, that's going to cause problems on the buildds whenever
a chain of (build-)dependencies pulls in libpam-systemd, because apt
apparently commits to installing systemd-shim and is not able to roll
back far enough to consider installing systemd-sysv instead.

smcv
--- End Message ---
--- Begin Message ---
Source: libnih
Source-Version: 1.0.3-10

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated libnih package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 06 Jan 2018 14:28:28 +0100
Source: libnih
Binary: libnih1 libnih-dev libnih-dbus1 libnih-dbus-dev nih-dbus-tool
Architecture: source amd64
Version: 1.0.3-10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Axel Beckert 
Description:
 libnih-dbus-dev - NIH D-Bus Bindings Library (development files)
 libnih-dbus1 - NIH D-Bus Bindings Library
 libnih-dev - NIH Utility Library (development files)
 libnih1- NIH Utility Library
 nih-dbus-tool - NIH D-Bus Binding Tool
Closes: 886416
Changes:
 libnih (1.0.3-10) unstable; urgency=medium
 .
   * QA upload.
   * Adapt test suite to expat 2.2.5. (Closes: #886416)
   * Declare compliance with Debian Policy 4.1.3.
   * Bump debhelper compatibility level to 11.
 + Update versioned debhelper build-dependency accordingly.
   * Update Vcs-* headers for switch to salsa.debian.org.
Checksums-Sha1:
 2991dbeda2765e2bebd37f71f1831a0844e3781e 2169 libnih_1.0.3-10.dsc
 db2485fe5596c9127c45eb96827bf7b7fd5080a7 9428 libnih_1.0.3-10.debian.tar.xz
 3634ce516fb7c714d6dd4850ac2437709f67139b 106280 
libnih-dbus-dev_1.0.3-10_amd64.deb
 45efc1993e501c5354281a2c0d1d0d7fdfdc315c 29968 
libnih-dbus1-dbgsym_1.0.3-10_amd64.deb
 7c1f22893eb7d07c2dccec8fbf55d4156bc13f37 97744 libnih-dbus1_1.0.3-10_amd64.deb
 ab3958b3956ac5c5b051302a4a8967e9e9492393 153336 libnih-dev_1.0.3-10_amd64.deb
 460cabffa40360d164c29cd45a29d4db20255acf 91348 
libnih1-dbgsym_1.0.3-10_amd64.deb
 2e4c27c69567fcefa3f72512e23da952b36eceb7 126448 libnih1_1.0.3-10_amd64.deb
 f263f9bac9851890238966418fa0673fb32459a3 7563 libnih_1.0.3-10_amd64.buildinfo
 c4fc0e874ffe199b239e3c9da255a0194157480a 114512 
nih-dbus-tool-dbgsym_1.0.3-10_amd64.deb
 2a515cdfa0078da1cf3258fa92968afc371a8688 135708 
nih-dbus-tool_1.0.3-10_amd64.deb
Checksums-Sha256:
 ebb817a2d068ad2cc77510bd774a5c7aa2da7ddb8a0ad95d1c99cb68187d56e2 2169 
libnih_1.0.3-10.dsc
 e8fa98507f820127c74269aecc23cd2a1276e01f3967cebecdfb0be59db227d4 9428 
libnih_1.0.3-10.debian.tar.xz
 00325fd521508696d5ab473a6a2416544d8b9f468738621fa5f8c59cabd2

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

[Adrian Bunk]

On Sat, Jan 06, 2018 at 02:09:44PM +0100, John Paul Adrian Glaubitz wrote:
> > dh_compress: unknown option or error during option parsing; aborting
> > debian/rules:1354: recipe for target 'binary-native' failed
> > make: *** [binary-native] Error 25
> 
> I'm running into this on ia64 now but I'm not sure whom to blame.
> 
> "Unknown option or error" doesn't make it seem that debhelper is
> working as expected, is it? At least there should be a comprehensible
> error message.

The comprehensive error messages are above, check the lines
  dh_compress: Requested unknown package ... via -N/--no-package, expected one 
of: ...

cu
Adrian

-- 

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

Bug#885989: Downgrade the severity of this bug, or close it

[Jeremy Lainé]

TLS guarantees you have established a secure connection to the host name 
you requested, nothing else. If a host name resolves to cloudflare's 
servers, that's the domain owner's decision. Almost every production 
deployment involves reverse proxies at one point or another (terminating 
TLS in the application server is exceedingly rare), so "end to end 
encryption" is definitely not the promise.


Suggested that detecting certain headers to flag "man in the middle 
attacks" is not a serious claim either.


This bug report should be closed as wontfix, and should not hold up a 
transition from unstable to testing.


Jeremy

Bug#878338: gcc-defaults FTBFS with debhelper 10.9

[John Paul Adrian Glaubitz]

> dh_compress: unknown option or error during option parsing; aborting
> debian/rules:1354: recipe for target 'binary-native' failed
> make: *** [binary-native] Error 25

I'm running into this on ia64 now but I'm not sure whom to blame.

"Unknown option or error" doesn't make it seem that debhelper is
working as expected, is it? At least there should be a comprehensible
error message.

Adrian

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

Processed: Re: Bug#883526 closed by Andreas Rönnquist (Bug#883526: fixed in geeqie 1:1.4-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #883526 {Done: Andreas Rönnquist } [src:geeqie] geeqie 
build does not trap errors from make
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions geeqie/1:1.4-1.
> affects 882785 + src:geeqie
Bug #882785 [libgdk-pixbuf2.0-dev] move gdk-pixbuf-csource to a Multi-Arch: 
foreign package
Added indication that 882785 affects src:geeqie

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

Bug#883526: closed by Andreas Rönnquist (Bug#883526: fixed in geeqie 1:1.4-1)

[Helmut Grohne]

Control: reopen -1
Control: affects 882785 + src:geeqie

On Wed, Jan 03, 2018 at 11:21:06PM +, Debian Bug Tracking System wrote:
>* New upstream version 1.4
>  - Really fixes the problems with trapping errors (Closes: 883526)

I'm very sorry to reopen this bug again, but this fix doesn't quite cut
it. I goes a long way, but is still incomplete.

This is how it looks like when gdk-pixbuf-csource[1] fails to run now:

|dh_auto_build -a -O--parallel -O--fail-missing
| make -j1
| make[1]: Entering directory '/<>'
| make  all-recursive
| make[2]: Entering directory '/<>'
| Making all in src
| make[3]: Entering directory '/<>/src'
| Making all in icons
| make[4]: Entering directory '/<>/src/icons'
| Making all in svg
| make[5]: Entering directory '/<>/src/icons/svg'
| make[5]: Nothing to be done for 'all'.
| make[5]: Leaving directory '/<>/src/icons/svg'
| make[5]: Entering directory '/<>/src/icons'
| sh: 1: /usr/bin/gdk-pixbuf-csource: Exec format error
| !!! Failed to generate icons_inline.h !!!
| make[5]: Leaving directory '/<>/src/icons'
| make[4]: Leaving directory '/<>/src/icons'
| make[4]: Entering directory '/<>/src'
| powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/lua5.1-I.. -I.. -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Werror -Wno-error=deprecated-declarations 
-Wno-error=sign-compare -Wno-error=return-type -c -o ui_bookmark.o ui_bookmark.c
| powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/lua5.1-I.. -I.. -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Werror -Wno-error=deprecated-declarations 
-Wno-error=sign-compare -Wno-error=return-type -c -o ui_fileops.o ui_fileops.c
| powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/lua5.1-I.. -I.. -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Werror -Wno-error=deprecated-declarations 
-Wno-error=sign-compare -Wno-error=return-type -c -o ui_help.o ui_help.c
| powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/powerpc64le-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/lua5.1-I.. -I.. -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Werror -Wno-error=deprecated-declarations 
-Wno-error=sign-compare -Wno-error=return-type -c -o ui_menu.o ui_menu.c
| powerpc64le-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

[Axel Beckert]

Control: tag -1 + pending

Hi Simon,

Simon McVittie wrote:
> > > -   TEST_FILE_EQ (output, ("test:foo:2:0: "
> > > +   TEST_FILE_EQ (output, ("test:foo:1:36: "
> > >"Invalid object path in  
> > > name attribute\n"));
[…]
> It certainly seems more true to say that the error in
> "\n" is at line 1 column 36 (the
> closing double quote around the invalid object path) than at line 2
> column 0 (after the newline).

Argh! Thanks for enlightening me what these numbers mean!

Yes, indeed, that looks much more sane now. Might be related to this
bug fix in expat 2.2.5:

   #137 #138  Fix a case of mistakenly reported parsing success where
XML_StopParser was called from an element handler

> > I'd appreciate some more eyes on that change as I have not much of an
> > idea of libnih's guts.
> 
> I have no idea about how libnih works, but the change looks harmless at
> worst - it's not as if it changes the behaviour of non-test code, and the
> new output looks more correct than the old.

Thanks for the review! Will prepare an upload.

> (My only interest in libnih is in keeping libpam-systemd installable
> on buildds.)

(My only interest in libnih is in being able to continue to not have to
use systemd as init system on my systems without having to uninstall
about 500 packages. :-P)

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #886416 [src:libnih] libnih: FTBFS with expat 2.2.5: "FAIL test_parse 
(unexpected line numbering)" and is now uninstallable due now failing BinNMU
Added tag(s) pending.

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

Bug#886367: IMPORTANT: ARE they (Chip-Makers) creasy! -- Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured HW-Factories!

[Patrik Lori]

STOP, STOP, STOP -> ALL THIS "Microcode-Patch" Infos!
=

If Intel, AMD, ARM, .. now communicating, that they can change the 
CPU/MMU-Microcode outside there secured factories; they send (with this) very 
dangerous messages to all hackers.

Hackers can use "the same procedure" to do the oposit of these patches!

Changing CPU/MMU-Microcodes MUST NOT BE POSSIBLE outside the secured 
HW-Factories!

Otherwize, we are all in great new SECURITY-DANGER!

I hope the CPU/MMU-Microcode - Patch can NOT be manipulated or canceled 
afterwards !!!

Kind regards
Patrik
 


ifs³ Consulting+Engineering
Patrik Lori
CTO, cert. Computer Engineer & MAS-BA
Panoramastr. 6, 5625 Kallern, Switzerland
 
Web:http://www.ifs3.com 
Email:  patrik.l...@ifs3.com 
Mobile:+41 79 326 75 97
 
CONFIDENTIALITY NOTICE: This e-mail message including attachments, if any, is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any unauthorised review, use, 
disclosure or distribution is prohibited. If you are not the intended 
recipient, please contact the sender by reply e-mail and destroy all copies of 
the original message. If you are the intended recipient but do not wish to 
receive communications through this medium, please do advise the sender 
immediately.

Bug#886416: libnih: uninstallable, and FTBFS when rebuilt: FAIL test_parse (unexpected line numbering)

[Simon McVittie]

On Sat, 06 Jan 2018 at 03:01:35 +0100, Axel Beckert wrote:
> Axel Beckert wrote:
> > I don't know if that test suite failure shows that expat broke libnih
> > or if the test suite just needs to be adapted to the new expat
> > version.
> >  
> > -   TEST_FILE_EQ (output, ("test:foo:2:0: "
> > +   TEST_FILE_EQ (output, ("test:foo:1:36: "
> >"Invalid object path in  name 
> > attribute\n"));
> > TEST_FILE_END (output);
> > TEST_FILE_RESET (output);

It certainly seems more true to say that the error in
"\n" is at line 1 column 36 (the
closing double quote around the invalid object path) than at line 2
column 0 (after the newline).

> I'd appreciate some more eyes on that change as I have not much of an
> idea of libnih's guts.

I have no idea about how libnih works, but the change looks harmless at
worst - it's not as if it changes the behaviour of non-test code, and the
new output looks more correct than the old. (My only interest in libnih
is in keeping libpam-systemd installable on buildds.)

smcv

Bug#883987: boost1.62: FTBFS error: partial specialization ... after instantiation ... (with patch)

[Pierre Saramito]

Hi all,

Any news from the boost package maintainers for this bug ?

A patch is available for this bug (see attachement)
and it should be easy to fix it now.

It affects the Rheolef package: there is a BinNMU issue still pending.

Many thanks for your help and reactivity,

Pierre
--
pierre.saram...@imag.fr
Directeur de Recherche CNRS
Laboratoire Jean Kuntzmann, Grenoble, France
http://ljk.imag.fr/membres/Pierre.Saramito
// bug description
// https://svn.boost.org/trac10/ticket/12534
// and its fix in boost-dev 1.65:
// https://github.com/boostorg/container/commit/5e4a107e82ab3281688311d22d2bfc2fddcf84a3
// i.e. remove from line 431 to 460 in include/boost/container/detail/pair.hpp

#undef FIX_BUG
#ifdef  FIX_BUG
#include 
#endif // FIX_BUG

#include 

static const bool is_enum = boost::is_enum >::value;

#include 

boost::container::flat_map m;

int main() {}
*** /usr/include/boost/container/detail/pair.hpp.orig	Tue Dec 12 12:15:26 2017
--- /usr/include/boost/container/detail/pair.hpp	Tue Dec 12 12:41:22 2017
***
*** 416,451 
  }  //namespace container_detail {
  }  //namespace container {
  
- 
- //Without this specialization recursive flat_(multi)map instantiation fails
- //because is_enum needs to instantiate the recursive pair, leading to a compilation error).
- //This breaks the cycle clearly stating that pair is not an enum avoiding any instantiation.
- template
- struct is_enum;
- 
- template
- struct is_enum< ::boost::container::container_detail::pair >
- {
-static const bool value = false;
- };
- 
- template
- struct is_enum< ::std::pair >
- {
-static const bool value = false;
- };
- 
- template 
- struct is_class;
- 
- //This specialization is needed to avoid instantiation of pair in
- //is_class, and allow recursive maps.
- template 
- struct is_class< ::boost::container::container_detail::pair >
- {
-static const bool value = true;
- };
- 
  #ifdef BOOST_NO_CXX11_RVALUE_REFERENCES
  
  template
--- 416,421 

Processed: #886433

[Debian Bug Tracking System]

Processing control commands:

> tag -1 confirmed pending
Bug #886433 [src:org-mode-doc] org-mode-doc: Incomplete debian/copyright?
Added tag(s) confirmed and pending.

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

Bug#886433: #886433

[Sébastien Delafond]

Control: tag -1 confirmed pending

The testing/ directory is new in recent in org-mode releases, and I
missed it when repacking org-mode-doc. I'll fix correct this with the
next upstream release.

Cheers,

--Seb

Bug#881205: Assistance for maintaining src:backintime

[Ghislain Vaillant]

Dear Jonathan,

I was suprised to discover that backintime had been removed from
testing despite RC bug #881205 being fixed upstream [1].

For testing/unstable an update of the package to version 1.1.24 should
do the trick, whilst stretch/wheezy will require a backport of this
particular commit.

I was wondering whether you need any help with the maintenance of the
package, which I'd be happy to offer. It might also be useful to move
the package to team-maintenance long term, under collab-maint or one of
the Python packaging teams.

[1] https://github.com/bit-team/backintime/commit/cef81d0da93ff60125260
7df3db1a48f7f6f01

Cheers,
Ghis

Bug#886125: marked as done (slic3r: Binaries except slic3r cannot find Slic3r.pm)

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 09:36:37 +
with message-id 
and subject line Bug#886125: fixed in slic3r 1.2.9+dfsg-9
has caused the Debian Bug report #886125,
regarding slic3r: Binaries except slic3r cannot find Slic3r.pm
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.)


-- 
886125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: slic3r
Version: 1.2.9+dfsg-6.1~deb9u1
Severity: serious
Control: found -1 1.2.9+dfsg-6.1

The binaries shipped except slic3r cannot find Slic3r.pm
in the non-standard location, e.g.:

$ split_stl
Can't locate Slic3r.pm in @INC (you may need to install the Slic3r module) 
(@INC contains: /usr/bin/../lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/usr/bin/split_stl line 14.
BEGIN failed--compilation aborted at /usr/bin/split_stl line 14.
$
--- End Message ---
--- Begin Message ---
Source: slic3r
Source-Version: 1.2.9+dfsg-9

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r 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: Fri, 05 Jan 2018 17:30:58 +0800
Source: slic3r
Binary: slic3r
Architecture: source amd64
Version: 1.2.9+dfsg-9
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Chow Loong Jin 
Description:
 slic3r - G-code generator for 3D printers
Closes: 886125
Changes:
 slic3r (1.2.9+dfsg-9) unstable; urgency=medium
 .
   * [1ae29f4] Patch "use lib" line in all installed binaries (Closes: #886125)
Checksums-Sha1:
 ddc8216308817e9b0b4ebf0ebee573136cb6dcaf 2439 slic3r_1.2.9+dfsg-9.dsc
 d6e1386e47ab07d0ff7a99de41f743ebe1f6c269 31864 
slic3r_1.2.9+dfsg-9.debian.tar.xz
 56fbce408399985bbb21d5aa674b6989c65fda85 7513600 
slic3r-dbgsym_1.2.9+dfsg-9_amd64.deb
 66d0549f20d42064db2f5ef928e564e410129776 19827 
slic3r_1.2.9+dfsg-9_amd64.buildinfo
 a0f4e1e9d1020b519c3b684fe562ac6367fafbcc 1218932 slic3r_1.2.9+dfsg-9_amd64.deb
Checksums-Sha256:
 9a8195d8e965497c3530d812c96f58da970e2955680adcf9a07558d5d859cded 2439 
slic3r_1.2.9+dfsg-9.dsc
 9d5d9d7848059fd873067ed6f06fd44692cbdcc4617081d9af25ee9be81e9a1c 31864 
slic3r_1.2.9+dfsg-9.debian.tar.xz
 f8ff8c431e369df66d6b341b98e1124dc7e05151f54eba3db79b73ffa6f3daf6 7513600 
slic3r-dbgsym_1.2.9+dfsg-9_amd64.deb
 7c1ff1a39e68c7c2ef1456c57b30059e45f0bbf050692bf5c9af6e8ab56faac9 19827 
slic3r_1.2.9+dfsg-9_amd64.buildinfo
 240aa81832c93a4b5cd012f463b43cf12b8513552655e27c8b49e9621e22e5ae 1218932 
slic3r_1.2.9+dfsg-9_amd64.deb
Files:
 331ab7f389541ed8127ac764ad257a71 2439 perl optional slic3r_1.2.9+dfsg-9.dsc
 fc166352ad56033ca7b2a1d8e7ecf600 31864 perl optional 
slic3r_1.2.9+dfsg-9.debian.tar.xz
 003fadb78ddd3f8e4cf631b0e2d4001c 7513600 debug optional 
slic3r-dbgsym_1.2.9+dfsg-9_amd64.deb
 2e9891af44be054a6fe903992fb63916 19827 perl optional 
slic3r_1.2.9+dfsg-9_amd64.buildinfo
 5426594464c9099ef663196fa2d956e6 1218932 perl optional 
slic3r_1.2.9+dfsg-9_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJaUJLLAAoJEPvVIltYh1Khu4IP/2IoFKspbJIGAc+5MVdNcQpJ
O6ikWJHrF3U5WkPFDXP687Q+19kuHkr2tAAvWD3jZzpfa9G/wl2yLCjqgN7ar8Sq
WvURnETM6lAjw20E7OK4K6diYI4RllyQqe/8szMOXJjqjKWnNSeZxM4BSMs+j8oA
Oz+RXMdA8qIAKYiGjyf11bhgOyl7BANv0oKCnoBRdLEGT0JPf5ZHYL7eC+GJZT6p
rDYzqLt5WoR+IN1HzgVAWhXkTi4nv8KFsT/Z2EIOWUMIwW0dulGXRaS9qlQ5UfCx
ymzfpPkK72RuS/lacg6zEtman4IEbTdPQgL38uKynh1ns1x8OuqKkmVpZlQbeNkr
nviAfekFfFmmiqjOKUEeOpeTbWgEB71FRUUqFjhHqnnfeka2ZT1CfAqMabSDyvPO
MFbodRd0ADZGocAwoRpNB4gXvA20LIGtWZMrb85d8K0h1XRM62j2xf5EECZVEVid
NsyAvJsWtrD5vDSaFOHivwG6++FkRbXfcl4l67y8M+STB0MQd/7v+GnOSh3N+svn
xCCOBowH7l5lkA9QwJV5idonLOXFhAlCQD63bcyuZo0ZkiW6ECiXPHAjw52i3Eu8
b0CHVN9B9ZxnnkxY40yNeaN6ci/+GxCbiBR+mOz708RI/wcLl+O3uarT5IpSKgQv

Bug#886453: [src:zfs-linux]

[Antonio Russo]

Control: reassign -1 spl-linux 0.7.4-1

The bug affects building spl.

Also for anyone trying to build this, you can build objtool in the
tools/objtool directory of the linux source (apt source linux). Then
copy it to

/usr/src/linux-headers-4.14.0-3-amd64/tools/objtool/objtool

Processed: [src:zfs-linux]

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 spl-linux 0.7.4-1
Bug #886453 [src:zfs-linux] [src:spl-linux] Fails to build for 4.14.0-3
Bug reassigned from package 'src:zfs-linux' to 'spl-linux'.
No longer marked as found in versions zfs-linux/0.7.4-1.
Ignoring request to alter fixed versions of bug #886453 to the same values 
previously set
Bug #886453 [spl-linux] [src:spl-linux] Fails to build for 4.14.0-3
There is no source info for the package 'spl-linux' at version '0.7.4-1' with 
architecture ''
Unable to make a source version for version '0.7.4-1'
Marked as found in versions 0.7.4-1.

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

Bug#886434: marked as done (libcitadel FTBFS with "dpkg-buildpackage -B")

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 09:19:13 +
with message-id 
and subject line Bug#886434: fixed in libcitadel 917-2
has caused the Debian Bug report #886434,
regarding libcitadel FTBFS with "dpkg-buildpackage -B"
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.)


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

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

...
 fakeroot debian/rules binary-arch
make: Nothing to be done for 'binary-arch'.
 dpkg-genbuildinfo --build=any
dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless
dpkg-buildpackage: error: dpkg-genbuildinfo --build=any subprocess returned 
exit status 25


This is caused by the following 916-1 -> 917-1 change in debian/rules:

-binary-arch: build install debian/libcitadel4.install 
debian/libcitadel-dev.install
+binary: build install debian/libcitadel4.install debian/libcitadel-dev.install
--- End Message ---
--- Begin Message ---
Source: libcitadel
Source-Version: 917-2

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

Debian distribution maintenance software
pp.
Michael Meskes  (supplier of updated libcitadel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Jan 2018 09:54:15 +0100
Source: libcitadel
Binary: libcitadel4 libcitadel-dev
Architecture: source amd64
Version: 917-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Citadel Team 
Changed-By: Michael Meskes 
Description:
 libcitadel-dev - Development files for libcitadel4
 libcitadel4 - Citadel toolbox
Closes: 886434
Changes:
 libcitadel (917-2) unstable; urgency=medium
 .
   * Re-added rules target that was lost in the last version. (Closes: #886434)
Checksums-Sha1:
 0d91cc651dd024052664a63616f1b84d3ee65e27 2098 libcitadel_917-2.dsc
 7209dbfb933dd1ce6a3d6c64a3e871bf65239b57 10338 libcitadel_917-2.diff.gz
 ca0f16780e733b933f73f93a575fa6343b8d724f 76744 libcitadel-dev_917-2_amd64.deb
 049da737fb66843373026dc793becd717563ad57 147712 
libcitadel4-dbgsym_917-2_amd64.deb
 7abcfc1f79b45773970c6cb4483a1d9d76cc9922 67716 libcitadel4_917-2_amd64.deb
 90331ebde0f45bb2706a92c0fc92d1565f80502a 6097 libcitadel_917-2_amd64.buildinfo
Checksums-Sha256:
 875497e71b958859622787ea601a8346bce08f168e9d2b5f42a29aac62c372b2 2098 
libcitadel_917-2.dsc
 075d620320e20391256c20ec26493d1909ed97163493367bec832dee12a79a55 10338 
libcitadel_917-2.diff.gz
 1354ab6f135a1267a9f1f82256e27ca30d728ecdfe27944b8a97695843ee0419 76744 
libcitadel-dev_917-2_amd64.deb
 2f6b4f4e41eb7d2d7616b4159693dea9cbc3924aa2e80bfb039e63161e45829b 147712 
libcitadel4-dbgsym_917-2_amd64.deb
 ff67e02348e8e049556d2dce6641fcb0b89c961fa3d903d2242beb43bea69d4f 67716 
libcitadel4_917-2_amd64.deb
 62a4ff961a8863f6ada64c11301f896773909d1c71c910d6cbe05dfa8bd3b7a6 6097 
libcitadel_917-2_amd64.buildinfo
Files:
 e9f2b837998fec19effbe0ca9237e56e 2098 libs optional libcitadel_917-2.dsc
 8a917e722ab87c328f56c237f9ce6d78 10338 libs optional libcitadel_917-2.diff.gz
 5db4423d3c6d543978582021230a0f45 76744 libdevel optional 
libcitadel-dev_917-2_amd64.deb
 c66ac80f1027f641fc1bd15ab5e15123 147712 debug optional 
libcitadel4-dbgsym_917-2_amd64.deb
 a4d9a1b5f4ddc228877a2fdc31541344 67716 libs optional 
libcitadel4_917-2_amd64.deb
 895ee96636e5857ee256d391ce770179 6097 libs optional 
libcitadel_917-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEZ/2RWVGI6sRsEOjtNdhXwLvLOyUFAlpQj9oWHG1lc2tlc0Bw
b3N0Z3Jlc3FsLm9yZwAKCRA12FfAu8s7JcK3D/9+ZjQH0Mx3+pLwFYGfabKnC1H/
8kLbl2icljKO9JibocABXDZoRiPObMpNnZonpbGtye+Hse7l1Z8a/06sHwb691Wz
dkDAzlDvryePk8LSSQwHqvV054MXGu3shuQEUKU7C1UieUOdstZy22yd0t2b1Ogb
HM6aYGvF5GOiSlVm5GNx9kndt+zetJRFH4OOtDryu0jyoe+otpJNlj0qb4KBfVJl
rTNPK00vek7q8eLPcciodNnpbU+37dDA+4CC61sZH12topuMLT9wHc13uP0EEvEO
vARi/N6OzX4dYrwiIsxImxXssmdFIJpq2Rh2z0+qd/rTl5FobISilkBLriTpVJqT
QIabfBpyq7u4gCK1Lt75eJUe4t+Wy6XrSJac0tz27hobUsLEWEY4uOjmCiiJEbao
rr8cIgVEe

Bug#886385: marked as done (netsniff-ng: FTBFS: error: inlining failed in call to always_inline '__builtin_memset')

[Debian Bug Tracking System]

Your message dated Sat, 06 Jan 2018 09:06:05 +
with message-id 
and subject line Bug#886385: fixed in netsniff-ng 0.6.4-1
has caused the Debian Bug report #886385,
regarding netsniff-ng: FTBFS: error: inlining failed in call to always_inline 
'__builtin_memset'
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.)


-- 
886385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netsniff-ng
Version: 0.6.3-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

netsniff-ng fails to build from source in unstable/amd64:

  […]

  gcc -g -O2 -fdebug-prefix-map=«BUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 
-DVERSION_STRING=\""0.6.3"""\" -DVERSION_LONG=\""0.6.3"" (Mookid)"\" 
-DETCDIRE_STRING=\"/etc/netsniff-ng\" -I. -DNEED_TCPDUMP_LIKE_FILTER 
-I/usr/include/libnl3 -I/usr/include/libnl3 -I/usr/include/libnl3 
-DNEED_TCPDUMP_LIKE_FILTER -I/usr/include/libnl3 -I/usr/include/libnl3 
-I/usr/include/libnl3 -o netsniff-ng/proto_ipv4.o -c proto_ipv4.c
  In file included from /usr/include/features.h:419:0,
   from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
   from /usr/include/stdio.h:27,
   from proto_ipv4.c:8:
  /usr/include/x86_64-linux-gnu/bits/string_fortified.h: In function 'ipv4':
  built_in.h:69:19: error: inlining failed in call to always_inline 
'__builtin_memset': function body not available
   # define fmemset  __builtin_memset
 ^
  In file included from /usr/include/string.h:494:0,
   from die.h:8,
   from geoip.h:8,
   from proto_ipv4.c:17:
  /usr/include/x86_64-linux-gnu/bits/string_fortified.h:71:10: note: called 
from here
 return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest));
^
  In file included from /usr/include/features.h:419:0,
   from 
/usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
   from /usr/include/stdio.h:27,
   from proto_ipv4.c:8:
  built_in.h:69:19: error: inlining failed in call to always_inline 
'__builtin_memset': function body not available
   # define fmemset  __builtin_memset
 ^
  In file included from /usr/include/string.h:494:0,
   from die.h:8,
   from geoip.h:8,
   from proto_ipv4.c:17:
  /usr/include/x86_64-linux-gnu/bits/string_fortified.h:71:10: note: called 
from here
 return __builtin___memset_chk (__dest, __ch, __len, __bos0 (__dest));
^
  Makefile:184: recipe for target 'netsniff-ng/proto_ipv4.o' failed
  make[1]: *** [netsniff-ng/proto_ipv4.o] Error 1
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:29: recipe for target 'build-stamp' failed
  make: *** [build-stamp] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

  […]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


netsniff-ng.0.6.3-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: netsniff-ng
Source-Version: 0.6.4-1

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated netsniff-ng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 06 Jan 2018 10:31:15 +0530
Source: netsniff-ng
Binary: netsniff-ng
Architecture: source amd64
Version: 0.6.4-1
Distribution: unstable
Urgency: low
Mai