Bug#937900: marked as done (python-lxc: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:30:55 +
with message-id 
and subject line Bug#947099: Removed package(s) from unstable
has caused the Debian Bug report #937900,
regarding python-lxc: 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.)


-- 
937900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-lxc
Version: 0.1-3
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:python-lxc

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.1-3+rm

Dear submitter,

as the package python-lxc 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/947099

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#937440: marked as done (pyftpd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:30:08 +
with message-id 
and subject line Bug#947095: Removed package(s) from unstable
has caused the Debian Bug report #937440,
regarding pyftpd: 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.)


-- 
937440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyftpd
Version: 0.8.5+nmu1
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:pyftpd

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.8.5+nmu1+rm

Dear submitter,

as the package pyftpd 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/947095

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#938252: marked as done (python-vsgui: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:30:32 +
with message-id 
and subject line Bug#947096: Removed package(s) from unstable
has caused the Debian Bug report #938252,
regarding python-vsgui: 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.)


-- 
938252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-vsgui
Version: 0.3.3-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:python-vsgui

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.3-1+rm

Dear submitter,

as the package python-vsgui 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/947096

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#937179: marked as done (obmenu: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:29:42 +
with message-id 
and subject line Bug#947094: Removed package(s) from unstable
has caused the Debian Bug report #937179,
regarding obmenu: 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.)


-- 
937179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:obmenu
Version: 1.0-4
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:obmenu

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.0-4+rm

Dear submitter,

as the package obmenu 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/947094

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#897281: marked as done (doc-debian-fr: Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:31:36 +
with message-id 
and subject line Bug#947104: Removed package(s) from unstable
has caused the Debian Bug report #897281,
regarding doc-debian-fr: Should this package 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.)


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

These docs have been updated the last time over 12 years ago, is this actually
still useful or rather misleading and should be removed?

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 3.1.3.2+rm

Dear submitter,

as the package doc-debian-fr 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/947104

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#885508: marked as done (obmenu: Depends on unmaintained python-glade2)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:29:42 +
with message-id 
and subject line Bug#947094: Removed package(s) from unstable
has caused the Debian Bug report #885508,
regarding obmenu: Depends on unmaintained python-glade2
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.)


-- 
885508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obmenu
Version: 1.0-4
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.0-4+rm

Dear submitter,

as the package obmenu 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/947094

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#943622: marked as done (some python-biom-format tests fail with python3.8)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:19:13 +
with message-id 
and subject line Bug#943622: fixed in python-biom-format 2.1.7+dfsg-5
has caused the Debian Bug report #943622,
regarding some python-biom-format tests fail with python3.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.)


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

Package: src:python-biom-format
Version: 2.1.7+dfsg-3
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

==
ERROR: Test an invalid HDF5 table
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/decorators.py", 
line 155, in skipper_func

return f(*args, **kwargs)
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/tests/test_cli/test_validate_table.py", 
line 88, in test_invalid_hdf5

copy(self.hdf5_file_valid, 'invalid.hdf5')
  File "/usr/lib/python3.8/shutil.py", line 409, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 259, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 
'/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/examples/min_sparse_otu_table_hdf5.biom'


==
ERROR: Test a valid HDF5 table
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/decorators.py", 
line 155, in skipper_func

return f(*args, **kwargs)
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/tests/test_cli/test_validate_table.py", 
line 79, in test_valid_hdf5

obs = self.cmd(table=self.hdf5_file_valid)
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/cli/table_validator.py", 
line 112, in __call__

return self.run(table=table, format_version=format_version,
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/cli/table_validator.py", 
line 78, in run

is_json = not is_hdf5_file(kwargs['table'])
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/util.py", 
line 518, in is_hdf5_file

with open(fp, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 
'/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/examples/min_sparse_otu_table_hdf5.biom'


==
ERROR: test_valid_hdf5_metadata_v210 
(biom.tests.test_cli.test_validate_table.TableValidatorTests)

--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/decorators.py", 
line 155, in skipper_func

return f(*args, **kwargs)
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/tests/test_cli/test_validate_table.py", 
line 62, in test_valid_hdf5_metadata_v210

obs = self.cmd(table=self.hdf5_file_valid,
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/cli/table_validator.py", 
line 112, in __call__

return self.run(table=table, format_version=format_version,
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/cli/table_validator.py", 
line 78, in run

is_json = not is_hdf5_file(kwargs['table'])
  File 
"/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/biom/util.py", 
line 518, in is_hdf5_file

with open(fp, 'rb') as f:
FileNotFoundError: [Errno 2] No such file or directory: 
'/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build/examples/min_sparse_otu_table_hdf5.biom'


--
Ran 336 tests in 4.624s

FAILED (SKIP=1, errors=3)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd 
/<>/python-biom-format-2.1.7+dfsg/.pybuild/cpython3_3.8_biom-format/build; 
python3.8 -m nose -v
dh_auto_test: pybuild --test --test-nose -i python{version} -p "3.8 3.7" 
returned exit code 13
--- End Message ---
--- Begin Message ---
Source: 

Bug#945263: marked as done (f2py3.8 fails with "Entry point not found" exception)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 07:04:14 +
with message-id 
and subject line Bug#945263: fixed in numpy 1:1.17.4-5
has caused the Debian Bug report #945263,
regarding f2py3.8 fails with "Entry point not found" exception
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.)


-- 
945263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:numpy
Version: 1:1.17.4-3
Severity: serious
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

f2py3.8 fails with "Entry point not found" exception.

patch at
http://launchpadlibrarian.net/452313700/numpy_1%3A1.17.4-3ubuntu1_1%3A1.17.4-3ubuntu2.diff.gz

Another solution might be to loop around the py3 versions in building f2py_cmds
in setup.py.
--- End Message ---
--- Begin Message ---
Source: numpy
Source-Version: 1:1.17.4-5

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Dec 2019 01:50:13 -0500
Source: numpy
Architecture: source
Version: 1:1.17.4-5
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 945263
Changes:
 numpy (1:1.17.4-5) unstable; urgency=medium
 .
   * debian/rules
 - edit entry_points.txt only if it's present, fixing a FTBFS for arch:all;
   Closes: #945263
Checksums-Sha1:
 54380b22be211af5caede6df621ad8ace57b0c95 2654 numpy_1.17.4-5.dsc
 df060e0effc2597ffa8ca757066ff944c4830523 30216 numpy_1.17.4-5.debian.tar.xz
 197ef6f5db225a945c7b30e25bef72052e4c5ec7 10907 numpy_1.17.4-5_source.buildinfo
Checksums-Sha256:
 a5f77e3d7357b8b09fb83c903ddb3c1b691300a51527508509d09927698c09cb 2654 
numpy_1.17.4-5.dsc
 e3493e3b82bc83694c64fbb699368f7501fcb935ddd264f364d12281016a1d90 30216 
numpy_1.17.4-5.debian.tar.xz
 02c53eb9565d0697d31b4d26ae85a9307dc62b040b556e1f62ac5ac7e77c0416 10907 
numpy_1.17.4-5_source.buildinfo
Files:
 307b0935744a626dc334c359100125a6 2654 python optional numpy_1.17.4-5.dsc
 7d9fbe45739a706c57091aca6f431196 30216 python optional 
numpy_1.17.4-5.debian.tar.xz
 6739e70eb0d1763ba645bc15b20f2ad0 10907 python optional 
numpy_1.17.4-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3/Ej4ACgkQh588mTgB
qU9QbBAAz0g/xA1w/VKV4ytGZxRcXCLZQvRxn9MOq6VXZ72ut8+Cdw5ZZLJ3H9+k
FGEX3BggsZDtLX90lOlk8xCQktrANH9BczH0CAM5Om7agOKVAWZcdtYeOTvJsZfM
RtiB6pj74EloOG8IKWZeAnXLB77y/jEBxlnMibCLQeLb2vCgmqbOxyZhnxQ1Yd3j
SnGk6KtKx0VN9Jf1s7k65Y6HAioLCrhvjA9DZCSdiSTE2sHozPU4zrXdzvDT/teQ
a3X5sm1VhzstjKtMKn8ToxNSvr5B9sRNml5oWOei6NdpHtHksQZXMelZeRi/xLMu
D9DwTlmqiLIhtDSSQ3Yejs+1I9eMbi2KsgNtQwpztMlgXVMOHpKPZn9F+e61thak
CyMR3vYhE+ux7gIqUnQ9t12mycF43tuUWxLgLiV47WrZK/D6oHQaSMo/eWAetfCi
seW7ABthhLnfdzug0aiReUR9HlyHTjmytIgwYZYFTi56uG5BeijTtxDg6oDQS2pN
9oudjmV6c0GO5vOU8ZsB43GLRKwBt8vvnl4BHUNc3x726Jgz9NTPSlyyO2QpeSoK
0k7UuZVnPHE36XeXhZv+EsaK2aEr0NSPev45cRVi7nTITJ4/QtGcPAl1hC4gQOMm
lBgwOKRGihtaU/QR9s9dY/03Z3KY1VGuX1heX6FsXEazNb/UpNo=
=NQXV
-END PGP SIGNATURE End Message ---

Processed: dwz: returns exit status 1, causing FTBFS in deal.ii

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #946255 [src:deal.ii] dwz: returns exit status 1, causing FTBFS in deal.ii
Severity set to 'serious' from 'important'
> tags -1 + pending
Bug #946255 [src:deal.ii] dwz: returns exit status 1, causing FTBFS in deal.ii
Added tag(s) pending.
> block -1 by 944688
Bug #946255 [src:deal.ii] dwz: returns exit status 1, causing FTBFS in deal.ii
946255 was not blocked by any bugs.
946255 was not blocking any bugs.
Added blocking bug(s) of 946255: 944688

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

Bug#943786: lmfit-py: failing tests with python3.8

[Andreas Tille]

Hi Alexandre,

since you previously did some commits fixing a RC bug:  It would help if
you make some noise on the Debian Science list to get the fix sponsored.
May be it was not the best idea of mine to bump to the new upstream
version since it created new trouble.  If you have some idea how to fix
it, please commit and ping me.

Kind regards
Andreas.

On Sat, Dec 21, 2019 at 11:30:02PM +0100, Andreas Tille wrote:
> Hi,
> 
> I tried hard to get lmfit-py (now at upstream version 1.0.0) building
> but I endet up with 
> 
> 
> build succeeded, 73 warnings.
> 
> The HTML pages are in build/html.
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py", line 
> 313, in sumarize_failing_examples
> "\n" + "-" * 79)
> ValueError: Here is a summary of the problems encountered when running the 
> examples
> 
> Examples expected to fail, but not failing:
> Please remove these examples from
> sphinx_gallery_conf['expected_failing_examples']
> /build/lmfit-py-1.0.0/examples/documentation/model_loadmodel.py
> 
> 
> 
> The full sphinx log says:
> 
> 
> # Sphinx version: 1.8.5
> # Python version: 3.7.6 (CPython)
> # Docutils version: 0.15.2 release
> # Jinja2 version: 2.10.1
> # Last messages:
> #   done
> #   copying extra files...
> #   done
> #   dumping search index in English (code: en) ...
> #   done
> #   dumping object inventory...
> #   done
> #   build succeeded, 73 warnings.
> #...
> #   The HTML pages are in build/html.
> # Loaded extensions:
> #   sphinx.ext.mathjax (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/mathjax.py
> #   alabaster (0.7.8) from 
> /usr/lib/python3/dist-packages/alabaster/__init__.py
> #   sphinx.ext.autodoc (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/autodoc/__init__.py
> #   sphinx.ext.extlinks (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/extlinks.py
> #   sphinx.ext.intersphinx (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py
> #   sphinx.ext.napoleon (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/napoleon/__init__.py
> #   sphinx.ext.todo (1.8.5) from 
> /usr/lib/python3/dist-packages/sphinx/ext/todo.py
> #   IPython.sphinxext.ipython_console_highlighting (unknown version) from 
> /usr/lib/python3/dist-packages/IPython/sphinxext/ipython_console_highlighting.py
> #   sphinx_gallery.gen_gallery (0.2.0) from 
> /usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 304, in 
> build_main
> app.build(args.force_all, filenames)
>   File "/usr/lib/python3/dist-packages/sphinx/application.py", line 369, in 
> build
> self.emit('build-finished', None)
>   File "/usr/lib/python3/dist-packages/sphinx/application.py", line 510, in 
> emit
> return self.events.emit(event, self, *args)
>   File "/usr/lib/python3/dist-packages/sphinx/events.py", line 80, in emit
> results.append(callback(*args))
>   File "/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py", line 
> 313, in sumarize_failing_examples
> "\n" + "-" * 79)
> ValueError: Here is a summary of the problems encountered when running the 
> examples
> 
> Examples expected to fail, but not failing:
> Please remove these examples from
> sphinx_gallery_conf['expected_failing_examples']
> /build/lmfit-py-1.0.0/examples/documentation/model_loadmodel.py
> ---
> 
> 
> 
> Any idea how to fix this?
> 
> 
> Kind regards
> 
>Andreas.
> 
> 
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

Bug#938270: marked as done (python-x2go: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 05:04:24 +
with message-id 
and subject line Bug#938270: fixed in python-x2go 0.6.1.1-1.1
has caused the Debian Bug report #938270,
regarding python-x2go: 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.)


-- 
938270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938270
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-x2go
Version: 0.6.0.2-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:python-x2go

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 ---
Source: python-x2go
Source-Version: 0.6.1.1-1.1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-x2go package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Dec 2019 23:32:09 -0500
Source: python-x2go
Architecture: source
Version: 0.6.1.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Sandro Tosi 
Closes: 938270
Changes:
 python-x2go (0.6.1.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #938270
Checksums-Sha1:
 15a8cda6a5fab495457a2f2e8113340ce1d5ad04 2403 python-x2go_0.6.1.1-1.1.dsc
 7f5066007b5aff670fd40aa15507750d28a14471 25968 
python-x2go_0.6.1.1-1.1.debian.tar.xz
 74d618a3dbb55c8a5fe7c55d735e7bcbbdc28936 7440 
python-x2go_0.6.1.1-1.1_source.buildinfo
Checksums-Sha256:
 c43e84872322a69394cb5972dcb74ad0a66bb7a3c8da3004ffa54945fe3e2152 2403 
python-x2go_0.6.1.1-1.1.dsc
 9f57fcbe90c09fa93f61e5623ca13984a0d098a5ebc1edc96b975656e2313e57 25968 
python-x2go_0.6.1.1-1.1.debian.tar.xz
 6d4fbd9a76f6eff7092325bb159193e1871415b0e4d7be947fdd4a20f1c9a820 7440 

Bug#941527: marked as done (Build-depends on Qt4)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 03:19:36 +
with message-id 
and subject line Bug#941527: fixed in matplotlib 3.1.2-1
has caused the Debian Bug report #941527,
regarding Build-depends on Qt4
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.)


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

matplotlib build-depends on python3-pyqt4 (build from src:python-qt4), which is 
being
removed along with Qt4 itself now.

Given that matplotlib only has a run-time Suggests: on python3-pyqt4, this is 
probably
optional and simply be disabled.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 3.1.2-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 21:56:14 -0500
Source: matplotlib
Architecture: source
Version: 3.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 941527 942766 943169 945169
Changes:
 matplotlib (3.1.2-1) unstable; urgency=medium
 .
   * New upstream release; Closes: #945169
   * debian/copyright
 - update copyright for new upstream release
 - extend packaging copyright years
   * debian/control
 - bump Standards-Version to 4.4.1 (no changes needed)
 - drop Qt4 from depends; Closes: #941527
 - add sphinx-copybutton to b-d, needed by doc
   * debian/tests/
 - drop python2 tests and test Qt5 instead of Qt4; Closes: #943169
   * debian/patches/
 - refresh/drop patches as per new upstream code
   * debian/rules
 - error out in case of a failure during build or install targets; patch by
   Matthias Klose; Closes: #942766
 - skip tests!! temporary measure due to
   https://github.com/matplotlib/matplotlib/issues/15960
   * debian/patches/0016-use-packaged-jquery.patch
 - use the packaged JQuery and JQuery UI
