Bug#893075: marked as done (liblttoolbox3-3.3-0v5 must be dropped since it now depends on the wrong soversion)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 07:04:15 +
with message-id 
and subject line Bug#893075: fixed in lttoolbox 3.4.2-2
has caused the Debian Bug report #893075,
regarding liblttoolbox3-3.3-0v5 must be dropped since it now depends on the 
wrong soversion
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.)


-- 
893075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: liblttoolbox3-3.3-0v5
Version: 3.4.0~r84331-1
Severity: grave
Control: affects -1 apertium src:apertium-es-pt

$ apertium-preprocess-transfer
apertium-preprocess-transfer: error while loading shared libraries: 
liblttoolbox3-3.3.so.0: cannot open shared object file: No such file or 
directory
$


Root cause:

Package: liblttoolbox3-3.3-0v5
Version: 3.4.0~r84331-1
Depends: liblttoolbox3-3.4-1 (>= 3.4.0~r84331-1)
Description-en: Transitional package to undo g++-5 renaming
 This is a transitional dummy package. It can safely be removed.
--- End Message ---
--- Begin Message ---
Source: lttoolbox
Source-Version: 3.4.2-2

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated lttoolbox package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 11:48:08 +0530
Source: lttoolbox
Binary: lttoolbox liblttoolbox3-3.4-1 lttoolbox-dev
Architecture: source amd64
Version: 3.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 liblttoolbox3-3.4-1 - Shared library for lttoolbox
 lttoolbox  - Apertium lexical processing modules and tools
 lttoolbox-dev - Development tools and library for lttoolbox
Closes: 893075
Changes:
 lttoolbox (3.4.2-2) unstable; urgency=medium
 .
   * debian/control:
 + Regression fix: Drop dummy transitional package. (Closes: #893075)
Checksums-Sha1:
 b2de53bc9aaac43776b15a5a6e6885f01831b307 2303 lttoolbox_3.4.2-2.dsc
 b62fc801ae59dd2263b2c5d60a95ef39d71564ae 4652 lttoolbox_3.4.2-2.debian.tar.xz
 b5cd3a4ffa988e492ea0f05913a76a2172ef 2160756 
liblttoolbox3-3.4-1-dbgsym_3.4.2-2_amd64.deb
 cba5d53dbb92ed94b3ebf0df71437a08fe74c24e 156384 
liblttoolbox3-3.4-1_3.4.2-2_amd64.deb
 f65e13111944ad9046a303b1c0110eb70c8a3954 337420 
lttoolbox-dbgsym_3.4.2-2_amd64.deb
 d1dcc021eaf366648dd8210160f3014c0c1fcbe3 432928 
lttoolbox-dev-dbgsym_3.4.2-2_amd64.deb
 2df4b007a6d7f83a08094992299a404f4bd7e77a 51056 lttoolbox-dev_3.4.2-2_amd64.deb
 2071bd66dd25e50a6ce953af346793b909676c92 8796 lttoolbox_3.4.2-2_amd64.buildinfo
 d189a7bcb33d4ec5472cb48b779e891d48890368 22596 lttoolbox_3.4.2-2_amd64.deb
Checksums-Sha256:
 d12dc0799e8c2306dc9de01d9b4665b0ceee9de198c908f73635eed56c8fbad0 2303 
lttoolbox_3.4.2-2.dsc
 69c07e917f626f5d1fe5813a2620b0b6258320f54b1dac388cdb5b7bd093aa93 4652 
lttoolbox_3.4.2-2.debian.tar.xz
 693d989f45cca4d08bd7cc940da2dc65529af184bcd77d9489021599851f9b3a 2160756 
liblttoolbox3-3.4-1-dbgsym_3.4.2-2_amd64.deb
 32ac3dc474a3cae345c3ddbbd7b4da57dcc482aea6806769ba7cea1981771523 156384 
liblttoolbox3-3.4-1_3.4.2-2_amd64.deb
 851cad28f8b406fc5c78bb53e3448acb06d7b52bf809ad54f9b60448a022bf52 337420 
lttoolbox-dbgsym_3.4.2-2_amd64.deb
 c5b81aeb5221aedc64674221b7d24e70465ecea82b1541d564ebe8c4d4466abf 432928 
lttoolbox-dev-dbgsym_3.4.2-2_amd64.deb
 2a5632f1814d8cb7fc67febcd466ff0c667aea997e217b06b7b7d5841122f151 51056 
lttoolbox-dev_3.4.2-2_amd64.deb
 e2b7aed1901fb63822744996ddf7af0eea680d551ecbac6201da69c47bcc0645 8796 
lttoolbox_3.4.2-2_amd64.buildinfo
 f71ad483cfc0704b55057c476dcb8cfc83b7c408f3bcb7409975a44b7eb0dc96 22596 
lttoolbox_3.4.2-2_amd64.deb
Files:
 10f871c2ca0c33d901e40e6cf3d711fe 2303 science optional lttoolbox_3.4.2-2.dsc
 eae96440bbda7990dfd7851047c07184 4652 science optional 
lttoolbox_3.4.2-2.debian.tar.xz
 4787770432bfb04465aeb2c79099ac4c 2160756 debug optional 
liblttoolbox3-3.4-1-dbgsym_3.4.2-2_amd64.deb
 a3cea4221efa88fa662672d98b9a3b5e 156384 libs optional 
liblttoolbox3-3.4-1_3.4.2-2_amd64.deb
 c0c0be88555d247c287ae

Bug#897504: marked as done (golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/hashicorp/go-plugin returned exit code 1)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 07:04:00 +
with message-id 
and subject line Bug#897504: fixed in golang-github-hashicorp-go-plugin 
0.0~git20170621.5ee1a665-1
has caused the Debian Bug report #897504,
regarding golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 1 github.com/hashicorp/go-plugin 
returned exit code 1
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.)


-- 
897504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-hashicorp-go-plugin
Version: 0.0~git20160212.0.cccb4a1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 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):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install 
> -gcflags=\"-trimpath=/<>/golang-github-hashicorp-go-plugin-0.0\~git20160212.0.cccb4a1/obj-x86_64-linux-gnu/src\"
>  
> -asmflags=\"-trimpath=/<>/golang-github-hashicorp-go-plugin-0.0\~git20160212.0.cccb4a1/obj-x86_64-linux-gnu/src\"
>  -v -p 1 github.com/hashicorp/go-plugin
> github.com/hashicorp/yamux
> github.com/hashicorp/go-plugin
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
> github.com/hashicorp/go-plugin
> === RUN   TestClient_testInterfaceReattach
> 2018/05/02 19:21:27 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "test-interface-daemon"}
> 2018/05/02 19:21:27 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:27 [DEBUG] plugin: go-plugin.test: 2018/05/02 19:21:27 
> [DEBUG] plugin: plugin address: unix /tmp/plugin359815028
> 2018/05/02 19:21:28 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> 2018/05/02 19:21:29 [DEBUG] plugin: reattached plugin process exited
> --- PASS: TestClient_testInterfaceReattach (2.00s)
> === RUN   TestClient
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "mock"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClient (0.00s)
> === RUN   TestClient_testInterface
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "test-interface"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: go-plugin.test: 2018/05/02 19:21:29 
> [DEBUG] plugin: plugin address: unix /tmp/plugin030403425
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClient_testInterface (0.01s)
> === RUN   TestClient_cmdAndReattach
> --- PASS: TestClient_cmdAndReattach (0.00s)
> === RUN   TestClient_reattachNotFound
> --- PASS: TestClient_reattachNotFound (0.01s)
> === RUN   TestClientStart_badVersion
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "bad-version"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEBUG] plugin: 
> /tmp/go-build273529730/b001/go-plugin.test: plugin process exited
> --- PASS: TestClientStart_badVersion (0.00s)
> === RUN   TestClient_Start_Timeout
> 2018/05/02 19:21:29 [DEBUG] plugin: starting plugin: 
> /tmp/go-build273529730/b001/go-plugin.test 
> []string{"/tmp/go-build273529730/b001/go-plugin.test", 
> "-test.run=TestHelperProcess", "--", "start-timeout"}
> 2018/05/02 19:21:29 [DEBUG] plugin: waiting for RPC address for: 
> /tmp/go-build273529730/b001/go-plugin.test
> 2018/05/02 19:21:29 [DEB

Bug#896636: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 07:49:23 +
with message-id 
and subject line Bug#896636: fixed in sphinx-argparse 0.2.2-1
has caused the Debian Bug report #896636,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: sphinx-argparse
Source-Version: 0.2.2-1

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sphinx-argparse 
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: Thu, 28 Jun 2018 10:30:18 +0300
Source: sphinx-argparse
Binary: python-sphinx-argparse python3-sphinx-argparse
Architecture: source
Version: 0.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dmitry Shachnev 
Description:
 python-sphinx-argparse - Sphinx extension for argparse commands and options 
(Python 2)
 python3-sphinx-argparse - Sphinx extension for argparse commands and options 
(Python 3)
Closes: 840038 896636
Changes:
 sphinx-argparse (0.2.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
 - No longer uses sphinx.util.compat (Closes: #896636).
 .
   [ ChangZhuo Chen (陳昌倬) ]
   * Add ChangZhuo Chen as Uploaders (Closes: #840038).
   * Bump compat to 10.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
 .
   [ Dmitry Shachnev ]
   * Remove usage of Markdown options in docs/markdown.rst. Upstream code for
 Markdown requires CommonMark 0.5.6, which is not yet in Debian.
   * Fix sphinx-build invocation in debian/rules.
   * Prevent dh_compress from compressing changelog.html.
   * Drop unneeded dh_auto_test override, rely on pybuild magic.
   * Make autopkgtests test the installed version of the package.
   * Bump Standards-Version to 4.1.4, no changes needed.
Checksums-Sha1:
 bd17318b8927

Bug#902526: [Pkg-zsh-devel] Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Daniel Shahaf]

Axel Beckert wrote on Wed, 27 Jun 2018 15:19 +0200:
> Hi,
> 

Thanks for having a look, Axel.

> Daniel Shahaf wrote:
> > > dh_installchangelogs
> > > rm 
> > > debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog.md
> > > rm: cannot remove 
> > > 'debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog.md':
> > >  No such file or directory
> > > debian/rules:14: recipe for target 'override_dh_installchangelogs' failed
> > > make[1]: *** [override_dh_installchangelogs] Error 1
> > 
> > I'm guessing that debhelper on buster installs that file as
> > /usr/share/doc/.../changelog.md.gz or something,
> 
> It is only installed as
> /usr/share/doc/zsh-syntax-highlighting/changelog at that time.
> 
> Not sure why the path used by the upstream build system to install it,
> seems no more present.
> 

That's odd.  Upstream's 'make install' does 'cp changelog.md $(DOC_DIR)'
and that part hasn't changed between 0.5.0 (stretch) and 0.6.0 (buster).  It's 
even
the same in upstream's HEAD.

> > but I don't have a buster build env handy to investigate. Is someone
> > able to look into this?
> 
> Done: Dropping override_dh_installchangelogs already suffices to make
> the package build again.
> 
> I though wonder if that isn't actually a regression in a recent
> debhelper release.

You mean, a regression whereby debhelper removes the .md suffix
overzealously?  According to debhelper's own changelog, there have been
several changes to dh_installchangelogs in debhelper 11.3{,.1,.2}, so a
regression is not inconceivable.  However, all those mentions of
'upstream changelogs' in dh's own changelog make me wonder if dh got smarter,
is recognising changelog.md as an upstream changelog, and by itself avoids 
installing
changelog twice --- which makes the 'rm' in z-sy-h's d/rules redundant.
If that's the case, then removing the override_dh_installchangelogs
target would be the correct fix.

Does this make senes?

Thanks again,

Daniel

Processed: reassign 902514 to python-cmd2

[Debian Bug Tracking System]

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

> reassign 902514 python-cmd2
Bug #902514 [python-cmd2] python-cmd2: missing dependency on python-enum34
Ignoring request to reassign bug #902514 to the same package
> thanks
Stopping processing here.

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

Processed: Bug #901672 in python-pygit2 marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #901672 [src:python-pygit2] python-pygit2: FTBFS on i386: error: struct 
git_time: wrong total size (cdef says 12, but C compiler says 16)
Added tag(s) pending.

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

Bug#901672: Bug #901672 in python-pygit2 marked as pending

[Ondřej Nový]

Control: tag -1 pending

Hello,

Bug #901672 in python-pygit2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/python-team/modules/python-pygit2/commit/3bcc43b49c20162010fc79ddbf2b5fa3dd3da4dc


New upstream release (Closes: #901672)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/901672

Bug#902592: spades ftbfs with new nlopt in unstable

[Matthias Klose]

Package: src:spades
Version: 3.11.1+dfsg-1
Severity: serious
Tags: sid buster

spades ftbfs with the new nlopt in unstable:

[ 49%] Building CXX object 
common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o
cd /<>/spades-3.11.1+dfsg/build_spades/common/modules/coverage_model 
&& /usr/bin/c++  -DJEMALLOC_NO_DEMANGLE -DUSE_GLIBCXX_PARALLEL=1 
-I/<>/spades-3.11.1+dfsg/build_spades/common/modules/coverage_model 
-I/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model 
-I/<>/spades-3.11.1+dfsg/src/include 
-I/<>/spades-3.11.1+dfsg/build_spades/include 
-I/<>/spades-3.11.1+dfsg/src 
-I/<>/spades-3.11.1+dfsg/src/common -isystem 
/<>/spades-3.11.1+dfsg/src/../ext/include  -g -O2 
-fdebug-prefix-map=/<>/spades-3.11.1+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp 
-std=c++11 -O2 -g -DNDEBUG   -UNDEBUG -Wno-deprecated -g3 -O2 -Wall -Wextra 
-Wconversion -Wno-sign-conversion -Wno-long-long -Wwrite-strings -o 
CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o -c 
/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model/kmer_coverage_model.cpp
/<>/spades-3.11.1+dfsg/src/common/modules/coverage_model/kmer_coverage_model.cpp:21:10: 
fatal error: nlopt.hpp: No such file or directory

 #include 
  ^~~
compilation terminated.
common/modules/coverage_model/CMakeFiles/coverage_model.dir/build.make:62: 
recipe for target 
'common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o' 
failed
make[4]: *** 
[common/modules/coverage_model/CMakeFiles/coverage_model.dir/kmer_coverage_model.cpp.o] 
Error 1

make[4]: Leaving directory '/<>/spades-3.11.1+dfsg/build_spades'
CMakeFiles/Makefile2:1310: recipe for target 
'common/modules/coverage_model/CMakeFiles/coverage_model.dir/all' failed
make[3]: *** [common/modules/coverage_model/CMakeFiles/coverage_model.dir/all] 
Error 2

make[3]: Leaving directory '/<>/spades-3.11.1+dfsg/build_spades'
Makefile:151: recipe for target 'all' failed
make[2]: *** [all] Error 2

Bug#902597: protobuf ftbfs with python3.7 as a supported version

[Matthias Klose]

Package: src:protobuf
Version: 3.0.0-9.1
Severity: serious
Tags: sid buster

protobuf ftbfs with python3.7 as a supported version:

390x-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I. -I../src 
-I/usr/include/python3.7m -c google/protobuf/pyext/descriptor_pool.cc -o 
build/temp.linux-s390x-3.7/google/protobuf/pyext/descriptor_pool.o 
-Wno-write-strings -Wno-invalid-offsetof -Wno-sign-compare
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindMessageByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:176:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindFileByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:224:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindFieldByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:242:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindExtensionByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:260:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindEnumTypeByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:277:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindOneofByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:294:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &name, &name_size) < 0) {
   ^~~~
google/protobuf/pyext/descriptor_pool.cc: In function ‘PyObject* 
google::protobuf::python::cdescriptor_pool::FindServiceByName(google::protobuf::python::PyDescriptorPool*, 
PyObject*)’:
google/protobuf/pyext/descriptor_pool.cc:50:45: error: invalid conversion from 
‘const char*’ to ‘char*’ [-fpermissive]

((*(charpp) = PyUnicode_AsUTF8AndSize(ob, (sizep))) == NULL? -1: 0): \
  ~~~^
google/protobuf/pyext/descriptor_pool.cc:311:7: note: in expansion of macro 
‘PyString_AsStringAndSize’

   if (PyString_AsStringAndSize(arg, &na

Bug#902526: [Pkg-zsh-devel] Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Axel Beckert]

Hi Daniel,

Daniel Shahaf wrote:
> > > I'm guessing that debhelper on buster installs that file as
> > > /usr/share/doc/.../changelog.md.gz or something,
> > 
> > It is only installed as
> > /usr/share/doc/zsh-syntax-highlighting/changelog at that time.
> > 
> > Not sure why the path used by the upstream build system to install it,
> > seems no more present.
> 
> That's odd.  Upstream's 'make install' does 'cp changelog.md $(DOC_DIR)'
> and that part hasn't changed between 0.5.0 (stretch) and 0.6.0 (buster).  
> It's even
> the same in upstream's HEAD.

*nod*

> > > but I don't have a buster build env handy to investigate. Is someone
> > > able to look into this?
> > 
> > Done: Dropping override_dh_installchangelogs already suffices to make
> > the package build again.
> > 
> > I though wonder if that isn't actually a regression in a recent
> > debhelper release.
> 
> You mean, a regression whereby debhelper removes the .md suffix
> overzealously?

Maybe. Or something else.

> According to debhelper's own changelog, there have been
> several changes to dh_installchangelogs in debhelper 11.3{,.1,.2}, so a
> regression is not inconceivable.

Exactly. Especially because nothing in these entries sounded close
enough to cause such a behaviour on purpose. But maybe I haven't
looked close enough.

> However, all those mentions of 'upstream changelogs' in dh's own
> changelog make me wonder if dh got smarter, is recognising
> changelog.md as an upstream changelog, and by itself avoids
> installing changelog twice --- which makes the 'rm' in z-sy-h's
> d/rules redundant.

That seems to be the reason. Running with DH_VERBOSE=1 I see this line:

mv 
debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog.md
 debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog

This corresponds to a change in 11.3:

  * dh_installchangelogs: Look for changelog files installed by the
upstream build system in the package build dir (i.e. d//
and *not* debian/tmp!) and use them in preference to the one in the
source package where available.  This avoids some cases of duplicated
upstream changelogs.  Thanks to Evgeni Golov for the suggestion.
(Closes: #513521)

> If that's the case, then removing the override_dh_installchangelogs
> target would be the correct fix.

Yes.

> Does this make senes?

Now that I verified that your guess was right, yes. :-)

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

Processed: Re: [Pkg-zsh-devel] Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #902526 [src:zsh-syntax-highlighting] zsh-syntax-highlighting: FTBFS in 
buster/sid (does not work with recent debhelper)
Added tag(s) patch.

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

Bug#902526: [Pkg-zsh-devel] Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Daniel Shahaf]

Control: tags -1 patch

Axel Beckert wrote on Thu, 28 Jun 2018 11:24 +0200:
> Daniel Shahaf wrote:
> > If that's the case, then removing the override_dh_installchangelogs
> > target would be the correct fix.
> 
> Yes.
> 

Okay.  In this case the attached patch should fix it.

Getting a bit ahead of myself, we don't seem to have anywhere to push
that patch now, since the package's repository was on alioth and hasn't
been migrated to salsa.  I'll have to look into migrating that.  (Also would
need to test the patch and tag an 0.6.0-2 that has it.)

> > Does this make senes?
> 
> Now that I verified that your guess was right, yes. :-)

Thanks again your the help, Axel. :-)

Daniel
From 7ce9697ed43d20e9a10fce052516b4b324654c6c Mon Sep 17 00:00:00 2001
From: Daniel Shahaf 
Date: Thu, 28 Jun 2018 09:29:06 +
Subject: [PATCH] Bump debhelper dependency to 11.3 and rely on new
 dh_installchangelogs deduplication features. Closes: #902526.

---
 debian/changelog | 2 ++
 debian/control   | 2 +-
 debian/rules | 5 -
 3 files changed, 3 insertions(+), 6 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 233eab7..725c862 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -6,6 +6,8 @@ zsh-syntax-highlighting (0.6.0-1+git) UNRELEASED; urgency=medium
   Debian maintainer and the upstream maintainer are currently the same
   person.)
 + §9.2.3: Patch unit test to use /nonexistent.  No functional change.
+  * Bump debhelper dependency to 11.3 and rely on new dh_installchangelogs
+deduplication features. Closes: #902526.
 
  -- Daniel Shahaf   Wed, 30 Aug 2017 08:06:24 +
 
diff --git a/debian/control b/debian/control
index 16f9a20..4e10b7e 100644
--- a/debian/control
+++ b/debian/control
@@ -4,7 +4,7 @@ Priority: optional
 Maintainer: Debian Zsh Maintainers 
 Uploaders: Daniel Shahaf 
 Build-Depends:
-	debhelper (>= 10),
+	debhelper (>= 11.3),
 	zsh,
 Standards-Version: 4.1.1
 Vcs-Browser: https://anonscm.debian.org/cgit/pkg-zsh/zsh-syntax-highlighting.git/
diff --git a/debian/rules b/debian/rules
index f8e3ec6..76ab9b2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,11 +9,6 @@ override_dh_auto_install:
 	dh_auto_install -- PREFIX=$(PREFIX)
 	rm debian/$(NAME)/usr/share/doc/$(NAME)/COPYING.md
 
-# Remove 'changelog.md' which both upstream and debhelper install to different names
-override_dh_installchangelogs:
-	dh_installchangelogs
-	rm debian/$(NAME)/usr/share/doc/$(NAME)/changelog.md
-
 %:
 	dh $@
 

Bug#902526: [Pkg-zsh-devel] Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Axel Beckert]

Hi Daniel,

Daniel Shahaf wrote:
> Getting a bit ahead of myself, we don't seem to have anywhere to push
> that patch now, since the package's repository was on alioth and hasn't
> been migrated to salsa.  I'll have to look into migrating that.  (Also would
> need to test the patch and tag an 0.6.0-2 that has it.)

Ah, right, I migrated at least the zsh repo, but might have forgotton
to also create the remaining repos on Salsa.

Tell me if you can't create repos under /debian/ (the collab-maint
successor) and I'll create one for you.

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

