date:20191230

Processing control commands:

> tags -1 - moreinfo
Bug #942428 [release.debian.org] transition: gssdp/gupnp
Removed tag(s) moreinfo.
> tags -1 confirmed
Bug #942428 [release.debian.org] transition: gssdp/gupnp
Added tag(s) confirmed.
> block -1 by 947805
Bug #942428 [release.debian.org] transition: gssdp/gupnp
942428 was not blocked by any bugs.
942428 was not blocking any bugs.
Added blocking bug(s) of 942428: 947805

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

Processed: block 947486 with 947617

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

> block 947486 with 947617
Bug #947486 [src:golang-github-containers-image] 
golang-github-containers-image: FTBFS with test failures
947486 was not blocked by any bugs.
947486 was not blocking any bugs.
Added blocking bug(s) of 947486: 947617
> thanks
Stopping processing here.

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

Bug#947816: GeoLite2 databases are now non-free

2019-12-30 Thread Harlan Lieberman-Berg

Package: geoipupdate
Severity: serious

Hello maintainer,

Unfortunately, it seems that MaxMind have changed their policies on GeoLite2 
databases such that they now require a license key.  In addition (and more 
critically), they are no longer licensed under a Creative Commons BY-SA 
license, and now are under a custom EULA.

I reviewed the EULA (https://www.maxmind.com/en/geolite2/eula) and, while I am 
neither an attorney nor a debian-legal faux-counsel, the agreement seems to 
violate the DFSG in several regards.

First, it places restrictions on fields of endeavor -- specifically, that you 
may not use the data for Fair Credit Reporting Act purposes, including 
determining whether a person may be granted credit, eligible for insurance, for 
employment purposes, or any other purpose governed by the FCRA.

Second, you are no longer permitted to redistribute the data except by binding 
them to the EULA.

Third, you are required to check in with MaxMind regularly and destroy old 
versions of the dataset within 30 days.  This seems to violate several 
long-standing interpretations of the DFSG including the desert island test and 
the tentacles of evil test.

Based on this license change, it seems to me that geoipupdate can no longer be 
in main.  Contrib may be a suitable home, however?

Sincerely,

--
Harlan Lieberman-Berg
~hlieberman

Bug#936508: marked as done (fdb: Python2 removal in sid/bullseye)

Your message dated Tue, 31 Dec 2019 04:19:14 +
with message-id 
and subject line Bug#936508: fixed in fdb 2.0.0-1.1
has caused the Debian Bug report #936508,
regarding fdb: 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.)


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

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: fdb
Source-Version: 2.0.0-1.1

We believe that the bug you reported is fixed in the latest version of
fdb, 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.
Sandro Tosi  (supplier of updated fdb 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 22:53:40 -0500
Source: fdb
Architecture: source
Version: 2.0.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Russell Stuart 
Changed-By: Sandro Tosi 
Closes: 936508
Changes:
 fdb (2.0.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936508
Checksums-Sha1:
 5e01722d701463d86fd09b864125682f869874eb 1884 fdb_2.0.0-1.1.dsc
 a654d9609a87a536c9c38fb0752dc9ba23eb2d04 4812 fdb_2.0.0-1.1.debian.tar.xz
 cee8ccb676d9d19869135b418732a37b7ea433c4 5619 fdb_2.0.0-1.1_source.buildinfo
Checksums-Sha256:
 6a4f89f70be9eb4b1426eb4070a8b51817990caf199c2e56855b47bb8f8f992c 1884 
fdb_2.0.0-1.1.dsc
 c06d05319117d2f3b9e2b5b3ccedc56d7cef3fc910215e899ca2b30089c5a326 4812 
fdb_2.0.0-1.1.debian.tar.xz
 3119d14557714613a89450a22595b0736655bca55ba30c79e8de4b43f1573a35 5619 
fdb_2.0.0-1.1_source.buildinfo
Files:
 6d55c64b2fa2bd8e14036361f255d389 1884 python optional fdb_2.0.0-1.1.dsc
 d3ef351f5d3f625a7c6b6340b96d1a85 4812 python optional 
fdb_2.0.0-1.1.

Bug#936508: fdb: diff for NMU version 2.0.0-1.1

Control: tags 936508 + patch


Dear maintainer,

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

Regards.

diff -Nru fdb-2.0.0/debian/changelog fdb-2.0.0/debian/changelog
--- fdb-2.0.0/debian/changelog	2019-02-07 05:43:34.0 -0500
+++ fdb-2.0.0/debian/changelog	2019-12-30 22:53:40.0 -0500
@@ -1,3 +1,10 @@
+fdb (2.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936508
+
+ -- Sandro Tosi   Mon, 30 Dec 2019 22:53:40 -0500
+
 fdb (2.0.0-1) unstable; urgency=low
 
   * New upstream version
diff -Nru fdb-2.0.0/debian/control fdb-2.0.0/debian/control
--- fdb-2.0.0/debian/control	2019-02-07 05:43:34.0 -0500
+++ fdb-2.0.0/debian/control	2019-12-30 22:48:38.0 -0500
@@ -4,31 +4,14 @@
 Priority: optional
 Build-Depends: debhelper (>= 9)
 Build-Depends-Indep:
-  python-all (>= 2.7), python3-all,
-  python-sphinx, python-sphinx-bootstrap-theme,
-  python-setuptools, python3-setuptools,
-  python-future,
+  python3-all,
+  python3-sphinx, python3-sphinx-bootstrap-theme,
+  python3-setuptools,
   libjs-sphinxdoc,
   dh-python
 Standards-Version: 3.9.8
-X-Python-Version: >= 2.7
-X-Python3-Version: >= 3.4
 Homepage: https://pypi.python.org/pypi/fdb/
 
-Package: python-fdb
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}, libfbclient2, python-future
-Suggests: python-fdb-doc
-Description: Python2 DB-API driver for Firebird
- FDB is a Python library package that implements Python Database API
- 2.0-compliant support for the open source relational database Firebird®.
- In addition to the minimal feature set of the standard Python DB API,
- FDB also exposes nearly the entire native client API of the database
- engine.  This version installs the Python2 byte code.
- .
- FDB is a replacement for python-kinterbasdb, which is no longer
- maintained by upstream.
-
 Package: python3-fdb
 Architecture: all
 Depends: ${python3:Depends}, ${misc:Depends}, libfbclient2
@@ -47,7 +30,7 @@
 Architecture: all
 Section: doc
 Depends: ${misc:Depends}, libjs-sphinxdoc
-Recommends: python-fdb
+Recommends: python3-fdb
 Description: Python DB-API driver for Firebird documentation
  FDB is a Python library package that implements Python Database API
  2.0-compliant support for the open source relational database Firebird®.
diff -Nru fdb-2.0.0/debian/rules fdb-2.0.0/debian/rules
--- fdb-2.0.0/debian/rules	2019-02-07 05:43:34.0 -0500
+++ fdb-2.0.0/debian/rules	2019-12-30 22:53:20.0 -0500
@@ -8,7 +8,7 @@
 
 %:
 	#dh $@ -v --with python2,python3,sphinxdoc --buildsystem=pybuild
-	dh "$@" -v --with python2,python3 --buildsystem=pybuild
+	dh "$@" -v --with python3 --buildsystem=pybuild
 
 get-orig-source:
 	uscan --force-download
@@ -16,7 +16,7 @@
 override_dh_auto_build: $(PYBUILD_NAME).egg-info.orig
 	dh_auto_build
 	rm -rf docs
-	$(MAKE) --directory sphinx html
+	$(MAKE) --directory sphinx html SPHINXBUILD=/usr/share/sphinx/scripts/python3/sphinx-build
 	rm -rf html
 	mv docs html

Processed: fdb: diff for NMU version 2.0.0-1.1

Processing control commands:

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

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

Bug#947812: python3-socksipychain: missing Breaks+Replaces: python-socksipychain

2019-12-30 Thread Andreas Beckmann

Package: python3-socksipychain
Version: 2.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package python3-socksipychain.
  Preparing to unpack .../python3-socksipychain_2.1.0-1_all.deb ...
  Unpacking python3-socksipychain (2.1.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-socksipychain_2.1.0-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/sockschain', which is also in package 
python-socksipychain 2.0.15-2
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-socksipychain_2.1.0-1_all.deb


cheers,

Andreas


python-socksipychain=2.0.15-2_python3-socksipychain=2.1.0-1.log.gz
Description: application/gzip

Bug#946415: marked as done (rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which doesn't exist)

Your message dated Tue, 31 Dec 2019 01:38:40 +
with message-id 
and subject line Bug#946415: fixed in rust-cargo 0.41.0-1
has caused the Debian Bug report #946415,
regarding rust-cargo Build-Depends on librust-crates-io-0.25+default-dev which 
doesn't exist
to be marked as done.

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

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


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on librust-crates-io-0.25+default-dev but that
package doesn't exist.

Paul

- -- 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-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3tXnsACgkQnFyZ6wW9
dQrJEAgArOfLFxtWX9VX9pCwEY7IANOd7+n2fzBHBSEpydXsryT3WxJGhYihrzrY
+XFKFSoKqNMzuEhR9hyKsjLfiCIn8QiEhrftdGEXHWaHvWHw9VU/f+FCCFfDl3n9
Hho655KiAIoQbOI1tuosN/q9bY0CV+zQOb5z17eAEIt0Aj3V0++uQIV5pJk96yU5
+0FZptGyLVv1waGJ3gaBIK1E2bi0XZyO43LnF93BpH6l1c4FeD4dWetTe/IdvD8N
itjowp1e7KiOCxiZCRk4BSU4d6xkeKOMCMQrUdtBN5ZfBXgJRGQaBG69ck5TG5js
YTtiQEp4fy4/jglgEmkIoazcvLUNnA==
=pbb/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rust-cargo
Source-Version: 0.41.0-1

We believe that the bug you reported is fixed in the latest version of
rust-cargo, 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.
Ximin Luo  (supplier of updated rust-cargo 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, 31 Dec 2019 01:18:37 +
Source: rust-cargo
Architecture: source
Version: 0.41.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Ximin Luo 
Closes: 946415
Changes:
 rust-cargo (0.41.0-1) unstable; urgency=medium
 .
   * Package cargo 0.41.0 from crates.io using debcargo 2.4.0
   * Closes: #946415
Checksums-Sha1:
 be541bda5895b4fa88185602f83232620875b4be 5301 rust-cargo_0.41.0-1.dsc
 29be1ad41eff4ff18147e6d1ba65bb0d928d24b6 1070528 rust-cargo_0.41.0.orig.tar.gz
 3e31949635e76f1e5bc0da42b8e47bf39bdd09a1 4636 rust-cargo_0.41.0-1.debian.tar.xz
 1cf5fb070c4662befde8655f765dacef65548f76 6563 
rust-cargo_0.41.0-1_source.buildinfo
Checksums-Sha256:
 dd5e73984b337a1461f3219f67d138e6053e474663512aa55c7496ed907dba4e 5301 
rust-cargo_0.41.0-1.dsc
 2737475f76ce9681e230a4e5cb2476fb133875f28fd84a834a6b5aefd83d3741 1070528 
rust-cargo_0.41.0.orig.tar.gz
 2dda408f4350dd89d68b5457a1b5f338b14ba6f371f93bdad7c959a83e5c5ff4 4636 
rust-cargo_0.41.0-1.debian.tar.xz
 1d721542bdc2a21af2bb0aee8f800d3086ca59fd7df7c845445531e687d2ed0c 6563 
rust-cargo_0.41.0-1_source.buildinfo
Files:
 7f0ba9cab09f079bdf5f0f5217275b74 5301 rust optional rust-cargo_0.41.0-1.dsc
 b38a83fec4a9cc03f6e282116449a7c6 1070528 rust optional 
rust-cargo_0.41.0.orig.tar.gz
 fb82c11369130f7cfbf2f619f396067c 4636 rust optional 
rust-cargo_0.41.0-1.debian.tar.xz
 91fc6ae03ff9b3f9fee6b870e9913135 6563 rust optional 
rust-cargo_0.41.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCXgqh8AAKCRDrH8jaRfsp
MF7YAQCmHcOIkBZr3I+usLj47Q0Umy7yOY+P3vh6q7OSIqiRdAEAmRp26oiYBe5O
qe5/o8gKfL6pewdXqf7aGLBiBV7dMQs=
=PyKK
-END PGP SIGNATURE End Message ---

Bug#947810: gvm-libs: FTBFS during indep-only build

2019-12-30 Thread Andreas Beckmann

Source: gvm-libs
Version: 11.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

gvm-libs/experimental FTBFS during the indep-only build:

[...]
   dh_auto_test -i
cd obj-x86_64-linux-gnu && make -j3 test ARGS\+=-j3
make[1]: Entering directory '/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j3
Test project /build/gvm-libs-11.0.0/obj-x86_64-linux-gnu
Start 1: testhosts
Could not find executable 
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
Looked in the following places:
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Release/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Release/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Debug/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Debug/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/MinSizeRel/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/MinSizeRel/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/RelWithDebInfo/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/RelWithDebInfo/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Deployment/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Deployment/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Development/test-hosts
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Development/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Release/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Release/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Debug/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Debug/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/MinSizeRel/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/MinSizeRel/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/RelWithDebInfo/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/RelWithDebInfo/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Deployment/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Deployment/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Development/test-hosts
build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/Development/test-hosts
Unable to find executable: 
/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu/tests/test-hosts
1/1 Test #1: testhosts ***Not Run   0.00 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.01 sec

The following tests FAILED:
  1 - testhosts (Not Run)
Errors while running CTest
make[1]: *** [Makefile:155: test] Error 8
make[1]: Leaving directory '/build/gvm-libs-11.0.0/obj-x86_64-linux-gnu'
dh_auto_test: cd obj-x86_64-linux-gnu && make -j3 test ARGS\+=-j3 returned exit 
code 2
[...]


Andreas


gvm-libs_11.0.0-1_indep.log.gz
Description: application/gzip

Processed: found 934687 in 0.5.4-1, tagging 947712, found 947712 in 0.18.3-2, tagging 946926 ..., tagging 947757 ...

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

> found 934687 0.5.4-1
Bug #934687 {Done: Debian FTP Masters } 
[heudiconv] heudiconv, indirectly build-depends on cruft package, needs to 
migrate to python 3
Marked as found in versions heudiconv/0.5.4-1 and reopened.
> tags 947712 + sid bullseye
Bug #947712 [network-manager, python-dbusmock] autopkgtest regressions in  
python-dbusmock with newer network-manager 1.22.2-1
Added tag(s) sid and bullseye.
> found 947712 0.18.3-2
Bug #947712 [network-manager, python-dbusmock] autopkgtest regressions in  
python-dbusmock with newer network-manager 1.22.2-1
There is no source info for the package 'network-manager' at version '0.18.3-2' 
with architecture ''
There is no source info for the package 'python-dbusmock' at version '0.18.3-2' 
with architecture ''
Unable to make a source version for version '0.18.3-2'
Marked as found in versions 0.18.3-2.
> tags 946926 =
Bug #946926 [ftp.debian.org] RM: pysparse -- RoQA; python2-only; no upstream 
release in 8+ years; python3-sparse exists
Removed tag(s) bullseye and sid.
> found 947757 1.1.1-2
Bug #947757 [src:pysparse] pysparse: should this package be removed?
Marked as found in versions pysparse/1.1.1-2.
> tags 947757 + sid bullseye
Bug #947757 [src:pysparse] pysparse: should this package be removed?
Added tag(s) sid and bullseye.
> tags 947794 + experimental
Bug #947794 [src:python-apt] python-apt: autopkgtest fails on deprecation 
*warnings* to stderr
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#947805: Please port to gupnp/gssdp 1.2

2019-12-30 Thread Laurent Bigonville

Package: upnp-router-control
Version: 0.2-1.2
Severity: serious
Tags: sid buster
Forwarded: https://bugs.launchpad.net/upnp-router-control/+bug/1857942

Hello,

We are planning to upload gupnp/gssdp 1.2 to debian unstable.

Unfortunately upnp-router-control FTBFS with this version and needs to
be ported.

Could you please have a look at porting it to the latest version? I've
opened a bug upstream for that as well:
https://bugs.launchpad.net/upnp-router-control/+bug/1857942

Kind regards,

Laurent Bigonville

-- System Information:
Debian Release: bullseye/sid
  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 5.4.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Processed: bug 947237 is forwarded to https://gitlab.gnome.org/GNOME/gnome-software/issues/880

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

> forwarded 947237 https://gitlab.gnome.org/GNOME/gnome-software/issues/880
Bug #947237 [gnome-software-plugin-snap] gnome-software: Crashes on click over 
any software icon
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-software/issues/880'.
> 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#937794: marked as done (python-gnupg: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 23:34:15 +
with message-id 
and subject line Bug#937794: fixed in python-gnupg 0.4.5-2
has caused the Debian Bug report #937794,
regarding python-gnupg: 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.)


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

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-gnupg
Source-Version: 0.4.5-2

We believe that the bug you reported is fixed in the latest version of
python-gnupg, 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-gnupg 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 18:23:06 -0500
Source: python-gnupg
Architecture: source
Version: 0.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Elena Grandi 
Changed-By: Sandro Tosi 
Closes: 937794 946897
Changes:
 python-gnupg (0.4.5-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Elena Grandi ]
   * Remove python2 version; Closes: #937794
   * Bump compat to 12
 .
   [ Sandro Tosi ]
   * debian/patches/make-tests-more-verbose.patch
 - make tests a bit more verbose, initial patch by Matthias Klose;
   Closes: #946897
Checksums-Sha1:
 b1b47c862ecbf2cf6cb1481efa52261ebe4a1f08 2033 python-gnupg_0.4.5-2.dsc
 439dcfffc084aa5a144367919beac0ecad34add0 7480 
python-gnupg_0.4.5-2.debian.tar.xz
 3b1ec57fb49152058ba7ad6b34d4335539d2348f 10340 
python-gnupg_0.4.5-2_source.buildinfo
Checksums-Sha256:
 3fe52d3aff364dfa5fb982deefb3065de552ac79a61ac79b836cccdaee92ccd4 2033 
python-gnupg_0.4.5-2.dsc

Bug#947058: marked as done (pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x))

Your message dated Mon, 30 Dec 2019 23:05:07 +
with message-id 
and subject line Bug#947058: fixed in pygalmesh 0.5.0-3
has caused the Debian Bug report #947058,
regarding pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)
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.)


-- 
947058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygalmesh
Version: 0.5.0-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: needs-update

Hi Maintainer

Pygalmesh 0.5.0-1 is failing its autopkgtests on arm64 [1], and on
ppc64el and s390x in Ubuntu [2], with the output below.

Regards
Graham


[1] https://ci.debian.net/packages/p/pygalmesh/testing/arm64/
[2] http://autopkgtest.ubuntu.com/packages/pygalmesh


___ test_inr ___

def test_inr():
this_dir = os.path.dirname(os.path.abspath(__file__))
mesh = pygalmesh.generate_from_inr(
os.path.join(this_dir, "meshes", "skull_2.9.inr"),
cell_size=5.0, verbose=False
)

tol = 1.0e-3
ref = [2.031053e02, 3.739508e01, 2.425594e02, 2.558910e01,
2.300883e02, 1.775010e00]
assert abs(max(mesh.points[:, 0]) - ref[0]) < tol * ref[0]
assert abs(min(mesh.points[:, 0]) - ref[1]) < tol * ref[1]
assert abs(max(mesh.points[:, 1]) - ref[2]) < tol * ref[2]
>   assert abs(min(mesh.points[:, 1]) - ref[3]) < tol * ref[3]
E   assert 0.035070535278318715 < (0.001 * 25.5891)
E+  where 0.035070535278318715 = abs((25.55403 - 25.5891))
E+where 25.55403 = min(array([124.876366, 124.18895 ,
119.206505, ...,  96.627495, 124.194954,\n   143.47313 ],
dtype=float32))

test/test_inr.py:18: AssertionError
--- End Message ---
--- Begin Message ---
Source: pygalmesh
Source-Version: 0.5.0-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 31 Dec 2019 09:19:05 +1100
Source: pygalmesh
Architecture: source
Version: 0.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 947058
Changes:
 pygalmesh (0.5.0-3) unstable; urgency=medium
 .
   * more tolerance relaxing in relax_test_tolerance.patch.
 Closes: #947058.
Checksums-Sha1:
 e68c8c8ffa09ef46efc192851d65d5c54d7aed86 2172 pygalmesh_0.5.0-3.dsc
 01b726baa7f093512ee19ef0edd83455f385fe70 4792 pygalmesh_0.5.0-3.debian.tar.xz
Checksums-Sha256:
 aa760d8231b177b6dc45589d626392123390f90961763c264728439dea6dd3b0 2172 
pygalmesh_0.5.0-3.dsc
 95bfb661171999d6e5b3dbed4ca681502b9f8a30070fa53217100c919c3be49a 4792 
pygalmesh_0.5.0-3.debian.tar.xz
Files:
 28cc6faed626c680d781920f6d10f801 2172 python optional pygalmesh_0.5.0-3.dsc
 5c55680a6ffe67db2365a784f36b0847 4792 python optional 
pygalmesh_0.5.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAl4KfYkACgkQVz7x5L1a
AfrnahAAtuVbUuNDlQA6CaDt+Z+IErRf7lJm91sN/X5aWGr6gFNCSCam//KuIHM5
j3zC5rsHd4dADtHBXjhHhhDErTpgAD1Ph6mSjN3GBtU8XY9FPZa/I4sKzLWW2VdV
JQZV2HKWS5bhgKh/d0k2tUKcq6Po3LKL6GWrmOraCdA/Cfn+RX/xGirl5FkQRbwu
bfC113H4ssTKEbGypu/DWm+CIKwsaU3R0PdLFZb/9aTJC0Vaud/gTofIDbZ1w5rQ
+azizMzcCysPJwRvfm3brkTlQtLYU4WHGu9rZhoG8Nvw30hJykVOM+M3GuQ5f+WU
7i4XjPBicDB9+lO60mmT9x8s6WWTv5WdCBQoMCleh/2TsbyO3p4j16HewTiCxgVW
JmqJqFf/f2B6QbdFql2weBDflTvwDGDZYY1Z2hJtoPJcalI+1EwrUK0o+UMf1CaG
3os5BOEpl6aztMNsSWgECFrIqLElzlTO1DQVYOQWcYPMTAD0J1OtldKdyPaijn/w
kVvAxkpenay8ccJBFYP5YyvVrUNB+taRmHR0WUm8HC9eVNmILu9vHd1+n60kpL2n
A2uoXL8mUCV9aqDNBMvVNCFoVPAU4OoQI0t5IRaV5xHeunSGjS5Y4CgXECPiXBL4
PJWuwqsIXuxK1qMxcskQB9wIVlxZVWenQBk4RWSQGqCkyepgyTQ=
=+NAy
-END PGP SIGNATURE End Message ---

Bug#937267: Is there any Python3 version of pebl

2019-12-30 Thread Abhik Shah

The first link is mine and the original fork but its basically abandoned. I
haven’t looked at any of the forks so unsure which are popular or being
kept up-to-date.

On Mon, Dec 30, 2019 at 12:56 PM Andreas Tille  wrote:

> Hi Abhik,
>
> thanks for the quick reply.
>
> On Sun, Dec 29, 2019 at 05:55:35PM -0800, Abhik Shah wrote:
> > 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.
>
> This one looks official
>
>https://github.com/abhik/pebl
>
> I've found another clone
>
>https://github.com/arnaudsj/pebl
>
> which has just one commit less.  Any hint what fork could be recommended
> for a py3 port?
>
> Kind regards
>
>  Andreas.
>
> > 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
> > >
>
> --
> http://fam-tille.de
>

Bug#947780: libcrypt1: keep from migrating to testing until libcrypt{,1}-dev situation is fixed in glibc

Marco d'Itri dixit:

>>   a new source-only upload and piuparts fails testing, though
>>   the latter might be due to the glibc issue maybe?
>No, this is an unrelated piuparts bug which was fixed yesterday.

Ah okay.

In the meantime, a new glibc was uploaded and just needs to
finish building on all release architectures, then I’ll close
this bug here as well.

bye,
//mirabilos
-- 
08:05⎜ mika: Does grml have an tool to read Apple
 ⎜System Log (asl) files? :)