Checksums-Sha1:
 6d2df82a67906f9ef79a4ba45054091f104196a1 3304 matplotlib_3.1.2-1.dsc
 45e61b14e71090804d0a7cd44fd20cc52b0547e0 32889032 matplotlib_3.1.2.orig.tar.xz
 02c48eb1a3fc52286cf5c2bb28644da14474c405 33616 matplotlib_3.1.2-1.debian.tar.xz
 569727ade7c5a954b21534d5dd80e9c894cf3fac 22183 
matplotlib_3.1.2-1_source.buildinfo
Checksums-Sha256:
 25895645499ca5141cfc136b295a12dbbfc0203a156933f2f8e8f352f465a6bb 3304 
matplotlib_3.1.2-1.dsc
 05b4d6c5a5c1792ca4b875f2e6ae2adfffcf4413569ea1b1a6f6a7fd0b5bc288 32889032 
matplotlib_3.1.2.orig.tar.xz
 90fede4a675c01d2fed26a36c351286901500a95001e21396b5124417c332b40 33616 
matplotlib_3.1.2-1.debian.tar.xz
 8c44a11c30bf2b69c2bb2b2e30d32856908f6580f192e0c45e769740f1186669 22183 
matplotlib_3.1.2-1_source.buildinfo
Files:
 ea0562d766ae0a0b6811eaa8c89b9c23 3304 python optional matplotlib_3.1.2-1.dsc
 d9a3a686ba6af55f84f240a2bc732555 32889032 python optional 
matplotlib_3.1.2.orig.tar.xz
 88247d0452ce5b5c657c58953df4774b 33616 python optional 
matplotlib_3.1.2-1.debian.tar.xz
 c9aef7fed0939a300aa0892425a65828 22183 python optional 
matplotlib_3.1.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3+2+cACgkQh588mTgB
qU9lfhAAu9NIwnbRo8Y9oPBV5+ICMkuEAxEla/ci8CustiLMu7X1TiASliRSv/8Q
jX7VKad54BIRBgTE2sNtGRzgxHT+Jy2LvG7IqoBiPACoy4zUYr+hjWrUQ7SWunoD
MRO+2dzAGC402EUj3920xQieAbwi2jvntT8bBj8NVyemV0RfCTECsh6Xn3X0DSZ6
0FJ9wIffkiUWbrfuESCtp9UwGdFs9zNLC6jAvINpfKglaO7xshu2BL+BfiLn8mnG
pOXiNuqrfUNaS3AZ+ROTK1rYD1QnPcsII6zfs8BXkNU5LjC89/XzfxJlt8ibzsE4
otE4nQ7/KgO9RdWPbipm7pkbQjxjrRFBhMBEOCQiwPwlolURvEfyLk/TIYao7AIC
P8IV4w0Vr6xrS8xjodc1/SaQ+yUxoYufCSWW7ofu2BqsyCcKusg6vFHvwFeV1B/s
xRwfKJeXqUxY2ItBcu2aeAe3xdoHCUZ109kORsVi2VNAhAcbxlHr3h7hItlNLkxr
Bk4hKDhlvKiTiCbNCSUNP87cjCoJwAemdzRKu1Cw5Cahh/waY6aTl5dBTf91BJ6v
pe7l1MZK7zB2xruOvVcqF+wzVoAf4dCGmoIwQNmFZcDDg1FhWkGXaIEI6FKTIZP1
IrgnFXtqjH01kWoJnLyDLUKSvTQ6ojVCuzqmw0Ya0Exnq37lnoU=
=bmnI

Bug#942766: marked as done (matplotlib should error out when failing to build/install)

[Debian Bug Tracking System]

Your message dated Sun, 22 Dec 2019 03:19:36 +
with message-id 
and subject line Bug#942766: fixed in matplotlib 3.1.2-1
has caused the Debian Bug report #942766,
regarding matplotlib should error out when failing to build/install
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.)


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

Package: src:matplotlib
Version: 3.0.2-2
Severity: important
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: python3.8

matplotlib should error out when failing to build/install. seen when matplotlib 
failed to build for unrelated reasons with python3.8.


http://launchpadlibrarian.net/447821439/matplotlib_3.0.2-2build1_3.0.2-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: matplotlib
Source-Version: 3.1.2-1

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 21:56:14 -0500
Source: matplotlib
Architecture: source
Version: 3.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 941527 942766 943169 945169
Changes:
 matplotlib (3.1.2-1) unstable; urgency=medium
 .
   * New upstream release; Closes: #945169
   * debian/copyright
 - update copyright for new upstream release
 - extend packaging copyright years
   * debian/control
 - bump Standards-Version to 4.4.1 (no changes needed)
 - drop Qt4 from depends; Closes: #941527
 - add sphinx-copybutton to b-d, needed by doc
   * debian/tests/
 - drop python2 tests and test Qt5 instead of Qt4; Closes: #943169
   * debian/patches/
 - refresh/drop patches as per new upstream code
   * debian/rules
 - error out in case of a failure during build or install targets; patch by
   Matthias Klose; Closes: #942766
 - skip tests!! temporary measure due to
   https://github.com/matplotlib/matplotlib/issues/15960
   * debian/patches/0016-use-packaged-jquery.patch
 - use the packaged JQuery and JQuery UI
Checksums-Sha1:
 6d2df82a67906f9ef79a4ba45054091f104196a1 3304 matplotlib_3.1.2-1.dsc
 45e61b14e71090804d0a7cd44fd20cc52b0547e0 32889032 matplotlib_3.1.2.orig.tar.xz
 02c48eb1a3fc52286cf5c2bb28644da14474c405 33616 matplotlib_3.1.2-1.debian.tar.xz
 569727ade7c5a954b21534d5dd80e9c894cf3fac 22183 
matplotlib_3.1.2-1_source.buildinfo
Checksums-Sha256:
 25895645499ca5141cfc136b295a12dbbfc0203a156933f2f8e8f352f465a6bb 3304 
matplotlib_3.1.2-1.dsc
 05b4d6c5a5c1792ca4b875f2e6ae2adfffcf4413569ea1b1a6f6a7fd0b5bc288 32889032 
matplotlib_3.1.2.orig.tar.xz
 90fede4a675c01d2fed26a36c351286901500a95001e21396b5124417c332b40 33616 
matplotlib_3.1.2-1.debian.tar.xz
 8c44a11c30bf2b69c2bb2b2e30d32856908f6580f192e0c45e769740f1186669 22183 
matplotlib_3.1.2-1_source.buildinfo
Files:
 ea0562d766ae0a0b6811eaa8c89b9c23 3304 python optional matplotlib_3.1.2-1.dsc
 d9a3a686ba6af55f84f240a2bc732555 32889032 python optional 
matplotlib_3.1.2.orig.tar.xz
 88247d0452ce5b5c657c58953df4774b 33616 python optional 
matplotlib_3.1.2-1.debian.tar.xz
 c9aef7fed0939a300aa0892425a65828 22183 python optional 
matplotlib_3.1.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3+2+cACgkQh588mTgB
qU9lfhAAu9NIwnbRo8Y9oPBV5+ICMkuEAxEla/ci8CustiLMu7X1TiASliRSv/8Q
jX7VKad54BIRBgTE2sNtGRzgxHT+Jy2LvG7IqoBiPACoy4zUYr+hjWrUQ7SWunoD
MRO+2dzAGC402EUj3920xQieAbwi2jvntT8bBj8NVyemV0RfCTECsh6Xn3X0DSZ6
0FJ9wIffkiUWbrfuESCtp9UwGdFs9zNLC6jAvINpfKglaO7xshu2BL+BfiLn8mnG
pOXiNuqrfUNaS3AZ+ROTK1rYD1QnPcsII6zfs8BXkNU5LjC89/XzfxJlt8ibzsE4
otE4nQ7/KgO9RdWPbipm7pkbQjxjrRFBhMBEOCQiwPwlolURvEfyLk/TIYao7AIC
P8IV4w0Vr6xrS8xjodc1/SaQ+yUxoYufCSWW7ofu2BqsyCcKusg6vFHvwFeV1B/s
xRwfKJeXqUxY2ItBcu2aeAe3xdoHCUZ109kORsVi2VNAhAcbxlHr3h7hItlNLkxr
Bk4hKDhlvKiTiCbNCSUNP87cjCoJwAemdzRKu1Cw5Cahh/waY6aTl5dBTf91BJ6v

Processed: Re: py2removal blocks updates - 2019-12-20 19:36:59.949400+00:00

[Debian Bug Tracking System]

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

> unblock 938473 by 943162
Bug #938473 [src:sgmltools-lite] sgmltools-lite: Python2 removal in sid/bullseye
938473 was blocked by: 943162
938473 was blocking: 937695
Removed blocking bug(s) of 938473: 943162
> thanks
Stopping processing here.

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

Processed: Bug#942766 marked as pending in matplotlib

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #942766 [src:matplotlib] matplotlib should error out when failing to 
build/install
Added tag(s) pending.

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

Bug#942766: marked as pending in matplotlib

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/matplotlib/commit/3b7e69d7c6da92fad07f07f7ab36c5530e31ff3e


error out in case of a failure during build or install targets; patch by 
Matthias Klose; Closes: #942766


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942766

Bug#938840: xcffib: Python2 removal in sid/bullseye

[peter green]

I just tried removing the build-dependency on python-autopep8 and other than 
file date changes, there did not seem to be any changes in the resulting 
packagse, so I decided to go ahead with a NMU.

While preparing the NMU I noticed that the clean target was not cleaning up 
properly, so I fixed that too.

Debdiff is attached, NMU is in delayed/5.

diff -Nru xcffib-0.8.1/debian/changelog xcffib-0.8.1/debian/changelog
--- xcffib-0.8.1/debian/changelog   2019-09-07 09:47:56.0 +
+++ xcffib-0.8.1/debian/changelog   2019-12-22 01:57:12.0 +
@@ -1,3 +1,11 @@
+xcffib (0.8.1-0.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove build-depends on python-autopep8 (downgrades: 938840)
+  * Fix clean target.
+
+ -- Peter Michael Green   Sun, 22 Dec 2019 01:57:12 +
+
 xcffib (0.8.1-0.5) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru xcffib-0.8.1/debian/control xcffib-0.8.1/debian/control
--- xcffib-0.8.1/debian/control 2019-07-26 07:27:42.0 +
+++ xcffib-0.8.1/debian/control 2019-12-22 01:57:02.0 +
@@ -22,7 +22,6 @@
   , libghc-either-dev
   , python-setuptools
   , python3-setuptools
-  , python-autopep8
   , python-all
   , python3-all
   , python-cffi
diff -Nru xcffib-0.8.1/debian/rules xcffib-0.8.1/debian/rules
--- xcffib-0.8.1/debian/rules   2019-09-07 09:47:56.0 +
+++ xcffib-0.8.1/debian/rules   2019-12-22 01:57:12.0 +
@@ -10,6 +10,8 @@
 # we can't use setup.py clean here, since it checks for the existence of 
xcffib/
 override_dh_auto_clean:
make clean
+   rm -rf debian/cabalconfig
+   rm -rf .ghc.environment.*
 
 %:
dh $@ --with python2,python3 --buildsystem=pybuild

Bug#937834: python-iniparse: Python2 removal in sid/bullseye

[Stuart Prescott]

Control: tags -1 pending

I've prepared an upload for this package and made a MR on salsa with the 
relevant changes.

https://salsa.debian.org/debian/python-iniparse/merge_requests/1

I'll upload this once #936346 is fixed.

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Processed: Re: Bug#937834: python-iniparse: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #937834 [src:python-iniparse] python-iniparse: Python2 removal in 
sid/bullseye
Added tag(s) pending.

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

Bug#946629: marked as done (tilix: fails to start after upgrade)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 23:51:44 +
with message-id 
and subject line Bug#946629: fixed in tilix 1.9.3-4
has caused the Debian Bug report #946629,
regarding tilix: fails to start after upgrade
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.)


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

hey, 

after latest upgrade to version 1.9.3-3, tilix won't start.. 
there was a post-install message during upgrade :

...
Processing triggers for libglib2.0-0:amd64 (2.62.3-2) ...
/usr/share/glib-2.0/schemas/com.gexperts.Tilix.gschema.xml:207:1  Failed to pars
e  value of type “s”: 0:expected value.  This entire file has been igno
red.
...

then after upgrade completes, tilix won't start. error : 
$ tilix

(tilix:6051): Gtk-WARNING **: 11:19:53.847: Theme parsing error: 
gtk-widgets.css:1214:18: Not using units is deprecated. Assuming 'px'.

(tilix:6051): GLib-GIO-ERROR **: 11:19:53.866: Settings schema 
'com.gexperts.Tilix.Keybindings' is not installed
[1]6051 trace trap  tilix


thanks in advance,
d.

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