Bug#871613: general: Kernel Panic caused by smp.c:127 check_preempt_curr

[fran]

Package: general
Followup-For: Bug #871613

Dear Maintainer,

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

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

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



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

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

Bug#890307: tortoisehg: needs update for mercurial 4.6

[Philippe Pepiot]

In case someone want to take over this update, we made a package for
tortoisehg 4.6 (I also sent this to the maintainers few weeks ago).

See attached diff and dsc available at 
https://apt.logilab.fr/pool/main/t/tortoisehg/tortoisehg_4.6-1.dsc

Changes are:

  * update to upstream version 4.6
  * drop compiled pyqt ui files (which are now part of the release on bitbucket)
  * add python-pyqt5.qtsvg as explicit dependency, it's required to have icons 
properly displayed but isn't pulled with --no-install-recommends.


Cheers,
>From c61dcc419ee2a9dc76d32de37bc0610ff96ee94e Mon Sep 17 00:00:00 2001
From: Philippe Pepiot 
Date: Thu, 24 May 2018 11:00:15 +0200
Subject: [PATCH] New upstream version 4.6

---
 debian/changelog | 8 
 debian/control   | 4 ++--
 debian/copyright | 1 +
 3 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index dbce1d0..44a8f6d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+tortoisehg (4.6-1) unstable; urgency=medium
+
+  * New upstream version 4.6
+  * Add explicit dependency on python-pyqt5.qtsvg to have icons working
+  * Exclude qt ui files from orig tarball
+
+ -- Philippe Pepiot   Thu, 24 May 2018 10:59:03 +0200
+
 tortoisehg (4.5.3-1) unstable; urgency=medium
 
   [ Thomas Liebetraut ]
diff --git a/debian/control b/debian/control
index 9d61c5a..7b0290f 100644
--- a/debian/control
+++ b/debian/control
@@ -18,8 +18,8 @@ X-Python-Version: >= 2.4
 
 Package: tortoisehg
 Architecture: all
-Depends: mercurial (>= 4.4~), mercurial (<< 4.6~), python-pyqt5,
- python-pyqt5.qsci, ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
+Depends: mercurial (>= 4.6~), mercurial (<< 4.7~), python-pyqt5,
+ python-pyqt5.qsci, python-pyqt5.qtsvg, ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}
 Recommends: libjs-jquery, libjs-underscore, python-iniparse, python-pygments
 Suggests: tortoisehg-nautilus
 Description: Graphical tool for working with Mercurial
diff --git a/debian/copyright b/debian/copyright
index a96d7c2..77e0433 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -2,6 +2,7 @@ Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: TortoiseHg
 Upstream-Contact: Maintainer: Steve Borho , TK Soh 
 Source: https://tortoisehg.bitbucket.io/download/source.html