08:08⎜ yeah. /bin/rm. ;)   08:09⎜ hexdump -C
08:31⎜ ft, mrud: *g*

Processed: Bug#937794 marked as pending in python-gnupg

Processing control commands:

> tag -1 pending
Bug #937794 [src:python-gnupg] python-gnupg: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #937794 to the same tags previously set

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

Bug#937794: marked as pending in python-gnupg

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/python-gnupg/commit/d447902caa71593517174df65c8e49814b0ab77f


Remove python2 version; Closes: #937794


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937794

Bug#947780: libcrypt1: keep from migrating to testing until libcrypt{,1}-dev situation is fixed in glibc

2019-12-30 Thread Marco d'Itri

On Dec 30, Thorsten Glaser  wrote:

> ① it won’t migrate as-is currently anyway, because it needs
>   a new source-only upload and piuparts fails testing, though
>   the latter might be due to the glibc issue maybe?
No, this is an unrelated piuparts bug which was fixed yesterday.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#947793: tkmpeg not working

2019-12-30 Thread andreimpopescu

Control: reassign -1 tk-mpeg
Control: found -1 1.0.7-1

On Lu, 30 dec 19, 21:14:12, Ole Streicher wrote:
> Package: tk-mpeg 1.0.7-1
> Severity: serious
> 
> Tkmpeg does not work and causes saods9 to fail:
> 
> Error in startup script: couldn't load file 
> "/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so": 
> /usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so: undefined symbol: 
> _ZTVSt9basic_iosIcSt11char_traitsIcEE
> while executing
> "load /usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so tkmpeg"
> ("package ifneeded tkmpeg 1.0" script)
> invoked from within
> "package require tkmpeg"
> (file "/usr/share/saods9/library/ds9.tcl" line 207)
> 
> This is seen in the saods9 CI tests,
> 
> https://ci.debian.net/data/autopkgtest/unstable/amd64/s/saods9/3742299/log.gz
> 
> No idea what the cause is.

-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Processed: Re: Bug#947793: tkmpeg not working

Processing control commands:

> reassign -1 tk-mpeg
Bug #947793 [tk-mpeg 1.0.7-1] tkmpeg not working
Warning: Unknown package '1.0.7-1'
Bug reassigned from package 'tk-mpeg 1.0.7-1' to 'tk-mpeg'.
Ignoring request to alter found versions of bug #947793 to the same values 
previously set
Ignoring request to alter fixed versions of bug #947793 to the same values 
previously set
> found -1 1.0.7-1
Bug #947793 [tk-mpeg] tkmpeg not working
Marked as found in versions tkmpeg/1.0.7-1.

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

Bug#945920: Random Chromium crashes

2019-12-30 Thread Eloston

Alright, here's a revised process to compile Chromium locally with tracing re-
enabled:

1. First, download the patch and save it as "enable-tracing.patch"
2. Run the following:

$ wget
https://salsa.debian.org/chromium-team/chromium/-/archive/c88b97a6dc183a6a7f8a05aee9e99957285a9371/chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371.tar.bz2
$ tar xf chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371.tar.bz2
$ cd chromium-c88b97a6dc183a6a7f8a05aee9e99957285a9371
$ patch -p1 < enable-tracing.patch
# mk-build-deps -i debian/control
$ ./debian/rules get-orig-source
$ cd chromium-79.0.3945.79
$ dpkg-buildpackage -b -uc

After several hours, packages should appear in chromium-
c88b97a6dc183a6a7f8a05aee9e99957285a9371

Regards,
Eloston
commit 9a07b14585c4948d3baf2763d0f71ac5b3af758c
Author: Eloston 
Date:   Mon Dec 30 21:34:23 2019 +

Revert disabling tracing

