Bug#883938: fixed in linux 3.16.51-3

[Thomas Martin]

Hi all,

I saw that the package 3.16.51-3 is now available in jessie-update.
Is there any chance to have this package available in jessie
repository before the next point release ?


Thomas

Processed: Re: Bug#884655: lintian: multiarch-foreign-static-library for non-multiarch package

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #884655 [lintian] lintian: multiarch-foreign-static-library for 
non-multiarch package
Severity set to 'serious' from 'important'
> tags -1 patch
Bug #884655 [lintian] lintian: multiarch-foreign-static-library for 
non-multiarch package
Added tag(s) patch.

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

Bug#884654: glib2.0 FTBFS on amd64: gdbus test suite failures

[Helmut Grohne]

Source: glib2.0
Version: 2.54.2-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

glib2.0 fails to build from source on amd64. This happens both on the
buildd
https://buildd.debian.org/status/fetch.php?pkg=glib2.0&arch=amd64&ver=2.54.2-2&stamp=1513222982&raw=0
and on the reproducible infrastructure
https://tests.reproducible-builds.org/debian/logs/unstable/amd64/glib2.0_2.54.2-2.build2.log.gz.
Though reproducible experiences more failures (including gwakeup and
gmenumodel). It seems unlikely that this fixes itself somehow.

Helmut

Processed: tagging 884293, tagging 882141, found 875505 in 1.8.13-9 ..., found 882059 in 0.3.1-1, tagging 882059 ...

[Debian Bug Tracking System]

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

> tags 884293 + sid buster experimental
Bug #884293 [src:kcalutils] kcalutils: Cannot fulfill the build dependencies
Added tag(s) buster, sid, and experimental.
> # this is not stretch-only
> tags 882141 - stretch
Bug #882141 {Done: Scott Kitterman } [src:postfix] postfix 
- systemd generator broken with inet_interfaces
Removed tag(s) stretch.
> found 875505 1.8.13-9
Bug #875505 [src:doxygen] doxygen: build-dependency ruby-compass obsolete and 
broken
Marked as found in versions doxygen/1.8.13-9.
> retitle 884597 mono-runtime-common: Fail to install mono-runtime-common:i386 
> on amd64
Bug #884597 [mono-runtime-common] mono-runtime-common: Fail to install 
mono-runtime-common:i386
Changed Bug title to 'mono-runtime-common: Fail to install 
mono-runtime-common:i386 on amd64' from 'mono-runtime-common: Fail to install 
mono-runtime-common:i386'.
> # should be working in wheezy
> found 882059 0.3.1-1
Bug #882059 [ibus-tegaki] rewrite ibus-tegaki with GObject introspection (GI)
Marked as found in versions ibus-tegaki/0.3.1-1.
> tags 882059 + sid buster
Bug #882059 [ibus-tegaki] rewrite ibus-tegaki with GObject introspection (GI)
Added tag(s) buster and sid.
> tags 884616 + sid buster
Bug #884616 [python-visual] exception "ValueError: The truth value..." on import
Added tag(s) sid and buster.
> found 858693 4.0.0+dfsg1-3
Bug #858693 [congress-server] congress-server: Missing dependency net-tools
Marked as found in versions congress/4.0.0+dfsg1-3.
> fixed 858693 6.0.0+dfsg1-1
Bug #858693 [congress-server] congress-server: Missing dependency net-tools
Marked as fixed in versions congress/6.0.0+dfsg1-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
858693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858693
875505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875505
882059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882059
882141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882141
884293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884293
884597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884597
884616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837628: marked as done (Removal of Heimdal from testing)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2017 05:19:20 +
with message-id 
and subject line Bug#837628: fixed in libheimdal-kadm5-perl 0.08-5
has caused the Debian Bug report #837628,
regarding Removal of Heimdal from testing
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.)


-- 
837628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkadm5-heimdal-perl
Severity: normal

Just an FYI to let you know that the heimdal maintainers are planning to remove 
Heimdal from testing because of its upstream state. (See the severe bugs filed 
against it for details)

For other packages that are built against heimdal, we have suggested building 
against MIT instead. That is probably not as easy as option here.
--- End Message ---
--- Begin Message ---
Source: libheimdal-kadm5-perl
Source-Version: 0.08-5