+Files-Excluded: tortoisehg/hgqt/*_ui.py
 
 Files: *
 Copyright: 2007-2018, Steve Borho 
-- 
2.11.0

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

[Eric Valette]

  
  


Just a quick note to say that indeed the proposed
patch to look for DRI modules at the right place is working.
However, I have a bunch of other problems since driver update
even with the fix in place:

  Sddm does not start. I get only a black screen
  with the mouse pointer. I have should check but I think I have
  a backtrace that points to qtRenderGlthread that is crashing
  in systemd-nss lib,

  using lightdm and using plasma I'm able to get
  back to my kde environment however the kde setup takes ages to
  start (and I have no more the DRI message in Xorg.0.log),
  The lock screen also takes ages to start,
  black screen for 30s or so with keyboar input or mous move not
  working,

  Launching Kodi, takes 40s but is fluid
  afterwards

  Checked both glxinfo, vdpau info : all normal,


It takes time to start some applications but when
launched it is normally quick. I also had plasmashell crash,
kwin crash, ...
So not currently really usable (after the break
due to udev upgrade failing if systemd was not also updated that
has been since fixed),
-- eric
  
  

Bug#900378: marked as done (glx-alternative-nvidia: Fails to enable proprietary accelerated OpenGL and does not report the problem)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900248: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900248,
regarding glx-alternative-nvidia: Fails to enable proprietary accelerated 
OpenGL and does not report the problem
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.)


-- 
900248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glx-alternative-nvidia
Version: 0.8.3
Severity: normal

Since a dist-upgrade I noticed a poor framerate and high CPU usage in
Minecraft. glxinfo seems to indicate it's using software rendering:

name of display: :1
display: :1  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 6.0, 128 bits) (0x)
Version: 18.0.4
Accelerated: no
...

I think the source of the problem is that the available version of most
of the binary packages of nvidia-graphics-drivers is 390.59-1 but for
libgl1-glvnd-nvidia-glx it's 390.48-3 (can there really be a lag of a
whole day for packages from the same source package to make it into the
archive?) so it can't be installed. But seeing as
glx-alternative-nvidia's main job is to activate the proprietary driver
it should report the problem if it's unable to do that and/or it should
depend on all the packages it needs.

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-lin

Bug#900248: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900248: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900248,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Update to the current version in sid breaks direct rendering, my
system now uses the software pipe:
$ glxinfo | grep OpenGL
...
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
...

Looking at the Xorg.0.log I see
[12.045] (EE) NVIDIA(0): Failed to initialize the GLX module; please check 
in your X
[12.045] (EE) NVIDIA(0): log file that the GLX module has been loaded 
in your X
[12.045] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX 
module.  If
[12.045] (EE) NVIDIA(0): you continue to encounter problems, Please try
[12.045] (EE) NVIDIA(0): reinstalling the NVIDIA driver.

So then I did as root
# # update-glx --config nvidia
There is only one alternative in link group nvidia (providing 
/usr/lib/nvidia/nvidia): /usr/lib/nvidia/current
Nothing to configure.
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for update-glx (0.8.3) ...
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.11
#

and even after reboot nothing has changed.

Best

Norbert


-- Package-specific info:
uname -a:
Linux bulldog 4.16.11 #50 SMP Thu May 24 12:35:27 JST 2018 x86_64 GNU/Linux

/proc/version:
Linux version 4.16.11 (norbert@bulldog) (gcc version 7.3.0 (Debian 7.3.0-19)) 
#50 SMP Thu May 24 12:35:27 JST 2018

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.909202] pci :01:00.0: vgaarb: setting as boot VGA device
[0.909202] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.909202] pci :01:00.0: vgaarb: bridge control possible
[0.909202] vgaarb: loaded
[1.309924] fb0: EFI VGA frame buffer device
[1.470133] Linux agpgart interface v0.103
[1.911353] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[2.728879] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[2.730912] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
[2.733010] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[3.419570] nvidia: loading out-of-tree module taints kernel.
[3.420013] nvidia: module license 'NVIDIA' taints kernel.
[3.429869] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[3.430493] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.430987] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  
9 22:33:42 PDT 2018 (using threaded interrupts)
[3.463770] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.59  Wed May  9 21:59:27 PDT 2018
[3.486333] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.486813] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 0
[   12.697265] nvidia-modeset: Allocated GPU:0 
(GPU-ae45f56a-df50-cbc7-737d-a20dd48d7bdd) @ PCI::01:00.0
[   12.843050] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLAB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   12.843056] Modules linked in: ip6table_filter ip6_tables xt_conntrack 
devlink tun iptable_filter nf_nat nf_conntrack br_netfilter bridge

Bug#900264: marked as done (bzflag is slow since nvidia-graphics-drivers 390.59-1)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900248: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900248,
regarding bzflag is slow since nvidia-graphics-drivers 390.59-1
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.)


-- 
900248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bzflag
Version: 2.4.14-1

Since I upgraded nvidia-graphics-drivers to version 390.59-1, bzflag seems
to prefer libllvm opengl support instead of Nvidia's hardware acceleration.
It says

OpenGL Driver: llvmpipe (LLVM 6.0, 256 bits)

Its unplayable slow.

Other games (e.g. tuxracer) are fine.


Regards
Harri
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.67-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 12:32:19 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglx-nvidia0 libgl1-nvidia-glvnd-glx libgl1-nvidia-glx libnvidia-glcore 
libegl1-nvidia libegl-nvidia0 libgles1-nvidia libgles-nvidia1 libgles2-nvidia 
libgles-nvidia2 libnvidia-eglcore nvidia-egl-common nvidia-egl-icd 
libnvidia-egl-wayland1 nvidia-egl-wayland-common nvidia-egl-wayland-icd 
nvidia-vulkan-common nvidia-vulkan-icd nvidia-nonglvnd-vulkan-common 
nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 nvidia-alternative 
nvidia-kernel-support nvidia-kernel-dkms nvidia-kernel-source 
nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 libcuda1-i386 
libnvidia-compiler libnvidia-fatbinaryloader libnvidia-ptxjitcompiler1 
libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 390.67-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libegl-nvidia0 - NVIDIA binary EGL library
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND variant)
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND variant)
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND variant)
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library (transitional)
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library (transitional)
 libglx-nvidia0 - NVIDIA binary GLX library
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-egl-wayland1 - NVIDIA binary Wayland EGL external platform library
 libnvidia-eglcore - NVIDIA binary EGL core libraries
 libnvidia-encode1 - NVENC Video Encoding runtime library
 libnvidia-fatbinaryloader - NVIDIA FAT binary loader
 libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
 libnvidia-glcore - NVIDIA binary OpenGL/GLX core libraries
 libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
 libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-ptxjitcompiler1 - NVIDIA PTX JIT Compiler
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-driver - NVIDIA metapackage
 nvidia-driver-bin - NVIDIA driver support binaries
 nvidia-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
 nvidia-

Bug#900766: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900248: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900248,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading Debian Sid nvidia-driver from  Version: 390.48-3 to Version:
390.59-1
nvidia-driver 390.59-1 breaks direct rendering

Creating /usr/share/X11/xorg.conf.d/xorg.conf containing:

Section "OutputClass"
Identifier  "Nvidia Modules"
MatchDriver "nvidia-drm"
Driver  "nvidia"
Option  "AllowEmptyInitialConfiguration" "true"
ModulePath  "/usr/lib/nvidia"
EndSection

with original files in place as suggested by Luca Boccassi works for me

uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
GNU/Linux

glxinfo:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4




-- Package-specific info:
uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 
GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-21) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2765]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jun  4  2018 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jun  4  2018 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jun  4  2018 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jun  4  2018 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jun  4  2018 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jun  4  2018 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jun  4  2018 pci-:01:00.0-render -> ../renderD128
video:x:44:grash,motion,boinc

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 1952 Jul 23  2016 /etc/X11/xorg (copy).conf
-rw-r--r-- 1 root root 2134 Sep 14  2017 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Jun  2 18:54 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Jan 14 17:48 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   51 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 Jan 14 17:48 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwx

Bug#900378: marked as done (glx-alternative-nvidia: Fails to enable proprietary accelerated OpenGL and does not report the problem)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900264: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900264,
regarding glx-alternative-nvidia: Fails to enable proprietary accelerated 
OpenGL and does not report the problem
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.)


-- 
900264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glx-alternative-nvidia
Version: 0.8.3
Severity: normal

Since a dist-upgrade I noticed a poor framerate and high CPU usage in
Minecraft. glxinfo seems to indicate it's using software rendering:

name of display: :1
display: :1  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 6.0, 128 bits) (0x)
Version: 18.0.4
Accelerated: no
...

I think the source of the problem is that the available version of most
of the binary packages of nvidia-graphics-drivers is 390.59-1 but for
libgl1-glvnd-nvidia-glx it's 390.48-3 (can there really be a lag of a
whole day for packages from the same source package to make it into the
archive?) so it can't be installed. But seeing as
glx-alternative-nvidia's main job is to activate the proprietary driver
it should report the problem if it's unable to do that and/or it should
depend on all the packages it needs.

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-lin

Bug#900264: marked as done (bzflag is slow since nvidia-graphics-drivers 390.59-1)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900264: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900264,
regarding bzflag is slow since nvidia-graphics-drivers 390.59-1
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.)


-- 
900264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bzflag
Version: 2.4.14-1

Since I upgraded nvidia-graphics-drivers to version 390.59-1, bzflag seems
to prefer libllvm opengl support instead of Nvidia's hardware acceleration.
It says

OpenGL Driver: llvmpipe (LLVM 6.0, 256 bits)

Its unplayable slow.

Other games (e.g. tuxracer) are fine.


Regards
Harri
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.67-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 12:32:19 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglx-nvidia0 libgl1-nvidia-glvnd-glx libgl1-nvidia-glx libnvidia-glcore 
libegl1-nvidia libegl-nvidia0 libgles1-nvidia libgles-nvidia1 libgles2-nvidia 
libgles-nvidia2 libnvidia-eglcore nvidia-egl-common nvidia-egl-icd 
libnvidia-egl-wayland1 nvidia-egl-wayland-common nvidia-egl-wayland-icd 
nvidia-vulkan-common nvidia-vulkan-icd nvidia-nonglvnd-vulkan-common 
nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 nvidia-alternative 
nvidia-kernel-support nvidia-kernel-dkms nvidia-kernel-source 
nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 libcuda1-i386 
libnvidia-compiler libnvidia-fatbinaryloader libnvidia-ptxjitcompiler1 
libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 390.67-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libegl-nvidia0 - NVIDIA binary EGL library
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND variant)
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND variant)
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND variant)
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library (transitional)
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library (transitional)
 libglx-nvidia0 - NVIDIA binary GLX library
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-egl-wayland1 - NVIDIA binary Wayland EGL external platform library
 libnvidia-eglcore - NVIDIA binary EGL core libraries
 libnvidia-encode1 - NVENC Video Encoding runtime library
 libnvidia-fatbinaryloader - NVIDIA FAT binary loader
 libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
 libnvidia-glcore - NVIDIA binary OpenGL/GLX core libraries
 libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
 libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-ptxjitcompiler1 - NVIDIA PTX JIT Compiler
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-driver - NVIDIA metapackage
 nvidia-driver-bin - NVIDIA driver support binaries
 nvidia-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
 nvidia-

Bug#900248: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900264: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900264,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Update to the current version in sid breaks direct rendering, my
system now uses the software pipe:
$ glxinfo | grep OpenGL
...
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
...

Looking at the Xorg.0.log I see
[12.045] (EE) NVIDIA(0): Failed to initialize the GLX module; please check 
in your X
[12.045] (EE) NVIDIA(0): log file that the GLX module has been loaded 
in your X
[12.045] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX 
module.  If
[12.045] (EE) NVIDIA(0): you continue to encounter problems, Please try
[12.045] (EE) NVIDIA(0): reinstalling the NVIDIA driver.

So then I did as root
# # update-glx --config nvidia
There is only one alternative in link group nvidia (providing 
/usr/lib/nvidia/nvidia): /usr/lib/nvidia/current
Nothing to configure.
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for update-glx (0.8.3) ...
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.11
#

and even after reboot nothing has changed.

Best

Norbert


-- Package-specific info:
uname -a:
Linux bulldog 4.16.11 #50 SMP Thu May 24 12:35:27 JST 2018 x86_64 GNU/Linux

/proc/version:
Linux version 4.16.11 (norbert@bulldog) (gcc version 7.3.0 (Debian 7.3.0-19)) 
#50 SMP Thu May 24 12:35:27 JST 2018

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.909202] pci :01:00.0: vgaarb: setting as boot VGA device
[0.909202] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.909202] pci :01:00.0: vgaarb: bridge control possible
[0.909202] vgaarb: loaded
[1.309924] fb0: EFI VGA frame buffer device
[1.470133] Linux agpgart interface v0.103
[1.911353] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[2.728879] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[2.730912] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
[2.733010] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[3.419570] nvidia: loading out-of-tree module taints kernel.
[3.420013] nvidia: module license 'NVIDIA' taints kernel.
[3.429869] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[3.430493] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.430987] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  
9 22:33:42 PDT 2018 (using threaded interrupts)
[3.463770] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.59  Wed May  9 21:59:27 PDT 2018
[3.486333] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.486813] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 0
[   12.697265] nvidia-modeset: Allocated GPU:0 
(GPU-ae45f56a-df50-cbc7-737d-a20dd48d7bdd) @ PCI::01:00.0
[   12.843050] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLAB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   12.843056] Modules linked in: ip6table_filter ip6_tables xt_conntrack 
devlink tun iptable_filter nf_nat nf_conntrack br_netfilter bridge

Bug#900378: marked as done (glx-alternative-nvidia: Fails to enable proprietary accelerated OpenGL and does not report the problem)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900378: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900378,
regarding glx-alternative-nvidia: Fails to enable proprietary accelerated 
OpenGL and does not report the problem
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.)


-- 
900378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glx-alternative-nvidia
Version: 0.8.3
Severity: normal

Since a dist-upgrade I noticed a poor framerate and high CPU usage in
Minecraft. glxinfo seems to indicate it's using software rendering:

name of display: :1
display: :1  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 6.0, 128 bits) (0x)
Version: 18.0.4
Accelerated: no
...

I think the source of the problem is that the available version of most
of the binary packages of nvidia-graphics-drivers is 390.59-1 but for
libgl1-glvnd-nvidia-glx it's 390.48-3 (can there really be a lag of a
whole day for packages from the same source package to make it into the
archive?) so it can't be installed. But seeing as
glx-alternative-nvidia's main job is to activate the proprietary driver
it should report the problem if it's unable to do that and/or it should
depend on all the packages it needs.

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-lin

Bug#900248: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900378: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900378,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Update to the current version in sid breaks direct rendering, my
system now uses the software pipe:
$ glxinfo | grep OpenGL
...
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
...

Looking at the Xorg.0.log I see
[12.045] (EE) NVIDIA(0): Failed to initialize the GLX module; please check 
in your X
[12.045] (EE) NVIDIA(0): log file that the GLX module has been loaded 
in your X
[12.045] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX 
module.  If
[12.045] (EE) NVIDIA(0): you continue to encounter problems, Please try
[12.045] (EE) NVIDIA(0): reinstalling the NVIDIA driver.

So then I did as root
# # update-glx --config nvidia
There is only one alternative in link group nvidia (providing 
/usr/lib/nvidia/nvidia): /usr/lib/nvidia/current
Nothing to configure.
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for update-glx (0.8.3) ...
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.11
#

and even after reboot nothing has changed.

Best

Norbert


-- Package-specific info:
uname -a:
Linux bulldog 4.16.11 #50 SMP Thu May 24 12:35:27 JST 2018 x86_64 GNU/Linux

/proc/version:
Linux version 4.16.11 (norbert@bulldog) (gcc version 7.3.0 (Debian 7.3.0-19)) 
#50 SMP Thu May 24 12:35:27 JST 2018

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.909202] pci :01:00.0: vgaarb: setting as boot VGA device
[0.909202] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.909202] pci :01:00.0: vgaarb: bridge control possible
[0.909202] vgaarb: loaded
[1.309924] fb0: EFI VGA frame buffer device
[1.470133] Linux agpgart interface v0.103
[1.911353] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[2.728879] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[2.730912] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
[2.733010] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[3.419570] nvidia: loading out-of-tree module taints kernel.
[3.420013] nvidia: module license 'NVIDIA' taints kernel.
[3.429869] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[3.430493] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.430987] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  
9 22:33:42 PDT 2018 (using threaded interrupts)
[3.463770] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.59  Wed May  9 21:59:27 PDT 2018
[3.486333] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.486813] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 0
[   12.697265] nvidia-modeset: Allocated GPU:0 
(GPU-ae45f56a-df50-cbc7-737d-a20dd48d7bdd) @ PCI::01:00.0
[   12.843050] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLAB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   12.843056] Modules linked in: ip6table_filter ip6_tables xt_conntrack 
devlink tun iptable_filter nf_nat nf_conntrack br_netfilter bridge

Bug#900378: marked as done (glx-alternative-nvidia: Fails to enable proprietary accelerated OpenGL and does not report the problem)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900766: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900766,
regarding glx-alternative-nvidia: Fails to enable proprietary accelerated 
OpenGL and does not report the problem
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.)


-- 
900766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: glx-alternative-nvidia
Version: 0.8.3
Severity: normal

Since a dist-upgrade I noticed a poor framerate and high CPU usage in
Minecraft. glxinfo seems to indicate it's using software rendering:

name of display: :1
display: :1  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
...
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0x)
Device: llvmpipe (LLVM 6.0, 128 bits) (0x)
Version: 18.0.4
Accelerated: no
...

I think the source of the problem is that the available version of most
of the binary packages of nvidia-graphics-drivers is 390.59-1 but for
libgl1-glvnd-nvidia-glx it's 390.48-3 (can there really be a lag of a
whole day for packages from the same source package to make it into the
archive?) so it can't be installed. But seeing as
glx-alternative-nvidia's main job is to activate the proprietary driver
it should report the problem if it's unable to do that and/or it should
depend on all the packages it needs.

-- Package-specific info:
Diversions:
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.1.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv1_CM.so.1.2.0 by 
glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.0.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.0.0 by glx-diversions
diversion of /usr/lib/arm-linux-gnueabihf/libGLESv2.so.2.1.0 to 
/usr/lib/mesa-diverted/arm-linux-gnueabihf/libGLESv2.so.2.1.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.0.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.0.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.2.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGL.so.1.7.0 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.7.0 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1 to 
/usr/lib/mesa-diverted/i386-linux-gnu/libGLESv1_CM.so.1 by glx-diversions
diversion of /usr/lib/i386-linux-gnu/libGLESv1_CM.so.1.1.0 to 
/usr/lib/mesa-diverted/i386-lin

Bug#900766: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900378: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900378,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading Debian Sid nvidia-driver from  Version: 390.48-3 to Version:
390.59-1
nvidia-driver 390.59-1 breaks direct rendering

Creating /usr/share/X11/xorg.conf.d/xorg.conf containing:

Section "OutputClass"
Identifier  "Nvidia Modules"
MatchDriver "nvidia-drm"
Driver  "nvidia"
Option  "AllowEmptyInitialConfiguration" "true"
ModulePath  "/usr/lib/nvidia"
EndSection

with original files in place as suggested by Luca Boccassi works for me

uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
GNU/Linux

glxinfo:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4




-- Package-specific info:
uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 
GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-21) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2765]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jun  4  2018 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jun  4  2018 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jun  4  2018 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jun  4  2018 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jun  4  2018 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jun  4  2018 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jun  4  2018 pci-:01:00.0-render -> ../renderD128
video:x:44:grash,motion,boinc

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 1952 Jul 23  2016 /etc/X11/xorg (copy).conf
-rw-r--r-- 1 root root 2134 Sep 14  2017 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Jun  2 18:54 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Jan 14 17:48 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   51 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 Jan 14 17:48 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwx

Bug#900248: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900766: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900766,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Update to the current version in sid breaks direct rendering, my
system now uses the software pipe:
$ glxinfo | grep OpenGL
...
OpenGL renderer string: llvmpipe (LLVM 6.0, 256 bits)
...

Looking at the Xorg.0.log I see
[12.045] (EE) NVIDIA(0): Failed to initialize the GLX module; please check 
in your X
[12.045] (EE) NVIDIA(0): log file that the GLX module has been loaded 
in your X
[12.045] (EE) NVIDIA(0): server, and that the module is the NVIDIA GLX 
module.  If
[12.045] (EE) NVIDIA(0): you continue to encounter problems, Please try
[12.045] (EE) NVIDIA(0): reinstalling the NVIDIA driver.

So then I did as root
# # update-glx --config nvidia
There is only one alternative in link group nvidia (providing 
/usr/lib/nvidia/nvidia): /usr/lib/nvidia/current
Nothing to configure.
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for update-glx (0.8.3) ...
Processing triggers for glx-alternative-nvidia (0.8.3) ...
Processing triggers for libc-bin (2.27-3) ...
Processing triggers for initramfs-tools (0.130) ...
update-initramfs: Generating /boot/initrd.img-4.16.11
#

and even after reboot nothing has changed.

Best

Norbert


-- Package-specific info:
uname -a:
Linux bulldog 4.16.11 #50 SMP Thu May 24 12:35:27 JST 2018 x86_64 GNU/Linux

/proc/version:
Linux version 4.16.11 (norbert@bulldog) (gcc version 7.3.0 (Debian 7.3.0-19)) 
#50 SMP Thu May 24 12:35:27 JST 2018

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-19) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:11bf]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.909202] pci :01:00.0: vgaarb: setting as boot VGA device
[0.909202] pci :01:00.0: vgaarb: VGA device added: 
decodes=io+mem,owns=io+mem,locks=none
[0.909202] pci :01:00.0: vgaarb: bridge control possible
[0.909202] vgaarb: loaded
[1.309924] fb0: EFI VGA frame buffer device
[1.470133] Linux agpgart interface v0.103
[1.911353] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[2.728879] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input14
[2.730912] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input15
[2.733010] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:01.0/:01:00.1/sound/card1/input16
[3.419570] nvidia: loading out-of-tree module taints kernel.
[3.420013] nvidia: module license 'NVIDIA' taints kernel.
[3.429869] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[3.430493] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
[3.430987] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  
9 22:33:42 PDT 2018 (using threaded interrupts)
[3.463770] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.59  Wed May  9 21:59:27 PDT 2018
[3.486333] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
[3.486813] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 on 
minor 0
[   12.697265] nvidia-modeset: Allocated GPU:0 
(GPU-ae45f56a-df50-cbc7-737d-a20dd48d7bdd) @ PCI::01:00.0
[   12.843050] Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLAB object 'nvidia_stack_cache' (offset 11440, size 3)!
[   12.843056] Modules linked in: ip6table_filter ip6_tables xt_conntrack 
devlink tun iptable_filter nf_nat nf_conntrack br_netfilter bridge

Bug#900264: marked as done (bzflag is slow since nvidia-graphics-drivers 390.59-1)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900766: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900766,
regarding bzflag is slow since nvidia-graphics-drivers 390.59-1
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.)


-- 
900766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bzflag
Version: 2.4.14-1

Since I upgraded nvidia-graphics-drivers to version 390.59-1, bzflag seems
to prefer libllvm opengl support instead of Nvidia's hardware acceleration.
It says

OpenGL Driver: llvmpipe (LLVM 6.0, 256 bits)

Its unplayable slow.

Other games (e.g. tuxracer) are fine.


Regards
Harri
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.67-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 12:32:19 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglx-nvidia0 libgl1-nvidia-glvnd-glx libgl1-nvidia-glx libnvidia-glcore 
libegl1-nvidia libegl-nvidia0 libgles1-nvidia libgles-nvidia1 libgles2-nvidia 
libgles-nvidia2 libnvidia-eglcore nvidia-egl-common nvidia-egl-icd 
libnvidia-egl-wayland1 nvidia-egl-wayland-common nvidia-egl-wayland-icd 
nvidia-vulkan-common nvidia-vulkan-icd nvidia-nonglvnd-vulkan-common 
nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 nvidia-alternative 
nvidia-kernel-support nvidia-kernel-dkms nvidia-kernel-source 
nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 libcuda1-i386 
libnvidia-compiler libnvidia-fatbinaryloader libnvidia-ptxjitcompiler1 
libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 390.67-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libegl-nvidia0 - NVIDIA binary EGL library
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND variant)
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND variant)
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND variant)
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library (transitional)
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library (transitional)
 libglx-nvidia0 - NVIDIA binary GLX library
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-egl-wayland1 - NVIDIA binary Wayland EGL external platform library
 libnvidia-eglcore - NVIDIA binary EGL core libraries
 libnvidia-encode1 - NVENC Video Encoding runtime library
 libnvidia-fatbinaryloader - NVIDIA FAT binary loader
 libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
 libnvidia-glcore - NVIDIA binary OpenGL/GLX core libraries
 libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
 libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-ptxjitcompiler1 - NVIDIA PTX JIT Compiler
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-driver - NVIDIA metapackage
 nvidia-driver-bin - NVIDIA driver support binaries
 nvidia-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
 nvidia-

Bug#900766: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900264: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900264,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading Debian Sid nvidia-driver from  Version: 390.48-3 to Version:
390.59-1
nvidia-driver 390.59-1 breaks direct rendering

Creating /usr/share/X11/xorg.conf.d/xorg.conf containing:

Section "OutputClass"
Identifier  "Nvidia Modules"
MatchDriver "nvidia-drm"
Driver  "nvidia"
Option  "AllowEmptyInitialConfiguration" "true"
ModulePath  "/usr/lib/nvidia"
EndSection

with original files in place as suggested by Luca Boccassi works for me

uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
GNU/Linux

glxinfo:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4




-- Package-specific info:
uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 
GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-21) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2765]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jun  4  2018 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jun  4  2018 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jun  4  2018 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jun  4  2018 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jun  4  2018 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jun  4  2018 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jun  4  2018 pci-:01:00.0-render -> ../renderD128
video:x:44:grash,motion,boinc

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 1952 Jul 23  2016 /etc/X11/xorg (copy).conf
-rw-r--r-- 1 root root 2134 Sep 14  2017 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Jun  2 18:54 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Jan 14 17:48 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   51 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 Jan 14 17:48 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwx

Bug#900264: marked as done (bzflag is slow since nvidia-graphics-drivers 390.59-1)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900378: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900378,
regarding bzflag is slow since nvidia-graphics-drivers 390.59-1
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.)


-- 
900378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bzflag
Version: 2.4.14-1

Since I upgraded nvidia-graphics-drivers to version 390.59-1, bzflag seems
to prefer libllvm opengl support instead of Nvidia's hardware acceleration.
It says

OpenGL Driver: llvmpipe (LLVM 6.0, 256 bits)

Its unplayable slow.

Other games (e.g. tuxracer) are fine.


Regards
Harri
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.67-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 12:32:19 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglx-nvidia0 libgl1-nvidia-glvnd-glx libgl1-nvidia-glx libnvidia-glcore 
libegl1-nvidia libegl-nvidia0 libgles1-nvidia libgles-nvidia1 libgles2-nvidia 
libgles-nvidia2 libnvidia-eglcore nvidia-egl-common nvidia-egl-icd 
libnvidia-egl-wayland1 nvidia-egl-wayland-common nvidia-egl-wayland-icd 
nvidia-vulkan-common nvidia-vulkan-icd nvidia-nonglvnd-vulkan-common 
nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 nvidia-alternative 
nvidia-kernel-support nvidia-kernel-dkms nvidia-kernel-source 
nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 libcuda1-i386 
libnvidia-compiler libnvidia-fatbinaryloader libnvidia-ptxjitcompiler1 
libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 390.67-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 libegl-nvidia0 - NVIDIA binary EGL library
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND variant)
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND variant)
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND variant)
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library (transitional)
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library (transitional)
 libglx-nvidia0 - NVIDIA binary GLX library
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration library
 libnvidia-compiler - NVIDIA runtime compiler library
 libnvidia-egl-wayland1 - NVIDIA binary Wayland EGL external platform library
 libnvidia-eglcore - NVIDIA binary EGL core libraries
 libnvidia-encode1 - NVENC Video Encoding runtime library
 libnvidia-fatbinaryloader - NVIDIA FAT binary loader
 libnvidia-fbc1 - NVIDIA OpenGL-based Framebuffer Capture runtime library
 libnvidia-glcore - NVIDIA binary OpenGL/GLX core libraries
 libnvidia-ifr1 - NVIDIA OpenGL-based Inband Frame Readback runtime library
 libnvidia-ml1 - NVIDIA Management Library (NVML) runtime library
 libnvidia-ptxjitcompiler1 - NVIDIA PTX JIT Compiler
 nvidia-alternative - allows the selection of NVIDIA as GLX provider
 nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
 nvidia-detect - NVIDIA GPU detection utility
 nvidia-driver - NVIDIA metapackage
 nvidia-driver-bin - NVIDIA driver support binaries
 nvidia-driver-libs - NVIDIA metapackage (OpenGL/GLX/EGL/GLES libraries)
 nvidia-

Bug#900766: marked as done (nvidia-driver: update to 390.59 breaks direct rendering)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 11:19:30 +
with message-id 
and subject line Bug#900766: fixed in nvidia-graphics-drivers 390.67-1
has caused the Debian Bug report #900766,
regarding nvidia-driver: update to 390.59 breaks direct rendering
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.)


-- 
900766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.59-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading Debian Sid nvidia-driver from  Version: 390.48-3 to Version:
390.59-1
nvidia-driver 390.59-1 breaks direct rendering

Creating /usr/share/X11/xorg.conf.d/xorg.conf containing:

Section "OutputClass"
Identifier  "Nvidia Modules"
MatchDriver "nvidia-drm"
Driver  "nvidia"
Option  "AllowEmptyInitialConfiguration" "true"
ModulePath  "/usr/lib/nvidia"
EndSection

with original files in place as suggested by Luca Boccassi works for me

uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64
GNU/Linux

glxinfo:
name of display: :0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4




-- Package-specific info:
uname -a:
Linux garypc 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 
GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-21) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK104 [GeForce GTX 
760] [10de:1187] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GK104 [GeForce GTX 760] [3842:2765]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jun  4  2018 /dev/dri/card0
crw-rw+ 1 root video 226, 128 Jun  4  2018 /dev/dri/renderD128
crw-rw-rw-  1 root root  195, 254 Jun  4  2018 /dev/nvidia-modeset
crw-rw-rw-  1 root root  195,   0 Jun  4  2018 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jun  4  2018 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 Jun  4  2018 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 Jun  4  2018 pci-:01:00.0-render -> ../renderD128
video:x:44:grash,motion,boinc

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root root 1952 Jul 23  2016 /etc/X11/xorg (copy).conf
-rw-r--r-- 1 root root 2134 Sep 14  2017 /etc/X11/xorg.conf
lrwxrwxrwx 1 root root   15 Jun  2 18:54 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 Jan 14 17:48 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   49 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   51 Jun  2 18:54 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jan 14 17:48 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   48 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 Jun  2 18:54 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 Jan 14 17:48 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwx

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

[Andreas Beckmann]

On 2018-06-28 12:54, Eric Valette wrote:
> 
> Just a quick note to say that indeed the proposed patch to look for DRI 
> modules 
> at the right place is working. However, I have a bunch of other problems 
> since 
> driver update even with the fix in place:

I just uploaded 390.67-1 - if your issues are still reproducible with
that version, please file a new bug.


Andreas

Bug#902526: [Pkg-zsh-devel] Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Daniel Shahaf]

Axel Beckert wrote on Thu, 28 Jun 2018 12:11 +0200:
> Tell me if you can't create repos under /debian/ (the collab-maint
> successor) and I'll create one for you.

Indeed I can't; I can sign in to salsa but even then I have read-only
access to salsa.d.o/debian/.  Could you please create a z-sy-h
repository and give me push access thereto?  I can take care of populating
the empty clone with the preexisting history (planning to download the
tar.xz from alioth-archive.d.o and 'git push --mirror' to salsa).

Thanks,

Daniel

Bug#902526: [Pkg-zsh-devel] Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Axel Beckert]

Hi Daniel,

Daniel Shahaf wrote:
> Axel Beckert wrote on Thu, 28 Jun 2018 12:11 +0200:
> > Tell me if you can't create repos under /debian/ (the collab-maint
> > successor) and I'll create one for you.
> 
> Indeed I can't; I can sign in to salsa but even then I have read-only
> access to salsa.d.o/debian/.  Could you please create a z-sy-h
> repository and give me push access thereto?

Done: https://salsa.debian.org/debian/zsh-syntax-highlighting

> I can take care of populating the empty clone with the preexisting
> history (planning to download the tar.xz from alioth-archive.d.o and
> 'git push --mirror' to salsa).

Thanks!

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

Processed: Re: Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Debian Bug Tracking System]

Processing control commands:

> affects 901771 src:gtkdataboxmm src:libgtkdatabox src:osm-gps-map 
> src:sugar-toolkit-gtk3 src:fontforge
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Added indication that 901771 affects src:gtkdataboxmm, src:libgtkdatabox, 
src:osm-gps-map, src:sugar-toolkit-gtk3, and src:fontforge
> severity 901771 serious
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Severity set to 'serious' from 'normal'
> tags 901771 + patch
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Added tag(s) patch.

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

Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Simon McVittie]

Control: affects 901771 src:gtkdataboxmm src:libgtkdatabox src:osm-gps-map 
src:sugar-toolkit-gtk3 src:fontforge
Control: severity 901771 serious
Control: tags 901771 + patch

On Thu, 19 Apr 2018 at 23:56:18 -0400, Jeremy Bicha wrote:
> The build itself completes fine. If pango were broken, I'd expect a
> lot more bug reports.
> 
> But it's the d-shlibmove command that fails. Note this line in the build log:
> 
> > devlibs error: There is no package matching [libfribidi0-dev] and noone
> > provides it, please report bug to d-shlibs maintainer

On Fri, 20 Apr 2018 at 09:09:12 +0300, Adrian Bunk wrote:
> d-devlibdeps basically contains a manual mapping to the -dev packages 
> in such cases, this is horribly fragile.

I was about to clone this bug to d-shlibs, because that's clearly a bug
in d-shlibs, orthogonal to whether anything is wrong with pango1.0; but
 was reported
in the meantime, so let's use that one instead.

I'm escalating #901771 to RC, because d-shlibs is clearly
not helping here, and the solution is trivial; see attached
0001-Add-quirk-for-libfribidi-dev.patch, which I have confirmed fixes the
build of src:libgtkdatabox (patches also on the way for the existing RC
bug #897539). I've also opened a bug suggesting that d-devlibdeps should
be deprecated.

> In this specific case the root problem is that using pango results in 
> needlessly linking with libfribidi, which can also become annoying for
> transitions.
> 
> This would otherwise not be a FTBFS-causing RC bug, but it is an easily 
> fixable bug that should be fixed.

Normally, I'd say fribidi should be moved from Requires
to Requires.private (or the Requires.internal proposed on
, but that doesn't
exist yet) to resolve this while not breaking static linking; and I'd
also say we should augment debian/tests/build to exercise static linking,
to prove that that can still work.

However, libfribidi in Debian doesn't provide a static library
any more, so static linking can't actually work anyway. I've asked
fribidi upstream whether they intend to be only supporting shared
linking, or whether their change of defaults was misinterpreted by
the Debian maintainer of fribidi as having been a policy change:
https://github.com/fribidi/fribidi/issues/83

Either moving this dependency from Requires to Requires.private or
removing it altogether is clearly an improvement, so I think we should
do one or the other, and I'm very tempted to pick one arbitrarily and
JFDI, with the intention of swapping to the other if the result of
fribidi#83 indicates that the opposite would be better.

smcv

Processed: Re: Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Debian Bug Tracking System]

Processing control commands:

> affects 901771 src:gtkdataboxmm src:libgtkdatabox src:osm-gps-map 
> src:sugar-toolkit-gtk3 src:fontforge
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Ignoring request to set affects of bug 901771 to the same value previously set
> severity 901771 serious
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Ignoring request to change severity of Bug 901771 to the same value.
> tags 901771 + patch
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Ignoring request to alter tags of bug #901771 to the same tags previously set

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

Bug#902526: [Pkg-zsh-devel] Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Daniel Shahaf]

Axel Beckert wrote on Thu, Jun 28, 2018 at 13:47:38 +0200:
> Daniel Shahaf wrote:
> > Axel Beckert wrote on Thu, 28 Jun 2018 12:11 +0200:
> > > Tell me if you can't create repos under /debian/ (the collab-maint
> > > successor) and I'll create one for you.
> > 
> > Indeed I can't; I can sign in to salsa but even then I have read-only
> > access to salsa.d.o/debian/.  Could you please create a z-sy-h
> > repository and give me push access thereto?
> 
> Done: https://salsa.debian.org/debian/zsh-syntax-highlighting
> 

Thanks!

> > I can take care of populating the empty clone with the preexisting
> > history (planning to download the tar.xz from alioth-archive.d.o and
> > 'git push --mirror' to salsa).
> 
> Thanks!

Done: https://salsa.debian.org/debian/zsh-syntax-highlighting

>

:-)

Daniel

Bug#897539: d-shlibs: FTBFS: shellcheck errors

[Simon McVittie]

Control: tags -1 + patch

On Wed, 02 May 2018 at 22:56:36 +0200, Lucas Nussbaum wrote:
> > shellcheck d-shlibmove
> > 
> > In d-shlibmove line 243:
> > sed -i -e "/^.*\.la usr\/lib || true$/d" "$INSTALLFILE_DEVPKG"
> >^-- SC1117: Backslash is literal in "\.". Prefer 
> > explicit escaping: "\\.".
> >^-- SC1117: Backslash is literal in "\/". 
> > Prefer explicit escaping: "\\/".
(etc.)

I don't think packages should run shellcheck and similar linting tools
at build time and make warnings fatal: it's just too fragile when the
linting tool is improved to detect additional lint. Maintainers are
welcome to run these tools and use them to improve their code, but that
should be a maintainer step, not a build-time step.

However, this did at least find a real bug: d-shlibdeps didn't implement
"--" as it appeared to be intended to.

Patches attached.

Regards,
smcv
>From 6b320e56473e7dc538fed0e80ae81ef35589cc1f Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 28 Jun 2018 12:39:04 +0100
Subject: [PATCH 2/4] d-devlibdeps: Parse -- with its conventional meaning

This appears to have always been intended, but shellcheck indicated
that the precedence was wrong, causing it to be parsed as an unknown
option instead.

Part of #897539.
---
 d-devlibdeps | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/d-devlibdeps b/d-devlibdeps
index e805491..dab5d92 100755
--- a/d-devlibdeps
+++ b/d-devlibdeps
@@ -242,11 +242,15 @@ while true; do
 		OVERRIDE[${#OVERRIDE[@]}]="$2"
 		shift 2
 		;;
+	  --)
+		shift
+		break
+		;;
 	  --*)
 		echo "$0: Unknown option $1" > /dev/stderr
 		exit 64 # EX_USAGE: command line usage error
 		;;
-	  --|*)
+	  *)
 		break
 		;;
 esac
-- 
2.18.0

>From a423c0a4346b415fd0134bb95773e2a7d3a16cb2 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 28 Jun 2018 12:23:03 +0100
Subject: [PATCH 3/4] Fix remaining shellcheck warnings

Closes: #897539
---
 d-devlibdeps | 2 +-
 d-shlibmove  | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/d-devlibdeps b/d-devlibdeps
index dab5d92..9e57d96 100755
--- a/d-devlibdeps
+++ b/d-devlibdeps
@@ -294,7 +294,7 @@ outputtmp=$(mktemp)
 		fi
 	done \
 	| sed -e 's/\([a-z0-9)]\) \+\([a-z]\)/\1, \2/g' -e 's/ \+/ /g' -e 's/^ //' -e 's/ $//'
-	printf "\n"
+	printf '\n'
 ) > "$outputtmp"
 
 if grep "ERROR_DEVLIB" "$outputtmp" > /dev/null; then
diff --git a/d-shlibmove b/d-shlibmove
index 6d1909d..bbb1295 100755
--- a/d-shlibmove
+++ b/d-shlibmove
@@ -240,7 +240,7 @@ while read -r A B; do
 	echo "mv $A debian/$PKGSHL/$B" >> "$execscript"
 done < "$INSTALLFILE_SHLPKG"
 if [ "$INCLUDELA" = "no" ]; then
-	sed -i -e "/^.*\.la usr\/lib || true$/d" "$INSTALLFILE_DEVPKG"
+	sed -i -e '/^.*\.la usr\/lib || true$/d' "$INSTALLFILE_DEVPKG"
 fi
 while read -r A B; do
 	echo "$INSTALLDIR debian/$PKGDEV/$B" >> "$execscript"
@@ -248,7 +248,7 @@ while read -r A B; do
 done < "$INSTALLFILE_DEVPKG"
 
 if [ "$MULTIARCH" = "yes" ]; then
-	sed -i -e "s/usr\/lib\( || true\)\?$/usr\/lib\/$DEB_HOST_MULTIARCH\1/" "$execscript"
+	sed -i -e "s/usr\\/lib\\( || true\\)\\?$/usr\\/lib\\/$DEB_HOST_MULTIARCH\\1/" "$execscript"
 fi
 
 cat "$execscript"
@@ -267,7 +267,7 @@ fi
 if [ -n "$TRANSITIONSUFFIX" ]; then
 	check_line "$PKGSHL" "Conflicts: $SONAMEPKGNAME$SUFFIX"
 fi
-check_line "$PKGDEV" "Section: \(devel\|libdevel\)"
+check_line "$PKGDEV" 'Section: \(devel\|libdevel\)'
 if ! [ "$IGNORELIBDEP" = "yes" ]; then
 	check_line "$PKGDEV" "Depends:.*$PKGSHL"
 fi
-- 
2.18.0

Processed: bug 901771 is forwarded to https://salsa.debian.org/debian/d-shlibs/merge_requests/2

[Debian Bug Tracking System]

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

> forwarded 901771 https://salsa.debian.org/debian/d-shlibs/merge_requests/2
Bug #901771 [d-shlibs] [d-shlibs] Include override of libfribidi0-dev to 
libfribidi-dev
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/d-shlibs/merge_requests/2'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#897539: d-shlibs: FTBFS: shellcheck errors

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #897539 [src:d-shlibs] d-shlibs: FTBFS: shellcheck errors
Added tag(s) patch.

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

Processed: bug 897539 is forwarded to https://salsa.debian.org/debian/d-shlibs/merge_requests/3

[Debian Bug Tracking System]

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

> forwarded 897539 https://salsa.debian.org/debian/d-shlibs/merge_requests/3
Bug #897539 [src:d-shlibs] d-shlibs: FTBFS: shellcheck errors
Set Bug forwarded-to-address to 
'https://salsa.debian.org/debian/d-shlibs/merge_requests/3'.
> thanks
Stopping processing here.

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

Bug#901771: Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

[Simon McVittie]

On Thu, 28 Jun 2018 at 13:01:37 +0100, Simon McVittie wrote:
> I'm escalating #901771 to RC, because d-shlibs is clearly
> not helping here, and the solution is trivial; see attached
> 0001-Add-quirk-for-libfribidi-dev.patch, which I have confirmed fixes the
> build of src:libgtkdatabox

Sorry, here's that patch. Also available from
https://salsa.debian.org/debian/d-shlibs/merge_requests/2

smcv
>From 52a1ecd72ba4205764e9c1441f464881c2608e6d Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Thu, 28 Jun 2018 12:00:26 +0100
Subject: [PATCH 1/4] Add quirk for libfribidi-dev

Closes: #901771
---
 d-devlibdeps | 1 +
 1 file changed, 1 insertion(+)

diff --git a/d-devlibdeps b/d-devlibdeps
index 71fffa1..e805491 100755
--- a/d-devlibdeps
+++ b/d-devlibdeps
@@ -82,6 +82,7 @@ overridedevlibdeps() {
 		-e 's/libeXosip2-[0-9]\+-dev/libexosip2-dev/' \
 		-e 's/libf2clibf2c.so-dev/libf2c2-dev/' \
 		-e 's/libffado2-dev/libffado-dev/' \
+		-e 's/libfribidi0-dev/libfribidi-dev/' \
 		-e 's/libGenome-\([.0-9]\+\)-[0-9]\+-dev/libgenome-\1-dev/' \
 		-e 's/libGL1-dev/xlibmesa-gl-dev/' \
 		-e 's/libGLU1-dev/xlibmesa-glu-dev/' \
-- 
2.18.0

Bug#895235: Bug #895235 in pango marked as pending

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #895235 in pango reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/pango/commit/5856e3fb30bb970201bd51ae47f14400f5868718


Move fribidi from Requires to Requires.private

Closes: #895235



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/895235

Processed: Bug #895235 in pango marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #895235 [libpango1.0-dev] "pkg-config --libs pango" incorrectly contains 
-lfribidi
Added tag(s) pending.

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

Bug#902499: marked as done (git-annex: network access during build)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 12:34:30 +
with message-id 
and subject line Bug#902499: fixed in git-annex 6.20180626-2
has caused the Debian Bug report #902499,
regarding git-annex: network access during build
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.)


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

For some reasons git-annex is attempting network access during build, this is 
obvious if you look at the ubuntu log
where network is really disabled.
https://launchpad.net/ubuntu/+source/git-annex/6.20180626-1

I had this issue with haskell-src-exts-util and haskell-iso8601-time, and I 
fixed with the following commits:
https://salsa.debian.org/haskell-team/DHG_packages/commit/ccf233ff83823136e2c4123364cb5e44fa5a5f3a
and
https://salsa.debian.org/haskell-team/DHG_packages/commit/5274d07ad4588fbba875872d408c0d6a22cbd262

this is debian/rules file did the trick
-DEB_SETUP_BIN_NAME = cabal
+DEB_SETUP_BIN_NAME = debian/hlibrary.setup


but git-annex is not using cdbs, so I don't know how to best fix this issue...

snip of the build log below

make -j1
make[1]: Entering directory '/<>'
if [ "debian/cabal-wrapper" = ./Setup ]; then ghc --make Setup; fi
if [ "debian/cabal-wrapper" != stack ]; then \
debian/cabal-wrapper configure 
--ghc-options="-optl-Wl,-Bsymbolic-functions -optl-Wl,-z,relro -optc-g -optc-O2 
-optc-fdebug-prefix-map=/<>=. -optc-fstack-protector-strong 
-optc-Wformat -optc-Werror=format-security -optc-Wp,-Wdate-time 
-optc-Wp,-D_FORTIFY_SOURCE=2"; \
else \
debian/cabal-wrapper setup; \
fi
Config file path source is default config file.
Config file /tmp/tmp.UZlSj03KsY/.cabal/config not found.
Writing default configuration to /tmp/tmp.UZlSj03KsY/.cabal/config
Warning: 'nslookup' tool missing - can't locate mirrors
dieVerbatim: user error (cabal: '/usr/bin/curl' exited with an error:
curl: (6) Could not resolve host: hackage.haskell.org
)Makefile:22: recipe for target 'tmp/configure-stamp' failed
make[1]: *** [tmp/configure-stamp] Error 1
make[1]: Leaving directory '/<>'

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: git-annex
Source-Version: 6.20180626-2

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated git-annex 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: Thu, 28 Jun 2018 13:13:16 +0100
Source: git-annex
Binary: git-annex
Architecture: source
Version: 6.20180626-2
Distribution: unstable
Urgency: high
Maintainer: Debian Haskell Group 

Changed-By: Sean Whitton 
Description:
 git-annex  - manage files with git, without checking their contents into git
Closes: 902499
Changes:
 git-annex (6.20180626-2) unstable; urgency=high
 .
   * Drop debian/cabal-wrapper, which should no longer be needed
 (Closes: #902499).
 Thanks Ilias Tsitsimpis for noticing that the wrapper is no longer
 needed.
   * urgency=high because CVE fixes have not yet migrated to testing users.
Checksums-Sha1:
 17e0aed3b4495568e6c092dbbd33a68577977e98 5293 git-annex_6.20180626-2.dsc
 fc7655f44c43cd2e3d7cb2f061c7a48790ce3537 77780 
git-annex_6.20180626-2.debian.tar.xz
Checksums-Sha256:
 ba3b7854fb24278e31e6bd6c8944d33293ed2ca878a642b892b5c4dbdea21fdc 5293 
git-annex_6.20180626-2.dsc
 9c61b92e1d313ee2fa74da836b8f6feff5f55fb946f4a5051058fe5a9e31fe98 77780 
git-annex_6.20180626-2.debian.tar.xz
Files:
 7ca4f8e0b07981b946be134680536f0e 5293 utils optional git-annex_6.20180626-2.dsc
 2e745896bf80f99a3b62aeaa1c520043 77780 utils optional 
git-annex_6.20180626-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAls00TwACgkQaVt65L8G
YkCAMxAAr5V4Nr43CN5sr4zNjCfjuglwpukPYRQgAuqNbwHaDxygBM4l+bSYGttI
BZus1/PRpJ71VxyzbFB3fsRS2JKpk3IYOxI/9J1gXqsHBSyoIJRwTwAPkSqczUhm
gUmbITFVAwD/Kni3YYmD6Eo1kq8bbHWh7eQWLX9HHcNciz4c7F0AIhUJyzk3vC32
H5CA1

Bug#902578: marked as done (dgit: missing seperator between items in Depends: field of bin:git-deborig)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 12:49:03 +
with message-id 
and subject line Bug#902578: fixed in dgit 5.5
has caused the Debian Bug report #902578,
regarding dgit: missing seperator between items in Depends: field of 
bin:git-deborig
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.)


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

Depends: perl, git-core, libdpkg-perl, libfile-fnmatch-perl
 ${misc:Depends}

Should be a comma after libfile-fnmatch-perl.

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 5.5

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

Debian distribution maintenance software
pp.
Ian Jackson  (supplier of updated dgit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 13:25:21 +0100
Source: dgit
Binary: dgit git-debrebase dgit-infrastructure
Architecture: all source
Version: 5.5
Distribution: unstable
Urgency: medium
Maintainer: Ian Jackson 
Changed-By: Ian Jackson 
Closes: 902578
Description: 
 dgit   - git interoperability with the Debian archive
 dgit-infrastructure - dgit server backend infrastructure
 git-debrebase - rebasing git workflow tool for Debian packaging
Changes:
 dgit (5.5) unstable; urgency=medium
 .
   * Add missing comma in debian/control.  Closes:#902578.
   * dgit(1): Fix a wrong reference to \fp, which should be \fP.
Checksums-Sha1: 
 4be7eea6198c00b62e8ab86c031c800d41c7e070 1607 dgit_5.5.dsc
 627526f7dd0875da1b2e35dc925811d2963d3403 454091 dgit_5.5.tar.gz
 2459e56059eaa84a29d31e61ade4c0fad5033008 53556 dgit-infrastructure_5.5_all.deb
 74e4232f14b3f56b1d9852e7fbc2431dfa6be67a 153596 dgit_5.5_all.deb
 7ce70941cde4c2b58de4639a4f1732a51d540f28 5608 dgit_5.5_amd64.buildinfo
 f356b729f712c3696a278375ce57861335b7bdb1 63616 git-debrebase_5.5_all.deb
Checksums-Sha256: 
 87f8090742c6ec02c6fc567c766a3e65363b48bb5a53505ea878c2877c90bf5e 1607 
dgit_5.5.dsc
 449e51f6126ed9cba01be816c1305e3627cd4141c0c9f9ac886b5c872686e3ac 454091 
dgit_5.5.tar.gz
 19a89389b8dede159108fe70b124ae87430ec1cd95c66f136f31b33a19210ff7 53556 
dgit-infrastructure_5.5_all.deb
 a26d7ebc0a3385dc8cba5d42b2ce8919205209f34050668acb3aea1ffe82686d 153596 
dgit_5.5_all.deb
 2fcf9dbf9764e6720add4a433dd005929a01f4dea84ba842fa826aae2f62a828 5608 
dgit_5.5_amd64.buildinfo
 c53ac6b1cf78ec42d1bd807be9c4958e6d278d440c3979f9915a7a0b5220848b 63616 
git-debrebase_5.5_all.deb
Files: 
 38ae0b68cd17ae2d41b17ea144495ac4 1607 devel optional dgit_5.5.dsc
 45485c417b5943862de15f105164462d 454091 devel optional dgit_5.5.tar.gz
 6bf45632290477d35287b489a9537c20 53556 devel extra 
dgit-infrastructure_5.5_all.deb
 bcc3f4e43a6b54c7d0b34bd37ca55dd9 153596 devel optional dgit_5.5_all.deb
 ab3ebcc279977fc9d3504df8891ddf4c 5608 devel optional dgit_5.5_amd64.buildinfo
 652aa2c0cad7447df245eed39a5bdd75 63616 devel optional git-debrebase_5.5_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAls01AcACgkQ4+M5I0i1
DTn7JQf/fQtplJTS+0AjkYVoiEIBwk5oGczZ8D7eT9XwvDqizuvZXgbQYabDox8X
6GcTIVgv3uv84oWil4xkfNbRThi2SUZZ9bW6Mi0H9+y1TKyu9+yoZeS9ftt/nKPS
xelMrFRPAh6M2Sc0mr2Mi5AetfWyBgFw5+VYxJNaIXqtxETWAlkSzbNYNZ1GByr/
Sg+8PRQtw39VyYr9ktJHekXwRogk7jVkCUGHX4cwO+eEokaguPTl7R7gu1E3e3cU
eyaRARdnNf49vKpyuCs81qIxfJC8HiAww02zmC2g0EjA6Gjnrg6QmXA6MyonBCHY
llmza5DJgI+e4sLkcEUZZ74TnuODGA==
=mDU5
-END PGP SIGNATURE End Message ---

Bug#902526: [Pkg-zsh-devel] Bug#902526: Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Daniel Shahaf]

Control: tag -1 pending

Daniel Shahaf wrote on Thu, Jun 28, 2018 at 09:36:07 +:
> Control: tags -1 patch
> 
> Axel Beckert wrote on Thu, 28 Jun 2018 11:24 +0200:
> > Daniel Shahaf wrote:
> > > If that's the case, then removing the override_dh_installchangelogs
> > > target would be the correct fix.
> > 
> > Yes.
> > 
> 
> Okay.  In this case the attached patch should fix it.
> 
> Getting a bit ahead of myself, we don't seem to have anywhere to push
> that patch now, since the package's repository was on alioth and hasn't
> been migrated to salsa.  I'll have to look into migrating that.  (Also would
> need to test the patch and tag an 0.6.0-2 that has it.)

Okay.  I've verified the patch and pushed it in
7ce9697ed43d20e9a10fce052516b4b324654c6c.  (Does salsa have a facility for
automatically adding the 'pending' tag, like git-tag-pending on alioth?)

There are a few lintian warnings with that, but I think they are less important
than fixing the FTBFS:

> P: zsh-syntax-highlighting source: package-uses-old-debhelper-compat-version 
> 10

I've looked through the upgrade checklist in debhelper(7) on buster.  It's
probably safe to just bump to 11 but I would like to first upload the FTBFS fix
since, if there is fallout here, I wouldn't have time to deal with it.

> I: zsh-syntax-highlighting source: out-of-date-standards-version 4.1.1 
> (released 2017-09-27) (current is 4.1.4)

v4.1.2 adds a requirement in §4.10 that Perl scripts must use "#!/usr/bin/perl"
as the first line.  I assume that requirement doesn't affect tests/tap, right?

Assuming that's the case, it's safe to just bump to 4.1.4 with no changes.

> I: zsh-syntax-highlighting source: testsuite-autopkgtest-missing

New feature, not a bug, doesn't block fixing the FTBFS.

> X: zsh-syntax-highlighting source: upstream-metadata-file-is-missing

New feature, not a bug, doesn't block fixing the FTBFS.

> P: zsh-syntax-highlighting source: debian-watch-does-not-check-gpg-signature
> N:
> N:   This watch file does not include a means to verify the upstream
> N:   tarball using cryptographic signature.

Upstream doesn't provide signed tarballs, only signed git tags.  We can either
ignore this warning or ask upstream to start producing signed tarballs as well.
At any rate, doesn't block fixing the FTBFS, especially since this isn't a new
upstream release.

> W: zsh-syntax-highlighting source: debian-watch-could-verify-download 
> debian/upstream/signing-key.asc
> N:
> N:   One or more upstream signing keys are present in the Debian package
> N:   but are not being used.
> N:   
> N:   Please enable the cryptographic verification of downloads with the
> N:   "pgpsigurlmangle" option in your watch file or remove the key.
> N:   

False positive.  Upstream provides only signed tags, no signed tarballs, so
there is no value pgpsigurlmangle can be set to, but at the same time, having
signing-key.asc in the package adds value, since it allows maintainers to
manually verify upstream releases (using 'git tag --verify').

> N:   Refer to the uscan(1) manual page for details.
> N:   
> N:   Severity: normal, Certainty: certain
> N:   
> N:   Check: watch-file, Type: source

Assuming we're in agreement about all that, I'll extend my PGP key validity
(just expired earlier today) and tag 7f8062b9b0d656292080d441f417e84adc253d78
as debian/0.6.0-2 and upload it.

And I suppose I should check whether there's a bug open against lintian asking
to demote the severity of debian-watch-could-verify-download.

Cheers,

Daniel

Processed: Re: [Pkg-zsh-devel] Bug#902526: Bug#902526: Bug#902526: zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902526 [src:zsh-syntax-highlighting] zsh-syntax-highlighting: FTBFS in 
buster/sid (does not work with recent debhelper)
Added tag(s) pending.

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

Bug#895235: marked as done ("pkg-config --libs pango" incorrectly contains -lfribidi)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 13:04:33 +
with message-id 
and subject line Bug#895235: fixed in pango1.0 1.42.1-2
has caused the Debian Bug report #895235,
regarding "pkg-config --libs pango" incorrectly contains -lfribidi
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.)


-- 
895235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sugar-toolkit-gtk3
Version: 0.112-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sugar-toolkit-gtk3.html

...
d-shlibmove --commit \
--multiarch \
--exclude-la --exclude-a \
--devunversioned --ignorelibdep \
--movedev debian/tmp/usr/share/gir-1.0 usr/share/ \
--extralib 
debian/tmp/usr/lib/x86_64-linux-gnu/libsugar-eventcontroller.so \
debian/tmp/usr/lib/x86_64-linux-gnu/libsugarext.so
Library package automatic movement utility
 --> libasound2-dev package exists.
 --> libatk1.0-dev package exists.
 --> libcairo-dev is provided by a package.
 --> libcairo2-dev package exists.
devlibs error: There is no package matching [libfribidi0-dev] and noone 
provides it, please report bug to d-shlibs maintainer
 --> libglib2.0-dev package exists.
 --> libgtk-3-dev package exists.
 --> libgtk2.0-dev package exists.
 --> libice-dev package exists.
 --> libpango1.0-dev package exists.
 --> librsvg2-dev package exists.
 --> libsm-dev package exists.
 --> libx11-dev package exists.
 --> libxfixes-dev package exists.
 --> libxi-dev package exists.
make: *** [debian/rules:118: debian/stamp-local-shlibs-libsugarext] Error 1
--- End Message ---
--- Begin Message ---
Source: pango1.0
Source-Version: 1.42.1-2

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated pango1.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 13:16:24 +0100
Source: pango1.0
Binary: libpango1.0-0 libpango-1.0-0 libpangocairo-1.0-0 libpangoxft-1.0-0 
libpangoft2-1.0-0 libpango1.0-udeb libpango1.0-dev libpango1.0-doc 
gir1.2-pango-1.0 pango1.0-tests
Architecture: source
Version: 1.42.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Description:
 gir1.2-pango-1.0 - Layout and rendering of internationalized text - gir 
bindings
 libpango-1.0-0 - Layout and rendering of internationalized text
 libpango1.0-0 - Layout and rendering of internationalized text (transitional 
pack
 libpango1.0-dev - Development files for the Pango
 libpango1.0-doc - Documentation files for the Pango
 libpango1.0-udeb - Layout and rendering of internationalized text - minimal 
runtime (udeb)
 libpangocairo-1.0-0 - Layout and rendering of internationalized text
 libpangoft2-1.0-0 - Layout and rendering of internationalized text
 libpangoxft-1.0-0 - Layout and rendering of internationalized text
 pango1.0-tests - Layout and rendering of internationalized text - installed 
tests
Closes: 895235
Changes:
 pango1.0 (1.42.1-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jeremy Bicha ]
   * Drop obsolete debian/source/options
 .
   [ Simon McVittie ]
   * d/p/pango.pc.in-Move-fribidi-to-Requires.private.patch:
 Move fribidi from Requires to Requires.private (Closes: #895235)
Checksums-Sha1:
 e80a23b77f7e6bcd57c399d4aae6394a207d9cfa 3266 pango1.0_1.42.1-2.dsc
 99eac14857eb033770a41dd86487a7c1e33ae653 30156 pango1.0_1.42.1-2.debian.tar.xz
 668ee4f8c22e9a2245814980d4bde231cac527e3 9206 
pango1.0_1.42.1-2_source.buildinfo
Checksums-Sha256:
 bc1eca182e2c489324a05ac446efe54c4ecb79614b0742aabf6dc4e0203acb33 3266 
pango1.0_1.42.1-2.dsc
 806bdae7e4a014d344ed2defaf4964af6ef0722f9df2bc5eac7e69b008b3372d 30156 
pango1.0_1.42.1-2.debian.tar.xz
 1d3e60ea4d808a78f936ac8940065c677ff550d91c44644f26f0731ab79c389f 9206 
pango1.0_1.42.1-2_source.buildinfo
Files:
 3d5d7bbb960a713922295db8affd5da8 3266 libs optional pango1.0_1.42.1-2.dsc
 a40ba620550aeb220ec6d431

Bug#900311: marked as done (recoll: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 13:19:12 +
with message-id 
and subject line Bug#900311: fixed in recoll 1.24.1-2
has caused the Debian Bug report #900311,
regarding recoll: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
900311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900311
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: recoll
Version: 1.23.7-4
Severity: serious

Dear maintainer: This package fails to build from source when built
with dpkg-buildpackage -A:

[...]
running install_egg_info
Writing 
/<>/debian/tmp/usr/lib/python3/dist-packages/Recoll-1.0.egg-info
 dpkg-genbuildinfo --build=all
 dpkg-genbuildinfo: error: binary build with no binary artifacts found; 
.buildinfo is meaningless 
dpkg-buildpackage: error: dpkg-genbuildinfo --build=all subprocess
returned exit status 25

To reproduce, please try "dpkg-buildpackage -A".


This happens because debian/rules has a binary-indep target which does
nothing:

binary-indep: build install

The arch:all packages are supposed to be created there, but the target
does not create any packages, they are only created in binary-arch.

Sorry, I don't have a fix, but I would personally recommend switching
to a dh-style debian/rules as part of the fix.

I would also recommend that you try to upload packages
in source-only form, i.e. using "dpkg-buildpackage -S"
so that this kind of bugs never propagate to testing.

Thanks.
--- End Message ---
--- Begin Message ---
Source: recoll
Source-Version: 1.24.1-2

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated recoll package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 17:26:02 +0530
Source: recoll
Binary: recoll recollcmd recollgui python-recoll python3-recoll
Architecture: source amd64 all
Version: 1.24.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kartik Mistry 
Changed-By: Kartik Mistry 
Description:
 python-recoll - Python extension for recoll
 python3-recoll - Python extension for recoll (Python3)
 recoll - Personal full text search package
 recollcmd  - Command line programs for recoll
 recollgui  - GUI program and elements for recoll
Closes: 900311
Changes:
 recoll (1.24.1-2) unstable; urgency=medium
 .
   * debian/rules:
 + Fix FTBFS when built with dpkg-buildpackage -A (Closes: #900311)
Checksums-Sha1:
 f171dedd4fec65f6754aef11d9243f3ffef56740 2192 recoll_1.24.1-2.dsc
 c9ab6a81546712e7de4ed28d747d890ac470c36d 11128 recoll_1.24.1-2.debian.tar.xz
 bcaad4f3364be2077fdeee1ddc58d9c7fa7daa77 129696 
python-recoll_1.24.1-2_amd64.deb
 a21695298623bf952856aff5ed345b37f0608370 130036 
python3-recoll_1.24.1-2_amd64.deb
 1b1cbe44fb38e2f1b1728d134b57f2782b791d58 148920 recoll_1.24.1-2_all.deb
 07135ae2933ccfd1d030480d8c4497e7acc48c6e 13114 recoll_1.24.1-2_amd64.buildinfo
 1d5687a551dfeface7f8a57e51ad101cfa1f838a 1236264 recollcmd_1.24.1-2_amd64.deb
 16913d42fb5ab6b72acfcb7986f8c9a6388480de 722740 recollgui_1.24.1-2_amd64.deb
Checksums-Sha256:
 5a09f5e912e8b68fd095843ac12e9fbcc38b81ba9979ccd1b01db68fe656c926 2192 
recoll_1.24.1-2.dsc
 04869fbd4bebb0a2feb526a6bcb50445612f8715a70992ee53d439564598da15 11128 
recoll_1.24.1-2.debian.tar.xz
 d068a84aa2b9804e9942b229ab5a4e430537c9e3bef88eeffd3eb11c943e5caf 129696 
python-recoll_1.24.1-2_amd64.deb
 f2f584d2f348b228b725de63cb5e1e12ac536f13191c9267e600f365bab268ac 130036 
python3-recoll_1.24.1-2_amd64.deb
 d41c1ffaa93c4876fb814bed7f12784574f2326c53bab6243943de52903fd6bb 148920 
recoll_1.24.1-2_all.deb
 55fcd87f66507dae3ce03678aebd43f66ff0d78ffcde9b780e30645cc16fc954 13114 
recoll_1.24.1-2_amd64.buildinfo
 8d02ed1a92b448ee8ea05e099a17d019498babba0fb0fad63b509efb8095f9c9 1236264 
recollcmd_1.24.1-2_amd64.deb
 d26a6887b0d469dfa882870067754f72f14c866a7ddce224ce08167149b66756 722740 
recollgui_1.24.1-2_amd64.deb
Files:
 93a885c41240d3a8c81870bee5724869 2192 x11 optional recoll_1.24.1-2.dsc
 12943c8af44d94e0f1bfadf2a1

Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

[Lisandro Damián Nicanor Pérez Meyer]

El miércoles, 27 de junio de 2018 16:25:23 -03 Niko Tyni escribió:
> On Tue, Jun 19, 2018 at 10:05:09AM -0300, Lisandro Damián Nicanor Pérez 
Meyer wrote:
[snip] 
> > > Copying the debconf maintainers as well.
> > 
> > Hi! I have just pinged the rest of the Qt/KDE team for thoughts, as I have
> > never used this myself so I might not have a good view on the issue.
> > 
> > I'll try to follow up soon, but please ping me again (IRC is valid too) if
> > I don't cam up with a reply in, let's say, 5 to 7 days.
> 
> Hi, any news here? FWIW Perl 5.28.0 final was released recently and is
> now in experimental. It would be great to get this issue moving forward
> one way or another.

For what I know Scott (CCed) was waiting on a reply from someone wrt this. 
That's all I could gather I'm afraid.

-- 
The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself.  Therefore all
progress depends on the unreasonable man.
  George Bernard Shaw

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Processed: forwarded 896630, tagging 896630

[Debian Bug Tracking System]

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

> forwarded 896630 https://github.com/pallets/click/pull/991
Bug #896630 [src:python-click] FTBFS with sphinx 1.7.2: exception: cannot 
import name 'Directive'
Set Bug forwarded-to-address to 'https://github.com/pallets/click/pull/991'.
> tags 896630 + fixed-upstream
Bug #896630 [src:python-click] FTBFS with sphinx 1.7.2: exception: cannot 
import name 'Directive'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#893649: xvt: should this package be removed?

[Boyuan Yang]

X-Debbugs-CC: s...@debian.org

On Tue, 20 Mar 2018 22:36:31 +0100 Adam Borowski  wrote:
> Package: xvt
> Version: 2.1-20.3
> Severity: serious
> Justification: QA query
> 
> Hi!
> I believe that xvt is no longer suitable for inclusion in Debian, and thus
> propose its removal.  Not only has it been dead upstream since times
> immemorial but also it lacks features so basic it's mind-boggling.
> 
> For example, I believed that Windows 3.11's TELNET.EXE was the last terminal
> in existence that lacked color support.  Turns out, here we ship xvt, in
> 2018.  Or, no UTF-8 support is probably worth a RC bug on its own.
> 
> More than two decades ago, xvt was superseded by its fork rxvt, which in
> turn spawned a multitude of forks on its own.  I for one remember using a
> bunch of them on IRIX, when the world was still young...  Those forks have
> then died out around the beginning of this millenium, of them only
> rxvt-unicode is still struggling along.
> 
> As this package is still nominally maintained (well, your last upload was in
> 2006...), I can't file a RoQA immediately.  Thus, please tell me whether it
> should be removed.  If not, please close this bug, otherwise I'll ask for
> removal before Buster freeze.

Hi Sam,

I noticed that the maintainer field still points to your old email (non 
@debian.org one). I'm forwarding this mail to your @debian.org mail address 
again to eusure mail delivery.

I personally second the idea of requesting package removal for xvt. If you 
agree with that, it would be better for us to do it earlier than later.

--
Regards,
Boyuan Yang

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

Processed: forwarded 896627

[Debian Bug Tracking System]

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

> forwarded 896627 
> https://bitbucket.org/birkenfeld/pygments-main/pull-requests/726/change-to-docutilsparsers-in-sphinxext
Bug #896627 [src:pygments] FTBFS with sphinx 1.7.2: exception: cannot import 
name 'Directive'
Set Bug forwarded-to-address to 
'https://bitbucket.org/birkenfeld/pygments-main/pull-requests/726/change-to-docutilsparsers-in-sphinxext'.
> thanks
Stopping processing here.

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

Bug#902348: marked as done (pymol: fails to start with runtime error regarding Qt)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 15:20:59 +
with message-id 
and subject line Bug#902348: fixed in pymol 2.1.0+dfsg-3
has caused the Debian Bug report #902348,
regarding pymol: fails to start with runtime error regarding Qt
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.)


-- 
902348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pymol
Version: 2.1.0+dfsg-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

pymol fails to start with the following error:

Traceback (most recent call last):
  File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File "/usr/lib/python2.7/dist-packages/pymol/__init__.py", line 65, in 

pymol.launch(args)
  File "/usr/lib/python2.7/dist-packages/pymol/__init__.py", line 444, in launch
from pmg_qt import pymol_qt_gui
  File "/usr/lib/python2.7/dist-packages/pmg_qt/pymol_qt_gui.py", line 17, in 

from pymol.Qt import QtGui, QtCore, QtWidgets
  File "/usr/lib/python2.7/dist-packages/pymol/Qt/__init__.py", line 34, in 

from PyQt4 import QtGui, QtCore, QtOpenGL
RuntimeError: the PyQt4.QtCore and PyQt5.QtCore modules both wrap the QObject 
class


I am not sure what is going on. Pymol checks for Qt versions 5 and 4 
for python 2.7 in it's startup script on my system. I have both 
python-qt4 and python-pyqt5 installed on my system. Other packages 
seem to depend on one or the other.

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

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

Versions of packages pymol depends on:
ii  freeglut3 2.8.1-3
ii  libc6 2.27-3
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.1.0-8
ii  libgl11.0.0+git20180308-3
ii  libglew2.02.0.0-6
ii  libpng16-16   1.6.34-1
ii  libstdc++68.1.0-8
ii  libxml2   2.9.4+dfsg1-7
ii  pymol-data2.1.0+dfsg-2
ii  python2.7.15-3
ii  python-numpy [python-numpy-abi9]  1:1.14.4-1
ii  python-pmw1.3.2-6
ii  python-tk 2.7.15-1

Versions of packages pymol recommends:
ii  apbs  1.4-1+b1

pymol suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pymol
Source-Version: 2.1.0+dfsg-3

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated pymol package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 29 Jun 2018 00:30:41 +1000
Source: pymol
Binary: pymol pymol-data
Architecture: source
Version: 2.1.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Stuart Prescott 
Description:
 pymol  - Molecular Graphics System
 pymol-data - data files for PyMOL
Closes: 902348
Changes:
 pymol (2.1.0+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Force use of Tk GUI to prevent crashes with Qt GUI (Closes: #902348).
Checksums-Sha1:
 b69776d291ace63c1d731b682daf770ab77dd6a7 2163 pymol_2.1.0+dfsg-3.dsc
 e5c88fe2fe9ce9f38a799595a090f1ee508805d1 56280 pymol_2.1.0+dfsg-3.debian.tar.xz
 60e1e259fc40481e5f08787038570a896578d360 12903 
pymol_2.1.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 c4ab4da8e9ec3608aff48b32351df9ffcebebc91e1f5382c3f6ae626d024affe 2163 
pymol_2.1.0+dfsg-3.dsc
 da05b0b9198a224b349002f089d643c5b4d80b48787f7544ba95a8a34af59fb8 56280 
pymol_2.1.

Bug#902620: certbot.service should not use root privileges

[Roland Tapken]

Package: certbot
Version: 0.10.2-1
Severity: serious
Tags: security
Justification: 5.b

Dear Maintainer,

certbot.service is configured to be executed with root privileges.
This leads to a potential attack vector while renewing certificates,
especially when using the 'standalone' authenticator.

For most setups it should be sufficient to run 'certbot --renew' as
an unprivileged user 'certbot'. This would require the following changes in the
default setup:

- /etc/letsencrypt and /var/letsencrypt must be owned and writable by
  'certbot'

- for standalone authenticator, the default port has to be changed to an
  unprivileged one (e.g. 8080).

- for webroot authenticator, a seperate directory for the acme challenge
  owned and writable by 'certbot' must be created (e.g.
  /etc/letsencrypt/acme-challenge) and an Apache rewrite rule must
  redirect requests to this directory:

  RewriteRule ^/(\.well-known/acme-challenge/.*)$ \
  /etc/letsencrypt/acme-challenge$1 [L]
  
  AllowOverride none
  Require all granted
  

  For nginx, a similar configuration would be required.

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

Kernel: Linux 4.9.0-6-amd64 (SMP w/2 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 certbot depends on:
ii  init-system-helpers  1.48
ii  python   2.7.13-2
ii  python-certbot   0.10.2-1

certbot recommends no packages.

Versions of packages certbot suggests:
pn  python-certbot-apache  
pn  python-certbot-doc 

-- no debconf information

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

[Jiri Palecek]

Hi,

On 6/28/18 12:54 PM, Eric Valette wrote:



Just a quick note to say that indeed the proposed patch to look for 
DRI modules at the right place is working. However, I have a bunch of 
other problems since driver update even with the fix in place:


  * Sddm does not start. I get only a black screen with the mouse
pointer. I have should check but I think I have a backtrace that
points to qtRenderGlthread that is crashing in systemd-nss lib,
  * using lightdm and using plasma I'm able to get back to my kde
environment however the kde setup takes ages to start (and I have
no more the DRI message in Xorg.0.log),
  * The lock screen also takes ages to start, black screen for 30s or
so with keyboar input or mous move not working,
  * Launching Kodi, takes 40s but is fluid afterwards
  * Checked both glxinfo, vdpau info : all normal,


Are you using xserver 1.20 from unstable or 1.19.6 from testing? I've 
had similar problems when I updated, and they went away when I 
downgraded xserver-xorg-core.


Regards

   Jiri Palecek

Bug#902623: libgsl23: missing shlibs information for 2.5 symbols

[Niko Tyni]

Package: libgsl23
Version: 2.5+dfsg-3
Severity: serious

The 2.5 versions of this package introduced new symbols, but that isn't
reflected in the shlibs file. It looks like this is caused by a simple
typo: debian/libgsl23.shlib should be named debian/libgsl23.shlibs .
So its contents aren't currently reflected in the binary package.

(This is showing up in the autopkgtest checks of the new libmath-gsl-perl
 package, which was built in sid against the new libgsl23 versions but
 didn't gain a corresponding versioned dependency, so it's installable
 but broken with the old libgsl23 in testing.)
-- 
Niko Tyni   nt...@debian.org

Processed: libmath-gsl-perl: needs a versioned dependency on libgsl23 (>= 2.5) or so

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 902623
Bug #902625 [libmath-gsl-perl] libmath-gsl-perl: needs a versioned dependency 
on libgsl23 (>= 2.5) or so
902625 was not blocked by any bugs.
902625 was not blocking any bugs.
Added blocking bug(s) of 902625: 902623

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

Bug#902625: libmath-gsl-perl: needs a versioned dependency on libgsl23 (>= 2.5) or so

[Niko Tyni]

Package: libmath-gsl-perl
Version: 0.39-2
Severity: serious
Control: block -1 with 902623
User: debian-p...@lists.debian.org
Usertags: autopkgtest

This package uses symbols from libgsl23 >= 2.5, but that isn't
reflected in the package dependencies because of #902623 (libgsl23
missing shlibs information). Once that bug is fixed, libmath-gsl-perl
needs a rebuild so that the package dependencies get updated. A binNMU
should be enough but we might as well make a sourceful one and declare
a build dependency on fixed gsl versions.

(This was noticed by the awesome ci.debian.net autopkgtest migration
 checks, which highlighted that the package is installable but broken
 with the libgsl23 version currently in testing.)

 https://ci.debian.net/packages/libm/libmath-gsl-perl/testing/amd64/
-- 
Niko Tyni   nt...@debian.org

Bug#902623: libgsl23: missing shlibs information for 2.5 symbols

[Dirk Eddelbuettel]

On 28 June 2018 at 21:05, Niko Tyni wrote:
| Package: libgsl23
| Version: 2.5+dfsg-3
| Severity: serious
| 
| The 2.5 versions of this package introduced new symbols, but that isn't
| reflected in the shlibs file. It looks like this is caused by a simple
| typo: debian/libgsl23.shlib should be named debian/libgsl23.shlibs .
| So its contents aren't currently reflected in the binary package.

Nice catch!

Building -4 in a moment.

Dirk

| (This is showing up in the autopkgtest checks of the new libmath-gsl-perl
|  package, which was built in sid against the new libgsl23 versions but
|  didn't gain a corresponding versioned dependency, so it's installable
|  but broken with the old libgsl23 in testing.)
| -- 
| Niko Tyni   nt...@debian.org

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

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

[Drew Parsons]

On Sat, 23 Jun 2018 12:54:19 +0300 Adrian Bunk  wrote:
> ...
> odepkg_octsolver_mebdfdae.cc:42:10: fatal error: config.h: No such
file or directory
>  #include 
>   ^~


The patch is trivial. Replace all  with .

config.h was already deprecated, and is now removed in octave 4.4.0.

Drew

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

[Sébastien Villemot]

On Fri, Jun 29, 2018 at 02:50:36AM +0800, Drew Parsons wrote:
> On Sat, 23 Jun 2018 12:54:19 +0300 Adrian Bunk  wrote:
> > ...
> > odepkg_octsolver_mebdfdae.cc:42:10: fatal error: config.h: No such
> file or directory
> >  #include 
> >   ^~
> 
> 
> The patch is trivial. Replace all  with .
> 
> config.h was already deprecated, and is now removed in octave 4.4.0.

Yes, but then you get many numerical test failures, which are not trivial at
all to fix…

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#902623: marked as done (libgsl23: missing shlibs information for 2.5 symbols)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 19:04:07 +
with message-id 
and subject line Bug#902623: fixed in gsl 2.5+dfsg-4
has caused the Debian Bug report #902623,
regarding libgsl23: missing shlibs information for 2.5 symbols
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.)


-- 
902623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgsl23
Version: 2.5+dfsg-3
Severity: serious

The 2.5 versions of this package introduced new symbols, but that isn't
reflected in the shlibs file. It looks like this is caused by a simple
typo: debian/libgsl23.shlib should be named debian/libgsl23.shlibs .
So its contents aren't currently reflected in the binary package.

(This is showing up in the autopkgtest checks of the new libmath-gsl-perl
 package, which was built in sid against the new libgsl23 versions but
 didn't gain a corresponding versioned dependency, so it's installable
 but broken with the old libgsl23 in testing.)
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: gsl
Source-Version: 2.5+dfsg-4

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated gsl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 28 Jun 2018 13:38:17 -0500
Source: gsl
Binary: libgsl23 libgslcblas0 libgsl-dev gsl-bin libgsl-dbg libgsl-prof
Architecture: source amd64
Version: 2.5+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gsl-bin- GNU Scientific Library (GSL) -- binary package
 libgsl-dbg - GNU Scientific Library (GSL) -- debug symbols package
 libgsl-dev - GNU Scientific Library (GSL) -- development package
 libgsl-prof - GNU Scientific Library (GSL) -- profiling symbols package
 libgsl23   - GNU Scientific Library (GSL) -- library package
 libgslcblas0 - GNU Scientific Library (GSL) -- blas library package
Closes: 902623
Changes:
 gsl (2.5+dfsg-4) unstable; urgency=medium
 .
   * debian/libgsl23.shlibs: Use correct suffix (Closes: #902623)
   * debian/libgslcblas0.shlibs: Idem
Checksums-Sha1:
 69d6c2fb99fe55a921b5ec7cf3ed2b8314dca0ce 2069 gsl_2.5+dfsg-4.dsc
 d1ec00dce23f58afeca1ba7a11cebc6a4462236c 18820 gsl_2.5+dfsg-4.debian.tar.xz
 8ebb0da69c3d203472bdfe44a65dcf29a4248138 29344 gsl-bin_2.5+dfsg-4_amd64.deb
 3f48c29e7be6f74a5c9985d794b95f657b307409 6060 gsl_2.5+dfsg-4_amd64.buildinfo
 c30cf637731602fb7736824c381853145b25846c 2538268 
libgsl-dbg_2.5+dfsg-4_amd64.deb
 5471ae36c58b12685d54c2df9c5ba0d2df63fd12 1057428 
libgsl-dev_2.5+dfsg-4_amd64.deb
 d169a035358ab21826b24f242ae35707a6e3a36d 878352 libgsl23_2.5+dfsg-4_amd64.deb
 ebab50ae3a391efdd0d121f016b93b5cacdad307 96788 
libgslcblas0_2.5+dfsg-4_amd64.deb
Checksums-Sha256:
 7ed3ee0db0b8304cfe1d337f70cc306d43fdabcc537b221a6849b118951ac7e6 2069 
gsl_2.5+dfsg-4.dsc
 c9a4262c705bab1c45e74886c90b5af3c1f68dbae47a1862149ebce27364b70e 18820 
gsl_2.5+dfsg-4.debian.tar.xz
 bcfe4abef45b25b799956d9c324569a44fc451c7b149f23a9af3576e7d2d28e0 29344 
gsl-bin_2.5+dfsg-4_amd64.deb
 e80d312a3f818bc11a21db3acc82cc828aadb6009f06207df9b539246ae6e97f 6060 
gsl_2.5+dfsg-4_amd64.buildinfo
 e525d9ba758c734ef331d8710271d8f4f2e658ba1154a57868e6c9d70de13e28 2538268 
libgsl-dbg_2.5+dfsg-4_amd64.deb
 d4bf8312d76aa01755b29f2e815beae460dfa3b6451d257ef36b8496dc573460 1057428 
libgsl-dev_2.5+dfsg-4_amd64.deb
 88afef7d69e524fb9ad9ce325b030600c1616afe714b1517f8be8cbad8a0d543 878352 
libgsl23_2.5+dfsg-4_amd64.deb
 0131c268eeac101d885984d8a0cdf45d57d87951c4303d6cad1f0ae857239a5b 96788 
libgslcblas0_2.5+dfsg-4_amd64.deb
Files:
 e17a5d7e8c91c61ac0da77118e22de6b 2069 math optional gsl_2.5+dfsg-4.dsc
 fad0ae883798304011215e0d5d54bc69 18820 math optional 
gsl_2.5+dfsg-4.debian.tar.xz
 87ca9dcf9c42a64b705ced37df707d28 29344 math optional 
gsl-bin_2.5+dfsg-4_amd64.deb
 11ecb49108e08c9b036ddf4dd7f30602 6060 math optional 
gsl_2.5+dfsg-4_amd64.buildinfo
 0ad009058035c817053c4

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

[Drew Parsons]

On Thu, 28 Jun 2018 20:57:52 +0200 =?iso-8859-1?Q?S=E9bastien?=
Villemot  wrote:
> > 
> > The patch is trivial. Replace all  with .
> > 
> > config.h was already deprecated, and is now removed in octave
4.4.0.
> 
> Yes, but then you get many numerical test failures, which are not
trivial at
> all to fix…
> 

Does 
https://bitbucket.org/odepkg/odepkg/commits/d4f56c4f3678f7f55d8dc84c96fbd0f98f8d4191
help?

Perhaps with 
https://bitbucket.org/odepkg/odepkg/commits/d60b477d520c762ba4093e1a8f7a036d50b80db1


Or does latest the upstream git work, should we just grab that?

Drew

Bug#898519: marked as done (libpam-u2f: upgrade to 1.0.6 breaks authentication with u2fzero device)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 19:19:45 +
with message-id 
and subject line Bug#898519: fixed in pam-u2f 1.0.7-1
has caused the Debian Bug report #898519,
regarding libpam-u2f: upgrade to 1.0.6 breaks authentication with u2fzero device
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.)


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

Dear Maintainer,

during a system upgrade on buster the package libpam-u2f is upgraded from 1.0.4 
to 1.0.6.

After the upgrade the PAM modules fails to authenticate with the U2Fzero device 
(u2fzero.com).
A manual downgrade to 1.0.4 solves all issues.

This is severe: if the system is rebooted directly, authentication would fail.
The user would be locked out from machine.

A quick look at the code shows a lot changes between the two (minor) versions. 
But i couldn't
figure out the exact lines involved yet.

While with the 1.0.4 version the u2f device shows a red light as signal for 
pressing the button,
the 1.0.6 version makes the device just light up bright green.


My Configuration files:


/etc/pam.d/u2f:

auth required pam_u2f.so authfile=/etc/u2f_keys cue debug openasuser


/etc/pam.d/sudo:

#%PAM-1.0
@include common-auth
@include common-account
@include common-session-noninteractive
@include u2f



Output with debug option enabled:

jkur@durruti:~$ sudo su
[sudo] Passwort für jkur: 
[../pam-u2f.c:parse_cfg(64)] called.
[../pam-u2f.c:parse_cfg(65)] flags 32768 argc 3
[../pam-u2f.c:parse_cfg(67)] argv[0]=authfile=/etc/u2f_keys
[../pam-u2f.c:parse_cfg(67)] argv[1]=cue
[../pam-u2f.c:parse_cfg(67)] argv[2]=debug
[../pam-u2f.c:parse_cfg(68)] max_devices=0
[../pam-u2f.c:parse_cfg(69)] debug=1
[../pam-u2f.c:parse_cfg(70)] interactive=0
[../pam-u2f.c:parse_cfg(71)] cue=1
[../pam-u2f.c:parse_cfg(72)] manual=0
[../pam-u2f.c:parse_cfg(73)] nouserok=0
[../pam-u2f.c:parse_cfg(74)] alwaysok=0
[../pam-u2f.c:parse_cfg(75)] authfile=/etc/u2f_keys
[../pam-u2f.c:parse_cfg(76)] origin=(null)
[../pam-u2f.c:parse_cfg(77)] appid=(null)
[../pam-u2f.c:pam_sm_authenticate(119)] Origin not specified, using 
"pam://durruti"
[../pam-u2f.c:pam_sm_authenticate(130)] Appid not specified, using the same 
value of origin (pam://durruti)
[../pam-u2f.c:pam_sm_authenticate(140)] Maximum devices number not set. Using 
default (24)
[../pam-u2f.c:pam_sm_authenticate(158)] Requesting authentication for user jkur
[../pam-u2f.c:pam_sm_authenticate(169)] Found user jkur
[../pam-u2f.c:pam_sm_authenticate(170)] Home directory for jkur is /home/jkur
[../pam-u2f.c:pam_sm_authenticate(221)] Using authentication file /etc/u2f_keys
[../util.c:get_devices_from_authfile(107)] Authorization line: 
jkur:bz1_psgGoVqj7EF6woABHuu4FSQ_oTJz_5zwzE-mIm_KRib_,047d360b8d4c2077430d1c42ff0f39788ec45e805bdc95a8f6b645d781ac00056b19289a9a1519bdbe94de5f7e4a98858811e7e09e34d4c51763287bd9d971134d
[../util.c:get_devices_from_authfile(112)] Matched user: jkur
[../util.c:get_devices_from_authfile(130)] KeyHandle for device number 1: 
bz1_psgGoVqj7EF6woABHuu4FSQ_oTJz_5zwzE-mIm_KRib_
[../util.c:get_devices_from_authfile(157)] publicKey for device number 1: 
047d360b8d4c2077430d1c42ff0f39788ec45e805bdc95a8f6b645d781ac00056b19289a9a1519bdbe94de5f7e4a98858811e7e09e34d4c51763287bd9d971134d
[../util.c:get_devices_from_authfile(172)] Length of key number 1 is 65
[../util.c:get_devices_from_authfile(200)] Found 1 device(s) for user jkur
Please touch the device.
[../util.c:do_authentication(262)] Device max index is 0
[../util.c:do_authentication(288)] Attempting authentication with device number 
1
[../util.c:do_authentication(310)] Challenge: { "keyHandle": 
"bz1_psgGoVqj7EF6woABHuu4FSQ_oTJz_5zwzE-mIm_KRib_", "version": "U2F_V2", 
"challenge": "frqCM5S0XEXkVNKHoRD96P9jVFLmDI0M-jdLWb_kK0U", "appId": 
"pam:\/\/durruti" }
[../util.c:do_authentication(316)] Response: { "signatureData": 
"AQAAAcgwRQIgRoPNq_hryxmrH6m2VWM5ANsHptaUTefUmUEjtKehr_gCIQDHVex3x3XYKQfXBbTGGDndLklGbh80DkEHff2e9KvKbA",
 "clientData": 
"eyAiY2hhbGxlbmdlIjogImZycUNNNVMwWEVYa1ZOS0hvUkQ5NlA5alZGTG1ESTBNLWpkTFdiX2tLMFUiLCAib3JpZ2luIjogInBhbTpcL1wvZHVycnV0aSIsICJ0eXAiOiAibmF2aWdhdG9yLmlkLmdldEFzc2VydGlvbiIgfQ",
 "keyHandle": "bz1_psgGoVqj7EF6woABHuu4FSQ_oTJz_5zwzE-mIm_KRib_" }
[../pam-u2f.c:pam_sm_authenticate(275)] done. [Erfolg]
root@durruti:/home/jkur# 
root@durruti:/home/jkur# 
root@durruti:/home/jkur# 
root@durruti:/home/jkur# exit
jkur@durruti:~$ sudo su
[sudo] Passwort für jkur: 
debug(pam_u2f): ../pam-u2f.c:89 (parse_cfg): called.
debug

Bug#898075: I'll confirm this occurs for me as well

[Daniel Lakeland]

My particular CD doesn't ask me for multiple entries, it just detects 
the CD's identity correctly, and then segfaults without any input from me.

Bug#902625: libmath-gsl-perl: needs a versioned dependency on libgsl23 (>= 2.5) or so

[gregor herrmann]

On Thu, 28 Jun 2018 21:17:31 +0300, Niko Tyni wrote:

> This package uses symbols from libgsl23 >= 2.5, but that isn't
> reflected in the package dependencies because of #902623 (libgsl23
> missing shlibs information). Once that bug is fixed, libmath-gsl-perl
> needs a rebuild so that the package dependencies get updated. A binNMU
> should be enough but we might as well make a sourceful one and declare
> a build dependency on fixed gsl versions.

Fixed in git (locally), waiting for gsl 2.5+dfsg-4 to hit the
mirrors.
 
Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#902198: octave-odepkg FTBFS with octave 4.4.0

[Sébastien Villemot]

On Fri, Jun 29, 2018 at 03:04:56AM +0800, Drew Parsons wrote:
> On Thu, 28 Jun 2018 20:57:52 +0200 =?iso-8859-1?Q?S=E9bastien?=
> Villemot  wrote:
> > > 
> > > The patch is trivial. Replace all  with  config.h>.
> > > 
> > > config.h was already deprecated, and is now removed in octave
> 4.4.0.
> > 
> > Yes, but then you get many numerical test failures, which are not
> trivial at
> > all to fix…
> > 
> 
> Does 
> https://bitbucket.org/odepkg/odepkg/commits/d4f56c4f3678f7f55d8dc84c96fbd0f98f8d4191
> help?
> 
> Perhaps with 
> https://bitbucket.org/odepkg/odepkg/commits/d60b477d520c762ba4093e1a8f7a036d50b80db1
> 
> 
> Or does latest the upstream git work, should we just grab that?

I remember having tried to apply some upstream patches, but maybe not the
second one that you linked to. In any case, someone has to try again.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

[Eric Valette]

On 6/28/18 7:16 PM, Jiri Palecek wrote:

Are you using xserver 1.20 from unstable or 1.19.6 from testing? I've 
had similar problems when I updated, and they went away when I 
downgraded xserver-xorg-core.


1.20 from unstable.

-- eric

Processed: Bug #902625 in libmath-gsl-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #902625 [libmath-gsl-perl] libmath-gsl-perl: needs a versioned dependency 
on libgsl23 (>= 2.5) or so
Added tag(s) pending.

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

Bug#902625: Bug #902625 in libmath-gsl-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #902625 in libmath-gsl-perl reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/perl-team/modules/packages/libmath-gsl-perl/commit/2d5490dbb050be26831bcb860d70e0627045a285


Make the build dependency on libgsl-dev versioned

to get the correct runtime dependencies with the new 2.5 symbols.

Thanks: Niko Tyni and ci.debian.net for catching this issue.
Closes: #902625



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/902625

Bug#902625: marked as done (libmath-gsl-perl: needs a versioned dependency on libgsl23 (>= 2.5) or so)

[Debian Bug Tracking System]

Your message dated Thu, 28 Jun 2018 21:19:00 +
with message-id 
and subject line Bug#902625: fixed in libmath-gsl-perl 0.39-3
has caused the Debian Bug report #902625,
regarding libmath-gsl-perl: needs a versioned dependency on libgsl23 (>= 2.5) 
or so
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.)


-- 
902625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmath-gsl-perl
Version: 0.39-2
Severity: serious
Control: block -1 with 902623
User: debian-p...@lists.debian.org
Usertags: autopkgtest

This package uses symbols from libgsl23 >= 2.5, but that isn't
reflected in the package dependencies because of #902623 (libgsl23
missing shlibs information). Once that bug is fixed, libmath-gsl-perl
needs a rebuild so that the package dependencies get updated. A binNMU
should be enough but we might as well make a sourceful one and declare
a build dependency on fixed gsl versions.

(This was noticed by the awesome ci.debian.net autopkgtest migration
 checks, which highlighted that the package is installable but broken
 with the libgsl23 version currently in testing.)

 https://ci.debian.net/packages/libm/libmath-gsl-perl/testing/amd64/
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libmath-gsl-perl
Source-Version: 0.39-3

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libmath-gsl-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 28 Jun 2018 22:52:30 +0200
Source: libmath-gsl-perl
Binary: libmath-gsl-perl
Architecture: source
Version: 0.39-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 902625
Description: 
 libmath-gsl-perl - interface to the GNU Scientific Library using SWIG
Changes:
 libmath-gsl-perl (0.39-3) unstable; urgency=medium
 .
   * Team upload.
   * Make the build dependency on libgsl-dev versioned to get the correct
 runtime dependencies with the new 2.5 symbols. Thanks to Niko Tyni and
 ci.debian.net for catching this issue. (Closes: #902625)
Checksums-Sha1: 
 db088444e0852bf1e812bae6029a77aee66ca74f 2378 libmath-gsl-perl_0.39-3.dsc
 dcd5addc7abb9adc8ca17c3c2121f166f6892e0d 16804 
libmath-gsl-perl_0.39-3.debian.tar.xz
Checksums-Sha256: 
 4339ac2754e304f529d2647c5e9de6ec6db52cfc01fa7a2f214c5b4c80e1151f 2378 
libmath-gsl-perl_0.39-3.dsc
 5a9c3bb8903b81c7713c9ea9bedb80fdaaf7656b2fabe478fc574d4eee678558 16804 
libmath-gsl-perl_0.39-3.debian.tar.xz
Files: 
 132ecd8aa4960fe217fd702d07de9bcc 2378 perl optional libmath-gsl-perl_0.39-3.dsc
 0f0a563d19ba6087ecfc30f4c435c647 16804 perl optional 
libmath-gsl-perl_0.39-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAls1TYtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbEOQ//Tq9Awg4Pp55d/yBcjyjuPWfbUAGRR9UEbvoNR1DAY5niXP/Ptb72teaR
iuxVDA0uCjs0tSKKjVZ5ZD7yAapPBWj3yHd1e4GgKS5lQzqDYTGplBOAEHBt9fX8
M5QGkt7HdX6lfTnWNR7g5Gv4c807l3r5Yi6gNpsMcS9eL1o7MyWpszpzdZ5JiSbR
scYsGePrIIhrThZ73N3Eg+cUm2jt0im/Y//dJjr4HAaxv0yyusiJRp25lpAAzkRH
oy1iblbOO7edaXvJunWabybG+6PU1ZTKxMw16ONhjPyndPF0VTQTapJt9ZYYcjc/
Me+9boLGTsRVc40TwZptC/5G5pE/b2xCjHfzaPt+caVy9+eJdZWOr+Gw6PwG3uhz
5RAnSoSN9xemXlpQM9AlXhg46sTPlVn3UtH746ymHEbQ+RDKaFGxwXJVvhRYuxLF
26OE+tTovF3TDQDcxIlcq/yKOklQK/kS1yXxHj6M9xcBbZo7iPb5t0V9p8jxRdol
BX6QDGxP5yT1SZeopk6iy7oCmZAoXCx+xpzcb+GiXMrLVwaD8TcOVetsf241Cm1R
IBZmx5OA/vpdBffjNZvuOsY055qPrUZVfKvzVDxWGSjog3tGZelhXL4oO/plzjAd
akEwKjkZtBRRk43KoZYn9dJtuQIktXGwv/MFpL09rK2OeW+JOuM=
=y4Wt
-END PGP SIGNATURE End Message ---

Processed: RFS: flashplugin-nonfree/1:3.7+nmu1 [NMU] [RC] -- Adobe Flash Player - browser plugin

[Debian Bug Tracking System]

Processing control commands:

> block 851066 by -1
Bug #851066 [flashplugin-nonfree] flashplugin-nonfree: Mismatch between 
detected and available versions (Download file not available at 
people.debian.org)
Bug #851819 [flashplugin-nonfree] ERROR: wget failed to download 
http://people.debian.org/~bartm/...
Bug #853095 [flashplugin-nonfree] flashplugin-nonfree: Unable to update to the 
last flash version
Bug #854467 [flashplugin-nonfree] cannot upgrade
Bug #857765 [flashplugin-nonfree] flashplugin-nonfree has 33 severe security 
flaws, orphaned?
Bug #857766 [flashplugin-nonfree] ERROR: wget failed to download
Bug #85 [flashplugin-nonfree] flashplugin-nonfree: wget tries to download 
old version
Bug #859904 [flashplugin-nonfree] flashplugin-nonfree fails update
Bug #861434 [flashplugin-nonfree] cannot upgrade from 24 to 25
Bug #864030 [flashplugin-nonfree] flashplugin-nonfree: Flashplugin-nonfree 
cannot download flash plugin
851066 was not blocked by any bugs.
851066 was not blocking any bugs.
Added blocking bug(s) of 851066: 902634
851819 was not blocked by any bugs.
851819 was not blocking any bugs.
Added blocking bug(s) of 851819: 902634
853095 was not blocked by any bugs.
853095 was not blocking any bugs.
Added blocking bug(s) of 853095: 902634
854467 was not blocked by any bugs.
854467 was not blocking any bugs.
Added blocking bug(s) of 854467: 902634
857765 was not blocked by any bugs.
857765 was not blocking any bugs.
Added blocking bug(s) of 857765: 902634
857766 was not blocked by any bugs.
857766 was not blocking any bugs.
Added blocking bug(s) of 857766: 902634
85 was not blocked by any bugs.
85 was not blocking any bugs.
Added blocking bug(s) of 85: 902634
859904 was not blocked by any bugs.
859904 was not blocking any bugs.
Added blocking bug(s) of 859904: 902634
861434 was not blocked by any bugs.
861434 was not blocking any bugs.
Added blocking bug(s) of 861434: 902634
864030 was not blocked by any bugs.
864030 was not blocking any bugs.
Added blocking bug(s) of 864030: 902634
> block 889804 by -1
Bug #889804 [flashplugin-nonfree] flashplugin-nonfree: Does not work anymore 
because adobe site have moved to https and script does not hanlde redirect
889804 was not blocked by any bugs.
889804 was not blocking any bugs.
Added blocking bug(s) of 889804: 902634

-- 
851066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851066
851819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851819
853095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853095
854467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854467
857765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857765
857766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857766
85: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=85
859904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859904
861434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861434
864030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864030
889804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889804
902634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: python-pydap: FTBFS and Debci failure with NumPy 1.14

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #900486 [src:python-pydap] python-pydap: FTBFS and Debci failure with NumPy 
1.14
Added tag(s) patch.

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

Bug#900486: python-pydap: FTBFS and Debci failure with NumPy 1.14

[Graham Inggs]

Control: tags -1 + patch

The attached patch adjusts the test output for NumPy 1.14.

However, with this patch in place, python-pydap will need a
build-dependency on python-numpy (>= 1:1.14~) and its autopkgtests
will fail with NumPy 1.13.
Description: Fix FTBFS with NumPy 1.14
Bug-Debian: https://bugs.debian.org/900486
Author: Graham Inggs 
Last-Update: 2018-06-20

--- a/src/pydap/tests/test_responses_ascii.py
+++ b/src/pydap/tests/test_responses_ascii.py
@@ -48,7 +48,7 @@
 ('XDODS-Server', 'pydap/' + __version__),
 ('Content-description', 'dods_ascii'),
 ('Content-type', 'text/plain; charset=ascii'),
-('Content-Length', '440')]))
+('Content-Length', '436')]))
 
 def test_body(self):
 """Test the generated ASCII response."""
@@ -66,8 +66,8 @@
 } SimpleSequence;
 -
 cast.id, cast.lon, cast.lat, cast.depth, cast.time, cast.temperature, cast.salinity, cast.pressure
-"1", 100, -10, 0, -1, 21, 35, 0
-"2", 200, 10, 500, 1, 15, 35, 100
+1, 100, -10, 0, -1, 21, 35, 0
+2, 200, 10, 500, 1, 15, 35, 100
 
 """)
 
--- a/src/pydap/tests/test_wsgi_functions.py
+++ b/src/pydap/tests/test_wsgi_functions.py
@@ -45,8 +45,8 @@
  '-\n'
  'cast.id, cast.lon, cast.lat, cast.depth, cast.time, '
  'cast.temperature, cast.salinity, cast.pressure\n'
- '"1", 100, -10, 0, -1, 21, 35, 0\n'
- '"2", 200, 10, 500, 1, 15, 35, 100\n'
+ '1, 100, -10, 0, -1, 21, 35, 0\n'
+ '2, 200, 10, 500, 1, 15, 35, 100\n'
  '\n')
 
 def test_projection(self):
@@ -161,7 +161,7 @@
  '-\n'
  'cast.id, cast.lon, cast.lat, cast.depth, cast.time, '
  'cast.temperature, cast.salinity, cast.pressure\n'
- '"2", 200, 10, 500, 1, 15, 35, 100\n'
+ '2, 200, 10, 500, 1, 15, 35, 100\n'
  '\n')
 
 def test_subset_with_selection(self):
@@ -185,7 +185,7 @@
  '-\n'
  'cast.id, cast.lon, cast.lat, cast.depth, cast.time, '
  'cast.temperature, cast.salinity, cast.pressure\n'
- '"1", 100, -10, 0, -1, 21, 35, 0\n'
+ '1, 100, -10, 0, -1, 21, 35, 0\n'
  '\n')
 
 def test_projection(self):
@@ -224,7 +224,7 @@
  '-\n'
  'cast.id, cast.lon, cast.lat, cast.depth, cast.time, '
  'cast.temperature, cast.salinity, cast.pressure\n'
- '"1", 100, -10, 0, -1, 21, 35, 0\n'
+ '1, 100, -10, 0, -1, 21, 35, 0\n'
  '\n')
 
 def test_grads_step(self):
--- a/src/pydap/tests/test_wsgi_ssf.py
+++ b/src/pydap/tests/test_wsgi_ssf.py
@@ -68,7 +68,7 @@
 } SimpleSequence;
 -
 cast.id, cast.lon, cast.lat, cast.depth, cast.time, cast.temperature, cast.salinity, cast.pressure
-"2", 200, 10, 500, 1, 15, 35, 100
+2, 200, 10, 500, 1, 15, 35, 100
 
 """)
 

Bug#902638: mwic: FTBFS in buster/sid (dh: unable to load addon python3)

[Santiago Vila]

Package: src:mwic
Version: 0.7.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
dpkg-buildpackage: info: source package mwic
dpkg-buildpackage: info: source version 0.7.4-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Georg Faerber 
 dpkg-source --before-build mwic-0.7.4
 debian/rules clean
dh clean --with=python3
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 9) line 
1.
BEGIN failed--compilation aborted at (eval 9) line 1.

debian/rules:4: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder
but it also fails in reproducible builds:

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

If this is really a bug in one of the build-depends and you have to
use "reassign", please use "affects" as well, so that this is still
visible in the BTS page for this package.

Thanks.

Bug#902637: autoradio: FTBFS in buster/sid

[Santiago Vila]

Package: src:autoradio
Version: 2.8.10-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
dpkg-buildpackage: info: source package autoradio
dpkg-buildpackage: info: source version 2.8.10-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andrea Capriotti 

 dpkg-source --before-build autoradio-2.8.10
 fakeroot debian/rules clean
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
dh_auto_clean: Please use the third-party "pybuild" build system instead of 
python-distutils
dh_auto_clean: This feature will be removed in compat 12.
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
python setup.py clean -a
django_extensions is not installed; I do not use it
Traceback (most recent call last):
  File "setup.py", line 16, in 
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 108, in 
populate
app_config.import_models()
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 202, in 
import_models
self.models_module = import_module(models_module_name)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/<>/autoradio/jingles/models.py", line 4, in 
from autoradio.autoradio_config import *
  File "/<>/autoradio/autoradio_config.py", line 75, in 
locale.setlocale(locale.LC_ALL, config['autoradiod']['locale'])
  File "/usr/lib/python2.7/locale.py", line 581, in setlocale
return _setlocale(category, locale)
locale.Error: unsupported locale setting
dh_auto_clean: python setup.py clean -a returned exit code 1
debian/rules:5: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 1
make[1]: Leaving directory '/<>'
debian/rules:3: recipe for target 'clean' failed
make: *** [clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder
but it also fails in reproducible builds:

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

In this case the error is different: "ImportError: No module named magic".

If this is really a bug in one of the build-depends and you have to
use "reassign", please use "affects" as well, so that this is still
visible in the BTS page for this package.

Thanks.

Bug#902640: magit: FTBFS if machine has no domain

[Santiago Vila]

Package: src:magit
Version: 2.13.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed.
BuIld log follows:


[...]
dpkg-buildpackage: info: source package magit
dpkg-buildpackage: info: source version 2.13.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Rémi Vanicat 
 dpkg-source --before-build magit-2.13.0
 fakeroot debian/rules clean
dh clean --with elpa
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/<>'
make[2]: Entering directory '/<>/lisp'
Cleaning lisp/*...
make[2]: Leaving directory '/<>/lisp'
make[2]: Entering directory '/<>/Documentation'
Cleaning Documentation/*...
make[2]: Leaving directory '/<>/Documentation'
Cleaning...
make[1]: Leaving directory '/<>'
   debian/rules override_dh_clean
make[1]: Entering directory '/<>'
dh_clean
make[1]: Leaving directory '/<>'
 debian/rules build-indep
dh build-indep --with elpa
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
make info
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>/Documentation'
Generating magit.info
Generating dir
make[3]: Leaving directory '/<>/Documentation'
make[2]: Leaving directory '/<>'
do not run make
make[1]: Leaving directory '/<>'
   debian/rules override_dh_elpa_test
make[1]: Entering directory '/<>'
make test
make[2]: Entering directory '/<>'
Loading /<>/t/magit-tests.el (source)...
Cannot determine Magit’s version (error "/<>/lisp/magit.el" repo 
static elpa debug)
Running 16 tests (2018-06-22 15:45:52+)
   passed   1/16  magit--with-safe-default-directory
Keeping test directory:
  /tmp/magit-244342AY/
Test magit-get backtrace:
  (let ((dir (file-name-as-directory (make-temp-file "magit-" t))) (pr
  (lambda nil (let ((dir (file-name-as-directory (make-temp-file "magi
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test magit-get nil (lambda nil (let ((di
  ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test m
  ert-run-tests(t #[385 "\306\307\"\203GDDIR>>'
debian/rules:22: recipe for target 'override_dh_elpa_test' failed
make[1]: *** [override_dh_elpa_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


There is an interesting line saying "unable to auto-detect email address"
where it may be seen that my machine has no domain. However, having a
domain has never been a requirement to build Debian packages. In fact,
one might ask: The fact that such test fails means the package will
not work in machines not having a domain?

To reproduce, please try "dpkg-buildpackage -A" on a machine not
having a domain.

Thanks.

Processed: severity of 871613 is important, tagging 871613

[Debian Bug Tracking System]

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

> severity 871613 important
Bug #871613 [general] general: Kernel Panic caused by smp.c:127 
check_preempt_curr
Severity set to 'important' from 'critical'
> tags 871613 + moreinfo
Bug #871613 [general] general: Kernel Panic caused by smp.c:127 
check_preempt_curr
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#902545: sagemath: sage 8.2-4 fails to start with error /usr/bin/env: ‘sage-python23’: No such file or directory

[Gilles Crèvecœur]

Hi,

I have looked for a get around for this bug.
It seems due to some files in 
/usr/share/sagemath/bin
The command:
 grep sage-python23 /usr/share/sagemath/bin/*
yields:
/usr/share/sagemath/bin/sage-eval:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-fixdoctests:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-ipython:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-list-packages:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-preparse:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-run-cython:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-runtests:#!/usr/bin/env sage-python23
/usr/share/sagemath/bin/sage-startuptime.py:#!/usr/bin/env sage-python23

For the moment, I suggest to symlink
the file: 
sage-python23 to sage-python
in the directory /usr/share/sagemath/bin with commands:
cd /usr/share/sagemath/bin && ln -s sage-python sage-python23

It seems to work for me.

Cheers.
--
Gilles Crèvecœur

Bug#896630: marked as done (FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive')

[Debian Bug Tracking System]

Your message dated Fri, 29 Jun 2018 00:48:57 +
with message-id 
and subject line Bug#896630: fixed in python-click 6.7-5
has caused the Debian Bug report #896630,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
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.)


-- 
896630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinx
Version: 1.7.2-1
Severity: serious
Control: affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat 
src:julia src:mako src:prospector src:pyevolve src:pymvpa2 
src:python-cryptography src:python-expyriment src:python-numpy src:python-scipy

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/alembic.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bcfg2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bottleneck.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heat.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/julia.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mako.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prospector.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyevolve.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pymvpa2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/python-cryptography.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-expyriment.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-numpy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-scipy.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sqlalchemy.html

Example (from alembic):

...
   debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/build/1st/alembic-0.9.7'
sphinx-build -b html docs/build 
/build/1st/alembic-0.9.7/debian/alembic/usr/share/doc/alembic/html
Running Sphinx v1.7.2

Extension error:
Could not import extension changelog (exception: cannot import name 'Directive')
make[1]: *** [debian/rules:13: override_dh_sphinxdoc] Error 2
--- End Message ---
--- Begin Message ---
Source: python-click
Source-Version: 6.7-5

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

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated python-click 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: Thu, 28 Jun 2018 20:37:56 -0400
Source: python-click
Binary: python-click python3-click python-click-doc
Architecture: source
Version: 6.7-5
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau 
Changed-By: Alexandre Viau 
Description:
 python-click - Wrapper around optparse for command line utilities - Python 2.7
 python-click-doc - Wrapper around optparse for command line utilities - 
documentatio
 python3-click - Wrapper around optparse for command line utilities - Python 3.x
Closes: 896630
Changes:
 python-click (6.7-5) unstable; urgency=medium
 .
   * Sphinx 1.7 support. (Closes: #896630)
Checksums-Sha1:
 fe79f0fa965ca1cb7d906c1896c2aadf6f33e35c 2261 python-click_6.7-5.dsc
 5e526bd9a07438ad1653c32b773df91be1b08868 3916 python-click_6.7-5.debian.tar.xz
 9e189abc1e25ab9dbbc9e2f02b82998a9a1b1798 6937 
python-click_6.7-5_source.buildinfo
Checksums-Sha256:
 6c60755a85ac47cb2b329cb2a948a8d57370b9dde1a5931153e6dafba6e7c1b8 2261 
python-click_6.7-5.dsc
 232da520c25a91562f31f243983879d8cc72999ee5f7d75cb22771600a6526d1 3916 
python-click_6.7-5.debian.tar.xz
 504eb518869b2200fcb23ea2eb32d1892206aa0844f2a5f80a72779b03af64a3 6937 
python-click_6.7-5_source.buildinfo
Files:
 8d195341b8323624675c70a4ddf54910 2261 python optional python-click_6.7-5.dsc
 d749fe00edb011388f536f558968e7a9 3916 python optional 
python-click_6.7-5.debian.tar.xz
 859e2212920eeaeb88e1f6da

Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

[Scott Kitterman]

I had hoped to work on this this week.  It hasn't happened and it's not going 
to.

In the end, I the Qt4 stuff has to go, so I wouldn't wait on this for the 
transition.

Scott K

On June 28, 2018 1:23:31 PM UTC, "Lisandro Damián Nicanor Pérez Meyer" 
 wrote:
>El miércoles, 27 de junio de 2018 16:25:23 -03 Niko Tyni escribió:
>> On Tue, Jun 19, 2018 at 10:05:09AM -0300, Lisandro Damián Nicanor
>Pérez 
>Meyer wrote:
>[snip] 
>> > > Copying the debconf maintainers as well.
>> > 
>> > Hi! I have just pinged the rest of the Qt/KDE team for thoughts, as
>I have
>> > never used this myself so I might not have a good view on the
>issue.
>> > 
>> > I'll try to follow up soon, but please ping me again (IRC is valid
>too) if
>> > I don't cam up with a reply in, let's say, 5 to 7 days.
>> 
>> Hi, any news here? FWIW Perl 5.28.0 final was released recently and
>is
>> now in experimental. It would be great to get this issue moving
>forward
>> one way or another.
>
>For what I know Scott (CCed) was waiting on a reply from someone wrt
>this. 
>That's all I could gather I'm afraid.

Processed: tagging 899725

[Debian Bug Tracking System]

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

> tags 899725 + pending
Bug #899725 [src:wml] wml: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: found 899725 in 2.4.1ds1-2

[Debian Bug Tracking System]

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

> found 899725 2.4.1ds1-2
Bug #899725 [src:wml] wml: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
Marked as found in versions wml/2.4.1ds1-2.
> thanks
Stopping processing here.

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

Bug#899725: marked as done (wml: Invalid maintainer address pkg-wml-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 29 Jun 2018 01:49:00 +
with message-id 
and subject line Bug#899725: fixed in wml 2.0.12ds1-11
has caused the Debian Bug report #899725,
regarding wml: Invalid maintainer address 
pkg-wml-maintain...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wml
Version: 2.0.12ds1-10
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of wml,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package wml since the list address
pkg-wml-maintain...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-wml-maintain...@lists.alioth.debian.org is 4.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: wml
Source-Version: 2.0.12ds1-11

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 29 Jun 2018 03:31:52 +0200
Source: wml
Binary: wml
Architecture: source amd64
Version: 2.0.12ds1-11
Distribution: unstable
Urgency: medium
Maintainer: Axel Beckert 
Changed-By: Axel Beckert 
Description:
 wml- off-line HTML generation toolkit
Closes: 899725
Changes:
 wml (2.0.12ds1-11) unstable; urgency=medium
 .
   * debian/watch: Remove pagemangle again, now that uscan got fixed. (See
 #833779 for details.)
   * Update Vcs-* headers for packaging repository moving to Salsa.
   * Drop one-man-team from Maintainer field, set myself personally there
 instead. (Closes: #899725)
   * Declare compliance with Debian Policy 4.1.4.
 + Update debian/copyright format URL to HTTPS.
   * Mention new github.com repository in debian/copyright.
   * Drop unused lintian override manpage-has-errors-from-man.
   * Bump debhelper compatibility level to 11.
 + Update versioned build-dependency on debhelper accordingly.
 + Drop --with autotools-dev from debian/rules.
 + Drop autotools-dev from build-dependencies.
 + Use DH_COMPAT=10 for configure. (Doesn't know about --runstatedir.)
 + Don't run tests in parallel, pass --no-parallel to dh_auto_test.
   * Fix spelling error in do-not-build-all-embedded-code-copies.diff.
Checksums-Sha1:
 ea235

Bug#899613: mokomaze: Invalid maintainer address pkg-fso-ma...@lists.alioth.debian.org

[Paul Wise]

On Thu, 24 May 2018 09:44:13 +0200 (CEST) Christoph Biedl wrote:

> This affects your package mokomaze since the list address
> pkg-fso-ma...@lists.alioth.debian.org used in the Maintainer: field was
> not transferred to the alioth-lists service that provides a
> continuation for the lists in the @lists.alioth.debian.org domain.

I'll probably move this to the games team during DebCamp18.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#902646: python3-pexpect: Failure to install with Python 3.7

[Austin Roach]

Package: python3-pexpect
Version: 4.2.1-1
Severity: serious

Installation fails with python3.7 installed:

Setting up python3-pexpect (4.2.1-1) ...
  File "/usr/lib/python3/dist-packages/pexpect/spawnbase.py"
def expect(self, pattern, timeout=-1, searchwindowsize=-1, async=False):
SyntaxError: invalid syntax

'async' is a reserved keyword in Python 3.7. This issue has been
previously reported upstream, and was fixed in version 4.3 of
pexpect.[1] The current upstream version is 4.6.

[1] https://github.com/pexpect/pexpect/issues/453

Bug#894757: (No Subject)

[Fjfj109]

Judging from the reply ... is this actually fixed now and the bug just isn't 
closed or is it not fixed?

Bug#902650: SyntaxError during package configuration with Python 3.7

[Andrey Rahmatullin]

Package: diffoscope
Version: 97
Severity: grave

Setting up diffoscope (97) ...
  File "/usr/lib/python3/dist-packages/diffoscope/comparators/json.py", line 41
file.magic_file_type.startswith(x)
^
SyntaxError: Generator expression must be parenthesized

  File "/usr/lib/python3/dist-packages/diffoscope/presenters/formats.py", line
112
x['klass'].supports_visual_diffs for x in self.config.values(),
^
SyntaxError: Generator expression must be parenthesized

dpkg: error processing package diffoscope (--configure):
 installed diffoscope package post-installation script subprocess returned
error exit status 1


>From the 3.7 release notes
(https://docs.python.org/3.7/whatsnew/3.7.html#changes-in-python-behavior):

"""
Due to an oversight, earlier Python versions erroneously accepted the following
syntax:

f(1 for x in [1],)

class C(1 for x in [1]):
pass
Python 3.7 now correctly raises a SyntaxError, as a generator expression always
needs to be directly inside a set of parentheses and cannot have a comma on
either side, and the duplication of the parentheses can be omitted only on
calls.
"""



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

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

Versions of packages diffoscope depends on:
ii  libpython3.6-stdlib3.6.6-1
ii  python33.6.6-1
ii  python3-distro 1.0.1-2
ii  python3-distutils  3.6.6-1
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  2:0.4.15-1
ii  python3-pkg-resources  39.2.0-1

Versions of packages diffoscope recommends:
pn  abootimg 
ii  acl  2.2.52-3+b1
pn  apktool  
pn  binutils-multiarch   
ii  bzip21.0.6-8.1
ii  caca-utils   0.99.beta19-2+b3
ii  colord   1.3.3-2
pn  db-util  
ii  default-jdk [java-sdk]   2:1.10-67
ii  default-jdk-headless 2:1.10-67
pn  device-tree-compiler 
pn  docx2txt 
ii  e2fsprogs1.44.2-1
pn  enjarify 
pn  fontforge-extras 
pn  fp-utils 
ii  genisoimage  9:1.1.11-3+b2
ii  gettext  0.19.8.1-6+b1
pn  ghc  
ii  ghostscript  9.22~dfsg-2.1
pn  giflib-tools 
pn  gnumeric 
ii  imagemagick  8:6.9.9.39+dfsg-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.9.39+dfsg-1
pn  jsbeautifier 
pn  libarchive-tools 
pn  llvm 
ii  mono-utils   4.6.2.7+dfsg-2
pn  odt2txt  
pn  oggvideotools
ii  openjdk-10-jdk [java-sdk]10.0.1+10-4
ii  openssh-client   1:7.7p1-2
pn  pgpdump  
ii  poppler-utils0.63.0-2
pn  procyon-decompiler   
pn  python3-argcomplete  
pn  python3-binwalk  
ii  python3-debian   0.1.32
pn  python3-defusedxml   
pn  python3-guestfs  
pn  python3-jsondiff 
pn  python3-progressbar  
pn  python3-pyxattr  
ii  python3-tlsh 3.4.4+20151206-1+b3
pn  r-base-core  
pn  sng  
ii  sqlite3  3.24.0-1
ii  squashfs-tools   1:4.3-6
ii  tcpdump  4.9.2-3
ii  unzip6.0-21
ii  vim-common   2:8.1.0089-1
pn  xmlutils 
ii  xxd  2:8.1.0089-1
ii  xz-utils 5.2.2-1.3

Versions of packages diffoscope suggests:
ii  libjs-jquery  3.2.1-1

-- debconf-show failed

Bug#902015: systemd-cron: fails to upgrade from 'wheezy' - trying to overwrite /usr/bin/crontab

[Alexandre Detiste]

Hi,

I feel like the severity of this bug is much too high,
as it only concerns bcron-run versus systemd-cron;
not vixie cron (the santdard implementation) vs systemd-cron.

I don't see how to cleanly solve it.

Should any cron implemnetation & breaks against
all the other cron implementation ?

Or better against virtual package cron-deamon ?

Also, why a bug between wheezy and jessie should affect a package in
the next release ?

"Your package has been marked for autoremoval from testing."


BTW: anyone interrested into this can upload a new version and
take car of it; I only ever power on my dev- computer once in a moon
when I have to rip new CD's.


Greetings,

Alexandre


2018-06-21 15:40 GMT+02:00 Andreas Beckmann :
>
> Package: systemd-cron
> Version: 1.3.1+ds1-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'wheezy'.
> It installed fine in 'wheezy', then the upgrade to 'jessie' 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 systemd-cron.
>   Preparing to unpack .../systemd-cron_1.3.1+ds1-2_all.deb ...
>   Unpacking systemd-cron (1.3.1+ds1-2) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/systemd-cron_1.3.1+ds1-2_all.deb (--unpack):
>trying to overwrite '/usr/bin/crontab', which is also in package bcron-run 
> 0.09-13
>   Errors were encountered while processing:
>/var/cache/apt/archives/systemd-cron_1.3.1+ds1-2_all.deb
>
>
> cheers,
>
> Andreas