Bug#937465: marked as done (pykerberos: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 30 Dec 2019 07:19:57 +
with message-id 
and subject line Bug#937465: fixed in pykerberos 1.1.14-3.1
has caused the Debian Bug report #937465,
regarding pykerberos: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pykerberos

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: pykerberos
Source-Version: 1.1.14-3.1

We believe that the bug you reported is fixed in the latest version of
pykerberos, 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.
Sandro Tosi  (supplier of updated pykerberos 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, 30 Dec 2019 01:53:20 -0500
Source: pykerberos
Architecture: source
Version: 1.1.14-3.1
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Sandro Tosi 
Closes: 937465
Changes:
 pykerberos (1.1.14-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937465
Checksums-Sha1:
 0bdf87ed112447c7666a44b7c465db088b5fc8e1 1981 pykerberos_1.1.14-3.1.dsc
 1719d6a271a7f6e831469f9afe3e037c4369f162 5812 
pykerberos_1.1.14-3.1.debian.tar.xz
 d71b48c5bbf19862ca663b67dc6d081bc826f4b3 7014 
pykerberos_1.1.14-3.1_source.buildinfo
Checksums-Sha256:
 547c7bd2f9282ef22e7c81ddbe7c267b50ccf2c893718939464cbcef9099407e 1981 
pykerberos_1.1.14-3.1.dsc
 c24dc1a98a8bf53efe75f93f2f21cd53259143f43d6d599ad47592b650882c49 5812 
pykerberos_1.1.14-3.1.debian.tar.xz
 08f1daf55c77849217c93190d5e15f2145cb92be9c1cff7c201517d1b8231b2a 7014 
pykerberos_1.1.14-3.1_source.buildinfo
Files:
 bb9b9fb21702d1fb73b44a59c

Processed: python-jedi: diff for NMU version 0.14.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937849 + pending
Bug #937849 [src:python-jedi] python-jedi: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#943012: marked as done (dfwinreg: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 30 Dec 2019 07:04:14 +
with message-id 
and subject line Bug#943012: fixed in dfwinreg 20190122-1.1
has caused the Debian Bug report #943012,
regarding dfwinreg: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_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: dfwinreg
Source-Version: 20190122-1.1

We believe that the bug you reported is fixed in the latest version of
dfwinreg, 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.
Sandro Tosi  (supplier of updated dfwinreg 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, 30 Dec 2019 01:37:16 -0500
Source: dfwinreg
Architecture: source
Version: 20190122-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sandro Tosi 
Closes: 936389 943012
Changes:
 dfwinreg (20190122-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #943012, #936389
Checksums-Sha1:
 6aaf21ee298e657166fe1fb6c7ac792072ac0dec 2167 dfwinreg_20190122-1.1.dsc
 a9d6605e947df1705a85b66ac67b429333fa6792 2932 
dfwinreg_20190122-1.1.debian.tar.xz
 cba7917ab7e841aa0b52c1b855535d5275db4405 6071 
dfwinreg_20190122-1.1_source.buildinfo
Checksums-Sha256:
 c6a47fe807fa5a40ea3392faddfe13ed9a6e05b906b5643d7ab2a2dfe10711e6 2167 
dfwinreg_20190122-1.1.dsc
 c151b7bbd0fe1954affac0c8b0808356f9a74f8e0f98498be4bf099511388092 2932 
dfwinreg_20190122-1.1.debian.tar.xz
 76e90f975fac66bb1ba64a9106ca486ed042888784bcebd9f65a1050117923e3 6071 
dfwinreg_20190122-1.1_source.buildinfo
Files:
 dac0a1357807a9a3288f95fc67bf0e16 2167 python optional dfwinreg_20190122-1.1.dsc
 22eaba8e2919590bcbb75f51b8bfc99b 2932 python optional 
dfwinreg_20190122-1.1.debian.tar.xz

Bug#937849: python-jedi: diff for NMU version 0.14.1-1.1

[Sandro Tosi]

Control: tags 937849 + pending


Dear maintainer,

I've prepared an NMU for python-jedi (versioned as 0.14.1-1.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

I didnt think a new upstream release is necessary to fix this bug, so in the
spirit of keeping the NMU as short as possible, i've prepared this one

Regards.

diff -Nru python-jedi-0.14.1/debian/changelog python-jedi-0.14.1/debian/changelog
--- python-jedi-0.14.1/debian/changelog	2019-07-22 18:24:39.0 -0400
+++ python-jedi-0.14.1/debian/changelog	2019-12-30 02:02:27.0 -0500
@@ -1,3 +1,10 @@
+python-jedi (0.14.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937849
+
+ -- Sandro Tosi   Mon, 30 Dec 2019 02:02:27 -0500
+
 python-jedi (0.14.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-jedi-0.14.1/debian/control python-jedi-0.14.1/debian/control
--- python-jedi-0.14.1/debian/control	2018-12-31 05:33:46.0 -0500
+++ python-jedi-0.14.1/debian/control	2019-12-30 01:59:18.0 -0500
@@ -3,23 +3,14 @@
 Section: python
 Priority: optional
 Build-Depends: debhelper (>= 10), dh-python,
- python-all, python3-all,
- python-setuptools, python3-setuptools,
- python-pytest, python3-pytest,
- python-unittest2, python3-unittest2,
- python-docopt, python3-docopt,
+ python3-all,
+ python3-setuptools,
+ python3-pytest,
+ python3-unittest2,
+ python3-docopt,
 Standards-Version: 4.3.0
 Homepage: https://github.com/davidhalter/jedi
 
-Package: python-jedi
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, python-parso (>= 0.3)
-Description: autocompletion tool for Python
- Jedi is an autocompletion tool for Python. It works. With and without syntax
- errors. Sometimes it sucks, but that's normal in dynamic languages. But it
- sucks less than other tools. It understands almost all of the basic Python
- syntax elements including many builtins.
-
 Package: python3-jedi
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}, python3-parso (>= 0.3)
diff -Nru python-jedi-0.14.1/debian/python-jedi.install python-jedi-0.14.1/debian/python-jedi.install
--- python-jedi-0.14.1/debian/python-jedi.install	2016-12-28 11:39:01.0 -0500
+++ python-jedi-0.14.1/debian/python-jedi.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-/usr/lib/python2.*
diff -Nru python-jedi-0.14.1/debian/rules python-jedi-0.14.1/debian/rules
--- python-jedi-0.14.1/debian/rules	2017-01-19 13:04:56.0 -0500
+++ python-jedi-0.14.1/debian/rules	2019-12-30 01:59:34.0 -0500
@@ -3,7 +3,7 @@
 export PYBUILD_DISABLE=test
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 override_dh_installchangelogs:
 	dh_installchangelogs CHANGELOG.rst

Bug#937465: pykerberos: diff for NMU version 1.1.14-3.1

[Sandro Tosi]

Control: tags 937465 + patch


Dear maintainer,

I've prepared an NMU for pykerberos (versioned as 1.1.14-3.1). The diff
is attached to this message.

Regards.

diff -Nru pykerberos-1.1.14/debian/changelog pykerberos-1.1.14/debian/changelog
--- pykerberos-1.1.14/debian/changelog	2019-11-30 09:26:03.0 -0500
+++ pykerberos-1.1.14/debian/changelog	2019-12-30 01:53:20.0 -0500
@@ -1,3 +1,10 @@
+pykerberos (1.1.14-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #937465
+
+ -- Sandro Tosi   Mon, 30 Dec 2019 01:53:20 -0500
+
 pykerberos (1.1.14-3) unstable; urgency=medium
 
   * Depend on dh-python.
diff -Nru pykerberos-1.1.14/debian/control pykerberos-1.1.14/debian/control
--- pykerberos-1.1.14/debian/control	2019-11-30 09:24:44.0 -0500
+++ pykerberos-1.1.14/debian/control	2019-12-30 01:52:41.0 -0500
@@ -6,9 +6,6 @@
 Build-Depends: debhelper (>= 9),
dh-python,
libkrb5-dev,
-   python (>= 2.6.6-3~),
-   python-all-dev,
-   python-setuptools,
python3-all-dev,
python3-setuptools
 Standards-Version: 4.4.0
@@ -16,21 +13,6 @@
 Vcs-Git: https://salsa.debian.org/agx/pykerberos.git
 Vcs-Browser: https://salsa.debian.org/agx/pykerberos
 
-Package: python-kerberos
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Provides: ${python:Provides}
-Description: GSSAPI interface module - Python 2.x
- This Python package is a high-level wrapper for Kerberos (GSSAPI) operations.
- The goal is to avoid having to build a module that wraps the entire
- Kerberos.framework, and instead offer a limited set of functions that do what
- is needed for client/server Kerberos authentication based on
- .
- .
- Much of the C-code here is adapted from Apache's mod_auth_kerb-5.0rc7.
- .
- This package contains the Python 2.x module.
-
 Package: python3-kerberos
 Architecture: any
 Depends: lsb-release, ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
diff -Nru pykerberos-1.1.14/debian/rules pykerberos-1.1.14/debian/rules
--- pykerberos-1.1.14/debian/rules	2019-03-21 04:26:46.0 -0400
+++ pykerberos-1.1.14/debian/rules	2019-12-30 01:53:09.0 -0500
@@ -1,22 +1,4 @@
 #!/usr/bin/make -f
 
-PYTHONS:=$(shell pyversions -vr)
-PYTHON3S:=$(shell py3versions -vr)
-
 %:
-	dh $@ --buildsystem=python_distutils --with python2,python3
-
-override_dh_auto_install:
-	set -e && for pyvers in $(PYTHONS); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python-kerberos; \
-	done
-	set -e && for pyvers in $(PYTHON3S); do \
-		python$$pyvers setup.py install --install-layout=deb \
-			--root $(CURDIR)/debian/python3-kerberos; \
-	done
-
-override_dh_clean:
-	rm -rf build
-	dh_clean -O--buildsystem=python_distutils
-
+	dh $@ --buildsystem=pybuild --with python3

Processed: pykerberos: diff for NMU version 1.1.14-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 937465 + patch
Bug #937465 [src:pykerberos] pykerberos: Python2 removal in sid/bullseye
Added tag(s) patch.

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

Bug#947757: pysparse: should this package be removed?

[Sandro Tosi]

Source: pysparse
Severity: serious

Hello,
it seeems to me there are several issues with this package:

* python2 only, and there's already another `python3-sparse` from another src
* no upstream commits since 2013, 
https://sourceforge.net/p/pysparse/git/commit_browser
* no upstream releases since 2010

If i dont hear back within a week with a good reason to keep this package in
Debian, i'll file for its removal.

Regards,
Sandro

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

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

Bug#943012: dfwinreg: diff for NMU version 20190122-1.1

[Sandro Tosi]

Dear maintainer,

I've prepared an NMU for dfwinreg (versioned as 20190122-1.1). The diff
is attached to this message.

Regards.

diff -Nru dfwinreg-20190122/debian/changelog dfwinreg-20190122/debian/changelog
--- dfwinreg-20190122/debian/changelog	2019-01-23 04:45:44.0 -0500
+++ dfwinreg-20190122/debian/changelog	2019-12-30 01:37:16.0 -0500
@@ -1,3 +1,10 @@
+dfwinreg (20190122-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #943012, #936389
+
+ -- Sandro Tosi   Mon, 30 Dec 2019 01:37:16 -0500
+
 dfwinreg (20190122-1) unstable; urgency=medium
 
   * New upstream version 20190122
diff -Nru dfwinreg-20190122/debian/control dfwinreg-20190122/debian/control
--- dfwinreg-20190122/debian/control	2019-01-23 04:45:15.0 -0500
+++ dfwinreg-20190122/debian/control	2019-12-30 01:36:58.0 -0500
@@ -4,37 +4,19 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 12), dh-python,
- python-dtfabric (>= 20170524), python3-dtfabric (>= 20170524),
- python, python3,
- python-setuptools, python3-setuptools,
- python-dfdatetime (>= 20160814), python3-dfdatetime (>= 20160814),
- python-libregf (>=20150315), python3-libregf (>=20150315),
- python-mock, python3-mock,
- python-six (>= 1.1.0), python3-six (>= 1.1.0),
- python-yaml (>= 3.10),  python3-yaml (>= 3.10),
+ python3-dtfabric (>= 20170524),
+ python3-all,
+ python3-setuptools,
+ python3-dfdatetime (>= 20160814),
+ python3-libregf (>=20150315),
+ python3-mock,
+ python3-six (>= 1.1.0),
+ python3-yaml (>= 3.10),
 Standards-Version: 4.3.0
 Homepage: https://github.com/log2timeline/dfwinreg
 Vcs-Git: https://salsa.debian.org/pkg-security-team/dfwinreg.git
 Vcs-Browser: https://salsa.debian.org/pkg-security-team/dfwinreg
 
-Package: python-dfwinreg
-Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
- python-dtfabric (>= 20170524),
- python-dfdatetime (>= 20160814),
- python-libregf (>=20150315),
- python-mock,
- python-six (>= 1.1.0),
- python-yaml (>= 3.10)
-Description: Digital Forensics Windows Registry library for Python 2
- dfWinReg, or Digital Forensics Windows Registry, provides read-only
- access to Windows Registry objects. The goal of dfWinReg is to
- provide a generic interface for accessing Windows Registry objects
- that resembles the Registry key hierarchy as seen on a live Windows
- system.
- .
- This package contains the library for Python 2.
-
 Package: python3-dfwinreg
 Architecture: all
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends},
diff -Nru dfwinreg-20190122/debian/rules dfwinreg-20190122/debian/rules
--- dfwinreg-20190122/debian/rules	2019-01-14 04:46:40.0 -0500
+++ dfwinreg-20190122/debian/rules	2019-12-30 01:37:11.0 -0500
@@ -7,19 +7,16 @@
 export PYBUILD_NAME:=dfwinreg
 
 %:
-	dh $@ --with=python2,python3 --buildsystem=pybuild
+	dh $@ --with=python3 --buildsystem=pybuild
 
 override_dh_install:
 	dh_install
 	mv debian/python3-dfwinreg/usr/share/doc/dfwinreg \
 	   debian/python3-dfwinreg/usr/share/doc/python3-dfwinreg
-	mv debian/python-dfwinreg/usr/share/doc/dfwinreg \
-	   debian/python-dfwinreg/usr/share/doc/python-dfwinreg
 	find ./debian -name "LICENSE" -delete
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-	python run_tests.py
 	python3 run_tests.py
 endif
 

Bug#947424: marked as done (qtltools 1.2+dfsg-1 ftbfs on mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 30 Dec 2019 07:31:41 +0100
with message-id 

and subject line 
has caused the Debian Bug report #947424,
regarding qtltools 1.2+dfsg-1 ftbfs on mipsel
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.)


-- 
947424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qtltools
Version: 1.2+dfsg-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your last upload failed to build on mipsel. Your package is part of the
htslib 1.10.2 transition, but I can't binNMU it on mipsel. Please have a
look.

Paul

https://buildd.debian.org/status/package.php?p=qtltools

(I am warned against a big log file, I am restricted in my bandwidth at
the moment so I don't copy in the end of the log file).




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.2+dfsg-2--- End Message ---

Bug#947717: pbcopper FTBFS on all architectures except x32

[Andreas Tille]

On Sun, Dec 29, 2019 at 07:00:54PM +0100, Michael Crusoe wrote:
> pbcopper's latest release has slipped in a code copy of libssw which uses
> x86 SIMD intrinsics. I've pushed up a fix along the lines I made to libssw
> to enable cross architecture compilation at
> https://salsa.debian.org/med-team/pbcopper/commit/f9678ed29590b57fe30638eed3d6819577b4ace1
> and it awaits sponsorship

Thanks a lot for the fix that is sponsored.  However, for s390[1]
there seems to be a timout problem:

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
cd build && meson test --no-rebuild --print-errorlogs
1/2 pbcopper formatting check   OK   0.01 s 
2/2 pbcopper gtest unittestsTIMEOUT 33.17 s 

Ok:1
Expected Fail: 0
Fail:  0
Unexpected Pass:   0
Skipped:   0
Timeout:   1


The output from the failed tests:

2/2 pbcopper gtest unittestsTIMEOUT 33.17 s 

--- command ---
VERBOSE='1' ARGS='-V' /<>/build/tests/pbcopper_test 
--gtest_output=xml:/<>/build/pbcopper-gtest-unittests.xml
--- stdout ---
Running main() from 
/build/googletest-b6wiRD/googletest-1.9.0.20190831/googletest/src/gtest_main.cc
[==] Running 355 tests from 53 test suites.
[--] Global test environment set-up.
[--] 6 tests from CLI_Runner
[ RUN  ] CLI_Runner.emits_tool_contract_when_requested_from_command_line
[   OK ] CLI_Runner.emits_tool_contract_when_requested_from_command_line (0 
ms)
[ RUN  ] CLI_Runner.runs_application_from_vector_of_args
[   OK ] CLI_Runner.runs_application_from_vector_of_args (0 ms)
[ RUN  ] CLI_Runner.runs_application_from_C_style_args
[   OK ] CLI_Runner.runs_application_from_C_style_args (0 ms)
[ RUN  ] CLI_Runner.can_retrieve_input_commandline
[   OK ] CLI_Runner.can_retrieve_input_commandline (1 ms)
[ RUN  ] CLI_Runner.runs_application_from_resolved_tool_contract
[   OK ] CLI_Runner.runs_application_from_resolved_tool_contract (0 ms)
[ RUN  ] CLI_Runner.throws_on_invalid_choices
[   OK ] CLI_Runner.throws_on_invalid_choices (0 ms)
[--] 6 tests from CLI_Runner (1 ms total)

[--] 5 tests from Align_PairwiseAlignment
[ RUN  ] 
Align_PairwiseAlignment.calculates_metrics_from_input_aligned_sequences
[   OK ] 
Align_PairwiseAlignment.calculates_metrics_from_input_aligned_sequences (0 ms)
[ RUN  ] Align_PairwiseAlignment.can_generate_basic_global_alignments
[   OK ] Align_PairwiseAlignment.can_generate_basic_global_alignments (0 ms)
[ RUN  ] 
Align_PairwiseAlignment.maps_target_to_query_positions_from_transcript
[   OK ] 
Align_PairwiseAlignment.maps_target_to_query_positions_from_transcript (0 ms)
[ RUN  ] Align_PairwiseAlignment.check_justify_internals
[   OK ] Align_PairwiseAlignment.check_justify_internals (0 ms)
[ RUN  ] Align_PairwiseAlignment.can_left_and_right_justify_alignments
[   OK ] Align_PairwiseAlignment.can_left_and_right_justify_alignments (0 
ms)
[--] 5 tests from Align_PairwiseAlignment (0 ms total)

[--] 3 tests from Align_AffineAlignment
[ RUN  ] Align_AffineAlignment.can_generate_basic_affine_alignments
[   OK ] Align_AffineAlignment.can_generate_basic_affine_alignments (0 ms)
[ RUN  ] Align_AffineAlignment.correctly_aligns_large_insertion
[   OK ] Align_AffineAlignment.correctly_aligns_large_insertion (10 ms)
[ RUN  ] Align_AffineAlignment.can_generate_IUPAC_aware_alignments
[   OK ] Align_AffineAlignment.can_generate_IUPAC_aware_alignments (0 ms)
[--] 3 tests from Align_AffineAlignment (10 ms total)

[--] 1 test from Align_LinearAlignment
[ RUN  ] Align_LinearAlignment.can_generate_basic_linear_alignments
[   OK ] Align_LinearAlignment.can_generate_basic_linear_alignments (2 ms)
[--] 1 test from Align_LinearAlignment (2 ms total)

[--] 1 test from Align_LocalAlignment
[ RUN  ] Align_LocalAlignment.can_generate_basic_local_alignments
---

Full log written to /<>/build/meson-logs/testlog.txt
make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1


Kind regards

  Andreas.


[1] 
https://buildd.debian.org/status/fetch.php?pkg=pbcopper&arch=s390x&ver=1.3.0%2Bdfsg-2&stamp=1577654596&raw=0

-- 
http://fam-tille.de

Bug#945723: marked as done (weevely: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 30 Dec 2019 02:47:15 +
with message-id 
and subject line Bug#945723: fixed in weevely 4.0.0-1
has caused the Debian Bug report #945723,
regarding weevely: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

We believe that the bug you reported is fixed in the latest version of
weevely, 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.
Samuel Henrique  (supplier of updated weevely 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, 30 Dec 2019 02:07:06 +
Source: weevely
Architecture: source
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 945723
Changes:
 weevely (4.0.0-1) unstable; urgency=medium
 .
   * New upstream version 4.0.0
   * Bump DH to v12
   * Bump Standards-Version to 4.4.1
   * Bump dependencies to python3 (closes: #945723)
   * Add salsa-ci.yml
   * d/copyright: Use https
   * d/control: Add Rules-Requires-Root: no
Checksums-Sha1:
 269918197072477dc5e32e4a18e5b6a31d436774 1909 weevely_4.0.0-1.dsc
 49ddc7d027dc128b24313bf56a5a1ca34adb79cf 164456 weevely_4.0.0.orig.tar.gz
 ae87a980a497f24d062034711c04931684665a86 3108 weevely_4.0.0-1.debian.tar.xz
 8300dfafbec59d6936de2b199ebeb354e1c1e3c5 5276 weevely_4.0.0-1_amd64.buildinfo
Checksums-Sha256:
 3614de030d25b9c20c78b24e8f2e627324db27c512db3511422e85cc4bc044b8 1909 
weevely_4.0.0-1.dsc
 a07c4de3c49d521c8d7050b54c2fef848360171c4600f5e632468228489970a8 164456 
weevely_4.0.0.orig.tar.gz
 bc8eb467d57028f15954144e5e179170cceddc7a1ad0afd1c4090975d1b61537 3108 
weevely_4.0.0-1.debian.tar.xz
 af400aa1fb1246ede15d28

Bug#937267: Is there any Python3 version of pebl

[Abhik Shah]

I haven’t made a py3 port and actually haven’t worked on Pebl in years.
There are some forks though (on github) and they may have py3 versions.



On Sun, Dec 29, 2019 at 5:38 AM Andreas Tille  wrote:

> Control: tags -1 upstream
> Control: forwarded -1 abhiks...@gmail.com
>
> Hi,
>
> Python2 is End Or Life at 1.1.2020 and Debian is about to remove
> all Python2 dependencies.  I wonder if there is any Python2 port
> of Pebl.  I just found
>
>https://pypi.org/project/pebl/
>
> which is at version 1.01 while it seems that at googlecode once
> was a version 1.0.2 - at least the Debian package is at this
> version.  Could you please clarify whether there is some Python3
> version of pebl somewhere else?
>
> Kind regards
>
>  Andreas.
>
> --
> http://fam-tille.de
>

Bug#925822: marked as done (scanbd: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Mon, 30 Dec 2019 01:50:55 +
with message-id 
and subject line Bug#925822: fixed in scanbd 1.5.1-5
has caused the Debian Bug report #925822,
regarding scanbd: ftbfs with GCC-9
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.)


-- 
925822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:scanbd
Version: 1.5.1-4
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/scanbd_1.5.1-4_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
checking for utmpx.h... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for CONFUSE... yes
checking for DBUS... yes
checking for UDEV... yes
checking for pkg-config... (cached) /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
Package systemd was not found in the pkg-config search path.
Perhaps you should add the directory containing `systemd.pc'
to the PKG_CONFIG_PATH environment variable
No package 'systemd' found
checking for SANE... yes
configure: Using user: saned
configure: Using group: scanner
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/scanbd/Makefile
config.status: creating src/scanbuttond/Makefile
config.status: creating src/scanbuttond/backends/Makefile
config.status: creating src/scanbuttond/interface/Makefile
config.status: creating src/scanbuttond/include/Makefile
config.status: creating integration/Makefile
config.status: creating contrib/Makefile
config.status: creating doc/Makefile
config.status: creating conf/Makefile
config.status: creating scripts/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
make[1]: Leaving directory '/<>'
   dh_auto_build -a
make -j4
make[1]: Entering directory '/<>'
Making all in src/scanbd
make[2]: Entering directory '/<>/src/scanbd'
gcc -DPACKAGE_NAME=\"scanbd\" -DPACKAGE_TARNAME=\"scanbd\" 
-DPACKAGE_VERSION=\"1.92\" -DPACKAGE_STRING=\"scanbd\ 1.92\" 
-DPACKAGE_BUGREPORT=\"wilhelm.me...@fh-kl.de\" -DPACKAGE_URL=\"\" 
-DPACKAGE=\"scanbd\" -DVERSION=\"1.92\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 
-DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
-DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ALARM=1 -DHAVE_DUP2=1 
-DHAVE_FTRUNCATE=1 -DHAVE_GETCWD=1 -DHAVE_MEMSET=1 -DHAVE_PUTENV=1 
-DHAVE_REGCOMP=1 -DHAVE_STRDUP=1 -DHAVE_STRERROR=1 -DHAVE_ARPA_INET_H=1 
-DHAVE_FCNTL_H=1 -DHAVE_LIMITS_H=1 -DHAVE_NETINET_IN_H=1 -DHAVE_SYS_SOCKET_H=1 
-DHAVE_SYS_TIME_H=1 -DHAVE_SYSLOG_H=1 -DHAVE_PTHREAD_H=1 -DHAVE_UNISTD_H=1 
-DHAVE_CHOWN=1 -DHAVE_FORK=1 -DHAVE_VFORK=1 -DHAVE_WORKING_VFORK=1 
-DHAVE_WORKING_FORK=1 -DHAVE_STDLIB_H=1 -DHAVE_MALLOC=1 -DHAVE__BOOL=1 
-DHAVE_STDBOOL_H=1 -DHAVE_LINUX_LIMITS_H=1 -DHAVE_UTMP_H=1 -DHAVE_UTMPX_H=1 
-DUSE_LIB
 UDEV=1 -DHAVE_SYSTEMD=1 -DUSE_SANE=1 -I.   -Wdate-time -D_FORTIFY_SOURCE=2 
-Wall -Wextra -std=c11 -g   -Werror   -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include  
-DSCANBUTTOND_LIB_DIR=\"/usr/lib/x86_64-linux-gnu/scanbd/scanbuttond/backe

Bug#946857: marked as done (pyfftw: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 23:49:24 +
with message-id 
and subject line Bug#946857: fixed in pyfftw 0.11.1-4
has caused the Debian Bug report #946857,
regarding pyfftw: FTBFS in unstable
to be marked as done.

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

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


-- 
946857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyfftw
Version: 0.11.1-3
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen on the reproducible builders [1], pyfftw currently
FTBFS in unstable.
This seems to be a combination of new versions of python3-defaults,
numpy and dask.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/pyfftw.html


FAIL: test_objects_removed_after_keepalive
(test.test_pyfftw_interfaces_cache.CacheTest)
--
Traceback (most recent call last):
  File 
"/build/1st/pyfftw-0.11.1/.pybuild/cpython3_3.7_pyfftw/build/test/test_pyfftw_interfaces_cache.py",
line 328, in test_objects_removed_after_keepalive
self.assertRaises(KeyError, _cache.lookup, key)
AssertionError: KeyError not raised by lookup
--- End Message ---
--- Begin Message ---
Source: pyfftw
Source-Version: 0.11.1-4

We believe that the bug you reported is fixed in the latest version of
pyfftw, 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.
Drew Parsons  (supplier of updated pyfftw 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, 30 Dec 2019 10:00:20 +1100
Source: pyfftw
Architecture: source
Version: 0.11.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 946857
Changes:
 pyfftw (0.11.1-4) unstable; urgency=medium
 .
   * Team upload.
   * debian patch fix_dask_011a808.patch applies upstream commit
 011a808 to fix tests against current dask. Closes: #946857.
   * Standards-Version: 4.4.1
Checksums-Sha1:
 915a2fec41a4c6114d7abe4d4dc2e0acf282538f 2334 pyfftw_0.11.1-4.dsc
 31b5a17f46ae826c382de9fcd9e049052af1479a 6836 pyfftw_0.11.1-4.debian.tar.xz
Checksums-Sha256:
 5e923a3f1687347cc6a2d40d4cdf982d7ad8e15f3480e25d7dcbfa738482185a 2334 
pyfftw_0.11.1-4.dsc
 185eed4fd1578ee77eb4e33b96d8b53cafe865680a7521506e09ce1e4c60f752 6836 
pyfftw_0.11.1-4.debian.tar.xz
Files:
 f094b2437e530cc85ebd2f2ce4535ade 2334 python optional pyfftw_0.11.1-4.dsc
 2845466fe0b8b37381b676a5185e632a 6836 python optional 
pyfftw_0.11.1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl4JNJ8ACgkQVz7x5L1a
Afoo6A//Xmo/1+YnoJmo4XaBEJtrxuBPuB12IdAa/CvkQA7vxF+hSV7IPu05XoHg
MFnVkGnncd6MP3T4pPq8lr3RV2YOLN+TJpwqxOMln/xGU2NOnJ3OwrG+IO0kNmQx
FR+9ecSeJ6tRpUUvo84cacR+3FU0AbIUFj+hPojUP2BV27T0CTUDssjJf8KNAeba
RYPbOyJ3AdsfExhFWfmW2jLTn659EPdFmKm/90kVch8MpvL0Tv4WkSK7lOqFGbke
mT3/NUsOnWVOksVONl7WPvaHLOd5UpBbLzx26R3fZemmUWM/Eodn5+N7XTFfZy8C
rzFMP6g1SYc7W1GGxJprr2kCBB6yJn9xV3gptQ9dvgfW9OlOR2lsdoTJsdsOCWHS
JQQIgDQL4FVKkisjGM5PFoaKtH24UHP7iN7F+gjiWgHIeoE9p3zp79/V87/7PoYv
8iTCJd3fvNutXEBk0cPaiB6eynPd832IFZFBSeYMc6kg+yx1Dh2Cba5enlbW9MAj
jETHR41S2s/XNiMf2Kh4qU2YzjXcIayY7/r//zxqledCKxOYnfjDKL5+VXkpkGZ/
Df8XIewHmuz74PiXv8oQj24DAio3JRdbKpU3hEjva4KHmUz4rCS4Tu3zatmJylJL
ekDNQabOk6so/lknSavD0r5La78vGM9DaDq/OJWmJ44fbjzKD5o=
=A/qv
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 23:19:22 +
with message-id 
and subject line Bug#937848: fixed in python-itsdangerous 0.24+dfsg1-2.1
has caused the Debian Bug report #937848,
regarding python-itsdangerous: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-itsdangerous

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-itsdangerous
Source-Version: 0.24+dfsg1-2.1

We believe that the bug you reported is fixed in the latest version of
python-itsdangerous, 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.
Sandro Tosi  (supplier of updated python-itsdangerous 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, 28 Dec 2019 00:41:35 -0500
Source: python-itsdangerous
Architecture: source
Version: 0.24+dfsg1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 937848
Changes:
 python-itsdangerous (0.24+dfsg1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #937848
Checksums-Sha1:
 8a5d112f393f263cc5943942847674518485d3fb 2308 
python-itsdangerous_0.24+dfsg1-2.1.dsc
 e096748163a0d483d54bcc27c34e6e0ae5f02cd1 4748 
python-itsdangerous_0.24+dfsg1-2.1.debian.tar.xz
 b2b650ad8699a32d4e4a44bf62b29cbd40ea1c4b 7279 
python-itsdangerous_0.24+dfsg1-2.1_source.buildinfo
Checksums-Sha256:
 b692ce3fbbf591ad2ea80d575fa0853243b8f4af67f94b709687ab8c48185fc8 2308 
python-itsdangerous_0.24+dfsg1-2.1.dsc
 ba82f01ab1ccbef05e1c5f3763cc51471561fe86cc0e32c4c3bb287a884ec3c6 4748 
python-itsda

Bug#945469: marked as done (yarl fails a test at least with Python 3.8)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 23:19:56 +
with message-id 
and subject line Bug#945469: fixed in yarl 1.4.2-1
has caused the Debian Bug report #945469,
regarding yarl fails a test at least with Python 3.8
to be marked as done.

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

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


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


I: pybuild base:217: cd /<>/.pybuild/cpython3_3.8_yarl/build;
python3.8 -m pytest tests
= test session starts ==
platform linux -- Python 3.8.0+, pytest-4.6.6, py-1.8.0, pluggy-0.13.0
rootdir: /<>
collected 865 items

tests/test_cached_property.py ...[  0%]
tests/test_normalize_path.py ... [  2%]
tests/test_pickle.py ..  [  2%]
tests/test_quoting.py .. [  8%]
 [ 16%]
 [ 24%]
 [ 33%]
 [ 41%]
 [ 49%]
 [ 53%]
tests/test_update_query.py ..[ 57%]
tests/test_url.py .. [ 64%]
 [ 72%]
 [ 80%]
...  [ 83%]
tests/test_url_build.py .[ 86%]
tests/test_url_cmp_and_hash.py ..[ 87%]
tests/test_url_parsing.py F. [ 93%]
 [ 95%]
tests/test_url_query.py ...  [ 96%]
tests/test_url_update_netloc.py  [100%]

=== FAILURES ===
__ TestScheme.test_no_scheme1 __

self = 

def test_no_scheme1(self):
u = URL("google.com:80")
>   assert u.scheme == ""
E   AssertionError: assert 'google.com' == ''
E - google.com

tests/test_url_parsing.py:43: AssertionError
=== 1 failed, 856 passed, 8 xfailed in 2.23 seconds 
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.8_yarl/build; python3.8 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.8 3.7"
returned exit code 13
make: *** [debian/rules:6: build-arch] Error 255
--- End Message ---
--- Begin Message ---
Source: yarl
Source-Version: 1.4.2-1

We believe that the bug you reported is fixed in the latest version of
yarl, 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.
Ondřej Nový  (supplier of updated yarl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 23:49:54 +0100
Source: yarl
Architecture: source
Version: 1.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Ondřej Nový 
Closes: 945469
Changes:
 yarl (1.4.2-1) unstable; urgency=medium
 .
   * Team upload.
   [ Ondřej Nový ]
   * New upstream release.
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
   * Add python3-idna to B-D.
   * Fix tests in new Pythons (Closes: #945469).
   * Remove .coverage fr

Bug#947748: xorg-server: FTBFS in sid (probably due to newer mesa)

[Samuel Thibault]

Source: xorg-server
Version: 2:1.20.6-1
Severity: serious
Tags: patch
Justification: FTBFS

Hello,

Probably since the upload of the newer mesa, xorg-server now FTBFS,
because it misses dri.pc and x11-xcb.pc. The attached patch fixes this.

Samuel

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 
'proposed-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 
'oldstable-proposed-updates'), (500, 'oldoldstable'), (500, 'buildd-unstable'), 
(500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'buildd-experimental'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
"c'est pas nous qui sommes à la rue, c'est la rue qui est à nous"
--- debian/control.original 2019-12-29 23:42:11.163003763 +0100
+++ debian/control  2019-12-29 23:42:28.333138832 +0100
@@ -13,6 +13,7 @@
  xutils-dev (>= 1:7.6+4),
  xfonts-utils (>= 1:7.5+1),
  x11proto-dev (>= 2018.4),
+ libx11-xcb-dev,
  xtrans-dev (>= 1.3.5),
  libxau-dev (>= 1:1.0.5-2),
  libxdmcp-dev (>= 1:0.99.1),
@@ -27,6 +28,7 @@
  libaudit-dev [linux-any],
  libdrm-dev (>= 2.4.89) [!hurd-i386],
  libgl1-mesa-dev (>= 9.2),
+ mesa-common-dev,
  libunwind-dev [amd64 arm64 armel armhf hppa i386 ia64 mips64 mips64el mipsel 
powerpc powerpcspe ppc64 ppc64el sh4],
  libxmuu-dev (>= 1:0.99.1),
  libxext-dev (>= 1:0.99.1),

Bug#947360: marked as done (coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, coinor-libosi-dev)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 22:05:07 +
with message-id 
and subject line Bug#947360: fixed in coinor-dylp 1.10.4-2
has caused the Debian Bug report #947360,
regarding coinor-libdylp-dev: ships headers owned by coinor-libcoinutils-dev, 
coinor-libosi-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.)


-- 
947360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coinor-libdylp-dev
Version: 1.10.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/CoinAlloc.hpp', which is also in 
package coinor-libcoinutils-dev 2.11.3+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb

  Selecting previously unselected package coinor-libdylp-dev.
  Preparing to unpack .../coinor-libdylp-dev_1.10.4-1_amd64.deb ...
  Unpacking coinor-libdylp-dev (1.10.4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/coin/OsiAuxInfo.hpp', which is also in 
package coinor-libosi-dev 0.108.5+repack1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/coinor-libdylp-dev_1.10.4-1_amd64.deb


cheers,

Andreas


coinor-libcoinutils-dev=2.11.3+repack1-1_coinor-libdylp-dev=1.10.4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: coinor-dylp
Source-Version: 1.10.4-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 18:57:28 +
Source: coinor-dylp
Architecture: source
Version: 1.10.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sudip Mukherjee 
Closes: 947360
Changes:
 coinor-dylp (1.10.4-2) unstable; urgency=medium
 .
   * QA upload.
   * Remove CoinUtils and Osi from build. (Closes: #947360)
   * Remove CoinUtils and Osi from doc.
   * Add Rules-Requires-Root to d/control.
   * Update Vcs to debian namespace in salsa.
   * Exclude .md5 files from doc package.
   * Use canonical URI in Vcs.
Checksums-Sha1:
 705ae2e0335463be5eb908bc71602cd5be8254b8 2067 coinor-dylp_1.10.4-2.dsc
 0e9fd2852772a001d17bc44745389a1fd9f53517 9592 
coinor-dylp_1.10.4-2.debian.tar.xz
 2b3d91c266cb1d70c3f0f683996e4b89ef29611a 5806 
coinor-dylp_1.10.4-2_source.buildinfo
Checksums-Sha256:
 f583c7f004bcb414ef478e59b6c6dac39546a885e2dd8b8fae1cafa50cdbc8ed 2067 
coinor-dylp_1.10.4-2.dsc
 670b09941a2d64f492813f5a009300df28c10710f132aead715045dba5805e2f 9592 
coinor-dylp_1.10.4-2.debian.tar.xz
 ef4d311e41ffd13f1f33bc8b81443ce796f64b41770eaa87ed04412a7c92b990 5806 
coinor-dylp_1.10.4-2_source.buildinfo
Files:
 fec4b82859f6fa9a954b440078b624bb 2067 science optional coinor-dylp_1.10.4-2.dsc
 9ca879a8f5cd5ce2a001cd9ba4ecbd4a 9592 science optional 
coinor-dylp_1.10.4-2.debian.tar.xz
 5be850cdf529b7af8811760ee51494ba 5806 science optional 
coinor-dylp_1.10.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl4JH7QACgkQweDZLphv
fH7QSRAA5Kw29DePPfPv3xJQ7CaCnKTUlF2mQDUt

Bug#947745: recent version for stable-(updates|backports)

[Kevin Price]

Package: youtube-dl
Version: 2019.01.17-1.1
Severity: grave

Justification: renders package unusable

Dear maintainer,

the buster version has quit working with yt. The error message is: "YouTube
said: This video is unavailable." 2019.09.28-1 works. Due to the package's
volatility (which causes this grave bug) and given its fairly stable
dependencies, migrating recent versions into stable-updates might well be the
neatest fix to this, imho.

See also #908947.

Cheers
Kevin



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

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

Versions of packages youtube-dl depends on:
ii  python33.7.3-1
ii  python3-pkg-resources  40.8.0-1

Versions of packages youtube-dl recommends:
ii  aria21.34.0-4
ii  ca-certificates  20190110
ii  curl 7.64.0-4
ii  ffmpeg   7:4.1.4-1~deb10u1
ii  mpv  0.29.1-1
ii  phantomjs2.1.1+dfsg-2
ii  python3-pyxattr  0.6.1-1
ii  rtmpdump 2.4+20151223.gitfa8646d.1-2
ii  wget 1.20.1-1.1

youtube-dl suggests no packages.

-- no debconf information

Bug#943509: marked as done (python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 21:54:23 +
with message-id 
and subject line Bug#943509: fixed in sqlite3 3.30.1+fossil191229-1
has caused the Debian Bug report #943509,
regarding python-django: FTBFS due to failed tests: failures=7, skipped=891, 
expected failures=4
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.)


-- 
943509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django
Version: 2:3.0~beta1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

python-django/experimental FTBFS:
https://buildd.debian.org/status/fetch.php?pkg=python-django&arch=all&ver=2%3A3.0%7Ebeta1-1&stamp=1571079369&raw=0


==
FAIL: test_explicit_ForeignKey 
(nested_foreign_keys.tests.DeeplyNestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 176, in 
test_explicit_ForeignKey

self.assertEqual(Package.objects.exclude(screening__movie__director=self.director).count(),
 1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_inheritance (nested_foreign_keys.tests.DeeplyNestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 153, in 
test_inheritance

self.assertEqual(Event.objects.exclude(screening__movie__director=self.director).count(),
 1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_explicit_ForeignKey 
(nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 100, in 
test_explicit_ForeignKey

self.assertEqual(Package.objects.exclude(screening__movie=self.movie).count(), 
1)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 0 != 1

==
FAIL: test_explicit_ForeignKey_NullFK 
(nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
  File "/<>/tests/nested_foreign_keys/tests.py", line 121, in 
test_explicit_ForeignKey_NullFK

self.assertEqual(PackageNullFK.objects.exclude(screening__movie=self.movie).count(),
 2)
  File "/usr/lib/python3.7/unittest/case.py", line 852, in assertEqual
assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.7/unittest/case.py", line 845, in _baseAssertEqual
raise self.failureException(msg)
AssertionError: 1 != 2

==
FAIL: test_inheritance (nested_foreign_keys.tests.NestedForeignKeysTests)
--
Traceback (most recent call last):
  File "/usr/lib/python3.7/unittest/case.py", line 59, in testPartExecutor
yield
  File "/usr/lib/python3.7/unittest/case.py", line 628, in run
testMethod()
 

Bug#947744: installation-reports: Debian Live Testing LXQt + nonfree - install fails with: "Bad unsquash configuration"

[scott092707]

Package: installation-reports
Severity: grave
Justification: renders package unusable

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs 
To: Debian Bug Tracking System 
Subject: installation-reports: Debian Live Testing LXQt + nonfree - install 
fails with: "Bad unsquash configuration"
Bcc: Scott Jacobs 
Message-ID: 
<157765450239.2521.4290165524983598064.reportbug@ASUS-PRIME-B350M-A-CSM>
X-Mailer: reportbug 7.5.3
Date: Sun, 29 Dec 2019 16:21:42 -0500
X-Debbugs-Cc: scott092...@aol.com

Dear Maintainer,

Twice, I tried to install the Debian Testing Live LXQt + nonfree .iso, with the
Calamares installer, and twice received the error window with:

"Installation Failed

Bad unsquash configuration
The source filesystem "/run/live/medium/live/filesystem.squashfs" does not
exist"

The .iso s from 12/11/2019 and 12/23/2019 failed exactly the same way.
These came from:
"https://cdimage.debian.org/images/unofficial/non-free/images-including-
firmware/weekly-live-builds/amd64/iso-hybrid/"

My SSD has boot/efi and swap partitions, a /data partition, and 5 20GB
partitions for OS installations.
This is being written from my current Debian Testing LXQt install, which dates
from March of this year, and has been upgraded. (I also sometimes use an old
Lubuntu 17.10 install when I need to scan, as I cannot use my printer/scanner
to scan with Debian, for some reason...)

The install proceeds normally, past the manual install stage (where I mark the
new OS partition for formatting, and keep all others unformatted and labelled
for access from the new install)

Shortly afterwards, the error window appears.

I know the root fs formatting succeeds, at least as far as assigning it a new
UUID - I was unable to boot THIS install until I edited my fstab to comment out
the mount line referring to the old install partition with its old UUID)



-- Package-specific info:

Boot method: USB
Image version: Debian Testing Live LXQt + nonfree .iso  12/11/2019  AND  
12/23/2019
Date: 29, December 2019, ~1pm, ~2pm

Machine: ASUS Prime B350M-A(CSM) + AMD A12e processor and Sapphire Pulse Radeon 
RX560 Graphics Card - 16GB RAM -1TB Crucial MX500 SSD
Partitions: 
scott@ASUS-PRIME-B350M-A-CSM:~$ sudo /sbin/fdisk -l 




   
[sudo] password for scott:  




   
Disk /dev/sda: 931.53 GiB, 1000204886016 bytes, 1953525168 sectors  




   
Disk model: CT1000MX500SSD1 




   
Units: sectors of 1 * 512 = 512 bytes   




   
Sector size (logical/physical): 512 bytes / 4096 bytes  




   
I/O size (minimum/optimal): 4096 bytes / 4096 bytes 

  

Bug#916107: mongodb: MongoDB should not be part of a stable release

[Sandro Tosi]

> I propose to now remove it from unstable, per 
> https://www.mongodb.com/support-policy
> support for 3.4 ends in January 2020.

ive opened #947743 to ask for mongodb removal

Regards,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Processed: Re: Processed (with 1 error): help bts & britney

[Debian Bug Tracking System]

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

> # Oops.
> fixed 946984 2019.12~git~0~e74819ea-6
Bug #946984 {Done: Anton Gladky } [src:yade] yade: Ships 
python3.8 scripts, without any python3 or python3.8 deps
Marked as fixed in versions yade/2019.12~git~0~e74819ea-6.
> thanks
Stopping processing here.

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

Processed (with 1 error): help bts & britney

[Debian Bug Tracking System]

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

> reassign 946984 src:yade 2019.12~git~0~e74819ea-4
Bug #946984 {Done: Anton Gladky } [yade] yade: Ships 
python3.8 scripts, without any python3 or python3.8 deps
Bug reassigned from package 'yade' to 'src:yade'.
No longer marked as found in versions yade/2019.12~git~0~e74819ea-4.
No longer marked as fixed in versions yade/2019.12~git~0~e74819ea-6.
Bug #946984 {Done: Anton Gladky } [src:yade] yade: Ships 
python3.8 scripts, without any python3 or python3.8 deps
Marked as found in versions yade/2019.12~git~0~e74819ea-4.
> fixed 946984 src:yade 2019.12~git~0~e74819ea-6
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[GCS]

Hi Chris,

On Sun, Dec 29, 2019 at 5:57 PM Chris Lamb  wrote:
> I don't fully understand the ramifications or risks of uploading the
> current Fossil tree I'm afraid so I will have to leave that judgement
> to you. Can you let me know your intention either way so that we don't
> lose this down the cracks and delay Paul's work further? I would not
> want to disable the test and remember to re-enable it again, after all.
 OK, I did some testing and couldn't find any immediate problem. Going
to upload the current Fossil tree soon, then follow what problem may
arise in Debian or in upstream issues.

Regards,
Laszlo/GCS

Bug#947482: marked as done (txt2tags: missing Depends: python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 20:55:09 +
with message-id 
and subject line Bug#947482: fixed in txt2tags 3.4-2
has caused the Debian Bug report #947482,
regarding txt2tags: missing Depends: python3-pkg-resources
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.)


-- 
947482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: txt2tags
Version: 3.4-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:thunderbolt-tools

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

This is due to a missing dependency on python3-pkg-resources. It happens
to make packages that use txt2tags during build (such as
thunderbolt-tools) ftbfs.

Helmut
--- End Message ---
--- Begin Message ---
Source: txt2tags
Source-Version: 3.4-2

We believe that the bug you reported is fixed in the latest version of
txt2tags, 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.
Sandro Tosi  (supplier of updated txt2tags 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, 29 Dec 2019 14:55:22 -0500
Source: txt2tags
Architecture: source
Version: 3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Sandro Tosi 
Closes: 947482
Changes:
 txt2tags (3.4-2) unstable; urgency=medium
 .
   * Team upload.
   * Add python3-pkg-resources to Depends; Closes: #947482
Checksums-Sha1:
 e0bf70f9d900a4699d26c7ec41db2ccbedbe018a 2094 txt2tags_3.4-2.dsc
 a1aa279c9f4e176cd86aaae91ad5b43afe8f7aab 5336 txt2tags_3.4-2.debian.tar.xz
 268aee07c9c1830f03ea3088b23d594e3adbcd64 6124 txt2tags_3.4-2_source.buildinfo
Checksums-Sha256:
 c42e8addf6c8ed3d436de7fbd81a3f024443ea5e3e625feea04cb5002f600b39 2094 
txt2tags_3.4-2.dsc
 feba1217f8e8b3cf9c966093ce03ffa209ea5686756043defa2b4005dc6d4ff6 5336 
txt2tags_3.4-2.debian.tar.xz
 93d558ff876f3e9738b26b0a59bf7693033d65e506e1cc4f2dd10f4182f14238 6124 
txt2tags_3.4-2_source.buildinfo
Files:
 b14a79e55bc898d8f2157e55486d06b6 2094 misc optional txt2tags_3.4-2.dsc
 88227e1c3a7b60e1864f2986c07be1e5 5336 misc optional 
txt2tags_3.4-2.debian.tar.xz
 53b09baabe7d9fcdeb587e492c514e3c 6124 misc optional 
txt2tags_3.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4JBLYACgkQh588mTgB
qU9CiBAAhjZvvM6zgGO+FDPKaQJBFtl437FU7qQuqsnxfJfSjy1NmlEbSo8/9+I4
abK+Nju0o6uNAZIJcfI2rhkEhyBWj3wKBvU0VLuxJO1fDwNSPDWy5XgLBdSOVybt
8l3+2zC1IQZW3g6XWEd1MSdmzUzLp3ieD2vFUGwTqT+ms5pMUoIxXdIVMOI6qkpF
vYp9A1l47ZiSo7V2cnZqYbYlQSUGj0FC2TqLb6O2p5CWZRkH835SBW5XqsDkX+8t
L3/grioLDUtizBmXaG5qQR3DC+JtnIfhMyLVakzV+AIryZ030e3HVnvQpvJU9VcZ
cVZsGeTJcAzUxR/JQsqgv/8+CQFMpe60G41XKah2ndpZtZtkuEPIJNyOkrSP+GV0
v+SABNBPria1pjPPUAi7ndPKzMk2aeGxqccFM589jqDHEqQI3BIFTZIbjzXuxrXA
BqekrFLIyPj2DHE03zdUB4qpw/qKAMpLv9Aaj2C/iNumJQnCapYuOHrXbaJKHMYw
KqFZXsnNTXPRfIYwfmby2qZ0aL6Ja16P9SE/XVL0RJKJCOUXoczu2Jl2YJFsUG1F
smcNNHSYYSXAAlsbVNBYnrnw0yc4rStcy0jXDkz5JbhSfo5JwD9XgG4wLPkLxU/T
xjWNPJx92g94BvqMFvps3VMP3waG7ZuMrodiARdG2YPryMLwIyI=
=Q7A2
-END PGP SIGNATURE End Message ---

Bug#947717: marked as done (pbcopper FTBFS on all architectures except x32)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 20:52:27 +
with message-id 
and subject line Bug#947717: fixed in pbcopper 1.3.0+dfsg-2
has caused the Debian Bug report #947717,
regarding pbcopper FTBFS on all architectures except x32
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.)


-- 
947717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pbcopper
Version: 1.3.0+dfsg-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your package fails to build from source on all buildds except x32. Your
package is involved in the pbbam and htslib transitions and blocking
progress. Please have a look.

Paul

https://buildd.debian.org/status/package.php?p=pbcopper

Tail of log for pbcopper on arm64:

cc -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude -I../include
-Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -MF
'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o.d' -o
'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -c ../src/align/cssw/ssw.c
../src/align/cssw/ssw.c:38:10: fatal error: emmintrin.h: No such file or
directory
   38 | #include 
  |  ^
compilation terminated.
[9/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -c
../src/align/LinearAlignment.cpp
[10/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -c
../src/align/BandedChainAlignment.cpp
[11/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -c
../src/align/AffineAlignment.cpp
[12/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -c
../src/align/SparseAlignment.cpp
[13/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/alig

Bug#943458: marked as done (python-redis: missing test dep on python3-all)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 19:10:09 +
with message-id 
and subject line Bug#943458: fixed in python-redis 3.3.11-2
has caused the Debian Bug report #943458,
regarding python-redis: missing test dep on python3-all
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.)


-- 
943458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-redis
Version: 3.2.1-3
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

The python-redis package quite sensibly runs autopkgtests to confirm the
module's compatibility with all supported versions of python.  However, it
does not declare a test dependency on python3-all, so not all the versions
of python returned by py3versions -r are guaranteed to be installed,
resulting in failures such as the following:

[...]
autopkgtest [18:45:55]: test 0002-python3: [---
+ py3versions -r
+ python3.8 setup.py test
/tmp/autopkgtest.DB01Mz/build.tmH/src/debian/tests/0002-python3: 9: python3.8: 
not found
autopkgtest [18:45:56]: test 0002-python3: ---]
[...]

  (http://autopkgtest.ubuntu.com/packages/p/python-redis/focal/amd64)

This is an issue today in Ubuntu where python3-defaults has been updated to
support python3.8.  It has not yet hit Debian, since this version of
python3-defaults is still only in experimental.

The attached patch adds the necessary test dep on python3-all.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru python-redis-3.2.1/debian/tests/control 
python-redis-3.2.1/debian/tests/control
--- python-redis-3.2.1/debian/tests/control 2019-07-20 13:06:05.0 
-0700
+++ python-redis-3.2.1/debian/tests/control 2019-10-24 16:54:10.0 
-0700
@@ -4,7 +4,7 @@
 
 Tests: 0002-python3
 Restrictions: allow-stderr
-Depends: @, redis-server, python3-pytest, python3-setuptools, python3-mock
+Depends: @, redis-server, python3-pytest, python3-setuptools, python3-mock, 
python3-all
 
 Tests: 0003-interaction
 Depends: @, redis-server
--- End Message ---
--- Begin Message ---
Source: python-redis
Source-Version: 3.3.11-2

We believe that the bug you reported is fixed in the latest version of
python-redis, 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.
Sandro Tosi  (supplier of updated python-redis 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, 29 Dec 2019 13:38:01 -0500
Source: python-redis
Architecture: source
Version: 3.3.11-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 943458
Changes:
 python-redis (3.3.11-2) unstable; urgency=medium
 .
   * Team upload.
   * Add python3-all to py3k autopkgtests; Closes: #943458
Checksums-Sha1:
 c76efee89d084822f81d3e22cc2584a8840b9ba7 2287 python-redis_3.3.11-2.dsc
 470326e8de09cbd978bf54e0f4552d8586733e77 4988 
python-redis_3.3.11-2.debian.tar.xz
 489288258cab2c4bb9d25bd7b663c453257e569d 6716 
python-redis_3.3.11-2_source.buildinfo
Checksums-Sha256:
 f18746b3ff87439c438dab806a57845f1e9adf19591eaf90b6ef36bbba8f35ca 2287 
python-redis_3.3.11-2.dsc
 9744486b76811f1510b6aeaba2b11cbc1f41b05e6293c823ca1fc206dd5d79aa 4988 
python-redis_3.3.11-2.debian.tar.xz
 28e0262bf3673aa4364e0618bc4a35232dcc3d28fdf69a2790bfb2c0b5ef9f10 6716 
python-redis_3.3.11-2_source.buildinfo
Files:
 f7ebe81ff52992c8f64d526b405942fb 2287 python optional python-redis_3.3.11-2.dsc
 969986f8976cb2457b6f7b2487ef0b96 4988 python optional 
python-redis_3.3.11-2.debian.tar.xz
 faafce8c324c4cf4b85c4c4be6afc630 6716 python optional 
python-redis_3.3.11-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl4I8qIACgkQh588mTgB
qU9a0w//V0za

Processed: watson: FTBFS in bullseye and sid

[Debian Bug Tracking System]

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

> tags 947733 + sid bullseye
Bug #947733 [src:watson] watson: FTBFS in bullseye and sid
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#947237: gnome-software: Crashes on click over any software icon

[Laurent Bigonville]

On Mon, 23 Dec 2019 11:45:45 +0100 definetti  wrote:

> Dear Maintainer,

Hello,

> upon updating to 3.34.2, the application crashes when I click over any
software
> icon, before the relative page is loaded.
> Valgrind reports a segmentation fault with the error
>
> ==186020== Thread 5 pool-gnome-soft:
> ==186020== Invalid read of size 1
> ==186020== at 0x49AAE20: g_str_hash (in /usr/lib/x86_64-linux-
> gnu/libglib-2.0.so.0.6200.3)
> ==186020== by 0x49A9EFE: g_hash_table_lookup (in /usr/lib/x86_64-linux-
> gnu/libglib-2.0.so.0.6200.3)
> ==186020== by 0xE030388: ??? (in /usr/lib/x86_64-linux-gnu/gs-
> plugins-13/libgs_plugin_snap.so)
> ==186020== by 0xE030D2C: gs_plugin_add_alternates (in
/usr/lib/x86_64-linux-
> gnu/gs-plugins-13/libgs_plugin_snap.so)

The issue seems to be in the snap plugin, are you using snap? Could you
please install the debug packages (gnome-software-plugin-snap-dbgsym and
gnome-software-dbgsym) and try to reproduce the issue so we have a
better trace?

If you are not using snap, could you try to uninstall the
gnome-software-plugin-snap package and see if you can still reproduce it?

Thanks,

Laurent Bigonville

Processed: found 947237 in 3.34.2-1

[Debian Bug Tracking System]

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

> found 947237 3.34.2-1
Bug #947237 [gnome-software-plugin-snap] gnome-software: Crashes on click over 
any software icon
Marked as found in versions gnome-software/3.34.2-1.
> thanks
Stopping processing here.

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

Processed: reassign 947237 to gnome-software-plugin-snap

[Debian Bug Tracking System]

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

> reassign 947237 gnome-software-plugin-snap
Bug #947237 [gnome-software] gnome-software: Crashes on click over any software 
icon
Bug reassigned from package 'gnome-software' to 'gnome-software-plugin-snap'.
No longer marked as found in versions gnome-software/3.34.2-1.
Ignoring request to alter fixed versions of bug #947237 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#937170: marked as done (nvpy: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 13:30:20 -0500
with message-id 

and subject line Re: nvpy: Python2 removal in sid/bullseye
has caused the Debian Bug report #937170,
regarding nvpy: 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.)


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

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: 2.0.0-1

On Fri, 30 Aug 2019 07:28:52 + Matthias Klose  wrote:
> Package: src:nvpy
> Version: 1.0.0+git20171203.c91062c-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal

https://tracker.debian.org/news/1090249/accepted-nvpy-200-1-source-all-into-unstable-unstable/--- End Message ---

Bug#947726: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 18:19:58 +
with message-id 
and subject line Bug#947726: fixed in osmnx 0.11+ds-2
has caused the Debian Bug report #947726,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in 
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.)


-- 
947726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breathe
Version: 4.11.1-1
Severity: serious
Tags: ftbfs sid bullseye

Recently the texlive-base package has stopped building the transitional
package texlive-generic-extra. This is an issue for your package as it
build-depends on it. Please update the building of your package to use
texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-07-16.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: osmnx
Source-Version: 0.11+ds-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 17:57:41 +
Source: osmnx
Architecture: source
Version: 0.11+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Jerome Benoit 
Changed-By: Jerome Benoit 
Closes: 947726
Changes:
 osmnx (0.11+ds-2) unstable; urgency=medium
 .
   * Fix Release Critical bug due texliv-base transition (Closes: #947726).
   * Debiaization:
 - debian/control:
   - Build-Depends-Indep field, replace texlive-generic-extra by
 texlive-plain-generic.
Checksums-Sha1:
 80015f784c6759593b075012625cdd66b693b03f 3269 osmnx_0.11+ds-2.dsc
 bb359281ff7e6c4aad6847ec881d9249bbf74696 7984 osmnx_0.11+ds-2.debian.tar.xz
 e820ee394e43cb83be1467b02a77adeeadc8c56c 11102 osmnx_0.11+ds-2_source.buildinfo
Checksums-Sha256:
 1d6ccb5c0e385e9640cd96fc7525492d12821cc6c75df3eabf5d94a4f9b780e1 3269 
osmnx_0.11+ds-2.dsc
 1fa3b3a41e0f4e5d7410528708982e94b55fa173cd47433c3d6f3fd6aa2d662d 7984 
osmnx_0.11+ds-2.debian.tar.xz
 dce3d942b0c247261bef5c10e1290e4faed54d7cde6b66db9150d383d46ee4d5 11102 
osmnx_0.11+ds-2_source.buildinfo
Files:
 2935f027fd6d850ffc99d42de6de3325 3269 python optional osmnx_0.11+ds-2.dsc
 08755ec649b023edd313f0334f0d40fc 7984 python optional 
osmnx_0.11+ds-2.debian.tar.xz
 b0de6cd7cf9fb1366f4ba3122b2fdf3d 11102 python optional 
osmnx_0.11+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl4I6lEVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaL7/ggAIJ1S2xQxMaw0qgIIXcllKuIbMtl
DeH2DSA536Fj8MysjxLTTWlpY4Mmf5tM75Ji5WFYrvmSHBpasq2ySkKBeA1mJtou
XQvf7MFR9RX/mOUEY+SsUZHq39m5B+clMa1B2fwbElMxB73fBD64X0OPw7qXhG2a
2UZeze8wRfemlJnTbHKcqYDIfe9xXYeb/oyb4yHQq02uX+EkGQSZUY8xl6v46Idn
gVDXLWcDgDxWh9SGYyyLat4amYCGHsq5NFjHaoHjHQ0YGo0iQaBjcZwU8gA1T2tx
X85RIfOLQ4GM3rQ/IrO6/awOSO6IoHOpB3dYSI80DJbWKaiZOZj3EGQuqOfFBpW6
0upTVKjT+TDVv+9KHUcYVu66p+809kTheiQThy+jr4ysMc+ylNu/ttWMl2wWYCKr
R5VzY63EEiIj6QWC1U0ux00aYoFWHQBnfFMC6++tIrhQKHmkw8+wcd8UaHx8w0WW
3MnupqNMFs43KRfNkNayGTWKI33n2/syoqD3yUnRKLnYzIGrxy0hPeCA3hjlJMWF
5ildttUyIZx7IvfIp1gzwC7c816eqOru+SifQcF2OxNlhH0NLGmuYD/+cu4ZkkQ3
Ka7iCvxONeB2z9HDmOeGRIGwbttXOEG2UdxpsH4Ucv5K+Sk3AK//7C+Je+MGAUOx
31Dfhkhgb5L+bDz7Es4F3DyqweqoSl0rkfYrlekvxl+51Sx4hNI4up/xX0yceoQC
Z2ThOo+GhJOYd0m6iggNjTbIy9PPlokORkpqN27ZAj5/QUEhe1bQjHB8MSs0/q0A
eSFAFjE+qmrEKiqiOnNDV2di/mhdT+5It6txBz80WqvaYQuGhtn/3Afmpo9CrYL2
x6XP70oLC3W3DOeP+GgSuzyhA/7+9FMGL+Z8kiV5LwodOTyEo4tJmgfWh6YHWBeu
J9OdyKRVIi4hR/Khs+RKexV6e9kqulasHTGy3pf15ienFmMkNT3mS2s51skeY0sp
B6FrYm3YzdpZjjCyolCrgI6NG+yt6dB156B7W60L7s1xBJ8gJjEriikGpadKeuJW
eGt/H5ALOdK6Zx7f1MungmTQJvO6q/rwjqRZNHZf7W6mIQ3mHmG4df/BxH14a+LN
wBGB80xIGv/rvrjbIv77oReAo3TKF/CvLHg/L5tJBhY80TLmmWZB9rXNhhT8kkVj
p+NeWQ0pwEECmIuwQfNk0lWIi9uJQa7e03LhMkB7L2PJm7VrEhhvpS7zg8jDgcSC
Rhq7jOTa1ja7L9WfCD1PMp4fo5HP11/45gOFPYklglT60w7ZJqYWOboqCStGbswi
D8fijhbEM0hC4ZvWGOgt4zj39A

Bug#947717: pbcopper FTBFS on all architectures except x32

[Michael Crusoe]

pbcopper's latest release has slipped in a code copy of libssw which uses
x86 SIMD intrinsics. I've pushed up a fix along the lines I made to libssw
to enable cross architecture compilation at
https://salsa.debian.org/med-team/pbcopper/commit/f9678ed29590b57fe30638eed3d6819577b4ace1
and it awaits sponsorship

Thanks,

On Sun, Dec 29, 2019 at 5:45 PM Andreas Tille  wrote:

> Control: tags -1 help
>
> Hi,
>
> it might be that the new upstream version is targeting only at amd64
> (and by chance builds on x32).  If there is a hint from porters how to
> fix the build the only idea I have is to restrict it to amd64 (and x32).
>
> Kind regards
>
>Andreas.
>
> On Sun, Dec 29, 2019 at 02:15:58PM +0100, Paul Gevers wrote:
> > Source: pbcopper
> > Version: 1.3.0+dfsg-1
> > Severity: serious
> > Justification: ftbfs
> > Tags: ftbfs sid bullseye
> >
> > Dear maintainer,
> >
> > Your package fails to build from source on all buildds except x32. Your
> > package is involved in the pbbam and htslib transitions and blocking
> > progress. Please have a look.
> >
> > Paul
> >
> > https://buildd.debian.org/status/package.php?p=pbcopper
> >
> > Tail of log for pbcopper on arm64:
> >
> > cc -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude -I../include
> > -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c11 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
> > -MD -MQ 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -MF
> > 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o.d' -o
> > 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -c
> ../src/align/cssw/ssw.c
> > ../src/align/cssw/ssw.c:38:10: fatal error: emmintrin.h: No such file or
> > directory
> >38 | #include 
> >   |  ^
> > compilation terminated.
> > [9/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> > -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> > -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> > -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> > 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -MF
> > 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o.d' -o
> > 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -c
> > ../src/align/LinearAlignment.cpp
> > [10/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> > -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> > -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> > -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> > 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -MF
> > 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o.d' -o
> > 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -c
> > ../src/align/BandedChainAlignment.cpp
> > [11/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> > -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> > -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> > -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> > 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -MF
> > 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o.d' -o
> > 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -c
> > ../src/align/AffineAlignment.cpp
> > [12/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> > -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> > -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> > -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> > 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -MF
> > 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o.d' -o
> > 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -c
> > ../src/align/SparseAlignment.cpp
> > [13/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> > -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> > -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> > -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC

Bug#936493: marked as done (exactimage: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 17:34:32 +
with message-id 
and subject line Bug#936493: fixed in exactimage 1.0.2-7
has caused the Debian Bug report #936493,
regarding exactimage: 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.)


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

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: exactimage
Source-Version: 1.0.2-7

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 12:54:56 +0100
Source: exactimage
Architecture: source
Version: 1.0.2-7
Distribution: unstable
Urgency: medium
Maintainer: Sven Eckelmann 
Changed-By: Sven Eckelmann 
Closes: 936493
Changes:
 exactimage (1.0.2-7) unstable; urgency=medium
 .
   * Upload to unstable
 .
 exactimage (1.0.2-6) experimental; urgency=medium
 .
   * Replace python-exactimage package with python3-exactimage (Closes: #936493)
   * debian/control:
 - Allow build without (fake)root
 - Upgraded to policy 4.4.1, no changes required
Checksums-Sha1:
 2db9a602ca15e3ce1d614f9c91a44a39da865ff1 2287 exactimage_1.0.2-7.dsc
 6a523819f8342674657ebeeb16f68f1751b0739d 31016 exactimage_1.0.2-7.debian.tar.xz
 9551ce83b945ac59a9b71cfd6a7d95863546fba8 7968 
exactimage_1.0.2-7_source.buildinfo
Checksums-Sha256:
 0522d6a7fa7a941733086f8067efc35d9a78987797ce0fabfd1647b14c8faa3c 2287 
exactimage_1.0.2-7.dsc
 963661117e2175a5951d20ce09bdb62a59c3dd5cf2894004ace95e6972a5ffd5 3

Processed: tagging 938766

[Debian Bug Tracking System]

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

> tags 938766 + upstream
Bug #938766 [src:uwsgi] uwsgi: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: python-redis: missing test dep on python3-all

[Debian Bug Tracking System]

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

> severity 943458 serious
Bug #943458 [python-redis] python-redis: missing test dep on python3-all
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[Chris Lamb]

Hi László,

> scheduled to 31st of December, this year but it was delayed with a
> whole month later

I don't fully understand the ramifications or risks of uploading the
current Fossil tree I'm afraid so I will have to leave that judgement
to you. Can you let me know your intention either way so that we don't
lose this down the cracks and delay Paul's work further? I would not
want to disable the test and remember to re-enable it again, after all.


Regards,

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

Processed: Re: Bug#947717: pbcopper FTBFS on all architectures except x32

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #947717 [src:pbcopper] pbcopper FTBFS on all architectures except x32
Added tag(s) help.

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

Bug#947717: pbcopper FTBFS on all architectures except x32

[Andreas Tille]

Control: tags -1 help

Hi,

it might be that the new upstream version is targeting only at amd64
(and by chance builds on x32).  If there is a hint from porters how to
fix the build the only idea I have is to restrict it to amd64 (and x32).

Kind regards

   Andreas.

On Sun, Dec 29, 2019 at 02:15:58PM +0100, Paul Gevers wrote:
> Source: pbcopper
> Version: 1.3.0+dfsg-1
> Severity: serious
> Justification: ftbfs
> Tags: ftbfs sid bullseye
> 
> Dear maintainer,
> 
> Your package fails to build from source on all buildds except x32. Your
> package is involved in the pbbam and htslib transitions and blocking
> progress. Please have a look.
> 
> Paul
> 
> https://buildd.debian.org/status/package.php?p=pbcopper
> 
> Tail of log for pbcopper on arm64:
> 
> cc -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude -I../include
> -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c11 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
> -MD -MQ 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -MF
> 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -c ../src/align/cssw/ssw.c
> ../src/align/cssw/ssw.c:38:10: fatal error: emmintrin.h: No such file or
> directory
>38 | #include 
>   |  ^
> compilation terminated.
> [9/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -MF
> 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -c
> ../src/align/LinearAlignment.cpp
> [10/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -MF
> 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -c
> ../src/align/BandedChainAlignment.cpp
> [11/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -MF
> 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -c
> ../src/align/AffineAlignment.cpp
> [12/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -MF
> 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -c
> ../src/align/SparseAlignment.cpp
> [13/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
> -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
> 'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o' -MF
> 'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o.d' -o
> 'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o' -c
> ../src/align/PairwiseAlignment.cpp
> [14/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
> -I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
> -D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
>

Processed: closing 946563

[Debian Bug Tracking System]

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

> close 946563 1:4.4.10-8
Bug #946563 [src:libxcrypt] there is no need for a versioned libxcrypt1-dev 
package
The source 'libxcrypt' and version '1:4.4.10-8' do not appear to match any 
binary packages
Marked as fixed in versions libxcrypt/1:4.4.10-8.
Bug #946563 [src:libxcrypt] there is no need for a versioned libxcrypt1-dev 
package
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#947729: radicale: broken after upgrade from stretch

[Jonas Smedegaard]

control: severity -1 normal

Hi Stefan,

Quoting Stefan Fritsch (2019-12-29 16:14:36)
> Severity: grave
> Justification: renders package unusable

Severity lowered: Package is certainly not unusable (even if upgrade 
feature failed to work for you).


 - Jonas

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

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


signature.asc
Description: signature

Processed: Re: Bug#947729: radicale: broken after upgrade from stretch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #947729 [radicale] radicale: broken after upgrade from stretch
Severity set to 'normal' from 'grave'

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

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[GCS]

Hi Paul, Chris,

On Sun, Dec 29, 2019 at 4:27 PM Chris Lamb  wrote:

> > @python-django maintainers what does this mean for the functionality of
> > python-django in bullseye? Is it "only" the test that fails and can that
> > thus be temporarily disabled?
>
> I would be amenable to disabling the test in python-django if a
> response or fix in sqlite3 is not forthcoming within a few days.
>
 It's a complex situation. SQLite3 upstream recently got fuzzing their
Fossil (source code management tool like Git) tree. Several vulnerabilities
are found - while upstream say these are only an issue if you allow
unauthenticated users enter free form SQL queries against your database.
That means only one possible application, the Chromium browser via WebSQL.
Indeed, a group of security  researchers found a way to exploit a remote
code execution in it, called Magellan 2.0 [1]. It was patched meanwhile and
at least Sid is not affected anymore.
While upstream is quick to fix these reported security problems, there were
introduced an other at least once. This is true for other fixes as well,
they broke something else then. Maybe this is the reason why 3.31.0 (the
next stable SQLite3 release) was first scheduled to 31st of December, this
year but it was delayed with a whole month [2] later. Of course I can
package the current Fossil tree, I'm not sure how it would work in many
scenarios. The upstream testing tools and cases are not open source thus I
can't test it. :-/
As I read, I should do the packaging nevertheless or Chris, may you solve
it with disabled tests?

Regards,
Laszlo/GCS
[1] https://blade.tencent.com/magellan2/index_en.html
[2] https://sqlite.org/draft/releaselog/3_31_0.html

Bug#947733: watson: FTBFS in bullseye and sid

[Graham Inggs]

Source: watson
Version: 1.6.0-6
Severity: serious
Tags: ftbfs

Hi Maintainer

Both watson 1.6.0-6 in bullseye and 1.7.0-5 in sid FTBFS [1].
The upload to sid did not migrate to testing [2].  Please do
source-only uploads, unless there are NEW binaries.

Not built on buildd: arch all binaries uploaded by hpfn, a new
source-only upload is needed to allow migration

I've copied what I hope are the relevant parts of the logs below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/history/amd64/watson.html
[2] https://qa.debian.org/excuses.php?package=watson


= test session starts ==
platform linux -- Python 3.7.5, pytest-3.10.1, py-1.8.0, pluggy-0.13.0
rootdir: /build/watson-1.6.0, inifile:
plugins: mock-1.10.4
collected 82 items

tests/test_config.py ..  [  7%]
tests/test_utils.py ..FF [ 26%]
tests/test_watson.py ... [ 89%]
.[100%]
...
=== 2 failed, 80 passed, 45 warnings in 0.84 seconds ===


= test session starts ==
platform linux -- Python 3.8.1, pytest-4.6.7, py-1.8.0, pluggy-0.13.0
rootdir: /build/1st/watson-1.7.0
plugins: mock-1.10.4
collected 104 items

tests/test_config.py ..  [  5%]
tests/test_fullmoon.py ..[  7%]
tests/test_utils.py ..F.F...FFF. [ 38%]
tests/test_watson.py ... [ 87%]
.[100%]
...
=== 9 failed, 95 passed, 48 warnings in 2.44 seconds ===

Bug#929954: [Python-apps-team] Bug#929954: what about just uploading relevant patch for now?

[Yaroslav Halchenko]

On Fri, 09 Aug 2019, Elena ``of Valhalla'' wrote:

> Yaroslav Halchenko  wrote:
> > If new version building is problematic, why not to upload just a patched
> > version?

> That would only delay the removal a bit: I'm sure that the current
> version doesn't work with python3, so it's going to be removed sooner or
> later from the archive.

> Uploading the new upstream would also be python2 only, at least at the
> beginning, but at least there is hope that it can be made to work also
> with python3.

> I don't expect the new version to be problematic, but it will involve a
> bit of yak shaving, and and see #876681 (RFH: rst2pdf) on how this
> package is pretty low on my priorities.

Hi Elena et al

I wonder if anything could be done to have this package fixed, so
dependent packages (e.g. nuitka) aren't blocked awaiting for the
resolution.

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: python-jellyfish: autopkgtest fails if more than one supported python version

[Debian Bug Tracking System]

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

> severity 943454 serious
Bug #943454 [python-jellyfish] python-jellyfish: autopkgtest fails if more than 
one supported python version
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#947723: devede BD on python-scour which isn't build anymore and isn't in sid/bullseye

[Jonas Smedegaard]

Quoting Paul Gevers (2019-12-29 15:07:13)
> Recently the scour package has stopped building the python-scour 
> package. This is an issue for your package as it build-depends on it. 
> Please update the building of your package.

The _command-line tool_ "scour" has moved to its own package "scour" 
since release 0.36-2, in case that's what is really used during build.

There is also nowadays the package "dh-scour" possible useful.


 - Jonas

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

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


signature.asc
Description: signature

Processed: rdflib: Build-Depends on python-rdflib-jsonld

[Debian Bug Tracking System]

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

> clone 938336 -1
Bug #938336 [src:rdflib] rdflib: Python2 removal in sid/bullseye
Bug 938336 cloned as bug 947730
936709 was blocked by: 937911 937614 938336 943193 936973 937236 938216 936678 
938845 938528 936196 938712 936270 938518 937182 938348
936709 was blocking: 936289 936599 936973 937558 937559 937695 937757 937926 
938168 938256 938492
Added blocking bug(s) of 936709: 947730
936749 was blocked by: 942906 938336
936749 was blocking: 937695 938168 938492
Added blocking bug(s) of 936749: 947730
937156 was blocked by: 937768 936821 942943 937255 936473 937159 937888 937952 
938871 938068 937256 937808 938244 937836 934870 937117 943158 934852 936775 
937404 937415 936569 936196 937426 938719 938716 936637 936742 936424 936528 
937757 938155 936398 947297 938256 936561 945714 938653 937617 936282 937897 
937253 937725 936797 936154 938651 937140 936870 938810 936825 947298 937657 
942992 937168 938022 937758 937680 942973 938458 937318 936285 936120 938753 
938261 937944 936932 938116 938229 936110 937053 936745 938211 938444 938370 
937577 936743 938166 936995 938727 937263 937762 942978 938848 937119 938663 
937252 938661 938845 938625 938618 938336 937114 937224 937491 938310 936304 
937681 937558 937082 938840 938305 938386 937236 938283 937950 938862 942966 
937787 938407 937605 937688 936744 938301 937609 938188 937271 938209 937998 
937851 938236 936219 938002 938278 937446 937675 943199 938008 938408 938515 
937811 938009 936806 936578 936474 937903 936926 937145 936934 936585 936217 
938277 936820 937064 938648 937710 938863 938202 937720 938177 937516 937088 
937293 937489 936501 937143 937291 937485 937939 936774 936503 937232 937250 
937439 937764 937182 935450 938249 938307 937914 938568 936560 938523
937156 was blocking: 937665 937695 938168 938528
Added blocking bug(s) of 937156: 947730
937503 was blocked by: 936270 937300 938471 936312 936580 937267 936561 938730 
936995 937425 936830 938554 937660 936440 938059 943240 936790 93 938348 
938336 937993 938372 938549 938058 937336
937503 was blocking: 937695 938168
Added blocking bug(s) of 937503: 947730
937622 was blocked by: 938336
937622 was blocking: 937569 937695
Added blocking bug(s) of 937622: 947730
937695 was blocked by: 936707 936931 937397 938712 936998 938522 937339 938626 
936241 938690 937168 936457 938490 945626 936196 937047 938861 937066 937033 
936657 936735 936172 939487 883173 938164 937770 937616 938769 945690 937243 
943260 937237 936120 936709 936938 937642 937337 943115 936952 937845 945746 
937161 936459 937803 936659 943223 937049 937297 936810 945630 937993 943027 
938746 936341 937364 937899 937009 938471 937684 937843 945688 936150 937837 
937534 938706 938488 943113 937791 937402 937738 912495 945734 936627 945671 
938261 938688 937602 936793 936427 936208 936749 938591 938734 938671 936165 
936310 937484 943225 936841 945706 938656 937897 937007 943057 938478 937203 
938268 945678 936629 943253 937907 937245 938598 937474 938361 936733 937264 
936848 937035 938794 937411 936982 936312 936936 938307 936489 936267 938295 
936246 943275 938621 937548 937193 936477 937600 942935 937149 945748 936191 
936904 937400 938544 938866 937061 938847 938209 937611 939104 936539 938748 
937961 936689 937750 938565 936894 936152 938421 938309 937541 938235 938628 
936505 936996 937418 936269 936806 943285 936920 942995 938614 937166 936972 
938003 942909 937068 936212 936834 936543 947027 938428 936537 936346 937618 
936687 936599 937968 943079 937135 938476 938809 942993 936170 938099 938451 
936294 943262 937720 937510 945692 938043 945651 937796 938701 938492 938233 
945676 945710 936503 936768 938393 938692 938596 937501 938520 938710 938676 
938651 936564 936867 938572 943157 945701 938807 938458 938097 936812 936944 
942933 942966 937440 943273 937654 938293 938432 936180 945658 936615 938486 
938708 938249 937508 938582 936950 936206 937454 938347 938632 936761 938366 
938686 938835 943217 945708 936869 943159 937640 936614 937001 938096 937891 
937838 938479 937743 937901 936945 937737 938020 937194 938269 937852 938487 
937222 936309 937270 936235 936628 938072 938505 938346 936741 938367 938212 
938834 938543 936428 936207 937660 938198 937910 939103 938131 936893 937455 
937898 937831 938036 938063 942969 945689 943058 938489 945677 937423 943032 
938613 936550 936307 938689 936565 938004 938369 938152 936748 936335 936544 
936833 943156 936866 936847 938677 942912 942994 937331 936997 938180 938615 
936708 936249 937398 936939 938044 937425 936293 937167 938065 938234 937252 
938394 937822 938050 936658 937048 935358 937870 943021 936632 936366 936686 
937625 937238 936536 937291 936266 938503 936247 943126 937568 936999 937338 
937391 936937 942934 936943 938306 936701 938294 937169 943274 943302 936809 
937764 937453 943014 938564 936572 938867 936895 937041 938846 936520 936710 
939478 936596 938545 937880 937231 939481 937941 937703 937675 943056 93845

Bug#947729: radicale: broken after upgrade from stretch

[Stefan Fritsch]

Package: radicale
Version: 2.1.11-6
Severity: grave
Justification: renders package unusable

Hi,

I have upgraded my system from stretch. After some head scratching due
to the new disk format, I have installed the package listen in
NEWS.debian, did

 radicale --export-storage /var/tmp/radicale

Then moved /var/tmp/radicale/collection-root to
/var/lib/radicale/collections and did a chown. Is this the correct path?
This should be described much more verbosely in NEWS.Debian, for example
including the exact commands and directory names.

After that and re-installing radicale 2.1.11-6,

  radicale --verify-storage

did run without error. But now, all requests to radicale return a 500
internal server error. radicale does not log any information despite log
level debug:

# journalctl -u radicale

Dec 29 16:04:01 manul systemd[1]: Starting LSB: Radicale CalDAV and
CardDAV server...
Dec 29 16:04:01 manul radicale[16324]: Starting Radicale CalDAV server :
radicale[7f555ae2f740] INFO: Starting Radicale
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] INFO:
Authentication type is 'htpasswd'
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] DEBUG: registered
'apr_md5_crypt' handler: 
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] INFO: Storage type
is 'multifilesystem'
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] INFO: Rights type
is 'owner_only'
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] INFO: Web type is
'internal'
Dec 29 16:04:01 manul radicale[16324]: [7f555ae2f740] INFO: Listening to
'localhost' on port 5232
Dec 29 16:04:01 manul radicale[16324]: .
Dec 29 16:04:01 manul systemd[1]: Started LSB: Radicale CalDAV and
CardDAV server.


How does one make radicale log what is wrong?

BTW, I run radicale behind an apache reverse proxy and did the
x-script-name config changes.

Cheers,
Stefan

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

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

Versions of packages radicale depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56+nmu1
ii  lsb-base 10.2019051400
ii  python3  3.7.3-1
ii  python3-radicale 2.1.11-6

Versions of packages radicale recommends:
ii  ssl-cert  1.0.39

Versions of packages radicale suggests:
ii  apache2 2.4.38-3+deb10u3
ii  apache2-utils   2.4.38-3+deb10u3
pn  libapache2-mod-proxy-uwsgi  
pn  python3-bcrypt  
ii  python3-passlib 1.7.1-1
pn  uwsgi   
pn  uwsgi-plugin-python3

-- Configuration Files:
/etc/radicale/config changed:
[server]
hosts = 127.0.0.1:5232
certificate = /etc/ssl/certs/ssl-cert-snakeoil.pem
key = /etc/ssl/private/ssl-cert-snakeoil.key
[encoding]
[auth]
type = htpasswd
htpasswd_encryption = md5
[rights]
type = owner_only
[storage]
[web]
[logging]
config = /etc/radicale/logging
debug = true
[headers]

/etc/radicale/logging changed:
[loggers]
keys = root
[handlers]
keys = console
[formatters]
keys = simple
[logger_root]
level = DEBUG
handlers = console
[handler_console]
class = StreamHandler
args = (sys.stderr,)
formatter = simple
[formatter_simple]
format = [%(thread)x] %(levelname)s: %(message)s


-- no debconf information

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[Chris Lamb]

Hi Paul,

> @python-django maintainers what does this mean for the functionality of
> python-django in bullseye? Is it "only" the test that fails and can that
> thus be temporarily disabled?

I would be amenable to disabling the test in python-django if a
response or fix in sqlite3 is not forthcoming within a few days.


Regards,

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

Bug#933284: marked as done (BD on texlive-generic-extra which isn't build anymore and isn't in bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 15:20:37 +
with message-id 
and subject line Bug#933284: fixed in highlight.js 9.12.0+dfsg1-5
has caused the Debian Bug report #933284,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in 
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.)


-- 
933284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: breathe
Version: 4.11.1-1
Severity: serious
Tags: ftbfs sid bullseye

Recently the texlive-base package has stopped building the transitional
package texlive-generic-extra. This is an issue for your package as it
build-depends on it. Please update the building of your package to use
texlive-plain-generic instead.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package also FTBFS in bullseye since 2019-07-16.

Paul





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: highlight.js
Source-Version: 9.12.0+dfsg1-5

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated highlight.js 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, 29 Dec 2019 15:17:41 +0100
Source: highlight.js
Architecture: source
Version: 9.12.0+dfsg1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paul Gevers 
Closes: 933284
Changes:
 highlight.js (9.12.0+dfsg1-5) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI.
   * Trim trailing whitespace.
 .
   [ Paul Gevers ]
   * Build-Depends on texlive-plain-generic i.s.o. texlive-generic-extra
 (Closes: #933284)
   * Update Vcs-* tags to salsa
Checksums-Sha1:
 0f92f2833651929bf454ca9968b10978dd120629 2203 highlight.js_9.12.0+dfsg1-5.dsc
 c5b1c89c48c321935179b5fb9dc43e4fa6c5cc49 16256 
highlight.js_9.12.0+dfsg1-5.debian.tar.xz
Checksums-Sha256:
 080eb7250d11bc0768fce86b635311e3f8d459d64c80347375fb882d825a6295 2203 
highlight.js_9.12.0+dfsg1-5.dsc
 0f6b282246fc61139f540ea98f77eb7d7dfb8c76640fa4e5fd37d5ee80f840a8 16256 
highlight.js_9.12.0+dfsg1-5.debian.tar.xz
Files:
 f3af59813cb138e1b5f03f22533d7d2e 2203 web optional 
highlight.js_9.12.0+dfsg1-5.dsc
 79145246f3d6cb1db8a958bf452dcfe0 16256 web optional 
highlight.js_9.12.0+dfsg1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl4IurgACgkQnFyZ6wW9
dQqLUAgAt+XaMu+dvZlJAe5fjeL744j9JJHBtChXBJ3MaS9Qiu7NofrQ4qNYuJnP
/MpwiP7Qy2s8IQiKP3ZahBJQnvQbMtgRVYA1HQpdygoPK/WqFmu7AlPLWnF3+U8H
LzmZh8maHszrhwerxf/uEyFqAW6vNk3yt7Fsr2XT5w+8mjS5HDIB7oUG/WeE+4J4
VhfLtuGXXkPggjDCBrWNs/zf/gOCpbuky5aYOUz0PhPp+DbuV35mYtkuRcq/AIeI
W/TOYIE4kWyXrM7AkPDV6Y27IPTzlL3ZbqN38Y0eKoXUfgrPBPITby+5pdCm+fIq
IEOaYedcT6md17ZSBr/lniSJZq96yQ==
=S8kF
-END PGP SIGNATURE End Message ---

Bug#943509: python-django: FTBFS due to failed tests: failures=7, skipped=891, expected failures=4

[Paul Gevers]

Hi,

On Sat, 26 Oct 2019 19:17:01 +0100 "Chris Lamb"  wrote:
> Hi László,
> 
> > But you mean plural packages? I knew only python-django. I meant
> > sure, it's a FTBFS in experimental where […]
> 
> I see what you mean now, thanks. I assumed it affected more packages
> and was more severe than just python-django from the description, but
> I admittedly had done no specific searching.
> 
> > In short, I don't get the importance of filing a FTBFS bug for a beta 
> > release in experimental.
> 
> Hah, well my defense I did not file this bug and indeed deliberately
> did not file any issue in Debian for this very reason when I first
> noticed it, prefering to file a bug upstream first (there have been
> similar short-term issues in other database backends in the past).
> 
> I would be perfectly happy with downgrading this to important and thus
> non-RC.
> 
> >  Yeah, you are British. :)
> 
> Don't quite follow that... :)

Can we please move this bug forward? python-django *in sid* has been
failing to build from source since the beginning of November. It's FTBFS
is hampering CVE fixes from reaching testing users and is hampering the
python 2 removal effort.

@python-django maintainers what does this mean for the functionality of
python-django in bullseye? Is it "only" the test that fails and can that
thus be temporarily disabled?

Paul



signature.asc
Description: OpenPGP digital signature

Processed: BD on texlive-generic-extra which isn't build anymore and isn't in bullseye

[Debian Bug Tracking System]

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

> clone 933284 -1
Bug #933284 [highlight.js] BD on texlive-generic-extra which isn't build 
anymore and isn't in bullseye
Bug 933284 cloned as bug 947726
> reassign -1 osmnx 0.10+ds-2
Bug #947726 [highlight.js] BD on texlive-generic-extra which isn't build 
anymore and isn't in bullseye
Bug reassigned from package 'highlight.js' to 'osmnx'.
No longer marked as found in versions 9.12.0+dfsg1-4.
Ignoring request to alter fixed versions of bug #947726 to the same values 
previously set
Bug #947726 [osmnx] BD on texlive-generic-extra which isn't build anymore and 
isn't in bullseye
There is no source info for the package 'osmnx' at version '0.10+ds-2' with 
architecture ''
Unable to make a source version for version '0.10+ds-2'
Marked as found in versions 0.10+ds-2.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 14:44:56 +
with message-id 
and subject line Bug#947129: fixed in x2goclient 4.0.5.2-2+deb9u1
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



pgpvuy82LKl2T.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: x2goclient
Source-Version: 4.0.5.2-2+deb9u1

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: Sun, 22 Dec 2019 14:53:58 +0100
Source: x2goclient
Architecture: source
Version: 4.0.5.2-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 947129
Changes:
 x2goclient (4.0.5.2-2+deb9u1) stretch; 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:
 0244ba470443ff25216cf62258156e3803d78692 2427 x2goclient_4.0.5.2-2+deb9u1.dsc
 337c99644163694d99a85f18599ae35a674cebbb 19392 
x2goclient_4.0.5.2-2+deb9u1.debian.tar.xz
 de6ec636d19cae96d7b01e822b0f3e527eb75745 9895 
x2goclient_4.0.5.2-2+deb9u1_source.buildinfo
Checksums-Sha256:
 52469be2c1d12427aa35c4c3f1109ca43a51bf56890774993f7bb8831be5 2427 
x2goclient_4.0.5.2-2+deb9u1.dsc
 3b0b6f7d4235b7debbdd23a8d2ba40a33831f0a98b4773f48ffdda6413eaa0d2 19392 
x2goclient_4.0.5.2-2+deb9u1.debian.tar.xz
 fea1d7b4a076dc2a7aeeb08eb48ae555682ed25dcf6b28dfd8ca6855cdbbdbc0 9895 
x2goclient_4.0.5.2-2+deb9u1_source.buildinfo
Files:
 bf3e9fbeafc260e3c54370a6c791dda0 2427 x11 extra x2goclient_4.0.5.2-2+deb9u1.dsc
 82e79762c750b1936d5450c74f6d21e5 19392 x11 extra 
x2goclient_4.0.5.2-2+deb9u1.debian.tar.xz
 4ce8b8a1a3c761bc30c726dea03fe9e8 9895 x11 extra 
x2goclient_4.0.5.2-2+deb9u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3/dtsVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxBHYQAIkQh703jOSC4FNbNoEfR53Zrm5+
QRuRnuZZwFEBTUtwwaBAcOhrUyjpb6RygLBI8bPijeKV6sDdcz6eu8boAFETvkHY
iKFv3tyeagjOUMxrklm4CtD1Ml/wIA9+vcBKcEMPsaSgPUZgODSikAumW+2UAd95
ikoPifv6/DWXnD5KcNITFzl+d64HIWMwlxAOXLOVWuWDlHvnpiB8Cd721X8QyyiR
YGXXkRrPCXPcEoxwrToPRpo9ec8xFAw1fNCHHsvEyC5Ce91qMbVlSAvw/6N6qU1d
JUbVwGtCySC7Qr5K07efJQxubJ9XpZspFfN+8tWX7YmSy2Wh8a7w7HcOZHuUzxDZ
YMNXmmGz9nmFgbsnfeV5U9gV7CyvrLfBQqWR/a4IGkUvbPF3H9lpyA4TuWnKLeSs
Y5ODIspTMazS8ECQer8zWCtxx0Rfr+lMwpP9zEXrgpoRCcpuIjbTwNcbdae4Sx/u
N+zjhaGZbof7ogS2y6jBQGW6c/rxZWYlih2nRbIET+0DMR/ZXAzLXBorbdxYqPj8
OVhdX0z3EVzmeA5qEoU2tcD3zHwM01nY7ltUJ4cZ+QwFvzfOVnXcE/+x402boGzW
io3ziyI0kPj0LeT9oP+jDOfYPBRUL9MAzNkGweMfLPOJbgwLsYKhkFRppo1G0ctt
U+VclJXs/V0T

Bug#947723: devede BD on python-scour which isn't build anymore and isn't in sid/bullseye

[Paul Gevers]

Source: devede
Version: 4.15.0-1
Severity: serious
Tags: ftbfs sid bullseye

Dear maintainer,

Recently the scour package has stopped building the python-scour
package. This is an issue for your package as it
build-depends on it. Please update the building of your package.

Unfortunately the migration software doesn't detected this kind of
situation yet, so your package FTBFS in sid and bullseye.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#937267: Is there any Python3 version of pebl

[Andreas Tille]

Control: tags -1 upstream
Control: forwarded -1 abhiks...@gmail.com

Hi,

Python2 is End Or Life at 1.1.2020 and Debian is about to remove
all Python2 dependencies.  I wonder if there is any Python2 port
of Pebl.  I just found

   https://pypi.org/project/pebl/

which is at version 1.01 while it seems that at googlecode once
was a version 1.0.2 - at least the Debian package is at this
version.  Could you please clarify whether there is some Python3
version of pebl somewhere else?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Is there any Python3 version of pebl

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #937267 [src:pebl] pebl: Python2 removal in sid/bullseye
Added tag(s) upstream.
> forwarded -1 abhiks...@gmail.com
Bug #937267 [src:pebl] pebl: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'abhiks...@gmail.com'.

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

Bug#947720: sollya ftbfs with libfplll6

[Paul Gevers]

Source: sollya
Version: 7.0+ds-3
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your package is part of the libfpll6 transition. I scheduled binNMU's,
but your package fails everywhere. Please have a look.

Paul

https://buildd.debian.org/status/package.php?p=sollya

FAIL: check029.sh
=

An error occurred when calling gnuplot : No such file or directory
FAIL check029.sh (exit status: 1)


Testsuite summary for sollya 7.0

# TOTAL: 32
# PASS:  31
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests-tool/test-suite.log
Please report to sollya-d...@lists.gforge.inria.fr

make[5]: *** [Makefile:708: test-suite.log] Error 1
make[5]: Leaving directory '/<>/_build/tests-tool'
make[4]: *** [Makefile:816: check-TESTS] Error 2
make[4]: Leaving directory '/<>/_build/tests-tool'
make[3]: *** [Makefile:1107: check-am] Error 2
make[3]: Leaving directory '/<>/_build/tests-tool'
make[2]: *** [Makefile:969: check-recursive] Error 1
make[2]: Leaving directory '/<>/_build'
make[1]: *** [Makefile:1259: check] Error 2
make[1]: Leaving directory '/<>/_build'
dh_auto_test: cd _build && make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:12: build-arch] Error 255
dpkg-buildpackage: error: debian/rules build-arch subprocess returned
exit status 2



signature.asc
Description: OpenPGP digital signature

Bug#947718: fplll ftbfs on armel and mipsel (and m68k, powerpc and sh4)

[Paul Gevers]

Source: fplll
Version: 5.3.1-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your package fails to build from source on armel and mipsel. Because it
started a transition, this failure has more widespread impact than just
your package. Please have a look.

Paul
PS: you'll need to do a source-only upload with the next upload,
otherwise the package will not migrate to testing.

https://buildd.debian.org/status/package.php?p=fplll

Tail of log for fplll on armel:

collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:1333: latsieve] Error 1
/usr/bin/ld: ./.libs/libfplll.so: undefined reference to `__atomic_store_8'
/usr/bin/ld: ./.libs/libfplll.so: undefined reference to `__atomic_load_8'
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:1323: fplll] Error 1
make[4]: Leaving directory '/<>/fplll'
make[3]: *** [Makefile:898: all] Error 2
make[3]: Leaving directory '/<>/fplll'
make[2]: *** [Makefile:496: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:384: all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:8: build-arch] Error 255



signature.asc
Description: OpenPGP digital signature

Bug#947717: pbcopper FTBFS on all architectures except x32

[Paul Gevers]

Source: pbcopper
Version: 1.3.0+dfsg-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your package fails to build from source on all buildds except x32. Your
package is involved in the pbbam and htslib transitions and blocking
progress. Please have a look.

Paul

https://buildd.debian.org/status/package.php?p=pbcopper

Tail of log for pbcopper on arm64:

cc -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude -I../include
-Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -MF
'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o.d' -o
'src/25a6634@@pbcopper@sha/align_cssw_ssw.c.o' -c ../src/align/cssw/ssw.c
../src/align/cssw/ssw.c:38:10: fatal error: emmintrin.h: No such file or
directory
   38 | #include 
  |  ^
compilation terminated.
[9/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_LinearAlignment.cpp.o' -c
../src/align/LinearAlignment.cpp
[10/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_BandedChainAlignment.cpp.o' -c
../src/align/BandedChainAlignment.cpp
[11/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_AffineAlignment.cpp.o' -c
../src/align/AffineAlignment.cpp
[12/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_SparseAlignment.cpp.o' -c
../src/align/SparseAlignment.cpp
[13/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_PairwiseAlignment.cpp.o' -c
../src/align/PairwiseAlignment.cpp
[14/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iinclude
-I../include -Isrc/utility -fdiagnostics-color=always -DNDEBUG -pipe
-D_FILE_OFFSET_BITS=64 -std=c++14 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict
-Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ
'src/25a6634@@pbcopper@sha/align_FindSeeds.cpp.o' -MF
'src/25a6634@@pbcopper@sha/align_FindSeeds.cpp.o.d' -o
'src/25a6634@@pbcopper@sha/align_FindSeeds.cpp.o' -c
../src/align/FindSeeds.cpp
[15/114] c++ -Isrc/25a6634@@pbcopper@sha -Isrc -I../src -Iincl

Bug#947076: marked as done (xchat.desktop file has invalid Exec line (at least for KDE))

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 12:55:29 +
with message-id 
and subject line Bug#947076: fixed in xchat 2.8.8-19
has caused the Debian Bug report #947076,
regarding xchat.desktop file has invalid Exec line (at least for KDE)
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.)


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

Dear Maintainer,

since the most recent update, trying to start xchat via the KDE launcher just 
shows an error:

  Error processeing Exec field in /usr/share/applications/xchat.desktop

And indeed that fileld looks suspicious:

  Exec=xchat --existing --url %U"

Notice the unmatched quote.

Kind regards,
Ralf

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

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

Versions of packages xchat depends on:
ii  libc6   2.29-3
ii  libdbus-glib-1-20.110-5
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-1
ii  libglib2.0-02.62.3-2
ii  libgtk2.0-0 2.24.32-4
ii  libgtkspell02.0.16-1.2+b1
ii  libpango-1.0-0  1.42.4-7
ii  libperl5.30 5.30.0-9
ii  libpython2.72.7.17-1
ii  libssl1.1   1.1.1d-2
ii  libtcl8.6   8.6.10+dfsg-1
ii  libx11-62:1.6.8-1
ii  xchat-common2.8.8-18

Versions of packages xchat recommends:
ii  alsa-utils   1.1.9-1
ii  libnotify-bin0.7.8-1
ii  libnotify4   0.7.8-1
pn  xchat-indicator  
ii  xdg-utils1.1.3-1

xchat suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xchat
Source-Version: 2.8.8-19

We believe that the bug you reported is fixed in the latest version of
xchat, 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.
Gianfranco Costamagna  (supplier of updated xchat 
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, 29 Dec 2019 13:35:32 +0100
Source: xchat
Binary: xchat xchat-common
Architecture: source
Version: 2.8.8-19
Distribution: unstable
Urgency: medium
Maintainer: Gianfranco Costamagna 
Changed-By: Gianfranco Costamagna 
Description:
 xchat  - IRC client for X similar to AmIRC
 xchat-common - Common files for X-Chat
Closes: 947076
Changes:
 xchat (2.8.8-19) unstable; urgency=medium
 .
   * Fix unmatched quote (Closes: #947076)
Checksums-Sha1:
 558e4fca64e0c2c65f1b1493e230af8d989671c1 1916 xchat_2.8.8-19.dsc
 5e024441446c6d2db41ce8c495b63a5cf70e2f04 96824 xchat_2.8.8-19.debian.tar.xz
 b6d0c362d2a36ceaf386d9097ba8c9b503f214fa 14197 xchat_2.8.8-19_source.buildinfo
Checksums-Sha256:
 90d43c9444a4853088deb38e2c934ba0bc29b9ef29b6948a6a39bf8c9f43dae4 1916 
xchat_2.8.8-19.dsc
 b79a5cc32a9c31813e82e294e4eeedc20a212c2574466f8aa2c86d68e0da426b 96824 
xchat_2.8.8-19.debian.tar.xz
 5d6425050ece72994938d679374d178660dc917d5f251c6ceecd458d86ace1b3 14197 
xchat_2.8.8-19_source.buildinfo
Files:
 a5f85b09b8464988a4b55d6a2628dfc8 1916 net optional xchat_2.8.8-19.dsc
 a59e94bdf75fd1b6f0b079220bde0437 96824 net optional 
xchat_2.8.8-19.debian.tar.xz
 de17a62edfe1c1c05d21f865a3dd4fd6 14197 net optional 
xchat_2.8.8-19_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl4InboACgkQ808JdE6f
XdkZvRAAjY3L2FhKWpU4Le8dZaWrGfEW8EopurDtO+l4xKcyicsenucFi6jHP3x4
o/2RtNdlEoXktdhJNZtrhrTrColdsxtmacABGEJgQTxnE+jFBN96e7lGeF3Y1VKx
LPOyTpvZM+p23UG7/+BscgYO9q47aMWvxj2Fx13r0K4D+O2OTR45G1u/PEUB9P23
2sQTFSNPbQUzNX5X00is7qLc4xahP83JFawxBlJvfRa81+aN6tW+gMftHJKsEnfp
BiXBN0YN9t1RCfBE6gbct32znaM+uVd6JFqo/9QwDVXlZ0x7g6dAsXLA9BDAV0Xq
TZcLRqBN/9WuOsetp

Bug#944277: marked as done (FTBFS with OCaml 4.08.1 (Error while running external preprocessor))

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 12:51:55 +
with message-id 
and subject line Bug#944277: fixed in hol-light 20190729-3
has caused the Debian Bug report #944277,
regarding FTBFS with OCaml 4.08.1 (Error while running external preprocessor)
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.)


-- 
944277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hol-light
Version: 20190729-2
Severity: serious
Tags: ftbfs
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

hol-light FTBFS with OCaml 4.08.1 because of an error while running
external preprocessor:

  https://buildd.debian.org/status/package.php?p=hol-light


Cheers,

-- 
Stéphane

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: hol-light
Source-Version: 20190729-3

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

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

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated hol-light package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 13:24:09 +0100
Source: hol-light
Architecture: source
Version: 20190729-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Closes: 944277
Changes:
 hol-light (20190729-3) unstable; urgency=medium
 .
   * Team upload
   * Add libnum-ocaml-dev to Build-Depends (Closes: #944277)
   * Bump debhelper compat level to 12
   * Bump Standards-Version to 4.4.1
   * Add Rules-Requires-Root: no
Checksums-Sha1:
 9c03986035286199a702ad81575c5de9afcdc9ee 1815 hol-light_20190729-3.dsc
 3549b50dd5b81a7d93528b544dfebb2cce38859b 10228 
hol-light_20190729-3.debian.tar.xz
Checksums-Sha256:
 f5c9b46d7e897a8a4f040164b4cbcf86139528de867ae2bc8c081a69f9df28fa 1815 
hol-light_20190729-3.dsc
 9e25343e354fca2853de8a81d4608e2f596ef0b9e4d24807f45adfb03196a42a 10228 
hol-light_20190729-3.debian.tar.xz
Files:
 65a1da50813f8b7a6851a97133989782 1815 math optional hol-light_20190729-3.dsc
 b592f153f203989250029bd3d30cb131 10228 math optional 
hol-light_20190729-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQFGBAEBCgAwFiEEbeJOl+yohsxW5iUOIbju8bGJMIEFAl4InNMSHGdsb25kdUBk
ZWJpYW4ub3JnAAoJECG47vGxiTCB9D4IALBs892XYv5ljnLzJXl7DYoRuL24u8JZ
mc8tXVIzvwDPFTysjWkYOYh33bdqlKbxMpIWdxyD4OYx1F133yVOn8X6T2tniaZb
GgW6Lu4vnCvCaNiSyLsKXQls6ob8rUiNXtNUr7ftFZjYmCmhLCU5SkSycqrSkrsq
CbAY3C7BhYngaF9YHz5W8ddYKVv5KfzKwJ/OxI49gyiW2TNULuVkkXlaZUTKvEkR
GdflJ4b30Ud1mAfn7bUllim5UTXzcA196hKVJexX9TH3aCvmzyldB91TqwNpnxTR
ZwONXJFdzpysWeEZd6mjCjsBrXoADe70YVJnPGdcy18ojTg1+/W0Cz4=
=Zn9s
-END PGP SIGNATURE End Message ---

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

[Michael Biebl]

Can you provide a full, verbose debug log:

https://wiki.gnome.org/Projects/NetworkManager/Debugging

Which dhcp client do you use: internal, isc-dhcp-client, ...?



signature.asc
Description: OpenPGP digital signature

Processed: libgtk2.0-0: is deprecated and mostly unmaintained

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 885135
Bug #947713 [libgtk2.0-0] libgtk2.0-0: is deprecated and mostly unmaintained
947713 was not blocked by any bugs.
947713 was not blocking any bugs.
Added blocking bug(s) of 947713: 885752 and 885135

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

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

[Michael Biebl]

Package: network-manager, python-dbusmock
Version: 1.22.2-1
Severity: serious

The latest update of network-manager causes an autopkgtest regression in
python-dbusmock.

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz

==
FAIL: test_eth_and_wifi (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 138, in test_eth_and_wifi
self.assertRegex(out, r'eth0.*\sdisconnected')
AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  -- 
\nwlan0   wifi  unknown  -- \n'

==
FAIL: test_one_eth_connected (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 115, in test_one_eth_connected
self.assertRegex(out, r'eth0.*\sconnected')
AssertionError: Regex didn't match: 'eth0.*\\sconnected' not found in 'DEVICE  
TYPE  STATECONNECTION \neth0ethernet  unknown  -- \n'

==
FAIL: test_one_eth_disconnected (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 109, in test_one_eth_disconnected
self.assertRegex(out, r'eth0.*\sdisconnected')
AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  -- 
\n'

==
FAIL: test_one_wifi_with_accesspoints (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 155, in test_one_wifi_with_accesspoints
self.assertRegex(out, r'wlan0.*\sconnected')
AssertionError: Regex didn't match: 'wlan0.*\\sconnected' not found in 'DEVICE  
TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \n'

==
FAIL: test_remove_connection (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 349, in test_remove_connection
self.assertRegex(self.read_device(), r'wlan0.*\sdisconnected')
AssertionError: Regex didn't match: 'wlan0.*\\sdisconnected' not found in 
'DEVICE  TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \n'

==
FAIL: test_two_eth (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 123, in test_two_eth
self.assertRegex(out, r'eth0.*\sdisconnected')
AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  -- 
\neth1ethernet  unknown  -- \n'

==
FAIL: test_two_wifi_with_accesspoints (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 179, in test_two_wifi_with_accesspoints
self.assertRegex(out, r'wlan0.*\sconnected')
AssertionError: Regex didn't match: 'wlan0.*\\sconnected' not found in 'DEVICE  
TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \nwlan1   wifi  
unknown  -- \n'

==
FAIL: test_wifi_without_access_points (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File "test_networkmanager.py", line 130, in test_wifi_without_access_points
self.assertRegex(out, r'wlan0.*\sconnected')
AssertionError: Regex didn't match: 'wlan0.*\\sconnected' not found in 'DEVICE  
TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \n'

--
Ran 18 tests in 2.971s


Martin, could you have a look if this is a bug in python-dbusmock or a
real regression in NetworkManager.

Regards,
Michael



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

Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-

Bug#944277: actually a bug in camlp5

[Stéphane Glondu]

Le 29/12/2019 à 13:05, Stéphane Glondu a écrit :
>> This is probably caused by a bug in camlp5, caught by a stricter dynamic
>> linker in OCaml 4.08. It is fixed in camlp5 7.10.
>>
>> See https://github.com/camlp5/camlp5/pull/46
> 
> I've updated camlp5 to 7.10, and given back hol-light on amd64. It still
> fails:
> 
> https://buildd.debian.org/status/fetch.php?pkg=hol-light&arch=amd64&ver=20190729-2%2Bb2&stamp=1577619908&raw=0

It turned out it was just the libnum-ocaml-dev dependency that was missing.

Thank you for your hints on this issue!


Cheers,

-- 
Stéphane

Bug#947711: rust-goblin: autopkgtest failure

[Paul Gevers]

Source: rust-goblin
Version: 0.1.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of rust-goblin you added an autopkgtest to your
package, great. However, it fails. I copied some of the output
at the bottom of this report. It seems to me that this package is not
the only package in the rust ecosystem that is failing its new
autopktest, so probably there is something to fix in the generating
code. I am not familiar with the rust ecosystem, hence I'm filing
against the failing package.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=rust-goblin

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-goblin/3801004/log.gz

autopkgtest [07:51:28]: test command1:
/usr/share/cargo/bin/cargo-auto-test goblin 0.1.0 --all-targets
--all-features
autopkgtest [07:51:28]: test command1: [---
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/tmp/tmp.7DyZWmB1C0/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
'-j2', '--target', 'x86_64-unknown-linux-gnu', '--all-targets',
'--all-features'],) {}
   Compiling proc-macro2 v1.0.6
   Compiling unicode-xid v0.2.0
 Running `CARGO_PKG_VERSION_PRE=
CARGO_PKG_HOMEPAGE='https://github.com/alexcrichton/proc-macro2'
CARGO_PKG_DESCRIPTION='A stable implementation of the upcoming new
`proc_macro` API. Comes with an
option, off by default, to also reimplement itself in terms of the upstream
unstable API.
' CARGO_PKG_AUTHORS='Alex Crichton '
CARGO_PKG_VERSION_PATCH=6 CARGO=/usr/bin/cargo CARGO_PKG_VERSION=1.0.6
CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_NAME=proc-macro2
CARGO_MANIFEST_DIR=/tmp/tmp.7DyZWmB1C0/registry/proc-macro2-1.0.6
CARGO_PKG_VERSION_MAJOR=1
CARGO_PKG_REPOSITORY='https://github.com/alexcrichton/proc-macro2'
LD_LIBRARY_PATH='/tmp/tmp.7DyZWmB1C0/target/debug/deps:/usr/lib' rustc
--edition=2018 --crate-name build_script_build
/tmp/tmp.7DyZWmB1C0/registry/proc-macro2-1.0.6/build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
'feature="default"' --cfg 'feature="proc-macro"' -C
metadata=e9cfaf9dfb930ff0 -C extra-filename=-e9cfaf9dfb930ff0 --out-dir
/tmp/tmp.7DyZWmB1C0/target/debug/build/proc-macro2-e9cfaf9dfb930ff0 -L
dependency=/tmp/tmp.7DyZWmB1C0/target/debug/deps --cap-lints warn`
 Running `CARGO_PKG_VERSION_PRE=
CARGO_PKG_HOMEPAGE='https://github.com/unicode-rs/unicode-xid'
CARGO_PKG_DESCRIPTION='Determine whether characters have the XID_Start
or XID_Continue properties according to
Unicode Standard Annex #31.
' CARGO_PKG_AUTHORS='erick.tryzelaar :kwantam
' CARGO_PKG_VERSION_PATCH=0 CARGO=/usr/bin/cargo
CARGO_PKG_VERSION=0.2.0 CARGO_PKG_VERSION_MINOR=2
CARGO_PKG_NAME=unicode-xid
CARGO_MANIFEST_DIR=/tmp/tmp.7DyZWmB1C0/registry/unicode-xid-0.2.0
CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_REPOSITORY='https://github.com/unicode-rs/unicode-xid'
LD_LIBRARY_PATH='/tmp/tmp.7DyZWmB1C0/target/debug/deps:/usr/lib' rustc
--crate-name unicode_xid
/tmp/tmp.7DyZWmB1C0/registry/unicode-xid-0.2.0/src/lib.rs
--error-format=json --json=diagnostic-rendered-ansi,artifacts
--crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 --cfg
'feature="default"' -C metadata=23c2087afcd24636 -C
extra-filename=-23c2087afcd24636 --out-dir
/tmp/tmp.7DyZWmB1C0/target/debug/deps -L
dependency=/tmp/tmp.7DyZWmB1C0/target/debug/deps --cap-lints warn`
   Compiling syn v1.0.11
 Running `CARGO_PKG_VERSION_PRE= CARGO_PKG_HOMEPAGE=
CARGO_PKG_DESCRIPTION='Parser for Rust source code'
CARGO_PKG_AUTHORS='David Tolnay '
CARGO_PKG_VERSION_PATCH=11 CARGO=/usr/bin/cargo CARGO_PKG_VERSION=1.0.11
CARGO_PKG_VERSION_MINOR=0 CARGO_PKG_NAME=syn
CARGO_MANIFEST_DIR=/tmp/tmp.7DyZWmB1C0/registry/syn-1.0.11
CARGO_PKG_VERSION_MAJOR=1
CARGO_PKG_REPOSITORY='https://github.com/dtolnay/syn'
LD_LIBRARY_PATH='/tmp/tmp.7DyZWmB1C0/target/debug/deps:/usr/lib' rustc
--edition=2018 --crate-name build_script_build
/tmp/tmp.7DyZWmB1C0/registry/syn-1.0.11/build.rs --color never
--crate-type bin --emit=dep-info,link -C debuginfo=2 --cfg
'feature="clone-impls"' --cfg 'feature="default"' --cfg
'feature="derive"' --cfg 'feature="parsing"' --cfg 'feature="printing"'
--cfg 'feature="proc-macro"' --cfg 'feature="quote"' -C
metadata=b2da9b12627f9e9c -C extra-filename=-b2da9b12627f9e9c

Bug#947678: marked as done (FTBFS: /usr/bin/ld: cannot find -lGL)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 13:24:40 +0100
with message-id <9649c8b9-b92d-efef-9298-b73991d77...@physik.fu-berlin.de>
and subject line Re: Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL
has caused the Debian Bug report #947678,
regarding FTBFS: /usr/bin/ld: cannot find -lGL
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.)


-- 
947678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlt
Version: 6.18.0-3
Severity: serious
Justification: FTBFS on all archs

Hi! Your package failed to build form source on all archs:



The error seems to be:

g++ -shared -o ../libmltopengl.so factory.o consumer_xgl.o 
filter_glsl_manager.o filter_movit_blur.o filter_movit_convert.o 
filter_movit_crop.o filter_movit_deconvolution_sharpen.o 
filter_movit_diffusion.o filter_movit_flip.o filter_movit_glow.o 
filter_movit_lift_gamma_gain.o filter_movit_mirror.o filter_movit_opacity.o 
filter_movit_rect.o filter_movit_resample.o filter_movit_resize.o 
filter_movit_saturation.o filter_movit_vignette.o filter_movit_white_balance.o 
mlt_movit_input.o transition_movit_luma.o transition_movit_mix.o 
transition_movit_overlay.o -L../../framework -lmlt -lm -Wl,-z,relro -Wl,-z,now 
-Wl,--no-undefined -Wl,--as-needed -Wl,--no-undefined -Wl,--as-needed 
-Wl,--no-undefined -Wl,--as-needed -L../../mlt++ -lmlt++ -lmovit -lepoxy 
-lpthread -lGL -lX11
/usr/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1
make[3]: Leaving directory '/<>/src/modules/opengl'

Thanks for your work, Lisandro.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64, armhf

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
On 12/29/19 1:11 PM, John Paul Adrian Glaubitz wrote:
> I think it's more related to recent changes in libglvnd, see:
> 
>> https://packages.qa.debian.org/libg/libglvnd/news/20191220T191934Z.html
> 
> I'll try a give-back on one of the buildds.

Yep, that helped. I have given back the package on all architectures now:

> https://buildd.debian.org/status/package.php?p=mlt

Adrian

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

Bug#947710: rust-fallible-iterator: autopkgtest failure

[Paul Gevers]

Source: rust-fallible-iterator
Version: 0.2.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of rust-fallible-iterator you added an autopkgtest
to your package, great. However, it fails. I copied some of the output
at the bottom of this report. It seems to me that this package is not
the only package in the rust ecosystem that is failing its new
autopktest, so probably there is something to fix in the generating
code. I am not familiar with the rust ecosystem, hence I'm filing
against the failing package.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=rust-fallible-iterator

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-fallible-iterator/3801013/log.gz
autopkgtest [08:00:46]: test command1:
/usr/share/cargo/bin/cargo-auto-test fallible-iterator 0.2.0
--all-targets --all-features
autopkgtest [08:00:46]: test command1: [---
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/tmp/tmp.jtoofwWrw9/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
'-j2', '--target', 'x86_64-unknown-linux-gnu', '--all-targets',
'--all-features'],) {}
   Compiling fallible-iterator v0.2.0
(/usr/share/cargo/registry/fallible-iterator-0.2.0)
 Running
`CARGO_MANIFEST_DIR=/usr/share/cargo/registry/fallible-iterator-0.2.0
CARGO_PKG_VERSION_PRE= CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_REPOSITORY='https://github.com/sfackler/rust-fallible-iterator'
CARGO_PKG_HOMEPAGE=
LD_LIBRARY_PATH='/tmp/tmp.jtoofwWrw9/target/debug/deps:/usr/lib'
CARGO_PKG_VERSION_PATCH=0 CARGO=/usr/bin/cargo
CARGO_PKG_DESCRIPTION='Fallible iterator traits' CARGO_PKG_VERSION=0.2.0
CARGO_PKG_AUTHORS='Steven Fackler '
CARGO_PKG_NAME=fallible-iterator CARGO_PKG_VERSION_MINOR=2 rustc
--edition=2018 --crate-name fallible_iterator src/lib.rs --color never
--emit=dep-info,link -C debuginfo=2 --test --cfg 'feature="alloc"' --cfg
'feature="default"' --cfg 'feature="std"' -C metadata=a5d055ee2d2c2356
-C extra-filename=-a5d055ee2d2c2356 --out-dir
/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/incremental
-L
dependency=/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/deps
-L dependency=/tmp/tmp.jtoofwWrw9/target/debug/deps -C debuginfo=2
--cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
--remap-path-prefix
/usr/share/cargo/registry/fallible-iterator-0.2.0=/usr/share/cargo/registry/fallible-iterator-0.2.0`
error[E0554]: `#![feature]` may not be used on the stable release channel
  --> src/lib.rs:68:32
   |
68 | #![cfg_attr(feature = "alloc", feature(alloc))]
   |^^

error: aborting due to previous error

For more information about this error, try `rustc --explain E0554`.
error: could not compile `fallible-iterator`.

Caused by:
  process didn't exit successfully:
`CARGO_MANIFEST_DIR=/usr/share/cargo/registry/fallible-iterator-0.2.0
CARGO_PKG_VERSION_PRE= CARGO_PKG_VERSION_MAJOR=0
CARGO_PKG_REPOSITORY='https://github.com/sfackler/rust-fallible-iterator'
CARGO_PKG_HOMEPAGE=
LD_LIBRARY_PATH='/tmp/tmp.jtoofwWrw9/target/debug/deps:/usr/lib'
CARGO_PKG_VERSION_PATCH=0 CARGO=/usr/bin/cargo
CARGO_PKG_DESCRIPTION='Fallible iterator traits' CARGO_PKG_VERSION=0.2.0
CARGO_PKG_AUTHORS='Steven Fackler '
CARGO_PKG_NAME=fallible-iterator CARGO_PKG_VERSION_MINOR=2 rustc
--edition=2018 --crate-name fallible_iterator src/lib.rs --color never
--emit=dep-info,link -C debuginfo=2 --test --cfg 'feature="alloc"' --cfg
'feature="default"' --cfg 'feature="std"' -C metadata=a5d055ee2d2c2356
-C extra-filename=-a5d055ee2d2c2356 --out-dir
/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/deps --target
x86_64-unknown-linux-gnu -C
incremental=/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/incremental
-L
dependency=/tmp/tmp.jtoofwWrw9/target/x86_64-unknown-linux-gnu/debug/deps
-L dependency=/tmp/tmp.jtoofwWrw9/target/debug/deps -C debuginfo=2
--cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro
--remap-path-prefix
/usr/share/cargo/registry/fallible-iterator-0.2.0=/usr/share/cargo/registry/fallible-iterator-0.2.0`
(exit code: 1)




signa

Bug#944277: actually a bug in camlp5

[Stéphane Glondu]

Le 19/12/2019 à 23:39, Christopher Cramer a écrit :
> This is probably caused by a bug in camlp5, caught by a stricter dynamic
> linker in OCaml 4.08. It is fixed in camlp5 7.10.
> 
> See https://github.com/camlp5/camlp5/pull/46

I've updated camlp5 to 7.10, and given back hol-light on amd64. It still
fails:

https://buildd.debian.org/status/fetch.php?pkg=hol-light&arch=amd64&ver=20190729-2%2Bb2&stamp=1577619908&raw=0


Cheers,

-- 
Stéphane

Bug#947709: rust-clang-sys: autopkgtest failure: all tests fail

[Paul Gevers]

Source: rust-clang-sys
Version: 0.28.1-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of rust-clang-sys you added an autopkgtest to
rust-clang-sys, great. However, it fails. I copied some of the output at
the bottom of this report. It seems to me that this package is not the
only package in the rust ecosystem that is failing its new autopktest,
so probably there is something to fix in the generating code. I am not
familiar with the rust ecosystem, hence I'm filing against the failing
package.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=rust-clang-sys

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-clang-sys/3801037/log.gz

autopkgtest [08:12:03]: test command1:
/usr/share/cargo/bin/cargo-auto-test clang-sys 0.28.1 --all-targets
--all-features
autopkgtest [08:12:03]: test command1: [---
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into
/tmp/tmp.BSvGuVoPuG/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=2'] [] ['-j2']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose',
'-j2', '--target', 'x86_64-unknown-linux-gnu', '--all-targets',
'--all-features'],) {}
   Compiling cc v1.0.37
   Compiling libc v0.2.62
 Running `CARGO_PKG_VERSION=1.0.37
CARGO_PKG_HOMEPAGE='https://github.com/alexcrichton/cc-rs'
CARGO_PKG_VERSION_MINOR=0
LD_LIBRARY_PATH='/tmp/tmp.BSvGuVoPuG/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo
CARGO_MANIFEST_DIR=/tmp/tmp.BSvGuVoPuG/registry/cc-1.0.37
CARGO_PKG_VERSION_PRE= CARGO_PKG_NAME=cc CARGO_PKG_DESCRIPTION='A
build-time dependency for Cargo build scripts to assist in invoking the
native
C compiler to compile native C code into a static archive to be linked
into Rust
code.
' CARGO_PKG_REPOSITORY='https://github.com/alexcrichton/cc-rs'
CARGO_PKG_AUTHORS='Alex Crichton '
CARGO_PKG_VERSION_PATCH=37 CARGO_PKG_VERSION_MAJOR=1 rustc --crate-name
cc /tmp/tmp.BSvGuVoPuG/registry/cc-1.0.37/src/lib.rs --color never
--crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
metadata=055b36e8d34bc9b1 -C extra-filename=-055b36e8d34bc9b1 --out-dir
/tmp/tmp.BSvGuVoPuG/target/debug/deps -L
dependency=/tmp/tmp.BSvGuVoPuG/target/debug/deps --cap-lints warn`
 Running `CARGO_PKG_VERSION=0.2.62
CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/libc'
CARGO_PKG_VERSION_MINOR=2
LD_LIBRARY_PATH='/tmp/tmp.BSvGuVoPuG/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo
CARGO_MANIFEST_DIR=/tmp/tmp.BSvGuVoPuG/registry/libc-0.2.62
CARGO_PKG_VERSION_PRE= CARGO_PKG_NAME=libc CARGO_PKG_DESCRIPTION='Raw
FFI bindings to platform libraries like libc.
' CARGO_PKG_REPOSITORY='https://github.com/rust-lang/libc'
CARGO_PKG_AUTHORS='The Rust Project Developers'
CARGO_PKG_VERSION_PATCH=62 CARGO_PKG_VERSION_MAJOR=0 rustc --crate-name
build_script_build /tmp/tmp.BSvGuVoPuG/registry/libc-0.2.62/build.rs
--color never --crate-type bin --emit=dep-info,link -C debuginfo=2 -C
metadata=7f6a065a46d56068 -C extra-filename=-7f6a065a46d56068 --out-dir
/tmp/tmp.BSvGuVoPuG/target/debug/build/libc-7f6a065a46d56068 -L
dependency=/tmp/tmp.BSvGuVoPuG/target/debug/deps --cap-lints warn`
   Compiling glob v0.3.0
 Running `CARGO_PKG_VERSION=0.3.0
CARGO_PKG_HOMEPAGE='https://github.com/rust-lang/glob'
CARGO_PKG_VERSION_MINOR=3
LD_LIBRARY_PATH='/tmp/tmp.BSvGuVoPuG/target/debug/deps:/usr/lib'
CARGO=/usr/bin/cargo
CARGO_MANIFEST_DIR=/tmp/tmp.BSvGuVoPuG/registry/glob-0.3.0
CARGO_PKG_VERSION_PRE= CARGO_PKG_NAME=glob
CARGO_PKG_DESCRIPTION='Support for matching file paths against Unix
shell style patterns.
' CARGO_PKG_REPOSITORY='https://github.com/rust-lang/glob'
CARGO_PKG_AUTHORS='The Rust Project Developers'
CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_MAJOR=0 rustc --crate-name
glob /tmp/tmp.BSvGuVoPuG/registry/glob-0.3.0/src/lib.rs --color never
--crate-type lib --emit=dep-info,metadata,link -C debuginfo=2 -C
metadata=660f73cd021b27bc -C extra-filename=-660f73cd021b27bc --out-dir
/tmp/tmp.BSvGuVoPuG/target/debug/deps -L
dependency=/tmp/tmp.BSvGuVoPuG/target/debug/deps --cap-lints warn`
warning: trait objects without an explicit `dyn` are deprecated
   --> /tmp/tmp.BSvGuVoPuG/registry/glob-0.3.0/src/lib.rs:294:32
|
294 | fn cause(&self) -> Option<&Error> {
|^ help: use `dyn`: `dyn Error`
|
= note: `#[warn(b

Bug#916107: mongodb: MongoDB should not be part of a stable release

[Moritz Mühlenhoff]

On Sat, Nov 16, 2019 at 08:47:13PM -0500, Sandro Tosi wrote:
> On Mon, 10 Dec 2018 11:01:11 +0200 Apollon Oikonomopoulos
>  wrote:
> > Source: mongodb
> > Version: 1:3.4.15-1
> > Severity: serious
> > Justification: Cannot be properly supported
> >
> > MongoDB should not be part of (at least) Buster for the following
> > reasons:
> >
> >  - MongoDB 3.4 will be EOL by June 2019[1], which is way too soon for it
> >to be included in Buster.
> >
> >  - MongoDB 3.6 and 4.0 will be supported longer, but upstream's switch
> >to SSPLv1 complicates matters. As discussed in #915537, we will not
> >be distributing any SSPL-licensed software, and keeping the last
> >AGPL-licensed version (3.6.8 or 4.0.3) without the ability to
> >cherry-pick upstream fixes is not a viable option. (I am currently
> >not considering distributing mongodb in non-free.)
> >
> > I will not request removal immediately, to allow other packages time to
> > adjust their dependencies, but eventually auto-removal will kick in.
> >
> > That said, MongoDB 3.4 will probably remain in sid for as long as it is
> > AGPL-licensed and supported upstream.
> 
> is there a future for mongodb in Debian?

I propose to now remove it from unstable, per 
https://www.mongodb.com/support-policy
support for 3.4 ends in January 2020.

Cheers,
Moritz

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

[John Paul Adrian Glaubitz]

On 12/29/19 12:58 PM, Patrick Matthäi wrote:
>> It pretty much looks like the development files for OpenGL are missing
>> and the linker is complaining it can't find libGL to link against.
> 
> 
> I think this just happens because of the added -latomic flag. See the
> build logs and the changelog from -1 to -3

I don't think so. It builds fine on ia64 after all.

I think it's more related to recent changes in libglvnd, see:

> https://packages.qa.debian.org/libg/libglvnd/news/20191220T191934Z.html

I'll try a give-back on one of the buildds.

Adrian

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

Bug#942972: marked as done (csound: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 12:00:12 +
with message-id 
and subject line Bug#942972: fixed in csound 1:6.13.0~dfsg-2
has caused the Debian Bug report #942972,
regarding csound: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests (the specific reason can be found searching this
source package in
https://people.debian.org/~morph/mass-bug-py2removal_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: csound
Source-Version: 1:6.13.0~dfsg-2

We believe that the bug you reported is fixed in the latest version of
csound, 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.
Felipe Sateler  (supplier of updated csound 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, 28 Dec 2019 18:28:55 -0300
Source: csound
Binary: csound csound-data csound-dbgsym csound-utils csound-utils-dbgsym 
libcsnd-dev libcsnd6-6.0v5 libcsnd6-6.0v5-dbgsym libcsnd6-java 
libcsnd6-java-dbgsym libcsound64-6.0 libcsound64-6.0-dbgsym libcsound64-dev 
libcsound64-doc liblua5.1-luacsnd liblua5.1-luacsnd-dbgsym python3-csound 
python3-csound-dbgsym
Architecture: source all amd64
Version: 1:6.13.0~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Felipe Sateler 
Description:
 csound - powerful and versatile sound synthesis software
 csound-data - data files used by the csound library
 csound-utils - miscellaneous utilities for the Csound system
 libcsnd-dev - development files for Csound -- C++ API
 libcsnd6-6.0v5 - C++ bindings for the Csound API
 libcsnd6-java - Java bindings for the Csound API
 libcsound64-6.0 - main library for Csound
 libcsound64-dev - development files for Csound
 libcsound64-doc - Csound API documentation
 liblua5.1-luacsnd - Lua bindings for the Csound API
 python3-csound - Python bindings for Csound
Closes: 942972
Changes:

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

[Patrick Matthäi]

Am 29.12.2019 um 10:51 schrieb John Paul Adrian Glaubitz:
> Hi!
>
> On 12/29/19 10:36 AM, Patrick Matthäi wrote:
>>> collect2: error: ld returned 1 exit status
>>> make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1
>>> make[3]: Leaving directory '/<>/src/modules/opengl'
>> Yes, I already asked for help here:
>> https://lists.debian.org/debian-arm/2019/12/msg00017.html
> Did you try adding libgl1-dev to Build-Depends in debian/control?
>
> It pretty much looks like the development files for OpenGL are missing
> and the linker is complaining it can't find libGL to link against.


I think this just happens because of the added -latomic flag. See the
build logs and the changelog from -1 to -3


>
> Adrian
>

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Guido Maria Serra]

Il giorno sab, 28/12/2019 alle 15.49 +0100, Axel Beckert ha scritto:
> look at that issue, i.e. Debian bug report #946380?)

sure, sorry... was having some time off keyboard as well :)
...I'll spend some time on it in the upcoming week

best,
GMS

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:47:19 +
with message-id 
and subject line Bug#947129: fixed in x2goclient 4.1.2.1-2+deb10u1
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



pgp_x1bcR5eZ8.pgp
Description: Digitale PGP-Signatur
--- End Message ---
--- Begin Message ---
Source: x2goclient
Source-Version: 4.1.2.1-2+deb10u1

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 18:22:22 +0100
Source: x2goclient
Architecture: source
Version: 4.1.2.1-2+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 947129
Changes:
 x2goclient (4.1.2.1-2+deb10u1) buster; 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:
 df8f3fc84a7b0bd388803200c4057e15f0a3ac32 2524 x2goclient_4.1.2.1-2+deb10u1.dsc
 b880847bce015331fcb2b62bbeda29194068b510 23976 
x2goclient_4.1.2.1-2+deb10u1.debian.tar.xz
 b3987af3dad42f6ff3f6b04bc0424d745dd736f1 13293 
x2goclient_4.1.2.1-2+deb10u1_source.buildinfo
Checksums-Sha256:
 655c0a02eb93c4ac1547969d3eb8d0e57c0a2802748a5b1aec45d152f45dede7 2524 
x2goclient_4.1.2.1-2+deb10u1.dsc
 a47d06f610acc8505c474ba3876f9e3b83c1edceb5124a68d66194083907c545 23976 
x2goclient_4.1.2.1-2+deb10u1.debian.tar.xz
 2667c61d7faec2abb82250a3bf38e22a7e31b13df228bbe32cace1228e245504 13293 
x2goclient_4.1.2.1-2+deb10u1_source.buildinfo
Files:
 d26da1a02c6bfb6f8604c71b3c74 2524 x11 optional 
x2goclient_4.1.2.1-2+deb10u1.dsc
 5bfd9edaefc75fe247e76d9a17b90b7c 23976 x11 optional 
x2goclient_4.1.2.1-2+deb10u1.debian.tar.xz
 8ab6412cffbcd49c133e7465435c9bba 13293 x11 optional 
x2goclient_4.1.2.1-2+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl3/LqcVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxJBYQAKSvOxU8qN7PkOwetsQOubM/e72G
n0ehx5g+49g1tzCyoAaWRKKQGK3GMultnm7OgMQK07I0TUc523pdoo7AHhpDXloR
POhTH2E9JLBjEGkYq6ohrr056Snf7IwvWGyU2vMuvshrpZ2k3ySDbMm4JFk85hhF
OtEsnymcttted+OFIPk01SnaRlQJYODvI94Fkxa9OygnjEOOzzql4vz2icJGT5vl
Rgw4WvEL0QBLZ7fPOmCSsxtnEYiY22o6euRAfQxMZLzoq+V0ZOiwuE0IL0+oMZHa
wJGdzWhkRlX4RYc33QAnIyqhdPs+IGLIhmvT2lEH8+kAku5eAbuHdNTvATIZAP4X
6y+iQQigVadBDK8bwXNyE2cStFwXkQNpXTEKbFmxOhMJpetVLorXtH02qEWkRHju
rzS9PJozXzrEc5kM/0upm/JOQKcR3sho7ISXWpPZK/t7Aru0gI/dyNlhdXOQRXt3
t/TaQPwgvoZLNO4pnBJmR3suNGS+BZQEICAz7k1kL33qNHzIEZ4le44ZDTbajFzO
YABdyR8kc4daYezoWfleAgS+5CKBEiV1e/5dUr8lNjFfuVZypQSPMVg/smKHJsMu
53EfUSrSRYYrnDc/puTNkpiTvLYU4XFBmCuTHJ2x/EgwQYr/4c7aq

Bug#942315: marked as done (tcpdump: Version in oldoldstable is higher than oldstable and stable)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:26:20 +
with message-id <877e2fl6eb.fsf@lusus>
and subject line Closing
has caused the Debian Bug report #942315,
regarding tcpdump: Version in oldoldstable is higher than oldstable and stable
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.)


-- 
942315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcpdump
Version: 4.9.2-1~deb9u1
Severity: serious
Tags: stretch buster

Hi!

With the latest upload to oldoldstable-security, the versions in
oldstable and stable are now lower. This means that upgrades will
not take effect for this package, which will be left built against
libraries and packaging from oldoldstable.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Version: 4.9.3-1~deb10u1

The natural order of things should now be respected:

tcpdump| 4.9.2-1~deb8u1  | oldoldstable | source
tcpdump| 4.9.2-1~deb9u1  | oldstable| source
tcpdump| 4.9.2-1~deb9u1  | oldstable-debug  | source
tcpdump| 4.9.3-1~deb9u1  | oldstable-proposed-updates   | source
tcpdump| 4.9.3-1~deb9u1  | oldstable-proposed-updates-debug | source
tcpdump| 4.9.3-1~deb10u1 | stable   | source
tcpdump| 4.9.3-1~deb10u1 | stable-debug | source
tcpdump| 4.9.3-3 | testing  | source
tcpdump| 4.9.3-3 | unstable | source
tcpdump| 4.9.3-3 | unstable-debug   | source--- End Message ---

Bug#936493: marked as done (exactimage: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:11 +
with message-id 
and subject line Bug#936493: fixed in exactimage 1.0.2-6
has caused the Debian Bug report #936493,
regarding exactimage: 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.)


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

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: exactimage
Source-Version: 1.0.2-6

We believe that the bug you reported is fixed in the latest version of
exactimage, 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.
Sven Eckelmann  (supplier of updated exactimage 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, 30 Sep 2019 08:57:07 +0200
Source: exactimage
Binary: exactimage exactimage-dbgsym libexactimage-perl 
libexactimage-perl-dbgsym python3-exactimage python3-exactimage-dbgsym
Architecture: source amd64
Version: 1.0.2-6
Distribution: experimental
Urgency: medium
Maintainer: Sven Eckelmann 
Changed-By: Sven Eckelmann 
Description:
 exactimage - fast image manipulation programs
 libexactimage-perl - fast image manipulation library (Perl bindings)
 python3-exactimage - fast image manipulation library (Python3 bindings)
Closes: 936493
Changes:
 exactimage (1.0.2-6) experimental; urgency=medium
 .
   * Replace python-exactimage package with python3-exactimage (Closes: #936493)
   * debian/control:
 - Allow build without (fake)root
 - Upgraded to policy 4.4.1, no changes required
Checksums-Sha1:
 35e09ec8fe0ed20fbd8b846579b7cc31b8f43250 2296 exactimage_1.0.2-6.dsc
 f61b5e33ffcec5b8431ff780c6a213cf64e48ae5 30964 exactimage_1.0.2-6.debian.tar.xz

Bug#925729: marked as done (lammps: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:14 +
with message-id 
and subject line Bug#925729: fixed in lammps 20190919+dfsg2-1
has caused the Debian Bug report #925729,
regarding lammps: ftbfs with GCC-9
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.)


-- 
925729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lammps
Version: 0~20181211.gitad1b1897d+dfsg1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/lammps_0~20181211.gitad1b1897d+dfsg1-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/group.cpp:730:21: 
warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', 
declared with attribute warn_unused_result [-Wunused-result]
  730 |   if (me == 0) fread(&ngroup,sizeof(int),1,fp);
  |~^~
/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/group.cpp:742:23: 
warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', 
declared with attribute warn_unused_result [-Wunused-result]
  742 | if (me == 0) fread(&n,sizeof(int),1,fp);
  |  ~^
/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/group.cpp:746:25: 
warning: ignoring return value of 'size_t fread(void*, size_t, size_t, FILE*)', 
declared with attribute warn_unused_result [-Wunused-result]
  746 |   if (me == 0) fread(names[i],sizeof(char),n,fp);
  |~^~~~
[ 31%] Building CXX object 
CMakeFiles/lmp.dir/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/imbalance_group.cpp.o
/usr/bin/c++  -DFFT_FFTW -DLAMMPS_GZIP -DLAMMPS_JPEG -DLAMMPS_MEMALIGN=64 
-DLAMMPS_PNG -DLAMMPS_SMALLBIG -DLAMMPS_VTK -DLMP_HAS_NETCDF -DLMP_MPIIO 
-DLMP_PYTHON -DLMP_USER_OMP -DNC_64BIT_DATA=0x0020 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src" 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gn
 u/openmpi/include -I/usr/include/python2.7 -I/usr/include/voro++ 
-I/usr/include/eigen3 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
-I/usr/include/libxml2 -I/usr/include/jsoncpp -I/usr/include/tcl 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/ASPHERE" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/BODY" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/CLASS2" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/COLLOID" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/src/COMPRESS" 
-I"/<>/lammps-0~20181211.gitad1b1897d+dfsg1/

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:19 +
with message-id 
and subject line Bug#937730: fixed in python-envisage 4.9.0-1
has caused the Debian Bug report #937730,
regarding python-envisage: 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.)


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

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-envisage
Source-Version: 4.9.0-1

We believe that the bug you reported is fixed in the latest version of
python-envisage, 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.
Scott Talbert  (supplier of updated python-envisage 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, 26 Dec 2019 10:56:49 -0500
Source: python-envisage
Binary: python3-envisage
Architecture: source all
Version: 4.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Talbert 
Description:
 python3-envisage - Extensible Application Framework
Closes: 937730
Changes:
 python-envisage (4.9.0-1) unstable; urgency=medium
 .
   * Team Upload.
 .
   [ Ondřej Nový ]
   * Fixed homepage (https)
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/control: Remove ancient X-Python-Version field
   * Remove debian/pycompat, it's not used by any modern Python helper
   * Convert git repository from git-dpm to gbp layout
 .
   [ Scott Talbert ]
   * Remove outdated orig-tar.sh
   * Update to latest upstream release 4.9.0
   * Switch from Python 2 to Python 3 (Closes: #937730)
   * Update and convert d/copyright to DEP5 format
   * Use secure URL in d

Bug#902513: marked as done (openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory))

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:17 +
with message-id 
and subject line Bug#902513: fixed in openturns 1.14-1
has caused the Debian Bug report #902513,
regarding openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory)
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.)


-- 
902513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openturns
Version: 1.10-5
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
DEB_BUILD_OPTIONS:environment=parallel=1
dh build-indep --buildsystem=cmake --with python2,python3 --parallel
   dh_update_autotools_config -i -O--buildsystem=cmake -O--parallel
   dh_autoreconf -i -O--buildsystem=cmake -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
DEB_BUILD_OPTIONS:environment=parallel=1
mkdir -p /<>/debian/tmp/usr/lib/R/site-library
R CMD INSTALL --library=/<>/debian/tmp/usr/lib/R/site-library 
--built-timestamp='Sun, 08 Apr 2018 11:59:13 +' utils/rot_1.4.6.tar.gz
* installing *source* package 'rot' ...
** R
** byte-compile and prepare package for lazy loading

[... snipped ...]

cd /<>/build-python2.7/lib/src && /usr/bin/g++  -DHAVE_CONFIG_H 
-DOT_DLL_EXPORTS -DOT_EXPORTS -I/usr/lib/cmake/hmat/../../../include/hmat 
-I/usr/include/libxml2 -I/<>/lib/include 
-I/<>/build-python2.7/lib/include -I/<>/lib/src 
-I/<>/lib/src/Base -I/<>/lib/src/Base/Algo 
-I/<>/lib/src/Base/Common -I/<>/lib/src/Base/Diff 
-I/<>/lib/src/Base/Diff/Ev3 
-I/<>/lib/src/Base/Experiments 
-I/<>/lib/src/Base/Func 
-I/<>/lib/src/Base/Func/SpecFunc 
-I/<>/lib/src/Base/Geom -I/<>/lib/src/Base/Graph 
-I/<>/lib/src/Base/MetaModel -I/<>/lib/src/Base/Optim 
-I/<>/lib/src/Base/Solver -I/<>/lib/src/Base/Stat 
-I/<>/build-python2.7/lib/src/Base/Stat 
-I/<>/lib/src/Base/Type -I/<>/lib/src/Uncertainty 
-I/<>/lib/src/Uncertainty/Bayesia
 n -I/<>/lib/src/Uncertainty/Model 
-I/<>/lib/src/Uncertainty/Distribution 
-I/<>/lib/src/Uncertainty/Algorithm 
-I/<>/lib/src/Uncertainty/Algorithm/Analytical 
-I/<>/lib/src/Uncertainty/Algorithm/Classification 
-I/<>/lib/src/Uncertainty/Algorithm/MetaModel 
-I/<>/lib/src/Uncertainty/Algorithm/MetaModel/FunctionalChaos 
-I/<>/lib/src/Uncertainty/Algorithm/MetaModel/Kriging 
-I/<>/lib/src/Uncertainty/Algorithm/MetaModel/TensorApproximation 
-I/<>/lib/src/Uncertainty/Algorithm/Optimization 
-I/<>/lib/src/Uncertainty/Algorithm/OrthogonalBasis 
-I/<>/lib/src/Uncertainty/Algorithm/Sensitivity 
-I/<>/lib/src/Uncertainty/Algorithm/Simulation 
-I/<>/lib/src/Uncertainty/Algorithm/Transformation 
-I/<>/lib/src/Uncertainty/Algorithm/Transformation/MarginalTransformation
 -I/<>/lib/src/Uncertainty/Algorit
 hm/Transformation/NatafEllipticalCopula 
-I/<>/lib/src/Uncertainty/Algorithm/Transformation/NatafEllipticalDistribution
 
-I/<>/lib/src/Uncertainty/Algorithm/Transformation/NatafIndependentCopula
 -I/<>/lib/src/Uncertainty/Algorithm/Transformation/Rosenblatt 
-I/<>/lib/src/Uncertainty/Algorithm/Transformation/ProcessTransformation
 -I/<>/lib/src/Uncertainty/Algorithm/WeightedExperiments 
-I/<>/lib/src/Uncertainty/StatTests 
-I/<>/lib/src/Uncertainty/Process  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   -o 
CMakeFiles/OT.dir/Base/Graph/Text.cxx.o -c 
/<>/lib/src/Base/Graph/Text.cxx
[ 36%] Building CXX object lib/src/CMakeFiles/OT.dir/Base/Graph/Graph.cxx.o
cd /<>/build-python2.7/lib/src && /usr/bin/g++  -DHAVE_CONFIG_H 
-DOT_DLL_EXPORTS -DOT_EXPORTS -I/usr/lib/cmake/hmat/../../../include/hmat 
-I/usr/include/libxml2 -I/<>/lib/include 
-I/<>/build-python2.7/lib/include -I/<>/lib/src 
-I/<>/lib/src/Base -I/<>/lib/src/Base/Algo 
-I/<>/lib/src/Base/Common -I/<>/lib/src/Base/Diff 
-I/<>/lib/src/Base/Diff/Ev3 
-I/<>/lib/src/Base/Experiments 
-I/<>/lib/src/Base/Func 
-I/<>/lib/src/Base/Func/SpecFunc 
-I/<>/lib/src/Base/Geom -I/<>/lib/src/Base/Graph 
-I/<>/lib/src/Base/MetaModel -I/<>/lib/src/Base/Optim 
-I/<>/lib/src/Base/Solver -I/<>/lib/src/Base/Stat 
-I/<>/build-python2.7/lib/src/Base/Stat 
-I/<>/lib/src/Base/Type -I/<>/lib/src/Uncertainty 
-I/<>/lib/src/Uncertainty/Bayesia
 n -I/<>/lib/src/Uncertainty/Model 
-I/<>/lib/src/Uncertainty/Distribution 
-I/<>/lib/s

Bug#946734: marked as done (rust-addr2line Build-Depends on librust-fallible-iterator-0.1+default-dev which isn't available)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:21 +
with message-id 
and subject line Bug#946734: fixed in rust-addr2line 0.10.0-1
has caused the Debian Bug report #946734,
regarding rust-addr2line Build-Depends on 
librust-fallible-iterator-0.1+default-dev which isn't available
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.)


-- 
946734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-addr2line
Version: 0.7.0-1
Severity: serious
Tags: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package was never build on a buildd, and was rescheduled 117 days
ago. Since then, the status is BD-Uninstallable. Can you please make sure that
we can actually build packages in Debian?

Please check https://release.debian.org/transitions/html/rust.html, there is at
least one more packages like this one: rust-nitrokey-test. Can/should I
reschedule all the red packages or will that fail anyways?

Paul

https://buildd.debian.org/status/package.php?p=rust-addr2line

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl31WOcACgkQnFyZ6wW9
dQp0Zgf/bA4UCAQxjVR5DtcSOLUqu6EUE95xVachj5+CU2Q9Qaxg9ZNn78vZs0QN
B0gitIAwPrCo+lMN3/asZcQNvpS/XPPo+7qlZkU5/bFlR/ND29wbccz+RdLm7f6k
Air/SA73bX6W2jYpS3Jrt3bqe7HX9T7ta7f3YBd0hCdAAvH1zVs9eyy//YOTRmxi
quU1I9rx5+JVJcw788iqMrof3vtns4CWwxkEMhQENXKF6xC5W43nIHBk/W9Ad6f4
LUGhutDXosX8cFJdV10Geowfxx7B8e1dyEHTOPh/RM20gYxbuiHQUvB0DNd6lyDZ
I7f7D7MbB808tAKmG5iTD+npXMEGSw==
=jGM4
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-addr2line
Source-Version: 0.10.0-1

We believe that the bug you reported is fixed in the latest version of
rust-addr2line, 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.
Wolfgang Silbermayr  (supplier of updated 
rust-addr2line 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, 24 Dec 2019 21:19:40 GMT
Source: rust-addr2line
Binary: librust-addr2line+alloc-dev librust-addr2line+cpp-demangle-dev 
librust-addr2line+default-dev librust-addr2line+object-dev 
librust-addr2line+rustc-demangle-dev librust-addr2line+std-dev 
librust-addr2line+std-object-dev librust-addr2line-dev
Architecture: amd64 source
Version: 0.10.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Wolfgang Silbermayr 
Description: 
 librust-addr2line+alloc-dev - Cross-platform symbolication library - feature 
"alloc"
 librust-addr2line+cpp-demangle-dev - Cross-platform symbolication library - 
feature "cpp_demangle"
 librust-addr2line+default-dev - Cross-platform symbolication library - feature 
"default"
 librust-addr2line+object-dev - Cross-platform symbolication library - feature 
"object"
 librust-addr2line+rustc-demangle-dev - Cross-platform symbolication library - 
feature "rustc-demangle"
 librust-addr2line+std-dev - Cross-platform symbolication library - feature 
"std"
 librust-addr2line+std-object-dev - Cross-platform symbolication library - 
feature "std-object"
 librust-addr2line-dev - Cross-platform symbolication library - Rust source code
Closes: 946734
Changes:
 rust-addr2line (0.10.0-1) unstable; urgency=medium
 .
   * Package addr2line 0.10.0 from crates.io using debcargo 2.4.0
   * Closes: #946734
Checksums-Sha256: 
 42b0f2fe1d875385377c21c37c0dbddb66e4f42380b40715a19b0fca670fba8d 1028 
librust-addr2line+alloc-dev_0.10.0-1_amd64.deb
 25f6d6de98b1163e3d4a125a785ca3fcbd1c48624893e058638c962c668c 1032 
librust-addr2line+cpp-demangle-dev_0.10.0-1_amd64.

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:19 +
with message-id 
and subject line Bug#938051: fixed in python-psycogreen 1.0.1-1
has caused the Debian Bug report #938051,
regarding python-psycogreen: 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.)


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

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-psycogreen
Source-Version: 1.0.1-1

We believe that the bug you reported is fixed in the latest version of
python-psycogreen, 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.
Dmitry Smirnov  (supplier of updated python-psycogreen 
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, 25 Dec 2019 20:26:55 +1100
Source: python-psycogreen
Binary: python3-psycogreen
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 python3-psycogreen - psycopg2 integration with coroutine libraries
Closes: 938051
Changes:
 python-psycogreen (1.0.1-1) unstable; urgency=medium
 .
   * Converted to Python3 (Closes: #938051)
   * New upstream release
   * VCS URLs to Salsa
   * DH to version 12
   * Standards-Version: 4.4.1
   * Testsuite: autopkgtest-pkg-python
Checksums-Sha1:
 8524b1c496811f330d70a50730c4af8eddee0685 2003 python-psycogreen_1.0.1-1.dsc
 9a976a9a3200dc2b267e3dd1c72c76ffe803ae8e 4916 
python-psycogreen_1.0.1.orig.tar.xz
 87bda03bb03d7d8d2525beb4ce7dec53562045ae 2648 
python-psycogreen_1.0.1-1.debian.tar.xz
 ccb2d4a11e2fc7f5f9a2d8a0f6cc7dddf5d3ef5d 6344 
python-psycogreen_1.0.1-1_amd64.bu

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:20 +
with message-id 
and subject line Bug#938184: fixed in python-socksipychain 2.1.0-1
has caused the Debian Bug report #938184,
regarding python-socksipychain: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-socksipychain

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-socksipychain
Source-Version: 2.1.0-1

We believe that the bug you reported is fixed in the latest version of
python-socksipychain, 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.
Federico Ceratto  (supplier of updated 
python-socksipychain 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, 24 Dec 2019 20:36:54 +
Source: python-socksipychain
Binary: python3-socksipychain
Architecture: source all
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: FreedomBox packaging team 

Changed-By: Federico Ceratto 
Description:
 python3-socksipychain - Python SOCKS/HTTP/SSL chaining proxy module
Closes: 938184
Changes:
 python-socksipychain (2.1.0-1) unstable; urgency=medium
 .
   [ James Valleroy ]
   * d/control: Use salsa repo for Vcs
   * Add autopkgtests
 .
   [ Federico Ceratto ]
   * New upstream release
   * Switch to Python 3 (Closes: #938184)
Checksums-Sha1:
 19c27d9f70dd3450904eb277691e7906e1efcfcf 2284 python-socksipychain_2.1.0-1.dsc
 bd31cb8b38cb2cc164aa27a3dec69ae6f54d87a7 19162 
python-socksipychain_2.1.0.orig.tar.gz
 73ed6a44ee7063cf11c0e35ce5c92f7e119d8845 2664 
python-socksipychain_2.1.0-1.debian.tar.xz
 f22e1339d5d35ac64c71ef9cdca

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

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:18 +
with message-id 
and subject line Bug#937697: fixed in python-demgengeo 1.4-1
has caused the Debian Bug report #937697,
regarding python-demgengeo: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-demgengeo

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-demgengeo
Source-Version: 1.4-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Dec 2019 17:49:34 +1100
Source: python-demgengeo
Binary: python3-gengeo python3-gengeo-dbgsym
Architecture: source amd64
Version: 1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Stuart Prescott 
Description:
 python3-gengeo - DEMGenGeo is a library for creating geometry files (Python 3)
Closes: 937697
Changes:
 python-demgengeo (1.4-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version.
   * Update to debhelper-compat (= 12).
   * Drop Python 2 module package (Closes: #937697).
   * Build Python 3 module package.
   * Rename module package to be policy compliant.
   * Update Vcs-* fields.
   * Fix copyright-format/1.0 URL.
   * Add Rules-Requires-Root: no.
   * Use autopkgtest provided tmp directory.
   * Update to Standards-Version 4.4.1.
   * Change priority from extra to optional.
Checksums-Sha1:
 c5b367f567aef778633827832a45c6ba94deff2

Bug#937214: marked as done (openturns: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 11:00:17 +
with message-id 
and subject line Bug#937214: fixed in openturns 1.14-1
has caused the Debian Bug report #937214,
regarding openturns: 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.)


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

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: openturns
Source-Version: 1.14-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 26 Dec 2019 01:40:15 -0500
Source: openturns
Binary: libopenturns-dev libopenturns0.15 libopenturns0.15-dbgsym 
openturns-examples python3-openturns python3-openturns-dbgsym
Architecture: source amd64
Version: 1.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Sandro Tosi 
Description:
 libopenturns-dev - headers and development libraries for OpenTURNS
 libopenturns0.15 - dynamic libraries for OpenTURNS
 openturns-examples - examples of OpenTURNS functionalities
 python3-openturns - Python3 front-end of OpenTURNS (aka TUI)
Closes: 902513 937214
Changes:
 openturns (1.14-1) unstable; urgency=medium
 .
   * Team upload.
   * Drop python2 support; Closes: #937214
   * New upstream release; Closes: #902513
   * Import packaging from upstream, inclusing rename to libopenturns0.15 and
 drop of R bindings
   * debian/watch
 - point to github
Checksums-Sha1:
 f1a5eb46a3d9e7289588930e70436630ae95ed01 2392 opent

Bug#920456: marked as done (i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 10:49:34 +
with message-id 
and subject line Bug#920456: fixed in i2p 0.9.44-2
has caused the Debian Bug report #920456,
regarding i2p: modifies conffiles (policy 10.7.3): /etc/i2p/wrapper.config
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.)


-- 
920456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: i2p
Version: 0.9.38-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files

10.7.3: "[...] The easy way to achieve this behavior is to make the
configuration file a conffile. [...] This implies that the default
version will be part of the package distribution, and must not be
modified by the maintainer scripts during installation (or at any
other time)."

Note that once a package ships a modified version of that conffile,
dpkg will prompt the user for an action how to handle the upgrade of
this modified conffile (that was not modified by the user).

Further in 10.7.3: "[...] must not ask unnecessary questions
(particularly during upgrades) [...]"

If a configuration file is customized by a maintainer script after
having asked some debconf questions, it may not be marked as a
conffile. Instead a template could be installed in /usr/share and used
by the postinst script to fill in the custom values and create (or
update) the configuration file (preserving any user modifications!).
This file must be removed during postrm purge.
ucf(1) may help with these tasks.
See also https://wiki.debian.org/DpkgConffileHandling

In https://lists.debian.org/debian-devel/2012/09/msg00412.html and
followups it has been agreed that these bugs are to be filed with
severity serious.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

  /etc/i2p/wrapper.config


cheers,

Andreas


i2p_0.9.38-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: i2p
Source-Version: 0.9.44-2

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

Debian distribution maintenance software
pp.
Masayuki Hatta  (supplier of updated i2p package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 11:33:06 +0100
Source: i2p
Architecture: source
Version: 0.9.44-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta 
Changed-By: Masayuki Hatta 
Closes: 920456
Changes:
 i2p (0.9.44-2) unstable; urgency=medium
 .
   * Use ucf again - closes: #920456
Checksums-Sha1:
 eeb9501e5f98fbb39c7104eb76df5dd3ef02e448 2194 i2p_0.9.44-2.dsc
 d88572567e61a76c891219baa9d627306358fa31 55956 i2p_0.9.44-2.debian.tar.xz
 f2b94faf77c9ee1e0c239a3597dd3881017f93b0 9654 i2p_0.9.44-2_amd64.buildinfo
Checksums-Sha256:
 60f08e18b36b55ba10ea431880685d93332a9b6047dddec5b6be2b43c0c58227 2194 
i2p_0.9.44-2.dsc
 e4007cf01e198f2d3950b4c2d7176cdc677798924f515fc8bf94cea5c9c1257e 55956 
i2p_0.9.44-2.debian.tar.xz
 d86598a88a6e260778635a714e6a065a4e2acd1e9db0640fa017104120dca9b9 9654 
i2p_0.9.44-2_amd64.buildinfo
Files:
 85e99f24b1bde889cb438e1f6d6c84a6 2194 net optional i2p_0.9.44-2.dsc
 e2682b49287bec23f1d999d38f198cce 55956 net optional i2p_0.9.44-2.debian.tar.xz
 ac59c3b2f78c27a59dce367c000f45a0 9654 net optional i2p_0.9.44-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEZDzS6N3LAPjxWBIb3a4SYm4UEDUFAl4Igi4SHG1oYXR0YUBk
ZWJpYW4ub3JnAAoJEN2uEmJuFBA1LZgP/0hxhpsMbXcW/NthzKShdSmQaFNMbfWR
w714R89JYTvenT0osvPlZUfvXJSZvwR77oJaBEykwhlVBK+jkBYm9b+uGGsj/zwV
PQJh9ggVx3Xm6sz5SCl/3S3uBBouq13+bgMo8nWrohKiPjVwHfQCTEi4PsUzkCwV
SEC3YHLgl8baVxUJx39MWJbRyRO5RxAJ1wSRzGS5H8/u/8hKRhqA6U75xlmfguaf
/3kN7fNynvV6VAesSqu5Es9zhlPb9+v1eDrBArlnb2VeYsOSjaQaoGB1gZFGYr2m
MGUyH4NcWzGj7cIsnO6Puz5j7ns+JAEdYYIJwvK6qXGFE/kJt2aywIj25Ux5NTn3
voHCxSHLx6n9g+cGpNYaLKuvCbTSu2rXbPV2wFiRxjs0C3Hs+zTcuKuhWC6dbvkZ
GUnyuhzIDF9o9Kh

Bug#947053: marked as done (pep8 uses python instead of python2 in the autopkg tests)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 10:04:40 +
with message-id 
and subject line Bug#947053: fixed in pep8 1.7.1-8
has caused the Debian Bug report #947053,
regarding pep8 uses python instead of python2 in the autopkg tests
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.)


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

pep8 uses python instead of python2 in the autopkg tests:

autopkgtest [23:57:13]: test command1: cd "$AUTOPKGTEST_TMP" ; python -c "import
pep8; print pep8.__version__"
autopkgtest [23:57:13]: test command1: [---
bash: python: command not found
autopkgtest [23:57:13]: test command1: ---]
autopkgtest [23:57:13]: test command1:  - - - - - - - - - - results - - - - - -
- - - -
command1 FAIL non-zero exit status 127
autopkgtest [23:57:14]: test command1:  - - - - - - - - - - stderr - - - - - - -
- - -
bash: python: command not found
--- End Message ---
--- Begin Message ---
Source: pep8
Source-Version: 1.7.1-8

We believe that the bug you reported is fixed in the latest version of
pep8, 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.
Andrej Shadura  (supplier of updated pep8 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, 29 Dec 2019 10:59:38 +0100
Source: pep8
Architecture: source
Version: 1.7.1-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 947053
Changes:
 pep8 (1.7.1-8) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * Use python2 instead of python on autopkgtest (Closes: #947053)
Checksums-Sha1:
 88208da1ba37f48b89931dff38e6a874acfd688a 1914 pep8_1.7.1-8.dsc
 1ee4eed2aabcdd6ab5efe94c4cbffd98a2915d04 6024 pep8_1.7.1-8.debian.tar.xz
Checksums-Sha256:
 0385d7f4f4cacb87da346b89b1921566c87bce9c4a0a9e3817950601b0bd64a2 1914 
pep8_1.7.1-8.dsc
 11811abda8a93689f53c3f8a7b73bd4b5d116883d3c48d601692ff16dcce58e4 6024 
pep8_1.7.1-8.debian.tar.xz
Files:
 bbfe95bf81a44aa31cf6a04572d6c3e2 1914 python optional pep8_1.7.1-8.dsc
 b571e59387d36284aa7571703f29a3c0 6024 python optional 
pep8_1.7.1-8.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl4IeUEACgkQXkCM2RzY
OdLuhAf/d2qG9wxQl/79y///q5mI1A+x8QtcQOg3V2kCKxJPNAWPhPDP77eVDUcR
Et2LFvn912QkNBhOnm7WqMV2njQrTsxoc5B3eWOWTR/KK37auhVcIhSbMYU8Ewp5
G0Ef0dfv9D9avw7WtpEvmOFuhr2ZhLs9OGCx41nIxmuQJu+9aL7RFf7fFXAOeFWH
qi9tGJZK8NNbkYtUsN7zCeWBzy5hT7lf8p07/0F7PaSsJq4JKY19d8GU5RBW+9Im
SBHp4lBKhVv0I5oKe87kUgbkNM9z4/QgRuf2YkYX198FKg0ZKmE0zNhrl3MXae6Y
HqVNKoMYcAKkVIefUo59GQeN4AGalg==
=rvZS
-END PGP SIGNATURE End Message ---

Processed: reassign 947060 to network-manager, forcibly merging 947003 947060

[Debian Bug Tracking System]

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

> reassign 947060 network-manager
Bug #947060 [resolvconf] resolvconf: dots stipped from dhcp search domain
Bug reassigned from package 'resolvconf' to 'network-manager'.
No longer marked as found in versions resolvconf/1.81.
Ignoring request to alter fixed versions of bug #947060 to the same values 
previously set
> forcemerge 947003 947060
Bug #947003 {Done: Michael Biebl } [network-manager] 
network-manager: Incorrect update of /etc/resolv.conf, bad search field
Bug #947060 [network-manager] resolvconf: dots stipped from dhcp search domain
Severity set to 'important' from 'serious'
Marked Bug as done
Marked as fixed in versions network-manager/1.22.0-2.
Marked as found in versions network-manager/1.22.0-1.
Merged 947003 947060
> thanks
Stopping processing here.

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

Bug#947263: marked as done (python3-iniparse: missing Breaks+Replaces: python-iniparse)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 09:52:43 +
with message-id 
and subject line Bug#947263: fixed in python-iniparse 0.4-3
has caused the Debian Bug report #947263,
regarding python3-iniparse: missing Breaks+Replaces: python-iniparse
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.)


-- 
947263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-iniparse
Version: 0.4-2.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../python3-iniparse_0.4-2.3_all.deb ...
  Unpacking python3-iniparse (0.4-2.3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-iniparse_0.4-2.3_all.deb (--unpack):
   trying to overwrite '/usr/share/doc-base/python-iniparse', which is also in 
package python-iniparse 0.4-2.2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-iniparse_0.4-2.3_all.deb


cheers,

Andreas


python-iniparse=0.4-2.2_python3-iniparse=0.4-2.3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-iniparse
Source-Version: 0.4-3

We believe that the bug you reported is fixed in the latest version of
python-iniparse, 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.
Andrej Shadura  (supplier of updated python-iniparse 
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, 29 Dec 2019 10:43:25 +0100
Source: python-iniparse
Architecture: source
Version: 0.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Andrej Shadura 
Closes: 947263
Changes:
 python-iniparse (0.4-3) unstable; urgency=medium
 .
   * Maintain under DPMT.
   * Fix the copyright file.
   * Take over some files shipped in python-iniparse (Closes: #947263).
Checksums-Sha1:
 9d4407157d42503f4ed29320cbb2eeb5e24e202e 1872 python-iniparse_0.4-3.dsc
 38ec610501c39d559b2f911884728f9d6389b41b 11104 
python-iniparse_0.4-3.debian.tar.xz
Checksums-Sha256:
 c3c59e90a95cdc2c6adfe4c9239cd84a5df9debbb7e68a8bd778a76ee06f4733 1872 
python-iniparse_0.4-3.dsc
 3ffd176838bbca8bb73d5419cb21ca0c1489996b33de524aa16a938d9a2b5c8d 11104 
python-iniparse_0.4-3.debian.tar.xz
Files:
 662f7c888ccbad687c43273655c25f35 1872 python optional python-iniparse_0.4-3.dsc
 23faace0151ca5a9ee0780584c416f97 11104 python optional 
python-iniparse_0.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl4Idb4ACgkQXkCM2RzY
OdLgjAf/TarbOE1sNP83BIX8tyEeO+BvvNImnSyq1sVdzwUGwHOCJ/3c9MyC9Aem
f22hFOFM5cLb4dE1GHODVfbDWIDBF8eDrE/ygERy/S0asD27tKjbtoZ6lBlLtHED
GKq3I1lT5Q/er1XVdNhnGu9vqYvtwG6UdMZJqALdVY0MeQV80icPOSonpYE2/gFP
4ovVMSi4YfIOh/XIUEYgg3HXV1EaXghmvVXPCfQMnG0Rbm6uVSEuLtKvJ8ERD0l/
njkkur7Wbhh5POAqEEdMdJpN1zkF7IHWSyN+o6hdZfpiDbDiw0CZhnWaCi8vB/dk
iyfFUOgYhPyOBH3fP3AN6bJAZnImgg==
=7Uh/
-END PGP SIGNATURE End Message ---

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

[John Paul Adrian Glaubitz]

Hi!

On 12/29/19 10:36 AM, Patrick Matthäi wrote:
>> collect2: error: ld returned 1 exit status
>> make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1
>> make[3]: Leaving directory '/<>/src/modules/opengl'
> 
> Yes, I already asked for help here:
> https://lists.debian.org/debian-arm/2019/12/msg00017.html

Did you try adding libgl1-dev to Build-Depends in debian/control?

It pretty much looks like the development files for OpenGL are missing
and the linker is complaining it can't find libGL to link against.

Adrian

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

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

[Patrick Matthäi]

Hi

Am 29.12.2019 um 01:58 schrieb Lisandro Damián Nicanor Pérez Meyer:
> Source: mlt
> Version: 6.18.0-3
> Severity: serious
> Justification: FTBFS on all archs
>
> Hi! Your package failed to build form source on all archs:
>
> 
>
> The error seems to be:
>
> g++ -shared -o ../libmltopengl.so factory.o consumer_xgl.o 
> filter_glsl_manager.o filter_movit_blur.o filter_movit_convert.o 
> filter_movit_crop.o filter_movit_deconvolution_sharpen.o 
> filter_movit_diffusion.o filter_movit_flip.o filter_movit_glow.o 
> filter_movit_lift_gamma_gain.o filter_movit_mirror.o filter_movit_opacity.o 
> filter_movit_rect.o filter_movit_resample.o filter_movit_resize.o 
> filter_movit_saturation.o filter_movit_vignette.o 
> filter_movit_white_balance.o mlt_movit_input.o transition_movit_luma.o 
> transition_movit_mix.o transition_movit_overlay.o -L../../framework -lmlt -lm 
> -Wl,-z,relro -Wl,-z,now -Wl,--no-undefined -Wl,--as-needed -Wl,--no-undefined 
> -Wl,--as-needed -Wl,--no-undefined -Wl,--as-needed -L../../mlt++ -lmlt++ 
> -lmovit -lepoxy -lpthread -lGL -lX11
> /usr/bin/ld: cannot find -lGL
> collect2: error: ld returned 1 exit status
> make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1
> make[3]: Leaving directory '/<>/src/modules/opengl'

Yes, I already asked for help here:
https://lists.debian.org/debian-arm/2019/12/msg00017.html

Processed: Re: Processed: Tag

[Debian Bug Tracking System]

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

> tag 947678 + help
Bug #947678 [src:mlt] FTBFS: /usr/bin/ld: cannot find -lGL
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#947678: Processed: Tag

[Patrick Matthäi]

tag 947678 + help
thanks

Am 29.12.2019 um 02:18 schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
>
>> tag 947678 ftbfs
> Bug #947678 [src:mlt] FTBFS: /usr/bin/ld: cannot find -lGL
> Added tag(s) ftbfs.
>> thanks
> Stopping processing here.
>
> Please contact me if you need assistance.