Bug#938502: marked as done (smart: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 06:46:12 +
with message-id 
and subject line Bug#946692: Removed package(s) from unstable
has caused the Debian Bug report #938502,
regarding smart: Python2 removal in sid/bullseye
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.)


-- 
938502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:smart
Version: 1.4-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:smart

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.4-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#885481: marked as done (smartpm: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 06:46:12 +
with message-id 
and subject line Bug#946692: Removed package(s) from unstable
has caused the Debian Bug report #885481,
regarding smartpm: Depends on unmaintained pygtk
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.)


-- 
885481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smartpm
Version: 1.4-2
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.4-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936608: marked as done (gextractwinicons: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 06:46:50 +
with message-id 
and subject line Bug#946693: Removed package(s) from unstable
has caused the Debian Bug report #936608,
regarding gextractwinicons: Python2 removal in sid/bullseye
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.)


-- 
936608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gextractwinicons
Version: 0.3.1-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:gextractwinicons

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.3.1-1.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#941868: marked as done (gextractwinicons: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 06:46:50 +
with message-id 
and subject line Bug#946693: Removed package(s) from unstable
has caused the Debian Bug report #941868,
regarding gextractwinicons: Depends on unmaintained pygtk
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.)


-- 
941868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gextractwinicons
Version:  0.3.1-1.1
Severity: serious
Control: block 885135 by -1
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid bullseye

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011. Also, it uses Python2 and Python2 is being removed
from Debian.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Debian 11 "Bullseye" release as
we're going to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.3.1-1.1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#943976: marked as done (Should smart be removed?)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 06:46:12 +
with message-id 
and subject line Bug#946692: Removed package(s) from unstable
has caused the Debian Bug report #943976,
regarding Should smart be removed?
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.)


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

Should smart be removed? It depends on Python 2 and pygtk, which are going away,
and it's dead upstream (last release from 2011).

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 1.4-2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#946648: crash report log

[Peter Newey]

Running for 80 minutes ok then another crash :