We believe that the bug you reported is fixed in the latest version of
libheimdal-kadm5-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Russ Allbery  (supplier of updated libheimdal-kadm5-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Dec 2017 20:55:21 -0800
Source: libheimdal-kadm5-perl
Binary: libheimdal-kadm5-perl
Architecture: source amd64
Version: 0.08-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Russ Allbery 
Description:
 libheimdal-kadm5-perl - Perl module to administer a Heimdal Kerberos KDC
Closes: 670517 837628
Changes:
 libheimdal-kadm5-perl (0.08-5) unstable; urgency=medium
 .
   * Build with current Heimdal.  (Closes: #837628)
   * Guard against a NULL mod_name in getModName and return undef.  Thanks,
 Sergio Gelato.  (Closes: #670517)
   * Strip out the -rpath setting from the Heimdal krb5-config --libs call.
 This isn't necessary; the libraries are installed in the normal
 library search path.
   * Strip the LD_RUN_PATH setting added by ExtUtils::MakeMaker out of the
 generated Makefile before building the package.
   * Fix spelling errors in manual page caught by Lintian.
   * Convert to a proper 3.0 (quilt) package with managed patches.
   * Contribute the package to the Debian Perl Group.
 - Change Maintainer to the group.
 - Add myself to Uploaders.
 - Change Homepage to the metacpan.org URL.
 - Change Vcs-Git and Vcs-Browser to point to the pkg-perl repository.
 - Change debian/watch to use the metacpan.org URL.
   * Update debhelper compatibility level to V11.
   * Update standards version to 4.1.2.
 - Rewrite copyright file in copyright-format 1.0.
 - Change priority to optional.
   * Run wrap-and-sort -ast.
Checksums-Sha1:
 0926c519120b6618a50e13b478ea351e786bf4ee 1740 libheimdal-kadm5-perl_0.08-5.dsc
 d93dd3646c01819d6e68aa0e3547ff752ecd3f5d 5680 
libheimdal-kadm5-perl_0.08-5.debian.tar.xz
 e272d2a86109224da9b27c19474f1f575cb640cc 60152 
libheimdal-kadm5-perl-dbgsym_0.08-5_amd64.deb
 f55e85f9ee3708a6f3989159b8152f36542328e6 6474 
libheimdal-kadm5-perl_0.08-5_amd64.buildinfo
 dd2e586a5a1628b209d6fe74c766db3795a23f5d 28520 
libheimdal-kadm5-perl_0.08-5_amd64.deb
Checksums-Sha256:
 8420a81529fcd9377e5a4b6a51ef04f829ac58dd3dbd3b5e95f896818a90fd1a 1740 
libheimdal-kadm5-perl_0.08-5.dsc
 cec31de1c5cf1cbe69a235aa7d52dc00c0d816a048060cbc5c82d6d2d784e27b 5680 
libheimdal-kadm5-perl_0.08-5.debian.tar.xz
 572dba18a513d45bca42294c631406d2eb90ee3a934900dee8fef4f97810a634 60152 
libheimdal-kadm5-perl-dbgsym_0.08-5_amd64.deb
 6c2432cfffd0e76fce282e743018b348f87d2c0eabd4b1dba612d1e1bdbe3a34 6474 
libheimdal-kadm5-perl_0.08-5_amd64.buildinfo
 cf36e190c28701b882b84c947af636d2211ae5330400e749b64156ac7baf4ae9 28520 
libheimdal-kadm5-perl_0.08-5_amd64.deb
Files:
 530c8404bd7c38cb4f40acb74d592cb3 1740 perl optional 
libheimdal-kadm5-perl_0.08-5.dsc
 8064852b4022203e20ab2ac4e031187d 5680 perl optional 
libheimdal-kadm5-perl_0.08-5.debian.tar.xz
 7bca424792244e124ef3754c74475ec0 60152 debug optional 
libheimdal-kadm5-perl-dbgsym_0.08-5_amd64.deb
 bee9fb24d3fc18df5cd8a38dbbb99d89 6474 perl optiona

Bug#884542: [pkg-go] Bug#884542: prometheus-mysqld-exporter FTBFS: FAIL: TestScrapeInnodbMetrics

[Martín Ferrari]

Adrian,

Thanks for the report. I presume this error is due to the change in the
Prometheus' common library. I am already preparing a new upstream
release, but that is waiting on an upstream bug:
https://github.com/prometheus/mysqld_exporter/issues/251


On 16/12/17 12:03, Adrian Bunk wrote:
> Source: prometheus-mysqld-exporter
> Version: 0.9.0+ds-3
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes prometheus-mysqld-exporter FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/prometheus-mysqld-exporter.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-mysqld-exporter.html
> 
> ...
> === RUN   TestScrapeInnodbMetrics
> --- FAIL: TestScrapeInnodbMetrics (0.00s)
>   info_schema_innodb_metrics_test.go:17: no such flag -log.level



-- 
Martín Ferrari (Tincho)

Processed: found 884417 in 0.7.16-2

[Debian Bug Tracking System]

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

> found 884417 0.7.16-2
Bug #884417 [trezor] trezor: fails to upgrade from 'testing' - trying to 
overwrite /usr/bin/trezorctl
Marked as found in versions python-trezor/0.7.16-2.
> thanks
Stopping processing here.

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

Bug#884645: qupzilla-plugin-{gnome-keyring,kwallet}: fails to upgrade from 'testing' - trying to overwrite /usr/lib/x86_64-linux-gnu/qupzilla/lib{GnomeKeyring,KWallet}Passwords.so

[Andreas Beckmann]

Package: qupzilla-plugin-gnome-keyring,qupzilla-plugin-kwallet
Version: 2.2.2~dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package qupzilla-plugin-gnome-keyring.
  Preparing to unpack 
.../193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb ...
  Unpacking qupzilla-plugin-gnome-keyring (2.2.2~dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-jSbyKA/193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qupzilla/libGnomeKeyringPasswords.so', which is also 
in package libqupzilla1 2.2.0~dfsg1-2
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-jSbyKA/193-qupzilla-plugin-gnome-keyring_2.2.2~dfsg1-1_amd64.deb

  Selecting previously unselected package qupzilla-plugin-kwallet.
  Preparing to unpack .../193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb 
...
  Unpacking qupzilla-plugin-kwallet (2.2.2~dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-Azhy0x/193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qupzilla/libKWalletPasswords.so', which is also in 
package libqupzilla1 2.2.0~dfsg1-2
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-Azhy0x/193-qupzilla-plugin-kwallet_2.2.2~dfsg1-1_amd64.deb


cheers,

Andreas


libqupzilla1=2.2.0~dfsg1-2_qupzilla-plugin-gnome-keyring=2.2.2~dfsg1-1.log.gz
Description: application/gzip

Bug#884583: marked as done (qutebrowser: Missing install dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 18 Dec 2017 00:06:32 +
with message-id 
and subject line Bug#884583: fixed in qutebrowser 1.0.4-3
has caused the Debian Bug report #884583,
regarding qutebrowser: Missing install dependencies
to be marked as done.

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

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


-- 
884583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qutebrowser
Version: 1.0.4-2
Severity: normal

Dear Maintainer,

in the light of the latest Mozilla stupidities, I gave your package
a try. It seems however several install dependencies are missing:

| $ qutebrowser
| Traceback (most recent call last):
|   File "/usr/bin/qutebrowser", line 6, in 
| from pkg_resources import load_entry_point
| ModuleNotFoundError: No module named 'pkg_resources'

-> python3-setuptools is needed.

Then a pop-up:

| Error initializing SQL: Failed to add database. Are sqlite and Qt sqlite
| support installed?

-> fixed by installing libqt5sql5-sqlite.

There might be more, can you please run qutebrowser from a minimal
installation to check?

Aside: Seems a stretch backport isn't that difficult, perhaps only an
additional trivial pypeg2 backport is needed.

Christoph


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Source: qutebrowser
Source-Version: 1.0.4-3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 18 Dec 2017 00:21:09 +0100
Source: qutebrowser
Binary: qutebrowser
Architecture: source all
Version: 1.0.4-3
Distribution: unstable
Urgency: high
Maintainer: Fritz Reichwald 
Changed-By: Axel Beckert 
Description:
 qutebrowser - Keyboard-driven, vim-like browser based on PyQt5
Closes: 884583
Changes:
 qutebrowser (1.0.4-3) unstable; urgency=high
 .
   * Add missing runtime dependencies python3-pkg-resources and
 libqt5sql5-sqlite. Thanks Christoph Biedl! (Closes: #884583)
   * Apply "wrap-and-sort -a".
   * Make versioned dependencies more readable by inserting a blank between
 relation and version number.
Checksums-Sha1:
 625d70aceccc6fdd85c6bd93d742a795ac90fc19 2041 qutebrowser_1.0.4-3.dsc
 68afa63e59149c46eeaf28b7c057ec026e7e7602 13604 
qutebrowser_1.0.4-3.debian.tar.xz
 152bfba03e286f5af91979a785b240db116cd9a6 1545672 qutebrowser_1.0.4-3_all.deb
 12994f780a79d23d4c44fd206e95ee6798934461 6645 
qutebrowser_1.0.4-3_amd64.buildinfo
Checksums-Sha256:
 fccf43b08fc2aef7f6d96529213f725ef78c374ea9271f709c0c8176f21cf59d 2041 
qutebrowser_1.0.4-3.dsc
 2d64955147bc0fb532ad0bd1f5a9bfd9bb76bc78c9c0de65320e127f97beabb5 13604 
qutebrowser_1.0.4-3.debian.tar.xz
 84b9626b72174d35cea15bade9fff12ed6f5a5f8e46f66dab0f2333dde2c2d17 1545672 
qutebrowser_1.0.4-3_all.deb
 5b097282e7ec73367b18f3f700d4c45aeaebae726701ca11c9f38a3eaaf288ad 6645 
qutebrowser_1.0.4-3_amd64.buildinfo
Files:
 45a2c143272cfd32a5383250cd910aa1 2041 web optional qutebrowser_1.0.4-3.dsc
 ac32d797b848f0ea8a830e704a496c7d 13604 web optional 
qutebrowser_1.0.4-3.debian.tar.xz
 4330addf36ac35bda5cf0152ec167de2 1545672 web optional 
qutebrowser_1.0.4-3_all.deb
 60859579ca695f304687f7684ea9c51f 6645 web optional 
qutebrowser_1.0.4-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERoyJeTtCmBnp12Ema+Zjx1o1yXUFAlo2/EoACgkQa+Zjx1o1
yXUOsA//Z/hbaqRdqQd4QpSWk3jBDL267nqezDiRqSTVWPe/F+nnReYk3NDbdm2h
evgryOSCpQUJf7dn+3cQZCfReCODvzyC0PhdLZq1mMxtMMRTszVCDX/YQ9Qwlevq
jEobU5BKSkL70jR2IHg6GQY1T5Os21ZdYO8LXiW2r+7RzYvrlOd2Z53NZauSfVPC
78sU+5Sck5/r9nTvSLm7hF4N+COV8qvM1lFlwIhncxIjmYwZe4raQ/NJ7dF8BMUF
k6RMei5JFJwgbuBfstcwp545NgnK75yWVPfxGpJLI5w3DQmMMP4vVQBiPWyC0uNy
dyXhLi43JOvTMP9vHR8Cx3Fz+sz32QD3zpdFJIE9XHgJ5Wa8CcE8aNuj7dza2N7n
geAuR0sqrtCa65yH9d2s5UuSlXEqcjcdvfKW/FZYDQy8JMiUFWiNzoFdK8lHj+OK
ZY1QeVnfkDrjBv1Y7qAue2J17ApApN/udoVWAXxawZYc+lREZGteGcS0RLXvwxWD
ejd87h11uGQTOTe6idTXeANs/Y5zyCY75aq0fn7nfp1xz2mgLko/9ocqpHDK6ftU
gUSxaT+34K3N1sYzuZJ7qUubMTlNm

Bug#884643: mobyle,mobyle-utils: both ship /usr/share/mobyle/core/Tools/setsid

[Andreas Beckmann]

Package: mobyle,mobyle-utils
Version: 1.5.5+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files:

  Selecting previously unselected package mobyle.
  Preparing to unpack .../96-mobyle_1.5.5+dfsg-4_all.deb ...
  Unpacking mobyle (1.5.5+dfsg-4) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-M0zAuC/96-mobyle_1.5.5+dfsg-4_all.deb (--unpack):
   trying to overwrite '/usr/share/mobyle/core/Tools/setsid', which is also in 
package mobyle-utils 1.5.5+dfsg-4
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-M0zAuC/96-mobyle_1.5.5+dfsg-4_all.deb


cheers,

Andreas

Bug#853492: libgdf: ftbfs with GCC-7

[Yaroslav Halchenko]

Thanks!

On Mon, 18 Dec 2017, Juhani Numminen wrote:

> Control: tags -1 + patch

> This patch removes -Werror to resolve this FTBFS. Removing the deprecated
> exception specifications is another option but I didn't feel like editing
> the public headers of the library.
-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: tagging 884583

[Debian Bug Tracking System]

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

> tags 884583 + pending
Bug #884583 [qutebrowser] qutebrowser: Missing install dependencies
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 884626, bug 884626 is forwarded to schm...@schmorp.de

[Debian Bug Tracking System]

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

> tags 884626 + confirmed upstream
Bug #884626 [src:liblinux-dvb-perl] liblinux-dvb-perl FTBFS with linux-libc-dev 
4.14.2-1
Added tag(s) confirmed and upstream.
> forwarded 884626 schm...@schmorp.de
Bug #884626 [src:liblinux-dvb-perl] liblinux-dvb-perl FTBFS with linux-libc-dev 
4.14.2-1
Set Bug forwarded-to-address to 'schm...@schmorp.de'.
> thanks
Stopping processing here.

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

Bug#884639: debops: Uninstallable due to debops-playbooks removal

[Axel Beckert]

Package: debops
Version: 0.4.3-1
Severity: serious

debops has a hard dependency on debops-playbooks, but debops-playbooks
has been removed from Debian with the claim "it's no more needed"
(https://bugs.debian.org/880102). Sounds for me as if that claim was
wrong.

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

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

Versions of packages debops depends on:
ii  ansible2.4.2.0+dfsg-1
ii  debops-playbooks   0.2.8+git20160329.3286ccd-1
ii  libpython2.7-stdlib [python-argparse]  2.7.14-4
ii  python 2.7.14-4
ii  python-netaddr 0.7.19-1
ii  python-pkg-resources   38.2.4-2

Versions of packages debops recommends:
ii  encfs   1.9.2-2
ii  gnupg   2.2.3-1
pn  python-ldap 
ii  python-passlib  1.7.1-1
pn  uuid-runtime

debops suggests no packages.

-- no debconf information

Processed: Re: libgdf: ftbfs with GCC-7

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #853492 [src:libgdf] libgdf: ftbfs with GCC-7
Added tag(s) patch.

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

Bug#853492: libgdf: ftbfs with GCC-7

[Juhani Numminen]

Control: tags -1 + patch

This patch removes -Werror to resolve this FTBFS. Removing the deprecated
exception specifications is another option but I didn't feel like editing
the public headers of the library.


--
Juhani
Description: Remove -Werror to fix FTBFS with GCC-7
 Modifying build flags avoids having to edit public library headers.
 GCC-7 gives the following error:
 dynamic exception specifications are deprecated in C++11; use 'noexcept' instead [-Werror=deprecated]
Author: Juhani Numminen 
Bug-Debian: https://bugs.debian.org/853492
Last-Update: 2017-12-17

--- a/libgdf/CMakeLists.txt
+++ b/libgdf/CMakeLists.txt
@@ -2,7 +2,7 @@
 project( GDF )
 
 if( UNIX )
-add_definitions( -Wall -Wextra -pedantic -Werror -fPIC )
+add_definitions( -Wall -Wextra -pedantic -fPIC )
 elseif( MINGW )
 add_definitions( -Wall -Wextra -pedantic -Werror )
 elseif( WIN32 )
--- a/test/CMakeLists.txt
+++ b/test/CMakeLists.txt
@@ -2,7 +2,7 @@
 project( gdf_tests )
 
 if( UNIX )
-	add_definitions( -Wall -Wextra -pedantic -Werror -fPIC)
+	add_definitions( -Wall -Wextra -pedantic -fPIC)
 elseif( MINGW )
 	add_definitions( -Wall -Wextra -pedantic -Werror )
 elseif( WIN32 )
--- a/tools/gdf_merger/CMakeLists.txt
+++ b/tools/gdf_merger/CMakeLists.txt
@@ -2,7 +2,7 @@
 project( gdf_merger )
 
 if( UNIX )
-	add_definitions( -Wall -Wextra -pedantic -Werror -fPIC)
+	add_definitions( -Wall -Wextra -pedantic -fPIC)
 elseif( MINGW )
 	add_definitions( -Wall -Wextra -pedantic -Werror )
 elseif( WIN32 )

Processed: Re: Bug#884635: transition: libupnp

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 882377 884252 884243 884245 884246 884247 884248
Bug #884635 [release.debian.org] transition: libupnp
884635 was not blocked by any bugs.
884635 was not blocking any bugs.
Added blocking bug(s) of 884635: 882377, 884246, 884248, 884247, 884252, 
884245, and 884243
> block -1 by 884249 884250 884251
Bug #884635 [release.debian.org] transition: libupnp
884635 was blocked by: 882377 884248 884246 884247 884252 884245 884243
884635 was not blocking any bugs.
Added blocking bug(s) of 884635: 884251, 884249, and 884250

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

Processed: found 884102 in 2.5.2-1, tagging 884102, found 882953 in 3.0.1-1, found 882886 in 2.0.0-1

[Debian Bug Tracking System]

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

> found 884102 2.5.2-1
Bug #884102 [src:yowsup] yowsup FTBFS: TypeError: Error when calling the 
metaclass bases
Marked as found in versions yowsup/2.5.2-1.
> tags 884102 + experimental
Bug #884102 [src:yowsup] yowsup FTBFS: TypeError: Error when calling the 
metaclass bases
Added tag(s) experimental.
> found 882953 3.0.1-1
Bug #882953 [src:php-phpdocumentor-reflection] php-phpdocumentor-reflection 
FTBFS with phpunit 6.4.4-2
Marked as found in versions php-phpdocumentor-reflection/3.0.1-1.
> found 882886 2.0.0-1
Bug #882886 [src:php-hamcrest] php-hamcrest FTBFS: PHP Fatal error:  Class 
'PHPUnit_Framework_TestCase' not found
Marked as found in versions php-hamcrest/2.0.0-1.
> thanks
Stopping processing here.

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

Bug#884241: marked as done (bouncycastle: CVE-2017-13098)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 21:19:23 +
with message-id 
and subject line Bug#884241: fixed in bouncycastle 1.58-1
has caused the Debian Bug report #884241,
regarding bouncycastle: CVE-2017-13098
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.)


-- 
884241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bouncycastle
Version: 1.57-1
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for bouncycastle.

CVE-2017-13098[0]:
| Information leak by distinguish valid and invalid RSA PKCS #1 v1.5
| paddings based on different server responses.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13098
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13098
[1] 
https://github.com/bcgit/bc-java/commit/a00b684465b38d722ca9a3543b8af8568e6bad5c
[2] https://downloads.bouncycastle.org/betas/
[3] https://www.kb.cert.org/vuls/id/144389

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bouncycastle
Source-Version: 1.58-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated bouncycastle 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, 17 Dec 2017 20:32:38 +0100
Source: bouncycastle
Binary: libbcprov-java libbcprov-java-doc libbcmail-java libbcmail-java-doc 
libbcpkix-java libbcpkix-java-doc libbcpg-java libbcpg-java-doc
Architecture: source
Version: 1.58-1
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libbcmail-java - Bouncy Castle generators/processors for S/MIME and CMS
 libbcmail-java-doc - Bouncy Castle generators/processors for S/MIME and CMS 
(Documenta
 libbcpg-java - Bouncy Castle generators/processors for OpenPGP
 libbcpg-java-doc - Bouncy Castle generators/processors for OpenPGP 
(Documentation)
 libbcpkix-java - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS, OCSP, 
CMP,
 libbcpkix-java-doc - Bouncy Castle Java API for PKIX, CMS, EAC, TSP, PKCS... 
(Document
 libbcprov-java - Bouncy Castle Java Cryptographic Service Provider
 libbcprov-java-doc - Bouncy Castle Java Cryptographic Service Provider 
(Documentation)
Closes: 884241
Changes:
 bouncycastle (1.58-1) unstable; urgency=high
 .
   * Team upload.
   * New upstream version 1.58.
   * Declare compliance with Debian Policy 4.1.2.
   * Apply CVE-2017-13098.patch and fix CVE-2017-13098.
 Thanks to Salvatore Bonaccorso for the report. (Closes: #884241)
Checksums-Sha1:
 88c9c589553a24ccfd711276959d90666a6639c7 2689 bouncycastle_1.58-1.dsc
 20b5f05d8d7f331d77a2d2a70996f2b7ca499821 12145176 bouncycastle_1.58.orig.tar.xz
 acdc54e688b62a67564c44f0c26ff3116fa362b0 10440 
bouncycastle_1.58-1.debian.tar.xz
 05d5154d90914683976ec032f811c33ef075ee89 13774 
bouncycastle_1.58-1_amd64.buildinfo
Checksums-Sha256:
 1cabe2850e5cd0717c1c9ac2051421ec2fa2b6718ad993bdb345c7b9152d9758 2689 
bouncycastle_1.58-1.dsc
 9df97df679ea63cde67c20126bc08c51e90f310da335e9cea1df8fca88b36f79 12145176 
bouncycastle_1.58.orig.tar.xz
 99ecb6f1e88d00a1855371fe04233a706930f4a296c28732e4756da38f020b57 10440 
bouncycastle_1.58-1.debian.tar.xz
 5c86eed4b61ac84b5f8e37013972c22e147dd15fd369679a940d033e66f0cd1a 13774 
bouncycastle_1.58-1_amd64.buildinfo
Files:
 1041326bcc7cf76363bf7ac7cfa3d7af 2689 java optional bouncycastle_1.58-1.dsc
 a368811cb38c8a592861f2171b72 12145176 java optional 
bouncycastle_1.58.orig.tar.xz
 c3cedde5b29e38e45247471a0e66ee9f 10440 java optional 
bouncycastle_1.58-1.debian.tar.xz
 405549d011f5770584fc2d5e73e5d9be 13774 java optional 
bouncycastle_1.58-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFA

Bug#858398: curl: Please migrate to openssl1.1 in Buster

[Adrian Bunk]

On Fri, Dec 08, 2017 at 05:44:55PM +0100, Ondřej Surý wrote:
> Hi,
> 
> just innocent bystander here with an observation:
> 
> These two options:
> 
> a)
> > I do agree it's the correct solution though, and it would be a good 
> > opportunity
> > to finally sync SONAME with upstream
> 
> b)
> > Because of 1 I think we should change the package name (and SONAME) for
> > libcurl3.  I don't think 2 is appropriate.
> 
> are mutually exclusive, so even if we rename the share library packages
> to libcurl4*, they would have to conflict with libcurl3* because they
> would contain same files.
> 
> And the SONAME is already libcurl.so.4 (at least on stretch):
> 
> $ objdump -p /usr/lib/x86_64-linux-gnu/libcurl* | grep SONAME
>   SONAME   libcurl-gnutls.so.4
>   SONAME   libcurl-gnutls.so.4
>   SONAME   libcurl-gnutls.so.4
>   SONAME   libcurl.so.4
>   SONAME   libcurl.so.4
>   SONAME   libcurl.so.4
> 
> So in this case, unfortunately, bumping the SONAME is actually something
> different than changing package name to match to SONAME of the library. 
>...

Similar to all the v5 postfixed packages in Debian for C++ ABI changes 
in GCC 5, what matter here is actually not the SONAME but the package
name and that the new package conflicts with the old package.

This is sufficient to fix the issue for all packages using curl.

And different from breaks on specific packages, it will also force an
upgrade of packages from backports.

Non-packaged software is a different topic, but the whole OpenSSL 
situation in stretch is already a mess for that.

This whole transition looks pretty straightforward to me,
please let me know if there is anything where I could help.

> Ondrej

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#884636: aodh: build-depends on obsolete package python-gnocchi

[Andreas Beckmann]

Source: aodh
Version: 5.0.0-5
Severity: serious
Justification: fails to build from source

python-gnocchi is no longer built by src:gnocchi - maybe you can use
python3-gnocchi instead?


Andreas

Bug#884358: marked as done (gajim: broken dependencies, gajim no longer starts)

[W. Martin Borgert]

Hi Antonio, it seems upstream has fixed the bug you found and
also some other issues related to the database. Could you
please try alpha2? Should be in unstable now or very soon.
Thanks in advance!

Bug#875815: marked as done (mess-desktop-entries depends on cruft package.)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 20:59:47 +
with message-id 
and subject line Bug#875815: fixed in mess-desktop-entries 0.2-3
has caused the Debian Bug report #875815,
regarding mess-desktop-entries depends on cruft 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.)


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

Package: mess-desktop-entries
Severity: serious
Tags: buster sid

Mess-desktop-entries depends on mess. In wheezy and jessie mess was a real 
package, in stretch it was a transitional package to mame, in buster it has 
been removed.

If this package is usable with mame please fix your dependencies. If not please 
either make your package usable with mame or convert this bug to a removal 
request.
--- End Message ---
--- Begin Message ---
Source: mess-desktop-entries
Source-Version: 0.2-3

We believe that the bug you reported is fixed in the latest version of
mess-desktop-entries, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated mess-desktop-entries 
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, 17 Dec 2017 15:30:42 -0500
Source: mess-desktop-entries
Binary: mess-desktop-entries
Architecture: source
Version: 0.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 mess-desktop-entries - Desktop entries for MESS ROMs
Closes: 869390 875815
Launchpad-Bugs-Fixed: 1730579
Changes:
 mess-desktop-entries (0.2-3) unstable; urgency=medium
 .
   * Depend on mame instead of mess and set .desktop files accordingly
 (Closes: #869390, #875815) (LP: #1730579)
   * Add lintian override for desktop-command-not-in-package
   * Switch from cdbs to dh
   * Bump debhelper compat to 10
   * Disable autoreconf since it breaks the build and isn't needed right now
   * Update Vcs fields for conversion to git
   * Add debian/gbp.conf
   * Update maintainer
   * Bump Standards-Version to 4.1.2
Checksums-Sha1:
 437db6171b56db66d40e504e2d377add9b5a482d 2064 mess-desktop-entries_0.2-3.dsc
 5a3035fc83d75d914caeaea5e6bd13ba51d62fc4 2382 
mess-desktop-entries_0.2-3.debian.tar.bz2
 adef1ab34a95c8546a55fbabec3e9107040ac7f6 8339 
mess-desktop-entries_0.2-3_source.buildinfo
Checksums-Sha256:
 20d225a8627fc034088d728b7339a244bc72816761a9a7fb9fda02758c3424ef 2064 
mess-desktop-entries_0.2-3.dsc
 149bf2fafe0c57f2ea4e2b178abb6db21845772ade85bc0d11c064653162bc6e 2382 
mess-desktop-entries_0.2-3.debian.tar.bz2
 d6598201dcdb5cb1565f2bbde722e6f4bfebd1900c81feb1282e78a2575be547 8339 
mess-desktop-entries_0.2-3_source.buildinfo
Files:
 23b43b5a7f7b03c3dc0a51af3b62bce1 2064 contrib/gnome optional 
mess-desktop-entries_0.2-3.dsc
 dabed16f820801cb5d8ae60c96af7938 2382 contrib/gnome optional 
mess-desktop-entries_0.2-3.debian.tar.bz2
 69c582b96aa91d00c2347503c0ad719e 8339 contrib/gnome optional 
mess-desktop-entries_0.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJaNtRCAAoJEOZsd1rr/mx9huUQAM3tdk01dpe1jYvUyMfuYYtE
RFDj36lzvJOX9AIauect5WB1MjPkouljpsurr6HkuEJ/WG4UhRBiobC3QXUbQHtL
WFmW+QbJ8qxFBoHz2JwfEzfHckrsY4zOHCOp0J2s2f1brdH7OR9YNhLPyqb/odNu
IbO5Bt9vdzuwaA9lj9d79l8orjNGiit/rkafMJPl2IRGbVcYixch1tFWkS6Yv7Zj
KFNuW6CvUWNexfnbChzzzrun+GJIRtLlsIML/69Bds7v/xhzf9BOloVkRQC7I8/t
/83vASAHXkHhN06dGKuxhzzwC1GHH+SPdX7TppPjV3dkMiEKyrLD827iKoSkREpK
8fHbTA0pQLIcAps6qTEYXytOEiV3gAg5phGdi9UPlXdagYqRFR02YRQqeY4FjpPx
dKSNDhUMbS76SnSz2XiUCwe2Jj7CZWKMNqJQXlwvLXh9jMvrUHNgQaQoAIb0KKcy
OhBIL+o6RiOYcUvKqrKDv7IQuzMCQAoxEY+V+QiJBtkkko4bUGlAK5CSs4EzxG4R
5xYQqk+Ju8lfLMNyi3OfHUBOQog4TRmzGQ03gkwPRM5/8wAj4rpoZpdWdb4bLD7x
erk6tTYdPLcQHigD500I3zZMCIqlXC+hQuWU2yIWBlxBk+TQv5m21qF7QkDz49dS
5XgOHIL8AMI+c3/vXRvj
=9ACt
-END PGP SIGNATURE End Message ---

Bug#881064: drf-fsm-transitions: B-D on obsolete transitional package python3-appconf

[Andreas Beckmann]

Followup-For: Bug #881064

The same holds for python-appconf -> python-django-appconf


Andreas

Bug#884241: Pending fixes for bugs in the bouncycastle package

[pkg-java-maintainers]

tag 884241 + pending
thanks

Some bugs in the bouncycastle package are closed in revision
e21813f6dff60bdf67e6379e732dca8683ad2580 in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/bouncycastle.git/commit/?id=e21813f

Commit message:

Apply CVE-2017-13098.patch and fix CVE-2017-13098.

Closes: #884241
Thanks: Salvatore Bonaccorso for the report.

Processed: Pending fixes for bugs in the bouncycastle package

[Debian Bug Tracking System]

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

> tag 884241 + pending
Bug #884241 [src:bouncycastle] bouncycastle: CVE-2017-13098
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> affects 884628 + appstream appstream-generator vibe.d
Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment
Added indication that 884628 affects appstream, appstream-generator, and vibe.d
> reassign 884627 meson 0.44.0-1
Bug #884627 [src:vibe.d] vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must 
not contain a path segment
Bug reassigned from package 'src:vibe.d' to 'meson'.
No longer marked as found in versions vibe.d/0.8.1-2.
Ignoring request to alter fixed versions of bug #884627 to the same values 
previously set
Bug #884627 [meson] vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not 
contain a path segment
Marked as found in versions meson/0.44.0-1.
> reassign 884629 meson 0.44.0-1
Bug #884629 [src:appstream] appstream FTBFS with meson 0.44.0-1
Bug reassigned from package 'src:appstream' to 'meson'.
No longer marked as found in versions appstream/0.11.7-1.
Ignoring request to alter fixed versions of bug #884629 to the same values 
previously set
Bug #884629 [meson] appstream FTBFS with meson 0.44.0-1
Marked as found in versions meson/0.44.0-1.
> forcemerge 884628 884627 884629
Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment
Bug #884627 [meson] vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not 
contain a path segment
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/2719'.
Added indication that 884627 affects appstream,vibe.d,appstream-generator
Bug #884629 [meson] appstream FTBFS with meson 0.44.0-1
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/2719'.
Added indication that 884629 affects appstream,vibe.d,appstream-generator
Merged 884627 884628 884629
>
End of message, stopping processing here.

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

Bug#884628: appstream-generatorFTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment

[Matthias Klumpp]

2017-12-17 21:14 GMT+01:00 Adrian Bunk :
> Source: appstream-generator
> Version: 0.6.8-2
> Severity: serious
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/appstream-generator.html

This is a regression in Meson, see the following issue reports:
https://github.com/mesonbuild/meson/issues/2719
https://github.com/mesonbuild/meson/issues/2794

Issue reassigned accordingly.

Processed: Re: Bug#884628: appstream-generatorFTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment

[Debian Bug Tracking System]

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

> reassign 884628 meson 0.44.0-1
Bug #884628 [src:appstream-generator] appstream-generator FTBFS with meson 
0.44.0-1: Subproject_dir must not contain a path segment
Bug reassigned from package 'src:appstream-generator' to 'meson'.
No longer marked as found in versions appstream-generator/0.6.8-2.
Ignoring request to alter fixed versions of bug #884628 to the same values 
previously set
Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment
Marked as found in versions meson/0.44.0-1.
> forwarded 884628 https://github.com/mesonbuild/meson/issues/2719
Bug #884628 [meson] appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/2719'.
>
End of message, stopping processing here.

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

Bug#884629: appstream FTBFS with meson 0.44.0-1

[Adrian Bunk]

Source: appstream
Version: 0.11.7-1
Severity: serious

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

...
FAILED: data/org.freedesktop.appstream.cli.metainfo.xml 

Processed: Fix the bug title

[Debian Bug Tracking System]

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

> retitle 884628 appstream-generator FTBFS with meson 0.44.0-1: Subproject_dir 
> must not contain a path segment
Bug #884628 [src:appstream-generator] appstream-generatorFTBFS with meson 
0.44.0-1: Subproject_dir must not contain a path segment
Changed Bug title to 'appstream-generator FTBFS with meson 0.44.0-1: 
Subproject_dir must not contain a path segment' from 'appstream-generatorFTBFS 
with meson 0.44.0-1: Subproject_dir must not contain a path segment'.
> thanks
Stopping processing here.

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

Bug#884628: appstream-generatorFTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment

[Adrian Bunk]

Source: appstream-generator
Version: 0.6.8-2
Severity: serious

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

...
The Meson build system
Version: 0.44.0
Source dir: /build/1st/appstream-generator-0.6.8
Build dir: /build/1st/appstream-generator-0.6.8/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson.build, line 1, column 0:
Subproject_dir must not contain a path segment.

Bug#884627: vibe.d FTBFS with meson 0.44.0-1: Subproject_dir must not contain a path segment

[Adrian Bunk]

Source: vibe.d
Version: 0.8.1-2
Severity: serious

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

...
Source dir: /build/1st/vibe.d-0.8.1
Build dir: /build/1st/vibe.d-0.8.1/obj-x86_64-linux-gnu
Build type: native build

Meson encountered an error in file meson.build, line 1, column 0:
Subproject_dir must not contain a path segment.

Bug#884626: liblinux-dvb-perl FTBFS with linux-libc-dev 4.14.2-1

[Adrian Bunk]

Source: liblinux-dvb-perl
Version: 1.03-1
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/liblinux-dvb-perl.html

...
   dh_auto_build
make -j1
make[1]: Entering directory '/build/1st/liblinux-dvb-perl-1.03'
cp DVB.pm blib/lib/Linux/DVB.pm
Running Mkbootstrap for DVB ()
chmod 644 "DVB.bs"
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- DVB.bs 
blib/arch/auto/Linux/DVB/DVB.bs 644
"/usr/bin/perl" "/usr/share/perl/5.26/ExtUtils/xsubpp"  -typemap 
'/usr/share/perl/5.26/ExtUtils/typemap' -typemap 
'/build/1st/liblinux-dvb-perl-1.03/typemap'  DVB.xs > DVB.xsc
mv DVB.xsc DVB.c
x86_64-linux-gnu-gcc -c   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -DVERSION=\"1.03\" 
-DXS_VERSION=\"1.03\" -fPIC "-I/usr/lib/x86_64-linux-gnu/perl/5.26/CORE"   DVB.c
DVB.xs:193:10: error: 'DMX_KERNEL_CLIENT' undeclared here (not in a function)
   CONST (DMX_KERNEL_CLIENT),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:195:10: error: 'DMX_SOURCE_FRONT0' undeclared here (not in a function)
   CONST (DMX_SOURCE_FRONT0),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:196:10: error: 'DMX_SOURCE_FRONT1' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT0'?
   CONST (DMX_SOURCE_FRONT1),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:197:10: error: 'DMX_SOURCE_FRONT2' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT1'?
   CONST (DMX_SOURCE_FRONT2),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:198:10: error: 'DMX_SOURCE_FRONT3' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT2'?
   CONST (DMX_SOURCE_FRONT3),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:200:10: error: 'DMX_SOURCE_DVR0' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_FRONT0'?
   CONST (DMX_SOURCE_DVR0),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:201:10: error: 'DMX_SOURCE_DVR1' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR0'?
   CONST (DMX_SOURCE_DVR1),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:202:10: error: 'DMX_SOURCE_DVR2' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR1'?
   CONST (DMX_SOURCE_DVR2),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
DVB.xs:203:10: error: 'DMX_SOURCE_DVR3' undeclared here (not in a function); 
did you mean 'DMX_SOURCE_DVR2'?
   CONST (DMX_SOURCE_DVR3),
  ^
DVB.xs:10:30: note: in definition of macro 'CONST'
 #define CONST(name) { #name, name }
  ^~~~
Makefile:329: recipe for target 'DVB.o' failed
make[1]: *** [DVB.o] Error 1

Bug#884625: marked as done (cura FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 20:49:32 +0100
with message-id <20171217194932.3iufxxpsk2jd7...@werner.olasd.eu>
and subject line Re: [3dprinter-general] Bug#884625: cura FTBFS: test failures
has caused the Debian Bug report #884625,
regarding cura FTBFS: test failures
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=cura&arch=all&ver=3.0.3-1&stamp=1513493698&raw=0

...
   dh_auto_test -i -O--buildsystem=cmake -O--parallel
cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/obj-x86_64-linux-gnu
Start 1: pytest-main
Start 2: pytest-VersionUpgrade25to26
Start 3: pytest-VersionUpgrade26to27
Start 4: pytest-VersionUpgrade27to30
1/4 Test #4: pytest-VersionUpgrade27to30 ..***Failed0.04 sec
/usr/bin/python3: No module named pytest

2/4 Test #1: pytest-main ..***Failed0.05 sec
/usr/bin/python3: No module named pytest

3/4 Test #3: pytest-VersionUpgrade26to27 ..***Failed0.04 sec
/usr/bin/python3: No module named pytest

4/4 Test #2: pytest-VersionUpgrade25to26 ..***Failed0.05 sec
/usr/bin/python3: No module named pytest


0% tests passed, 4 tests failed out of 4

Total Test time (real) =   0.06 sec

The following tests FAILED:
  1 - pytest-main (Failed)
  2 - pytest-VersionUpgrade25to26 (Failed)
  3 - pytest-VersionUpgrade26to27 (Failed)
  4 - pytest-VersionUpgrade27to30 (Failed)
Errors while running CTest
Makefile:120: recipe for target 'test' failed
make[1]: *** [test] Error 8
--- End Message ---
--- Begin Message ---
Version: 3.0.3-2

Thanks for the report. It seems that it crossed my team upload :-)

Cheers,
-- 
Nicolas Dandrimont

BOFH excuse #383:
Your processor has taken a ride to Heaven's Gate on the UFO behind Hale-Bopp's 
comet.


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

Bug#882891: marked as done (php-db FTBFS with phpunit 6.4.4-2)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 19:34:31 +
with message-id 
and subject line Bug#882891: fixed in php-db 1.9.2-2
has caused the Debian Bug report #882891,
regarding php-db FTBFS with phpunit 6.4.4-2
to be marked as done.

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

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


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

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/php-db-1.9.2'
cd DB-* && \
for i in tests/db_* ; \
do phpunit $i ; \
done
PHPUnit 6.4.4 by Sebastian Bergmann and contributors.

PHP Fatal error:  Uncaught PHPUnit\Runner\Exception: PHPUnit does not support 
this PHPT file in /usr/share/php/PHPUnit/Runner/PhptTestCase.php:395
Stack trace:
#0 /usr/share/php/PHPUnit/Runner/PhptTestCase.php(148): 
PHPUnit\Runner\PhptTestCase->parse()
#1 /usr/share/php/PHPUnit/Framework/TestSuite.php(744): 
PHPUnit\Runner\PhptTestCase->run(Object(PHPUnit\Framework\TestResult))
#2 /usr/share/php/PHPUnit/TextUI/TestRunner.php(537): 
PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#3 /usr/share/php/PHPUnit/TextUI/Command.php(195): 
PHPUnit\TextUI\TestRunner->doRun(Object(PHPUnit\Framework\TestSuite), Array, 
true)
#4 /usr/share/php/PHPUnit/TextUI/Command.php(148): 
PHPUnit\TextUI\Command->run(Array, true)
#5 /usr/bin/phpunit(34): PHPUnit\TextUI\Command::main()
#6 {main}
  thrown in /usr/share/php/PHPUnit/Runner/PhptTestCase.php on line 395
PHPUnit 6.4.4 by Sebastian Bergmann and contributors.

.   1 / 1 (100%)

Time: 140 ms, Memory: 4.00MB

OK (1 test, 1 assertion)
PHPUnit 6.4.4 by Sebastian Bergmann and contributors.

PHP Fatal error:  Uncaught PHPUnit\Runner\Exception: PHPUnit does not support 
this PHPT file in /usr/share/php/PHPUnit/Runner/PhptTestCase.php:395
Stack trace:
#0 /usr/share/php/PHPUnit/Runner/PhptTestCase.php(148): 
PHPUnit\Runner\PhptTestCase->parse()
#1 /usr/share/php/PHPUnit/Framework/TestSuite.php(744): 
PHPUnit\Runner\PhptTestCase->run(Object(PHPUnit\Framework\TestResult))
#2 /usr/share/php/PHPUnit/TextUI/TestRunner.php(537): 
PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#3 /usr/share/php/PHPUnit/TextUI/Command.php(195): 
PHPUnit\TextUI\TestRunner->doRun(Object(PHPUnit\Framework\TestSuite), Array, 
true)
#4 /usr/share/php/PHPUnit/TextUI/Command.php(148): 
PHPUnit\TextUI\Command->run(Array, true)
#5 /usr/bin/phpunit(34): PHPUnit\TextUI\Command::main()
#6 {main}
  thrown in /usr/share/php/PHPUnit/Runner/PhptTestCase.php on line 395
PHPUnit 6.4.4 by Sebastian Bergmann and contributors.

PHP Fatal error:  Uncaught PHPUnit\Runner\Exception: PHPUnit does not support 
this PHPT file in /usr/share/php/PHPUnit/Runner/PhptTestCase.php:395
Stack trace:
#0 /usr/share/php/PHPUnit/Runner/PhptTestCase.php(148): 
PHPUnit\Runner\PhptTestCase->parse()
#1 /usr/share/php/PHPUnit/Framework/TestSuite.php(744): 
PHPUnit\Runner\PhptTestCase->run(Object(PHPUnit\Framework\TestResult))
#2 /usr/share/php/PHPUnit/TextUI/TestRunner.php(537): 
PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#3 /usr/share/php/PHPUnit/TextUI/Command.php(195): 
PHPUnit\TextUI\TestRunner->doRun(Object(PHPUnit\Framework\TestSuite), Array, 
true)
#4 /usr/share/php/PHPUnit/TextUI/Command.php(148): 
PHPUnit\TextUI\Command->run(Array, true)
#5 /usr/bin/phpunit(34): PHPUnit\TextUI\Command::main()
#6 {main}
  thrown in /usr/share/php/PHPUnit/Runner/PhptTestCase.php on line 395
PHPUnit 6.4.4 by Sebastian Bergmann and contributors.

PHP Fatal error:  Uncaught PHPUnit\Runner\Exception: PHPUnit does not support 
this PHPT file in /usr/share/php/PHPUnit/Runner/PhptTestCase.php:395
Stack trace:
#0 /usr/share/php/PHPUnit/Runner/PhptTestCase.php(148): 
PHPUnit\Runner\PhptTestCase->parse()
#1 /usr/share/php/PHPUnit/Framework/TestSuite.php(744): 
PHPUnit\Runner\PhptTestCase->run(Object(PHPUnit\Framework\TestResult))
#2 /usr/share/php/PHPUnit/TextUI/TestRunner.php(537): 
PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#3 /usr/share/php/PHPUnit/TextUI/Command.php(195): 
PHPUnit\TextUI\TestRunner->doRun(Object(PHPUnit\Framework\TestSuite), Array, 
true)
#4 /usr/share/php/PHPUnit/TextUI/Command.php(148): 
PHPUnit\TextUI\Command->run(Array, true)
#5 /usr/bin/phpunit(34): PHPUnit\TextUI\Command::main()
#6 {main}
  thrown in /usr/share/php/PHPUni

Bug#881097: To be removed from wheezy as well

[Ola Lundqvist]

Hi again

After some more reading I think removing it should be ok anyway. I'll
change the wording from "will be removed" to "may be removed" to allow
us the freedom to keep it if nobody takes the action to actually
remove it.

// Ola

On 17 December 2017 at 20:28, Ola Lundqvist  wrote:
> Hi
>
> I agree that it may not be the best to remove it then. I suggest we
> mark it as no-dsa then. Any objections?
>
> // Ola
>
> On 22 November 2017 at 21:00, Emilio Pozuelo Monfort  wrote:
>> On 08/11/17 20:19, Ola Lundqvist wrote:
>>> Hi
>>>
>>> Considering that this package is about to be removed from jessie I
>>> guess it should be removed from wheezy too. How is that done? Should I
>>> contact the FTP maintainers about it, or do we simply ignore the
>>> issue?
>>
>> We don't have point releases, so I'm not sure we can get a package removed at
>> this stage without extra work by the ftp masters. So our options would be:
>>
>> - mark as no-dsa if it's not important enough
>> - mark as unsupported / end-of-life
>> - fix it
>> - get it removed
>>
>> The issue seems only exploitable if it's used by a service that is exposed
>> remotely or to other issues... and has no rdeps in wheezy. OTOH there is at
>> least one sponsor using that package. So removing it may not be the best 
>> course
>> given there is a proposed patch. So I'd go with either no-dsa or fix it,
>> depending on the assessed importance.
>>
>> Cheers,
>> Emilio
>
>
>
> --
>  --- Inguza Technology AB --- MSc in Information Technology 
> /  o...@inguza.comFolkebogatan 26\
> |  o...@debian.org   654 68 KARLSTAD|
> |  http://inguza.com/Mobile: +46 (0)70-332 1551 |
> \  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
>  ---



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#883841: isdnactivecards: Source includes "pcbit/convhexbin.c" listed in Files-Excluded header

[Chris Lamb]

Hi Christoph

> Nope, the file is replaced by a compliant re-implementation, see
> debian/patches/replace-convhexbit.patch

Thanks :)


Regards,

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

Bug#881097: To be removed from wheezy as well

[Ola Lundqvist]

Hi

I agree that it may not be the best to remove it then. I suggest we
mark it as no-dsa then. Any objections?

// Ola

On 22 November 2017 at 21:00, Emilio Pozuelo Monfort  wrote:
> On 08/11/17 20:19, Ola Lundqvist wrote:
>> Hi
>>
>> Considering that this package is about to be removed from jessie I
>> guess it should be removed from wheezy too. How is that done? Should I
>> contact the FTP maintainers about it, or do we simply ignore the
>> issue?
>
> We don't have point releases, so I'm not sure we can get a package removed at
> this stage without extra work by the ftp masters. So our options would be:
>
> - mark as no-dsa if it's not important enough
> - mark as unsupported / end-of-life
> - fix it
> - get it removed
>
> The issue seems only exploitable if it's used by a service that is exposed
> remotely or to other issues... and has no rdeps in wheezy. OTOH there is at
> least one sponsor using that package. So removing it may not be the best 
> course
> given there is a proposed patch. So I'd go with either no-dsa or fix it,
> depending on the assessed importance.
>
> Cheers,
> Emilio



-- 
 --- Inguza Technology AB --- MSc in Information Technology 
/  o...@inguza.comFolkebogatan 26\
|  o...@debian.org   654 68 KARLSTAD|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9  /
 ---

Bug#884625: cura FTBFS: test failures

[Adrian Bunk]

Source: cura
Version: 3.0.3-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=cura&arch=all&ver=3.0.3-1&stamp=1513493698&raw=0

...
   dh_auto_test -i -O--buildsystem=cmake -O--parallel
cd obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j4
Test project /<>/obj-x86_64-linux-gnu
Start 1: pytest-main
Start 2: pytest-VersionUpgrade25to26
Start 3: pytest-VersionUpgrade26to27
Start 4: pytest-VersionUpgrade27to30
1/4 Test #4: pytest-VersionUpgrade27to30 ..***Failed0.04 sec
/usr/bin/python3: No module named pytest

2/4 Test #1: pytest-main ..***Failed0.05 sec
/usr/bin/python3: No module named pytest

3/4 Test #3: pytest-VersionUpgrade26to27 ..***Failed0.04 sec
/usr/bin/python3: No module named pytest

4/4 Test #2: pytest-VersionUpgrade25to26 ..***Failed0.05 sec
/usr/bin/python3: No module named pytest


0% tests passed, 4 tests failed out of 4

Total Test time (real) =   0.06 sec

The following tests FAILED:
  1 - pytest-main (Failed)
  2 - pytest-VersionUpgrade25to26 (Failed)
  3 - pytest-VersionUpgrade26to27 (Failed)
  4 - pytest-VersionUpgrade27to30 (Failed)
Errors while running CTest
Makefile:120: recipe for target 'test' failed
make[1]: *** [test] Error 8

Processed: Re: bouncycastle: CVE-2017-13098

[Debian Bug Tracking System]

Processing control commands:

> owner -1 !
Bug #884241 [src:bouncycastle] bouncycastle: CVE-2017-13098
Owner recorded as Markus Koschany .

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

Bug#883841: marked as done (isdnactivecards: Source includes "pcbit/convhexbin.c" listed in Files-Excluded header)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 20:28:46 +0100
with message-id <1513538...@msgid.manchmal.in-ulm.de>
and subject line Re: Bug#883841: isdnactivecards: Source includes 
"pcbit/convhexbin.c" listed in Files-Excluded header
has caused the Debian Bug report #883841,
regarding isdnactivecards: Source includes "pcbit/convhexbin.c" listed in 
Files-Excluded header
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.)


-- 
883841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isdnactivecards
Version: 1:3.12.2007-11-27-1
Severity: serious
User: la...@debian.org
Usertags: files-excluded

Dear Maintainer,

isdnactivecards lists "pcbit/convhexbin.c" in the Files-Excluded field
in debian/copyright but the source tree contains this file.

This is probably a DFSG violation, or at the upstream tarball was not
repacked as intended. Alternatively, the field is simply out of date.


Regards,

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

> isdnactivecards lists "pcbit/convhexbin.c" in the Files-Excluded field
> in debian/copyright but the source tree contains this file.

Check the (repacked) upstream tar ball. The file is not present there.

> This is probably a DFSG violation, or at the upstream tarball was not
> repacked as intended. Alternatively, the field is simply out of date.

Nope, the file is replaced by a compliant re-implementation, see
debian/patches/replace-convhexbit.patch

Christoph


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

Bug#884241: bouncycastle: CVE-2017-13098

[Markus Koschany]

Control: owner -1 !

I'm working on a fix right now.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Doen't require a newcomer, patch available

[Debian Bug Tracking System]

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

> tags 883987 - newcomer
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)
Removed tag(s) newcomer.
Removed tag(s) newcomer.
Removed tag(s) newcomer.
> tags 883987 patch
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)
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
> 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#828557: Patch for sslsniff, request for review

[Hilko Bengen]

Control: tag -1 patch

Hi,

here's a patch that fixes the OpenSSL-1.1-related FTBFS for sslsniff.

I'd appreciate a review of the patch.

Cheers,
-Hilko
Index: sslsniff/SessionCache.cpp
===
--- sslsniff.orig/SessionCache.cpp
+++ sslsniff/SessionCache.cpp
@@ -47,7 +47,9 @@ void SessionCache::removeSessionId(unsig
 }
 
 int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session) {
-  return setNewSessionId(s, session, session->session_id, session->session_id_length);
+  unsigned int id_length;
+  const unsigned char *id = SSL_SESSION_get_id(session, &id_length);
+  return setNewSessionId(s, session, (unsigned char*)id, id_length);
 }
 
 int SessionCache::setNewSessionId(SSL *s, SSL_SESSION *session, 
@@ -117,8 +119,8 @@ SSL_SESSION * SessionCache::getSessionId
 
 // Trampoline Functions.  Yay C.
 
-SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, unsigned char *id, int idLength, int *ref) {
-  return SessionCache::getInstance()->getSessionId(s, id, idLength, ref);
+SSL_SESSION * SessionCache::getSessionIdTramp(SSL *s, const unsigned char *id, int idLength, int *ref) {
+  return SessionCache::getInstance()->getSessionId(s, (unsigned char*)id, idLength, ref);
 }
 
 int SessionCache::setNewSessionIdTramp(SSL *s, SSL_SESSION *session) {
Index: sslsniff/SessionCache.hpp
===
--- sslsniff.orig/SessionCache.hpp
+++ sslsniff/SessionCache.hpp
@@ -49,7 +49,7 @@ class SessionCache {
 
 public:
   static SessionCache* getInstance();
-  static SSL_SESSION * getSessionIdTramp(SSL *s, unsigned char *id, int idLength, int *ref);
+  static SSL_SESSION * getSessionIdTramp(SSL *s, const unsigned char *id, int idLength, int *ref);
   static int setNewSessionIdTramp(SSL *s, SSL_SESSION *session);
 
   int setNewSessionId(SSL *s, SSL_SESSION *session);
Index: sslsniff/certificate/Certificate.hpp
===
--- sslsniff.orig/certificate/Certificate.hpp
+++ sslsniff/certificate/Certificate.hpp
@@ -92,7 +92,7 @@ private:
   }
 
   void parseCommonName(X509 *cert) {
-std::string distinguishedName(cert->name);
+std::string distinguishedName(X509_NAME_oneline(X509_get_subject_name(cert), NULL, 0));
 std::string::size_type cnIndex = distinguishedName.find("CN=");
 
 if (cnIndex == std::string::npos) throw BadCertificateException();
Index: sslsniff/certificate/TargetedCertificateManager.cpp
===
--- sslsniff.orig/certificate/TargetedCertificateManager.cpp
+++ sslsniff/certificate/TargetedCertificateManager.cpp
@@ -117,6 +117,6 @@ void TargetedCertificateManager::dump()
   std::list::iterator i;
 
   for(i=certificates.begin(); i != certificates.end(); ++i) 
-std::cout << "Certificate: " << (*i)->getCert()->name << std::endl;
+std::cout << "Certificate: " << X509_NAME_oneline(X509_get_subject_name((*i)->getCert()), NULL, 0) << std::endl;
 
 }

Processed: Patch for sslsniff, request for review

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #828557 [src:sslsniff] sslsniff: FTBFS with openssl 1.1.0
Added tag(s) patch.

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

Bug#883927: marked as done (claws-mail fails to build with libical3)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 18:20:15 +
with message-id 
and subject line Bug#883927: fixed in claws-mail 3.16.0-1
has caused the Debian Bug report #883927,
regarding claws-mail fails to build with libical3
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.)


-- 
883927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:claws-mail
Version: 3.15.1-1
Severity: serious
Tags: sid buster

claws-mail fails to build with libical3. As a temporary fix, please build-depend
on libical2-dev, or update the package to build with libical3.

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../.. -I../../../src
-I../../../src/common -I../../../src/common -I../../../src/gtk -pthread
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-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/libpng16 -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/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/freetype2 -I/usr/include/x86_64-linux-gnu -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wno-unused-function
-Wno-pointer-sign -Wall -pthread -I/usr/include/enchant -I/usr/include/glib-2.0
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -c vcal_folder.c  -fPIC -DPIC -o
.libs/vcalendar_la-vcal_folder.o
vcal_manager.c: In function ‘vcal_manager_event_dump’:
vcal_manager.c:398:30: warning: implicit declaration of function
‘icaltime_from_timet’; did you mean ‘icaltime_as_timet’?
[-Wimplicit-function-declaration]
   icalproperty_vanew_dtstamp(icaltime_from_timet(time(NULL), TRUE), (void*)0));
  ^~~
  icaltime_as_timet
vcal_manager.c:398:30: error: incompatible type for argument 1 of
‘icalproperty_vanew_dtstamp’
vcalendar.c: In function ‘create_meeting_from_message_cb_ui’:
In file included from vcal_manager.c:35:0:
/usr/include/libical/ical.h:3306:35: note: expected ‘struct icaltimetype’ but
argument is of type ‘int’
 LIBICAL_ICAL_EXPORT icalproperty *icalproperty_vanew_dtstamp(struct
icaltimetype v, ...);
   ^~
vcalendar.c:160:54: warning: implicit declaration of function
‘icaltime_from_timet’; did you mean ‘icaltime_as_timet’?
[-Wimplicit-function-declaration]
gchar *dtstart = g_strdup(icaltime_as_ical_string(icaltime_from_timet(t,
FALSE)));
  ^~~
  icaltime_as_timet
vcalendar.c:160:54: error: incompatible type for argument 1 of
‘icaltime_as_ical_string’
In file included from vcalendar.c:30:0:
/usr/include/libical/ical.h:171:33: note: expected ‘const struct icaltimetype’
but argument is of type ‘int’
 LIBICAL_ICAL_EXPORT const char *icaltime_as_ical_string(const struct
icaltimetype tt);
 ^~~
vcal_manager.c:426:30: error: incompatible type for argument 1 of
‘icalproperty_vanew_created’
   icalproperty_vanew_created(icaltime_from_timet(time(NULL), TRUE), (void*)0));
  ^~~