Kernel: Linux 5.4.2-gnu (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages tilix depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  libc62.29-6
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
--- End Message ---
--- Begin Message ---
Source: tilix
Source-Version: 1.9.3-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 22 Dec 2019 10:14:24 +0100
Source: tilix
Architecture: source
Version: 1.9.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Matthias Klumpp 
Closes: 940239 946629
Changes:
 tilix (1.9.3-4) unstable; urgency=medium
 .
   * default-tab-title.patch: Add missing quotemarks (Closes: #946629)
   * Adjust wrapper script to mention Tilix, not Terminix (Closes: #940239)
Checksums-Sha1:
 f4a287946e8b83db684ad3174d22369ab7d9ea82 2128 tilix_1.9.3-4.dsc
 56ebf04441551da01d70a1e99450b77672e025e3 837010 tilix_1.9.3.orig.tar.gz
 c26ca17ca9050adb6fa82602da20548ee9ca5a4e 23248 tilix_1.9.3-4.debian.tar.xz
 9c9a9de432e15ef7bb82294abf57ea6c1fbe1b6f 9370 tilix_1.9.3-4_source.buildinfo
Checksums-Sha256:
 a478ea158cf5e762ebe68eae2da00c14d0bb69ecb9867d751d7b0bd18f88a340 2128 
tilix_1.9.3-4.dsc
 f1b4dbbd60f4b9a91e0ab0954e3e6b8ebe5442d5fbb760a554a733903e44a1de 837010 
tilix_1.9.3.orig.tar.gz
 67a04eab7ad9f0e5128ea8103144cd00cecb5010d01a6fb60480b52390141d1c 23248 
tilix_1.9.3-4.debian.tar.xz
 76ec8b4b94f1cfdb19ea13869d45cb516427d8f293773101c0ef678910dc57a4 9370 
tilix_1.9.3-4_source.buildinfo
Files:
 3416b478b1dc55993dacea9118e4f7d0 2128 gnome optional tilix_1.9.3-4.dsc
 e17109f434011f79981fd7d1bef8da24 837010 gnome optional tilix_1.9.3.orig.tar.gz
 3bd4162b62a473d052444c4dab95cbb8 23248 gnome optional 
tilix_1.9.3-4.debian.tar.xz
 ade5c402f59cfc254df6ff8948aed5b2 9370 gnome optional 
tilix_1.9.3-4_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Bug#946629 marked as pending in tilix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #946629 [tilix] tilix: fails to start after upgrade
Added tag(s) pending.

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

Bug#946629: marked as pending in tilix

[Matthias Klumpp]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/tilix/commit/d4d54429efef18b0682d48feda785bf61518ce44


default-tab-title.patch: Add missing quotemarks (Closes: #946629)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/946629

Bug#946422: silx: autopkgtest regression: pocl error

[Andreas Beckmann]

Control: severity -1 important

I've now filed #947148 against openmpi 4 which seems to break lt_dlopen()

Andreas

Processed: Re: Bug#946422: silx: autopkgtest regression: pocl error

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #946422 [src:silx] silx: autopkgtest regression: pocl error
Severity set to 'important' from 'serious'

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

Processed: Re: Bug#946422: silx: autopkgtest regression: pocl error

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #946582 [pocl] silx: autopkgtest regression: pocl error
Bug #946583 [pocl] silx: autopkgtest regression: pocl error
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'

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

Bug#947148: openmpi: causes lt_dlopen() to fail with 'can't close resident module'

[Andreas Beckmann]

Source: openmpi
Version: 4.0.2-4
Severity: serious
Control: block 946422 with -1
Control: block 946582 with -1

Hi,

this bug was initially observed as a silx autopkgtest failure (#946422)
in pocl (#946582). I've reduced it to a python-free OpenCL example in C
and now I'm convinced that it is caused by by OpenMPI 4.

Attached you can find a trivial OpenCL example (yes, that needs a bit of
boilerplate code) that is linked against MPI and calls MPI_Init().
This works fine with OpenMPI 3 in buster, MPICH in sid (and no MPI as
well), but fails with OpenMPI 4 in sid.

You need opencl-dev and libopenmpi-dev to build it and pocl-opencl-icd
to run it.
You build it with 
 mpicc -o test_mpi_ocl test_mpi_ocl.c -lOpenCL
and get this when running successfully:

# ./test_mpi_ocl 
Success

but the failure with OpenMPI 4 is

# ./test_mpi_ocl 
pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close resident 
module'.
note: missing symbols in the kernel binary might be reported as 'file not 
found' errors.
Aborted

OpenMPI 4 seems to change some state causing subsequent lt_dlopen() to fail.

In gdb we have 
(gdb) bt
#0  0x77d10081 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x77cfb535 in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x7fffed2b66d1 in pocl_check_kernel_dlhandle_cache 
(cmd=cmd@entry=0x5562b730, initial_refcount=initial_refcount@entry=1) at 
./lib/CL/devices/common.c:1097
#3  0x7fffed2bc327 in pocl_pthread_prepare_kernel (cmd=0x5562b730, 
data=0x556cb5e0) at ./lib/CL/devices/pthread/pthread_scheduler.c:413
#4  pocl_pthread_exec_command (td=0x556cd200, cmd=0x5562b730) at 
./lib/CL/devices/pthread/pthread_scheduler.c:450
#5  pocl_pthread_driver_thread (p=) at 
./lib/CL/devices/pthread/pthread_scheduler.c:496
#6  0x779aafb7 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#7  0x77dd02df in clone () from /lib/x86_64-linux-gnu/libc.so.6

The error stems from line lib/CL/devices/common.c 1062
ci->dlhandle = lt_dlopen (module_fn);
where module_fn = 
"//.cache/pocl/kcache/IL/PFLJNNHLKAHONADOJOEENLMDLFHDJKOMFJHEO/foo/1-1-1/foo.so"

OK, we can further minimize this testcase if we just take foo.so
(amd64 version attached) and lt_dlopen() it:

// mpicc -o test_lt_dlopen test_lt_dlopen.c -lltdl 

#include 
#include 
#include 

int main(int argc, char **argv)
{
MPI_Init(, );
lt_dlinit();
lt_dlhandle handle = lt_dlopen ("./foo.so");
const char * dl_error = lt_dlerror ();
printf("%p %s\n", handle, dl_error ? dl_error : "(null)");
}

Without OpenMPI 4 we succeed:
# ./test_lt_dlopen
0x55c4accfc480 (null)

but with OpenMPI 4 we run into the same problem:
# ./test_lt_dlopen
0x559b5c923250 can't close resident module

Andreas
// install packages
// apt-get install libopenmpi-dev opencl-dev pocl-opencl-icd
// compile with
// mpicc -o test_mpi_ocl test_mpi_ocl.c -lOpenCL

// based on https://wiki.aalto.fi/display/HPEC/OpenCL+tutorial

#define CL_TARGET_OPENCL_VERSION 100

// 0a_trivial.c
#include 
#include 
 
#ifdef __APPLE__
#include 
#else
#include 
#endif

#include 

/* A kernel which does nothing */
const char * source_str  = "__kernel void foo(void)"
   "{"
   ""
   "}";

int main(int argc, char** argv) {
MPI_Init(, );

/* Get platform and device information */
cl_platform_id platform_id = NULL;
cl_device_id device_id = NULL;   
cl_uint num_devices;
cl_uint num_platforms;
cl_int ret = clGetPlatformIDs(1, _id, _platforms);
ret = clGetDeviceIDs( platform_id, CL_DEVICE_TYPE_CPU, 1, _id, 
_devices);
 
/* Create an OpenCL context */
cl_context context = clCreateContext( NULL, 1, _id, NULL, NULL, 
);
 
/* Create a command queue */
cl_command_queue command_queue = clCreateCommandQueue(context, device_id, 
0, );
 
/* Create a program from the kernel source */
cl_program program = clCreateProgramWithSource(context, 1, _str, 
NULL, );
 
/* Build the program */
ret = clBuildProgram(program, 1, _id, NULL, NULL, NULL);
 
/* Create the OpenCL kernel */
cl_kernel kernel = clCreateKernel(program, "foo", );
 
/* Execute the OpenCL kernel */
size_t global_item_size = 1;
size_t local_item_size = 1;
ret = clEnqueueNDRangeKernel(command_queue, kernel, 1, NULL, 
_item_size, _item_size, 0, NULL, NULL);

ret = clFlush(command_queue);
ret = clFinish(command_queue);

if (ret == CL_SUCCESS)
printf("Success\n");
else
printf("OpenCL error executing kernel: %d\n", ret); 
 
/* Clean up */
ret = clReleaseKernel(kernel);
ret = clReleaseProgram(program);
ret = clReleaseCommandQueue(command_queue);
ret = clReleaseContext(context);
return 0;
}
// mpicc -o test_lt_dlopen test_lt_dlopen.c -lltdl 

#include 
#include 
#include 

int main(int argc, char **argv)
{
MPI_Init(, );
  

Processed: openmpi: causes lt_dlopen() to fail with 'can't close resident module'

[Debian Bug Tracking System]

Processing control commands:

> block 946422 with -1
Bug #946422 [src:silx] silx: autopkgtest regression: pocl error
946422 was not blocked by any bugs.
946422 was not blocking any bugs.
Added blocking bug(s) of 946422: 947148
> block 946582 with -1
Bug #946582 [pocl] silx: autopkgtest regression: pocl error
Bug #946583 [pocl] silx: autopkgtest regression: pocl error
946582 was not blocked by any bugs.
946582 was not blocking any bugs.
Added blocking bug(s) of 946582: 947148
946583 was not blocked by any bugs.
946583 was not blocking any bugs.
Added blocking bug(s) of 946583: 947148

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

Bug#943786: lmfit-py: failing tests with python3.8

[Andreas Tille]

Hi,

I tried hard to get lmfit-py (now at upstream version 1.0.0) building
but I endet up with 


build succeeded, 73 warnings.

The HTML pages are in build/html.

Exception occurred:
  File "/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py", line 
313, in sumarize_failing_examples
"\n" + "-" * 79)
ValueError: Here is a summary of the problems encountered when running the 
examples

Examples expected to fail, but not failing:
Please remove these examples from
sphinx_gallery_conf['expected_failing_examples']
/build/lmfit-py-1.0.0/examples/documentation/model_loadmodel.py



The full sphinx log says:


# Sphinx version: 1.8.5
# Python version: 3.7.6 (CPython)
# Docutils version: 0.15.2 release
# Jinja2 version: 2.10.1
# Last messages:
#   done
#   copying extra files...
#   done
#   dumping search index in English (code: en) ...
#   done
#   dumping object inventory...
#   done
#   build succeeded, 73 warnings.
#...
#   The HTML pages are in build/html.
# Loaded extensions:
#   sphinx.ext.mathjax (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/mathjax.py
#   alabaster (0.7.8) from /usr/lib/python3/dist-packages/alabaster/__init__.py
#   sphinx.ext.autodoc (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/autodoc/__init__.py
#   sphinx.ext.extlinks (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py
#   sphinx.ext.intersphinx (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/intersphinx.py
#   sphinx.ext.napoleon (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/napoleon/__init__.py
#   sphinx.ext.todo (1.8.5) from 
/usr/lib/python3/dist-packages/sphinx/ext/todo.py
#   IPython.sphinxext.ipython_console_highlighting (unknown version) from 
/usr/lib/python3/dist-packages/IPython/sphinxext/ipython_console_highlighting.py
#   sphinx_gallery.gen_gallery (0.2.0) from 
/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 304, in 
build_main
app.build(args.force_all, filenames)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 369, in 
build
self.emit('build-finished', None)
  File "/usr/lib/python3/dist-packages/sphinx/application.py", line 510, in emit
return self.events.emit(event, self, *args)
  File "/usr/lib/python3/dist-packages/sphinx/events.py", line 80, in emit
results.append(callback(*args))
  File "/usr/lib/python3/dist-packages/sphinx_gallery/gen_gallery.py", line 
313, in sumarize_failing_examples
"\n" + "-" * 79)
ValueError: Here is a summary of the problems encountered when running the 
examples

Examples expected to fail, but not failing:
Please remove these examples from
sphinx_gallery_conf['expected_failing_examples']
/build/lmfit-py-1.0.0/examples/documentation/model_loadmodel.py
---



Any idea how to fix this?


Kind regards

   Andreas.



-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Christian Kastner]

Hi all,

Regarding liblinear: I thought I already set the Maintainer to Debian
Science Team, I guess I missed it.

On 2019-12-21 20:11, Chen-Tse Tsai wrote:
> I've created an account on Salsa. 
> 
> Do you think we should remove cdbs and use another build system
> instead? Please let me know if you have any suggestion. I'm not
> familiar with other build systems.

Yep, the Debian Policy was updated and recommends dh now.

@Andreas: Chen-Tse and I discussed upgrading the package in October (I
think), but both did not have the time back then.

I could also help with some work starting on the 27th or so. As
src:liblinear and src:libsvm have the same upstream, they are quite
similar WRT to building, so src:liblinear (which is up to date) might
have some helpful ideas.

Given that the last libsvm update was a while ago, I wouldn't be
surprised if a transition were necessary.

Processed: severity of 946829 is serious

[Debian Bug Tracking System]

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

> severity 946829 serious
Bug #946829 [sa-exim] sa-exim: After upgrade SA: GREYLIST_ISWHITE skipped, 
insecure dependencies
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#938174: python-simpy: Python2 removal in sid/bullseye

[Andreas Tille]

Hi,

just a comment that this bug is

   Fix blocked by 937033: mgltools-scenario2: Python2 removal in sid/bullseye

mgltools-scenario2 is in non-free and chances that somebody will care
soon are not very high.  I'd consider it sensible to ignore this rdepends
and remove Python2 support from python-simpy.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

Hi Chen-Tse,

On Sat, Dec 21, 2019 at 02:11:23PM -0500, Chen-Tse Tsai wrote:
> I've created an account on Salsa.

Nice, I've added you to the science-team.

> Do you think we should remove cdbs and use another build system instead?

Yes.  Debian Science (and all other teams I'm aware of) are migrating to
debhelper with short dh.  You have an example in the just uploaded

   https://salsa.debian.org/science-team/liblinear

> Please let me know if you have any suggestion. I'm not familiar with other
> build systems.

Dh is considered simpler and more transparent.  If you might have
serious trouble either I (or someone from the Debian Science team who
might beat me) will do this for you.  I need to admit my time to do so
is extremely limited between 24.12. and 6.1. but I'm sure we'll manage
in the team somehow.

> Thanks
> Chen-Tse

Thanks a lot for your cooperation

 Andreas.
 
> On Sat, Dec 21, 2019 at 12:27 PM Andreas Tille  wrote:
> 
> > Hi Chen-Tse,
> >
> > thanks for you quick response.
> >
> > On Sat, Dec 21, 2019 at 09:48:14AM -0500, Chen-Tse Tsai wrote:
> > > Hi, Andreas,
> > >
> > > I agree with your suggestions. Thanks for putting it on salsa!
> >
> > Thanks for confirming.
> >
> > > Should I investigate dropping python2? I can spend some time this week on
> > > this. But I may need help with debian stuff.
> >
> > What exact help do you need?  Do you have a login on Salsa?  We could
> > add you to science-team to grant you commit permissions.  I admit I have
> > not yet looked into the packaging - just realised that its cdbs which is
> > unfortunate since it would not eliminate the Python2 dependency fully.
> >
> > Kind regards
> >
> >   Andreas.
> >
> > > On Sat, Dec 21, 2019 at 7:39 AM Andreas Tille  wrote:
> > >
> > > > On Sat, Dec 21, 2019 at 08:28:57AM +, Mo Zhou wrote:
> > > > > I second this proposal, and the same for src:liblinear.
> > > >
> > > > That's done as I wrote.
> > > >
> > > > > These are high popcon packages, dependencies for a number of other
> > > > > packages. They should be team maintained to unblock important fixes.
> > > >
> > > > To push a bit I just commited
> > > >
> > > >https://salsa.debian.org/science-team/libsvm
> > > >
> > > > Last maintainer upload was more than 3 years ago, 2 NMUs inbetween,
> > > > package is lagging behind upstream.  Anybody is kindly invited to adapt
> > > > the packaging (I think we should really get rid of cdbs since this in
> > > > turn is Python2) and proceed from here.
> > > >
> > > > Kind regards
> > > >
> > > >  Andreas.
> > > >
> > > >
> > > > > On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> > > > > > Hi Chen-Tse,
> > > > > >
> > > > > > I'm maintaining a package that depends from libsvm.  Due to bug
> > #936924
> > > > > > that did not received any response since August it is in danger to
> > be
> > > > > > removed from testing so I'm interested that this bug will be fixed.
> > > > > > When looking at the package I realised that while it would fit into
> > > > > > Debian Science team scope it is not team maintained nor is there
> > any
> > > > > > repository in Salsa.  That's why I have the following suggestion:
> > > > > >
> > > > > >   1. I create a repository on Salsa
> > > > > >   2. Move the package to Debian Science team maintenance
> > > > > >  and add you as Uploader
> > > > > >   3. Drop Python2 package and close bug #936924
> > > > > >   4. May be migrate packaging from cdbs to dh
> > > > > >
> > > > > > If I do not hear from you until Monday I assume you agree with this
> > > > > > plan and will do so.
> > > > > >
> > > > > > Kind regards
> > > > > >
> > > > > >  Andreas.
> > > > > >
> > > > > > PS: @Christian: I noticed that you and Chen-Tse are maintaining
> > > > > > liblinear.  I have just removed Python2 package and reassigned
> > > > > > #936889 to ftp.debian.org to make sure python-liblinear will
> > be
> > > > > > removed.  Thus libsvm can be dealt as suggested.
> > > > > >
> > > > > > --
> > > > > > http://fam-tille.de
> > > > > >
> > > > >
> > > > >
> > > >
> > > > --
> > > > http://fam-tille.de
> > > >
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Bug#938559: squaremap: Python2 removal in sid/bullseye

[Federico Ceratto]

A new version without Python 2 is being uploaded.

-- 
Federico

Bug#936889: marked as done (liblinear: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 14:40:34 -0500
with message-id 

and subject line Re: Please remove python-liblinear (Was: liblinear: Python2 
removal in sid/bullseye)
has caused the Debian Bug report #936889,
regarding liblinear: 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.)


-- 
936889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liblinear
Version: 2.1.0+dfsg-4
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:liblinear

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 ---
On Sat, 21 Dec 2019 08:25:28 +0100 Andreas Tille  wrote:
> Control: reassign -1
>
> Just uploaded liblinear without the python2 package - please
> remove it from testing

it will be done automatically by autocruft, nothing else to do here;
closing (and please do close these bugs when fixing them, testing
cruft and automation will take care of doing the right thing
downstream).


thanks!--- End Message ---

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

I've created an account on Salsa.

Do you think we should remove cdbs and use another build system instead?
Please let me know if you have any suggestion. I'm not familiar with other
build systems.

Thanks
Chen-Tse


On Sat, Dec 21, 2019 at 12:27 PM Andreas Tille  wrote:

> Hi Chen-Tse,
>
> thanks for you quick response.
>
> On Sat, Dec 21, 2019 at 09:48:14AM -0500, Chen-Tse Tsai wrote:
> > Hi, Andreas,
> >
> > I agree with your suggestions. Thanks for putting it on salsa!
>
> Thanks for confirming.
>
> > Should I investigate dropping python2? I can spend some time this week on
> > this. But I may need help with debian stuff.
>
> What exact help do you need?  Do you have a login on Salsa?  We could
> add you to science-team to grant you commit permissions.  I admit I have
> not yet looked into the packaging - just realised that its cdbs which is
> unfortunate since it would not eliminate the Python2 dependency fully.
>
> Kind regards
>
>   Andreas.
>
> > On Sat, Dec 21, 2019 at 7:39 AM Andreas Tille  wrote:
> >
> > > On Sat, Dec 21, 2019 at 08:28:57AM +, Mo Zhou wrote:
> > > > I second this proposal, and the same for src:liblinear.
> > >
> > > That's done as I wrote.
> > >
> > > > These are high popcon packages, dependencies for a number of other
> > > > packages. They should be team maintained to unblock important fixes.
> > >
> > > To push a bit I just commited
> > >
> > >https://salsa.debian.org/science-team/libsvm
> > >
> > > Last maintainer upload was more than 3 years ago, 2 NMUs inbetween,
> > > package is lagging behind upstream.  Anybody is kindly invited to adapt
> > > the packaging (I think we should really get rid of cdbs since this in
> > > turn is Python2) and proceed from here.
> > >
> > > Kind regards
> > >
> > >  Andreas.
> > >
> > >
> > > > On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> > > > > Hi Chen-Tse,
> > > > >
> > > > > I'm maintaining a package that depends from libsvm.  Due to bug
> #936924
> > > > > that did not received any response since August it is in danger to
> be
> > > > > removed from testing so I'm interested that this bug will be fixed.
> > > > > When looking at the package I realised that while it would fit into
> > > > > Debian Science team scope it is not team maintained nor is there
> any
> > > > > repository in Salsa.  That's why I have the following suggestion:
> > > > >
> > > > >   1. I create a repository on Salsa
> > > > >   2. Move the package to Debian Science team maintenance
> > > > >  and add you as Uploader
> > > > >   3. Drop Python2 package and close bug #936924
> > > > >   4. May be migrate packaging from cdbs to dh
> > > > >
> > > > > If I do not hear from you until Monday I assume you agree with this
> > > > > plan and will do so.
> > > > >
> > > > > Kind regards
> > > > >
> > > > >  Andreas.
> > > > >
> > > > > PS: @Christian: I noticed that you and Chen-Tse are maintaining
> > > > > liblinear.  I have just removed Python2 package and reassigned
> > > > > #936889 to ftp.debian.org to make sure python-liblinear will
> be
> > > > > removed.  Thus libsvm can be dealt as suggested.
> > > > >
> > > > > --
> > > > > http://fam-tille.de
> > > > >
> > > >
> > > >
> > >
> > > --
> > > http://fam-tille.de
> > >
>
> --
> http://fam-tille.de
>

Bug#943793: marked as done (libvncserver: CVE-2019-15681)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 19:02:33 +
with message-id 
and subject line Bug#943793: fixed in libvncserver 0.9.11+dfsg-1.3~deb9u2
has caused the Debian Bug report #943793,
regarding libvncserver: CVE-2019-15681
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.)


-- 
943793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvncserver
Version: 0.9.11+dfsg-1.3
Severity: grave
Tags: security upstream
Control: found -1 0.9.11+dfsg-1.3~deb9u1

Hi,

The following vulnerability was published for libvncserver, severity
is choosen to be rather on safe side and issue has not been fully
checked/investigated for impact/attack vector.

CVE-2019-15681[0]:
| LibVNC commit before d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a contains
| a memory leak (CWE-655) in VNC server code, which allow an attacker to
| read stack memory and can be abused for information disclosure.
| Combined with another vulnerability, it can be used to leak stack
| memory and bypass ASLR. This attack appear to be exploitable via
| network connectivity. These vulnerabilities have been fixed in commit
| d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-15681
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15681

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libvncserver
Source-Version: 0.9.11+dfsg-1.3~deb9u2

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated libvncserver 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: Mon, 16 Dec 2019 11:08:42 +0100
Source: libvncserver
Architecture: source
Version: 0.9.11+dfsg-1.3~deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Peter Spiess-Knafl 
Changed-By: Mike Gabriel 
Closes: 880531 905786 943793
Changes:
 libvncserver (0.9.11+dfsg-1.3~deb9u2) stretch; urgency=medium
 .
   * CVE-2019-15681:
 + rfbserver: don't leak stack memory to the remote. (Closes: #943793).
   * debian/patches:
 + Trivial patch rebasing.
 + Add 3 use-after-free patches. Resolve a freeze during connection
   closure and a segmentation fault on multi-threaded VNC servers. (Closes:
   #905786).
 + Add 0002-set-true-color-flag-to-1.patch. Fix connecting to VMware 
servers.
   (Closes: #880531).
Checksums-Sha1:
 743692ad8dc1a4a4569f447a02b719174e016aa6 2463 
libvncserver_0.9.11+dfsg-1.3~deb9u2.dsc
 9ff36c8dcf566f4badde6e3d199a74a723e384dd 22652 
libvncserver_0.9.11+dfsg-1.3~deb9u2.debian.tar.xz
 dcbb4a90bfdea47044ae972040874f98f939e20f 7212 
libvncserver_0.9.11+dfsg-1.3~deb9u2_source.buildinfo
Checksums-Sha256:
 eb6e0ecbceb91e96c02422a0d937b9a1b0bfa2d1ec36b3e01d60e43ebfcd70d7 2463 
libvncserver_0.9.11+dfsg-1.3~deb9u2.dsc
 b600e935b5a25b52192407e03fc91e4aa667fc10e2cf0ef99684c3d5c88dbd89 22652 
libvncserver_0.9.11+dfsg-1.3~deb9u2.debian.tar.xz
 5d54792938c6709e41acb1096a8332990927fde7b382fe4f5eae380b2246aa36 7212 
libvncserver_0.9.11+dfsg-1.3~deb9u2_source.buildinfo
Files:
 43ca10dc7baef25e62dc2f0e4fe2dc9d 2463 libs optional 
libvncserver_0.9.11+dfsg-1.3~deb9u2.dsc
 06d5745952a59ee91d7521e8c2d6a6ca 22652 libs optional 
libvncserver_0.9.11+dfsg-1.3~deb9u2.debian.tar.xz
 560f77c1a3749fe1e646aa05439ab8f0 7212 libs optional 
libvncserver_0.9.11+dfsg-1.3~deb9u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl33WOkVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxohsP/1wxOd3RifEBFy6rBGESi5qmNAGT
+3FuX98idptSXQQIlAGckbChKWFKbcaQRtfS2RkTjhGYWiGs/AE5qwC170v26OrA
1W0kf2Rm1k9OxWLec309b0wg81GCLTUcKamSfGXotjTk2lUYw0Rd7B0CLHxgvuPe
fBsydEHVnkw5U8lYzX2tUfEJQTRHnI2yICFOUjEAGuB0Dv3Rkm2/IjLxH57rOrcH

Bug#943793: marked as done (libvncserver: CVE-2019-15681)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 18:32:11 +
with message-id 
and subject line Bug#943793: fixed in libvncserver 0.9.11+dfsg-1.3+deb10u1
has caused the Debian Bug report #943793,
regarding libvncserver: CVE-2019-15681
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.)


-- 
943793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvncserver
Version: 0.9.11+dfsg-1.3
Severity: grave
Tags: security upstream
Control: found -1 0.9.11+dfsg-1.3~deb9u1

Hi,

The following vulnerability was published for libvncserver, severity
is choosen to be rather on safe side and issue has not been fully
checked/investigated for impact/attack vector.

CVE-2019-15681[0]:
| LibVNC commit before d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a contains
| a memory leak (CWE-655) in VNC server code, which allow an attacker to
| read stack memory and can be abused for information disclosure.
| Combined with another vulnerability, it can be used to leak stack
| memory and bypass ASLR. This attack appear to be exploitable via
| network connectivity. These vulnerabilities have been fixed in commit
| d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-15681
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15681

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libvncserver
Source-Version: 0.9.11+dfsg-1.3+deb10u1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated libvncserver package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 03 Dec 2019 09:18:57 +0100
Source: libvncserver
Architecture: source
Version: 0.9.11+dfsg-1.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Peter Spiess-Knafl 
Changed-By: Mike Gabriel 
Closes: 880531 905786 943793
Changes:
 libvncserver (0.9.11+dfsg-1.3+deb10u1) buster; urgency=medium
 .
   * CVE-2019-15681: rfbserver: don't leak stack memory to the remote. (Closes:
 #943793).
   * debian/patches:
 + Trivial patch rebasing.
 + Add 3 use-after-free patches. Resolve a freeze during connection closure 
and a
   segmentation fault on multi-threaded VNC servers. (Closes: #905786).
 + Add 0002-set-true-color-flag-to-1.patch. Fix connecting to VMware 
servers.
   (Closes: #880531).
Checksums-Sha1:
 68c8384f21515664e6a4f8bdcfc998a66b32d293 2467 
libvncserver_0.9.11+dfsg-1.3+deb10u1.dsc
 a0c10a557c68aa604d87ebacb9d3651b891812aa 22592 
libvncserver_0.9.11+dfsg-1.3+deb10u1.debian.tar.xz
 36548d1d30dd9c68815bb3d23b4e19bc9d3e7c0c 7216 
libvncserver_0.9.11+dfsg-1.3+deb10u1_source.buildinfo
Checksums-Sha256:
 a6838380dedfdd90d960d2068030f9177b83a9f57e82097075eb798cba0129c4 2467 
libvncserver_0.9.11+dfsg-1.3+deb10u1.dsc
 1933e3ecde58b516895bf783e641d7f77a40ced8a38145096160b677fce57dca 22592 
libvncserver_0.9.11+dfsg-1.3+deb10u1.debian.tar.xz
 c8cf84b2142ed61685ad74aae374d0c393301637ead23fec6eba24f152e747de 7216 
libvncserver_0.9.11+dfsg-1.3+deb10u1_source.buildinfo
Files:
 0e2e1d3e7d8ff3d8c119ae3a30b6748d 2467 libs optional 
libvncserver_0.9.11+dfsg-1.3+deb10u1.dsc
 444e39b7b634b16e141f4aa050b14279 22592 libs optional 
libvncserver_0.9.11+dfsg-1.3+deb10u1.debian.tar.xz
 0956fe16fd5c14c1de840e1422b7fc06 7216 libs optional 
libvncserver_0.9.11+dfsg-1.3+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl33VaAVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxWQgQALEj8qryVNjMROH2+GYpZAy/sOjp
5Z1Yn5LTiTrpsEyMnD3mm4bIcOdsAXxK8UgeeuamSHCfqDL7l6fzm3cwxgP9p9pA
4GZ6J7luekBQTqX0oZ+wiCtZzhmLq+09mF4xhGMXk+2hsVD+HT7HX1vxrW/ivYQH
BwfRA8WY3B/A5wHJHCuc23q48L8jesuNeOvO1taEtytp5mJWoKYDoUXN4KQF97QY

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

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 18:32:10 +
with message-id 
and subject line Bug#946669: fixed in libmatroska 1.4.9-1+deb10u1
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 

Bug#947129: marked as done (x2goclient: regression caused by CVE-2019-14889/libssh fix)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 17:37:48 +
with message-id 
and subject line Bug#947129: fixed in x2goclient 4.1.2.1-4
has caused the Debian Bug report #947129,
regarding x2goclient: regression caused by CVE-2019-14889/libssh fix
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.)


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

Package: x2goclient
Version: 4.1.2.1-3
Severity: serious
Control: found -1 4.0.3.1-4
Control: found -1 4.0.5.2-2

the recent libssh fix for CVE-2019-14889 causes a regresion in X2Go Client:

```
Connection failed. Couldn't create remote file  
~/.x2go/ssh/key.X18947 - SCP: Warning: status code 1 received:  
scp: ~/.x2go/ssh: No such file or directory"

```

The solution to this is a fix to be applied against X2Go Client (in  
jessie/stretch/buster/unstable):

https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ce559d1

light+love
Mike

--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgp4cij6k0Aq1.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: x2goclient
Source-Version: 4.1.2.1-4

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated x2goclient package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 21 Dec 2019 17:56:23 +0100
Source: x2goclient
Architecture: source
Version: 4.1.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 947129
Changes:
 x2goclient (4.1.2.1-4) unstable; urgency=medium
 .
   * debian/patches:
 + Add libssh-regression-fix-CVE-2019-14889.patch. In src/sshprocess.cpp:
   strip ~/, ~user{,/}, ${HOME}{,/} and $HOME{,/} from destination paths
   in scp mode. Fixes: #1428. This was already necessary for pascp (PuTTY-
   based Windows solution for Kerberos support), but newer libssh versions
   with the CVE-2019-14889 also interpret paths as literal strings.
   (Closes: #947129).
Checksums-Sha1:
 e5a05985b48ac351cbea110711a29fb621a66ef6 2489 x2goclient_4.1.2.1-4.dsc
 dbc1e27d7d30127ff176b911193c6a6f2e13c95c 24068 
x2goclient_4.1.2.1-4.debian.tar.xz
 c7bad695f3d3499f83beafed23fdf135f5a04c87 13021 
x2goclient_4.1.2.1-4_source.buildinfo
Checksums-Sha256:
 21f9d6a71ba016003a6161aa8df366c25e2945f5a80f395df49bbfe210770fda 2489 
x2goclient_4.1.2.1-4.dsc
 986ada1ef922176baaff8bbde2e264e24153ce9fac962daa3d88694b99c73280 24068 
x2goclient_4.1.2.1-4.debian.tar.xz
 f8a0d0140c1ff0ac4245afa6597cc3e292a585fa8531bc01ceff50ac682b226a 13021 
x2goclient_4.1.2.1-4_source.buildinfo
Files:
 ab88fa360d9297e67679e76c4834a5fc 2489 x11 optional x2goclient_4.1.2.1-4.dsc
 bee88899ce4b13b1022ee44dc1bac673 24068 x11 optional 
x2goclient_4.1.2.1-4.debian.tar.xz
 300fa8976876634b8de6d96eb2b817eb 13021 x11 optional 
x2goclient_4.1.2.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3+VE4VHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx3dMP/iCSggpg5jtShOGo0VPNvu67cz1j
e0M0UO9uMjcu95hTeCySITbHKblQKB/VPgD910rW9dD9igGf/enM3Qg2ue0iY7Dt
d2ERKCZEZRum98+O9S1aMwQZypZEAxpGIe4xC5gItYqclBPnqTg9UadXP35DBmNf
3p4cUCwfAmFdi0Pz7m6NmDZ3H/1PoOH303d2+IdfndD6iZe+if45nEJfCganC5Fd
FFrUr+Bt1URGaN1/Gy8bMiRTfP+NXamyL7Yc2KCfxBAaARIZWrjO2yHff6OY2oPM
etnoJOUmFP6vtbiLhcconfXe+kYpOL0smlQp0CeK3PAGQkkqizKqk1i3FDU/PvCD
2pIUJvhV7Rhnbr2bG66VfT3mr3ekcoJynXOlLGEFqKsHtIu3xoOBWHbLoy8ouSwc
WK9A+eyBwKa2A4BF9f9W82ymZrHYP2BbA2nbpDhjEjIpjFR8a0tFEMCByIeXgGzo
2QNbG1crA7BwISbWR1cF/NmYxbNb0OpZYGuR6rFnxLARmEwfO+19AaFj385z05yJ
OAFHsqXBkUqm9Xwp8jfLsenOj1xK5vefiO1XC6JDwgi4vFf7X8TM6HXyBbPORiPT
79WRbvPV3mwzv+ifiVV3w6rwkwbowr2zvagEWXWYSQZ1RzaBD9wTDwJwt5Y1Mttr
Pm/Y+/yzQLtZ7KAb
=ovSJ
-END PGP SIGNATURE End Message ---

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

Hi Chen-Tse,

thanks for you quick response.

On Sat, Dec 21, 2019 at 09:48:14AM -0500, Chen-Tse Tsai wrote:
> Hi, Andreas,
> 
> I agree with your suggestions. Thanks for putting it on salsa!

Thanks for confirming.
 
> Should I investigate dropping python2? I can spend some time this week on
> this. But I may need help with debian stuff.

What exact help do you need?  Do you have a login on Salsa?  We could
add you to science-team to grant you commit permissions.  I admit I have
not yet looked into the packaging - just realised that its cdbs which is
unfortunate since it would not eliminate the Python2 dependency fully.

Kind regards

  Andreas. 
 
> On Sat, Dec 21, 2019 at 7:39 AM Andreas Tille  wrote:
> 
> > On Sat, Dec 21, 2019 at 08:28:57AM +, Mo Zhou wrote:
> > > I second this proposal, and the same for src:liblinear.
> >
> > That's done as I wrote.
> >
> > > These are high popcon packages, dependencies for a number of other
> > > packages. They should be team maintained to unblock important fixes.
> >
> > To push a bit I just commited
> >
> >https://salsa.debian.org/science-team/libsvm
> >
> > Last maintainer upload was more than 3 years ago, 2 NMUs inbetween,
> > package is lagging behind upstream.  Anybody is kindly invited to adapt
> > the packaging (I think we should really get rid of cdbs since this in
> > turn is Python2) and proceed from here.
> >
> > Kind regards
> >
> >  Andreas.
> >
> >
> > > On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> > > > Hi Chen-Tse,
> > > >
> > > > I'm maintaining a package that depends from libsvm.  Due to bug #936924
> > > > that did not received any response since August it is in danger to be
> > > > removed from testing so I'm interested that this bug will be fixed.
> > > > When looking at the package I realised that while it would fit into
> > > > Debian Science team scope it is not team maintained nor is there any
> > > > repository in Salsa.  That's why I have the following suggestion:
> > > >
> > > >   1. I create a repository on Salsa
> > > >   2. Move the package to Debian Science team maintenance
> > > >  and add you as Uploader
> > > >   3. Drop Python2 package and close bug #936924
> > > >   4. May be migrate packaging from cdbs to dh
> > > >
> > > > If I do not hear from you until Monday I assume you agree with this
> > > > plan and will do so.
> > > >
> > > > Kind regards
> > > >
> > > >  Andreas.
> > > >
> > > > PS: @Christian: I noticed that you and Chen-Tse are maintaining
> > > > liblinear.  I have just removed Python2 package and reassigned
> > > > #936889 to ftp.debian.org to make sure python-liblinear will be
> > > > removed.  Thus libsvm can be dealt as suggested.
> > > >
> > > > --
> > > > http://fam-tille.de
> > > >
> > >
> > >
> >
> > --
> > http://fam-tille.de
> >

-- 
http://fam-tille.de

Bug#936932: libvigraimpex: Python2 removal in sid/bullseye

[Andreas Metzler]

On 2019-12-21 Andreas Metzler  wrote:
> On 2019-12-21 Andreas Metzler  wrote:
> > On 2019-10-01 Andreas Tille  wrote:
> > > Control: tags -1 help

> > > Hi,

> > > I tried hard to port libvigraimpex to Python3 in Git[1] and think I
> > > managed.

> > Hello Andreas,

> > I did not get far trying to build what is currently on salsa:
> [...]

> I have now made progress to a successful build. Will post a patch series
> or merge request today or tomorrow.

See https://salsa.debian.org/science-team/libvigraimpex/merge_requests/1

cu Andreas

Bug#945035: marked as done (gnat-gps: Please build-depend on python-gi in addition to python-gi-dev)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 18:05:52 +0100
with message-id <20191221170552.GA23100@nicolasthinkpad>
and subject line Re: gnat-gps: Please build-depend on python-gi in addition to 
python-gi-dev
has caused the Debian Bug report #945035,
regarding gnat-gps: Please build-depend on python-gi in addition to 
python-gi-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.)


-- 
945035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnat-gps
Version: 18-5
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: python-gi-dev-945022
Control: block 945022 by -1

Please see https://salsa.debian.org/gnome-team/pygobject/merge_requests/2
for the latest information on this transition.

python-gi-dev contains development files (pkg-config metadata and header
file) corresponding to both python-gi and python3-gi.

At the moment, python-gi-dev Depends on both python-gi and python3-gi.
The GNOME team would like to drop the python-gi dependency, to make the
status of Python 2 removal easier to track. A version with this change
might become available in experimental soon.

The package receiving this bug is one of a few packages that build-depend
on python-gi-dev and appear to build Python 2 bindings. If our analysis is
correct, these packages will need to add a build-dependency on python-gi
in future.

If your package requires a Python 2 version of the gi module at build time
(which it appears it does), please add python-gi to its Build-Depends.
If it also requires a Python 3 version of the gi module, it is probably a
good idea to add an explicit Build-Depends on python3-gi as well - this
will ensure that it doesn't need changes if python-gi-dev subsequently
also drops its python3-gi dependency, similar to python-dbus-dev.

If your package does not require a Python 2 version of the gi module at
build time, you can just close this bug.

This bug's severity will be increased to serious if it is still open
when python-gi-dev's dependency on python-gi is removed in unstable.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Gnat-gps Build-Depends: python-gi-dev because of the C header, but
does not need python-gi at build time.  It won't be affected if
python-gi-dev stops depending on python-gi.--- End Message ---

Processed: x2goclient: regression caused by CVE-2019-14889/libssh fix

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.0.3.1-4
Bug #947129 [x2goclient] x2goclient: regression caused by CVE-2019-14889/libssh 
fix
Marked as found in versions x2goclient/4.0.3.1-4.
> found -1 4.0.5.2-2
Bug #947129 [x2goclient] x2goclient: regression caused by CVE-2019-14889/libssh 
fix
Marked as found in versions x2goclient/4.0.5.2-2.

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

Bug#947129: x2goclient: regression caused by CVE-2019-14889/libssh fix

[Mike Gabriel]

Package: x2goclient
Version: 4.1.2.1-3
Severity: serious
Control: found -1 4.0.3.1-4
Control: found -1 4.0.5.2-2

the recent libssh fix for CVE-2019-14889 causes a regresion in X2Go Client:

```
Connection failed. Couldn't create remote file  
~/.x2go/ssh/key.X18947 - SCP: Warning: status code 1 received:  
scp: ~/.x2go/ssh: No such file or directory"

```

The solution to this is a fix to be applied against X2Go Client (in  
jessie/stretch/buster/unstable):

https://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=ce559d1

light+love
Mike

--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpIsXn2YRcPP.pgp
Description: Digitale PGP-Signatur

Bug#947117: marked as done (doxygen: Build error: "Qt5::Gui" references the file "/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:49:12 +
with message-id 
and subject line Bug#947117: fixed in qtbase-opensource-src 5.12.5+dfsg-3
has caused the Debian Bug report #947117,
regarding doxygen: Build error: "Qt5::Gui" references the file 
"/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.
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.)


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

Hello,

doxygen does not build anymore on sid/amd64:

-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Using Qt5
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 
(message):
  The imported target "Qt5::Gui" references the file

 "/usr/lib/x86_64-linux-gnu/libEGL.so"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:63 
(_qt5_Gui_check_file_exists)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:85 
(_qt5gui_find_extra_libs)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:186 (include)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:101 
(find_package)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake:28 (find_package)
  addon/doxywizard/CMakeLists.txt:6 (find_package)

-- Configuring incomplete, errors occurred!

Cc-ing qtbase5-dev maintainers.

cu Andreas
--- End Message ---
--- Begin Message ---
Source: qtbase-opensource-src
Source-Version: 5.12.5+dfsg-3

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated qtbase-opensource-src 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Dec 2019 14:30:03 +0300
Source: qtbase-opensource-src
Architecture: source
Version: 5.12.5+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 939653 947117
Changes:
 qtbase-opensource-src (5.12.5+dfsg-3) unstable; urgency=medium
 .
   * Backport upstream patch to fix uic handling of .ui files with global
 includes. Thanks to Alexander Volkov for the pointer!
   * Stop depending on libgl1-mesa-dev and libgles2-mesa-dev, which are
 transitional packages in mesa ≥ 19.3.0~rc6-1.
   * Also make qtbase5-dev explicitly depend on libegl-dev (closes: #947117).
   * Move the compatibility symlinks from qtbase5-dev-tools to qtbase5-dev
 (closes: #939653).
Checksums-Sha1:
 4255d502465681ad3bf7e606d04d354a3b9e31fb 5319 
qtbase-opensource-src_5.12.5+dfsg-3.dsc
 57de5700bc1173fbdea2ebcadd595e3daf497df3 252384 
qtbase-opensource-src_5.12.5+dfsg-3.debian.tar.xz
 a601849e15e0010da0a03808ea3ef1e1b99e7b48 18004 
qtbase-opensource-src_5.12.5+dfsg-3_source.buildinfo
Checksums-Sha256:
 4144f6968617f071a1762114d095c3b223c18d1f94d167e4aed28958227cfc1c 5319 
qtbase-opensource-src_5.12.5+dfsg-3.dsc
 e984869f5cc41603519f5491abcc26f8164091956e11715994651d8e3620d504 252384 
qtbase-opensource-src_5.12.5+dfsg-3.debian.tar.xz
 589a119e732ef6b26bb087308f01b2f053a3a70690d993c3e16203ba66a6723f 18004 
qtbase-opensource-src_5.12.5+dfsg-3_source.buildinfo
Files:
 ce07b1c5b79c07d079d665d43aa988cf 5319 libs optional 
qtbase-opensource-src_5.12.5+dfsg-3.dsc
 c8d43e0174329d559fd4b0a6d92cc670 252384 libs optional 
qtbase-opensource-src_5.12.5+dfsg-3.debian.tar.xz
 a6049ab78f49220dc2337578c120fd80 18004 libs optional 

Bug#937527: marked as done (pyroma: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:47:46 +
with message-id 
and subject line Bug#937527: fixed in pyroma 2.6b2-1
has caused the Debian Bug report #937527,
regarding pyroma: 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.)


-- 
937527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyroma
Version: 2.3.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:pyroma

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 ---
Source: pyroma
Source-Version: 2.6b2-1

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated pyroma package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Dec 2019 10:25:15 +
Source: pyroma
Architecture: source
Version: 2.6b2-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Closes: 937527
Changes:
 pyroma (2.6b2-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Federico Ceratto ]
   * New upstream release
   * Drop Python 2 package (Closes: #937527)
Checksums-Sha1:
 295dff461aea1c71fe9b844dce9830dc7c2265b6 1921 pyroma_2.6b2-1.dsc
 b25a8cb3a9d8f9703aecfda67cf88bed4ea06f11 349252 pyroma_2.6b2.orig.tar.gz
 d9f3a178bbce621864533b81d8e5ef3c5ebd8000 2884 pyroma_2.6b2-1.debian.tar.xz
 320c5abd419c3d0347c58b2fbd8869f8845e3549 6233 pyroma_2.6b2-1_amd64.buildinfo
Checksums-Sha256:
 b868b37c208894e3652139fe287738c1d09055bd807b1c940f82f70f53b3479c 1921 
pyroma_2.6b2-1.dsc
 10b3851febfdde157e6155dbf2719f6ef656abb3d8b4075b3e4e6405ca79ac0c 349252 

Bug#947118: marked as done (node-on-headers: autopkgtest started failing and then times out)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:43:53 +
with message-id 
and subject line Bug#947118: fixed in node-on-headers 1.0.2-1
has caused the Debian Bug report #947118,
regarding node-on-headers: autopkgtest started failing and then times out
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.)


-- 
947118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947118
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-on-headers
Version: 1.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout regression

Dear maintainers,

Your package has an autopkgtest, great. However, I noticed that without
any change from your side it started failing, and while doing so also
doesn't finish, hence timing out on ci.debian.net. Obviously this isn't
your fault, but please investigate, such that you can assign this bug to
the right package. Please consider improving the test suite to not hang
in case of failure. This is not the only node package that has this,
e.g. check https://ci.debian.net/status/slow/ to see more. Don't
hesitate to ask for help from the Debian CI team (in X-Debbugs-CC) if
you need help solving this issue.

To avoid wasting lots of time on the ci.debian.net infrastructure, I
consider adding your package to the blacklist. If that happens, please
ping me to try any uploads you make that should fix the issue if you are
unsure and don't want to close this bug until verified.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-on-headers/3635022/log.gz

autopkgtest [01:16:29]: test testsuite: [---


  onHeaders(res, listener)
✓ should fire after setHeader
✓ should fire before write
✓ should fire with no headers
✓ should fire only once
✓ should fire in reverse order
arguments
  res
✓ should be required
  listener
1) should be required
2) should only accept function
setHeader
  ✓ should be available in listener
writeHead(status)
  ✓ should make status available in listener
  ✓ should allow manipulation of status in listener
  3) should pass-through core error
writeHead(status, reason)
  ✓ should be available in listener
writeHead(status, reason, obj)
  ✓ should be available in listener
writeHead(status, obj)
  ✓ should be available in listener
  ✓ should handle falsy keys
writeHead(status, arr)
  ✓ should be available in listener


  14 passing (76ms)
  3 failing

  1) onHeaders(res, listener)
   arguments
 listener
   should be required:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)

  2) onHeaders(res, listener)
   arguments
 listener
   should only accept function:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)

  3) onHeaders(res, listener)
   writeHead(status)
 should pass-through core error:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-on-headers