peter@peter-mate:~$ chromium
[30442:30442:1214/051955.275889:ERROR:vaapi_wrapper.cc(417)] vaInitialize 
failed: unknown libva error
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[32194:1:1214/052005.144949:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32194:1:1214/052005.146052:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32194:1:1214/052005.156409:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32194:1:1214/052005.159326:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.052325:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.065720:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.078173:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.080282:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.143199:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.144240:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
[32167:1:1214/052006.634797:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32167:1:1214/052006.636714:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.174953:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.177207:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.180813:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.182072:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.183491:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.184835:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.186613:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.187528:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.189257:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[32221:1:1214/052008.190141:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
Fontconfig error: Cannot load default config file

Processed: owner 874915

[Debian Bug Tracking System]

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

> owner 874915 !
Bug #874915 [src:heimdall-flash] [heimdall-flash] Future Qt4 removal from Buster
Owner recorded as Nicholas D Steeves .
> thanks
Stopping processing here.

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

Bug#944320: marked as done (platform.linux_distribution is gone in 3.8)

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 05:50:18 +
with message-id 
and subject line Bug#944320: fixed in python-blosc 1.8.1+ds1-1
has caused the Debian Bug report #944320,
regarding platform.linux_distribution is gone in 3.8
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.)


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

Package: src:python-blosc
Version: 1.7.0+ds1-2
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

platform.linux_distribution is gone in 3.8.

patch at
http://launchpadlibrarian.net/450341600/python-blosc_1.7.0+ds1-2_1.7.0+ds1-2ubuntu1.diff.gz

or use the python3-distro package.
--- End Message ---
--- Begin Message ---
Source: python-blosc
Source-Version: 1.8.1+ds1-1

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated python-blosc 
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, 13 Dec 2019 23:40:55 +0100
Source: python-blosc
Architecture: source
Version: 1.8.1+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard Flaget Aasen 
Closes: 944320
Changes:
 python-blosc (1.8.1+ds1-1) unstable; urgency=medium
 .
   * QA upload
   * New upstream version 1.8.1+ds1
   * Create 0002-platform-linux_distribution-is-gone-in-python-3.8.patch
 closes: #944320
   * Added minimum version on libblosc-dev in b-d
   * Bump dh to 12
   * Remove python2 package under recommends, for doc package.
   * Change copyright from Expat to BSD-3 for upstream files.
Checksums-Sha1:
 59d0bd0d61476a6878846bf2b4975cafbcf7fc78 2359 python-blosc_1.8.1+ds1-1.dsc
 37c48f8e5987b480007dd85d104f062151c8bd35 82916 
python-blosc_1.8.1+ds1.orig.tar.xz
 ca9f7ce72b855ac4da4c2cfc24923eeeb4939090 5440 
python-blosc_1.8.1+ds1-1.debian.tar.xz
 f19ea106f8023e8653e7d708d1e3eb6f58ff8444 6380 
python-blosc_1.8.1+ds1-1_source.buildinfo
Checksums-Sha256:
 ded4a897bb1255ca61f53b23ee87966d4d8e90180638393505dc53738b94e122 2359 
python-blosc_1.8.1+ds1-1.dsc
 0ea68d3fcd76a11a2982e05468279fba4b1923639a8cbe9f0898023a077f5770 82916 
python-blosc_1.8.1+ds1.orig.tar.xz
 2e9b08977f74d50c8b3e32c6b31e8b353a2f9832af6ed5454e2cb970fe736463 5440 
python-blosc_1.8.1+ds1-1.debian.tar.xz
 987e351d4b3e8818f53fc891fd8d4b94261474e7fa9c861c376b1d0874795255 6380 
python-blosc_1.8.1+ds1-1_source.buildinfo
Files:
 43e8b9deff9e4407c4a257156cda074c 2359 python optional 
python-blosc_1.8.1+ds1-1.dsc
 5eed5878716dc73a1205abfeef592ec9 82916 python optional 
python-blosc_1.8.1+ds1.orig.tar.xz
 20dede567988609f91040e8c6a807168 5440 python optional 
python-blosc_1.8.1+ds1-1.debian.tar.xz
 e77d8d1fcab5926488048f90672d74d9 6380 python optional 
python-blosc_1.8.1+ds1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl30clsACgkQweDZLphv
fH4vWRAAw1NLdINXaTsgPSHx4+ufwGD5JXsl3VwZUZdIMl0ObZz3TRTVwbQv8Lwi
hiN8liausfSTU0eTuwug79IgPrDr7EGry82ABg5ZpJSjIGS8cSQBJQLh1VGPdgkG
Up7IqirfG9aU4hiOR7I1Ql/pabaOkjTE+0k0LPq1jlhkaR5q59hiYb614aelrGTU
1UShjTLST2mrTKsTPcT0L+hraCXSCQ+jwUfopOEx5vHdqYF1Vh9jAISTGeCwFNbO
4xh2q70xROx9PGM+7i53go7fNZTrcFxh9/y1wwTjCCYxl6e5+yqMktzn8efTlfSU
Rm+Ch1RYbLSMlU4MZU6iItLX6Ypaq2pj5cdm+pWvYcbknpzALj/a6vEDSOyI1uiv
aBvNp7fEy8qDQ0oecflq+u3BaySOsEZVtN9p7yVYw9YlkIpfLZ6vPqpEaygl4stt
q2eM+HXZPRmiCOI59idu4HTjdJ+4TVFXKiBspT+r/WlsOMlihaIrvAfbPoJU2puX
txJhZjzfydka+4EHGNXpTeoTqlalH7S42sK9BPdgLvqDFz1F0NdLiiWzEQPVxtRn
Jl17tWEdSJ/o7ZffiZOgMlxO/KRqeREwxflGDTll2fLr38yN8p8LRIhxoq9NqSC6
MiX81c2QP5nj0XRk8F3p5UDbfC2NZbW7wlIc+oSzH4EvnuQoFIw=
=Lehk
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 945864 https://github.com/YJesus/Unhide/pull/1
Bug #945864 {Done: Thiago Andrade Marques } [unhide] 
unhide[208429]: segfault at 7ffd06cfec58 ip 55c15aa077d3 sp 
7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
Set Bug forwarded-to-address to 'https://github.com/YJesus/Unhide/pull/1'.
>
End of message, stopping processing here.

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

Bug#945864: marked as done (unhide[208429]: segfault at 7ffd06cfec58 ip 000055c15aa077d3 sp 00007ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000])

[Debian Bug Tracking System]

Your message dated Sat, 14 Dec 2019 00:34:16 +
with message-id 
and subject line Bug#945864: fixed in unhide 20130526-4
has caused the Debian Bug report #945864,
regarding unhide[208429]: segfault at 7ffd06cfec58 ip 55c15aa077d3 sp 
7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
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.)


-- 
945864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unhide
Version: 20130526-3
Severity: grave
Justification: renders package unusable



Since 1-3 weeks unhide segfaults every time:

Nov 30 01:39:48 heisenberg kernel: unhide[208429]: segfault at 7ffd06cfec58 ip 
55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
Nov 30 01:39:48 heisenberg kernel: Code: 00 48 89 45 c8 31 c0 48 63 05 5d 98 00 
00 48 8d 04 85 0f 00 00 00 48 83 e0 f0 48 29 c4 48 89 65 98 48 29 c4 31 c0 48 
89 65 90  d8 3e 00 00 31 c0 66 0f 1f 44 00 00 48 8b 4d 98 48 8b 55 90 c7


Cheers,
Chris.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages unhide depends on:
ii  libc6  2.29-3

unhide recommends no packages.

Versions of packages unhide suggests:
ii  rkhunter  1.4.6-7

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: unhide
Source-Version: 20130526-4

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

Debian distribution maintenance software
pp.
Thiago Andrade Marques  (supplier of updated unhide 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Dec 2019 18:06:58 -0300
Source: unhide
Architecture: source
Version: 20130526-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Thiago Andrade Marques 
Closes: 945864
Changes:
 unhide (20130526-4) unstable; urgency=medium
 .
   * Team Upload.
 .
   [ Thiago Andrade Marques ]
   * debian/control:
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Bumped Standards-Version to 4.4.1.
   * debian/copyright: Updated packaging copyright data.
   * debian/patch/allocate-pid-arrays-from-heap.patch: Added to fix a stack
 exhausting. Thanks to Bernhard Übelacker .
 (Closes: #945864)
 .
   [ Joao Eriberto Mota Filho ]
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 12.
 .
   [ Samuel Henrique ]
   * Add salsa-ci.yml.
   * Use my d.o email address in debian/{control,patches/fix-man}.
Checksums-Sha1:
 68a6c8eb87e93ab862657a36959b188aaa3460af 1888 unhide_20130526-4.dsc
 c405d01792827c48a233a2fdfe3d83cd8ce415fb 7312 unhide_20130526-4.debian.tar.xz
 1f9d337c71c473e443cd068b90839ee74de11815 5093 
unhide_20130526-4_source.buildinfo
Checksums-Sha256:
 92e1c705ebbdc9180b64888ba34920d918ddd3f8ecf7cc94db57eae12f45cb8c 1888 
unhide_20130526-4.dsc
 f0bc4f8468c30d9e5306d3698a79298d4dd6ef55ca872c7b8750561adaa10aed 7312 
unhide_20130526-4.debian.tar.xz
 9c3d95b6fc2af78d5814cd93b5b2dc3128e1f096c3ed671bd6b651f84717e9f5 5093 
unhide_20130526-4_source.buildinfo
Files:
 81241a49407469ac78ed8301ce76a862 1888 admin optional unhide_20130526-4.dsc
 bea5e259df9eafaab8ed0c80ab4590a1 7312 admin optional 
unhide_20130526-4.debian.tar.xz
 fecba3733184213bc22352f7a479c7fe 5093 admin optional 
unhide_20130526-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl30K2MACgkQ3mO5xwTr
6e+Q+A/+JB3/q0BRFRP8TxGgXkvG0Bms93s6yyaoEbUU8cbdXaDGqW5TrywMJybY
/3243hNQlEnif8HYt1g/4j+CY8JWdMprKqq9rmqfQ1CzEbaQkAawCSCJofolFnEk

Bug#945263: f2py3.8 fails with "Entry point not found" exception

[Andreas Beckmann]

Followup-For: Bug #945263
Control: found -1 1:1.17.4-4

This change caused the arch:all build to fail:
https://buildd.debian.org/status/fetch.php?pkg=numpy=all=1%3A1.17.4-4=1576093048=0

[...]
# tweak the entry_points list to include all supported versions
for v in 3.8 3.7; do \
if ! grep $v ; \
then \
echo "f2py$v = numpy.f2py.f2py2e:main" >>  ; \
fi; \
done
/bin/sh: 4: Syntax error: ";" unexpected
make[1]: *** [debian/rules:51: override_dh_python3] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: binary-indep] Error 2


Andreas

Processed: Re: f2py3.8 fails with "Entry point not found" exception

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:1.17.4-4
Bug #945263 {Done: Sandro Tosi } [src:numpy] f2py3.8 fails 
with "Entry point not found" exception
Marked as found in versions numpy/1:1.17.4-4; no longer marked as fixed in 
versions numpy/1:1.17.4-4 and reopened.

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

Bug#946289: ufw: fails to start with iptables 1.8.4

[Jamie Strandboge]

On Fri, 06 Dec 2019, Antonio Terceiro wrote:

> Package: ufw
> Version: 0.36-1
> Severity: grave
> Justification: renders package unusable
> 
> This started since the latest upgrade of iptables (1.8.4). Reverting to
> 1.8.3 (testing) makes it work again.
> 
> This is the contents of the journal for ufw.service:
> 
> -- Logs begin at Thu 2019-12-05 14:15:18 -03, end at Fri 2019-12-06 13:45:35 
> -03. --
> dez 05 14:15:18 lemur ufw-init[455]: Bad argument `DROP'
> dez 05 14:15:18 lemur ufw-init[455]: Error occurred at line: 4
> dez 05 14:15:18 lemur ufw-init[455]: Try `iptables-restore -h' or 
> 'iptables-restore --help' for more information.

I can confirm this. It looks like iptables-restore and iptables6-restore
in 1.8.4 has broken -n behavior with the nft varieties.

Create some simple policy:

$ cat /tmp/pol
*filter
# builtin chains
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
COMMIT

With 1.8.2-4 on buster:

$ cat /tmp/pol | sudo /usr/sbin/iptables-legacy-restore -n
$ cat /tmp/pol | sudo /usr/sbin/iptables-nft-restore -n
$

With 1.8.4-1 on sid:
$ cat /tmp/pol | sudo /usr/sbin/iptables-legacy-restore -n
$ cat /tmp/pol | sudo /usr/sbin/iptables-nft-restore -n
Bad argument `ACCEPT'
Error occurred at line: 4
Try `iptables-nft-restore -h' or 'iptables-nft-restore --help' for more 
information.

-- 
Email: ja...@strandboge.com
IRC:   jdstrand

Processed: reassign 946289 iptables

[Debian Bug Tracking System]

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

> reassign 946289 iptables
Bug #946289 [ufw] ufw: fails to start with iptables 1.8.4
Bug reassigned from package 'ufw' to 'iptables'.
No longer marked as found in versions ufw/0.36-1.
Ignoring request to alter fixed versions of bug #946289 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#933019: marked as done (bareos ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 21:34:12 +
with message-id 
and subject line Bug#933019: fixed in bareos 17.2.7-2.1
has caused the Debian Bug report #933019,
regarding bareos ftbfs in unstable
to be marked as done.

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

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


-- 
933019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bareos
Version: 17.2.7-2
Severity: serious
Tags: sid bullseye

seen on all architectures.

[...]
/<>/libtool --silent --tag=CXX --mode=link /usr/bin/g++
-Wl,-z,relro -Wl,-z,now -shared autoxflate-sd.lo -o
autoxflate-sd.la -rpath /usr/lib/bareos/plugins -module -export-dynamic
-avoid-version -L../../lib -lbareos
gfapi_device.c: In member function ‘virtual bool 
gfapi_device::d_truncate(DCR*)’:
gfapi_device.c:550:34: error: too few arguments to function ‘int
glfs_ftruncate(glfs_fd_t*, off_t, glfs_stat*, glfs_stat*
)’
   if (glfs_ftruncate(m_gfd, 0) != 0) {
  ^
In file included from ../backends/gfapi_device.h:31,
 from gfapi_device.c:34:
/usr/include/glusterfs/api/glfs.h:768:1: note: declared here
 glfs_ftruncate(glfs_fd_t *fd, off_t length, struct glfs_stat *prestat,
 ^~
make[2]: *** [Makefile:217: gfapi_device.lo] Error 1
make[2]: Leaving directory '/<>/src/stored/backends'
make[1]: *** [GNUmakefile:167: src/stored/backends] Error 2
--- End Message ---
--- Begin Message ---
Source: bareos
Source-Version: 17.2.7-2.1

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

Debian distribution maintenance software
pp.
Jakob Haufe  (supplier of updated bareos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Dec 2019 20:32:36 +
Source: bareos
Architecture: source
Version: 17.2.7-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bareos Packaging Team 
Changed-By: Jakob Haufe 
Closes: 874839 933019
Changes:
 bareos (17.2.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adjust for GlusterFS API change (Closes: #933019)
   * Switch to Qt5 (Closes: #874839)
Checksums-Sha1:
 7f37e4c9cc479175fb0fcac008b0e48323e4cf60 4384 bareos_17.2.7-2.1.dsc
 9c90573618ef5ec8f3767cef97915e9d548ff9d0 43980 bareos_17.2.7-2.1.debian.tar.xz
 d95048f0f254257cc426468f94a1728604bb5dbf 13829 
bareos_17.2.7-2.1_source.buildinfo
Checksums-Sha256:
 5ffcee14dac9910772be9c7baaa6345cb13672dded7865c50b24c9070c650168 4384 
bareos_17.2.7-2.1.dsc
 840c5dc4a033694b625c2add599738b42beeb979d3985cf91a2cc303ea681576 43980 
bareos_17.2.7-2.1.debian.tar.xz
 2cad9bc7d19df3636c762a32f8be67daaf50c0fec527bccae6440bac52be3a68 13829 
bareos_17.2.7-2.1_source.buildinfo
Files:
 6afc6e546898d6b58df07fa8014cb87f 4384 admin optional bareos_17.2.7-2.1.dsc
 be4f27b8c0b3e19c588f59eee8d05a5c 43980 admin optional 
bareos_17.2.7-2.1.debian.tar.xz
 b71b11858da47516eb378010f8622bb9 13829 admin optional 
bareos_17.2.7-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAl3tXsIACgkQTPKyGPVN
rj02gBAAnP+j3GV7ikJHjyuvSY9sHOlb/+HJE/YGIWtrkSI9IM53B1/nZ7qOF7tp
EsZjzwXcTJK1X/xxxURYU/czfHw64GM65twW2rvNzKNDyBfmUem+666tiY/Cz0UI
ZFNwol1sMeLJP2YxIHxT4AzBvAmQRHHII/gsV9kOLKTncOa679fi8P+n4vQJhKjj
+ZKAuOjopNXLHWL43FAg0xTHOD9Edkgr6VMNGPxxOBdiJOflLUsh7PnhUjXmABqw
lkznhKOhk9/+ZBpWI8VesEVEXVWwwCcG7OWzJNv7L525CIC8OzvGlzxe0LbSDgpg
19SlYKsSmDpHkeARD4P4/xjCqmWW+MlhMNExYO4RkU1KFs+ErSf8H/xO/nVdAd3q
ZFiJx/c5c4FfsprIcw3s8PRpUodq+Vel/eRNl/Ibg2I8Z2usDlRElg9hc4akPgd+
HwR8+rP0s7/Vf64sH5Zo0N0qQ5j0eL+gJ5Nczy2kVEk8qVRb4gTgicmBlGneXDwY
S/V6YN4ncW7f/VEQ2/IyDnv3DmngrA7jDxJUeie8+6GLnixkCIMuPmid8MPMmXF6
nUPDcM0k9ivop17qBoesVwSnXJHX28JtRA7EFy35xGWOQCMzGz6TwSIlXosvs+wU
4/ceDv4mlkQQ51tlR2dSTufbYtPIlxA23dtR5eiWe9Wa2mu3UNw=
=Jwss
-END PGP SIGNATURE End Message ---

Bug#874839: marked as done ([bareos] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 21:34:12 +
with message-id 
and subject line Bug#874839: fixed in bareos 17.2.7-2.1
has caused the Debian Bug report #874839,
regarding [bareos] Future Qt4 removal from Buster
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.)


-- 
874839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bareos
Version: 14.2.6-3
16.2.5-2
16.2.6-3
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: bareos
Source-Version: 17.2.7-2.1

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

Debian distribution maintenance software
pp.
Jakob Haufe  (supplier of updated bareos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Dec 2019 20:32:36 +
Source: bareos
Architecture: source
Version: 17.2.7-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bareos Packaging Team 
Changed-By: Jakob Haufe 
Closes: 874839 933019
Changes:
 bareos (17.2.7-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adjust for GlusterFS API change (Closes: #933019)
   * Switch to Qt5 (Closes: #874839)
Checksums-Sha1:
 7f37e4c9cc479175fb0fcac008b0e48323e4cf60 4384 bareos_17.2.7-2.1.dsc
 9c90573618ef5ec8f3767cef97915e9d548ff9d0 43980 bareos_17.2.7-2.1.debian.tar.xz
 d95048f0f254257cc426468f94a1728604bb5dbf 13829 
bareos_17.2.7-2.1_source.buildinfo
Checksums-Sha256:
 5ffcee14dac9910772be9c7baaa6345cb13672dded7865c50b24c9070c650168 4384 
bareos_17.2.7-2.1.dsc
 840c5dc4a033694b625c2add599738b42beeb979d3985cf91a2cc303ea681576 43980 
bareos_17.2.7-2.1.debian.tar.xz
 2cad9bc7d19df3636c762a32f8be67daaf50c0fec527bccae6440bac52be3a68 13829 
bareos_17.2.7-2.1_source.buildinfo
Files:
 6afc6e546898d6b58df07fa8014cb87f 4384 admin optional bareos_17.2.7-2.1.dsc
 be4f27b8c0b3e19c588f59eee8d05a5c 43980 admin optional 
bareos_17.2.7-2.1.debian.tar.xz
 b71b11858da47516eb378010f8622bb9 13829 admin optional 
bareos_17.2.7-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAl3tXsIACgkQTPKyGPVN
rj02gBAAnP+j3GV7ikJHjyuvSY9sHOlb/+HJE/YGIWtrkSI9IM53B1/nZ7qOF7tp

Bug#937262: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye)

[Andrey Rahmatullin]

On Fri, Dec 13, 2019 at 10:10:03PM +0100, Andreas Tille wrote:
> i$ pdb2pqr
> Traceback (most recent call last):
>   File "/usr/bin/pdb2pqr", line 52, in 
> from main import mainCommand
>   File "/usr/share/pdb2pqr/main.py", line 77, in 
> import extensions
>   File "/usr/share/pdb2pqr/extensions/__init__.py", line 56, in 
> extDict[extName] = __import__(extName,globals(),locals(),[], -1)
> ValueError: level must be >= 0

"""
level specifies whether to use absolute or relative imports. The default
is -1 which indicates both absolute and relative imports will be
attempted. 0 means only perform absolute imports.  Positive values for
level indicate the number of parent directories to search relative to the
directory of the module calling __import__().
"""
https://docs.python.org/2.7/library/functions.html#__import__

-1 was removed in 3.3 as implicit relative import are not supported in
3.x. As this code seems to use relative imports you need to change -1 to
1.

> So I tried:
> 
> --- a/extensions/__init__.py
> +++ b/extensions/__init__.py
> @@ -53,7 +53,7 @@ _extList = [name for _, name, _ in 
> pkgutil.iter_modules(__path__)]
>  extDict = {}
>  
>  for extName in _extList:
> -extDict[extName] = __import__(extName,globals(),locals(),[], -1)
> +extDict[extName] = __import__(extName,globals(),locals(),[], 0)^M

Mindlessly changing the code is almost always a bad idea...

>   File "/usr/share/pdb2pqr/extensions/__init__.py", line 57, in 
> extDict[extName] = __import__(extName,globals(),locals(),[], 0)
> ModuleNotFoundError: No module named 'chi'
This is expected as it now tries to do "import chi". With 1 it should try
"from . import chi". This fails later, as the source also has implicit
relative imports that needs to be fixed, for example "from aconf import"
in src/utilities.py.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#937262: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye)

[Andreas Tille]

On Fri, Dec 13, 2019 at 10:49:45PM +0500, Andrey Rahmatullin wrote:
> > I think at least this is solved now:
> > 
> >
> > https://salsa.debian.org/med-team/pdb2pqr/commit/1f4ee901456641140ef18ca8e91e4701e1175410
> 
> Nice catch, "env.Append(LIBS=[python_lib])" where "python_lib = 'python' +
> gcv('VERSION')" is definitely the cause.

Yes.  I've now a state where the package builds and installs.  However,
just calling pdb2pqr fails with

i$ pdb2pqr
Traceback (most recent call last):
  File "/usr/bin/pdb2pqr", line 52, in 
from main import mainCommand
  File "/usr/share/pdb2pqr/main.py", line 77, in 
import extensions
  File "/usr/share/pdb2pqr/extensions/__init__.py", line 56, in 
extDict[extName] = __import__(extName,globals(),locals(),[], -1)
ValueError: level must be >= 0


So I tried:

--- a/extensions/__init__.py
+++ b/extensions/__init__.py
@@ -53,7 +53,7 @@ _extList = [name for _, name, _ in 
pkgutil.iter_modules(__path__)]
 extDict = {}
 
 for extName in _extList:
-extDict[extName] = __import__(extName,globals(),locals(),[], -1)
+extDict[extName] = __import__(extName,globals(),locals(),[], 0)^M
 
 def setupExtensionsOptions(parser):
 """


which leads to:

$ pdb2pqr
Traceback (most recent call last):
  File "/usr/bin/pdb2pqr", line 52, in 
from main import mainCommand
  File "/usr/share/pdb2pqr/main.py", line 77, in 
import extensions
  File "/usr/share/pdb2pqr/extensions/__init__.py", line 57, in 
extDict[extName] = __import__(extName,globals(),locals(),[], 0)
ModuleNotFoundError: No module named 'chi'


I admit I have no clue whether my change was valid nor what to try next.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#946648: chromium 79.0.3945.79-1 suddenly crashes after a few minutes.

[Jürgen Göricke]

Package: chromium
Version: 79.0.3945.79-1

Dear Maintainer,

chromium crashes after a few minutes.
Especially on websites with active media content.

Please fix this bug.

[2538263:2538263:1213/195431.226626:ERROR:vaapi_wrapper.cc(417)] vaInitialize 
failed: unknown libva error
[2538263:2538263:1213/195431.795728:ERROR:sandbox_linux.cc(372)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[2538263:2538263:1213/195431.846543:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2538263:2538263:1213/195812.970619:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2539174:136:1213/195816.972398:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2539174:136:1213/195816.973049:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2539174:136:1213/195816.973841:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2539174:136:1213/195816.974314:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
Fontconfig error: Cannot load default config file
[2539174:136:1213/195817.863397:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2538229:2538267:1213/195827.275373:ERROR:object_proxy.cc(632)] Failed to call 
method: org.freedesktop.ScreenSaver.Inhibit: object_path= 
/org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: The 
name
org.freedesktop.ScreenSaver was not provided by any .service files 
[2538229:2538267:1213/195827.275403:ERROR:power_save_blocker_x11.cc(330)] No 
response to Inhibit() request!
[2538229:2538267:1213/200128.274852:ERROR:object_proxy.cc(632)] Failed to call 
method: org.freedesktop.ScreenSaver.UnInhibit: object_path= 
/org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.ServiceUnknown: The 
name
org.freedesktop.ScreenSaver was not provided by any .service files 
[2538229:2538267:1213/200128.274875:ERROR:power_save_blocker_x11.cc(403)] No 
response to Uninhibit() request!
[2539174:136:1213/200128.307197:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2539174:136:1213/200128.307742:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2538263:2538263:1213/200149.192602:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2538263:2538263:1213/200326.570765:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2538263:2538263:1213/200535.195688:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2538263:2538263:1213/200618.499126:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
[2540318:263:1213/200621.080811:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.081308:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.082233:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.082715:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.083550:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.084002:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.128401:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.128906:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.158951:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name matching request did not receive a response.
[2540318:263:1213/200621.159471:ERROR:child_process_sandbox_support_impl_linux.cc(79)]
 FontService unique font name 

Bug#946648: crashes within a few minutes

[Harald Dunkel]

metoo

Bug#946629: tilix: Same here

[EdiD]

Package: tilix
Version: 1.9.3-3
Followup-For: Bug #946629

I am wondering why such packages are not tested at all ?

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tilix depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  libc62.29-3
ii  libgtkd-3-0  3.9.0-3+b1
ii  libphobos2-ldc-shared88  1:1.18.0-2
ii  libunwind8   1.2.1-9
ii  libvted-3-0  3.9.0-3+b1
ii  libx11-6 2:1.6.8-1
ii  tilix-common 1.9.3-3

tilix recommends no packages.

Versions of packages tilix suggests:
pn  python-nautilus  

-- no debconf information

Processed: Re: Bug#945035: gnat-gps: Please build-depend on python-gi in addition to python-gi-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #945035 [src:gnat-gps] gnat-gps: Please build-depend on python-gi in 
addition to python-gi-dev
Severity set to 'serious' from 'important'

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

Bug#944249: [Pkg-emacsen-addons] Bug#944249: marked as done (gnuplot-mode does not work with emacs26)

[David Bremner]

"Debian Bug Tracking System"  writes:
>
> 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.
>

Do you plan to do a stable update? It seems not great that the package
is pretty broken in stable.

d

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

[Thorsten Glaser]

On Fri, 13 Dec 2019, Marco d'Itri wrote:

> Can you report this from your dpkg.log?
> 
> root@TMP19396:~# egrep '(libc6|libcrypt)' /var/log/dpkg.log 

Comments inline:

- from the dist-upgrade attempt -

2019-12-11 17:03:21 upgrade libc6:x32 2.29-3 2.29-6
2019-12-11 17:03:21 status half-configured libc6:x32 2.29-3
2019-12-11 17:03:21 status unpacked libc6:x32 2.29-3
2019-12-11 17:03:21 status half-configured libc6:i386 2.29-3
2019-12-11 17:03:21 status half-configured libc6:amd64 2.29-3
2019-12-11 17:03:21 status half-installed libc6:x32 2.29-3
2019-12-11 17:03:25 status unpacked libc6:x32 2.29-6
2019-12-11 17:03:35 upgrade libc6:amd64 2.29-3 2.29-6
2019-12-11 17:03:35 status unpacked libc6:amd64 2.29-3
2019-12-11 17:03:35 status half-installed libc6:amd64 2.29-3
2019-12-11 17:03:36 status unpacked libc6:amd64 2.29-3
2019-12-11 17:03:36 status installed libc6:amd64 2.29-3
2019-12-11 17:03:37 upgrade libc6:i386 2.29-3 2.29-6
2019-12-11 17:03:37 status unpacked libc6:i386 2.29-3
2019-12-11 17:03:37 status half-configured libc6:amd64 2.29-3
2019-12-11 17:03:38 status half-installed libc6:i386 2.29-3
2019-12-11 17:03:38 status unpacked libc6:i386 2.29-3
2019-12-11 17:03:38 status installed libc6:amd64 2.29-3
2019-12-11 17:03:38 status installed libc6:i386 2.29-3

- manual recovery -

2019-12-11 17:37:48 install libcrypt1:amd64  1:4.4.10-5
2019-12-11 17:37:48 status half-installed libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:37:49 status unpacked libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:37:49 install libcrypt1:i386  1:4.4.10-5
2019-12-11 17:37:49 status half-installed libcrypt1:i386 1:4.4.10-5
2019-12-11 17:37:49 status unpacked libcrypt1:i386 1:4.4.10-5
2019-12-11 17:37:49 install libcrypt1:x32  1:4.4.10-5
2019-12-11 17:37:49 status half-installed libcrypt1:x32 1:4.4.10-5
2019-12-11 17:37:50 status unpacked libcrypt1:x32 1:4.4.10-5
2019-12-11 17:37:50 configure libcrypt1:amd64 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:37:50 status half-configured libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:37:50 status installed libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:37:50 configure libcrypt1:i386 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:37:50 status half-configured libcrypt1:i386 1:4.4.10-5
2019-12-11 17:37:50 status installed libcrypt1:i386 1:4.4.10-5

- dpkg -i lib{c6,crypt1}_*.deb again, just to be sure -

2019-12-11 17:38:04 upgrade libc6:amd64 2.29-3 2.29-6
2019-12-11 17:38:04 status half-configured libc6:amd64 2.29-3
2019-12-11 17:38:04 status unpacked libc6:amd64 2.29-3
2019-12-11 17:38:04 status half-configured libc6:i386 2.29-3
2019-12-11 17:38:04 status half-installed libc6:amd64 2.29-3
2019-12-11 17:38:06 status unpacked libc6:amd64 2.29-6
2019-12-11 17:38:07 upgrade libc6:i386 2.29-3 2.29-6
2019-12-11 17:38:07 status unpacked libc6:i386 2.29-3
2019-12-11 17:38:07 status half-installed libc6:i386 2.29-3
2019-12-11 17:38:09 status unpacked libc6:i386 2.29-6
2019-12-11 17:38:09 upgrade libc6:x32 2.29-6 2.29-6
2019-12-11 17:38:09 status half-installed libc6:x32 2.29-6
2019-12-11 17:38:11 status unpacked libc6:x32 2.29-6
2019-12-11 17:38:11 configure libc6:amd64 2.29-6 2.29-6
2019-12-11 17:38:11 status half-configured libc6:amd64 2.29-6
2019-12-11 17:38:13 status installed libc6:amd64 2.29-6
2019-12-11 17:38:13 configure libc6:i386 2.29-6 2.29-6
2019-12-11 17:38:13 status half-configured libc6:i386 2.29-6
2019-12-11 17:38:15 status installed libc6:i386 2.29-6
2019-12-11 17:38:15 configure libcrypt1:x32 1:4.4.10-5 
2019-12-11 17:38:15 status unpacked libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:15 status half-configured libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:15 status installed libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:16 configure libc6:x32 2.29-6 2.29-6
2019-12-11 17:38:16 status half-configured libc6:x32 2.29-6
2019-12-11 17:38:18 status installed libc6:x32 2.29-6
2019-12-11 17:38:23 upgrade libcrypt1:amd64 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:38:23 status half-configured libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:38:23 status unpacked libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:38:23 status half-installed libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:38:23 status unpacked libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:38:24 upgrade libcrypt1:i386 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:38:24 status half-configured libcrypt1:i386 1:4.4.10-5
2019-12-11 17:38:24 status unpacked libcrypt1:i386 1:4.4.10-5
2019-12-11 17:38:24 status half-installed libcrypt1:i386 1:4.4.10-5
2019-12-11 17:38:24 status unpacked libcrypt1:i386 1:4.4.10-5
2019-12-11 17:38:25 upgrade libcrypt1:x32 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:38:25 status half-configured libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:25 status unpacked libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:25 status half-installed libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:25 status unpacked libcrypt1:x32 1:4.4.10-5
2019-12-11 17:38:25 configure libcrypt1:amd64 1:4.4.10-5 1:4.4.10-5
2019-12-11 17:38:25 status half-configured libcrypt1:amd64 1:4.4.10-5
2019-12-11 17:38:25 status installed libcrypt1:amd64 1:4.4.10-5
2019-12-11 

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

[Marco d'Itri]

On Dec 12, Thorsten Glaser  wrote:

> I did a dist-upgrade, and apt uses a different resolver than apt-get,
> but… perhaps the apt maintainers can help trying to figure this out?
I have tried "apt-get --purge dist-upgrade" too and it still does not 
fail on my system.

Can you report this from your dpkg.log?

root@TMP19396:~# egrep '(libc6|libcrypt)' /var/log/dpkg.log 
2019-12-12 18:28:46 install libc6:amd64  2.28-10
2019-12-12 18:28:46 status half-installed libc6:amd64 2.28-10
2019-12-12 18:28:47 status unpacked libc6:amd64 2.28-10
2019-12-12 18:28:47 configure libc6:amd64 2.28-10 2.28-10
2019-12-12 18:28:47 status half-configured libc6:amd64 2.28-10
2019-12-12 18:28:48 status installed libc6:amd64 2.28-10
2019-12-12 18:28:57 upgrade libc6:amd64 2.28-10 2.28-10
2019-12-12 18:28:57 status half-configured libc6:amd64 2.28-10
2019-12-12 18:28:57 status unpacked libc6:amd64 2.28-10
2019-12-12 18:28:57 status half-installed libc6:amd64 2.28-10
2019-12-12 18:28:58 status unpacked libc6:amd64 2.28-10
2019-12-12 18:29:11 configure libc6:amd64 2.28-10 
2019-12-12 18:29:11 status unpacked libc6:amd64 2.28-10
2019-12-12 18:29:11 status half-configured libc6:amd64 2.28-10
2019-12-12 18:29:11 status installed libc6:amd64 2.28-10
2019-12-12 18:29:30 install libc6-dev:amd64  2.28-10
2019-12-12 18:29:30 status half-installed libc6-dev:amd64 2.28-10
2019-12-12 18:29:30 status unpacked libc6-dev:amd64 2.28-10
2019-12-12 18:29:37 configure libc6-dev:amd64 2.28-10 
2019-12-12 18:29:37 status unpacked libc6-dev:amd64 2.28-10
2019-12-12 18:29:37 status half-configured libc6-dev:amd64 2.28-10
2019-12-12 18:29:37 status installed libc6-dev:amd64 2.28-10
2019-12-12 19:31:43 install libc6:i386  2.28-10
2019-12-12 19:31:43 status half-installed libc6:i386 2.28-10
2019-12-12 19:31:44 status unpacked libc6:i386 2.28-10
2019-12-12 19:31:44 configure libc6:i386 2.28-10 
2019-12-12 19:31:44 status unpacked libc6:i386 2.28-10
2019-12-12 19:31:44 status half-configured libc6:i386 2.28-10
2019-12-12 19:31:46 status installed libc6:i386 2.28-10
2019-12-13 16:52:18 upgrade libc6:i386 2.28-10 2.29-6
2019-12-13 16:52:18 status half-configured libc6:i386 2.28-10
2019-12-13 16:52:18 status unpacked libc6:i386 2.28-10
2019-12-13 16:52:18 status half-configured libc6:amd64 2.28-10
2019-12-13 16:52:18 status half-installed libc6:i386 2.28-10
2019-12-13 16:52:19 status unpacked libc6:i386 2.29-6
2019-12-13 16:52:19 upgrade libc6:amd64 2.28-10 2.29-6
2019-12-13 16:52:19 status unpacked libc6:amd64 2.28-10
2019-12-13 16:52:19 status half-installed libc6:amd64 2.28-10
2019-12-13 16:52:20 status unpacked libc6:amd64 2.29-6
2019-12-13 16:52:20 install libcrypt1:amd64  1:4.4.10-5
2019-12-13 16:52:20 status half-installed libcrypt1:amd64 1:4.4.10-5
2019-12-13 16:52:20 status unpacked libcrypt1:amd64 1:4.4.10-5
2019-12-13 16:52:20 install libcrypt1:i386  1:4.4.10-5
2019-12-13 16:52:20 status half-installed libcrypt1:i386 1:4.4.10-5
2019-12-13 16:52:20 status unpacked libcrypt1:i386 1:4.4.10-5
2019-12-13 16:52:20 configure libcrypt1:amd64 1:4.4.10-5 
2019-12-13 16:52:20 status unpacked libcrypt1:amd64 1:4.4.10-5
2019-12-13 16:52:20 status half-configured libcrypt1:amd64 1:4.4.10-5
2019-12-13 16:52:20 status installed libcrypt1:amd64 1:4.4.10-5
2019-12-13 16:52:20 configure libc6:amd64 2.29-6 
2019-12-13 16:52:20 status unpacked libc6:amd64 2.29-6
2019-12-13 16:52:20 status half-configured libc6:amd64 2.29-6
2019-12-13 16:52:21 status installed libc6:amd64 2.29-6
2019-12-13 16:52:21 configure libcrypt1:i386 1:4.4.10-5 
2019-12-13 16:52:21 status unpacked libcrypt1:i386 1:4.4.10-5
2019-12-13 16:52:21 status half-configured libcrypt1:i386 1:4.4.10-5
2019-12-13 16:52:21 status installed libcrypt1:i386 1:4.4.10-5
2019-12-13 16:52:21 configure libc6:i386 2.29-6 
2019-12-13 16:52:21 status unpacked libc6:i386 2.29-6
2019-12-13 16:52:21 status half-configured libc6:i386 2.29-6
2019-12-13 16:52:23 status installed libc6:i386 2.29-6
2019-12-13 16:52:23 upgrade libc6-dev:amd64 2.28-10 2.29-6
2019-12-13 16:52:23 status half-configured libc6-dev:amd64 2.28-10
2019-12-13 16:52:23 status unpacked libc6-dev:amd64 2.28-10
2019-12-13 16:52:23 status half-installed libc6-dev:amd64 2.28-10
2019-12-13 16:52:23 status unpacked libc6-dev:amd64 2.29-6
2019-12-13 16:52:23 install libcrypt1-dev:amd64  1:4.4.10-5
2019-12-13 16:52:23 status half-installed libcrypt1-dev:amd64 1:4.4.10-5
2019-12-13 16:52:23 status unpacked libcrypt1-dev:amd64 1:4.4.10-5
2019-12-13 15:52:47 configure libcrypt1-dev:amd64 1:4.4.10-5 
2019-12-13 15:52:47 status unpacked libcrypt1-dev:amd64 1:4.4.10-5
2019-12-13 15:52:47 status half-configured libcrypt1-dev:amd64 1:4.4.10-5
2019-12-13 15:52:47 status installed libcrypt1-dev:amd64 1:4.4.10-5
2019-12-13 15:52:48 configure libc6-dev:amd64 2.29-6 
2019-12-13 15:52:48 status unpacked libc6-dev:amd64 2.29-6
2019-12-13 15:52:48 status half-configured libc6-dev:amd64 2.29-6
2019-12-13 15:52:48 status installed libc6-dev:amd64 2.29-6
root@TMP19396:~#

-- 
ciao,
Marco

Bug#946561: Bug #946561

[Didier 'OdyX' Raboud]

Control: severity -1 important
Control: tags -1 +moreinfo

Le mercredi, 11 décembre 2019, 21.04:58 h CET Stefano Fabri a écrit :
> Try to apt-get install hplip when you have in the system python >=3.8
> (https://packages.debian.org/experimental/python3).
> 
> In this status hplip is not installable.

Well. Your bugreport still is not actionable for me as maintainer. What do you 
see on-screen when you do this installation combination (ideally in a 
terminal)? When you say "not installable", what exactly do you mean?

OdyX

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

Processed: Re: Bug#946561: Bug #946561

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #946561 [hplip] hplip: Not installable with python3 >= 3.8
Severity set to 'important' from 'grave'
> tags -1 +moreinfo
Bug #946561 [hplip] hplip: Not installable with python3 >= 3.8
Added tag(s) moreinfo.

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

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andreas Tille]

On Fri, Dec 13, 2019 at 03:16:32PM +0100, Andreas Tille wrote:
> 
> ...
> g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
> -Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os -L/usr/lib 
> -lpython3.7m -lpython3.7
> /usr/bin/ld: cannot find -lpython3.7
> collect2: error: ld returned 1 exit status
> ...
> 
> AAArgh, now we just need to get rid of the unwanted stuff.  Any scons
> expert around?

I think at least this is solved now:

   
https://salsa.debian.org/med-team/pdb2pqr/commit/1f4ee901456641140ef18ca8e91e4701e1175410

I might come back with other issues

 Andreas.

-- 
http://fam-tille.de

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andreas Tille]

On Fri, Dec 13, 2019 at 05:46:42PM +0500, Andrey Rahmatullin wrote:
> > 
> > Thanks for that additional hint.  I can confirm that I checked whether
> > pkgconfig can be used before I was asking here.  But we seem to agree
> > that this is not the case.  I admit I have no real clue how to convince
> > scons to link to the correct library name. :-(
> I have no idea either. It seems that it just uses the scons compilation
> code by creating an env.LoadableModule.

I tried a patch to use pkg-config which **partly** works:

...
g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
-Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os -L/usr/lib 
-lpython3.7m -lpython3.7
/usr/bin/ld: cannot find -lpython3.7
collect2: error: ld returned 1 exit status
...

AAArgh, now we just need to get rid of the unwanted stuff.  Any scons
expert around?

Kind regards, Andreas.


[1] 
https://salsa.debian.org/med-team/pdb2pqr/commit/dbee7b96cdb8cad7b60e8c6acffea068664ebe7c

-- 
http://fam-tille.de

Bug#946667: Proposing patch to fix the bug

[DarthDragon]

Hi,

I dive into the problem and I thing the attached patch (generated with
quilt) should fix the problems.
I installed it on my mercurial server, and I can't see any problem yet.
I didn't find any test suite to validate I didn't break anything.

BR,
Jeremy
fix: repo.changectx method has been removed from the API
fix: repo.join method has been removed from the API
Index: mercurial-server-1.2/src/mercurialserver/changes.py
===
--- mercurial-server-1.2.orig/src/mercurialserver/changes.py	2011-09-06 12:40:10.0 +0200
+++ mercurial-server-1.2/src/mercurialserver/changes.py	2019-12-13 14:48:13.712436790 +0100
@@ -3,10 +3,10 @@
 """
 
 def changes(repo, node):
-start = repo.changectx(node).rev()
+start = repo[node].rev()
 try:
 end = len(repo.changelog)
 except:
 end = repo.changelog.count()
 for rev in xrange(start, end):
-yield repo.changectx(rev)
+yield repo[repo.changelog.node(rev)]
Index: mercurial-server-1.2/src/mercurialserver/servelog.py
===
--- mercurial-server-1.2.orig/src/mercurialserver/servelog.py	2011-09-06 12:40:10.0 +0200
+++ mercurial-server-1.2/src/mercurialserver/servelog.py	2019-12-13 14:48:13.720436800 +0100
@@ -26,7 +26,7 @@
 else:
 raise mercurial.util.Abort(_('servelog installed as wrong hook type,'
 ' must be changegroup or outgoing but is %s') % hooktype)
-log = open(repo.join("mercurial-server.log"), "a+")
+log = open(os.path.join(repo.path, "mercurial-server.log"), "a+")
 try:
 fcntl.flock(log.fileno(), fcntl.LOCK_EX)
 log.seek(0, os.SEEK_END)

Processed: tagging 946561

[Debian Bug Tracking System]

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

> tags 946561 + experimental
Bug #946561 [hplip] hplip: Not installable with python3 >= 3.8
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 942744 1.16.2-1
Bug #942744 {Done: Sebastian Dröge } [src:gst-python1.0] fix 
python-config call to get flags for embedded build
Marked as fixed in versions gst-python1.0/1.16.2-1; no longer marked as fixed 
in versions 1.16.2-1.
>
End of message, stopping processing here.

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

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andrey Rahmatullin]

On Fri, Dec 13, 2019 at 01:40:34PM +0100, Andreas Tille wrote:
> > > g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
> > > -Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os 
> > > -L/usr/lib -lpython3.7
> > > /usr/bin/ld: cannot find -lpython3.7
> > Actually, it's a different problem, sorry.
> > There is no -lpython3.7, only -lpython3.7m. If the build system used
> > pkgconfig it would know that. I guess the library name is hardcoded
> > instead? I see that it got -I/usr/include/python3.7m from somewhere, so
> > it's not completely broken.
> 
> Thanks for that additional hint.  I can confirm that I checked whether
> pkgconfig can be used before I was asking here.  But we seem to agree
> that this is not the case.  I admit I have no real clue how to convince
> scons to link to the correct library name. :-(
I have no idea either. It seems that it just uses the scons compilation
code by creating an env.LoadableModule.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andreas Tille]

Hi Andrey,

On Fri, Dec 13, 2019 at 05:18:45PM +0500, Andrey Rahmatullin wrote:
> On Fri, Dec 13, 2019 at 09:49:47AM +0100, Andreas Tille wrote:
> > g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
> > -Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os -L/usr/lib 
> > -lpython3.7
> > /usr/bin/ld: cannot find -lpython3.7
> Actually, it's a different problem, sorry.
> There is no -lpython3.7, only -lpython3.7m. If the build system used
> pkgconfig it would know that. I guess the library name is hardcoded
> instead? I see that it got -I/usr/include/python3.7m from somewhere, so
> it's not completely broken.

Thanks for that additional hint.  I can confirm that I checked whether
pkgconfig can be used before I was asking here.  But we seem to agree
that this is not the case.  I admit I have no real clue how to convince
scons to link to the correct library name. :-(

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andrey Rahmatullin]

On Fri, Dec 13, 2019 at 09:49:47AM +0100, Andreas Tille wrote:
> g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
> -Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os -L/usr/lib 
> -lpython3.7
> /usr/bin/ld: cannot find -lpython3.7
Actually, it's a different problem, sorry.
There is no -lpython3.7, only -lpython3.7m. If the build system used
pkgconfig it would know that. I guess the library name is hardcoded
instead? I see that it got -I/usr/include/python3.7m from somewhere, so
it's not completely broken.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#945724: marked as done (xbattbar: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 11:20:46 +
with message-id 
and subject line Bug#945724: fixed in xbattbar 1.4.8-2
has caused the Debian Bug report #945724,
regarding xbattbar: Python2 removal in sid/bullseye
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.)


-- 
945724: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945724
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xbattbar
Version: 1.4.8-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ).
Please stop using Python2, and fix this issue by one of the following
actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: xbattbar
Source-Version: 1.4.8-2

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

Debian distribution maintenance software
pp.
Dmitry E. Oboukhov  (supplier of updated xbattbar 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, 13 Dec 2019 13:59:21 +0300
Source: xbattbar
Binary: xbattbar xbattbar-dbgsym
Architecture: source amd64
Version: 1.4.8-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov 
Changed-By: Dmitry E. Oboukhov 
Description:
 xbattbar   - Display battery status in X11
Closes: 945724
Changes:
 xbattbar (1.4.8-2) unstable; urgency=medium
 .
   * Drop python depends, closes: #945724.
Checksums-Sha1:
 f2cfe10013a0909f737c1c9aede1a2d6a584e1e4 1781 xbattbar_1.4.8-2.dsc
 63093544f971aa1268f7b3593c6968958c008ede 3564 xbattbar_1.4.8-2.diff.gz
 9f2999e9bd4c647e40ae2b9ea5ec7aee61b3b0e5 20616 
xbattbar-dbgsym_1.4.8-2_amd64.deb
 06c4959f8869d5e497aef4a83cf4f5250ae02a3c 5975 xbattbar_1.4.8-2_amd64.buildinfo
 36eb2571e8dc6d1fce032e9c80e2e36a4c0e9536 14884 xbattbar_1.4.8-2_amd64.deb
Checksums-Sha256:
 337fd397cef267faa68bb0b7287fbefc4fe5b45133f79fe71587129817bd4a3b 1781 
xbattbar_1.4.8-2.dsc
 472ff477f1fcc24f3596a6a5c702433807ef56a41c5b999808e16e2aad88f5d9 3564 
xbattbar_1.4.8-2.diff.gz
 0873945d4421e90a111942b6ce741faf6972e690cc2b220055463c4335114f35 20616 
xbattbar-dbgsym_1.4.8-2_amd64.deb
 

Bug#946669: marked as done (libmatroksa: bump version in shlibs)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 10:49:13 +
with message-id 
and subject line Bug#946669: fixed in libmatroska 1.5.2-3
has caused the Debian Bug report #946669,
regarding libmatroksa: bump version in shlibs
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.)


-- 
946669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vlc-plugin-base
Version: 3.0.8-0+deb10u1
Severity: serious
Justification: depend on libmatroska6v5 versioned too loosely

Playing an mkv video with 48kHz 32 bit Opus Audio results in total
silence. I tried alsa audio output, I tried pulseaudio output. Videos
with other codecs work correctly. I didn't try:

 * other sampling frequency, or other bit depth, of Opus Audio
 * Opus Audio in another container than mkv

I tried upgrading libopus0 to 1.3-1, same result.

vlc -vvv output:

This is caused by:

[556bdfd5bc60] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so' 
(/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so: undefined 
symbol: _ZN11libmatroska27KaxVideoProjectionPosePitch10ClassInfosE)

which is solved by upgrading libmatroska6v5 from version 1.4.5-2 to
1.4.9-1. This suggests that the depends of vlc-plugin-base on
 libmatroska6v5 (>= 1.4.5)
should be versioned more strictly, to require a higher version, making
this a Policy-serious bug.

Note that the "messages" window of vlc didn't show any error, nor did
stderr. They should have, which would have clued me in as to the
problem, before I ran with "-vvv" as instructed by reportug for this
bug report.

-- System Information:
Debian Release: 9.11
  APT prefers oldstable-updates
  APT policy: (600, 'oldstable-updates'), (600, 'oldstable'), (500, 
'stable-updates'), (400, 'stable'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages vlc depends on:
ii  vlc-bin  3.0.8-0+deb10u1
ii  vlc-plugin-base  3.0.8-0+deb10u1
ii  vlc-plugin-qt3.0.8-0+deb10u1
ii  vlc-plugin-video-output  3.0.8-0+deb10u1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.8-0+deb10u1
ii  vlc-plugin-notify  3.0.8-0+deb10u1
ii  vlc-plugin-samba   3.0.8-0+deb10u1
ii  vlc-plugin-skins2  3.0.8-0+deb10u1
ii  vlc-plugin-video-splitter  3.0.8-0+deb10u1
ii  vlc-plugin-visualization   3.0.8-0+deb10u1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.28-10
ii  libvlc5  3.0.8-0+deb10u1

Versions of packages libvlc5 depends on:
ii  libc62.28-10
ii  libvlccore9  3.0.8-0+deb10u1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.8-0+deb10u1

Versions of packages vlc-bin depends on:
ii  libc6   2.28-10
ii  libvlc-bin  3.0.8-0+deb10u1
ii  libvlc5 3.0.8-0+deb10u1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libaom0  1.0.0-3
ii  libarchive13 3.2.2-2+deb9u2
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.1.8-1
ii  libass9  1:0.14.0-2
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec58 7:4.1.4-1~deb10u1
ii  libavformat587:4.1.4-1~deb10u1
ii  libavutil56  7:4.1.4-1~deb10u1
ii  libbasicusageenvironment12018.11.26-1.1
ii  libbluray2   1:1.1.0-1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.3-3
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-10
ii  libdvbpsi10  1.3.0-5
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1.3.6-2
ii  libfaad2 

Processed: severity of 938581 is serious

[Debian Bug Tracking System]

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

> severity 938581 serious
Bug #938581 [src:sugar] sugar: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#946669: vlc: silently fails to play 32bit 48kHz Opus audio from mkv container

[Sebastian Ramacher]

Control: reassign -1 libmatroska6v5 1.4.9-1
Control: retitle -1 libmatroksa: bump version in shlibs

On 2019-12-13 10:45:44, Lionel Elie Mamane wrote:
> Package: vlc-plugin-base
> Version: 3.0.8-0+deb10u1
> Severity: serious
> Justification: depend on libmatroska6v5 versioned too loosely
> 
> Playing an mkv video with 48kHz 32 bit Opus Audio results in total
> silence. I tried alsa audio output, I tried pulseaudio output. Videos
> with other codecs work correctly. I didn't try:
> 
>  * other sampling frequency, or other bit depth, of Opus Audio
>  * Opus Audio in another container than mkv
> 
> I tried upgrading libopus0 to 1.3-1, same result.
> 
> vlc -vvv output:
> 
> This is caused by:
> 
> [556bdfd5bc60] main libvlc warning: cannot load module 
> `/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so' 
> (/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so: undefined 
> symbol: _ZN11libmatroska27KaxVideoProjectionPosePitch10ClassInfosE)
> 
> which is solved by upgrading libmatroska6v5 from version 1.4.5-2 to
> 1.4.9-1. This suggests that the depends of vlc-plugin-base on
>  libmatroska6v5 (>= 1.4.5)
> should be versioned more strictly, to require a higher version, making
> this a Policy-serious bug.

libmatroska needs to bump its version in shlibs. After that vlc needs to
be rebuilt to pick up the new version. Reassigning accordingly.

Cheers

> 
> Note that the "messages" window of vlc didn't show any error, nor did
> stderr. They should have, which would have clued me in as to the
> problem, before I ran with "-vvv" as instructed by reportug for this
> bug report.
> 
> -- System Information:
> Debian Release: 9.11
>   APT prefers oldstable-updates
>   APT policy: (600, 'oldstable-updates'), (600, 'oldstable'), (500, 
> 'stable-updates'), (400, 'stable'), (300, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 4.9.0-11-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), 
> LANGUAGE=en_GB.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages vlc depends on:
> ii  vlc-bin  3.0.8-0+deb10u1
> ii  vlc-plugin-base  3.0.8-0+deb10u1
> ii  vlc-plugin-qt3.0.8-0+deb10u1
> ii  vlc-plugin-video-output  3.0.8-0+deb10u1
> 
> Versions of packages vlc recommends:
> ii  vlc-l10n   3.0.8-0+deb10u1
> ii  vlc-plugin-notify  3.0.8-0+deb10u1
> ii  vlc-plugin-samba   3.0.8-0+deb10u1
> ii  vlc-plugin-skins2  3.0.8-0+deb10u1
> ii  vlc-plugin-video-splitter  3.0.8-0+deb10u1
> ii  vlc-plugin-visualization   3.0.8-0+deb10u1
> 
> vlc suggests no packages.
> 
> Versions of packages libvlc-bin depends on:
> ii  libc62.28-10
> ii  libvlc5  3.0.8-0+deb10u1
> 
> Versions of packages libvlc5 depends on:
> ii  libc62.28-10
> ii  libvlccore9  3.0.8-0+deb10u1
> 
> Versions of packages libvlc5 recommends:
> ii  libvlc-bin  3.0.8-0+deb10u1
> 
> Versions of packages vlc-bin depends on:
> ii  libc6   2.28-10
> ii  libvlc-bin  3.0.8-0+deb10u1
> ii  libvlc5 3.0.8-0+deb10u1
> 
> Versions of packages vlc-plugin-base depends on:
> ii  liba52-0.7.4 0.7.4-19
> ii  libaom0  1.0.0-3
> ii  libarchive13 3.2.2-2+deb9u2
> ii  libaribb24-0 1.0.3-2
> ii  libasound2   1.1.8-1
> ii  libass9  1:0.14.0-2
> ii  libavahi-client3 0.6.32-2
> ii  libavahi-common3 0.6.32-2
> ii  libavc1394-0 0.5.4-4+b1
> ii  libavcodec58 7:4.1.4-1~deb10u1
> ii  libavformat587:4.1.4-1~deb10u1
> ii  libavutil56  7:4.1.4-1~deb10u1
> ii  libbasicusageenvironment12018.11.26-1.1
> ii  libbluray2   1:1.1.0-1
> ii  libc62.28-10
> ii  libcairo21.16.0-4
> ii  libcddb2 1.3.2-5
> ii  libchromaprint1  1.4.3-3
> ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
> ii  libdbus-1-3  1.10.28-0+deb9u1
> ii  libdc1394-22 2.2.5-1
> ii  libdca0  0.0.5-10
> ii  libdvbpsi10  1.3.0-5
> ii  libdvdnav4   5.0.3-3
> ii  libdvdread4  5.0.3-2
> ii  libebml4v5   1.3.6-2
> ii  libfaad2 2.8.0~cvs20161113-1+deb9u2
> ii  libflac8 1.3.2-1
> ii  libfontconfig1   2.13.1-2
> ii  libfreetype6 2.9.1-3+deb10u1
> ii  libfribidi0  1.0.5-3.1+deb10u1
> ii  libgcc1  1:8.3.0-6
> ii  

Processed: Re: Bug#946669: vlc: silently fails to play 32bit 48kHz Opus audio from mkv container

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libmatroska6v5 1.4.9-1
Bug #946669 [vlc-plugin-base] vlc: silently fails to play 32bit 48kHz Opus 
audio from mkv container
Bug reassigned from package 'vlc-plugin-base' to 'libmatroska6v5'.
No longer marked as found in versions vlc/3.0.8-0+deb10u1.
Ignoring request to alter fixed versions of bug #946669 to the same values 
previously set
Bug #946669 [libmatroska6v5] vlc: silently fails to play 32bit 48kHz Opus audio 
from mkv container
Marked as found in versions libmatroska/1.4.9-1.
> retitle -1 libmatroksa: bump version in shlibs
Bug #946669 [libmatroska6v5] vlc: silently fails to play 32bit 48kHz Opus audio 
from mkv container
Changed Bug title to 'libmatroksa: bump version in shlibs' from 'vlc: silently 
fails to play 32bit 48kHz Opus audio from mkv container'.

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

Bug#946669: vlc: silently fails to play 32bit 48kHz Opus audio from mkv container

[Lionel Elie Mamane]

Package: vlc-plugin-base
Version: 3.0.8-0+deb10u1
Severity: serious
Justification: depend on libmatroska6v5 versioned too loosely

Playing an mkv video with 48kHz 32 bit Opus Audio results in total
silence. I tried alsa audio output, I tried pulseaudio output. Videos
with other codecs work correctly. I didn't try:

 * other sampling frequency, or other bit depth, of Opus Audio
 * Opus Audio in another container than mkv

I tried upgrading libopus0 to 1.3-1, same result.

vlc -vvv output:

This is caused by:

[556bdfd5bc60] main libvlc warning: cannot load module 
`/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so' 
(/usr/lib/x86_64-linux-gnu/vlc/plugins/demux/libmkv_plugin.so: undefined 
symbol: _ZN11libmatroska27KaxVideoProjectionPosePitch10ClassInfosE)

which is solved by upgrading libmatroska6v5 from version 1.4.5-2 to
1.4.9-1. This suggests that the depends of vlc-plugin-base on
 libmatroska6v5 (>= 1.4.5)
should be versioned more strictly, to require a higher version, making
this a Policy-serious bug.

Note that the "messages" window of vlc didn't show any error, nor did
stderr. They should have, which would have clued me in as to the
problem, before I ran with "-vvv" as instructed by reportug for this
bug report.

-- System Information:
Debian Release: 9.11
  APT prefers oldstable-updates
  APT policy: (600, 'oldstable-updates'), (600, 'oldstable'), (500, 
'stable-updates'), (400, 'stable'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages vlc depends on:
ii  vlc-bin  3.0.8-0+deb10u1
ii  vlc-plugin-base  3.0.8-0+deb10u1
ii  vlc-plugin-qt3.0.8-0+deb10u1
ii  vlc-plugin-video-output  3.0.8-0+deb10u1

Versions of packages vlc recommends:
ii  vlc-l10n   3.0.8-0+deb10u1
ii  vlc-plugin-notify  3.0.8-0+deb10u1
ii  vlc-plugin-samba   3.0.8-0+deb10u1
ii  vlc-plugin-skins2  3.0.8-0+deb10u1
ii  vlc-plugin-video-splitter  3.0.8-0+deb10u1
ii  vlc-plugin-visualization   3.0.8-0+deb10u1

vlc suggests no packages.

Versions of packages libvlc-bin depends on:
ii  libc62.28-10
ii  libvlc5  3.0.8-0+deb10u1

Versions of packages libvlc5 depends on:
ii  libc62.28-10
ii  libvlccore9  3.0.8-0+deb10u1

Versions of packages libvlc5 recommends:
ii  libvlc-bin  3.0.8-0+deb10u1

Versions of packages vlc-bin depends on:
ii  libc6   2.28-10
ii  libvlc-bin  3.0.8-0+deb10u1
ii  libvlc5 3.0.8-0+deb10u1

Versions of packages vlc-plugin-base depends on:
ii  liba52-0.7.4 0.7.4-19
ii  libaom0  1.0.0-3
ii  libarchive13 3.2.2-2+deb9u2
ii  libaribb24-0 1.0.3-2
ii  libasound2   1.1.8-1
ii  libass9  1:0.14.0-2
ii  libavahi-client3 0.6.32-2
ii  libavahi-common3 0.6.32-2
ii  libavc1394-0 0.5.4-4+b1
ii  libavcodec58 7:4.1.4-1~deb10u1
ii  libavformat587:4.1.4-1~deb10u1
ii  libavutil56  7:4.1.4-1~deb10u1
ii  libbasicusageenvironment12018.11.26-1.1
ii  libbluray2   1:1.1.0-1
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libcddb2 1.3.2-5
ii  libchromaprint1  1.4.3-3
ii  libcrystalhd31:0.0~git20110715.fdd2f19-12
ii  libdbus-1-3  1.10.28-0+deb9u1
ii  libdc1394-22 2.2.5-1
ii  libdca0  0.0.5-10
ii  libdvbpsi10  1.3.0-5
ii  libdvdnav4   5.0.3-3
ii  libdvdread4  5.0.3-2
ii  libebml4v5   1.3.6-2
ii  libfaad2 2.8.0~cvs20161113-1+deb9u2
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.9.1-3+deb10u1
ii  libfribidi0  1.0.5-3.1+deb10u1
ii  libgcc1  1:8.3.0-6
ii  libgcrypt20  1.8.4-5
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgnutls30  3.6.7-4
ii  libgpg-error01.35-1
ii  libgroupsock82018.11.26-1.1
ii  libharfbuzz0b2.3.1-1
ii  libixml101:1.8.4-2
ii  libjpeg62-turbo  1:1.5.1-2
ii  libkate1 0.4.1-7+b1
ii  liblirc-client0  0.9.4c-9
ii  liblivemedia64

Bug#942744: marked as done (fix python-config call to get flags for embedded build)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 11:38:41 +0200
with message-id 
and subject line Re: fix python-config call to get flags for embedded build
has caused the Debian Bug report #942744,
regarding fix python-config call to get flags for embedded 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.)


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

Package: src:gst-python1.0
Version: 1.16.1-1
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

fix python-config call to get flags for embedded build

patch at
http://launchpadlibrarian.net/447748585/gst-python1.0_1.16.1-1build1_1.16.1-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Version: 1.16.2-1

On Sun, 20 Oct 2019 22:15:23 +0200 Matthias Klose  wrote:
> Package: src:gst-python1.0
> Version: 1.16.1-1
> Severity: important
> Tags: sid bullseye patch
> User: debian-pyt...@lists.debian.org
> Usertags: python3.8
> 
> fix python-config call to get flags for embedded build
> 
> patch at
> http://launchpadlibrarian.net/447748585/gst-python1.0_1.16.1-1build1_1.16.1-1ubuntu1.diff.gz

Thanks, this is fixed in 1.16.2-1 by switching to the meson build
system and applying a minor workaround for this.

Great work by the Python developers to intentionally and knowingly
break build systems out there without a previous warning.


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

Bug#946667: mercurial-server: can't clone to or push repository to server (object has no attribute 'changectx')

[DarthDragon]

Package: mercurial-server
Version: 1.2-2.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

after upgrading my mercurial server from stretch to buster, I'm not
able to push or clone to this server from a buster client, the command
fails with:

...
remote:   File
"/usr/share/mercurial-server/mercurialserver/changes.py", line 6, in changes
remote: start = repo.changectx(node).rev()
remote: AttributeError:
'derivedrepo:/var/lib/mercurial-server/repos/projec' object has no
attribute 'changectx'
abort: stream ended unexpectedly (got 0 bytes, expected 4)

Only solution found is to disable access hook in
/etc/mercurial-server/remote-hgrc.d/access.rc but since it's removing
all access control security, this is not a real solution (and it also
raises another bug in the logging hook but at least repository is
cloned/pushed).

Clone from or pull are not affected (except for the logging hook bug).

Steps to reproduce:

sudo lxc-create hgserver -t debian --
--package=mercurial-server,openssh-server,sudo,reportbug -r buster
sudo lxc-start hgserver
sudo lxc-attach hgserver
apt update
apt dist-upgrade
cd
ssh-keygen
mkdir -p /etc/mercurial-server/keys/root
cp .ssh/id_rsa.pub /etc/mercurial-server/keys/root
sed -i 's/localhost/localhost hgserver/' /etc/hosts
sudo -u hg /usr/share/mercurial-server/refresh-auth
mkdir project
cd project
hg init
touch spam
hg add spam
hg commit -m 'add spam' -u root
hg clone . ssh://hg@127.0.0.1/project

Error trace:

searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
remote: error: pretxnchangegroup.access hook raised an exception:
'derivedrepo:/var/lib/mercurial-server/repos/projec' object has no
attribute 'changectx'
remote: transaction abort!
remote: rollback completed
remote: ** unknown exception encountered, please report by visiting
remote: ** https://mercurial-scm.org/wiki/BugTracker
remote: ** Python 2.7.16 (default, Oct 10 2019, 22:02:15) [GCC 8.3.0]
remote: ** Mercurial Distributed SCM (version 4.8.2)
remote: ** Extensions loaded:
remote: Traceback (most recent call last):
remote:   File "/usr/share/mercurial-server/hg-ssh", line 91, in

remote: dispatch.dispatch(request(['-R', repo, 'serve', '--stdio']))
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 220, in
dispatch
remote: ret = _runcatch(req) or 0
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 363, in
_runcatch
remote: return _callcatch(ui, _runcatchfunc)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 371, in
_callcatch
remote: return scmutil.callcatch(ui, func)
remote:   File "/usr/lib/python2.7/dist-packages/mercurial/scmutil.py",
line 166, in callcatch
remote: return func()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 354, in
_runcatchfunc
remote: return _dispatch(req)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 994, in
_dispatch
remote: cmdpats, cmdoptions)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 737, in
runcommand
remote: ret = _runcommand(ui, options, cmd, d)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 1003, in
_runcommand
remote: return cmdfunc()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/dispatch.py", line 991, in

remote: d = lambda: util.checksignature(func)(ui, *args,
**strcmdopt)
remote:   File "/usr/lib/python2.7/dist-packages/mercurial/util.py",
line 1646, in check
remote: return func(*args, **kwargs)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/commands.py", line 5207, in
serve
remote: s.serve_forever()
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotoserver.py", line 797,
in serve_forever
remote: self.serveuntil(threading.Event())
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotoserver.py", line 804,
in serveuntil
remote: _runsshserver(self._ui, self._repo, self._fin, self._fout,
ev)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotoserver.py", line 656,
in _runsshserver
remote: rsp = wireprotov1server.dispatch(repo, proto, request)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotov1server.py", line 74,
in dispatch
remote: return func(repo, proto, *args)
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/wireprotov1server.py", line
599, in unbundle
remote: proto.client())
remote:   File
"/usr/lib/python2.7/dist-packages/mercurial/exchange.py", line 2377, in
unbundle
remote: op = 

Bug#937262: Help with scons needed (Was: Help needed (Was: pdb2pqr: Python2 removal in sid/bullseye))

[Andreas Tille]

Hi Scott,

On Thu, Dec 12, 2019 at 04:34:09PM -0500, Scott Talbert wrote:
> On Thu, 12 Dec 2019, Andreas Tille wrote:
> > mkdir -p /build/pdb2pqr-2.1.1+dfsg/debian/tmp/usr/share/pdb2pqr
> > scons \
> >URL="http://localhost/pdb2pqr/; \
> >PREFIX="/build/pdb2pqr-2.1.1+dfsg/debian/tmp/usr/share/pdb2pqr"
> > scons: Reading SConscript files ...
> > not using opal
> > scons: done reading SConscript files.
> > scons: Building targets ...
> > CopySubAction("pdb2pqr.py", "pdb2pqr.py.in")
> > scons: *** [pdb2pqr.py] Can't write target file pdb2pqr.py
> > scons: building terminated because of errors.
> 
> I think you need to change the other open() call in that function to write
> in text mode also.

Thanks a lot for your patience and your always helpful hints.  After
changing this and some other issues with the C++ code I was (hopefully)
able to solve myself[1] I'm facing the next stumbling stone which is
most probably easy to solve for someone more experienced than me:


...
scons \
URL="http://localhost/pdb2pqr/; \
PREFIX="/usr/share/pdb2pqr"
scons: Reading SConscript files ...
not using opal 
scons: done reading SConscript files.
scons: Building targets ...
CopySubAction("pdb2pqr.py", "pdb2pqr.py.in")
Chmod("pdb2pqr.py", 0755)
CopySubAction("apbs_cgi.cgi", "apbs_cgi.py")
Chmod("apbs_cgi.cgi", 0755)
CopySubAction("visualize.cgi", "visualize.py")
Chmod("visualize.cgi", 0755)
CopySubAction("querystatus.cgi", "querystatus.py")
Chmod("querystatus.cgi", 0755)
CopySubAction("src/aconf.py", "src/aconf.py.in")
CopySubAction("html/server.html", "html/server.html.in")
Copy("pdb2pqr.cgi", "pdb2pqr.py")
g++ -o pdb2pka/substruct/Algorithms.os -c -g -fPIC -I/usr/include/python3.7m 
-I/usr/lib/python3/dist-packages/numpy/core/include 
pdb2pka/substruct/Algorithms.cpp
In file included from /usr/include/python3.7m/numpy/ndarraytypes.h:1830,
 from /usr/include/python3.7m/numpy/ndarrayobject.h:12,
 from /usr/include/python3.7m/numpy/arrayobject.h:4,
 from pdb2pka/substruct/Algorithms.cpp:43:
/usr/include/python3.7m/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning 
"Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API 
NPY_1_7_API_VERSION" [-Wcpp]
   17 | #warning "Using deprecated NumPy API, disable it with " \
  |  ^~~
pdb2pka/substruct/Algorithms.cpp: In function 'PyObject* initAlgorithms()':
pdb2pka/substruct/Algorithms.cpp:333:1: warning: control reaches end of 
non-void function [-Wreturn-type]
  333 | };
  | ^
g++ -o pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so 
-Wl,-z,relro -Wl,-z,now -shared pdb2pka/substruct/Algorithms.os -L/usr/lib 
-lpython3.7
/usr/bin/ld: cannot find -lpython3.7
collect2: error: ld returned 1 exit status
scons: *** [pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so] Error 
1
scons: building terminated because of errors.

TARGETS: ['pdb2pqr.py', 'apbs_cgi.cgi', 'visualize.cgi', 'querystatus.cgi', 
'src/aconf.py', 'html/server.html', 'pdb2pqr.cgi', 
'pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so', 
'pdb2pka/_pMC_mult.cpython-37m-x86_64-linux-gnu.so']


Configuration Parameters


Version: 2.1.1
Install directory: /usr/share/pdb2pqr/
pdb2pka and ligand support: True
Path to the website directory: http://localhost/pdb2pqr/
PDB2PQR jobs run via the web interface will be forked on the server.

The preferred way to configure the build is by editing the file build_config.py

Run scons with the python3 that you intend to use with pdb2pqr.
For example: "scons" will setup pdb2pqr to be run with Debian default Python3 
interpreter

Run "scons install" to install pdb2pqr in /usr/share/pdb2pqr/

Run "scons basic-test" for a basic functionality test
Run "scons advanced-test" for a single test of ligand and PROPKA support. 
Requires numpy and PDB2PKA support compiled.
Run "scons complete-test" for a complete test of all functionality EXCEPT 
PDB2PKA. Requires numpy and PDB2PKA support compiled.
Run "scons pdb2pka-test" for a test of PDB2PKA functionality.
Requires numpy, PDB2PKA support compiled AND the APBS python3 libraries 
compiled and installed in the pdb2pka directory.

To setup a web service create a symbolic link to /usr/share/pdb2pqr/ that 
enables you to view http://localhost/pdb2pqr/ after running "scons install"

Run "scons msvs" to build Visual Studio projects for the Algorithms and 
pMC_mult modules.
VS project generation is not well supported in scons. Resulting projects should 
build using NMAKE but cannot be used for debugging.
The resulting projects will need to modified to use VS natively to compile the 
code or debug.

FAILED
Failed building pdb2pka/substruct/Algorithms.cpython-37m-x86_64-linux-gnu.so: 
Error 1
...


So how can I enable proper linking to -lpython3.7 which is obviously not
in the library search path (but package libpython3.7 is definitely
installed in the pbuilder 

Bug#946424: marked as done (libopenvr-dev: missing Breaks+Replaces: libopenvr-api-dev)

[Debian Bug Tracking System]

Your message dated Fri, 13 Dec 2019 08:43:39 +
with message-id 
and subject line Bug#946424: fixed in openvr 1.8.19~ds1-3
has caused the Debian Bug report #946424,
regarding libopenvr-dev: missing Breaks+Replaces: libopenvr-api-dev
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.)


-- 
946424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libopenvr-dev
Version: 1.8.19~ds1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Selecting previously unselected package libopenvr-dev.
  Preparing to unpack .../libopenvr-dev_1.8.19~ds1-2_amd64.deb ...
  Unpacking libopenvr-dev (1.8.19~ds1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libopenvr-dev_1.8.19~ds1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/include/openvr/openvr.h', which is also in package 
libopenvr-api-dev 1.8.19~ds1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libopenvr-dev_1.8.19~ds1-2_amd64.deb


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: openvr
Source-Version: 1.8.19~ds1-3

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

Debian distribution maintenance software
pp.
Andrew Lee (李健秋)  (supplier of updated openvr 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, 13 Dec 2019 15:52:18 +0800
Source: openvr
Architecture: source
Version: 1.8.19~ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Andrew Lee (李健秋) 
Changed-By: Andrew Lee (李健秋) 
Closes: 946424
Changes:
 openvr (1.8.19~ds1-3) unstable; urgency=medium
 .
   * debian/control: fix overwriting files from libopenvr-api-dev.
 (Closes: #946424)
Checksums-Sha1:
 8c1c0b0d4e82b0a95b9eb14d07d3ebf9d3b9740c 2037 openvr_1.8.19~ds1-3.dsc
 21bb3848268c75d56eb144601f29e7118cc008f0 1015900 openvr_1.8.19~ds1.orig.tar.xz
 f69a729b255b2e6bed6f7218000d8520853aab16 6496 openvr_1.8.19~ds1-3.debian.tar.xz
 33829e768c7b20c3281e9627f8c69d22e4ca2ef2 6244 
openvr_1.8.19~ds1-3_source.buildinfo
Checksums-Sha256:
 8aee69724c395e72861b7bbe0fee1d3c5a8a515eaabbd991a3946f8cdd4ef701 2037 
openvr_1.8.19~ds1-3.dsc
 327ee391c820e11aada3e27f119db29273e5dd13e967bdbe33a5175965635bf7 1015900 
openvr_1.8.19~ds1.orig.tar.xz
 8f7d07e6b60adcf89873a303279ce416114fb2e396df9d75bb78afe8ee693a4d 6496 
openvr_1.8.19~ds1-3.debian.tar.xz
 4a197ee461cf15210c126aa62e8972c4083f4d0b90df38f9928d84a0e27430ae 6244 
openvr_1.8.19~ds1-3_source.buildinfo
Files:
 fa3baaf3d667df09979ae178e9b785c5 2037 contrib/devel optional 
openvr_1.8.19~ds1-3.dsc
 b7a5699bad27857d022112bfabeb25a2 1015900 contrib/devel optional 
openvr_1.8.19~ds1.orig.tar.xz
 c96e925c71b2c99bad4740b333dcfbbd 6496 contrib/devel optional 
openvr_1.8.19~ds1-3.debian.tar.xz
 803e47a845439e2eb451dda72e4cae7f 6244 contrib/devel optional 
openvr_1.8.19~ds1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE703UlH90QYpfEyJV58vhUqwX+XMFAl3zQ3IACgkQ58vhUqwX
+XPNqRAAx2FGP/jEiZIaoSLxn+Sld7XaMk0KwMiPTXl6KysLg6jbS+3+Pd/qLB0X
y+UprpRHu1yYlOkwSf1HLGvBLf6pXsvEzuHIwaQxe54EFTxgvqVgr43/muzpSJiV
BOl5PH68DQzHZ9Xu9nCqdskKW1gJaWmt/bqh7WkHVjjsrOucf3J5+WI+iwwxJmE8
6XvMiCpKgj7LZXED2TSW4MIu4VLRtt01o+OolSWs4SRCDCPDaDwfJLwxeStVmFRh
6Dl5x6UYA0d/8g/V/vh8/zm7Rq0BwtOR+u7JNB4KBCX/Z9aN6TU+MmMDW5/KcyBX
dL4upf2TCESa3fMnuYztryrK9ISzZRxAPzXjUujgMPTQqQXos5l/itPunmQEwlZo
z6wzRHpzd/MwBZggvsGdrZn57yjruIsnqIPabb8CU4ewmbyWOpUGExQbol47Xv+i
EVAgtgt/AqKUzgBkbXC+xTC0fDHXb2vKfZHSkZ1hjfCAhXp72E3Wn77n4V2Fkf1m
ElXCm1Y9i8KaI75KDFcA0mk5VXw/NauS4VmfyXk6+ABzn/uLjqifJQt4rCHqiD79