vcalendar.c:161:52: error: incompatible type for argument 1 of
‘icaltime_as_ical_string’
gchar *dtend = g_strdup(icaltime_as_ical_string(icaltime_from_timet(t2,
FALSE)));
^~~
In file included from vcalendar.c:30:0:
/usr/include/libical/ical.h:171:33: note: expected ‘const struct icaltimetype’
but argument is of type ‘int’
 LIBICAL_ICAL_EXPORT const char *icaltime_as_ical_string(const struct
icaltimetype tt);
 ^~~
In file included from vcal_manager.c:35:0:
/usr/include/libical/ical.h:3246:35: note: expected ‘struct icaltimetype’ but
argument is of type ‘int’
 LIBICAL_ICAL_EXPORT icalproperty *icalproperty_vanew_created(struct
icaltimetype v, ...);
   ^~
vcal_manager.c:428:35: error: incompatible type for argument 1 of
‘icalproperty_vanew_lastmodified’
   icalproperty_vanew_lastmodified(icaltime_from_timet(time(NULL), TRUE),
(void*)0));
   ^~~
In 

Bug#883958: marked as done (claws-mail fails to build with libical3)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 18:20:15 +
with message-id 
and subject line Bug#883927: fixed in claws-mail 3.16.0-1
has caused the Debian Bug report #883927,
regarding claws-mail fails to build with libical3
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.)