Source-Version: 1.0.2-1

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-on-headers package)

(This message was generated automatically at their request; if you
believe that 

Bug#943050: marked as done (greylistd: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:39:31 +
with message-id 
and subject line Bug#943050: fixed in greylistd 0.8.8.8
has caused the Debian Bug report #943050,
regarding greylistd: 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.)


-- 
943050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: greylistd
Version: 0.8.8.7
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_take2.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: greylistd
Source-Version: 0.8.8.8

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated greylistd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Dec 2019 15:30:00 +0100
Source: greylistd
Architecture: source
Version: 0.8.8.8
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Closes: 943050
Changes:
 greylistd (0.8.8.8) unstable; urgency=medium
 .
   * apply patch for python3 (Closes: #943050)
 thanks a lot to Stephan Helma for the patch
   * debian/control: bump standard to 4.4.1 (no changes)
   * debian/control: use dh12
   * debian/control: only use python3 in dependencies
Checksums-Sha1:
 9b346ad0c853fd28573cbab6bf1d1763369e18ef 1591 greylistd_0.8.8.8.dsc
 c1cc2473ad5ab88cde0ed5fac9ea48a2e6a76d24 50660 greylistd_0.8.8.8.tar.xz
 a004287a43e995037a54dce05dad9549a7337b37 6105 greylistd_0.8.8.8_amd64.buildinfo
Checksums-Sha256:
 f4ee416b6b122ce510b771087231472c3501fc44c571bb9a4ea0493631b74f22 1591 
greylistd_0.8.8.8.dsc
 e4eb261c2dc2ddf104022d435e7ea675453804da5313d2d52c1863bbc3fc9ea4 50660 
greylistd_0.8.8.8.tar.xz
 842269064e66130d59135377867ed83ae0f0326b7bdb6d145a555c2df6583070 6105 
greylistd_0.8.8.8_amd64.buildinfo
Files:
 d5a258401fdeba5ce462e685e685a6de 1591 mail optional 

Bug#930764: marked as done (Fails to configure package due to "unknown type of DB: BACKUP" on upgrade-db)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:39:07 +
with message-id 
and subject line Bug#930764: fixed in cyrus-imapd 3.0.13-2
has caused the Debian Bug report #930764,
regarding Fails to configure package due to "unknown type of DB: BACKUP" on 
upgrade-db
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.)