diff --git a/debian/copyright b/debian/copyright
index ef2174d..f81086c 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -37,7 +37,6 @@ Files-Excluded:
  chrome/installer/launcher_support
  chrome/common/extensions/docs
  chrome/common/safe_browsing/rar_analyzer.*
- chrome/browser/tracing
  chrome/browser/resources/chromeos
  chrome/browser/resources/default_apps
  chrome/test/data/android
@@ -45,7 +44,6 @@ Files-Excluded:
  chrome/test/data/extensions
  chrome/test/data/webui/i18n_process_css_test.html
  chrome/chrome_cleaner/test/resources/signed_dll
- services/tracing
  tools/emacs
  tools/luci-go
  tools/android
@@ -116,7 +114,6 @@ Files-Excluded:
  third_party/expat/src
  third_party/*rjsmin/bench
  third_party/unrar
- third_party/perfetto
  third_party/checkstyle
  third_party/swiftshader
  third_party/apache-win32
@@ -150,23 +147,6 @@ Files-Excluded:
  third_party/devtools-node-modules
  third_party/blanketjs/src/blanket.js
  third_party/accessibility-audit/axs_testing.js
- third_party/catapult/tracing
- third_party/catapult/third_party/flot
- third_party/catapult/third_party/chai
- third_party/catapult/third_party/vinn
- third_party/catapult/third_party/mocha
- third_party/catapult/third_party/coverage
- third_party/catapult/third_party/polymer2
- third_party/catapult/third_party/polymer3
- third_party/catapult/third_party/polymer/components
- third_party/catapult/third_party/d3/d3.min.js
- third_party/catapult/third_party/redux/redux.min.js
- third_party/catapult/experimental/heatmap/power.js
- third_party/catapult/experimental/heatmap/smoothness.js
- third_party/catapult/experimental/trace_on_tap/third_party/pako/pako_deflate.min.js
- third_party/catapult/third_party/gsutil
- third_party/catapult/third_party/Paste/paste/evalexception/media/MochiKit.packed.js
- third_party/catapult/telemetry/telemetry/internal/testing/perf_report_output.txt
  third_party/webrtc/sdk
  third_party/webrtc/data
  third_party/webrtc/examples
diff --git a/debian/patches/series b/debian/patches/series
index cc98644..42ca728 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -39,11 +39,9 @@ disable/owners.patch
 disable/signin.patch
 disable/android.patch
 disable/fuzzers.patch
-disable/tracing.patch
 disable/openh264.patch
 disable/buildbot.patch
 disable/chromeos.patch
-disable/perfetto.patch
 disable/installer.patch
 disable/font-tests.patch
 disable/swiftshader.patch
diff --git a/debian/rules b/debian/rules
index 59b541d..cafc753 100755
--- a/debian/rules
+++ b/debian/rules
@@ -199,16 +199,14 @@ get-orig-source:
 	patch -p1 < debian/scripts/mk-origtargz.patch
 	date +%s > $(seconds)
 	perl debian/scripts/mk-origtargz ../$(tarball) > $(removed)
+	echo $(extract)/third_party/perfetto/ui/src/gen >> $(removed)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
 	test ! -e $(extract) || rm -rf $(extract)
 	tar xf ../$(tarball)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	while read line; do rm -rf $$line; done < $(removed)
+	xargs rm -rf < $(removed)
 	cd $(extract) && ../debian/scripts/check-upstream
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	test ! -e $(origtxz) || rm -f $(origtxz)
-	tar cf - $(extract) | xz -6 -T $(njobs) - > $(origtxz)
-	echo $$(($$(date +%s) - $$(cat $(seconds seconds
-	rm -rf $(extract)
 	echo $$(($$(date +%s) - $$(cat $(seconds seconds | tee seconds
 	@mv -f seconds $(seconds)
+	test ! -e debian || rm -rf debian
+	cp -r ../debian ./

Bug#947293: marked as done (libkate: autopkgtest failures due to libkate-tools removal)

Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to 
libkate-tools removal
has caused the Debian Bug report #946632,
regarding libkate: autopkgtest failures due to libkate-tools removal
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.)


-- 
946632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkate
Version: 0.4.1-10
Severity: serious
Tags: patch
Justification: autopkgtest regression
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the removal of libkate-tools in libkate 0.4.1-10, the libkate
autopkgtest consistently fails, because all of the commands it previously
attempted to run were in the libkate-tools package:

[...]
autopkgtest [12:55:24]: test test-cmd-tools:  - - - - - - - - - - stderr - - - 
- - - - - - -
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 25: kateenc: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 31: katalyzer: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 37: katedec: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 40: errorunable to run katedec: not found
[...]

  
(https://ci.debian.net/data/autopkgtest/unstable/amd64/libk/libkate/3520793/log.gz)

I think the autopkgtest should simply be dropped, since there is nothing
left for it to do at present.  Please see the attached patch.

Cheers,
-- 
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 libkate-0.4.1/debian/tests/control libkate-0.4.1/debian/tests/control
--- libkate-0.4.1/debian/tests/control  2019-11-26 16:03:42.0 -0600
+++ libkate-0.4.1/debian/tests/control  1969-12-31 18:00:00.0 -0600
@@ -1,2 +0,0 @@
-Depends: @
-Tests: test-cmd-tools
diff -Nru libkate-0.4.1/debian/tests/test-cmd-tools 
libkate-0.4.1/debian/tests/test-cmd-tools
--- libkate-0.4.1/debian/tests/test-cmd-tools   2019-11-26 16:03:42.0 
-0600
+++ libkate-0.4.1/debian/tests/test-cmd-tools   1969-12-31 18:00:00.0 
-0600
@@ -1,49 +0,0 @@
-#!/bin/sh
-#
-# Test the kate command line tools to ensure they can run without
-# returning an error.
-
-set -e
-
-retval=0
-
-success() { echo "success:" "$@"; }
-error() { echo "error:" "$@"; retval=1; }
-
-cat > input.srt < 00:00:14,000
-This is a simple subtext block
-that will be encoded into an ogg file.
-
-2
-00:00:15,000 --> 00:00:16,000
-This is the second subtext block.
-
-EOF
-
-if kateenc -t srt -l cy -c SUB -o output.ogg input.srt ; then
-success "kateenc could encode an SRT file to OGG"
-else
-error "unable to run kateenc"
-fi
-
-if katalyzer output.ogg ; then
-success "running katalyzer worked"
-else
-error "unable to run katalyser"
-fi
-
-if katedec output.ogg ; then
-success "running katedec worked"
-else
-error"unable to run katedec"
-fi
-
-if KateDJ  --version ; then
-success "running KateDJ worked"
-else
-error "unable to run KateDJ"
-fi
-
-exit $retval
--- End Message ---
--- Begin Message ---
Version: 0.4.1-11

This was fixed in 0.4.1-11, which missed a "Closes:"

Cheers,
Moritz--- End Message ---

Bug#947293: marked as done (libkate: autopkgtest failures due to libkate-tools removal)

Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to 
libkate-tools removal
has caused the Debian Bug report #947293,
regarding libkate: autopkgtest failures due to libkate-tools removal
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.)


-- 
947293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libkate
Version: 0.4.1-10
Severity: serious
Tags: patch
Justification: autopkgtest regression
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the removal of libkate-tools in libkate 0.4.1-10, the libkate
autopkgtest consistently fails, because all of the commands it previously
attempted to run were in the libkate-tools package:

[...]
autopkgtest [12:55:24]: test test-cmd-tools:  - - - - - - - - - - stderr - - - 
- - - - - - -
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 25: kateenc: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 31: katalyzer: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 37: katedec: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
 40: errorunable to run katedec: not found
[...]

  
(https://ci.debian.net/data/autopkgtest/unstable/amd64/libk/libkate/3520793/log.gz)

I think the autopkgtest should simply be dropped, since there is nothing
left for it to do at present.  Please see the attached patch.

Cheers,
-- 
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 libkate-0.4.1/debian/tests/control libkate-0.4.1/debian/tests/control
--- libkate-0.4.1/debian/tests/control  2019-11-26 16:03:42.0 -0600
+++ libkate-0.4.1/debian/tests/control  1969-12-31 18:00:00.0 -0600
@@ -1,2 +0,0 @@
-Depends: @
-Tests: test-cmd-tools
diff -Nru libkate-0.4.1/debian/tests/test-cmd-tools 
libkate-0.4.1/debian/tests/test-cmd-tools
--- libkate-0.4.1/debian/tests/test-cmd-tools   2019-11-26 16:03:42.0 
-0600
+++ libkate-0.4.1/debian/tests/test-cmd-tools   1969-12-31 18:00:00.0 
-0600
@@ -1,49 +0,0 @@
-#!/bin/sh
-#
-# Test the kate command line tools to ensure they can run without
-# returning an error.
-
-set -e
-
-retval=0
-
-success() { echo "success:" "$@"; }
-error() { echo "error:" "$@"; retval=1; }
-
-cat > input.srt < 00:00:14,000
-This is a simple subtext block
-that will be encoded into an ogg file.
-
-2
-00:00:15,000 --> 00:00:16,000
-This is the second subtext block.
-
-EOF
-
-if kateenc -t srt -l cy -c SUB -o output.ogg input.srt ; then
-success "kateenc could encode an SRT file to OGG"
-else
-error "unable to run kateenc"
-fi
-
-if katalyzer output.ogg ; then
-success "running katalyzer worked"
-else
-error "unable to run katalyser"
-fi
-
-if katedec output.ogg ; then
-success "running katedec worked"
-else
-error"unable to run katedec"
-fi
-
-if KateDJ  --version ; then
-success "running KateDJ worked"
-else
-error "unable to run KateDJ"
-fi
-
-exit $retval
--- End Message ---
--- Begin Message ---
Version: 0.4.1-11

This was fixed in 0.4.1-11, which missed a "Closes:"

Cheers,
Moritz--- End Message ---

Bug#946632: marked as done (libkate: autopkgtest regression: tests removed executables)

Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to 
libkate-tools removal
has caused the Debian Bug report #947293,
regarding libkate: autopkgtest regression: tests removed executables
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.)


-- 
947293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkate
Version: 0.4.1-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of libkate the autopkgtest of libkate fails in
testing when that autopkgtest is run with the binary packages of libkate
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
libkatefrom testing0.4.1-10
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the
autopkgtest tries to test binaries that were removed in the latest upload.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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=libkate

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkate/3642386/log.gz

autopkgtest [04:12:56]: test test-cmd-tools: [---
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
25: kateenc: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
31: katalyzer: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
37: katedec: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
40: errorunable to run katedec: not found
error: unable to run kateenc
error: unable to run katalyser
autopkgtest [04:12:57]: test test-cmd-tools: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4.1-11

This was fixed in 0.4.1-11, which missed a "Closes:"

Cheers,
Moritz--- End Message ---

Bug#946632: marked as done (libkate: autopkgtest regression: tests removed executables)

Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to 
libkate-tools removal
has caused the Debian Bug report #946632,
regarding libkate: autopkgtest regression: tests removed executables
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.)


-- 
946632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkate
Version: 0.4.1-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of libkate the autopkgtest of libkate fails in
testing when that autopkgtest is run with the binary packages of libkate
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
libkatefrom testing0.4.1-10
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the
autopkgtest tries to test binaries that were removed in the latest upload.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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=libkate

https://ci.debian.net/data/autopkgtest/testing/amd64/libk/libkate/3642386/log.gz

autopkgtest [04:12:56]: test test-cmd-tools: [---
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
25: kateenc: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
31: katalyzer: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
37: katedec: not found
/tmp/autopkgtest-lxc.r9twx9yv/downtmp/build.Ya8/src/debian/tests/test-cmd-tools:
40: errorunable to run katedec: not found
error: unable to run kateenc
error: unable to run katalyser
autopkgtest [04:12:57]: test test-cmd-tools: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.4.1-11

This was fixed in 0.4.1-11, which missed a "Closes:"

Cheers,
Moritz--- End Message ---

Bug#937267: Is there any Python3 version of pebl

2019-12-30 Thread Andreas Tille

Hi Abhik,

thanks for the quick reply.

On Sun, Dec 29, 2019 at 05:55:35PM -0800, Abhik Shah wrote:
> 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.

This one looks official

   https://github.com/abhik/pebl

I've found another clone

   https://github.com/arnaudsj/pebl

which has just one commit less.  Any hint what fork could be recommended
for a py3 port?

Kind regards

 Andreas. 
 
> 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
> >

-- 
http://fam-tille.de

Processed: python-apt: autopkgtest fails on deprecation warnings to stderr

Processing control commands:

> affects -1 src:python3-defaults
Bug #947794 [src:python-apt] python-apt: autopkgtest fails on deprecation 
*warnings* to stderr
Added indication that 947794 affects src:python3-defaults

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

Bug#947794: python-apt: autopkgtest fails on deprecation warnings to stderr

2019-12-30 Thread Paul Gevers

Source: python-apt
Version: 1.8.4
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

Dear maintainers,

With a recent upload of python3-defaults the autopkgtest of python-apt
fails in testing when that autopkgtest is run with the binary packages
of python3-defaults from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
python3-defaults   from testing3.7.5-3
python-apt from testing1.8.4
all others from testingfrom testing

I copied some of the output at the bottom of this report. I seems your
test fails only on deprecation *warnings* to stderr. Please, either
disable deprecation warnings in your autopkgtest or allow output to
stderr (the allow-stderr restriction). Autopkgtest is not the place to
catch deprecation warnings.

Currently this regression is blocking the migration of python3-defaults
to testing [1], although we will ignore this failure for this migration.

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=python3-defaults

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

autopkgtest [04:46:34]: test run-tests: [---
[tests] Running on 2.7.17 (default, Oct 19 2019, 23:36:22) [GCC 9.2.1
20191008]
Using library_dir:
'None'--
Ran 104 tests in 14.284s

OK (skipped=3)
/usr/lib/python3/dist-packages/apt/package.py:484: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  return apt_pkg.version_compare(self._cand.ver_str, other.version)
/usr/lib/python3/dist-packages/apt/package.py:401: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  self._rec = apt_pkg.TagSection(record_str)
/usr/lib/python3/dist-packages/apt/debfile.py:89: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  self._sections = apt_pkg.TagSection(control)
/usr/lib/python3/dist-packages/apt/debfile.py:325: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  return apt_pkg.parse_depends(self._sections[key], False)
/usr/lib/python3/dist-packages/apt/debfile.py:338: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  apt_pkg.parse_depends(self._sections[key], False))
/usr/lib/python3/dist-packages/apt/debfile.py:349: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  return apt_pkg.parse_depends(self._sections[key], False)
/usr/lib/python3/dist-packages/apt/debfile.py:359: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  return apt_pkg.parse_depends(self._sections[key], False)
/usr/lib/python3/dist-packages/apt/debfile.py:799: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
  self._depends.extend(apt_pkg.parse_src_depends(sec[tag]))
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:75:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  deps = apt_pkg.parse_depends("p1a (<< 1a) | p1b (>> 1b)")
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:90:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual("<", apt_pkg.parse_depends("p1 (<< 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:91:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual("<=", apt_pkg.parse_depends("p1 (< 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:92:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual("<=", apt_pkg.parse_depends("p1 (<= 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:93:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual("=", apt_pkg.parse_depends("p1 (= 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:94:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual(">=", apt_pkg.parse_depends("p1 (>= 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:95:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual(">=", apt_pkg.parse_depends("p1 (> 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:96:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  self.assertEqual(">", apt_pkg.parse_depends("p1 (>> 1)")[0][0][2])
/tmp/autopkgtest-lxc.owlmydaz/downtmp/build.h5S/src/tests/test_deps.py:67:
DeprecationWarning: PY_SSIZE_T_CLEAN will be required for '#' formats
  deps = apt_pkg.parse_depends("po4a:native", True)
/tmp/autopkgtest-lxc

Bug#947793: tkmpeg not working

2019-12-30 Thread Ole Streicher

Package: tk-mpeg 1.0.7-1
Severity: serious

Tkmpeg does not work and causes saods9 to fail:

Error in startup script: couldn't load file 
"/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so": 
/usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so: undefined symbol: 
_ZTVSt9basic_iosIcSt11char_traitsIcEE
while executing
"load /usr/lib/tcltk/x86_64-linux-gnu/tkmpeg1.0/libtkmpeg1.0.so tkmpeg"
("package ifneeded tkmpeg 1.0" script)
invoked from within
"package require tkmpeg"
(file "/usr/share/saods9/library/ds9.tcl" line 207)

This is seen in the saods9 CI tests,

https://ci.debian.net/data/autopkgtest/unstable/amd64/s/saods9/3742299/log.gz

No idea what the cause is.

Bug#947789: dh-python: autopkgtest needs update for new version of python3-defaults: doesn't depend on itself

2019-12-30 Thread Paul Gevers

Source: dh-python
Version: 4.20191017
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults

[X-Debbugs-CC: debian...@lists.debian.org,
python3-defau...@packages.debian.org]

Dear maintainers,

With a recent upload of python3-defaults the autopkgtest of dh-python
fails in testing when that autopkgtest is run with the binary packages
of python3-defaults from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
python3-defaults   from testing3.7.5-3
dh-python  from testing4.20191017
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems that
the autopkgtests of dh-python don't depend on itself when running the
tests against the (not) installed package. You'll know better than I do
why the Python packages stopped depending on dh-python.

Currently this regression is blocking the migration of python3-defaults
to testing [1], although we will ignore this failure for this migration.

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=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/d/dh-python/3809157/log.gz

autopkgtest [04:46:25]: test nosetests: [---
Failure: OSError (No such file /usr/share/dh-python/dhpython) ... ERROR

==
ERROR: Failure: OSError (No such file /usr/share/dh-python/dhpython)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/failure.py", line 42, in runTest
raise self.exc_class(self.exc_val)
OSError: No such file /usr/share/dh-python/dhpython

--
Ran 1 test in 0.001s

FAILED (errors=1)
autopkgtest [04:46:26]: test nosetests: ---]




signature.asc
Description: OpenPGP digital signature

Processed: dh-python: autopkgtest needs update for new version of python3-defaults: doesn't depend on itself

Processing control commands:

> affects -1 src:python3-defaults
Bug #947789 [src:dh-python] dh-python: autopkgtest needs update for new version 
of python3-defaults: doesn't depend on itself
Added indication that 947789 affects src:python3-defaults

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

Bug#945648: marked as done (goldeneye: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 18:49:42 +
with message-id 
and subject line Bug#945648: fixed in goldeneye 1.2.0+git20191230-1
has caused the Debian Bug report #945648,
regarding goldeneye: 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.)


-- 
945648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: goldeneye
Version: 1.2.0-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 (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: goldeneye
Source-Version: 1.2.0+git20191230-1

We believe that the bug you reported is fixed in the latest version of
goldeneye, 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 goldeneye 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 18:14:52 +
Source: goldeneye
Architecture: source
Version: 1.2.0+git20191230-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Closes: 945648
Changes:
 goldeneye (1.2.0+git20191230-1) unstable; urgency=medium
 .
   * New upstream version 1.2.0+git20191230
   * Use python3 (closes: #945648)
   * Bump DH to v12
   * Bump Standards-Version to 4.4.1
   * Use my d.o email address
   * Add salsa-ci.yml
   * d/control:
 - Add Suggests: python3-bs4
 - Add Rules-Requires-Root: no
   * d/copyright: Use https
   * d/p/10_fix_help.patch: Update patch
Checksums-Sha1:
 7bad69a1c76a1802ae8e5d77dfc529e942704e2d 2015 goldeneye_1.2.0+git20191230-1.dsc
 ba2310c1238142cc2b46347a420137257614c34a 100418 
goldeneye_1.2.0+git20191230.orig.tar.gz
 eedd87db98736f712a40fd9d377df63ddff943c9 5028 
goldeneye_1.2.0+git20191230-1.debian.tar.xz
 6516d493ce2dba66b8426e6e83f34fd9af1a5315 5347 
goldeneye_1.2.0+git20191230-1_amd64.buildinfo
Checksums-Sha256:
 e81f6cfcf2306726de1ace70582f147e930207cea2ad21e4805e7f6c2c3f9f99 2015 
goldeneye_1.2.0+

Bug#947778: marked as done (libc6-dev: please change dependency on libcrypt1-dev to libcrypt-dev)

Your message dated Mon, 30 Dec 2019 18:35:20 +
with message-id 
and subject line Bug#947778: fixed in glibc 2.29-7
has caused the Debian Bug report #947778,
regarding libc6-dev: please change dependency on libcrypt1-dev to libcrypt-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.)


-- 
947778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-dev
Version: 2.29-6
Severity: grave
Justification: renders package unusable

The libcrypt1-dev package got renamed, so the dependencies must match,
or libc6-dev becomes uninstallable or libcrypt1 unupgradable. AIUI both
glibc and libxcrypt must migrate to testing together this time, too…

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

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

Versions of packages libc6-dev depends on:
ii  libc-dev-bin2.29-6
ii  libc6   2.29-6
ii  libcrypt1-dev   1:4.4.10-7
ii  linux-libc-dev  5.4.6-1

libc6-dev recommends no packages.

Versions of packages libc6-dev suggests:
pn  glibc-doc 
ii  manpages-dev  5.04-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.29-7

We believe that the bug you reported is fixed in the latest version of
glibc, 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.
Aurelien Jarno  (supplier of updated glibc 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 19:12:42 +0100
Source: glibc
Architecture: source
Version: 2.29-7
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Closes: 947778
Changes:
 glibc (2.29-7) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * patches/hurd-i386/git-altstack-RPC.diff: Fix restoring from altstack while
 blocked in an RPC.
   * patches/hurd-i386/git-getrandom.diff: Add support for getrandom &
 getentropy.
 .
   [ Aurelien Jarno ]
   * debian/rules.d/debhelper.mk: change dependency from libcrypt1-dev to
 libcrypt-dev.  Closes: #947778.
Checksums-Sha1:
 1ff10ce6cdb37a6d16459293ae079122564a0628 8735 glibc_2.29-7.dsc
 26a6a8d4f4793829843babcb603c9c6501fc9e23 856872 glibc_2.29-7.debian.tar.xz
 6cc1aa37bc070351108c2b5336dc1079a85d2ee8 7453 glibc_2.29-7_source.buildinfo
Checksums-Sha256:
 e35286c7493fb3d01551220ecbc20a2632f9ee2f148ddc5d4f5f91c296c3199b 8735 
glibc_2.29-7.dsc
 97181fd1c6f574edda864e10105fed69a1e1296a446cfff9b06ae8687f332a16 856872 
glibc_2.29-7.debian.tar.xz
 fbf088a2cde3166cd30de04a4d1f00325eeaf4e771e2cb96bd30fcac86a66a53 7453 
glibc_2.29-7_source.buildinfo
Files:
 dfdda565ebec98f8c4e8d01903934666 8735 libs required glibc_2.29-7.dsc
 135adb907169342a1c2b6f593e1bf0f2 856872 libs required 
glibc_2.29-7.debian.tar.xz
 c0045f8fe9ca3198d6fd75c71f5f284c 7453 libs required 
glibc_2.29-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAl4KPtYACgkQE4jA+Jno
M2tw8xAAj54sJKEe6sImu6OjsPkj91cbYrZZVueq+iytPX8dDq78+D59WLFikDH8
wJvve2TaG2Scp1rusfhEE2134hdwX9w8ne7NSTMWoBUxdFT2cMJO6KxY5BbSOcWX
WrcgGnw46+g3+yS3RuBkLbsbdMvwSSneeAsj2PwQL6amHDSf2gi8jPkQKbvVg5m8
BOpM3fQe4MQ9vI2eXU6avjuP7zbyZKD8LzY2IXUO+6nCBWRYO1rfK3Kmy5DFAg27
hELod5NcKG98Rxu5McG0UQTkZSfnUSY9jF7bjkUyOb9Fln248TiiKQjS6e7eQBe5
dFgLgQfRioXjTCeH41OX8P+o9HH+ffGHmdGEGsR1k46zphNvuQC9gLB90Vey4xwY
YKTcHNf8veonbQN1nRyExJJFl6AfBKoKcaelw7tltu2uA8hYycLHO8qzikujjDH1
CCM8duTIx9QEwWHn138dXrlQPUZXba31H+QJs9eUqbz9C9b0u1DgMRAlwa1wW1wK
67qkhZ4slmjd1txgTkAXS1tmi6RbJB85FQpxt4pZi/5jcP3HAcCPH/VTnDgHL6gJ
NtlWX+/tOAny+AhvXvaaMfAJ2WBrr5rOCscM1VZXjTElLsCvF064c92+YozxKHbZ
4oGG/y3fLncaqKv2+V/2Eo+8aRmHHqF38J0Oh3093Bo+pv/D9i4=
=jaPa
-END PGP SIGNATURE End Message ---

Bug#942957: marked as done (dfdatetime: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 18:34:17 +
with message-id 
and subject line Bug#942957: fixed in dfdatetime 20190116-1.1
has caused the Debian Bug report #942957,
regarding dfdatetime: 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.)


-- 
942957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dfdatetime
Version: 20190116-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: dfdatetime
Source-Version: 20190116-1.1

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated dfdatetime 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 13:04:58 -0500
Source: dfdatetime
Architecture: source
Version: 20190116-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sandro Tosi 
Closes: 936387 942957
Changes:
 dfdatetime (20190116-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #942957, #936387
Checksums-Sha1:
 18ca40a9ef19300e6407650379d589917017479e 2036 dfdatetime_20190116-1.1.dsc
 800c77bb430046a445fc99504f5a0051da2aea5f 2432 
dfdatetime_20190116-1.1.debian.tar.xz
 584fd360a46877e79c45545712d1704fead95713 6250 
dfdatetime_20190116-1.1_source.buildinfo
Checksums-Sha256:
 3c349f4eed4a2ad48671d36b09c28c9e5ff52727e489a474465c7fb23e8f5411 2036 
dfdatetime_20190116-1.1.dsc
 268a22d70649e6bbcc9910b9bc8454bd04b1309f9e4beaa28ca8ec094a66b01d 2432 
dfdatetime_20190116-1.1.debian.tar.xz
 5c22c33e455a695a68006b2f9595077c07b3582db6986069f9ddbad14cc8b859 6250 
dfdatetime_20190116-1.1_source.buildinfo
Files:
 8ad94410985d84a0616329d2f78539da 2036 python optional 
dfdatetime_20190116-1.1.dsc
 a676a4860c541cfb1f3b8cd3f46296f7 2432 python optional 
dfda

Processed: Bug#945648 marked as pending in goldeneye

Processing control commands:

> tag -1 pending
Bug #945648 [src:goldeneye] goldeneye: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#945648: marked as pending in goldeneye

2019-12-30 Thread Samuel Henrique

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-security-team/goldeneye/commit/80dee0f5afc8f8b77049b653d55a6a4c28250da4


Use python3 (closes: #945648)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/945648

Bug#947778: marked as pending in glibc

2019-12-30 Thread Aurelien Jarno

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/glibc-team/glibc/commit/b6fa329b0e576d1cb11bdd88df6b7df7bde402e0


debian/rules.d/debhelper.mk: change dependency from libcrypt1-dev to 
libcrypt-dev.  Closes: #947778.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947778

Bug#942957: dfdatetime: diff for NMU version 20190116-1.1

Control: tags 936387 + patch
Control: tags 942957 + patch


Dear maintainer,

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

Regards.

diff -Nru dfdatetime-20190116/debian/changelog dfdatetime-20190116/debian/changelog
--- dfdatetime-20190116/debian/changelog	2019-01-22 06:58:01.0 -0500
+++ dfdatetime-20190116/debian/changelog	2019-12-30 13:04:58.0 -0500
@@ -1,3 +1,10 @@
+dfdatetime (20190116-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #942957, #936387
+
+ -- Sandro Tosi   Mon, 30 Dec 2019 13:04:58 -0500
+
 dfdatetime (20190116-1) unstable; urgency=medium
 
   * New upstream version 20190116
diff -Nru dfdatetime-20190116/debian/control dfdatetime-20190116/debian/control
--- dfdatetime-20190116/debian/control	2019-01-22 06:57:55.0 -0500
+++ dfdatetime-20190116/debian/control	2019-12-30 13:01:44.0 -0500
@@ -4,21 +4,13 @@
 Maintainer: Debian Security Tools 
 Uploaders: Hilko Bengen 
 Build-Depends: debhelper (>= 11), dh-python,
- python, python-setuptools,
  python3, python3-setuptools,
- python-mock, python3-mock,
+ python3-mock,
 Standards-Version: 4.3.0
 Homepage: https://github.com/log2timeline/dfdatetime
 Vcs-Git: https://salsa.debian.org/pkg-security-team/dfdatetime.git
 Vcs-Browser: https://salsa.debian.org/pkg-security-team/dfdatetime
 
-Package: python-dfdatetime
-Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends},
-Description: Digital Forensics date and time library for Python 2
- dfDateTime, or Digital Forensics date and time, provides date and
- time objects to preserve accuracy and precision.
-
 Package: python3-dfdatetime
 Architecture: all
 Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends},
diff -Nru dfdatetime-20190116/debian/python3-dfdatetime.install dfdatetime-20190116/debian/python3-dfdatetime.install
--- dfdatetime-20190116/debian/python3-dfdatetime.install	2018-12-21 15:37:44.0 -0500
+++ dfdatetime-20190116/debian/python3-dfdatetime.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-/usr/lib/python3*
diff -Nru dfdatetime-20190116/debian/python-dfdatetime.install dfdatetime-20190116/debian/python-dfdatetime.install
--- dfdatetime-20190116/debian/python-dfdatetime.install	2018-12-21 15:37:44.0 -0500
+++ dfdatetime-20190116/debian/python-dfdatetime.install	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-/usr/lib/python2*
diff -Nru dfdatetime-20190116/debian/rules dfdatetime-20190116/debian/rules
--- dfdatetime-20190116/debian/rules	2018-12-26 11:28:50.0 -0500
+++ dfdatetime-20190116/debian/rules	2019-12-30 13:04:58.0 -0500
@@ -13,7 +13,7 @@
 
 # main packaging script based on dh7 syntax
 %:
-	dh $@ --with=python2,python3 --buildsystem=pybuild
+	dh $@ --with=python3 --buildsystem=pybuild
 
 override_dh_missing:
 	dh_missing --fail-missing
@@ -22,5 +22,4 @@
 	dh_install -X/usr/share/doc/
 
 override_dh_auto_test:
-	python run_tests.py
-	python3 run_tests.py
+	PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} run_tests.py" dh_auto_test

Processed: dfdatetime: diff for NMU version 20190116-1.1

Processing control commands:

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

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

Processed: Bug#947778 marked as pending in glibc

Processing control commands:

> tag -1 pending
Bug #947778 [libc6-dev] libc6-dev: please change dependency on libcrypt1-dev to 
libcrypt-dev
Added tag(s) pending.

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

Processed: dfdatetime: diff for NMU version 20190116-1.1

Processing control commands:

> tags 936387 + patch
Bug #936387 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #936387 to the same tags previously set
> tags 942957 + patch
Bug #942957 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #942957 to the same tags previously set

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

Bug#937323: marked as done (prettytable: Python2 removal in sid/bullseye)

Your message dated Mon, 30 Dec 2019 18:07:26 +
with message-id 
and subject line Bug#937323: fixed in prettytable 0.7.2-5
has caused the Debian Bug report #937323,
regarding prettytable: 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.)


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

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: prettytable
Source-Version: 0.7.2-5

We believe that the bug you reported is fixed in the latest version of
prettytable, 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 prettytable 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 12:45:27 -0500
Source: prettytable
Architecture: source
Version: 0.7.2-5
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 937323
Changes:
 prettytable (0.7.2-5) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop python2 support; Closes: #937323
Checksums-Sha1:
 9d486f5658056f6c2b3442f20c034a33ce4e5842 2048 prettytable_0.7.2-5.dsc
 1f23688edd38da9706c54529464d35897cd53e0c 3604 prettytable_0.7.2-5.debian.tar.xz
 6685abb4bae702ce0e4807af7e4141a543acadab 6350 
prettytable_0.7.2-5_source.buildinfo
Checksums-Sha256:
 bb946c9f32eea53dcb5dddf654e71681023cbc35e7f058d684ed3876ddfe4c2e 2048 
prettytable_0.7.2-5.dsc
 2405ef815961ba042c4810b5de0ded8a13e5f5fec0333e3da004c7d8e6cffd6e 3604 
prettytable_0.7.2-5.debian.tar.xz
 b0762f2f2bb9d1dc611fc4e07a2d75a348f71601528088e740b13f637

Processed: Bug#937323 marked as pending in prettytable

Processing control commands:

> tag -1 pending
Bug #937323 [src:prettytable] prettytable: Python2 removal in sid/bullseye
Added tag(s) pending.

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

Bug#945920: Random Chromium crashes

2019-12-30 Thread Jaap Joris Vens


Hi Eloston,

Thanks for figuring out the cause of these random crashes! However, I was
unable to recompile chromium from source following your instructions. I got
the following error message at step 4b:

jj@telos:~/src/chromium-79.0.3945.79$ debian/rules get-orig-source
wget -nv --show-progress -c 
https://gsdview.appspot.com/chromium-browser-official/chromium-79.0.3945.79-lite.tar.xz
 -O ../chromium-79.0.3945.79-lite.tar.xz
../chromium-79.0.3945.79-lite 100%[>] 633.92M  10.5MB/sin 70s 
2019-12-30 18:22:47 URL:http://commondatastorage.googleapis.com/chromium-browser-official/chromium-79.0.3945.79-lite.tar.xz [664711308/664711308] -> "../chromium-79.0.3945.79-lite.tar.xz" [1]

cp /usr/share/perl5/Devscripts/MkOrigtargz.pm debian/scripts/mk-origtargz
patch -p1 < debian/scripts/mk-origtargz.patch
patching file debian/scripts/mk-origtargz
date +%s > ../chromium_79.0.3945.79.seconds
perl debian/scripts/mk-origtargz ../chromium-79.0.3945.79-lite.tar.xz > 
../chromium_79.0.3945.79.files-removed
mk-origtargz warn: No files matched excluded pattern as the last matching 
glob: *.elf
mk-origtargz warn: No files matched excluded pattern as the last matching 
glob: *.swf
mk-origtargz warn: No files matched excluded pattern as the last matching 
glob: *.orig
echo $(($(date +%s) - $(cat ../chromium_79.0.3945.79.seconds))) seconds
473 seconds
test ! -e chromium-79.0.3945.79 || rm -rf chromium-79.0.3945.79
tar xf ../chromium-79.0.3945.79-lite.tar.xz
echo $(($(date +%s) - $(cat ../chromium_79.0.3945.79.seconds))) seconds
609 seconds
while read line; do rm -rf $line; done < 
../chromium_79.0.3945.79.files-removed
cd chromium-79.0.3945.79 && ../debian/scripts/check-upstream
realpath: ./third_party/perfetto/ui/src/gen: No such file or directory
symlink links to nothing: ./third_party/perfetto/ui/src/gen ../dist/gen
make: *** [debian/rules:207: get-orig-source] Error 1

Greetings,
JJ

Bug#937323: marked as pending in prettytable

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/prettytable/commit/edd58bd4a71d43b9df87530567a342e8b8eca7bd


Drop python2 support; Closes: #937323


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/937323

Processed: py2removal RC severity updates - 2019-12-30 17:36:36.635708+00:00

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # for more details on this severity bump
> # python-libregf is a module and has 0 external rdeps or not in testing
> severity 936912 serious
Bug #936912 [src:libregf] libregf: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-prettytable is a module and has 0 external rdeps or not in testing
> severity 937323 serious
Bug #937323 [src:prettytable] prettytable: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-dfdatetime is a module and has 0 external rdeps or not in testing
> severity 942957 serious
Bug #942957 [src:dfdatetime] dfdatetime: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#946850: marked as done (last-align ftbfs on non-x86 architectures)

Your message dated Mon, 30 Dec 2019 17:20:12 +
with message-id 
and subject line Bug#946850: fixed in last-align 1044-2
has caused the Debian Bug report #946850,
regarding last-align ftbfs on non-x86 architectures
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.)


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

last-align ftbfs on non-x86 architectures, and I really didn't check if it's
doing the right thing on i386 with the intrinsics ...


In file included from GappedXdropAligner.hh:49,
 from GappedXdropAligner.cc:49:
mcf_simd.hh:7:10: fatal error: immintrin.h: No such file or directory
7 | #include 
  |  ^
compilation terminated.
make[3]: *** [makefile:105: GappedXdropAligner.o] Error 1
make[3]: Leaving directory '/<>/src'
make[2]: *** [makefile:3: all] Error 2
--- End Message ---
--- Begin Message ---
Source: last-align
Source-Version: 1044-2

We believe that the bug you reported is fixed in the latest version of
last-align, 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.
Michael R. Crusoe  (supplier of updated last-align 
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 20:19:58 -0700
Source: last-align
Architecture: source
Version: 1044-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 946850
Changes:
 last-align (1044-2) unstable; urgency=medium
 .
   * Team upload.
   * Enable building on any architecture via simde. (Closes: #946850)
   * For any-amd64 and any-i386: compile multiple times with reducing levels of
 SIMD instruction support and ship a dispatching script to pick the best
 one for the user at run-time.
Checksums-Sha1:
 04cf4396864569090c2fb81d161092f80c20f665 2041 last-align_1044-2.dsc
 6a32a6073803f908d7e6a375b1a4f55c912119a0 65668 last-align_1044-2.debian.tar.xz
 e1489e92c2fb8e7e4d4c920fdc8872a7e5e15cd7 6354 
last-align_1044-2_source.buildinfo
Checksums-Sha256:
 5b9b20d7d204054b145ec77e56dbe281d3553398fd012ac6134ab3c3ac1ef0bc 2041 
last-align_1044-2.dsc
 543ea79608dbf90e5f8d4bc8ad88aacc4a09ff744e7a2a46cae564a1cdec0012 65668 
last-align_1044-2.debian.tar.xz
 59ec78133595800e470852a1469de12ff621005fcbffa3bff78ae263bc2a1d60 6354 
last-align_1044-2_source.buildinfo
Files:
 5b49badd7f8114877787857d5c5f3c8b 2041 science optional last-align_1044-2.dsc
 6bef871b94da976ea4c3edcbfcdc1793 65668 science optional 
last-align_1044-2.debian.tar.xz
 77569a357e4629a0762bd30af8e79c80 6354 science optional 
last-align_1044-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEhMGXeonn7+0+XKYuL9i+2sAg7tEFAl4KKvQACgkQL9i+2sAg
7tEBQA//XxNm+hXP9r0PZ0QCB0VjnnXOJd4umj0MMNnuETZdg6fR9CSLN07p7dQG
Q6z1MmLOMB+RJ7KAZzbsH1HOpVIEHsKf03sa/iVryXSaqFvI79xiqwfqzEQT3AYs
vLYi/I1WZjnZJhjyeLzhPKoyGRi7b/fU25T4AeCGMY9RYYyD40zojkEzeynZpVyb
mWfplHadUGzw90E1WalEyn0F68UqfuVM92lZpNQipCualX7pIR/gzVWHEj3SIfvw
aimRF07aa3yfuj7dRhU4OsH2HZv12VZRTaArgENVWh6nGjzA6BfnAW4n3Foc/eri
SJbGmlI+iHm3gh6loyNVequagm7k5EhHrI2SgAwPDLiOcuKPirGNZcy5xgJHzoxR
qSZV1ab4w0WKlXWtZwHIIHbrm87uFyNMAV4soixcZxq068XGm4pmIDG0LXGSqSF5
F9/ey/M92ANdHPYGuHLx5yvr2crPrThNu8b20b9TsjiAfviz/NomQvTTSdxJhvVS
ofMdOBygU3od/9oxKU/ik9QE1ia2JT799RTKATfW7HTzxW524ZLb3/A1YS93+D6X
C7easfb2xpwx1AO1sV4XA28SXtyQhokztqAgFf/z7dea/rac5C9Zpw76pTCjuZC6
2AIod+J87/0mBOQ8zuJ6n0Vy8XlSh1RQR+sFeklgYpEX/jE/m58=
=Fnac
-END PGP SIGNATURE End Message ---

Bug#947001: [R-pkg-team] Bug#947001: r-base blocked by r-bioc-{iranges, s4vectors}

2019-12-30 Thread Dirk Eddelbuettel



Just to follow-up here:  As upstream for Rcpp, I just ran another reverse
dependency check againt 1700+ packages on a machine I get to use for that,
and had S4Vectors and IRanges issues pop up for three packages. It looks like
an issue with S4Vectors.

But still: Three. Out of 1700+.

Holding the Rcpp upgrade hostage to this is sub-optimal, to put it mildly. It
is a simple bug in another, orthogonal package.  There happens to be a
package using both.  Yet Rcpp gets shot by shrapnel.

Dirk

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

Processed: bug 936299 is forwarded to https://chirp.danplanet.com/issues/495

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

> forwarded 936299 https://chirp.danplanet.com/issues/495
Bug #936299 [src:chirp] chirp: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'https://chirp.danplanet.com/issues/495'.
> thanks
Stopping processing here.

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

Bug#947780: libcrypt1: keep from migrating to testing until libcrypt{,1}-dev situation is fixed in glibc

Package: libcrypt1
Version: 1:4.4.10-7
Severity: grave
Justification: renders package unusable

Sorry, the migration to testing¹ needs to be postposed a bit,
at least until #947778 is fixed (due to the -dev renaming).

① it won’t migrate as-is currently anyway, because it needs
  a new source-only upload and piuparts fails testing, though
  the latter might be due to the glibc issue maybe?

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

Kernel: Linux 5.3.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libcrypt1 depends on:
ii  libc6  2.29-6

libcrypt1 recommends no packages.

libcrypt1 suggests no packages.

-- no debconf information

Bug#947711: [Pkg-rust-maintainers] Bug#947711: rust-goblin: autopkgtest failure

2019-12-30 Thread Sylvestre Ledru


Le 29/12/2019 à 13:30, Paul Gevers a écrit :

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



error: couldn't read examples/../assets/dotnet_executable_example.dll:
No such file or directory (os error 2)
   --> examples/dotnet_pe_analysis.rs:57:16
|
57 | let file =
include_bytes!("../assets/dotnet_executable_example.dll");
|
^

error: aborting due to previous error

error: could not compile `goblin`.

Caused by:


This is probably the problem (we are not shipping the .dll).
We should probably disable the test.

Cheers,
Sylvestre

Bug#947778: libc6-dev: please change dependency on libcrypt1-dev to libcrypt-dev

Package: libc6-dev
Version: 2.29-6
Severity: grave
Justification: renders package unusable

The libcrypt1-dev package got renamed, so the dependencies must match,
or libc6-dev becomes uninstallable or libcrypt1 unupgradable. AIUI both
glibc and libxcrypt must migrate to testing together this time, too…

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

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

Versions of packages libc6-dev depends on:
ii  libc-dev-bin2.29-6
ii  libc6   2.29-6
ii  libcrypt1-dev   1:4.4.10-7
ii  linux-libc-dev  5.4.6-1

libc6-dev recommends no packages.

Versions of packages libc6-dev suggests:
pn  glibc-doc 
ii  manpages-dev  5.04-1

-- no debconf information

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

severity 946599 important
thanks

Marco d'Itri dixit:

>Since nobody else managed to reproduce this so far I am inclined to
>demote the bug to "important" to allow the migration to testing.

Agreed, it’s probably a tricky package relationship combination that
it takes to trigger this, and perhaps even nothing easily solved in
the packages.

bye,
//mirabilos
-- 
 den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt…
oder netzteile, an die man auch den monitor angeschlossen hat und die dann für
ein elektrisch aufgeladenes gehäuse gesorgt haben […] für lacher gut auf jeder
LAN party │  damals, als der pizzateig noch auf dem monior "gegangen" ist

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

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

> severity 946599 important
Bug #946599 [libcrypt1] libcrypt1: failure to switch from libc6 to libcrypt1 
hoses the whole system
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#947428: marked as done (tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 CVE-2019-15695)

Your message dated Mon, 30 Dec 2019 15:05:29 +
with message-id 
and subject line Bug#947428: fixed in tigervnc 1.10.1+dfsg-1
has caused the Debian Bug report #947428,
regarding tigervnc: CVE-2019-15691 CVE-2019-15692 CVE-2019-15693 CVE-2019-15694 
CVE-2019-15695
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.)


-- 
947428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tigervnc
Version: 1.9.0+dfsg-4
Severity: grave
Tags: security upstream
Control: found -1 1.9.0+dfsg-3

Hi,

The following vulnerabilities were published for tigervnc.

CVE-2019-15691[0]:
| TigerVNC version prior to 1.10.1 is vulnerable to stack use-after-
| return, which occurs due to incorrect usage of stack memory in
| ZRLEDecoder. If decoding routine would throw an exception, ZRLEDecoder
| may try to access stack variable, which has been already freed during
| the process of stack unwinding. Exploitation of this vulnerability
| could potentially result into remote code execution. This attack
| appear to be exploitable via network connectivity.


CVE-2019-15692[1]:
| TigerVNC version prior to 1.10.1 is vulnerable to heap buffer
| overflow. Vulnerability could be triggered from CopyRectDecoder due to
| incorrect value checks. Exploitation of this vulnerability could
| potentially result into remote code execution. This attack appear to
| be exploitable via network connectivity.


CVE-2019-15693[2]:
| TigerVNC version prior to 1.10.1 is vulnerable to heap buffer
| overflow, which occurs in TightDecoder::FilterGradient. Exploitation
| of this vulnerability could potentially result into remote code
| execution. This attack appear to be exploitable via network
| connectivity.


CVE-2019-15694[3]:
| TigerVNC version prior to 1.10.1 is vulnerable to heap buffer
| overflow, which could be triggered from DecodeManager::decodeRect.
| Vulnerability occurs due to the signdness error in processing
| MemOutStream. Exploitation of this vulnerability could potentially
| result into remote code execution. This attack appear to be
| exploitable via network connectivity.


CVE-2019-15695[4]:
| TigerVNC version prior to 1.10.1 is vulnerable to stack buffer
| overflow, which could be triggered from CMsgReader::readSetCursor.
| This vulnerability occurs due to insufficient sanitization of
| PixelFormat. Since remote attacker can choose offset from start of the
| buffer to start writing his values, exploitation of this vulnerability
| could potentially result into remote code execution. This attack
| appear to be exploitable via network connectivity.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-15691
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15691
[1] https://security-tracker.debian.org/tracker/CVE-2019-15692
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15692
[2] https://security-tracker.debian.org/tracker/CVE-2019-15693
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15693
[3] https://security-tracker.debian.org/tracker/CVE-2019-15694
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15694
[4] https://security-tracker.debian.org/tracker/CVE-2019-15695
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15695

Please adjust the affected versions in the BTS as needed.



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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: tigervnc
Source-Version: 1.10.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
tigervnc, 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 tigervnc package)

(This message was generated automatically at their reque

Processed: pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)

Processing control commands:

> reopen -1
Bug #947058 {Done: Drew Parsons } [src:pygalmesh] 
pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions pygalmesh/0.5.0-2.

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

Bug#947058: pygalmesh: autopkgtest failure on arm64 (and ppc64el, s390x)

2019-12-30 Thread Graham Inggs

Control: reopen -1

Hi Drew

The test gets a little further [1], and now fails at:

___ test_inr ___

def test_inr():
this_dir = os.path.dirname(os.path.abspath(__file__))
mesh = pygalmesh.generate_from_inr(
os.path.join(this_dir, "meshes", "skull_2.9.inr"),
cell_size=5.0, verbose=False
)

tol = 2.0e-3
ref = [2.031053e02, 3.739508e01, 2.425594e02, 2.558910e01,
2.300883e02, 1.775010e00]
assert abs(max(mesh.points[:, 0]) - ref[0]) < tol * ref[0]
assert abs(min(mesh.points[:, 0]) - ref[1]) < tol * ref[1]
assert abs(max(mesh.points[:, 1]) - ref[2]) < tol * ref[2]
assert abs(min(mesh.points[:, 1]) - ref[3]) < tol * ref[3]
assert abs(max(mesh.points[:, 2]) - ref[4]) < tol * ref[4]
assert abs(min(mesh.points[:, 2]) - ref[5]) < tol * ref[5]

vol = sum(helpers.compute_volumes(mesh.points, mesh.cells["tetra"]))
ref = 2.725335e06
>   assert abs(vol - ref) < ref * 1.0e-3
E   assert 4425.526206357405 < (2725335.0 * 0.001)
E+  where 4425.526206357405 = abs((2729760.5262063574 - 2725335.0))

test/test_inr.py:24: AssertionError

Regards
Graham


[1] 
https://ci.debian.net/data/autopkgtest/testing/arm64/p/pygalmesh/3810331/log.gz

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

2019-12-30 Thread Bernhard Übelacker

Dear Maintainer,
the given valgrind backtrace should translate to something
like below (which did not crash for me).

The crashing instruction tries to read memory pointed by register $rdi,
that held in my test the address in parameters "v" / "key" / "name".

So I assume for some reason this register $rdi and
parameter "v" / "key" / "name" contain a null pointer
leading to the crash seen by definetti.

Kind regards,
Bernhard


(gdb) bt
#0  0x77df6e20 in g_str_hash (v=0x7fffdc38d780) at 
../../../glib/ghash.c:2324
#1  0x77df5eff in g_hash_table_lookup_node (hash_return, 
key=0x7fffdc38d780, hash_table) at ../../../glib/ghash.c:473
#2  0x77df5eff in g_hash_table_lookup (hash_table, 
key=key@entry=0x7fffdc38d780) at ../../../glib/ghash.c:1509
#3  0x708f9389 in store_snap_cache_lookup (need_details, 
name=0x7fffdc38d780 "notepad-plus-plus", plugin) at 
../plugins/snap/gs-plugin-snap.c:204
#4  0x708f9389 in get_store_snap (plugin, name=0x7fffdc38d780 
"notepad-plus-plus", need_details, cancellable, error) at 
../plugins/snap/gs-plugin-snap.c:520
#5  0x708f9d2d in gs_plugin_add_alternates (plugin, app, list, 
cancellable, error) at ../plugins/snap/gs-plugin-snap.c:592
#6  0x555cca3f in gs_plugin_loader_call_vfunc (helper, plugin, app, 
app@entry, list, list@entry, refine_flags, refine_flags@entry, cancellable, 
error) at ../lib/gs-plugin-loader.c:651
#7  0x555ccc62 in gs_plugin_loader_run_results (helper, cancellable, 
error) at ../lib/gs-plugin-loader.c:1084
#8  0x555cdac5 in gs_plugin_loader_process_thread_cb (task, object, 
task_data, cancellable) at ../lib/gs-plugin-loader.c:3040
#9  0x77c92bae in g_task_thread_pool_thread (thread_data, pool_data) at 
../../../gio/gtask.c:1410
#10 0x77e31404 in g_thread_pool_thread_proxy (data) at 
../../../glib/gthreadpool.c:308
#11 0x77e30d0d in g_thread_proxy (data) at ../../../glib/gthread.c:805
#12 0x76fcdfb7 in start_thread (arg) at pthread_create.c:486
#13 0x76eff2df in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

(gdb) display/i $pc
2: x/i $pc
=> 0x77df6e20 : movsbl (%rdi),%eax
(gdb) print/x $rdi
$5 = 0x7fffdc38d780

Bug#946082: fixed in pyside2 5.13.2-2.2

2019-12-30 Thread Gianfranco Costamagna

Hello,

full patch attached to this email!

G.
diff -Nru pyside2-5.13.2/debian/changelog pyside2-5.13.2/debian/changelog
--- pyside2-5.13.2/debian/changelog 2019-11-22 10:28:55.0 +0100
+++ pyside2-5.13.2/debian/changelog 2019-12-29 22:44:55.0 +0100
@@ -1,3 +1,19 @@
+pyside2 (5.13.2-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Update cmake paths for new locations
+
+ -- Gianfranco Costamagna   Sun, 29 Dec 2019 
22:44:55 +0100
+
+pyside2 (5.13.2-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Add an explicit shiboken dependency to fix FTBFS for reverse-dependencies
+cmake based, who expect it being installed (Closes: #946082)
+- thanks Tommaso Colombo for the patch
+
+ -- Gianfranco Costamagna   Tue, 24 Dec 2019 
09:22:39 +0100
+
 pyside2 (5.13.2-2) unstable; urgency=medium
 
   * Do not build-depends on libqt5datavisualization5-dev on mipsel and
diff -Nru pyside2-5.13.2/debian/control pyside2-5.13.2/debian/control
--- pyside2-5.13.2/debian/control   2019-11-22 10:28:55.0 +0100
+++ pyside2-5.13.2/debian/control   2019-12-28 11:55:28.0 +0100
@@ -144,7 +144,7 @@
 Section: libdevel
 Architecture: any
 Depends: ${misc:Depends}, ${shlibs:Depends},
- libshiboken2-py3-5.13 (= ${binary:Version}), python3-dev
+ libshiboken2-py3-5.13 (= ${binary:Version}), shiboken2 (= ${binary:Version}), 
python3-dev
 Description: CPython bindings generator for C++ libraries (development files)
  Shiboken2 is a bindings generator for C++ libraries that outputs CPython
  source code. It collects information from library headers, and then
diff -Nru pyside2-5.13.2/debian/set-paths pyside2-5.13.2/debian/set-paths
--- pyside2-5.13.2/debian/set-paths 2019-11-22 10:28:55.0 +0100
+++ pyside2-5.13.2/debian/set-paths 2019-12-29 22:44:55.0 +0100
@@ -7,6 +7,10 @@
debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
 sed -i "s|build.*relwithdebinfo|usr|" \
debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
+sed -i "s|\${PACKAGE_PREFIX_DIR}|/usr|" \
+   debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
+sed -i 
"s|\${_IMPORT_PREFIX}/lib|\${_IMPORT_PREFIX}/$DEB_HOST_MULTIARCH|" \
+   debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
 done
 
 package="libpyside2-dev"
@@ -15,8 +19,16 @@
debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
 sed -i "s|build.*relwithdebinfo|usr|" \
debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
+sed -i "s|\${PACKAGE_PREFIX_DIR}|/usr|" \
+   debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
+sed -i 
"s|\${_IMPORT_PREFIX}/lib|\${_IMPORT_PREFIX}/$DEB_HOST_MULTIARCH|" \
+   debian/$package/usr/lib/$DEB_HOST_MULTIARCH/$directory/*;
 done
 
 # Set correctly the python path for pyside2 (Python3)
-sed -i "s|^SET(PYSIDE_PYTHONPATH.*|SET(PYSIDE_PYTHONPATH 
\"/usr/lib/python3/dist-packages\")|" \
-
debian/libpyside2-dev/usr/lib/$DEB_HOST_MULTIARCH/cmake/PySide2-$MAIN_VERSION_UPSTREAM/PySide2Config.cpython-3*m-$DEB_HOST_MULTIARCH.cmake
+sed -i "s|^set_and_check(PYSIDE_PYTHONPATH.*|set_and_check(PYSIDE_PYTHONPATH 
\"/usr/lib/python3/dist-packages/PySide2\")|" \
+
debian/libpyside2-dev/usr/lib/$DEB_HOST_MULTIARCH/cmake/PySide2-$MAIN_VERSION_UPSTREAM/PySide2Config.cpython-3*-$DEB_HOST_MULTIARCH.cmake
+
+# Set correctly the python path for shiboken2 (Python3)
+sed -i 
"s|^set_and_check(SHIBOKEN_PYTHON_MODULE_DIR.*|set_and_check(SHIBOKEN_PYTHON_MODULE_DIR
 \"/usr/lib/python3/dist-packages/shiboken2\")|" \
+
debian/libshiboken2-dev/usr/lib/$DEB_HOST_MULTIARCH/cmake/Shiboken2-$MAIN_VERSION_UPSTREAM/Shiboken2Config.cpython-3*-$DEB_HOST_MULTIARCH.cmake

Processed: Bug#947428 marked as pending in tigervnc

Processing control commands:

> tag -1 pending
Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692 
CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Added tag(s) pending.

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

Bug#947428: marked as pending in tigervnc

2019-12-30 Thread Joachim Falk

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-remote-team/tigervnc/commit/3239944136c1d9b8455da5a325467eca8e23f021


Bump version to 1.10.1+dfsg-1 and mention fix of CVE-2019-15691, 
CVE-2019-15692, CVE-2019-15693, CVE-2019-15694, and CVE-2019-15695 in changelog 
(Closes: #947428).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947428

Bug#947428: marked as pending in tigervnc

2019-12-30 Thread Joachim Falk

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-remote-team/tigervnc/commit/3239944136c1d9b8455da5a325467eca8e23f021


Bump version to 1.10.1+dfsg-1 and mention fix of CVE-2019-15691, 
CVE-2019-15692, CVE-2019-15693, CVE-2019-15694, and CVE-2019-15695 in changelog 
(Closes: #947428).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/947428

Processed: Bug#947428 marked as pending in tigervnc

Processing control commands:

> tag -1 pending
Bug #947428 [src:tigervnc] tigervnc: CVE-2019-15691 CVE-2019-15692 
CVE-2019-15693 CVE-2019-15694 CVE-2019-15695
Ignoring request to alter tags of bug #947428 to the same tags previously set

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

Bug#943608: marked as pending in beancount

2019-12-30 Thread Pierre-Elliott Bécue

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/applications/beancount/commit/f417beee517881fc323ca98d0813ee351cdb9706


d/p/0003: Work around a Python3.8 bug causing a segfault

Closes: #943608


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943608

Processed: Bug#942791 marked as pending in pymssql

Processing control commands:

> tag -1 pending
Bug #942791 [src:pymssql] fix pymssql for python 3.8
Added tag(s) pending.

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

Processed: Re: freecad: FTBFS on several architectures

Processing control commands:

> tags -1 patch pending
Bug #945314 [src:freecad] freecad: FTBFS on several architectures
Added tag(s) pending and patch.

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

Bug#947238:

2019-12-30 Thread Hosted Power Info

I looked further and found this: 
https://github.com/acassen/keepalived/issues/1071

However I don't think it's the same bug , since it doesn't restart endlessly 
when it happens. So it's probable a separate bug than the initial one reported.

All in all I think the provided version doesn't seem very stable :)

Bug#945314: freecad: FTBFS on several architectures

2019-12-30 Thread Gianfranco Costamagna

control: tags -1 patch pending

in deferred/1 there is a version that should now build with the new pyside.

I'm pushing on git my changes

cheers, and thanks for the help

Gianfranco

On Wed, 18 Dec 2019 11:45:06 +0100 Tommaso Colombo  wrote:
> Package: freecad
> Version: 0.18.4+dfsg1-1
> Followup-For: Bug #945314
> Control: block -1 by 946082
> 
> I believe this is caused by a change in the pyside2 upstream source: since
> PySide 5.13, the CMake files shipped in libshiboken2-dev have a dependency on
> the /usr/bin/shiboken2 executable. However libshiboken2-dev does not depend on
> shiboken2, which causes freecad to FTBFS. I've reported the missing dependency
> as bug #946082.
> 
>

Bug#942791: marked as pending in pymssql

2019-12-30 Thread Håvard Flaget Aasen

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/pymssql/commit/d27767db7b5132258c373c516f847f53a3228dc4


Add 0003-Remove-platform.linux_distribution.patch closes: #942791


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/942791

Processed: Bug#943608 marked as pending in beancount

Processing control commands:

> tag -1 pending
Bug #943608 [src:beancount] tests segfault when run with Python 3.8
Added tag(s) pending.

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

Bug#947546: marked as done (libtexttools: FTBFS during indep-only build: clean calls gprclean but gprbuild is in B-D-Arch)

Your message dated Mon, 30 Dec 2019 13:49:47 +
with message-id 
and subject line Bug#947546: fixed in libtexttools 2.1.0-15
has caused the Debian Bug report #947546,
regarding libtexttools: FTBFS during indep-only build: clean calls gprclean but 
gprbuild is in B-D-Arch
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.)


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

Hi,

libtexttools/experimental FTBFS during an indep-only build:

 debian/rules clean
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/libtexttools-2.1.0'
dh_auto_clean -- ADAFLAGS="" CC="cc" CFLAGS="-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION="10" 
GNATMAKE_OPTIONS=""
make -j3 clean ADAFLAGS= CC=cc "CFLAGS=-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" 
"LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION=10 
GNATMAKE_OPTIONS=
make[2]: Entering directory '/build/libtexttools-2.1.0'
Package ncurses was not found in the pkg-config search path.
Perhaps you should add the directory containing `ncurses.pc'
to the PKG_CONFIG_PATH environment variable
No package 'ncurses' found
rm -f build-obj-dynamic/* build-obj-static/* build-lib-dynamic/* 
build-lib-static/*
find -name "*~" -delete
sed ' s%ADAFLAGS%%;  s%CFLAGS%-g", "-O2", 
"-fdebug-prefix-map=/build/libtexttools-2.1.0=.", "-fstack-protector-strong", 
"-Wformat", "-Werror=format-security%;  s%LDFLAGS%-Wl,-z,relro", "-Wl,-z,now", 
"-Wl,--no-undefined", "-Wl,--no-copy-dt-needed-entries", 
"-Wl,--no-allow-shlib-undefined%;  s%LDLIBS%%;  s%SOVERSION%10%;' \
 examples/examples.gpr.sed > examples/examples.gpr
sed ' s%ADAFLAGS%%;  s%CFLAGS%-g", "-O2", 
"-fdebug-prefix-map=/build/libtexttools-2.1.0=.", "-fstack-protector-strong", 
"-Wformat", "-Werror=format-security%;  s%LDFLAGS%-Wl,-z,relro", "-Wl,-z,now", 
"-Wl,--no-undefined", "-Wl,--no-copy-dt-needed-entries", 
"-Wl,--no-allow-shlib-undefined%;  s%LDLIBS%%;  s%SOVERSION%10%;' \
 texttools.gpr.sed > texttools.gpr
gprclean examples/examples.gpr -XKIND=static
make[2]: gprclean: Command not found
make[2]: *** [Makefile:91: clean] Error 127
make[2]: Leaving directory '/build/libtexttools-2.1.0'
dh_auto_clean: make -j3 clean ADAFLAGS= CC=cc "CFLAGS=-g -O2 
-fdebug-prefix-map=/build/libtexttools-2.1.0=. -fstack-protector-strong 
-Wformat -Werror=format-security" "CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" 
"LDFLAGS=-Wl,-z,relro -Wl,-z,now -Wl,--no-undefined 
-Wl,--no-copy-dt-needed-entries -Wl,--no-allow-shlib-undefined" SOVERSION=10 
GNATMAKE_OPTIONS= returned exit code 2
make[1]: *** [debian/rules:49: override_dh_auto_clean] Error 255
make[1]: Leaving directory '/build/libtexttools-2.1.0'
make: *** [debian/rules:39: clean] Error 2


gprbuild which ships gprclean has been moved to B-D-Arch which is not
installed for an indep-only build.

There is also a failure on most arch-only builds:
https://buildd.debian.org/status/package.php?p=libtexttools&suite=experimental

dh_ada_library: error while loading shared libraries: libgpr.so.18: cannot open 
shared object file: No such file or directory


Cheers,

Andreas


libtexttools_2.1.0-14_indep.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libtexttools
Source-Version: 2.1.0-15

We believe that the bug you reported is fixed in the latest version of
libtexttools, 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.
Nicolas Boulenguez  (supplier of updated libtexttools 
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.deb

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

2019-12-30 Thread Eugen Dedu


On 29/12/2019 13:40, Michael Biebl wrote:

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, ...?


I made more tests and noticed that when I upgrade from 1.22.0-2 to 
1.22.2-1, the IPv4 still works, even if I associate several times to the 
Internet box.  The problem comes when I *restart* my Internet box.


So: I have my laptop running and IPv4 ok with 1.22.2-1.  I restart my 
Internet box.  Around one minute later, I have an IPv6 address, but no 
IPv4 address, as shown by syslog:


root@snoopy:~# grep IPv /var/log/syslog|tail
Dec 30 14:06:04 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:06:04 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv6 no 
longer relevant for mDNS.
Dec 30 14:06:04 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv4 with address 192.168.0.37.
Dec 30 14:06:04 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv4 no 
longer relevant for mDNS.
Dec 30 14:07:44 snoopy kernel: [1688643.441802] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Dec 30 14:07:44 snoopy avahi-daemon[24644]: Joining mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:07:44 snoopy avahi-daemon[24644]: New relevant interface 
wlp1s0.IPv6 for mDNS.
Dec 30 14:07:47 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:07:47 snoopy avahi-daemon[24644]: Joining mDNS multicast group 
on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0.
Dec 30 14:07:48 snoopy NetworkManager[2495]:   [1577711268.6351] 
policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS


If I restart network-manager-gnome (the icon in the task bar, I use 
awesome window manager), syslog file insists on IPv6 only:


root@snoopy:~# grep IPv /var/log/syslog|tail -11
Dec 30 14:07:48 snoopy NetworkManager[2495]:   [1577711268.6351] 
policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS
Dec 30 14:21:33 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0.
Dec 30 14:21:33 snoopy avahi-daemon[24644]: Joining mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:21:33 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:21:33 snoopy avahi-daemon[24644]: Interface wlp1s0.IPv6 no 
longer relevant for mDNS.
Dec 30 14:21:35 snoopy kernel: [1689473.467493] IPv6: 
ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
Dec 30 14:21:35 snoopy avahi-daemon[24644]: Joining mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:21:35 snoopy avahi-daemon[24644]: New relevant interface 
wlp1s0.IPv6 for mDNS.
Dec 30 14:21:36 snoopy avahi-daemon[24644]: Leaving mDNS multicast group 
on interface wlp1s0.IPv6 with address fe80::bf01:6fea:9592:b415.
Dec 30 14:21:36 snoopy avahi-daemon[24644]: Joining mDNS multicast group 
on interface wlp1s0.IPv6 with address 2a01:e0a:290:82e0:5815:8149:bcb4:18b0.
Dec 30 14:21:38 snoopy NetworkManager[2495]:   [1577712098.1291] 
policy: set 'chenoisw' (wlp1s0) as default for IPv6 routing and DNS

root@snoopy:~#

ifconfig shows:
wlp1s0: flags=4163  mtu 1300
inet6 2a01:e0a:290:82e0:5815:8149:bcb4:18b0  prefixlen 64 
scopeid 0x0

inet6 fe80::bf01:6fea:9592:b415  prefixlen 64  scopeid 0x20
ether ...  txqueuelen 1000  (Ethernet)
RX packets 15747787  bytes 15483453634 (14.4 GiB)
[...]


Now, I downgrade to previous version:

root@snoopy:/home/ededu# dpkg -i *22.*
dpkg: warning: downgrading gir1.2-nm-1.0:amd64 from 1.22.2-1 to 1.22.0-2
(Reading database ... 330241 files and directories currently installed.)
Preparing to unpack gir1.2-nm-1.0_1.22.0-2_amd64.deb ...
Unpacking gir1.2-nm-1.0:amd64 (1.22.0-2) over (1.22.2-1) ...
dpkg: warning: downgrading libnm0:amd64 from 1.22.2-1 to 1.22.0-2
Preparing to unpack libnm0_1.22.0-2_amd64.deb ...
Unpacking libnm0:amd64 (1.22.0-2) over (1.22.2-1) ...
dpkg: warning: downgrading network-manager from 1.22.2-1 to 1.22.0-2
Preparing to unpack network-manager_1.22.0-2_amd64.deb ...
Unpacking network-manager (1.22.0-2) over (1.22.2-1) ...
Setting up libnm0:amd64 (1.22.0-2) ...
Setting up network-manager (1.22.0-2) ...
Setting up gir1.2-nm-1.0:amd64 (1.22.0-2) ...
Processing triggers for libc-bin (2.29-6) ...
Processing triggers for systemd (244-3) ...
Processing triggers for dbus (1.12.16-2) ...
Processing triggers for man-db (2.9.0-2) ...

syslog shows some IPv4 activity:

root@snoopy:/home/ededu# grep IPv /var/log/syslog|tail -15
Dec 30 14:21:38 snoopy NetworkManager[2495]:   [1577712098.1291] 
policy: set 'chenoisw' (wlp1s0) as default for IPv

Bug#947238:

2019-12-30 Thread Jo Goossens

We see more problems with this package, possibly/probably related error now on 
another machine:

Dec 29 00:00:01 .xxx.com keepalived[28830]: double free or corruption 
(fasttop)

And service crashed, never came back. Seems it's not very stable atm on Buster 
:/

Bug#945672: fortunes-mario: Python2 removal in sid/bullseye

2019-12-30 Thread Juhani Numminen

Hi,

Juhani Numminen kirjoitti 25.12.2019 klo 15.45:

> I propose that we stop shipping the python2 file which in fact is
> part of build system for a PDF, and ship the actual PDF book in
> the package instead. How do you find this approach?
> 
> An NMU patch is attached and I've tested it using sbuild.
> 
> Regards,
> Juhani
> 

I'll now move on to sending a request for sponsorship. A revised
debdiff is attached.

Links to the pull requests I have opened against Fernando's repos:
https://github.com/fike/fortunes-mario/pull/2
https://github.com/fike/fortunes-mario-deb/pull/4


Juhani
diff -Nru fortunes-mario-0.21/debian/changelog 
fortunes-mario-0.21/debian/changelog
--- fortunes-mario-0.21/debian/changelog2015-08-22 06:19:48.0 
+0300
+++ fortunes-mario-0.21/debian/changelog2019-12-30 14:20:57.0 
+0200
@@ -1,3 +1,11 @@
+fortunes-mario (0.21-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Converted livro.py to python3 (Closes: #945672).
+  * Ship the actual book PDF instead of its build files.
+
+ -- Juhani Numminen   Mon, 30 Dec 2019 14:20:57 
+0200
+
 fortunes-mario (0.21-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru fortunes-mario-0.21/debian/control fortunes-mario-0.21/debian/control
--- fortunes-mario-0.21/debian/control  2015-08-18 03:31:52.0 +0300
+++ fortunes-mario-0.21/debian/control  2019-12-30 14:03:25.0 +0200
@@ -3,7 +3,13 @@
 Priority: optional
 Maintainer: Otavio Salvador 
 Uploaders: Fernando Ike de Oliveira 
-Build-Depends: debhelper (>= 9)
+Build-Depends: debhelper (>= 9),
+   ghostscript,
+   poppler-utils,
+   psutils,
+   python3,
+   texlive-lang-portuguese,
+   texlive-latex-extra
 Build-Depends-Indep: fortune-mod (>= 1.99.1-6)
 Standards-Version: 3.9.6
 Homepage: http://github.com/fike/fortunes-mario
@@ -13,7 +19,6 @@
 Package: fortunes-mario
 Architecture: all
 Depends: fortune-mod (>= 1.99.1-6), 
- python, 
  ${misc:Depends}
 Provides: fortune-cookie-db
 Description: Fortunes files from Mario
diff -Nru fortunes-mario-0.21/debian/docs fortunes-mario-0.21/debian/docs
--- fortunes-mario-0.21/debian/docs 2015-08-22 06:10:43.0 +0300
+++ fortunes-mario-0.21/debian/docs 2019-12-25 14:54:27.0 +0200
@@ -2,3 +2,4 @@
 LEIAME
 BUGS
 CREDITOS
+livro/mario_fortunes-livro.pdf
diff -Nru fortunes-mario-0.21/debian/install fortunes-mario-0.21/debian/install
--- fortunes-mario-0.21/debian/install  2015-08-18 03:31:52.0 +0300
+++ fortunes-mario-0.21/debian/install  2019-12-25 13:02:32.0 +0200
@@ -1,2 +1 @@
 mario.*usr/share/games/fortunes/
-livro  usr/share/games/fortunes/
diff -Nru fortunes-mario-0.21/debian/patches/livro-python3.patch 
fortunes-mario-0.21/debian/patches/livro-python3.patch
--- fortunes-mario-0.21/debian/patches/livro-python3.patch  1970-01-01 
02:00:00.0 +0200
+++ fortunes-mario-0.21/debian/patches/livro-python3.patch  2019-12-30 
14:20:57.0 +0200
@@ -0,0 +1,43 @@
+Description: livro.py: Switch to python3 and utf8
+ livro/Makefile requires bash: In Debian, /bin/sh is dash which cannot
+ expand brace expansion {tex,dvi,...} used in the clean target.
+ It is a bashism: https://mywiki.wooledge.org/Bashism#Expansions
+Author: Juhani Numminen 
+Forwarded: https://github.com/fike/fortunes-mario/pull/2
+Bug-Debian: https://bugs.debian.org/945672
+
+--- a/livro/livro.py
 b/livro/livro.py
+@@ -1,4 +1,5 @@
+-#!/usr/bin/env python
++#!/usr/bin/env python3
++# -*- coding: utf-8 -*-
+ 
+ import sys
+ 
+@@ -12,7 +13,7 @@
+ \usepackage[brazil]{babel}
+ \usepackage{indentfirst}
+ % #\usepackage[T1]{fontenc}
+-\usepackage[latin1]{inputenc}
++\usepackage[utf8x]{inputenc}
+ \usepackage{fancyhdr}
+ \usepackage{fancyvrb}
+ \usepackage{url}
+@@ -68,7 +69,7 @@
+ tex_file.write(r'\chapter{' + section_name + '}\n')
+ tex_file.write(bminipage + '\n')
+ 
+-print section_name
++print(section_name)
+ if section_name == 'mario.arteascii':
+ tex_file.write(bverbatimascii + '\n')
+ elif section_name == 'mario.computadores':
+--- a/livro/Makefile
 b/livro/Makefile
+@@ -1,3 +1,5 @@
++SHELL=/bin/bash
++
+ all: booklet_from_pdf
+ 
+ SRCDIR=../
diff -Nru fortunes-mario-0.21/debian/patches/series 
fortunes-mario-0.21/debian/patches/series
--- fortunes-mario-0.21/debian/patches/series   1970-01-01 02:00:00.0 
+0200
+++ fortunes-mario-0.21/debian/patches/series   2019-12-30 14:05:27.0 
+0200
@@ -0,0 +1 @@
+livro-python3.patch
diff -Nru fortunes-mario-0.21/debian/rules fortunes-mario-0.21/debian/rules
--- fortunes-mario-0.21/debian/rules2015-08-18 03:31:52.0 +0300
+++ fortunes-mario-0.21/debian/rules2019-12-30 14:02:48.0 +0200
@@ -5,6 +5,8 @@
 
 override_dh_auto_clean:
rm -f *.dat
+   cd livro && $(MAKE) clean
 
 override_dh_auto_build:
find -name "mario.*" -exec strfile {} \;
+

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

2019-12-30 Thread Marco d'Itri

Since nobody else managed to reproduce this so far I am inclined to 
demote the bug to "important" to allow the migration to testing.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#946198: marked as done (Since upgrading to 1.25.13 no remote printer is made available anymore)

Your message dated Mon, 30 Dec 2019 12:21:51 +0100
with message-id <20191230112151.ga24...@land.credativ.lan>
and subject line Re: Bug#946198: Since upgrading to 1.25.13 no remote printer
is made available anymore
has caused the Debian Bug report #946198,
regarding Since upgrading to 1.25.13 no remote printer is made available anymore
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.)

--
946198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-browsed
Version: 1.25.13-1
Severity: serious

Since upgrading the package all remote printers are gone from my printers list.
Downgrading to the latest version brings them all back.

I made this bug serious in case the problem is a general one. If not, feel free
to downgrade. Upgrading the package and losing the ability to print in the
process is an unpleasant surprise, though.

Michael

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

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

Versions of packages cups-browsed depends on:
ii cups-daemon 2.3.0-7
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libavahi-glib10.7-4+b1
ii libc6 2.29-3
ii libcups2 2.3.0-7
ii libcupsfilters1 1.25.13-1
ii libglib2.0-0 2.62.3-2
ii libldap-2.4-2 2.4.48+dfsg-1+b2
ii lsb-base 11.1.0

Versions of packages cups-browsed recommends:
ii avahi-daemon 0.7-4+b1

cups-browsed suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
All,

I upgraded to 1.26.0-1 and the printers show up again. Not sure what you did
Till, but it seems to have work.

I take the liberty to close the report, should somebody else still see the
problem, please reopen it.

Thanks for your help.

Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL--- End Message ---

Bug#946937: marked as done (python-django: CVE-2019-19844: Potential account hijack via password reset form)

Your message dated Mon, 30 Dec 2019 11:04:49 +
with message-id 
and subject line Bug#946937: fixed in python-django 2:3.0.1-1
has caused the Debian Bug report #946937,
regarding python-django: CVE-2019-19844: Potential account hijack via password 
reset form
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.)


-- 
946937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2019-19844[0][1]: Potential account hijack via password
reset form

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-19844
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19844
[1] https://www.djangoproject.com/weblog/2019/dec/18/security-releases/


Regards,

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

We believe that the bug you reported is fixed in the latest version of
python-django, 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.
Chris Lamb  (supplier of updated python-django 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:44:01 +
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 2:3.0.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Closes: 946937
Changes:
 python-django (2:3.0.1-1) experimental; urgency=medium
 .
   * New upstream security release.
 
 (Closes: #946937)
Checksums-Sha1:
 0eb681c2ae72f3f635e38e333a2915c5eb2e6cf1 2769 python-django_3.0.1-1.dsc
 accee8de35164919fdb22b87e13324f14cfa2c0e 9022787 
python-django_3.0.1.orig.tar.gz
 1dd1fa8eec158cedeb041c8ab1ac80f841ad2224 25820 
python-django_3.0.1-1.debian.tar.xz
 90efe3e1b8fbe91de993b5191acaf2da88dd2aac 7436 
python-django_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 d7ae70bb7bc40551ee344869cdbf4b2866f5d0e14df2ecc63e1fe42bbd0abb10 2769 
python-django_3.0.1-1.dsc
 315b11ea265dd15348d47f2cbb044ef71da2018f6e582fed875c889758e6f844 9022787 
python-django_3.0.1.orig.tar.gz
 1a2e12496db4d006fdd249ba0d017ec09a2d654e7700abbcebbd6ce63923d286 25820 
python-django_3.0.1-1.debian.tar.xz
 cc7edfad9ca17db869a3c077ec332a2121d200578844642f2a35a437bb14230e 7436 
python-django_3.0.1-1_amd64.buildinfo
Files:
 2700c05b718ee83350c3c60673409494 2769 python optional python-django_3.0.1-1.dsc
 12f434ed7ccd6ee57be6f05a45e20e97 9022787 python optional 
python-django_3.0.1.orig.tar.gz
 39353e1e85078d8a1f86d88a90df1d52 25820 python optional 
python-django_3.0.1-1.debian.tar.xz
 554ac167f0654958673a3875b3a7abd0 7436 python optional 
python-django_3.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl4J1jkACgkQHpU+J9Qx
HljdgxAAkQu8AQMluyf2+VCLSuzIsCyLWFDRTwDjF4vygYB8Xh1Ut3sBaLd/tr69
jqP2MbCwQaMbVzya6U8ACOwIQUeCgcWzoLCY26To9rdNzTUL0kjBdbjF7s35icU/
4FuC2tgAZFDAFbiptouPoTofLRnVmXkMCwgnAWFHktsi87Pa/XsugW40bS3xNx6t
F8h4iP+lz6pMjQoAuLo1ZCjYLP4oyGuvx+/gmupf+JR4AL5gD6eJeQpvhhmkELDq
Rq02yH+F7SPlOY+PZvdSUWWCvAUStVTCVK/ee463d1vqXU5HsTRqMN1ysDWsVgZN
zYi3jhaO3j3nN/3IWiwpRi6H755c9oFdmzuz+L5keGCrdvZTm2Zbzb75UgSVFgit
+gJQ2wHw1/xHSca0GtUjhh6/B2D3URIDVV4fEV01d3V1D/g0VyA96yfv7yoHCL2Y
dpMbMH8TXLhn2JMQOjHeaCESbylhR0BCYZXqQYbmn6Jpy+mWbj/8GtXez0joUjEl
Qe8ldzOBecLcXP3/1e75K4Ege9tsV6zdbekBFd9OTTBcNug83gKwtNX2wrTGegRp
/Bj3JcMplDKOixij4BuNC+6HHRXbs2IYkq75kk+2VJkQwPnkNcW2Kik2ODgzR5TC
STfnQzP1xZjUpV098naUyYTc952PIkc09R/3hxO+vge8J3E2zSs=
=A7JO
-END PGP SIGNATURE End Message ---

Bug#925830: marked as done (sip-tester: ftbfs with GCC-9)

Your message dated Mon, 30 Dec 2019 10:04:34 +
with message-id 
and subject line Bug#925830: fixed in sip-tester 1:3.6.0-1
has caused the Debian Bug report #925830,
regarding sip-tester: 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.)


-- 
925830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925830
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sip-tester
Version: 1:3.5.2-1
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/sip-tester_3.5.2-1_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.

[...]
 from /usr/include/c++/9/bits/locale_classes.h:40,
 from /usr/include/c++/9/bits/ios_base.h:41,
 from /usr/include/c++/9/ios:42,
 from /usr/include/c++/9/ostream:38,
 from /usr/include/c++/9/iterator:64,
 from src/call.cpp:41:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:35: note: 
'__builtin___snprintf_chk' output between 18 and 2075 bytes into a destination 
of size 64
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ~^~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
src/call.cpp:846:31: warning: '%s' directive output may be truncated writing up 
to 2048 bytes into a region of size 64 [-Wformat-truncation=]
  846 | snprintf(tmpbuf, 64, "%s (send timeout %u)", s, send_timeout);
  |   ^~ ~
In file included from /usr/include/stdio.h:873,
 from /usr/include/c++/9/cstdio:42,
 from /usr/include/c++/9/ext/string_conversions.h:43,
 from /usr/include/c++/9/bits/basic_string.h:6489,
 from /usr/include/c++/9/string:55,
 from /usr/include/c++/9/bits/locale_classes.h:40,
 from /usr/include/c++/9/bits/ios_base.h:41,
 from /usr/include/c++/9/ios:42,
 from /usr/include/c++/9/ostream:38,
 from /usr/include/c++/9/iterator:64,
 from src/call.cpp:41:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:67:35: note: 
'__builtin___snprintf_chk' output between 18 and 2075 bytes into a destination 
of size 64
   67 |   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  |  ~^~~
   68 |__bos (__s), __fmt, __va_arg_pack ());
  |~
g++ -DHAVE_CONFIG_H  -DPCAPPLAY -DRTP_STREAM -DUSE_SCTP -DHAVE_GSL -DHAVE_EPOLL 
-I. -I./include   -Wdate-time -D_FORTIFY_SOURCE=2 -D__LINUX -I./include -Wall 
-pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
src/sipp-deadcall.o `test -f 'src/deadcall.cpp' || echo './'`src/deadcall.cpp
g++ -DHAVE_CONFIG_H  -DPCAPPLAY -DRTP_STREAM -DUSE_SCTP -DHAVE_GSL -DHAVE_EPOLL 
-I. -I./include   -Wdate-time -D_FORTIFY_SOURCE=2 -D__LINUX -I./include -Wall 
-pedantic  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
src/sipp-infile.o `test -f 'src/infile.cpp' || e

Processed: Set fixed version