-- 
883927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:claws-mail
Version: 3.15-1
Severity: serious
Tags: patch sid buster

claws-mail fails to build with libical3

patch at
http://launchpadlibrarian.net/348656446/claws-mail_3.15.1-1build1_3.15.1-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: claws-mail
Source-Version: 3.16.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Dec 2017 18:37:38 +0100
Source: claws-mail
Binary: claws-mail libclaws-mail-dev claws-mail-plugins claws-mail-spamassassin 
claws-mail-pgpmime claws-mail-pgpinline claws-mail-smime-plugin 
claws-mail-bogofilter claws-mail-i18n claws-mail-doc claws-mail-tools 
claws-mail-extra-plugins claws-mail-acpi-notifier claws-mail-address-keeper 
claws-mail-archiver-plugin claws-mail-attach-remover claws-mail-attach-warner 
claws-mail-bsfilter-plugin claws-mail-clamd-plugin claws-mail-feeds-reader 
claws-mail-fetchinfo-plugin claws-mail-gdata-plugin claws-mail-libravatar 
claws-mail-newmail-plugin claws-mail-mailmbox-plugin claws-mail-managesieve 
claws-mail-multi-notifier claws-mail-tnef-parser claws-mail-perl-filter 
claws-mail-pdf-viewer claws-mail-python-plugin claws-mail-spam-report 
claws-mail-vcalendar-plugin
Architecture: source amd64 all
Version: 3.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Description:
 claws-mail - Fast, lightweight and user-friendly GTK+2 based email client
 claws-mail-acpi-notifier - Laptop's Mail LED control for Claws Mail
 claws-mail-address-keeper - Address keeper plugin for Claws Mail
 claws-mail-archiver-plugin - Archiver plugin for Claws Mail
 claws-mail-attach-remover - Mail attachment remover for Claws Mail
 claws-mail-attach-warner - Missing attachment warnings for Claws Mail
 claws-mail-bogofilter - Bogofilter plugin for Claws Mail
 claws-mail-bsfilter-plugin - Spam filtering using bsfilter for Claws Mail
 claws-mail-clamd-plugin - ClamAV socket-based plugin for Claws Mail
 claws-mail-doc - User documentation for Claws Mail mailer
 claws-mail-extra-plugins - Extra plugins collection for Claws Mail
 claws-mail-feeds-reader - Feeds (RSS/Atom) reader plugin for Claws Mail
 claws-mail-fetchinfo-plugin - Add X-FETCH headers plugin for Claws Mail
 claws-mail-gdata-plugin - Access to GData (Google services) for Claws Mail
 claws-mail-i18n - Locale data for Claws Mail (i18n support)
 claws-mail-libravatar - Display sender avatar from a libravatar server
 claws-mail-mailmbox-plugin - mbox format mailboxes handler for Claws Mail
 claws-mail-managesieve - manage Sieve filters with Claws Mail
 claws-mail-multi-notifier - Various new mail notifiers for Claws Mail
 claws-mail-newmail-plugin - New mail logger plugin for Claws Mail
 claws-mail-pdf-viewer - PDF and PostScript attachment viewer for Claws Mail
 claws-mail-perl-filter - Message filtering plugin using perl for Claws Mail
 claws-mail-pgpinline - PGP/inline plugin for Claws Mail
 claws-mail-pgpmime - PGP/MIME plugin for Claws Mail
 claws-mail-plugins - Installs plugins for the Claws Mail mailer
 claws-mail-python-plugin - Python plugin and console for Claws Mail
 claws-mail-smime-plugin - S/MIME signature/encryption handling for Claws Mail
 claws-mail-spam-report - Spam reporting plugin for Claws Mail
 claws-mail-spamassassin - SpamAssassin plugin for Claws Mail
 claws-mail-tnef-parser - TNEF attachment handler for Claws Mail
 claws-mail-tools - Helper and utility scripts for Claws Mail mailer
 claws-mail-v