-- 
930764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-common
Version: 3.0.8-6
Severity: important

Dear Maintainer,

I'm getting this error after upgrading to 3.0.8-6

  $ dpkg --configure --pending
  Setting up cyrus-common (3.0.8-6) ...
  Creating/updating cyrus user account...
  The user `cyrus' is already a member of `sasl'.
  /usr/lib/cyrus/bin/upgrade-db: Unknown type of DB: BACKUP
  dpkg: error processing package cyrus-common (--configure):
   installed cyrus-common package post-installation script subprocess returned 
error exit status 1

I previously had 3.0.8-5 installed. There are 2 files that the upgrade-db
script looks at. They look like this:

  /usr/lib/cyrus/cyrus-db-types.txt:

ANNOTATION twoskip
BACKUP twoskip
CONVERSATIONS skiplist
DBENGINE BerkeleyDB5.3
DUPLICATE twoskip
MBOX twoskip
PTS twoskip
QUOTA quotalegacy
SEARCH_INDEXED twoskip
SEEN twoskip
SORTCACHE twoskip
STATUSCACHE twoskip
SUBS flat
TLS twoskip
USERDENY flat
ZONEINFO twoskip

  /usr/lib/cyrus/cyrus-db-types.active:

ANNOTATION twoskip
BACKUP twoskip
CONVERSATIONS skiplist
DBENGINE BerkeleyDB5.3
DUPLICATE twoskip
MBOX twoskip
PTS twoskip
QUOTA quotalegacy
SEARCH_INDEXED twoskip
SEEN twoskip
SORTCACHE twoskip
STATUSCACHE twoskip
SUBS flat
TLS twoskip
USERDENY flat
ZONEINFO twoskip

It looks like "BACKUP" is missing from the case statement which is causing
the error I'm seeing. Additionally, it looks like "CONVERSATIONS",
"SEARCH_INDEXED", and "SORTCACHE" are also missing.

Thanks,
  David


-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages cyrus-common depends on:
ii  adduser  3.118
ii  db-upgrade-util  5.3.1+nmu1
ii  db-util  5.3.1+nmu1
ii  debconf [debconf-2.0]1.5.71
ii  dpkg 1.19.7
ii  e2fsprogs1.44.5-1
ii  gawk 1:4.2.1+dfsg-1
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libclamav9   0.101.2+dfsg-1
ii  libcom-err2  1.44.5-1
ii  libgcc1  1:8.3.0-2
ii  libgssapi-krb5-2 1.17-2
ii  libical3 3.0.4-3
ii  libicu63 63.1-6
ii  libjansson4  2.12-1
ii  libk5crypto3 1.17-2
ii  libkrb5-31.17-2
ii  libkrb5support0  1.17-2
ii  libldap-2.4-22.4.47+dfsg-3
ii  libpcre3 2:8.39-12
ii  libsasl2-2   2.1.27+dfsg-1
ii  libsasl2-modules 2.1.27+dfsg-1
ii  libsnmp305.7.3+dfsg-5
ii  libsqlite3-0 3.27.2-3
ii  libssl1.11.1.1c-1
ii  libstdc++6   8.3.0-2
ii  libwrap0 7.6.q-28
ii  libxapian30  1.4.11-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libzephyr4   3.1.2-1+b3
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  perl 5.28.1-6
ii  sendmail-bin [mail-transport-agent]  8.15.2-12
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages cyrus-common recommends:
iu  cyrus-admin  3.0.8-6
iu  cyrus-imapd  3.0.8-6

Versions of packages cyrus-common suggests:
ii  apt-listchanges3.19
iu  cyrus-admin3.0.8-6
pn  cyrus-caldav   
iu  cyrus-clients  3.0.8-6
ii  cyrus-doc  3.0.8-6
iu 

Bug#945884: marked as done (aptly, build-depends on package that is no longer in testing.)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:38:08 +
with message-id 
and subject line Bug#945884: fixed in aptly 1.3.0+ds1-3
has caused the Debian Bug report #945884,
regarding aptly, build-depends on package that is no longer in testing.
to be marked as done.

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

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


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

Package: aptly
Version: 1.3.0+ds1-2.3
Severity: serious

aptly build-depends on golang-go.tools which has been dropped by the 
golang-golang-x-tools source package. It is still present in unstable as a 
cruft package but is completely gone from testing.

Please update your build-dependency to golang-golang-x-tools-dev
--- End Message ---
--- Begin Message ---
Source: aptly
Source-Version: 1.3.0+ds1-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 21 Dec 2019 10:29:09 +0100
Source: aptly
Architecture: source
Version: 1.3.0+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Closes: 945884
Changes:
 aptly (1.3.0+ds1-3) unstable; urgency=medium
 .
   * Build-Depend on golang-golang-x-tools-dev instead of golang-go.tools 
(Closes: #945884)
   * Lintian fix
Checksums-Sha1:
 e56c6a4c021d285ac46df0d2f3be65ab9cafaceb 2470 aptly_1.3.0+ds1-3.dsc
 efdd95848a7a199fb774d626021b9f50482b791a 8108 aptly_1.3.0+ds1-3.debian.tar.xz
 6e27c05bd24decb3e4ef5340843cdf2727cc8f75 9161 aptly_1.3.0+ds1-3_amd64.buildinfo
Checksums-Sha256:
 593dd8f0d99f36926800c0268c30694adf02af321422960bf57b3e3c73aedb27 2470 
aptly_1.3.0+ds1-3.dsc
 911ebdce131d2e669ae1217125d7726cd40b4e7e8339d665f3fa8d02a519c835 8108 
aptly_1.3.0+ds1-3.debian.tar.xz
 ffdb4eb1771297d3a6ce3499c2a90626fe0a6300ccf3643be20daa1d35159ad7 9161 
aptly_1.3.0+ds1-3_amd64.buildinfo
Files:
 1fd4b1e959b21debc3cdd187cde62016 2470 utils optional aptly_1.3.0+ds1-3.dsc
 6addaa17c7a90e26c31923c0e7cc8321 8108 utils optional 
aptly_1.3.0+ds1-3.debian.tar.xz
 db9c1ecb63b9fbd253c9794c472362f3 9161 utils optional 
aptly_1.3.0+ds1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAl3+FH8ACgkQEL6Jg/PV
nWREvwf+Og7LKi6EpkgNZ9aDXFEj5qqAQnHz9hhDkr36YCUbA4JYhi0uHm1KAsOQ
Byn+PYBGTxbXAIDK2iIj2GsAPbOqM7nQmJw4o3Gi26peyqm2cf99v0aYHRrBvc9U
CnuOiV60PuJb32ayBZmCuXfGSo05x/ovN7XFlObsY7qBrx5LdvKsGC7BEeK+fqPW
Z3kNEwxi4RYswHLtZsUbUp/XW6l+U5OUPBpE/+ULuNf7h5wp1e68Zic1f+6lRYzB
uNlPUy/5DPiUXNx1rTlMBuMr0bQ/WsGGjpHYbWOVF+iDf02ANM9TFRTYj9sk0i7C
rV7ExoyIGNQ0lZQVLLuMonbBQGnLeQ==
=wEZX
-END PGP SIGNATURE End Message ---

Bug#946797: marked as done (debian-edu-config: kadm5.acl should set proper rights for users)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:32:44 +
with message-id 
and subject line Bug#946797: fixed in debian-edu-config 2.10.65+deb10u3
has caused the Debian Bug report #946797,
regarding debian-edu-config: kadm5.acl should set proper rights for users
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.)


-- 
946797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 1.812+deb8u1
Severity: important

To improve security, settings in kadm5.acl should be adjusted.

The needed fix is minimal:

--- a/share/debian-edu-config/tools/kerberos-kdc-init
+++ b/share/debian-edu-config/tools/kerberos-kdc-init
@@ -187,7 +187,7 @@ EOF
 if [ ! -f /etc/krb5kdc/kadm5.acl ] ; then