Bug#884616: exception "ValueError: The truth value..." on import

[Ian Jackson]

Package: python-visual
Version: 1:5.12-1.6+b6
Severity: grave
Justification: renders package unusable

Reproduction transcript:

(build)ian@zealot:~$ python2
Python 2.7.14+ (default, Dec  5 2017, 15:17:02) 
[GCC 7.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import visual
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/visual/__init__.py", line 66, in 

from visual.ui import display
  File "/usr/lib/python2.7/dist-packages/visual/ui.py", line 3, in 
import materials
  File "/usr/lib/python2.7/dist-packages/visual/materials.py", line 152, in 

tx_turb3 = raw_texture( data=reshape(data,(64,64,64,3)), interpolate=True, 
mipmap=False )
  File "/usr/lib/python2.7/dist-packages/visual/materials.py", line 70, in 
__init__
self.__setattr__(key, value)
ValueError: The truth value of an array with more than one element is 
ambiguous. Use a.any() or a.all()
>>>

I had a look at the source but I'm afraid I'm mystified.

Ian.

-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Bug#884617: modemmanager: Maintainer email bounces

[Tobias Frost]

Package: modemmanager
Version: 1.6.8-2
Severity: serious
Justification: Policy 3.3

The maintainer email Mathieu Trudel-Lapierre  bounces.

This is a violation of a Policy "must" criteria, hence RC critical.

-- 
tobi


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

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

Versions of packages modemmanager depends on:
ii  libc6  2.25-3
ii  libglib2.0-0   2.54.2-1
ii  libgudev-1.0-0 232-1
ii  libmbim-glib4  1.14.2-2.1
ii  libmbim-proxy  1.14.2-2.1
ii  libmm-glib01.6.8-2
ii  libpolkit-gobject-1-0  0.105-18
ii  libqmi-glib5   1.18.0-3
ii  libqmi-proxy   1.18.0-3

Versions of packages modemmanager recommends:
ii  usb-modeswitch  2.5.1+repack0-1

modemmanager suggests no packages.

-- no debconf information

Processed: Patch

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch -fixed-upstream
Bug #847611 [src:ckermit] ckermit: Please migrate to openssl1.1 in buster
Added tag(s) patch.
Bug #847611 [src:ckermit] ckermit: Please migrate to openssl1.1 in buster
Removed tag(s) fixed-upstream.

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

Bug#847611: Patch

[Hilko Bengen]

Control: tag -1 patch -fixed-upstream

I don't see where the direct struct access issues have been fixed
upstream, the source code snapshot available from
http://www.kermitproject.org/ckdaily.html still has lots of those.

I have prepared a patch that fixes building with OpenSSL 1.1 and would
appreciate a review.

Cheers,
-Hilko
Index: ckermit-302/ck_ssl.c
===
--- ckermit-302.orig/ck_ssl.c
+++ ckermit-302/ck_ssl.c
@@ -301,7 +301,7 @@ X509_STORE_CTX *ctx;
 break;
 default:
 printf("Error %d while verifying certificate.\r\n",
-   ctx->error);
+   X509_STORE_CTX_get_error(ctx));
 break;
 }
 }
@@ -933,13 +933,15 @@ static DH *
 get_dh512()
 {
 DH *dh=NULL;
+BIGNUM *p, *g;
 
 if ((dh=DH_new()) == NULL)
 return(NULL);
-dh->p=BN_bin2bn(dh512_p,sizeof(dh512_p),NULL);
-dh->g=BN_bin2bn(dh512_g,sizeof(dh512_g),NULL);
-if ((dh->p == NULL) || (dh->g == NULL))
+p=BN_bin2bn(dh512_p,sizeof(dh512_p),NULL);
+g=BN_bin2bn(dh512_g,sizeof(dh512_g),NULL);
+if ((p == NULL) || (g == NULL))
 return(NULL);
+DH_set0_pqg(dh, p, NULL, g);
 return(dh);
 }
 
@@ -947,13 +949,15 @@ static DH *
 get_dh768()
 {
 DH *dh=NULL;
+BIGNUM *p, *g;
 
 if ((dh=DH_new()) == NULL)
 return(NULL);
-dh->p=BN_bin2bn(dh768_p,sizeof(dh768_p),NULL);
-dh->g=BN_bin2bn(dh768_g,sizeof(dh768_g),NULL);
-if ((dh->p == NULL) || (dh->g == NULL))
+p=BN_bin2bn(dh768_p,sizeof(dh768_p),NULL);
+g=BN_bin2bn(dh768_g,sizeof(dh768_g),NULL);
+if ((p == NULL) || (g == NULL))
 return(NULL);
+DH_set0_pqg(dh, p, NULL, g);
 return(dh);
 }
 
@@ -961,13 +965,15 @@ static DH *
 get_dh1024()
 {
 DH *dh=NULL;
+BIGNUM *p, *g;
 
 if ((dh=DH_new()) == NULL)
 return(NULL);
-dh->p=BN_bin2bn(dh1024_p,sizeof(dh1024_p),NULL);
-dh->g=BN_bin2bn(dh1024_g,sizeof(dh1024_g),NULL);
-if ((dh->p == NULL) || (dh->g == NULL))
+p=BN_bin2bn(dh1024_p,sizeof(dh1024_p),NULL);
+g=BN_bin2bn(dh1024_g,sizeof(dh1024_g),NULL);
+if ((p == NULL) || (g == NULL))
 return(NULL);
+DH_set0_pqg(dh, p, NULL, g);
 return(dh);
 }
 
@@ -975,13 +981,15 @@ static DH *
 get_dh1536()
 {
 DH *dh=NULL;
+BIGNUM *p, *g;
 
 if ((dh=DH_new()) == NULL)
 return(NULL);
-dh->p=BN_bin2bn(dh1536_p,sizeof(dh1536_p),NULL);
-dh->g=BN_bin2bn(dh1536_g,sizeof(dh1536_g),NULL);
-if ((dh->p == NULL) || (dh->g == NULL))
+p=BN_bin2bn(dh1536_p,sizeof(dh1536_p),NULL);
+g=BN_bin2bn(dh1536_g,sizeof(dh1536_g),NULL);
+if ((p == NULL) || (g == NULL))
 return(NULL);
+DH_set0_pqg(dh, p, NULL, g);
 return(dh);
 }
 
@@ -989,13 +997,15 @@ static DH *
 get_dh2048()
 {
 DH *dh=NULL;
+BIGNUM *p, *g;
 
 if ((dh=DH_new()) == NULL)
 return(NULL);
-dh->p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
-dh->g=BN_bin2bn(dh2048_g,sizeof(dh2048_g),NULL);
-if ((dh->p == NULL) || (dh->g == NULL))
+p=BN_bin2bn(dh2048_p,sizeof(dh2048_p),NULL);
+g=BN_bin2bn(dh2048_g,sizeof(dh2048_g),NULL);
+if ((p == NULL) || (g == NULL))
 return(NULL);
+DH_set0_pqg(dh, p, NULL, g);
 return(dh);
 }
 #endif /* NO_DH */
@@ -1054,10 +1064,11 @@ ssl_display_comp(SSL * ssl)
 if (ssl == NULL)
 return;
 
-if (ssl->expand == NULL || ssl->expand->meth == NULL)
+COMP_METHOD *x = SSL_get_current_expansion(ssl);
+if (x)
 printf("Compression: None\r\n");
 else {
-printf("Compression: %s\r\n",ssl->expand->meth->name);
+printf("Compression: %s\r\n",SSL_COMP_get0_name(x));
 }
 }
 
@@ -1457,13 +1468,15 @@ the build.\r\n\r\n");
 
 #ifdef ZLIB
 cm = COMP_zlib();