cat > /etc/krb5kdc/kadm5.acl <

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 2.10.65+deb10u3

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, 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.
Dominik George  (supplier of updated debian-edu-config 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 16 Dec 2019 16:29:19 +0100
Source: debian-edu-config
Architecture: source
Version: 2.10.65+deb10u3
Distribution: buster-security
Urgency: high
Maintainer: Debian Edu Developers 
Changed-By: Dominik George 
Closes: 946797
Changes:
 debian-edu-config (2.10.65+deb10u3) buster-security; urgency=high
 .
   * Security fix for CVE-2019-3467
 .
   [ Wolfgang Schweer ]
   * share/debian-edu-config/tools/kerberos-kdc-init:
 - Set proper rights for users in kadm5.acl file. (Closes: #946797)
   * Adjust debian/debian-edu-config.postinst to fix kadm5.acl upon upgrades.
 .
   [ Holger Levsen ]
   * Improve debian/debian-edu-config.postinst fix to only run once on
 upgrades.
 .
   [ Dominik George ]
   * Add NEWS to warn administrators with possible local changes.
Checksums-Sha1:
 c8d1697ca57aa596b5a9be450c5bb01621c6417a 2019 
debian-edu-config_2.10.65+deb10u3.dsc
 fdc366af82ac76bc960faa079885297b52f9d891 345320 
debian-edu-config_2.10.65+deb10u3.tar.xz
 bbba6e68d16e31013ccd37a7faa1c2efe12e11b1 5824 
debian-edu-config_2.10.65+deb10u3_amd64.buildinfo
Checksums-Sha256:
 9993c2b690261ef72409bee9674ec187ad58f41583a0b0a256aa5cc64e8aaf86 2019 
debian-edu-config_2.10.65+deb10u3.dsc
 aaf5a4130d2a032d5e56eac5aa63629d5f9ed08366e6df4f0f95eb8e923aa4ed 345320 
debian-edu-config_2.10.65+deb10u3.tar.xz
 311b91ce88fd4a26b45f9bb7752257a0de26e03c582c5088039374c867605ec4 5824 
debian-edu-config_2.10.65+deb10u3_amd64.buildinfo
Files:
 0bbc77ad3bfa657431b7216d4c2996cd 2019 misc optional 
debian-edu-config_2.10.65+deb10u3.dsc
 d38c7dd2f8ee6f4804f5e177bcbb74cd 345320 misc optional 
debian-edu-config_2.10.65+deb10u3.tar.xz
 da0f8ddd45485c45f287201756165264 5824 misc optional 
debian-edu-config_2.10.65+deb10u3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl35Dx8xGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTylim4D/9Nt1XbDfCh3QLu4IFHH87WKqmeJvR/zPWf7Qz3u4jV26TC7KwPwPSA
/EInc9VGafb0qPjCv80iVqygLHp5YVKC1K2h4Q7xxNUJz/WktyGM52IJJY83PrfK
PWNPCNrJ8WFDR8o2OJhNbchAX8nGvbw/mD7n2Vf4jcTEQrZE8o7ZLeGo2iluPXMf
BxPsQtna2tFF0pYgqcNe28hzWqDQurfwKYMRANxWNKbfetqDXgnKqJ6QBokKDGoS
VwSMepogM4RqQxPcH1E9/lXPzKYZY1EXqFR+lOWPF9X4LC38oTHQvgwVIAz3Vt93
b0ABi4IwxFKdYWcN/9oaWAyEr0rE3e6Ckpo/dAGBnCXti/homGT/+/XdBS85Vi37
3u5TDqRd3RJmkIQjFvo6bzE5XdNR+CVnh5+ioNsSKmaxsSKBjVAkqCDfowmWZL1B
FNKmRpX99cUdsJhGJ2ASyEl148pRxwU9tR8nVU72rx9L1oq3gWGsptYsPoi8LTwM
aS+v1qz3eYOrrkpqKv2YL3oSIVnUlxHZnnSzDbj5b7nQjqGnBh2SryXgnlxWfPGw
fmlZB8LxtoFxTejb45yz45ciyRNBYeYJX2CHsCx0Vfql/ZMVL9aXfyYgwuCpusuG
2DagMRMNBGV7a/lLVULqoQyyukUfiGNxPTUuM5M3uqPBtox2EQUNww==
=/iWq
-END PGP SIGNATURE End Message ---

Bug#947043: marked as done (cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:33:40 +
with message-id 
and subject line Bug#947043: fixed in cyrus-sasl2 
2.1.27~101-g0780600+dfsg-3+deb9u1
has caused the Debian Bug report #947043,
regarding cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function
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.)


-- 
947043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.27+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/cyrusimap/cyrus-sasl/issues/587
Control: found -1 2.1.27~101-g0780600+dfsg-3

Hi,

The following vulnerability was published for cyrus-sasl2.

CVE-2019-19906[0]:
Off by one in _sasl_add_string function

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19906
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906
[1] https://github.com/cyrusimap/cyrus-sasl/issues/587

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: cyrus-sasl2
Source-Version: 2.1.27~101-g0780600+dfsg-3+deb9u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated cyrus-sasl2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Dec 2019 23:13:43 +0100
Source: cyrus-sasl2
Architecture: source
Version: 2.1.27~101-g0780600+dfsg-3+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Cyrus SASL Team 

Changed-By: Salvatore Bonaccorso 
Closes: 947043
Changes:
 cyrus-sasl2 (2.1.27~101-g0780600+dfsg-3+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Off-by-one in _sasl_add_string function (CVE-2019-19906) (Closes: #947043)
Checksums-Sha1: 
 dc9b60273777b625263abd376136cf5c2b19cc84 3381 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.dsc
 627ff1c0d62984d60f7f98d6b14f6c36d6a9b0d9 1143888 
cyrus-sasl2_2.1.27~101-g0780600+dfsg.orig.tar.xz
 d48a36988dc3604eeb198ea7b554e342cb9bfde6 94992 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.debian.tar.xz
Checksums-Sha256: 
 a331441098ece65be5bf13d871b486115af68daf06a0145adf6cda8ef71d73e4 3381 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.dsc
 69f34971f768e7ee6a6b647ec2d16a5a72a854ecd4602b019d5f79ba61063fdc 1143888 
cyrus-sasl2_2.1.27~101-g0780600+dfsg.orig.tar.xz
 be1ba4b3bfcc4740354342686deac73ca2e46c4871219599229efe8cfe98df6f 94992 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.debian.tar.xz
Files: 
 71db97fd10e2727beddc112439fbe256 3381 libs standard 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.dsc
 4ca5bf3e08c62df06c3a5ffadcd9ab13 1143888 libs standard 
cyrus-sasl2_2.1.27~101-g0780600+dfsg.orig.tar.xz
 e88a9640371f49af4f8e95a42ba9ed21 94992 libs standard 
cyrus-sasl2_2.1.27~101-g0780600+dfsg-3+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl3792RfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E7BsP/08u143qVzZdjR/Gs9AjgRd5W2CAWMyL
WMvJb9ITtiHtDHXEgJ6N0XdjqRhGCUHWWVrJ+c5pTl1Y5HukXeEVZgGB3zO8MwMz
xW5UNL09mZcQ6fhXgHB7DSarrG9mupgHDBnmojzIz84VQDyECS9CGy3g8KPraqpv
/o70Xm2opBpt/2v6jJy+cGe5HMw2dVuSGiwKOrhQ7qSkfYLjON7CwDVNXTcqD3JS
xg6fkmGsxktdPV88at1INOF9Xb+kOklrRj1HqVEo+NmvwqR/wg64xj4StHGchNjX
C+vDDgbJhQ0M2YImFMsicbCKV7wxt2CY0gF/ruyc0mPR5EnUsAyuEICzIRNVePwb
616HIjnxQ3IBvrMhdZTwLP3X6yvxsgVKacXwROpgEuo3MuyolTWXT1Ds9b9o5oCA
mJOoghSkpQd+zUwLWqp37pKtIG5hVK2XfwDCN8Tw3OlZAKZRRErslp8mCgLdUS0P
wEFc+rwH3+NzKk67Q5HgymzmlACR//RM3cOu6wZQt6IyA86rn6WRatA8CJbQWl2H
Ljjz+borrD/hPFDdBRijq0k5q9RrQ2yrhi4z8iH99qGbNK7dMb5wXqoSwTvAD2iM
RrWamA4tHAZ+S+AfDN7jkdMYzKMgyPgFbST0vov8gRgrswHRTqIcOOyb5Q0xjJIc
Ao/Sm2HTJVdq
=pspV
-END PGP SIGNATURE End Message ---

Bug#946797: marked as done (debian-edu-config: kadm5.acl should set proper rights for users)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:33:58 +
with message-id 
and subject line Bug#946797: fixed in debian-edu-config 1.929+deb9u4
has caused the Debian Bug report #946797,
regarding debian-edu-config: kadm5.acl should set proper rights for users
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.)


-- 
946797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-config
Version: 1.812+deb8u1
Severity: important

To improve security, settings in kadm5.acl should be adjusted.

The needed fix is minimal:

--- a/share/debian-edu-config/tools/kerberos-kdc-init
+++ b/share/debian-edu-config/tools/kerberos-kdc-init
@@ -187,7 +187,7 @@ EOF
 if [ ! -f /etc/krb5kdc/kadm5.acl ] ; then
cat > /etc/krb5kdc/kadm5.acl <

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 1.929+deb9u4

We believe that the bug you reported is fixed in the latest version of
debian-edu-config, 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.
Dominik George  (supplier of updated debian-edu-config 
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: Tue, 17 Dec 2019 18:38:50 +0100
Source: debian-edu-config
Binary: debian-edu-config
Architecture: source
Version: 1.929+deb9u4
Distribution: stretch-security
Urgency: high
Maintainer: Debian Edu Developers 
Changed-By: Dominik George 
Description:
 debian-edu-config - Configuration files for Skolelinux systems
Closes: 946797
Changes:
 debian-edu-config (1.929+deb9u4) stretch-security; urgency=high
 .
   * Security fix for CVE-2019-3467
 .
   [ Wolfgang Schweer ]
   * share/debian-edu-config/tools/kerberos-kdc-init:
 - Set proper rights for users in kadm5.acl file. (Closes: #946797)
   * Adjust debian/debian-edu-config.postinst to fix kadm5.acl upon upgrades.
 .
   [ Holger Levsen ]
   * Improve debian/debian-edu-config.postinst fix to only run once on
 upgrades.
 .
   [ Dominik George ]
   * Add NEWS to warn administrators with possible local changes.
Checksums-Sha1:
 8b729d7257d08386744143610020e874232f61fa 1940 
debian-edu-config_1.929+deb9u4.dsc
 6bfe3fab7764f30a92e8f05dbc0f0baad0436fc1 386320 
debian-edu-config_1.929+deb9u4.tar.xz
 8f529c0c287558fb84711bc1bd4f7fa88fbcc43c 6090 
debian-edu-config_1.929+deb9u4_amd64.buildinfo
Checksums-Sha256:
 2ef1f0325d7d5fda92405fcb8d4fd27ca70d6fab87d4953dbbeaab1f35078a38 1940 
debian-edu-config_1.929+deb9u4.dsc
 a9b8d47a36c52d9ddd4b5196dd50ebc4ce10401271589756bc15f369c101a84d 386320 
debian-edu-config_1.929+deb9u4.tar.xz
 bb42c1eb191ad13315c3ee30da6d6f0e570cc4e5bff8f4860fde4b2d471603f1 6090 
debian-edu-config_1.929+deb9u4_amd64.buildinfo
Files:
 034169c8ac0215a3d1911f664835fc39 1940 misc extra 
debian-edu-config_1.929+deb9u4.dsc
 da4b1c3cc66f240fa0afe60168c636d7 386320 misc extra 
debian-edu-config_1.929+deb9u4.tar.xz
 1d6246d480b8641ddea6b6dd4faa666b 6090 misc extra 
debian-edu-config_1.929+deb9u4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJlBAEBCgBPFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAl3589cxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYwAKCRC3mjwW
oMTyliVqD/9gftFKEPsLrkqgnkie2d5y/J763Pajao2iHCQnWuvVPgOy3Jkj8Mlg
jTbkVpaqkM4lMR5+3xtNViKizsGdRbE3qae/Aij+iEkOQaS97fWjDKjPY9mwHnL9
nHBkEzl3V3aGuIU/eWidsHTQQSNyqulDLKFWAsKvDBJEknR2l/nyVcEdQZcZAP/t
LyXrbLY8gEO2hFYPVICLFwkjsty5Guk2LnKsRVbdLRPTQoU89kblhOBAy7Z9JmxB
8E9JzgXYtGjGDUkCGQQohya696ImDL/4vA+gkZZax4i6p46CeLWfPRPmhz755aUD
P1PMUVizggigHRtfCWtf1V1xOP5x1zXjIYOWT2XVH6gUiDdMvX05hiGmqq1FkIi7
8tq99IQ+PsJ3WxRA1oKMoWTkfPJBs4aFQtJ0rAfcxcFFESDVPl7tPW8lnz9M647n
h73ddyjuzfvRBS3DnPmfs/bKVA1QPK91QBRTlkVnViABLGeGV9DKA9GWyLd89oI8
9WGpXENUnNOY9ppIGjZlRZnkOmlbIVp0C4NwPhuNBtZNX9YtLtxl+86xShDDW06+
VpbaxLaFMDAEUfhW6Q6epfrNX7608oADR15pLBOoHUZcOJD7ycYvt3aCx2/IQElP
SKQ3UYUCmuWm+L02tKol7MJBI70B+88AxOyg+GOICEJnWrN8NceMXA==
=tMNo
-END PGP SIGNATURE End Message ---

Bug#947043: marked as done (cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 16:32:27 +
with message-id 
and subject line Bug#947043: fixed in cyrus-sasl2 2.1.27+dfsg-1+deb10u1
has caused the Debian Bug report #947043,
regarding cyrus-sasl2: CVE-2019-19906: Off-by-one in _sasl_add_string function
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.)


-- 
947043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-sasl2
Version: 2.1.27+dfsg-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/cyrusimap/cyrus-sasl/issues/587
Control: found -1 2.1.27~101-g0780600+dfsg-3

Hi,

The following vulnerability was published for cyrus-sasl2.

CVE-2019-19906[0]:
Off by one in _sasl_add_string function

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19906
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19906
[1] https://github.com/cyrusimap/cyrus-sasl/issues/587

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: cyrus-sasl2
Source-Version: 2.1.27+dfsg-1+deb10u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated cyrus-sasl2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Dec 2019 22:59:30 +0100
Source: cyrus-sasl2
Architecture: source
Version: 2.1.27+dfsg-1+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Cyrus Team 
Changed-By: Salvatore Bonaccorso 
Closes: 947043
Changes:
 cyrus-sasl2 (2.1.27+dfsg-1+deb10u1) buster-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Off-by-one in _sasl_add_string function (CVE-2019-19906) (Closes: #947043)
Checksums-Sha1: 
 c2af544a3fb6d6735dbf11958aaa772a07c8801b 3580 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.dsc
 6da3baff1685e96b93b46cdd47e13ecc34a632df 2058596 
cyrus-sasl2_2.1.27+dfsg.orig.tar.xz
 7535cdb01b04cfa4b2a5d9619aa2e837f0291dc9 99972 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.debian.tar.xz
Checksums-Sha256: 
 4537e3acdf1e009c402110aa47d6f5acef87594b4ad7e13733d3956d85b2d110 3580 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.dsc
 108b0c691c423837264f05abb559ea76c3dfdd91246555e8abe87c129a6e37cd 2058596 
cyrus-sasl2_2.1.27+dfsg.orig.tar.xz
 df71d3cd6c623702c5daeab440c91899c8d4e7955cf632e6bd07de3a65cb8538 99972 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.debian.tar.xz
Files: 
 5f4931df32fa8c405220d05c1f26925e 3580 libs standard 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.dsc
 ce30955361d1cdde3c31d0ee742e338d 2058596 libs standard 
cyrus-sasl2_2.1.27+dfsg.orig.tar.xz
 ba6707c9b3f82742a8b25d5d95fd6dd3 99972 libs standard 
cyrus-sasl2_2.1.27+dfsg-1+deb10u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl379AdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89En3AP/j/ZLqYssVCDeD358qGOdFwPB/m88w/E
Mwe1e3kwsXiItNuj7eZqiOVGdb4H2e102mH+h5NxBkruSGinBRSdcY2/4Cg39hKX
eXU8bH66O1HlLvsuvbP9PeMZ/3xQ7qktBLfIyAUQippTVcH2voqPj06kvInVsjOq
tTeVL12I2s70qUSgzI4C3ziSm4bx4qhRJ6YKoFjIflPXD3wSjItnFpSKTXVtQSvB
HNxT9dH55YdJz1U7KViMNvENjkf600izYi2QJLdVLfI+/YCyxDJRJj6JXzZbnCPD
Zfjeinxwztd+/U5lsT8/0JfEAEzGUXGaZvAKmYqIO3AKe+d2x0wpfOvgCoDGEgQV
mOUU2q6Iz6F9h0dll1nWXqFIcoXnYDO+LgHHVxskW2EJ5jTXfHaOu7bKG/rh18jf
dZZ+YYirfhA3YaCvp8URM1buvVL1klCD9hjO+ptScEhOi2EbN+6qVdYUPw9rj771
rrPxOFcx22NN+xjo2Hao8ennGtxKLmwjBTIGbYlNkHGUJ/0ai1t62HUUqLX2wRH5
EqpEtMxLqSgy1+fb0y/+qvnsJbiTJIa0ZriZh7O1igW473FHozT1oZjrJB9b+tQG
CLuELxucix+2s51y4D7aarqgEhpTNld5YnA0zaBd8iQgklZoLF59L5joFZDyiOdR
8qpQdx/5KtLO
=xA/a
-END PGP SIGNATURE End Message ---

Bug#936924: Moving libsvm to Debian Science team

[Chen-Tse Tsai]

Hi, Andreas,

I agree with your suggestions. Thanks for putting it on salsa!

Should I investigate dropping python2? I can spend some time this week on
this. But I may need help with debian stuff.

Thanks,
Chen-Tse


On Sat, Dec 21, 2019 at 7:39 AM Andreas Tille  wrote:

> On Sat, Dec 21, 2019 at 08:28:57AM +, Mo Zhou wrote:
> > I second this proposal, and the same for src:liblinear.
>
> That's done as I wrote.
>
> > These are high popcon packages, dependencies for a number of other
> > packages. They should be team maintained to unblock important fixes.
>
> To push a bit I just commited
>
>https://salsa.debian.org/science-team/libsvm
>
> Last maintainer upload was more than 3 years ago, 2 NMUs inbetween,
> package is lagging behind upstream.  Anybody is kindly invited to adapt
> the packaging (I think we should really get rid of cdbs since this in
> turn is Python2) and proceed from here.
>
> Kind regards
>
>  Andreas.
>
>
> > On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> > > Hi Chen-Tse,
> > >
> > > I'm maintaining a package that depends from libsvm.  Due to bug #936924
> > > that did not received any response since August it is in danger to be
> > > removed from testing so I'm interested that this bug will be fixed.
> > > When looking at the package I realised that while it would fit into
> > > Debian Science team scope it is not team maintained nor is there any
> > > repository in Salsa.  That's why I have the following suggestion:
> > >
> > >   1. I create a repository on Salsa
> > >   2. Move the package to Debian Science team maintenance
> > >  and add you as Uploader
> > >   3. Drop Python2 package and close bug #936924
> > >   4. May be migrate packaging from cdbs to dh
> > >
> > > If I do not hear from you until Monday I assume you agree with this
> > > plan and will do so.
> > >
> > > Kind regards
> > >
> > >  Andreas.
> > >
> > > PS: @Christian: I noticed that you and Chen-Tse are maintaining
> > > liblinear.  I have just removed Python2 package and reassigned
> > > #936889 to ftp.debian.org to make sure python-liblinear will be
> > > removed.  Thus libsvm can be dealt as suggested.
> > >
> > > --
> > > http://fam-tille.de
> > >
> >
> >
>
> --
> http://fam-tille.de
>

Bug#947081: fixed in fribidi 1.0.8-2

[gregor herrmann]

On Sat, 21 Dec 2019 02:35:48 +, أحمد المحمودي (Ahmed El-Mahmoudy) wrote:

>  fribidi (1.0.8-2) unstable; urgency=medium
>  .
>* Add  revert_log2vis_get_embedding_levels.diff patch to revert back
>  fribidi_log2vis_get_embedding_levels function.
>  It seems to be removed by mistake by upstream, since its documentation is
>  still there (Closes: #947081)
>* Revert last update to symbols file

Thanks for the quick fix!

I can confirm that libtext-bidi-perl indeed builds/tests/runs again
as expected.

pyfribidi still has an interesting failure in its autopkgtests but I
don't know if this is a problem of fribidi or pyfribidi:

https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pyfribidi/3712389/log.gz


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#945920: Chromium segfaults - backtraces

[Michel Meyers]

Thanks to Jaap Joris Vens for helping me figure out why my dumb ass 
couldn't find the debug package with apt-cache (they're in a separate 
repo now as the README points out).


I've discovered two interesting things, the first one is possibly 
unrelated:


1. I can reliably cause Chromium to SIGSEGV by opening the Task Manager 
(Ctrl+Esc). Here's a backtrace from such a crash:



Thread 1 "chromium" received signal SIGSEGV, Segmentation fault.
0x5a77cf87 in 
memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, 
base::OnceCallbackstd::unique_ptrstd::default_delete >)>) ()

(gdb) bt
#0  0x5a77cf87 in 
memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, 
base::OnceCallbackstd::unique_ptrstd::default_delete >)>) ()

#1  0x591baaa9 in task_manager::TaskManagerImpl::Refresh() ()
#2  0x593e7c76 in base::RepeatingTimer::RunUserTask() ()
#3  0x593b5165 in base::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) ()
#4  0x593c466b in 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, 
bool*) ()
#5  0x593c5fec in 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() 
()
#6  0x59376aca in base::(anonymous 
namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) ()
#7  0x77064f2e in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x770651c8 in  () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7706525c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x59376dd0 in 
base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#11 0x593c62a9 in 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, 
base::TimeDelta) ()

#12 0x593a22fa in base::RunLoop::Run() ()
#13 0x58ea8217 in 
ChromeBrowserMainParts::MainMessageLoopRun(int*) ()
#14 0x571cd1c6 in 
content::BrowserMainLoop::RunMainMessageLoopParts() ()

#15 0x571cd375 in content::BrowserMainRunnerImpl::Run() ()
#16 0x571a35f7 in 
content::BrowserMain(content::MainFunctionParams const&) ()
#17 0x58e30101 in 
content::RunBrowserProcessMain(content::MainFunctionParams const&, 
content::ContentMainDelegate*) ()
#18 0x58e30338 in 
content::ContentMainRunnerImpl::RunServiceManager(content::MainFunctionParams&, 
bool) ()

#19 0x58e306a7 in content::ContentMainRunnerImpl::Run(bool) ()
#20 0x58e66802 in 
service_manager::Main(service_manager::MainParams const&) ()
#21 0x58e2e0c6 in 
content::ContentMain(content::ContentMainParams const&) ()

#22 0x5635c3e5 in ChromeMain ()
#23 0x704a1bbb in __libc_start_main (main=
0x56339f80 , argc=1, argv=0x7fffe168, init=out>, fini=, rtld_fini=, 
stack_end=0x7fffe158)

at ../csu/libc-start.c:308
#24 0x5635c22a in _start ()
(gdb)


Might be an unrelated issue though.

2. While running in gbd and watching a YouTube video in full screen, I 
tried to pause it and couldn't (no cursor, YouTube UI not showing up), 
only to find it had segfaulted randomly. The video continued to play 
until I killed the process. This is that backtrace:



Thread 1 "chromium" received signal SIGSEGV, Segmentation fault.
0x5a77cee7 in 
memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, 
std::allocator, 
std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) ()

(gdb) bt
#0  0x5a77cee7 in 
memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, 
std::allocator, 
std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) ()
#1  0x58f8ddb0 in 
ProcessMemoryMetricsEmitter::FetchAndEmitProcessMemoryMetrics() ()
#2  0x58f85e82 in (anonymous namespace)::RecordMemoryMetrics() 
()
#3  0x593b5165 in base::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) ()
#4  0x593c466b in 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, 
bool*) ()
#5  0x593c5fec in 
base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() 
()
#6  0x59376aca in base::(anonymous 
namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) ()
#7  0x77064f2e in g_main_context_dispatch () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#8  0x770651c8 in  () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7706525c in g_main_context_iteration () at 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x59376dd0 in 
base::MessagePumpGlib::Run(base::MessagePump::Delegate*) ()
#11 0x593c62a9 in 

Processed: apache-log4j1.2: CVE-2019-17571

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.2.17-7
Bug #947124 [src:apache-log4j1.2] apache-log4j1.2: CVE-2019-17571
Marked as found in versions apache-log4j1.2/1.2.17-7.
> found -1 1.2.17-5
Bug #947124 [src:apache-log4j1.2] apache-log4j1.2: CVE-2019-17571
Marked as found in versions apache-log4j1.2/1.2.17-5.

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

Bug#947124: apache-log4j1.2: CVE-2019-17571

[Salvatore Bonaccorso]

Source: apache-log4j1.2
Version: 1.2.17-8
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 1.2.17-7
Control: found -1 1.2.17-5

Hi,

The following vulnerability was published for apache-log4j1.2.

CVE-2019-17571[0]:
| Included in Log4j 1.2 is a SocketServer class that is vulnerable to
| deserialization of untrusted data which can be exploited to remotely
| execute arbitrary code when combined with a deserialization gadget
| when listening to untrusted network traffic for log data. This affects
| Log4j versions up to 1.2 up to 1.2.17.

Note that this issue correponds to the old CVE-2017-5645 for the 2.x
branch codebasis[1].

1.2 reached end of life in 2015 accordingly, and the "right move"
would be to switch to 2.x. Which raises a question from security
support point of view: We would need to fade out apache-log4j1.2 for
bullseye at least now right? From a quick check via a simulated dak
rm, it looks right now impossible to actually remove it. Are there
current plans from the Debian Java Maintainers for that? Or is there
something I currently just miss from the big picture?

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-17571
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
[1] https://www.openwall.com/lists/oss-security/2019/12/19/2

Regards,
Salvatore

Bug#936932: libvigraimpex: Python2 removal in sid/bullseye

[Andreas Metzler]

On 2019-12-21 Andreas Metzler  wrote:
> On 2019-10-01 Andreas Tille  wrote:
> > Control: tags -1 help

> > Hi,

> > I tried hard to port libvigraimpex to Python3 in Git[1] and think I
> > managed.

> Hello Andreas,

> I did not get far trying to build what is currently on salsa:
[...]

I have now made progress to a successful build. Will post a patch series
or merge request today or tomorrow.

[...]
> I suspect Fedora's patch would help.
> https://src.fedoraproject.org/rpms/vigra/blob/master/f/vigra-1.11.1.py37.patch

it does.

cu Andreas

Bug#936924: Moving libsvm to Debian Science team

[Andreas Tille]

On Sat, Dec 21, 2019 at 08:28:57AM +, Mo Zhou wrote:
> I second this proposal, and the same for src:liblinear.

That's done as I wrote.
 
> These are high popcon packages, dependencies for a number of other
> packages. They should be team maintained to unblock important fixes.

To push a bit I just commited

   https://salsa.debian.org/science-team/libsvm

Last maintainer upload was more than 3 years ago, 2 NMUs inbetween,
package is lagging behind upstream.  Anybody is kindly invited to adapt
the packaging (I think we should really get rid of cdbs since this in
turn is Python2) and proceed from here.

Kind regards

 Andreas.


> On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> > Hi Chen-Tse,
> > 
> > I'm maintaining a package that depends from libsvm.  Due to bug #936924
> > that did not received any response since August it is in danger to be
> > removed from testing so I'm interested that this bug will be fixed.
> > When looking at the package I realised that while it would fit into
> > Debian Science team scope it is not team maintained nor is there any
> > repository in Salsa.  That's why I have the following suggestion:
> > 
> >   1. I create a repository on Salsa
> >   2. Move the package to Debian Science team maintenance
> >  and add you as Uploader
> >   3. Drop Python2 package and close bug #936924
> >   4. May be migrate packaging from cdbs to dh
> > 
> > If I do not hear from you until Monday I assume you agree with this
> > plan and will do so.
> > 
> > Kind regards
> > 
> >  Andreas.
> > 
> > PS: @Christian: I noticed that you and Chen-Tse are maintaining
> > liblinear.  I have just removed Python2 package and reassigned
> > #936889 to ftp.debian.org to make sure python-liblinear will be
> > removed.  Thus libsvm can be dealt as suggested.
> > 
> > -- 
> > http://fam-tille.de
> > 
> 
> 

-- 
http://fam-tille.de

Bug#936910: marked as done (librcsb-core-wrapper: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sat, 21 Dec 2019 11:10:10 +
with message-id 
and subject line Bug#936910: fixed in librcsb-core-wrapper 1.005-7
has caused the Debian Bug report #936910,
regarding librcsb-core-wrapper: 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.)


-- 
936910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:librcsb-core-wrapper
Version: 1.005-6
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:librcsb-core-wrapper

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 ---
Source: librcsb-core-wrapper
Source-Version: 1.005-7

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated librcsb-core-wrapper 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 18 Dec 2019 16:39:25 +0100
Source: librcsb-core-wrapper
Binary: librcsb-core-wrapper-doc librcsb-core-wrapper0 
librcsb-core-wrapper0-dbgsym librcsb-core-wrapper0-dev python3-corepywrap 
python3-corepywrap-dbgsym
Architecture: source all amd64
Version: 1.005-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 librcsb-core-wrapper-doc - documentation for librcsb-core-wrapper0
 librcsb-core-wrapper0 - C++ library providing OO API to information in mmCIF 
format
 librcsb-core-wrapper0-dev - development files for librcsb-core-wrapper0
 python3-corepywrap - library that exports C++ mmCIF accessors to Python3
Closes: 936910
Changes:
 librcsb-core-wrapper (1.005-7) unstable; urgency=medium
 .
   * Switch wrapper from Python2 to Python3
 Closes: #936910
   * debhelper-compat 10 (fails to build with 12 - so 

Bug#947118: [Pkg-javascript-devel] Bug#947118: node-on-headers: autopkgtest started failing and then times out

[Xavier]

Le 21/12/2019 à 12:04, Utkarsh Gupta a écrit :
> Hiya,
> 
> On Sat, Dec 21, 2019 at 3:51 PM Paul Gevers  > wrote:
> 
> Your package has an autopkgtest, great. However, I noticed that without
> any change from your side it started failing, and while doing so also
> doesn't finish, hence timing out on ci.debian.net
> . Obviously this isn't
> your fault, but please investigate, such that you can assign this bug to
> the right package. Please consider improving the test suite to not hang
> in case of failure. This is not the only node package that has this,
> e.g. check https://ci.debian.net/status/slow/ to see more. Don't
> hesitate to ask for help from the Debian CI team (in X-Debbugs-CC) if
> you need help solving this issue.
> 
> 
> I've just added a --timeout 1, which should be enough to fix this
> (and switched the package to use pkg-js-tools).
> 
> Could someone confirm if that indeed works?
> 
> Best,
> Utkarsh

No, this is a node-supertest problem. Fixed and uploaded (see the link,
test ≥ 2h)

Bug#947118: [Pkg-javascript-devel] Bug#947118: node-on-headers: autopkgtest started failing and then times out

[Utkarsh Gupta]

Hiya,

On Sat, Dec 21, 2019 at 3:51 PM Paul Gevers  wrote:

> Your package has an autopkgtest, great. However, I noticed that without
> any change from your side it started failing, and while doing so also
> doesn't finish, hence timing out on ci.debian.net. Obviously this isn't
> your fault, but please investigate, such that you can assign this bug to
> the right package. Please consider improving the test suite to not hang
> in case of failure. This is not the only node package that has this,
> e.g. check https://ci.debian.net/status/slow/ to see more. Don't
> hesitate to ask for help from the Debian CI team (in X-Debbugs-CC) if
> you need help solving this issue.
>

I've just added a --timeout 1, which should be enough to fix this (and
switched the package to use pkg-js-tools).

Could someone confirm if that indeed works?


Best,
Utkarsh

>

Bug#947118: node-on-headers: autopkgtest started failing and then times out

[Xavier]

Hi,

I updated node-supertest, this will fix most of node-* packages
referenced in https://ci.debian.net/status/slow/

Cheers,
Xavier

Bug#946951: workaround

[Benjamin Poirier]

Thanks for your analysis. I have the same problem and a simple
workaround for the time being is to do:
ln -s /tmp/.wine-1000/ /run/user/1000/wine

Bug#947117: reproducible

[Paolo Greppi]

Thanks for reporting !

Can be patched by adding libegl-dev to the build deps, but I'd wait of the Qt 
gurus find a better way to fix it.

Paolo

Bug#945595: Wrong bug number?

[Graham Inggs]

Hi, does this message have the wrong bug number?


To: cont...@bugs.debian.org
From: Mateusz Łukasik 
Subject: Re: New mpv in sid breaks smplayer
Message-ID: <8d5a8d18-b29a-179f-4701-b97226937...@linuxmint.pl>
Date: Thu, 12 Dec 2019 08:56:03 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Greylist: delayed 371 seconds by postgrey-1.36 at buxtehude; Thu, 12
Dec 2019 08:02:26 UTC
Delivered-To: cont...@bugs.debian.org

fixed 940919 19.10.2~ds0-1
thanks

Processed: Re: Bug#947117: doxygen: Build error: "Qt5::Gui" references the file "/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 qtbase5-dev 5.12.5+dfsg-2
Bug #947117 [src:doxygen] doxygen: Build error: "Qt5::Gui" references the file 
"/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.
Bug reassigned from package 'src:doxygen' to 'qtbase5-dev'.
No longer marked as found in versions doxygen/1.8.16-1.
Ignoring request to alter fixed versions of bug #947117 to the same values 
previously set
Bug #947117 [qtbase5-dev] doxygen: Build error: "Qt5::Gui" references the file 
"/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.
Marked as found in versions qtbase-opensource-src/5.12.5+dfsg-2.
> affects -1 src:doxygen
Bug #947117 [qtbase5-dev] doxygen: Build error: "Qt5::Gui" references the file 
"/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.
Added indication that 947117 affects src:doxygen

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

Bug#947117: doxygen: Build error: "Qt5::Gui" references the file "/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.

[Dmitry Shachnev]

Control: reassign -1 qtbase5-dev 5.12.5+dfsg-2
Control: affects -1 src:doxygen

On Sat, Dec 21, 2019 at 10:54:07AM +0100, Andreas Metzler wrote:
> doxygen does not build anymore on sid/amd64:
>
> -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
> -- Using Qt5
> CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 
> (message):
>   The imported target "Qt5::Gui" references the file
>
>  "/usr/lib/x86_64-linux-gnu/libEGL.so"
>
>   but this file does not exist.

I will make qtbase5-dev explicitly depend on libegl-dev.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#947118: node-on-headers: autopkgtest started failing and then times out

[Paul Gevers]

Source: node-on-headers
Version: 1.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout regression

Dear maintainers,

Your package has an autopkgtest, great. However, I noticed that without
any change from your side it started failing, and while doing so also
doesn't finish, hence timing out on ci.debian.net. Obviously this isn't
your fault, but please investigate, such that you can assign this bug to
the right package. Please consider improving the test suite to not hang
in case of failure. This is not the only node package that has this,
e.g. check https://ci.debian.net/status/slow/ to see more. Don't
hesitate to ask for help from the Debian CI team (in X-Debbugs-CC) if
you need help solving this issue.

To avoid wasting lots of time on the ci.debian.net infrastructure, I
consider adding your package to the blacklist. If that happens, please
ping me to try any uploads you make that should fix the issue if you are
unsure and don't want to close this bug until verified.

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-on-headers/3635022/log.gz

autopkgtest [01:16:29]: test testsuite: [---


  onHeaders(res, listener)
✓ should fire after setHeader
✓ should fire before write
✓ should fire with no headers
✓ should fire only once
✓ should fire in reverse order
arguments
  res
✓ should be required
  listener
1) should be required
2) should only accept function
setHeader
  ✓ should be available in listener
writeHead(status)
  ✓ should make status available in listener
  ✓ should allow manipulation of status in listener
  3) should pass-through core error
writeHead(status, reason)
  ✓ should be available in listener
writeHead(status, reason, obj)
  ✓ should be available in listener
writeHead(status, obj)
  ✓ should be available in listener
  ✓ should handle falsy keys
writeHead(status, arr)
  ✓ should be available in listener


  14 passing (76ms)
  3 failing

  1) onHeaders(res, listener)
   arguments
 listener
   should be required:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)

  2) onHeaders(res, listener)
   arguments
 listener
   should only accept function:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)

  3) onHeaders(res, listener)
   writeHead(status)
 should pass-through core error:
 Error: Internal Server Error
  at Test.Request.callback
(/usr/share/nodejs/superagent/lib/node/index.js:839:15)
  at IncomingMessage.parser
(/usr/share/nodejs/superagent/lib/node/index.js:1075:18)
  at endReadableNT (_stream_readable.js:1143:12)
  at process._tickCallback (internal/process/next_tick.js:63:19)




signature.asc
Description: OpenPGP digital signature

Bug#947117: doxygen: Build error: "Qt5::Gui" references the file "/usr/lib/x86_64-linux-gnu/libEGL.so" but this file does not exist.

[Andreas Metzler]

Source: doxygen
Version: 1.8.16-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello,

doxygen does not build anymore on sid/amd64:

-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
-- Using Qt5
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:27 
(message):
  The imported target "Qt5::Gui" references the file

 "/usr/lib/x86_64-linux-gnu/libEGL.so"

  but this file does not exist.  Possible reasons include:

  * The file was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and contained

 "/usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake"

  but not all the files it references.

Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:63 
(_qt5_Gui_check_file_exists)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:85 
(_qt5gui_find_extra_libs)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Gui/Qt5GuiConfig.cmake:186 (include)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5Widgets/Qt5WidgetsConfig.cmake:101 
(find_package)
  /usr/lib/x86_64-linux-gnu/cmake/Qt5/Qt5Config.cmake:28 (find_package)
  addon/doxywizard/CMakeLists.txt:6 (find_package)

-- Configuring incomplete, errors occurred!

Cc-ing qtbase5-dev maintainers.

cu Andreas

Processed: Still present in 3.0.13-1

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 Fails to configure package due to "unknown type of DB: BACKUP" on 
> upgrade-db
Bug #930764 [cyrus-common] cyrus-common 3.0.8-6 fails to configure package due 
to "unknown type of DB: BACKUP" on upgrade-db
Changed Bug title to 'Fails to configure package due to "unknown type of DB: 
BACKUP" on upgrade-db' from 'cyrus-common 3.0.8-6 fails to configure package 
due to "unknown type of DB: BACKUP" on upgrade-db'.
> severity -1 grave
Bug #930764 [cyrus-common] Fails to configure package due to "unknown type of 
DB: BACKUP" on upgrade-db
Severity set to 'grave' from 'important'
> tags -1 patch
Bug #930764 [cyrus-common] Fails to configure package due to "unknown type of 
DB: BACKUP" on upgrade-db
Added tag(s) patch.
> found -1 3.0.13-1
Bug #930764 [cyrus-common] Fails to configure package due to "unknown type of 
DB: BACKUP" on upgrade-db
Marked as found in versions cyrus-imapd/3.0.13-1.

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

Processed: python3-cxx-dev: removal of python3-cxx-dev makes files disappear from python-cxx-dev

[Debian Bug Tracking System]

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

> affects 940919 src:pysvn
Bug #940919 [python3-cxx-dev] python3-cxx-dev: removal of python3-cxx-dev makes 
files disappear from python-cxx-dev
Added indication that 940919 affects src:pysvn
> tags 940919 + ftbfs
Bug #940919 [python3-cxx-dev] python3-cxx-dev: removal of python3-cxx-dev makes 
files disappear from python-cxx-dev
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#947113: lout: CVE-2019-19917 CVE-2019-19918

[Salvatore Bonaccorso]

Source: lout
Version: 3.39-3
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

The following vulnerabilities were published for lout.

CVE-2019-19917[0]:
| Lout 3.40 has a buffer overflow in the StringQuotedWord() function in
| z39.c.


CVE-2019-19918[1]:
| Lout 3.40 has a heap-based buffer overflow in the srcnext() function
| in z02.c.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19917
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19917
[1] https://security-tracker.debian.org/tracker/CVE-2019-19918
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19918

Regards,
Salvatore

Bug#936924: Moving libsvm to Debian Science team

[Mo Zhou]

I second this proposal, and the same for src:liblinear.

These are high popcon packages, dependencies for a number of other
packages. They should be team maintained to unblock important fixes.

On Sat, Dec 21, 2019 at 08:35:28AM +0100, Andreas Tille wrote:
> Hi Chen-Tse,
> 
> I'm maintaining a package that depends from libsvm.  Due to bug #936924
> that did not received any response since August it is in danger to be
> removed from testing so I'm interested that this bug will be fixed.
> When looking at the package I realised that while it would fit into
> Debian Science team scope it is not team maintained nor is there any
> repository in Salsa.  That's why I have the following suggestion:
> 
>   1. I create a repository on Salsa
>   2. Move the package to Debian Science team maintenance
>  and add you as Uploader
>   3. Drop Python2 package and close bug #936924
>   4. May be migrate packaging from cdbs to dh
> 
> If I do not hear from you until Monday I assume you agree with this
> plan and will do so.
> 
> Kind regards
> 
>  Andreas.
> 
> PS: @Christian: I noticed that you and Chen-Tse are maintaining
> liblinear.  I have just removed Python2 package and reassigned
> #936889 to ftp.debian.org to make sure python-liblinear will be
> removed.  Thus libsvm can be dealt as suggested.
> 
> -- 
> http://fam-tille.de
>