-if (cm != NULL && cm->type != NID_undef) {
+if (cm != NULL && SSL_COMP_get_id(cm) != NID_undef) {
 SSL_COMP_add_compression_method(0xe0, cm); /* EAY's ZLIB ID */
 }
 #endif /* ZLIB */
+#if 0 /* COMP_rle has apparently been removed in OpenSSL 1.1 */
 cm = COMP_rle();
 if (cm != NULL && cm->type != NID_undef)
 SSL_COMP_add_compression_method(0xe1, cm); /* EAY's RLE ID */
+#endif
 
 /* Ensure the Random number generator has enough entropy */
 if ( !RAND_status() ) {
@@ -1483,12 +1496,14 @@ the build.\r\n\r\n");
 }
 debug(F110,"ssl_rnd_file",ssl_rnd_file,0);
 
+#ifndef OPENSSL_NO_EGD
 rc1 = RAND_egd(ssl_rnd_file);
 debug(F111,"ssl_once_init","RAND_egd()",rc1);
 if ( rc1 <= 0 ) {
 rc2 = RAND_load_file(ssl_rnd_file, -1);
 debug(F111,"ssl_once_init","RAND_load_file()",rc1);
 }
+#endif 
 
 if ( rc1 <= 0 && !rc2 )
 {
@@ -2583,7 +2598,7 @@ ssl_anonymous_cipher(ssl) SSL * ssl;
 int
 ssl_verify_crl(int ok, X509_STORE_CTX *ctx)
 {
-X509_OBJECT obj;
+X509_OBJECT *obj = X509_OBJECT_new();
 X509_NAME *sub

Bug#881249: marked as done (uncrustify FTBFS on armel/i386/mips64el/s390x: cpp_33057 fails)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 17:08:12 +
with message-id 
and subject line Bug#881249: fixed in uncrustify 0.66.1+dfsg1-1
has caused the Debian Bug report #881249,
regarding uncrustify FTBFS on armel/i386/mips64el/s390x: cpp_33057 fails
to be marked as done.

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

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


-- 
881249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uncrustify
Version: 0.66+dfsg1-1
Severity: serious

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

...
555/798 Test #557: cpp_33057 ***Failed0.10 sec
Files 
"/<>/uncrustify-0.66+dfsg1/tests/results/cpp/33057-bug_1349.cpp" to 
"/<>/uncrustify-0.66+dfsg1/tests/output/cpp/33057-bug_1349.cpp" are 
different.
CMake Error at /<>/uncrustify-0.66+dfsg1/tests/run_test.cmake:54 
(message):
  MISSMATCH: results/cpp/33057-bug_1349.cpp does not match
  output/cpp/33057-bug_1349.cpp
...
The following tests FAILED:
557 - cpp_33057 (Failed)
Errors while running CTest
Makefile:142: recipe for target 'test' failed
make[1]: *** [test] Error 8
--- End Message ---
--- Begin Message ---
Source: uncrustify
Source-Version: 0.66.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated uncrustify package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Dec 2017 18:49:06 +0300
Source: uncrustify
Binary: uncrustify
Architecture: source amd64
Version: 0.66.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Description:
 uncrustify - C, C++, ObjectiveC, C#, D, Java, Pawn and VALA source code beauti
Closes: 881249
Changes:
 uncrustify (0.66.1+dfsg1-1) unstable; urgency=medium
 .
   * Add debian/gbp.conf.
   * New upstream version 0.66.1 Fixed FTBFS on some arches (Closes: #881249)
   * Bump Standards-Version to 4.1.2 (no additional changes needed).
Checksums-Sha1:
 af9ccb3db14297984abba561e016a787a7074382 1632 uncrustify_0.66.1+dfsg1-1.dsc
 c62175c62ea5632ba448489c7074568453c179d3 700912 
uncrustify_0.66.1+dfsg1.orig.tar.xz
 8f5e7c28c6046cbf499882b35b61b94034cdb844 4480 
uncrustify_0.66.1+dfsg1-1.debian.tar.xz
 64bfa2ef774f436e79ea0d62b64f67f6c89967d8 2056300 
uncrustify-dbgsym_0.66.1+dfsg1-1_amd64.deb
 642d5e85fec5b70306b682bccf4540a20eba852c 6524 
uncrustify_0.66.1+dfsg1-1_amd64.buildinfo
 047888353a484c1a7d64ef9fd1d4ffbeff37f5ec 403604 
uncrustify_0.66.1+dfsg1-1_amd64.deb
Checksums-Sha256:
 225931ff5f0398061b8b6f8e9950e71658b067c352e78ea8e7ba36f69fd001d5 1632 
uncrustify_0.66.1+dfsg1-1.dsc
 f2599bee3ab0c529042742125e2d6325cd39ed8e2821c7dcff51405186ce02bc 700912 
uncrustify_0.66.1+dfsg1.orig.tar.xz
 e7e2101198f0250470f0b6d0b5ffe6f8cd02ebc475dfe1fa88dd341de2dacd09 4480 
uncrustify_0.66.1+dfsg1-1.debian.tar.xz
 265627577b478fbcfc437f0be87ca57ac7bca2a50070cf6010a351db34774158 2056300 
uncrustify-dbgsym_0.66.1+dfsg1-1_amd64.deb
 a5f0f083fef512fe61260da453108749bd4c65fe54eb492d73b6811bc3544bbb 6524 
uncrustify_0.66.1+dfsg1-1_amd64.buildinfo
 f5fb8863b348b86d665ff0f5ef2ee43f2cfda1ed1ee1c8b4892d2d1fe0a88188 403604 
uncrustify_0.66.1+dfsg1-1_amd64.deb
Files:
 28f9d4f4446aabae890f85636420fe1f 1632 devel optional 
uncrustify_0.66.1+dfsg1-1.dsc
 cf4bfe1dc1eaa9a75047ec2d502d4d52 700912 devel optional 
uncrustify_0.66.1+dfsg1.orig.tar.xz
 74152d416774e70977f575540972 4480 devel optional 
uncrustify_0.66.1+dfsg1-1.debian.tar.xz
 bbe3b5ebb04517e2a9b72f4b36b4c100 2056300 debug optional 
uncrustify-dbgsym_0.66.1+dfsg1-1_amd64.deb
 67922bd71e815b6f09dc4bcf4c832247 6524 devel optional 
uncrustify_0.66.1+dfsg1-1_amd64.buildinfo
 bb17766dcedc4393fc287c3257666899 403604 devel optional 
uncrustify_0.66.1+dfsg1-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQFCBAEBCAAsFiEEBLWdkN98wqvNSbrqyofp6CqsM/EFAlo2ncUOHGdxQGRlYmlh
bi5vcmcACgkQyofp6CqsM/E3zAf9GbFyRyGHQN1k/vvuaF8IU/J3urZSlFknUduc
sWW6tHQak9pTjaUPM1Eq1XRMuszblZ58g1T00KwmP9Shh52l

Bug#870599: python-jinja2 2.9 breaks ansible in stable

[Lee Garrett]

reassign 870599 python-jinja2
kthxbye

Hi,

can you add a Breaks: ansible << 2.3 to python-jinja2 in sid? That will help
with upgrading from stretch to buster. The template module in ansible 2.2.1
(stretch) is broken with jinja2 2.9 and above.

Regards,
Lee

Processed: python-jinja2 2.9 breaks ansible in stable

[Debian Bug Tracking System]

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

> reassign 870599 python-jinja2
Bug #870599 {Done: Harlan Lieberman-Berg } [ansible] 
ansible: Needs pinned Jinja2 dependency due to upstream bug #20494
Bug reassigned from package 'ansible' to 'python-jinja2'.
No longer marked as found in versions ansible/2.2.1.0-2.
No longer marked as fixed in versions ansible/2.3.1.0+dfsg-2.
> kthxbye
Stopping processing here.

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

Bug#884464: marked as done (crash: cannot resolve "init_level4_pgt")

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 16:04:07 +
with message-id 
and subject line Bug#884464: fixed in crash 7.2.0-1
has caused the Debian Bug report #884464,
regarding crash: cannot resolve "init_level4_pgt"
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.)


-- 
884464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884464
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crash
Version: 7.1.7-1
Severity: serious
Tags: patch

The utility is probably working in its current shape for older kernel,
but not for newer:

|$ crash ../build-RT/vmlinux mem2
|
|crash 7.1.7
|Copyright (C) 2002-2016  Red Hat, Inc.
|Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
|Copyright (C) 1999-2006  Hewlett-Packard Co
|Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
|Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
|Copyright (C) 2005, 2011  NEC Corporation
|Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
|Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
|This program is free software, covered by the GNU General Public
|License,
|and you are welcome to change it and/or distribute copies of it under
|certain conditions.  Enter "help copying" to see the conditions.
|This program has absolutely no warranty.  Enter "help warranty" for
|details.
|
|GNU gdb (GDB) 7.6
|Copyright (C) 2013 Free Software Foundation, Inc.
|License GPLv3+: GNU GPL version 3 or later
|
|This is free software: you are free to change and redistribute it.
|There is NO WARRANTY, to the extent permitted by law.  Type "show
|copying"
|and "show warranty" for details.
|This GDB was configured as "x86_64-unknown-linux-gnu"...
|
|
|crash: cannot resolve "init_level4_pgt"

This was a v4.14 kernel. With the patch attached on the other hand, it
works again.
This change is part of 7.2.0. Can please have an update for unstable and
a backport for stable?

Sebastian
>From a16324a2f05c0947a83e26a5de7c756de4603da9 Mon Sep 17 00:00:00 2001
From: Dave Anderson 
Date: Thu, 6 Jul 2017 16:19:41 -0400
Subject: [PATCH] Fix for Linux 4.13-rc0 commit
 7fd8329ba502ef76dd91db561c7aed696b2c7720 "x86/boot/64: Rename init_level4_pgt
 and early_level4_pgt".  Without the patch, the crash session fails during
 initialization with the error message "crash: cannot resolve
 "init_level4_pgt". (ander...@redhat.com)

---
 x86_64.c | 11 ---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/x86_64.c b/x86_64.c
index 1d23d784ad51..44d0c98660c0 100644
--- a/x86_64.c
+++ b/x86_64.c
@@ -1388,12 +1388,17 @@ static void
 x86_64_init_kernel_pgd(void)
 {
 	int i;
-	ulong init_level4_pgt;
+	ulong kernel_pgt = 0;
 
-	init_level4_pgt = symbol_value("init_level4_pgt");
+	if (kernel_symbol_exists("init_level4_pgt"))
+		kernel_pgt = symbol_value("init_level4_pgt");
+	else if (kernel_symbol_exists("init_top_pgt"))
+		kernel_pgt = symbol_value("init_top_pgt");
+	else
+		error(WARNING, "neither \"init_level4_pgt\" or \"init_top_pgt\" exist\n");
 
 	for (i = 0; i < NR_CPUS; i++) 
-		vt->kernel_pgd[i] = init_level4_pgt;
+		vt->kernel_pgd[i] = kernel_pgt;
 
 	FILL_PML4();
 }
-- 
2.15.1

--- End Message ---
--- Begin Message ---
Source: crash
Source-Version: 7.2.0-1

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

Debian distribution maintenance software
pp.
Troy Heber  (supplier of updated crash package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Dec 2017 08:25:06 -0700
Source: crash
Binary: crash
Architecture: source amd64
Version: 7.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Troy Heber 
Changed-By: Troy Heber 
Description:
 crash  - kernel debugging utility, allowing gdb like syntax
Closes: 884464
Changes:
 crash (7.2.0-1) unstable; urgency=medium
 .
   * New upstream (closes: #884464)
 .
   * Fix for the "snap.so" extension module to pass the KASLR relocation offset
 value in the ELF header for x86_64 kernels that are compiled with
 CONFIG_RANDOMIZE_BASE.  Without the patch, it is necess

Processed: Re: Bug#884583: qutebrowser: Missing install dependencies

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #884583 [qutebrowser] qutebrowser: Missing install dependencies
Severity set to 'serious' from 'normal'

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

Bug#880883: Some findings about g_closure_ref()/g_closure_unref()

[Michael Biebl]

Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=791706


Hi Punit,

thanks a lot for your excellent work so far!

On Sat, 2 Dec 2017 20:48:08 + Punit Agrawal 
wrote:
> I have a few ideas on how to improve the code by re-factoring
> INC_ASSIGN/DEC_ASSIGN to use specialised versions of CHANGE_FIELD in
> gobject/gclosure.c. I'll give those a shot and see if they lead to an
> improvement in performance. Happy to discuss any suggestions or try
> patches and report back.
> 
> It might also be worth raising/discussing the findings here with
> upstream. I am not at all familiar with glib and they might be able to
> help explain the code structure and have suggestions for improvement.

I've filed a bug upstream and copied your findings there. If you have a
bugzilla.gnome.org account, please consider subscribing to this bug
report. It's probably most effective, if you directly talk to upstream
about this.

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Some findings about g_closure_ref()/g_closure_unref()

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=791706
Bug #880883 [src:glib2.0] FTBFS on arm64: test suite times out (on arm-arm-04)
Set Bug forwarded-to-address to 
'https://bugzilla.gnome.org/show_bug.cgi?id=791706'.

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

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Aurelien Jarno]

On 2017-12-17 10:10, Andreas Beckmann wrote:
> I did dig further. An easier target for debugging is glxinfo. Which can be 
> further minimized to
> 
> #include 
> #include 
> #include 
> int main()
> {
> pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
> pthread_mutex_lock(&mutex);
> pthread_mutex_unlock(&mutex);
> 
> Display * dpy ;
> dpy = XOpenDisplay ( NULL ) ;
> 
> pthread_mutex_lock(&mutex);
> pthread_mutex_unlock(&mutex);
> 
>int fbAttribSingle[] = {
>   GLX_RENDER_TYPE,   GLX_RGBA_BIT,
>   GLX_RED_SIZE,  1,
>   GLX_GREEN_SIZE,1,
>   GLX_BLUE_SIZE, 1,
>   GLX_DOUBLEBUFFER,  False,
>   None };
> GLXFBConfig * configs ;
> int nConfigs ;
> configs = glXChooseFBConfig ( dpy , 0 , fbAttribSingle , & nConfigs ) 
> ;
> 
> pthread_mutex_lock(&mutex);
> pthread_mutex_unlock(&mutex);
> }
> 
> (link with -lGL -lX11)
> 
> that dies at some point in pthread_mutex_lock after several
> calls succeeded:
> 
> (gdb) bt
> #0  0x7754b1d4 in pthread_mutex_lock (mutex=0x77001180 
> ) at forward.c:192
> #1  0x76dab007 in LockDispatch () at 
> ../../../src/GLdispatch/GLdispatch.c:144
> #2  __glDispatchNewVendorID () at ../../../src/GLdispatch/GLdispatch.c:198
> #3  0x7702c3c2 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #4  0x7702d1ac in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #5  0x77026251 in glXChooseFBConfig () from 
> /usr/lib/x86_64-linux-gnu/libGLX.so.0
> #6  0x4964 in main () at mwe.c:25
> (gdb) info shared
> FromTo  Syms Read   Shared Object Library
> 0x77dd9aa0  0x77df5340  Yes 
> /lib64/ld-linux-x86-64.so.2
> 0x77b745d0  0x77b78c1b  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libGL.so.1
> 0x77812da0  0x7789a434  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libX11.so.6
> 0x77475910  0x7759f403  Yes 
> /lib/x86_64-linux-gnu/libc.so.6
> 0x77252d80  0x7725394e  Yes 
> /lib/x86_64-linux-gnu/libdl.so.2
> 0x77024a20  0x7702ef9d  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libGLX.so.0
> 0x76daabb0  0x76dada37  Yes 
> /usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
> 0x76b4fb40  0x76b619f5  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libxcb.so.1
> 0x76935700  0x7693f49f  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libXext.so.6
> 0x7672f010  0x7672fc8c  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libXau.so.6
> 0x76529340  0x7652ac48  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libXdmcp.so.6
> 0x763153d0  0x763225df  Yes (*) 
> /lib/x86_64-linux-gnu/libbsd.so.0
> 0x7610c0e0  0x7610eecf  Yes 
> /lib/x86_64-linux-gnu/librt.so.1
> 0x75ef2ab0  0x75eff811  Yes 
> /lib/x86_64-linux-gnu/libpthread.so.0
> 0x75c00f00  0x75c76291  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
> 0x759ab810  0x759ad5a3  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.375.82
> 0x73ed7600  0x74fbac77  Yes (*) 
> /usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.375.82
> 0x738d7680  0x739438da  Yes 
> /lib/x86_64-linux-gnu/libm.so.6
> (gdb) disassemble
> Dump of assembler code for function pthread_mutex_lock:
>0x7754b1b0 <+0>: mov0x2a957a(%rip),%eax# 
> 0x777f4730 <__libc_pthread_functions_init>
>0x7754b1b6 <+6>: test   %eax,%eax
>0x7754b1b8 <+8>: jne0x7754b1c0 
>0x7754b1ba <+10>:xor%eax,%eax
>0x7754b1bc <+12>:retq   
>0x7754b1bd <+13>:nopl   (%rax)
>0x7754b1c0 <+16>:mov0x2a94c1(%rip),%rax# 
> 0x777f4688 <__libc_pthread_functions+264>
>0x7754b1c7 <+23>:ror$0x11,%rax
>0x7754b1cb <+27>:xor%fs:0x30,%rax
> => 0x7754b1d4 <+36>:jmpq   *%rax
> 
> After finally understanding that the fs segment is used for TLS storage
> addressing, I actually saw the difference in the linked libraries:
> /usr/lib/x86_64-linux-gnu/libnvidia-tls.so.375.82 vs.
> /usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.375.82

Oh, it's strange this library didn't show up in the ldd tests that
appear earlier in this bug report. I guess it is (indirectly) dlopened.

> From the documentation:
> 
> The nvidia-tls libraries (/usr/lib/libnvidia-tls.so.384.98 and 
> /usr/lib/tls/libnvidia-tls.so.384.98); these files provide thread local 
> storage support for the NVIDIA OpenGL libraries (libGL, libnvidia-glcore, and 
> libglx). Each nvidia-tls library provides support for a particular thread 
> local storage model (such as ELF TLS), and the one appropriate for your 
> system will be loaded at run time.
> 
> and fr

Bug#882059: python-ibus package is missing in testing repository

[Osamu Aoki]

Hi,

Thanks for the reply ;-)

Please don't feel to "sorry".  My comments are not meant to blame you but to
be educational one to get you involved smoothly.

On Sat, Dec 16, 2017 at 03:04:46PM -0800, Van Goodwin wrote:
> Hello,
...
> I did use this package seriously.  I have used it since I first started using
> Debian.  It is necessary to be able to use the tegaki handwriting recognizer 
> as
> an input method.

I see.
 
> Well, no one using any current version of Debian is using it now since it is
> broken.  According to a post on Github, the tegaki project is no longer being
> maintained so there will be no fix coming from them.  I expect that this issue
> will not get fixed and ibus-tegaki will be removed from stable, testing, and
> unstable.  It is a shame since it was the best Japanese handwriting input
> method I have found for Linux.  The tegaki recognizer still works, but without
> integration with ibus or scim working  and no way to copy to the clipboard, it
> is useless for anything except for practicing one's handwriting.

Can you work on updating the script?  Hints are in my previous mail.

I have many backlog on important packages such as ibus itself.

Your help is most appreciated.

Regards,

Osamu
 

Bug#882344: marked as done (bpfcc FTBFS on !amd64/ppc64el/ppc64: test_usdt_args.cc:63:14: error: 'parser' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 13:19:21 +
with message-id 
and subject line Bug#882344: fixed in bpfcc 0.5.0-1
has caused the Debian Bug report #882344,
regarding bpfcc FTBFS on !amd64/ppc64el/ppc64: test_usdt_args.cc:63:14: error: 
'parser' was not declared in this scope
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.)


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

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

...
In file included from /<>/tests/cc/test_usdt_args.cc:19:0:
/<>/tests/cc/test_usdt_args.cc: In function 'void 
C_A_T_C_HT_E_S_T55()':
/<>/tests/cc/test_usdt_args.cc:63:14: error: 'parser' was not 
declared in this scope
 REQUIRE(!parser.parse(&arg));
  ^
/<>/tests/cc/test_usdt_args.cc:63:14: note: suggested alternative: 
'pause'
/<>/tests/cc/test_usdt_args.cc:63:14: error: 'parser' was not 
declared in this scope
 REQUIRE(!parser.parse(&arg));
  ^
/<>/tests/cc/test_usdt_args.cc:63:14: note: suggested alternative: 
'pause'
/<>/tests/cc/test_usdt_args.cc:148:13: error: 'parser' was not 
declared in this scope
 REQUIRE(parser.done());
 ^
/<>/tests/cc/test_usdt_args.cc:148:13: note: suggested 
alternative: 'pause'
/<>/tests/cc/test_usdt_args.cc:148:13: error: 'parser' was not 
declared in this scope
 REQUIRE(parser.done());
 ^
/<>/tests/cc/test_usdt_args.cc:148:13: note: suggested 
alternative: 'pause'
make[3]: Leaving directory '/<>/obj-aarch64-linux-gnu'
[ 98%] Built target LLCStat
/<>/tests/cc/test_usdt_args.cc: At global scope:
/<>/tests/cc/test_usdt_args.cc:35:13: warning: 'void 
verify_register(USDT::ArgumentParser&, int, const string&, 
std::experimental::optional, 
std::experimental::optional >, 
std::experimental::optional >, 
std::experimental::optional)' defined but not used [-Wunused-function]
 static void verify_register(USDT::ArgumentParser &parser, int arg_size,
 ^~~
/<>/tests/cc/test_usdt_args.cc:25:13: warning: 'void 
verify_register(USDT::ArgumentParser&, int, int)' defined but not used 
[-Wunused-function]
 static void verify_register(USDT::ArgumentParser &parser, int arg_size,
 ^~~
tests/cc/CMakeFiles/test_libbcc.dir/build.make:185: recipe for target 
'tests/cc/CMakeFiles/test_libbcc.dir/test_usdt_args.cc.o' failed
make[3]: *** [tests/cc/CMakeFiles/test_libbcc.dir/test_usdt_args.cc.o] Error 1



The problem is:

#ifdef __powerpc64__
USDT::ArgumentParser_powerpc64 parser("4@-12(42)");
#elif defined(__x86_64__)
USDT::ArgumentParser_x64 parser("4@i%ra+1r");
#endif
USDT::Argument arg;
REQUIRE(!parser.parse(&arg));
--- End Message ---
--- Begin Message ---
Source: bpfcc
Source-Version: 0.5.0-1

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

Debian distribution maintenance software
pp.
Ritesh Raj Sarraf  (supplier of updated bpfcc 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, 17 Dec 2017 18:19:44 +0530
Source: bpfcc
Binary: libbpfcc libbpfcc-dev python-bpfcc bpfcc-tools bpfcc-lua
Architecture: source amd64 all
Version: 0.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ritesh Raj Sarraf 
Changed-By: Ritesh Raj Sarraf 
Description:
 bpfcc-lua  - Standalone tool to run BCC tracers written in Lua
 bpfcc-tools - tools for BPF Compiler Collection (BCC)
 libbpfcc   - shared library for BPF Compiler Collection (BCC)
 libbpfcc-dev - shared library for BPF Compiler Collection (BCC)
 python-bpfcc - Python wrappers for BPF Compiler Collection (BCC)
Closes: 882344
Changes:
 bpfcc (0.5.0-1) unstable; urgency=medium
 .
   * New upstream version 0.5.0
   * Drop architecture support to 64bit common architectures only
 (Closes: #882344)
Checksums-Sha1:
 aa34383ea86027df0a3344ba87e61dacf920ee5d 2509 bpfcc_0.5.0-1.dsc
 81436852ff42d8f7d0e4af74228a83c8effca3d8 1764775 bpfcc_0.5.0.orig.tar.gz
 5b04bc9fd3912f266

Bug#884597: mono-runtime-common: Fail to install mono-runtime-common:i386

[Damien R.]

Package: mono-runtime-common
Version: 4.6.2.7+dfsg-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

When trying to install mono-runtime-common:i386 it fails with the following 
output:
--
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mono-runtime-common:i386 : Depends: binutils:i386 but it is not going to be 
installed
Depends: mono-gac:i386 (= 4.6.2.7+dfsg-1) but it is 
not installable
E: Unable to correct problems, you have held broken packages.
--

The problem is due to that it depends on mono-gac:i386 and as mono-gac is 
available for all
and not for i386 it fails.

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

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

Versions of packages mono-runtime-common depends on:
ii  binutils  2.29.1-12
ii  libc6 2.25-4
ii  mono-gac  4.6.2.7+dfsg-1
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages mono-runtime-common recommends:
ii  binfmt-support  2.1.8-1

Versions of packages mono-runtime-common suggests:
ii  xdg-utils  1.1.2-1

-- no debconf information

Bug#851013: python-pyramid: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Juhani Numminen]

Control: forwarded 851013 https://github.com/Pylons/pyramid/pull/2784
Control: tags 851013 + fixed-upstream

That pull request will probably be the fix.

Taniguchi Takaki is preparing the upstream release 1.9.1 in git
(please also push the upstream and pristine-tar branches) but I cannot
build the new version, there are apparently some missing build-depends.
https://anonscm.debian.org/cgit/python-modules/packages/python-pyramid.git


--
Juhani

Processed: Re: Bug#851013: python-pyramid: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> forwarded 851013 https://github.com/Pylons/pyramid/pull/2784
Bug #851013 [src:python-pyramid] python-pyramid: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/Pylons/pyramid/pull/2784'.
> tags 851013 + fixed-upstream
Bug #851013 [src:python-pyramid] python-pyramid: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 2.7 returned exit code 13
Added tag(s) fixed-upstream.

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

Bug#883953: marked as done (goldencheetah fails to build with libical3)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 12:04:55 +
with message-id 
and subject line Bug#883953: fixed in goldencheetah 1:3.5~DEV1710-1.1
has caused the Debian Bug report #883953,
regarding goldencheetah fails to build with libical3
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.)


-- 
883953: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:goldencheetah
Version: 1:3.5~DEV1710-1
Tags: patch sid buster
Severity: serious

goldencheetah fails to build with libical3

patch at
http://launchpadlibrarian.net/348653229/goldencheetah_1%3A3.5~DEV1710-1build1_1%3A3.5~DEV1710-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: goldencheetah
Source-Version: 1:3.5~DEV1710-1.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 17 Dec 2017 12:42:17 +0100
Source: goldencheetah
Binary: goldencheetah
Architecture: source
Version: 1:3.5~DEV1710-1.1
Distribution: unstable
Urgency: medium
Maintainer: KURASHIKI Satoru 
Changed-By: Matthias Klose 
Description:
 goldencheetah - set of analysis tools for cycling performance
Closes: 883953
Changes:
 goldencheetah (1:3.5~DEV1710-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix build with libical3. Closes: #883953.
Checksums-Sha1:
 161e1b6951a41851a118cef21266db3c67427793 2569 goldencheetah_3.5~DEV1710-1.1.dsc
 4c94a722b3064126a8feec32499a5fd59c552101 76232 
goldencheetah_3.5~DEV1710-1.1.debian.tar.xz
 dd31f65b8bb0e643c44ac85bfe2a5ae3e15cafe2 13334 
goldencheetah_3.5~DEV1710-1.1_source.buildinfo
Checksums-Sha256:
 e47c1995341761dc98cd2acc6ed21183cc11fd4bc08ca398d2f1887ded87b6dc 2569 
goldencheetah_3.5~DEV1710-1.1.dsc
 798fcbea3ec9fec53448144784044e0188d9e72e17e55f867b87e5f184dd79ab 76232 
goldencheetah_3.5~DEV1710-1.1.debian.tar.xz
 bafd3cab6a7ae6af54306082a9e80aa7b16892165f695688eb78df3b7d7d7be8 13334 
goldencheetah_3.5~DEV1710-1.1_source.buildinfo
Files:
 2a84b5afbbd9dfea2ab45a79c6ab4034 2569 misc optional 
goldencheetah_3.5~DEV1710-1.1.dsc
 3aba7da2aa15ab6dee2c888c4a6d8b2a 76232 misc optional 
goldencheetah_3.5~DEV1710-1.1.debian.tar.xz
 82ad20017f4d29e5dea08c6ba0f9956a 13334 misc optional 
goldencheetah_3.5~DEV1710-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlo2WJYQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9TfkEACLO7jcWLbM6OuhJ/fUA4ZE8PJYtBplHv0k
S4L2UP8dKSHmrOkjWYsUi8630m238P8L6nlq9vdPz/x1AGM3UB6pDSN/U/MewnBH
kk/r/JKeuXkG+OJyC2tHUPcUs16SZFlAH7OFhi/toxSI3E8SfoKQl9whs7RfEu+x
LTemIHQ/3ask57rQJBZba3GSRVXe2fP/5pjOVYFuwH3etaL1vv0ej0CJ82y6gnKV
sWVYBt+p7eqVljaduwHmQK45HzL0/sRStyIj1P1zydpQIBV6r1yemc1Qg6C5Hc5Z
JCCJRHxNwiL7q8sMNaZgSz6TydbfHJOlIUwPfbEFsFXBPM0Jl8pWQb0g/y+5POGb
NBELzrf0QGPAyHG8tcMBhp2ioxZI0VW3hEGwlRrbsgDgpk7LqVI/ULAGdIEukxyc
BP2SGmHAfg+nVO2EQhyS2zZ+aL9A77oZ8JKt6iy/V2xHVuL2XMzRntmRtFEIuQ7l
bl4TiiD6p85AqHtkD8a0HJtj1RlgLpZMjVOACnBRUFixQNldXKC3yhxxDk9E77Ot
qtFs4rHpPyNM0uRS4Xv+LLca9aWMYCXG6LHKZQwRTJ81KlkJpjNYA5oQ+9bIp1DS
JNyrjXpVuYJD8/CfDFSTn446ZCVeq7tL9M8XIibD6HSEE6dj5cZYuh/yPAcYMuVW
zcOrSHxkJg==
=llS6
-END PGP SIGNATURE End Message ---

Bug#883741: pyspread: Spreadsheet canvas won't show with newest update

[Martin Manns]

Sorry I mean thanks to the solution of bug #884411

Bug#883741: pyspread: Spreadsheet canvas won't show with newest update

[Martin Manns]

The issue seems to be fixed in Debian testing with 
python-wxgtk3.0 (3.0.2.0+dfsg-6)
thanks to the solution of bug #883741.

Bug#884188: marked as done (python-trezor: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 10:04:06 +
with message-id 
and subject line Bug#884188: fixed in python-trezor 0.7.16-2
has caused the Debian Bug report #884188,
regarding python-trezor: Incomplete debian/copyright?
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.)


-- 
884188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-trezor
Version: 0.7.16-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Tristan Seligmann 

Hi,

I just ACCEPTed python-trezor from NEW but noticed it was missing 
attribution in debian/copyright for at least Marek Palatinus and
Jochen Hoenicke.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-trezor
Source-Version: 0.7.16-2

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated python-trezor 
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, 17 Dec 2017 11:43:20 +0200
Source: python-trezor
Binary: trezor python-trezor python3-trezor
Architecture: source
Version: 0.7.16-2
Distribution: unstable
Urgency: medium
Maintainer: Richard Ulrich 
Changed-By: Tristan Seligmann 
Description:
 python-trezor - library for communicating with TREZOR Bitcoin HW wallet 
(Python 2
 python3-trezor - library for communicating with TREZOR Bitcoin HW wallet 
(Python 3
 trezor - utilities for communicating with TREZOR Bitcoin HW wallet
Closes: 884188
Changes:
 python-trezor (0.7.16-2) unstable; urgency=medium
 .
   * Add some missing copyright information (closes: #884188).
Checksums-Sha1:
 2756f6f261345d329d310e1f279189daf771d3ea 2144 python-trezor_0.7.16-2.dsc
 8b138a0183512d956004c40e79054e85b4ad85f6 3308 
python-trezor_0.7.16-2.debian.tar.xz
 85dc659449e25e5afc7be0924a9bcc4d89ada399 7211 
python-trezor_0.7.16-2_source.buildinfo
Checksums-Sha256:
 bfc87c0fb1eafd154bc5ca8b2f3bfa2ad8b7c549d90612d49e4247ac282039f9 2144 
python-trezor_0.7.16-2.dsc
 d0a94e61ddd777424f37a12f1efdb5e0b34c9525c797a02adc382b9f5d1d8b7d 3308 
python-trezor_0.7.16-2.debian.tar.xz
 b6936ce23cc5e21fd2c75243df7114655168643fb6fcad237e96f70fcdc80fc2 7211 
python-trezor_0.7.16-2_source.buildinfo
Files:
 cc11cf96119ecc3e8e47e9878f21a795 2144 python optional 
python-trezor_0.7.16-2.dsc
 f75833ee42a747ae54e76e129649731f 3308 python optional 
python-trezor_0.7.16-2.debian.tar.xz
 876e2714d7c611134094a186150c4ae8 7211 python optional 
python-trezor_0.7.16-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGpBAEBCgCTFiEEXAZWhXVRbQoz/6ejwImQ+x9jeJMFAlo2PUNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDVD
MDY1Njg1NzU1MTZEMEEzM0ZGQTdBM0MwODk5MEZCMUY2Mzc4OTMVHG1pdGhyYW5k
aUBkZWJpYW4ub3JnAAoJEMCJkPsfY3iTca4H/jVBtQwP7UD20xWgBxkGcTvC7MhS
GBipYoolqqwAnxHDybF41rPGkRPLfI714HM6RpRM5dh4Od8PHxoXsGoB85DtxJ9t
QSYo+vHYDbkgOS27oYKJmwPfZPbKviqenhFGlli4zxe/vo8Bbj6rXkCidESuFx3J
ynQDXhOl9UKKi9TDarojzCjU9mLZOgTxSWfhv6T9Yna0fY4gj+71wvbJn+0sAxAD
bn5LFXIvmIXstF2+FmyJXEOCtbwBP7CfYOzsQLOaGIegG5GhVKz0GehykkB8C2c+
Ljl0EJ0tbr0WjCYs3FMT5x33z9FSC9r1g5cB/z6m8TkqYTHmd+cn26JDy9U=
=q58g
-END PGP SIGNATURE End Message ---

Processed: Bug#884188 marked as pending

[Debian Bug Tracking System]

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

> tag 884188 pending
Bug #884188 [src:python-trezor] python-trezor: Incomplete debian/copyright?
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#884188: marked as pending

[Tristan Seligmann]

tag 884188 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/python-trezor.git/commit/?id=1b77075

---
commit 1b770751f669be06df92e0a94abc79d66ce5a117
Author: Tristan Seligmann 
Date:   Sun Dec 17 11:43:24 2017 +0200

Add some missing copyright information (closes: #884188).

diff --git a/debian/changelog b/debian/changelog
index 33d733d..0299631 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-trezor (0.7.16-2) unstable; urgency=medium
+
+  * Add some missing copyright information (closes: #884188).
+
+ -- Tristan Seligmann   Sun, 17 Dec 2017 11:43:20 +0200
+
 python-trezor (0.7.16-1) unstable; urgency=medium
 
   * New upstream release.

Bug#877159: marked as done (obnam FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 815: ordinal not in range(128))

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 09:38:23 +
with message-id 
and subject line Bug#884581: Removed package(s) from unstable
has caused the Debian Bug report #877159,
regarding obnam FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 
in position 815: ordinal not in range(128)
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.)


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

Some recent change in unstable makes obnam FTBFS:

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

...
ERROR:root:Command failed: python obnam --generate-manpage=obnam.1.de.in 
--output=obnam.1

CRITICAL:root:Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 183, in _run
args = self.parse_args(args)
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 548, in parse_args
compute_setting_values=self.compute_setting_values)
  File "/usr/lib/python2.7/dist-packages/cliapp/settings.py", line 732, in 
parse_args
_, args = p.parse_args(args)
  File "/usr/lib/python2.7/optparse.py", line 1400, in parse_args
stop = self._process_args(largs, rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1440, in _process_args
self._process_long_opt(rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1515, in _process_long_opt
option.process(opt, value, values, self)
  File "/usr/lib/python2.7/optparse.py", line 789, in process
self.action, self.dest, opt, value, values, parser)
  File "/usr/lib/python2.7/optparse.py", line 809, in take_action
self.callback(self, opt, value, parser, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cliapp/settings.py", line 886, in 
_generate_manpage
sys.stdout.write(generator.format_template())
  File "/usr/lib/python2.7/dist-packages/cliapp/genman.py", line 84, in 
format_template
text = text.replace(pattern, pattern + contents)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 815: 
ordinal not in range(128)

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 183, in _run
args = self.parse_args(args)
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 548, in parse_args
compute_setting_values=self.compute_setting_values)
  File "/usr/lib/python2.7/dist-packages/cliapp/settings.py", line 732, in 
parse_args
_, args = p.parse_args(args)
  File "/usr/lib/python2.7/optparse.py", line 1400, in parse_args
stop = self._process_args(largs, rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1440, in _process_args
self._process_long_opt(rargs, values)
  File "/usr/lib/python2.7/optparse.py", line 1515, in _process_long_opt
option.process(opt, value, values, self)
  File "/usr/lib/python2.7/optparse.py", line 789, in process
self.action, self.dest, opt, value, values, parser)
  File "/usr/lib/python2.7/optparse.py", line 809, in take_action
self.callback(self, opt, value, parser, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/cliapp/settings.py", line 886, in 
_generate_manpage
sys.stdout.write(generator.format_template())
  File "/usr/lib/python2.7/dist-packages/cliapp/genman.py", line 84, in 
format_template
text = text.replace(pattern, pattern + contents)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 815: 
ordinal not in range(128)

building manpage for obnam (lang=)
building manpage for obnam (lang=.de)
Traceback (most recent call last):
  File "setup.py", line 353, in 
'clean': CleanMore,
  File "/usr/lib/python2.7/distutils/core.py", line 151, in setup
dist.run_commands()
  File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
self.run_command(cmd)
  File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
cmd_obj.run()
  File "setup.py", line 65, in run
self.build_manpage('obnam', '.de')
  File "setup.py", line 69, in build_manpage
self.generate_troff(program, lang)
  File "setup.py", line 77, in generate_troff
stdout=f)
  File "/usr/lib/python2.7/dist-packages/cliapp/runcmd.py", line 64, in runcmd
raise cliapp.AppException(msg)
cliapp.app.AppException: Command failed: python obnam 
--generate-manpage=obnam.1.de.in --output=obnam.1

CRITICAL:root:Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 183, in

Bug#847641: marked as done (obnam: FTBFS on all archs due to test failure)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 09:38:23 +
with message-id 
and subject line Bug#884581: Removed package(s) from unstable
has caused the Debian Bug report #847641,
regarding obnam: FTBFS on all archs due to test failure
to be marked as done.

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

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


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

I checked the BTS but it doesn't look like this has been reported
before; sorry if this is a duplicate report.

obnam currently FTBFS on all archs in sid (for about a month now);
relevant part of build log is as follows:


ERROR: In scenario "encrypted backup and restore with a separate keyring"
step "WHEN user U backs up directory L to repository R" failed,
with exit code 1:
Standard output from shell command:

Standard error from shell command:
+ run_obnam U backup -r
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/R
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/L
+ local name=U
+ shift
+ local 
conf=/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
+ [ ! -e 
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
]
+ add_to_config U weak-random yes
+ local client=U
+ local 
filename=/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
+ local key=weak-random
+ local value=yes
+ [ ! -e 
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
]
+ printf %s = %s\n weak-random yes
+ add_to_config U lock-timeout 0
+ local client=U
+ local 
filename=/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
+ local key=lock-timeout
+ local value=0
+ [ ! -e 
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
]
+ printf %s = %s\n lock-timeout 0
+ [ -n 6 ]
+ add_to_config U repository-format 6
+ local client=U
+ local 
filename=/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
+ local key=repository-format
+ local value=6
+ [ ! -e 
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
]
+ printf %s = %s\n repository-format 6
+ [ -e 
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.env
]
+ /«PKGBUILDDIR»/obnam --no-default-config --config
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/U.conf
--quiet --log-level debug --log
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/obnam.log
--trace obnamlib --trace larch backup -r
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/R
/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/L
ERROR: R0C79EX: gpg failed with exit code 2:
Command: gpg -q --batch --no-textmode -c --passphrase-fd 4
gpg: can't open '/usr/share/gnupg/dirmngr-conf.skel': No such file
or directory
gpg: new configuration file
'/tmp/tmpNm8AbD/encrypted_backup_and_restore_with_a_separate_keyring/datadir/HOME/.gnupg/gpg.conf'
created
gpg: can't connect to the agent: IPC connect call failed
gpg: problem with the agent: No agent running
--- End Message ---
--- Begin Message ---
Version: 1.22-1+rm

Dear submitter,

as the package obnam has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/884581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#786743: marked as done (obnam: ftbfs, git command not found)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 09:38:23 +
with message-id 
and subject line Bug#884581: Removed package(s) from unstable
has caused the Debian Bug report #786743,
regarding obnam: ftbfs, git command not found
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.)


-- 
786743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: obnam
version: 1.8-1
Severity: serious
x-debbugs-cc: reproducible-bui...@lists.alioth.debian.org

Hi Lars,

While working on the “reproducible builds” effort [1], we have noticed that 
obnam fails to build from source:

[...]
running build_scripts
creating build/scripts-2.7
copying and adjusting obnam -> build/scripts-2.7
copying and adjusting obnam-viewprof -> build/scripts-2.7
changing mode of build/scripts-2.7/obnam from 644 to 755
changing mode of build/scripts-2.7/obnam-viewprof from 644 to 755
building manpages
make -C manual
make[2]: Entering directory '/tmp/buildd/obnam-1.8/manual'
/bin/sh: 1: git: not found
./format-pdf obnam-manual.en.pdf "Backups with Obnam" "Lars Wirzenius 
(l...@liw.fi)" "Version 1.8" en/010-introduction.mdwn en/020-concepts.mdwn 
en/040-installing.mdwn 
en/050-quick-tour.mdwn en/060-backing-up.mdwn en/070-restoring.mdwn 
en/080-forgetting.mdwn en/090-verifiying.mdwn en/100-many-clients.mdwn 
en/110-encryption.mdwn en/120-
misc.mdwn en/130-case-studies.mdwn en/140-troubleshooting.mdwn 
en/150-config.mdwn en/900-see-also.mdwn en/980-legalese.mdwn en/990-blurb.mdwn
pandoc: Duplicate link reference `[libgfshare]' "source" (line 1237, column 1)
! LaTeX Error: Command \textquotesingle unavailable in encoding T1.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.709 ...\textbackslash{}.mp3\$\textquotesingle{}}

pandoc: Error producing PDF from TeX source
Makefile:36: recipe for target 'obnam-manual.en.pdf' failed
make[2]: *** [obnam-manual.en.pdf] Error 43
make[2]: Leaving directory '/tmp/buildd/obnam-1.8/manual'
debian/rules:6: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/tmp/buildd/obnam-1.8'
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


The full log is available at 
https://reproducible.debian.net/rbuild/unstable/amd64/obnam_1.8-1.rbuild.log

I could also reproduce this issue locally on my laptop with pbuilder.


cheers,
Holger

 [1]: https://wiki.debian.org/ReproducibleBuilds


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 1.22-1+rm

Dear submitter,

as the package obnam has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/884581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#735809: marked as done (obnam: FTBFS: Tests failed)

[Debian Bug Tracking System]

Your message dated Sun, 17 Dec 2017 09:38:23 +
with message-id 
and subject line Bug#884581: Removed package(s) from unstable
has caused the Debian Bug report #735809,
regarding obnam: FTBFS: Tests failed
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.)


-- 
735809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obnam
Version: 1.6.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20140114 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> python setup.py build_ext -i
> running build_ext
> building 'obnamlib._obnam' extension
> x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 
> -Wall -Wstrict-prototypes -fPIC -I/usr/include/python2.7 -c _obnammodule.c -o 
> build/temp.linux-x86_64-2.7/_obnammodule.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector 
> --param=ssp-buffer-size=4 -Wformat -Werror=format-security 
> build/temp.linux-x86_64-2.7/_obnammodule.o -o 
> /«PKGBUILDDIR»/obnamlib/_obnam.so
> rm -rf build
> cp -a test-gpghome temp.gpghome
> env GNUPGHOME=temp.gpghome python setup.py check --fast
> running check
> 
> 
> FAILED
> 
> FAILURE: test_lgetxattr (vfs_local_tests.XAttrTests)
> Traceback (most recent call last):
>   File "./obnamlib/vfs_local_tests.py", line 74, in test_lgetxattr
> self.assertEqual(_obnam.lgetxattr(self.filename, "user.hello"), "world")
> AssertionError: 95 != 'world'
> 
> FAILURE: test_lsetxattr (vfs_local_tests.XAttrTests)
> Traceback (most recent call last):
>   File "./obnamlib/vfs_local_tests.py", line 69, in test_lsetxattr
> ["user.hello", "user.key"])
> AssertionError: Lists differ: [''] != ['user.hello', 'user.key']
> 
> First differing element 0:
> 
> user.hello
> 
> Second list contains 1 additional elements.
> First extra element 1:
> user.key
> 
> - ['']
> + ['user.hello', 'user.key']
> 
> 2 failures, 0 errors
> 231 excluded statements
> 24 excluded modules
> Time: 7.0 s
> ERROR: Command '['python', '-m', 'CoverageTestRunner', 
> '--ignore-missing-from=without-tests']' returned non-zero exit status 1
> run unit tests
> make[1]: *** [override_dh_auto_test] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/01/14/obnam_1.6.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.22-1+rm

Dear submitter,

as the package obnam has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/884581

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#883615: Acknowledgement ([CRITICAL] Stretch p-u 9.3 breaks NVidia driver and X.org)

[Andreas Beckmann]

I did dig further. An easier target for debugging is glxinfo. Which can be 
further minimized to

#include 
#include 
#include 
int main()
{
pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_lock(&mutex);
pthread_mutex_unlock(&mutex);

Display * dpy ;
dpy = XOpenDisplay ( NULL ) ;

pthread_mutex_lock(&mutex);
pthread_mutex_unlock(&mutex);

   int fbAttribSingle[] = {
  GLX_RENDER_TYPE,   GLX_RGBA_BIT,
  GLX_RED_SIZE,  1,
  GLX_GREEN_SIZE,1,
  GLX_BLUE_SIZE, 1,
  GLX_DOUBLEBUFFER,  False,
  None };
GLXFBConfig * configs ;
int nConfigs ;
configs = glXChooseFBConfig ( dpy , 0 , fbAttribSingle , & nConfigs ) ;

pthread_mutex_lock(&mutex);
pthread_mutex_unlock(&mutex);
}

(link with -lGL -lX11)

that dies at some point in pthread_mutex_lock after several
calls succeeded:

(gdb) bt
#0  0x7754b1d4 in pthread_mutex_lock (mutex=0x77001180 
) at forward.c:192
#1  0x76dab007 in LockDispatch () at 
../../../src/GLdispatch/GLdispatch.c:144
#2  __glDispatchNewVendorID () at ../../../src/GLdispatch/GLdispatch.c:198
#3  0x7702c3c2 in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
#4  0x7702d1ac in ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
#5  0x77026251 in glXChooseFBConfig () from 
/usr/lib/x86_64-linux-gnu/libGLX.so.0
#6  0x4964 in main () at mwe.c:25
(gdb) info shared
>FromTo  Syms Read   Shared Object Library
0x77dd9aa0  0x77df5340  Yes /lib64/ld-linux-x86-64.so.2
0x77b745d0  0x77b78c1b  Yes (*) 
/usr/lib/x86_64-linux-gnu/libGL.so.1
0x77812da0  0x7789a434  Yes (*) 
/usr/lib/x86_64-linux-gnu/libX11.so.6
0x77475910  0x7759f403  Yes 
/lib/x86_64-linux-gnu/libc.so.6
0x77252d80  0x7725394e  Yes 
/lib/x86_64-linux-gnu/libdl.so.2
0x77024a20  0x7702ef9d  Yes (*) 
/usr/lib/x86_64-linux-gnu/libGLX.so.0
0x76daabb0  0x76dada37  Yes 
/usr/lib/x86_64-linux-gnu/libGLdispatch.so.0
0x76b4fb40  0x76b619f5  Yes (*) 
/usr/lib/x86_64-linux-gnu/libxcb.so.1
0x76935700  0x7693f49f  Yes (*) 
/usr/lib/x86_64-linux-gnu/libXext.so.6
0x7672f010  0x7672fc8c  Yes (*) 
/usr/lib/x86_64-linux-gnu/libXau.so.6
0x76529340  0x7652ac48  Yes (*) 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6
0x763153d0  0x763225df  Yes (*) 
/lib/x86_64-linux-gnu/libbsd.so.0
0x7610c0e0  0x7610eecf  Yes 
/lib/x86_64-linux-gnu/librt.so.1
0x75ef2ab0  0x75eff811  Yes 
/lib/x86_64-linux-gnu/libpthread.so.0
0x75c00f00  0x75c76291  Yes (*) 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
0x759ab810  0x759ad5a3  Yes (*) 
/usr/lib/x86_64-linux-gnu/libnvidia-tls.so.375.82
0x73ed7600  0x74fbac77  Yes (*) 
/usr/lib/x86_64-linux-gnu/libnvidia-glcore.so.375.82
0x738d7680  0x739438da  Yes 
/lib/x86_64-linux-gnu/libm.so.6
(gdb) disassemble
Dump of assembler code for function pthread_mutex_lock:
   0x7754b1b0 <+0>: mov0x2a957a(%rip),%eax# 
0x777f4730 <__libc_pthread_functions_init>
   0x7754b1b6 <+6>: test   %eax,%eax
   0x7754b1b8 <+8>: jne0x7754b1c0 
   0x7754b1ba <+10>:xor%eax,%eax
   0x7754b1bc <+12>:retq   
   0x7754b1bd <+13>:nopl   (%rax)
   0x7754b1c0 <+16>:mov0x2a94c1(%rip),%rax# 
0x777f4688 <__libc_pthread_functions+264>
   0x7754b1c7 <+23>:ror$0x11,%rax
   0x7754b1cb <+27>:xor%fs:0x30,%rax
=> 0x7754b1d4 <+36>:jmpq   *%rax

After finally understanding that the fs segment is used for TLS storage
addressing, I actually saw the difference in the linked libraries:
/usr/lib/x86_64-linux-gnu/libnvidia-tls.so.375.82 vs.
/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.375.82


>From the documentation:

The nvidia-tls libraries (/usr/lib/libnvidia-tls.so.384.98 and 
/usr/lib/tls/libnvidia-tls.so.384.98); these files provide thread local storage 
support for the NVIDIA OpenGL libraries (libGL, libnvidia-glcore, and libglx). 
Each nvidia-tls library provides support for a particular thread local storage 
model (such as ELF TLS), and the one appropriate for your system will be loaded 
at run time.

and from the source code of nvidia-installer (which we don't use):

  "NVIDIA's OpenGL libraries are compiled with one of two "
  "different thread local storage (TLS) mechanisms: 'classic tls' "
  "which is used on systems with glibc 2.2 or older, and 'new tls' "
  "which is used on systems with tls-enabled glibc 2.3 or newer.  "

So we probably shouldn't ship the classic ones at all and move the new
one