Bug#954219: pyresample: autopkgtest failures (AttributeError: module 'pyproj._proj' has no attribute 'Proj')

[Sebastiaan Couwenberg]

Note this change between pyproj 2.5.0 & 2.6.0:

 --- a/pyproj/_proj.pxd
 +++ b/pyproj/_proj.pxd
 @@ -1,6 +1,6 @@
  include "proj.pxi"

 -cdef class Proj:
 +cdef class _Proj:
  cdef PJ * projobj
  cdef PJ_CONTEXT* context
  cdef PJ_PROJ_INFO projobj_info


Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: libperlspeak-perl: CVE-2020-10674

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + stretch buster bullseye sid
Bug #954238 [src:libperlspeak-perl] libperlspeak-perl: CVE-2020-10674
Added tag(s) sid, stretch, buster, and bullseye.

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

Bug#954238: libperlspeak-perl: CVE-2020-10674

[Salvatore Bonaccorso]

Source: libperlspeak-perl
Version: 2.01-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=132173
Control: tags -1 + stretch buster bullseye sid

Hi,

The following vulnerability was published for libperlspeak-perl.

CVE-2020-10674[0]:
| PerlSpeak through 2.01 allows attackers to execute arbitrary OS
| commands, as demonstrated by use of system and 2-argument open.

Gregor, the module seem to be basically unmaintained, I would propose
to actually remove the package from unstable and likely given there
are no reverse dependencies as well from any other suite.  What do you
think?

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-2020-10674
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-10674
[1] https://rt.cpan.org/Public/Bug/Display.html?id=132173

Regards,
Salvatore

Bug#954236: marked as done (python3-bleach: New secuirty issue: mutation XSS (again))

[Debian Bug Tracking System]

Your message dated Thu, 19 Mar 2020 04:19:36 +
with message-id 
and subject line Bug#954236: fixed in python-bleach 3.1.3-1
has caused the Debian Bug report #954236,
regarding python3-bleach: New secuirty issue: mutation XSS (again)
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.)


-- 
954236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-bleach
Version: 3.1.1-0+deb10u1
Severity: serious
Tags: security upstream

>From the upstream CHANGES for 3.1.2, which I just noticed:

**Security fixes**

* ``bleach.clean`` behavior parsing embedded MathML and SVG content
  with RCDATA tags did not match browser behavior and could result in
  a mutation XSS.

  Calls to ``bleach.clean`` with ``strip=False`` and ``math`` or
  ``svg`` tags and one or more of the RCDATA tags ``script``,
  ``noscript``, ``style``, ``noframes``, ``iframe``, ``noembed``, or
  ``xmp`` in the allowed tags whitelist were vulnerable to a mutation
  XSS.

  This security issue was confirmed in Bleach version v3.1.1. Earlier
  versions are likely affected too.

  Anyone using Bleach <=v3.1.1 is encouraged to upgrade.

  https://bugzilla.mozilla.org/show_bug.cgi?id=1621692

The mozilla bug is not public

Scott K
--- End Message ---
--- Begin Message ---
Source: python-bleach
Source-Version: 3.1.3-1
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-bleach 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 19 Mar 2020 00:04:59 -0400
Source: python-bleach
Architecture: source
Version: 3.1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Closes: 954236
Changes:
 python-bleach (3.1.3-1) unstable; urgency=medium
 .
   * Tests re-enabled now the python3.7/3.8 have reverted the problematic
 change
   * New upstream security release (Closes: #954236)
Checksums-Sha1:
 94bf7daf961e3c1e50249c6aa27a804c1e46e97b 2521 python-bleach_3.1.3-1.dsc
 17ac84c2081e006a3b3cf524c8c5ec11d0dae47f 161167 python-bleach_3.1.3.orig.tar.gz
 c610c4c1670e99baf05704d9eb17031a60c02689 5252 
python-bleach_3.1.3-1.debian.tar.xz
 203ce7ac2fe3d809c6261f41fa596b0cb39fbe1e 7024 
python-bleach_3.1.3-1_source.buildinfo
Checksums-Sha256:
 436d16f21c230f33bb57544101ffee80ac7311c1ae781ea2714f351d8fbfee4e 2521 
python-bleach_3.1.3-1.dsc
 beb2210a4a6e307270b3884469e5f44e3d83f512b9e17973d9a649c73c029cb3 161167 
python-bleach_3.1.3.orig.tar.gz
 1415c2505c92f8f05f82572475cc1dd6186fc6d37d6f79cd96531fddc99820cd 5252 
python-bleach_3.1.3-1.debian.tar.xz
 0c2ec57f13687ff56471c1460e9237f89c4dcafc1e22b7b3a289728f9a4dc914 7024 
python-bleach_3.1.3-1_source.buildinfo
Files:
 d8cf83629cb4459846c37c8adf094048 2521 python optional python-bleach_3.1.3-1.dsc
 995410de0eff35dcbe4ed1c25d29cb8e 161167 python optional 
python-bleach_3.1.3.orig.tar.gz
 dad26d4beaa06932b14fee44db43939b 5252 python optional 
python-bleach_3.1.3-1.debian.tar.xz
 d6ac6a910868bfc92ce4f33c35aaf876 7024 python optional 
python-bleach_3.1.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl5y74QACgkQeNfe+5rV
mvFnUxAAgntSKEQI01b3dfQ+EJ3YNvC8irOXQDd0s34gH1OJ00MBnw+40Jf+Bg5m
G4sPCXeguDuTSQH5GAiDNEDAOOwgS4rVN17HdxLlS75Ts55E8jCaWu3HEyJYkBrO
yYkxX47CkeTJbqOD1cbVU9upE8A60/q8Kb4V1m2m3xHTq5V457Q9JR8GhudJ/QI7
dCnXnA1X6kQaBl+IX5Uq5VbCoPrYuxXAXuWtl8/jFlkvHROO6Qj5mgG7IpCfROBI
NzBgtWe3ucNyVxnhENZs39hsJajgWrX6u7rdIiGelg07MezaW3H9SAmqN+Hc8xnu
tyNhCN1TzbS0YhPRu0l3Dvro5eSUZw5J2Wq5RoWOQgGiD78/ZPkA3YD8BgxVQtqj
c2dlbT3Bf1Rw7RNbKqexc0yTXgBlGvI8k7doUlQlcxd2VSf8s4d+Yv/B79/zB9lH
/huiXWeGR7K1XFsD9p1p7W/xVq5O13WnbupHBL6rPTRJjajZNubMmrw+03N8jdbF
i5J5gFttzEUhAj9cJzHw931takCMA1QncLgTmJnloaHiXrdAWPJAWnzCVk4F1OPZ
Ia0AyP9pxgyN5KR/1phyhFD/lJP0YbUsSGmwO9JZjKnOVJVmAOkdLB3lOugBGcDM
pwRp38LEj32gHduWJ1br6q9TTsmmnjhPAxOR3fkT4ktTVSMouqw=
=Shx1
-END PGP SIGNATURE En

Bug#954236: Proposed Buster Fix (pyhon3-bleach: New secuirty issue: mutation XSS (again))

[Scott Kitterman]

Upstream's 3.1.2 release had just the security fix in it.  I propose updating 
buster with it (I put 3.1.3 in unstable, but it had non-security fixes in it.

I'm not 100% sure about if we need to modify the import path for the new test 
since we don't use the vendored html5lib, but other than that (which I will 
investigate), this should be good.

Scott Kdiff -Nru python-bleach-3.1.1/bleach/html5lib_shim.py python-bleach-3.1.2/bleach/html5lib_shim.py
--- python-bleach-3.1.1/bleach/html5lib_shim.py	2020-02-19 12:34:12.0 -0500
+++ python-bleach-3.1.2/bleach/html5lib_shim.py	2020-03-17 10:26:44.0 -0400
@@ -533,7 +533,18 @@
 
 
 class BleachHTMLSerializer(HTMLSerializer):
-"""HTMLSerializer that undoes & -> & in attributes"""
+"""HTMLSerializer that undoes & -> & in attributes and sets
+escape_rcdata to True
+"""
+
+# per the HTMLSerializer.__init__ docstring:
+#
+# Whether to escape characters that need to be
+# escaped within normal elements within rcdata elements such as
+# style.
+#
+escape_rcdata = True
+
 def escape_base_amp(self, stoken):
 """Escapes just bare & in HTML attribute values"""
 # First, undo escaping of &. We need to do this because html5lib's
diff -Nru python-bleach-3.1.1/bleach/__init__.py python-bleach-3.1.2/bleach/__init__.py
--- python-bleach-3.1.1/bleach/__init__.py	2020-02-19 12:34:12.0 -0500
+++ python-bleach-3.1.2/bleach/__init__.py	2020-03-17 10:26:44.0 -0400
@@ -18,9 +18,9 @@
 
 
 # mmdd
-__releasedate__ = '20200213'
+__releasedate__ = '20200311'
 # x.y.z or x.y.z.dev0 -- semver
-__version__ = '3.1.1'
+__version__ = '3.1.2'
 VERSION = parse_version(__version__)
 
 
diff -Nru python-bleach-3.1.1/CHANGES python-bleach-3.1.2/CHANGES
--- python-bleach-3.1.1/CHANGES	2020-02-19 12:34:12.0 -0500
+++ python-bleach-3.1.2/CHANGES	2020-03-17 10:26:44.0 -0400
@@ -1,6 +1,40 @@
 Bleach changes
 ==
 
+Version 3.1.2 (March 11th, 2020)
+
+
+**Security fixes**
+
+* ``bleach.clean`` behavior parsing embedded MathML and SVG content
+  with RCDATA tags did not match browser behavior and could result in
+  a mutation XSS.
+
+  Calls to ``bleach.clean`` with ``strip=False`` and ``math`` or
+  ``svg`` tags and one or more of the RCDATA tags ``script``,
+  ``noscript``, ``style``, ``noframes``, ``iframe``, ``noembed``, or
+  ``xmp`` in the allowed tags whitelist were vulnerable to a mutation
+  XSS.
+
+  This security issue was confirmed in Bleach version v3.1.1. Earlier
+  versions are likely affected too.
+
+  Anyone using Bleach <=v3.1.1 is encouraged to upgrade.
+
+  https://bugzilla.mozilla.org/show_bug.cgi?id=1621692
+
+**Backwards incompatible changes**
+
+None
+
+**Features**
+
+None
+
+**Bug fixes**
+
+None
+
 Version 3.1.1 (February 13th, 2020)
 ---
 
diff -Nru python-bleach-3.1.1/debian/changelog python-bleach-3.1.2/debian/changelog
--- python-bleach-3.1.1/debian/changelog	2020-02-27 05:53:52.0 -0500
+++ python-bleach-3.1.2/debian/changelog	2020-03-19 00:14:11.0 -0400
@@ -1,3 +1,9 @@
+python-bleach (3.1.2-0+deb10u1) buster; urgency=medium
+
+  * New upstream security release (Closes: #954236)
+
+ -- Scott Kitterman   Thu, 19 Mar 2020 00:14:11 -0400
+
 python-bleach (3.1.1-0+deb10u1) buster-security; urgency=high
 
   * New upstream security release (Closes: #951907)
diff -Nru python-bleach-3.1.1/requirements-dev.txt python-bleach-3.1.2/requirements-dev.txt
--- python-bleach-3.1.1/requirements-dev.txt	2020-02-19 12:34:12.0 -0500
+++ python-bleach-3.1.2/requirements-dev.txt	2020-03-17 10:26:44.0 -0400
@@ -11,3 +11,6 @@
 
 # Requirements for updating package
 twine
+
+# Requirements for running setup.py bdist_wheel
+wheel
diff -Nru python-bleach-3.1.1/tests/test_clean.py python-bleach-3.1.2/tests/test_clean.py
--- python-bleach-3.1.1/tests/test_clean.py	2020-02-19 12:34:12.0 -0500
+++ python-bleach-3.1.2/tests/test_clean.py	2020-03-17 10:26:44.0 -0400
@@ -5,7 +5,7 @@
 from bleach import clean
 from bleach.html5lib_shim import Filter
 from bleach.sanitizer import Cleaner
-
+from bleach._vendor.html5lib.constants import rcdataElements
 
 def test_clean_idempotent():
 """Make sure that applying the filter twice doesn't change anything."""
@@ -787,7 +787,7 @@
 (
 raw_tag,
 "<%s>" % raw_tag,
-"<%s>" % raw_tag,
+"<%s>" % raw_tag,
 )
 for raw_tag in _raw_tags
 ],
@@ -797,6 +797,29 @@
 assert clean(data, tags=["noscript", raw_tag]) == expected
 
 
+@pytest.mark.parametrize(
+"namespace_tag, rc_data_element_tag, data, expected",
+[
+(
+namespace_tag,
+rc_data_element_tag,
+"<%s><%s>" % (namespace_tag, rc_data_element_tag),
+"<%s><%s>" % (

Bug#954236: marked as pending in python-bleach

[Scott Kitterman]

Control: tag -1 pending

Hello,

Bug #954236 in python-bleach 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-bleach/-/commit/fcd2bca75fad881ac55591d9f8c97b773a35da7f


New upstream security release (Closes: #954236)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954236

Processed: Bug#954236 marked as pending in python-bleach

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954236 [python3-bleach] python3-bleach: New secuirty issue: mutation XSS 
(again)
Added tag(s) pending.

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

Bug#954236: python3-bleach: New secuirty issue: mutation XSS (again)

[Scott Kitterman]

Package: python3-bleach
Version: 3.1.1-0+deb10u1
Severity: serious
Tags: security upstream

>From the upstream CHANGES for 3.1.2, which I just noticed:

**Security fixes**

* ``bleach.clean`` behavior parsing embedded MathML and SVG content
  with RCDATA tags did not match browser behavior and could result in
  a mutation XSS.

  Calls to ``bleach.clean`` with ``strip=False`` and ``math`` or
  ``svg`` tags and one or more of the RCDATA tags ``script``,
  ``noscript``, ``style``, ``noframes``, ``iframe``, ``noembed``, or
  ``xmp`` in the allowed tags whitelist were vulnerable to a mutation
  XSS.

  This security issue was confirmed in Bleach version v3.1.1. Earlier
  versions are likely affected too.

  Anyone using Bleach <=v3.1.1 is encouraged to upgrade.

  https://bugzilla.mozilla.org/show_bug.cgi?id=1621692

The mozilla bug is not public

Scott K

Processed: py2removal bugs severity updates - 2020-03-19 03:38:22.829617+00:00

[Debian Bug Tracking System]

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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-pathlib is a module and has 0 external rdeps or not in testing
> severity 938003 serious
Bug #938003 [src:python-pathlib] python-pathlib: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#952822: marked as done (/etc/zfs/zed.d configuration is clobbered on upgrade)

[Debian Bug Tracking System]

Your message dated Thu, 19 Mar 2020 03:21:03 +
with message-id 
and subject line Bug#952822: fixed in zfs-linux 0.8.3-2
has caused the Debian Bug report #952822,
regarding /etc/zfs/zed.d configuration is clobbered on upgrade
to be marked as done.

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

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


-- 
952822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zfs-zed
Version: 0.8.3-1
Severity: serious
Tags: patch
Justification: Policy 10.7.3

Please see my MR on salsa [1], which should address this policy violation.  In 
short: the symlinks shipped
by zfs-zed in /etc/zfs/zed.d are not tracked as conffiles by dpkg, so they 
re-appear even after being
deleted.

Antonio


[1] https://salsa.debian.org/zfsonlinux-team/zfs/-/merge_requests/21
--- End Message ---
--- Begin Message ---
Source: zfs-linux
Source-Version: 0.8.3-2
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated zfs-linux package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Mar 2020 10:58:53 +0800
Source: zfs-linux
Architecture: source
Version: 0.8.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian ZFS on Linux maintainers 

Changed-By: Mo Zhou 
Closes: 949911 952822
Changes:
 zfs-linux (0.8.3-2) unstable; urgency=medium
 .
   [ Richard Laager ]
   * cron: Do not error if already scrubbing
 .
   [ Antonio Russo ]
   * [dracut] include zfs-load-module.service
   * Preserve /etc/zfs/zed.d configuration on upgrade (Closes: #952822)
 .
   [ Mo Zhou ]
   * Reword ZFS Description, thanks to Richard Laager (Closes: #949911)
   * Import patches from Ubuntu delta (0.8.3-1ubuntu3).
 + Apply 2100-zfs-load-module.patch and add this new service.
 + The rest Ubuntu specific patches are left in the comment.
   * Refresh upstream Git repo URL in d/copyright.
   * Sync patchset with Ubuntu diff (= 0.8.3-1ubuntu8).
 + Cherry-pick patches for Linux 5.5, 5.6 support.
 + Rest patches are unapplied (can reduce Debian/Ubuntu debdiff).
 + Many thanks to Ubuntu developers.
   * Import the Ubuntu version of tests/control as tests/control.ubuntu
   * Autopkgtest: Reconfigure before testing binary kmod pkg builds.
Checksums-Sha1:
 dd9c4510b0748df454fda6469c3e9f458e6916db 3421 zfs-linux_0.8.3-2.dsc
 90b887cf9b2d6bf75edcdfe906d25bc85c600ee9 77568 zfs-linux_0.8.3-2.debian.tar.xz
 c481fca8af288995386fe99253a2238daea2dfef 8405 
zfs-linux_0.8.3-2_source.buildinfo
Checksums-Sha256:
 d1653d9958c5eedb26bfed79e0c0b01a652ac33eb8bfead9b8940847b6ee9c59 3421 
zfs-linux_0.8.3-2.dsc
 223ab68912a40afb7e5168103bdc903523241f878fb480cfdcfcfeb4c77bff9a 77568 
zfs-linux_0.8.3-2.debian.tar.xz
 6d6585fd7ec16ff1e40ded23c828afedde5a60136923cc9aea011f034254 8405 
zfs-linux_0.8.3-2_source.buildinfo
Files:
 c2f6ea8cf182defcd0941b948e7f04b3 3421 contrib/kernel optional 
zfs-linux_0.8.3-2.dsc
 b56bef77f7fade889db9bf0dceffb5e0 77568 contrib/kernel optional 
zfs-linux_0.8.3-2.debian.tar.xz
 015cce30f7833ecda791c8cb5ec1b81b 8405 contrib/kernel optional 
zfs-linux_0.8.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAl5y4CgRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaoq4ew//RAofGBIAXwzTsxicG4cHPvAuL62fn5H4
lK3cwZdCdH/AcDzy6PUr8IktTAJEsMkOfi9E8txqVQRjoGvcKBvfxZKyRJULepU1
tM3Rh5ydW9gfUwulmoQl6RwHe1pU2Bz5YEJ4XVJKyTFmks6S6NazKBg4V+BHriSs
IL9I/99vg+WTperbp66yLS3a39JS8rO5RvTyAY6FFqCR2WtnPifkqNONKYWid2tq
qlgb8N5TN7rDvoqxHFgkNTd2V4xSOr6P7bVixgnMmmiahRRntz1IhJEDN/FnhWUA
9I2EcGErz0A1ZURzDAP4F3BCavy0I1dYo+W5JWbyZ+FP3P8m3A8ZmKBPZW0eZ1/8
YxbxwMknCM5neaKQpIQPjzexI4eafGFB6x8L08YJBlzOq71E5xxkrx51hByTnE7n
NAhCz+eDjbgTokZb1+LeQLHFOePOL1g4QFCMXjKFXREnjSV5/EyBSvmSO2apMaho
3DT3vj5oKO2z80IC+vZvRcNcdeLmWjTlw8xdKK9ezGbz6WUbRjN8hXivCIoqXQd/
H+JtdDm8Cerm+1Yjmink1ntZkM2gzp4KuIJmSUn9jdnt+wZNzw0hxKRdqmwxy8YJ
bqCdN9NTLOonSiAbqTx7ZvSq+DKCGqnmGczvCUhjy6rUMc/Qt3f/8ywq4VqZIa2Z
FVmDxeA1xSM=
=PdEq
-END PGP SIGNATURE End Message -

Processed: py2removal bugs severity updates - 2020-03-19 02:38:03.246520+00:00

[Debian Bug Tracking System]

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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # pydxcluster is an application, has low popcon (62 < 300), and has 0 
> external rdeps or not in testing
> severity 945731 serious
Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye
Bug #912495 [src:pydxcluster] pydxcluster: Please migrate to python3-pygame
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> # kiki-the-nano-bot is an application, has low popcon (152 < 300), and has 0 
> external rdeps or not in testing
> severity 936796 serious
Bug #936796 [src:kiki-the-nano-bot] kiki-the-nano-bot: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # lepton-eda is an application, has low popcon (151 < 300), and has 0 
> external rdeps or not in testing
> severity 936839 serious
Bug #936839 [src:lepton-eda] lepton-eda: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pymissile is an application, has low popcon (121 < 300), and has 0 external 
> rdeps or not in testing
> severity 943176 serious
Bug #943176 [src:pymissile] pymissile: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # ardentryst is an application, has low popcon (164 < 300), and has 0 
> external rdeps or not in testing
> severity 936148 serious
Bug #936148 [src:ardentryst] ardentryst: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # snowballz is an application, has low popcon (149 < 300), and has 0 external 
> rdeps or not in testing
> severity 938509 serious
Bug #938509 [src:snowballz] snowballz: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # tennix is an application, has low popcon (73 < 300), and has 0 external 
> rdeps or not in testing
> severity 938647 serious
Bug #938647 [src:tennix] tennix: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pd-py is an application, has low popcon (80 < 300), and has 0 external 
> rdeps or not in testing
> severity 937266 serious
Bug #937266 [src:pd-py] pd-py: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # yorick-yao is an application, has low popcon (258 < 300), and has 0 
> external rdeps or not in testing
> severity 945726 serious
Bug #945726 [src:yorick-yao] yorick-yao: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
912495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912495
936148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936148
936796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936796
936839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936839
937266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937266
938509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938509
938647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938647
943176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943176
945726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945726
945731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: py2removal bugs severity updates - 2020-03-19 01:57:52.253665+00:00

[Debian Bug Tracking System]

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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # not all bin pkgs are leaf for src:pydxcluster, lower severity
> severity 945731 normal
Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye
Bug #912495 [src:pydxcluster] pydxcluster: Please migrate to python3-pygame
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:kiki-the-nano-bot, lower severity
> severity 936796 normal
Bug #936796 [src:kiki-the-nano-bot] kiki-the-nano-bot: Python2 removal in 
sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:lepton-eda, lower severity
> severity 936839 normal
Bug #936839 [src:lepton-eda] lepton-eda: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:pymissile, lower severity
> severity 943176 normal
Bug #943176 [src:pymissile] pymissile: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:ardentryst, lower severity
> severity 936148 normal
Bug #936148 [src:ardentryst] ardentryst: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:snowballz, lower severity
> severity 938509 normal
Bug #938509 [src:snowballz] snowballz: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:tennix, lower severity
> severity 938647 normal
Bug #938647 [src:tennix] tennix: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:pd-py, lower severity
> severity 937266 normal
Bug #937266 [src:pd-py] pd-py: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> # not all bin pkgs are leaf for src:yorick-yao, lower severity
> severity 945726 normal
Bug #945726 [src:yorick-yao] yorick-yao: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
912495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912495
936148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936148
936796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936796
936839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936839
937266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937266
938509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938509
938647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938647
943176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943176
945726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945726
945731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 953205 in 2:5.2.3+dfsg-1

[Debian Bug Tracking System]

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

> found 953205 2:5.2.3+dfsg-1
Bug #953205 [ruby-activesupport] "NameError: uninitialized constant 
URI::Generic" on upgrade
Marked as found in versions rails/2:5.2.3+dfsg-1.
> thanks
Stopping processing here.

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

Bug#952040: marked as done (ruby-innertube: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 22:09:47 +
with message-id 
and subject line Bug#952040: fixed in ruby-innertube 1.1.0-5
has caused the Debian Bug report #952040,
regarding ruby-innertube: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:
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.)


-- 
952040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-innertube
Version: 1.1.0-4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> LoadError:
>   cannot load such file -- thwait
> # ./spec/innertube_spec.rb:3:in `'
> Run options: include {:focus=>true}
> 
> All examples were filtered out; ignoring {:focus=>true}
> No examples found.
> 
> 
> Deprecation Warnings:
> 
>  The VerboseFormatter formatter uses the deprecated formatter interface not 
> supported directly by RSpec 3.  To continue to use this formatter you must 
> install the `rspec-legacy_formatters` gem, which provides support for legacy 
> formatters or upgrade the formatter to a compatible version.  Formatter added 
> at: /<>/spec/support/verbose_formatter.rb:111:in `block in  (required)>'
> 
> 
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
> 
> 1 deprecation warning total
> 
> Finished in 0.4 seconds (files took 0.1502 seconds to load)
> 0 examples, 0 failures, 1 error occurred outside of examples
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*_spec.rb failed
> ERROR: Test "ruby2.7" failed: 

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/ruby-innertube_1.1.0-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-innertube
Source-Version: 1.1.0-5
Done: Lucas Kanashiro 

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

Debian distribution maintenance software
pp.
Lucas Kanashiro  (supplier of updated 
ruby-innertube package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Mar 2020 18:39:00 -0300
Source: ruby-innertube
Architecture: source
Version: 1.1.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Lucas Kanashiro 
Closes: 952040
Changes:
 ruby-innertube (1.1.0-5) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci.yml
 .
   [ Lucas Kanashiro ]
   * Add b-d on ruby-thwait (Closes: #952040)
   * Declare compliance with Debian Policy 4.5.0
   * d/control: rules does not require rules
   * Do not runtime depend on the ruby interpreter
   * Bump debhelper compatibility level to 12
   * d/watch: update to use gemwatch.debian.net
Checksums-Sha1:
 c82e8182f9d4527055b0af677fb2c81066d4e473 2128 ruby-innertube_1.1.0-5.dsc
 c1e6840b89987d1108856345aafd82c08230dbf3 4268 
ruby-innertube_1.1.0-5.debian.tar.xz
Checksums-Sha256:
 22ad00427aaeaf224ea357e98a5b2b5238fc5554c88549076e0c329b79b1ea66 2128 
ruby-innertube_1.1.0-5.dsc
 63331b68bcda5def962de5b3ec73287b35ea0419e1d7a6c80e4bba9949fb3d23 4268 
ruby-innertube_1.1.0-5.debian.tar.xz
Files:
 4b72c3b700019f451350d81cd1a3cb82 2128 ruby optional ruby-innertube_1.1.0-5.dsc
 fcf3bf42b70aeb6

Bug#948416: marked as done (automat ftbfs, tests fail with Python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 22:08:43 +
with message-id 
and subject line Bug#948416: fixed in automat 0.8.0-1
has caused the Debian Bug report #948416,
regarding automat ftbfs, tests fail with Python 3.8
to be marked as done.

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

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


-- 
948416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:automat
Version: 0.6.0-1
Severity: serious
Tags: sid bullseye patch

The automat tests fail with Python 3.8, apparently fixed in 0.8.0.
Example packaging at https://launchpad.net/ubuntu/+source/automat/0.8.0-0ubuntu1

==
ERROR: test_badTransitionForCurrentState
(automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_test/test_methodical.py",
line 385, in test_badTransitionForCurrentState
machine.deadEnd()
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_methodical.py",
line 126, in __get__
def doInput(*args, **kwargs):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 39, in decorator
return copyfunction(decorated,
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 31, in copyfunction
return function(copycode(template.__code__, codechanges), *values)
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 19, in copycode
return code(*values)
TypeError: an integer is required (got type bytes)

==
ERROR: test_collectOutputs (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_test/test_methodical.py",
line 169, in test_collectOutputs
self.assertEqual(m.input(), "AB")
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_methodical.py",
line 126, in __get__
def doInput(*args, **kwargs):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 39, in decorator
return copyfunction(decorated,
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 31, in copyfunction
return function(copycode(template.__code__, codechanges), *values)
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 19, in copycode
return code(*values)
TypeError: an integer is required (got type bytes)

==
ERROR: test_inputFunctionsMustBeEmpty
(automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_test/test_methodical.py",
line 244, in test_inputFunctionsMustBeEmpty
MechanismWithDocstring().input()
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_methodical.py",
line 126, in __get__
def doInput(*args, **kwargs):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 39, in decorator
return copyfunction(decorated,
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 31, in copyfunction
return function(copycode(template.__code__, codechanges), *values)
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 19, in copycode
return code(*values)
TypeError: an integer is required (got type bytes)

==
ERROR: test_inputWithArguments (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_test/test_methodical.py",
line 209, in test_inputWithArguments
self.assertEqual(m.input(3), [4])
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_methodical.py",
line 126, in __get__
def doInput(*args, **kwargs):
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 39, in decorator
return copyfunction(decorated,
  File
"/<>/.pybuild/cpython3_3.8_automat/build/automat/_introspection.py",
line 31, in copyfunction
return function(copycode(template.__code__, codechanges), *values)
  File
"/<>/.pybuild/cpython3_3.8_automat/b

Bug#948416: marked as pending in automat

[Scott Kitterman]

Control: tag -1 pending

Hello,

Bug #948416 in automat 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/automat/-/commit/346c60e48f1c8fe8f3598288946bd889343100fb


* New upstream release (Closes: #948416)
  - Refresh patches


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948416

Processed: Bug#948416 marked as pending in automat

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948416 [src:automat] automat ftbfs, tests fail with Python 3.8
Added tag(s) pending.

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

Bug#952040: marked as pending in ruby-innertube

[Lucas Kanashiro]

Control: tag -1 pending

Hello,

Bug #952040 in ruby-innertube 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/ruby-team/ruby-innertube/-/commit/1e3c8cf7055aa3a26e418c244157fd21b7271d71


Add b-d on ruby-thwait (Closes: #952040)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952040

Processed: Bug#952040 marked as pending in ruby-innertube

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952040 [src:ruby-innertube] ruby-innertube: FTBFS: ERROR: Test "ruby2.7" 
failed: LoadError:
Added tag(s) pending.

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

Bug#953942: Removed package(s) from unstable

[Michael Banck]

On Wed, Mar 18, 2020 at 02:48:51AM +, Debian FTP Masters wrote:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
> 
>   jack | 3.1.1+cvs20050801-31 | source, amd64, arm64, armel, armhf, i386, 
> mips64el, mipsel, ppc64el, s390x

Great Job!


Michael

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

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 21:27:13 +
with message-id 
and subject line Bug#954225: Removed package(s) from unstable
has caused the Debian Bug report #937636,
regarding python-cddb: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-cddb

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

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

Dear submitter,

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

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

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

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

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

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

Bug#952080: marked as done (ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 20:39:08 +
with message-id 
and subject line Bug#952080: fixed in ruby-faker 1.9.1-2
has caused the Debian Bug report #952080,
regarding ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.
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.)


-- 
952080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-faker
Version: 1.9.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-faker/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"faker\"
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-faker/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.7 -w -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/test_array_sample_method_compat.rb" "test/test_avatar.rb" 
> "test/test_bg_locale.rb" "test/test_ca_cat_locale.rb" 
> "test/test_ca_locale.rb" "test/test_country_code.rb" 
> "test/test_da_dk_locale.rb" "test/test_de_at_locale.rb" 
> "test/test_de_ch_locale.rb" "test/test_de_locale.rb" 
> "test/test_determinism.rb" "test/test_ee_locale.rb" 
> "test/test_en_au_locale.rb" "test/test_en_au_ocker_locale.rb" 
> "test/test_en_ca_locale.rb" "test/test_en_gb_locale.rb" 
> "test/test_en_ind_locale.rb" "test/test_en_locale.rb" 
> "test/test_en_ms_locale.rb" "test/test_en_nep_locale.rb" 
> "test/test_en_ng_locale.rb" "test/test_en_nz_locale.rb" 
> "test/test_en_pak_locale.rb" "test/test_en_sg_locale.rb" 
> "test/test_en_ug_locale.rb" "test/test_en_us_locale.rb" 
> "test/test_es_locale.rb" "test/test_es_mx_locale.rb" "test/test_fa_locale.rb" 
> "test/test_faker.rb" "test/test_faker_address.rb" 
> "test/test_faker_ancient.rb" "test/test_faker_app.rb" 
> "test/test_faker_appliance.rb" "test/test_faker_aqua_teen_hunger_force.rb" 
> "test/test_faker_artist.rb" "test/test_faker_back_to_the_future.rb" 
> "test/test_faker_bank.rb" "test/test_faker_beer.rb" 
> "test/test_faker_birthday_in_leap_year.rb" "test/test_faker_bitcoin.rb" 
> "test/test_faker_bojack_horseman.rb" "test/test_faker_book.rb" 
> "test/test_faker_boolean.rb" "test/test_faker_bossa_nova.rb" 
> "test/test_faker_breaking_bad.rb" "test/test_faker_business.rb" 
> "test/test_faker_cannabis.rb" "test/test_faker_cat.rb" 
> "test/test_faker_char.rb" "test/test_faker_chuck_norris.rb" 
> "test/test_faker_city.rb" "test/test_faker_code.rb" 
> "test/test_faker_coffee.rb" "test/test_faker_color.rb" 
> "test/test_faker_commerce.rb" "test/test_faker_community.rb" 
> "test/test_faker_company.rb" "test/test_faker_compass.rb" 
> "test/test_faker_crypto.rb" "test/test_faker_currency.rb" 
> "test/test_faker_date.rb" "test/test_faker_demographic.rb" 
> "test/test_faker_dessert.rb" "test/test_faker_device.rb" 
> "test/test_faker_dog.rb" "test/test_faker_dota.rb" 
> "test/test_faker_dr_who.rb" "test/test_faker_dragon_ball.rb" 
> "test/test_faker_dumb_and_dumber.rb" "test/test_faker_dune.rb" 
> "test/test_faker_educator.rb" "test/test_faker_elder_scrolls.rb" 
> "test/test_faker_electrical_components.rb" "test/test_faker_esport.rb" 
> "test/test_faker_ethereum.rb" "test/test_faker_fallout.rb" 
> "test/test_faker_family_guy.rb" "test/test_faker_famous_last_words.rb" 
> "test/test_faker_file.rb" "test/test_faker_fillmurray.rb" 
> "test/test_faker_food.rb" "test/test_faker_football.rb" 
> "test/test_faker_friends.rb" "test/test_faker_funny_name.rb" 
> "test/test_faker_game_of_thrones.rb" "test/test_faker_gender.rb" 
> "test/test_faker

Bug#936498: marked as done (eyed3: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 20:35:06 +
with message-id 
and subject line Bug#936498: fixed in eyed3 0.8.10-1.1
has caused the Debian Bug report #936498,
regarding eyed3: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  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:eyed3

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: eyed3
Source-Version: 0.8.10-1.1
Done: Sandro Tosi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Mar 2020 16:02:56 -0400
Source: eyed3
Architecture: source
Version: 0.8.10-1.1
Distribution: unstable
Urgency: medium
Maintainer: Gaetano Guerriero 
Changed-By: Sandro Tosi 
Closes: 936498
Changes:
 eyed3 (0.8.10-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop python2 support; Closes: #936498
Checksums-Sha1:
 3dc1e4de27626e383d053636ee3ad14f1bb1e49c 1974 eyed3_0.8.10-1.1.dsc
 1edf2b11db0392b2efce0883aca2031ff396731c 13012 eyed3_0.8.10-1.1.debian.tar.xz
 2c38e44f0e73184b80bfb5f033f9d092ec1b43a7 7625 eyed3_0.8.10-1.1_amd64.buildinfo
Checksums-Sha256:
 08e1503a7b42a6dc95e009b6ea5cd99441b8da2e7be64504a6f3227eba53e951 1974 
eyed3_0.8.10-1.1.dsc
 271ed7bff3461a73fc98679e560f8ad1ca4d9daf342cc235539de8324bd29230 13012 
eyed3_0.8.10-1.1.debian.tar.xz
 13f965904aa05131d65624c1ff9bcfe7ecfc2641fc5d42ea96cf9652fe447803 7625 
eyed3_0.8.10-1.1_amd64.buildinfo
Files:
 6410eecaf827692a5ad244a6af53f7a3 1974 sound optional eyed3_0.8.10-1.1.dsc
 7ad42

Bug#950843: marked as done (chef: FTBFS against Ruby2.7 and Bundler 2.1.4)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 20:34:59 +
with message-id 
and subject line Bug#950843: fixed in chef 15.8.25.3.gcf41df6a2-2
has caused the Debian Bug report #950843,
regarding chef: FTBFS against Ruby2.7 and Bundler 2.1.4
to be marked as done.

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

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


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

Package: chef
Version: 13.8.7-4
Severity: critical

Dear Maintainer,

chef currently doesn't have support for Ruby2.7 and the latest version 
of bundler, that is, 2.1.4.


The logs for Ruby2.7 failures are as follows:
https://people.debian.org/~kanashiro/ruby2.7/builds/7/chef/chef_13.8.7-4+rebuild1580868163_amd64-2020-02-05T02:02:44Z.build


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages chef depends on:
ii  chef-zero   13.1.0-2
ii  debconf [debconf-2.0]   1.5.73
ii  lsb-base11.1.0
ii  ohai13.8.0-1
ii  ruby1:2.5.2
ii  ruby-addressable2.7.0-1
ii  ruby-bundler1.17.3-3
ii  ruby-chef-config13.8.7-4
ii  ruby-diff-lcs   1.3-1
ii  ruby-erubis 2.7.0-3
ii  ruby-ffi-yajl   2.3.1-1+b1
ii  ruby-highline   1.7.8-1
ii  ruby-iniparse   1.4.2-1
ii  ruby-iso86010.12.1-1
ii  ruby-mixlib-archive 0.4.1-1
ii  ruby-mixlib-authentication  1.4.1-1
ii  ruby-mixlib-cli 1.7.0-1
ii  ruby-mixlib-log 1.7.1-1
ii  ruby-mixlib-shellout2.2.6-1
ii  ruby-net-sftp   1:2.1.2-4
ii  ruby-net-ssh1:5.2.0-1
ii  ruby-net-ssh-multi  1.2.1-3
ii  ruby-plist  3.2.0-1
ii  ruby-proxifier  1.0.3-1
ii  ruby-rspec-core 3.8.0c0e1m0s0-1
ii  ruby-rspec-expectations 3.8.0c0e1m0s0-1
ii  ruby-rspec-mocks3.8.0c0e1m0s0-1
ii  ruby-serverspec 2.41.5-1
ii  ruby-specinfra  2.82.8-1
ii  ruby-syslog-logger  1.6.8-1
ii  ruby-uuidtools  2.1.5-2
ii  ucf 3.0038+nmu1

chef recommends no packages.

chef suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: chef
Source-Version: 15.8.25.3.gcf41df6a2-2
Done: Antonio Terceiro 

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated chef package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Mar 2020 12:21:50 -0300
Source: chef
Architecture: source
Version: 15.8.25.3.gcf41df6a2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Closes: 950843
Changes:
 chef (15.8.25.3.gcf41df6a2-2) unstable; urgency=medium
 .
   * Add new build dependencies to run test suite: ruby-webmock, git
   * debian/ruby-tests.rake: improve test suite (Closes: #950843)
 - Put debian/ruby-tests.rake back
 - Add patch to drop `bundle exec` from calls in the test suite
 - Add patch to add `require 'bundler'` in spec/spec_helper.rb
 - reduce explicit list of tests to skip
 - skip all windows-related tests
   * chef-bin: drop Windows-only executables
Checksums-Sha1:
 644febcd9d7795e9ff9ee9288b199dd747e20863 3154 chef_15.8.25.3.gcf41df6a2-2.dsc
 28efe0a494193b1fcd0d9687cb88ff3a5beaef36 37528 
chef_15.8.25.3.gcf41df6a2-2.debian.tar.xz
 6426b48c7be3e9fb13f86bf47b500b928640d203 15341 
chef_15.8.25.3.gcf41df6a2-2_source.buildinfo
Checksums-Sha256:
 bb5a834efffa1b375219412bc767782d7259dc0b5e7949883dcf508860b9c6a1 3154

Processed: Bug#950843 marked as pending in chef

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #950843 [chef] chef: FTBFS against Ruby2.7 and Bundler 2.1.4
Added tag(s) pending.

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

Bug#950843: marked as pending in chef

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #950843 in chef 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/ruby-team/chef/-/commit/773e43ac3988109f015fe85cce5b1eb96dee1cba


debian/ruby-tests.rake: improve test suite

- reduce explicit list of tests to skip
- skip all windows-related tests

Closes: #950843

Gbp-Dch: full


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/950843

Processed: found 953747 in 52.1-8+deb8u7

[Debian Bug Tracking System]

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

> found 953747 52.1-8+deb8u7
Bug #953747 {Done: Laszlo Boszormenyi (GCS) } [src:icu] icu: 
CVE-2020-10531
Marked as found in versions icu/52.1-8+deb8u7.
> thanks
Stopping processing here.

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

Bug#954227: node-eslint-plugin-node: unsuitable for stable release: too broken

[Jonas Smedegaard]

Package: node-eslint-plugin-node
Version: 6.0.1~dfsg-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Two rules (out of 13 rules in total) are broken:

  no-missing-import
  no-missing-require

The breakage is (at least partly) caused by an uncoordinated release of
too new node-espree.

For now, the two broken rules have been dropped from "recommended" list,
making the package suitable for _some_ test purposes, but *unsuitable*
for stable release.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl5ygRcACgkQLHwxRsGg
ASFhgg//T0JFnPSBOSst+lNVUFa+jLtba6OfSUpR21Aa2d9W2PfptVQEn9T7zi8D
7AqBU3+V7c0z4OA6NjFXzs+otmjHCWC0mYKBLQQLUCUZPP1p2wFzUSR8i4lEoFEc
rn00ug/1/iUdtICc2dVcuU8jIC5em0H7DAodE7hDbxBy+rYHZvDFii7smOhM+/Ct
GAcNTMmuAuN8LpMC9DqAP0sn2Sn+ICgEU+v01a6YKRZKBCnGtTJovwu9dApkdP83
0bx6OaR9g7CgSjgPZzoy4uggPidaWMeOEQeGV+JHumrWmeSXESIqEn8mLmbWQPQD
+xK66Ippl/YUiBUjCBurCeKprr7IiiM7JaRbWqfa8ICARJj5wO5O9Xny4BlUTdhw
QA9PZVs/ivS5eFdIXHvU+TnseHHH+fvwXpwvMxeVjSdzjyWgZwgL7CphlY1tVBqr
OgDQ6kFNTOlbNKd8N6/OPWLsknvCmHNHZLkzuBnW5xH9fgsv5iuVv0P45tQ6KYUQ
06Me8lU23+v5zK0PkRUd19CkpRzLFEoh/XB7XKRady8XTBms3JYRyuO7nyeE/e1x
I0llynFc/0Yq/5Gcstq5HPutC51lSti4DXQkbU2cFcyHW3l3oLmzZv9s1oCrEIpV
+9g5+q5GIfOAGkL3nTwDkRzP85DJm0bu+f0Xa35MivZ/xPLKuro=
=iXdm
-END PGP SIGNATURE-

Processed: eyed3: diff for NMU version 0.8.10-1.1

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: Bug#952080 marked as pending in ruby-faker

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #952080 [src:ruby-faker] ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.
Added tag(s) pending.

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

Bug#952080: marked as pending in ruby-faker

[Lucas Kanashiro]

Control: tag -1 pending

Hello,

Bug #952080 in ruby-faker 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/ruby-team/ruby-faker/-/commit/1cad3a5702e3869557d3634450791f89636f1aa7


Add patch to fix failing tests against Ruby 2.7 (Closes: #952080)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/952080

Bug#936498: eyed3: diff for NMU version 0.8.10-1.1

[Sandro Tosi]

Control: tags 936498 + patch


Dear maintainer,

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

Please  consider maintaining this package with DPMT/PAPT

Regards.

diff -Nru eyed3-0.8.10/debian/changelog eyed3-0.8.10/debian/changelog
--- eyed3-0.8.10/debian/changelog	2019-08-22 15:23:37.0 -0400
+++ eyed3-0.8.10/debian/changelog	2020-03-18 16:02:56.0 -0400
@@ -1,3 +1,10 @@
+eyed3 (0.8.10-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop python2 support; Closes: #936498
+
+ -- Sandro Tosi   Wed, 18 Mar 2020 16:02:56 -0400
+
 eyed3 (0.8.10-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru eyed3-0.8.10/debian/control eyed3-0.8.10/debian/control
--- eyed3-0.8.10/debian/control	2019-08-22 15:11:13.0 -0400
+++ eyed3-0.8.10/debian/control	2020-03-18 16:01:55.0 -0400
@@ -3,33 +3,18 @@
 Priority: optional
 Maintainer: Gaetano Guerriero 
 Build-Depends: debhelper (>= 10), dh-python,
-   python-all, python-setuptools,
python3, python3-setuptools
 Homepage: http://eyed3.nicfit.net/
 Standards-Version: 4.4.0
 Vcs-Browser: https://github.com/gaetano-guerriero/eyeD3-debian
 Vcs-Git: https://github.com/gaetano-guerriero/eyeD3-debian.git
 
-Package: python-eyed3
-Architecture: all
-Section: python
-Depends: ${misc:Depends}, ${python:Depends}, python-pathlib
-Suggests: ${python:Suggests}
-Provides: ${python:Provides}
-Description: Python module for id3-tags manipulation (Python 2 version)
- A Python module for the manipulation of ID3 tags. It supports versions
- 1.0, 1.1, 2.3, and 2.4 of the ID3 standard. It can also retrieve
- information such as length and bit rate from an MP3 file.
- .
- This is the Python 2 version of the package.
-
-
 Package: python3-eyed3
 Architecture: all
 Section: python
 Depends: ${misc:Depends}, ${python3:Depends}
 Suggests: ${python3:Suggests}
-Provides: ${python:Provides}
+Provides: ${python3:Provides}
 Description: Python module for id3-tags manipulation (Python 3 version)
  A Python module for the manipulation of ID3 tags. It supports versions
  1.0, 1.1, 2.3, and 2.4 of the ID3 standard. It can also retrieve
diff -Nru eyed3-0.8.10/debian/pydist-overrides eyed3-0.8.10/debian/pydist-overrides
--- eyed3-0.8.10/debian/pydist-overrides	2019-01-02 08:59:00.0 -0500
+++ eyed3-0.8.10/debian/pydist-overrides	1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-python_magic python-magic
\ No newline at end of file
diff -Nru eyed3-0.8.10/debian/rules eyed3-0.8.10/debian/rules
--- eyed3-0.8.10/debian/rules	2019-01-02 08:59:00.0 -0500
+++ eyed3-0.8.10/debian/rules	2020-03-18 16:02:19.0 -0400
@@ -2,27 +2,21 @@
 
 export PYBUILD_NAME=eyed3
 
-py2_dstdir := $(CURDIR)/debian/python-eyed3
 py3_dstdir := $(CURDIR)/debian/python3-eyed3
 eyed3_dstdir := $(CURDIR)/debian/eyed3
 
 
 %:
-	dh $@ --with python2,python3 --buildsystem=pybuild
+	dh $@ --with python3 --buildsystem=pybuild
 
 
 override_dh_python3:
 	dh_python3 --suggests-section=art-plugin
 
 
-override_dh_python2:
-	dh_python2 --suggests-section=art-plugin
-
-
 override_dh_installchangelogs:
 	dh_installchangelogs -p eyed3 HISTORY.rst
 	dh_installchangelogs -p python3-eyed3 -X history.rst -X HISTORY.rst
-	dh_installchangelogs -p python-eyed3 -X history.rst -X HISTORY.rst
 
 
 override_dh_auto_test:
@@ -32,4 +26,3 @@
 	dh_auto_install
 	mkdir -p ${eyed3_dstdir}/usr/bin/
 	mv ${py3_dstdir}/usr/bin/eyeD3 ${eyed3_dstdir}/usr/bin/eyeD3
-	rm ${py2_dstdir}/usr/bin/eyeD3
diff -Nru eyed3-0.8.10/debian/tests/control eyed3-0.8.10/debian/tests/control
--- eyed3-0.8.10/debian/tests/control	2019-01-02 08:59:00.0 -0500
+++ eyed3-0.8.10/debian/tests/control	2020-03-18 16:02:45.0 -0400
@@ -1,8 +1,5 @@
 Tests: base-script
 Depends: eyed3
 
-Test-Command: set -e ; for py in $(pyversions -r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c "import eyed3; print eyed3" ; done
-Depends: python-all, python-eyed3
-
 Test-Command: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$ADTTMP" ; echo "Testing with $py:" ; $py -c "import eyed3; print(eyed3)" ; done
-Depends: python3-all, python3-eyed3
\ No newline at end of file
+Depends: python3-all, python3-eyed3

Bug#954222: src:appdirs: Fails autopkgtest with non-default python3 installed

[Scott Kitterman]

Package: src:appdirs
Version: 1.4.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Note: Using the ftbfs tag since it seems to be the closest thing we have
for this.

Appdirs failed a recent autopkgtest and this is one of the blockers for
python3-defaults migration.  It failed because python3.7 was installed
in the chroot and the current autopkgtest doesn't handle that.

Autopkgtests should be run for all supported versions.  The attached
patch should solve it (untested on this package, but I've tested the
approach on others with the same problem).  Despite being in the form of
an NMU diff, I do not plan to NMU now.  If we get to the point where
this is one of a few remaining blockers or if the maintianers ask me to
handle it, then I will.  Please let me know (not cc'ed to the bug, so
either include -submitter or email me directly).

Here's the exact failure:

autopkgtest [09:16:17]: test python3: cp -r test "$AUTOPKGTEST_TMP" && cd 
"$AUTOPKGTEST_TMP" && for py in $(py3versions -vi); do "python$py" -m unittest 
discover -v; done
autopkgtest [09:16:17]: test python3: [---
/usr/bin/python3.7: No module named unittest
autopkgtest [09:16:18]: test python3: ---]
autopkgtest [09:16:18]: test python3:  - - - - - - - - - - results - - - - - - 
- - - -
python3  FAIL non-zero exit status 1

Scott K
diff -Nru appdirs-1.4.3/debian/changelog appdirs-1.4.3/debian/changelog
--- appdirs-1.4.3/debian/changelog  2020-02-26 15:13:19.0 -0500
+++ appdirs-1.4.3/debian/changelog  2020-03-18 15:30:59.0 -0400
@@ -1,3 +1,10 @@
+appdirs (1.4.3-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix autopkgtest to reliably run with multiple python3 versions installed
+
+ -- Scott Kitterman   Wed, 18 Mar 2020 15:30:59 -0400
+
 appdirs (1.4.3-2) unstable; urgency=medium
 
   * Move repository to salsa.debian.org
diff -Nru appdirs-1.4.3/debian/tests/control appdirs-1.4.3/debian/tests/control
--- appdirs-1.4.3/debian/tests/control  2020-02-26 15:06:10.0 -0500
+++ appdirs-1.4.3/debian/tests/control  2020-03-18 15:30:59.0 -0400
@@ -3,7 +3,7 @@
 Restrictions: allow-stderr
 Features: test-name=pypy
 
-Test-Command: cp -r test "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && for py 
in $(py3versions -vi); do "python$py" -m unittest discover -v; done
-Depends: python3-appdirs
+Test-Command: cp -r test "$AUTOPKGTEST_TMP" && cd "$AUTOPKGTEST_TMP" && for py 
in $(py3versions -vs); do "python$py" -m unittest discover -v; done
+Depends: python3-all, python3-appdirs
 Restrictions: allow-stderr
 Features: test-name=python3

Bug#954219: pyresample: autopkgtest failures (AttributeError: module 'pyproj._proj' has no attribute 'Proj')

[Bas Couwenberg]

Source: pyresample
Version: 1.14.0-3
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

The autopkgtest for your package fail with python-pyproj (2.6.0+ds-1):

 ==
 ERROR: test_lcc_basic1 (pyresample.test.test_ewa_ll2cr.TestLL2CRStatic)
 --
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/pyresample/test/test_ewa_ll2cr.py", 
line 73, in test_lcc_basic1
 points_in_grid = _ll2cr.ll2cr_static(lon_arr, lat_arr, fill_in, proj_str,
   File "pyresample/ewa/_ll2cr.pyx", line 261, in 
pyresample.ewa._ll2cr.ll2cr_static
   File "pyresample/ewa/_ll2cr.pyx", line 61, in 
pyresample.ewa._ll2cr.MyProj.__call__
 AttributeError: module 'pyproj._proj' has no attribute 'Proj'
 
 ==
 ERROR: test_lcc_fail1 (pyresample.test.test_ewa_ll2cr.TestLL2CRStatic)
 --
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/pyresample/test/test_ewa_ll2cr.py", 
line 90, in test_lcc_fail1
 points_in_grid = _ll2cr.ll2cr_static(lon_arr, lat_arr, fill_in, proj_str,
   File "pyresample/ewa/_ll2cr.pyx", line 261, in 
pyresample.ewa._ll2cr.ll2cr_static
   File "pyresample/ewa/_ll2cr.pyx", line 61, in 
pyresample.ewa._ll2cr.MyProj.__call__
 AttributeError: module 'pyproj._proj' has no attribute 'Proj'
 
 ==
 ERROR: test_basic1 (pyresample.test.test_ewa_ll2cr.TestLL2CRWrapper)
 --
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/pyresample/test/test_ewa_ll2cr.py", 
line 185, in test_basic1
 points_in_grid, lon_res, lat_res, = ll2cr(swath_def, area,
   File "/usr/lib/python3/dist-packages/pyresample/ewa/__init__.py", line 126, 
in ll2cr
 swath_points_in_grid = _ll2cr.ll2cr_static(lons, lats, fill,
   File "pyresample/ewa/_ll2cr.pyx", line 261, in 
pyresample.ewa._ll2cr.ll2cr_static
   File "pyresample/ewa/_ll2cr.pyx", line 61, in 
pyresample.ewa._ll2cr.MyProj.__call__
 AttributeError: module 'pyproj._proj' has no attribute 'Proj'
 
 --

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyresample/4592702/log.gz

Kind Regards,

Bas

Bug#953189: marked as done (src:libgphoto2: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 20:07:20 +0100
with message-id <87v9n1bhxz@lant.ki.iif.hu>
and subject line Re: src:libgphoto2: fails to migrate to testing for too long
has caused the Debian Bug report #953189,
regarding src:libgphoto2: fails to migrate to testing for too long
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.)


-- 
953189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgphoto2
Version: 2.5.22-3
Severity: serious
Control: fixed -1 2.5.23-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:libgphoto2 in
its current version in unstable has been trying to migrate for 223 days.
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have marked the version in unstable as fixing this bug, so if that
version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
2.5.24-1 is in testing now, so this is done.
-- 
Thanks,
Feri--- End Message ---

Bug#951821: gegl: FTBFS on arm*/mips* architectures; testing migration blocked

[Simon McVittie]

Version: 0.4.22-3

On Sat, 22 Feb 2020 at 00:23:13 -0500, Boyuan Yang wrote:
> The latest upload of package gegl was made on 2019-11-21 and it never migrated
> to Debian Testing.
[...]
> Looking into the current status, it fails to build on all ARM and MIPS
> architectures.

This appears to have been resolved by the changes I made in 0.4.22-2
and -3.

smcv

Processed: Re: Bug#954197: GFileMonitor can deadlock if not cancelled before last unref

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 GFileMonitor can deadlock if not cancelled before last unref
Bug #954197 [libglib2.0-0] gegl: FTBFS (most often on arm64, armhf): 
gegl:simple / backend-file times out
Changed Bug title to 'GFileMonitor can deadlock if not cancelled before last 
unref' from 'gegl: FTBFS (most often on arm64, armhf): gegl:simple / 
backend-file times out'.
> severity -1 normal
Bug #954197 [libglib2.0-0] GFileMonitor can deadlock if not cancelled before 
last unref
Severity set to 'normal' from 'serious'

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

Bug#954197: GFileMonitor can deadlock if not cancelled before last unref

[Simon McVittie]

Control: retitle -1 GFileMonitor can deadlock if not cancelled before last unref
Control: severity -1 normal

On Wed, 18 Mar 2020 at 09:37:15 +, Simon McVittie wrote:
> Looks like . The
> workaround, which gegl might be able to use, is to always cancel
> file monitors before their last-unref is reached.

I have done that in gegl and it seems to have resolved the FTBFS.

According to GLib developers, best-practice is to cancel file monitors,
close files and sockets, etc. before their last-unref *anyway*, similar
to the advice given for file-like objects in modern Python: this avoids
doing complicated things in the dispose() and finalize() callbacks,
and avoids leaking resources if a reference cycle, a temporary ref
taken while delivering events or a ref taken by a worker thread keeps
the object alive. So this workaround is not just a workaround, it is
also an improvement to gegl.

smcv

Bug#951979: Anything related to recent patch from Ubuntu?

[Tiago Bortoletto Vaz]

Hi Håvard,

This FTBFS might have something to do with the recent added patch by you on
last upload, and so far I can't find where is exactly the issue. Could you
help?

Thanks,

--
Tiago

Processed: reassign 953205 to ruby-activesupport

[Debian Bug Tracking System]

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

> reassign 953205 ruby-activesupport
Bug #953205 [redmine] "NameError: uninitialized constant URI::Generic" on 
upgrade
Bug reassigned from package 'redmine' to 'ruby-activesupport'.
No longer marked as found in versions redmine/4.0.6-2.
Ignoring request to alter fixed versions of bug #953205 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#951655: marked as done (r-cran-sf: FTBFS with PROJ 7.0.0 (configure: error: proj_api.h not found in standard or given locations.))

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 15:05:46 +
with message-id 
and subject line Bug#951655: fixed in r-cran-sf 0.8-1+dfsg-2
has caused the Debian Bug report #951655,
regarding r-cran-sf: FTBFS with PROJ 7.0.0 (configure: error: proj_api.h not 
found in standard or given locations.)
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.)


-- 
951655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-sf
Version: 0.8-1+dfsg-1
Severity: important
Tags: ftbfs
User: debian-...@lists.debian.org
Usertags: proj-7.0

Dear Maintainer,

Your package FTBFS with PROJ 7 from experimental:

 configure: error: proj_api.h not found in standard or given locations.

The full buildlog is attached.

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: r-cran-classint (>= 
0.4-1) r-cran-dbi (>= 0.8) r-cran-magrittr r-cran-rcpp (>= 0.12.18) 
r-cran-units libgdal-dev
W: Unmet build-dependency in source
dh clean --buildsystem R
   dh_auto_clean -O--buildsystem=R
   dh_autoreconf_clean -O--buildsystem=R
   dh_clean -O--buildsystem=R
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building r-cran-sf using existing 
./r-cran-sf_0.8-1+dfsg.orig.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: building r-cran-sf in r-cran-sf_0.8-1+dfsg-2.debian.tar.xz
dpkg-source: info: building r-cran-sf in r-cran-sf_0.8-1+dfsg-2.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.340
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.340
I: removed stale ilistfile /var/cache/pbuilder/build/cow.340/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.340 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.340 --buildresult /var/cache/pbuilder/result/ 
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.340 cow-shell' 
/home/bas/tmp/debian/r-cran-sf_0.8-1+dfsg-2.dsc
I: Running in no-targz mode
I: pbuilder: network access will be disabled during build
I: Current time: Wed Feb 19 08:33:14 CET 2020
I: pbuilder-time-stamp: 1582097594
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [/home/bas/tmp/debian/r-cran-sf_0.8-1+dfsg-2.dsc]
I: copying [/home/bas/tmp/debian/r-cran-sf_0.8-1+dfsg.orig.tar.xz]
I: copying [/home/bas/tmp/debian/r-cran-sf_0.8-1+dfsg-2.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package 
(r-cran-sf_0.8-1+dfsg-2.dsc)
dpkg-source: info: extracting r-cran-sf in r-cran-sf-0.8-1+dfsg
dpkg-source: info: unpacking r-cran-sf_0.8-1+dfsg.orig.tar.xz
dpkg-source: info: unpacking r-cran-sf_0.8-1+dfsg-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying exclude_test_requiring_rgeos.patch
dpkg-source: info: applying exclude_test_requiring_rgdal.patch
I: using fakeroot in build.
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper-compat (= 12), dh-r, r-base-dev, r-cran-classint (>= 0.4-1), 
r-cran-dbi (>= 0.8), r-cran-magrittr, r-cran-rcpp (>= 0.12.18), r-cran-units, 
libgdal-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' i

Bug#936873: Bug#727005: switch python bindings to python3

[Matthias Klose]

swig3 had support for Python3, and now we have swig 4.0 in the archive.  Any
update on this?

Processed: py2removal bugs severity updates - 2020-03-18 13:35:11.679615+00:00

[Debian Bug Tracking System]

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
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # pydxcluster is an application, has low popcon (62 < 300), and has 0 
> external rdeps or not in testing
> severity 945731 serious
Bug #945731 [src:pydxcluster] pydxcluster: Python2 removal in sid/bullseye
Bug #912495 [src:pydxcluster] pydxcluster: Please migrate to python3-pygame
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
> # python-eyed3 is a module and has 0 external rdeps or not in testing
> severity 936498 serious
Bug #936498 [src:eyed3] eyed3: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # kiki-the-nano-bot is an application, has low popcon (152 < 300), and has 0 
> external rdeps or not in testing
> severity 936796 serious
Bug #936796 [src:kiki-the-nano-bot] kiki-the-nano-bot: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'
> # lepton-eda is an application, has low popcon (151 < 300), and has 0 
> external rdeps or not in testing
> severity 936839 serious
Bug #936839 [src:lepton-eda] lepton-eda: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pymissile is an application, has low popcon (121 < 300), and has 0 external 
> rdeps or not in testing
> severity 943176 serious
Bug #943176 [src:pymissile] pymissile: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # ardentryst is an application, has low popcon (164 < 300), and has 0 
> external rdeps or not in testing
> severity 936148 serious
Bug #936148 [src:ardentryst] ardentryst: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-cddb is a module and has 0 external rdeps or not in testing
> severity 937636 serious
Bug #937636 [src:python-cddb] python-cddb: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # snowballz is an application, has low popcon (149 < 300), and has 0 external 
> rdeps or not in testing
> severity 938509 serious
Bug #938509 [src:snowballz] snowballz: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # tennix is an application, has low popcon (73 < 300), and has 0 external 
> rdeps or not in testing
> severity 938647 serious
Bug #938647 [src:tennix] tennix: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # pd-py is an application, has low popcon (80 < 300), and has 0 external 
> rdeps or not in testing
> severity 937266 serious
Bug #937266 [src:pd-py] pd-py: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # yorick-yao is an application, has low popcon (258 < 300), and has 0 
> external rdeps or not in testing
> severity 945726 serious
Bug #945726 [src:yorick-yao] yorick-yao: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
912495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912495
936148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936148
936498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936498
936796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936796
936839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936839
937266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937266
937636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937636
938509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938509
938647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938647
943176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943176
945726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945726
945731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#954196: marked as done (gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 13:34:19 +
with message-id 
and subject line Bug#954196: fixed in gegl 0.4.22-3
has caused the Debian Bug report #954196,
regarding gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and 
.../output/rgbe-save.hdr differ
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=gegl&arch=mipsel&ver=0.4.22-2&stamp=1584490046&raw=0
> [swscaler @ 0x5617e750] No accelerated colorspace conversion found from 
> yuv420p to rgb24.
> missing reference, assuming SUCCESS
> PASS color-reduction.xml
> missing reference, assuming SUCCESS
> PASS jpg-load-datauri.xml
> missing reference, assuming SUCCESS
> PASS pnm-ascii-load.xml
> missing reference, assuming SUCCESS
> PASS pnm-raw-load.xml
> missing reference, assuming SUCCESS
> PASS rgbe-load.xml
> 
> (gegl-imgcmp:1189): GEGL-WARNING **: 00:03:06.812: max diff is not a valid 
> property of gegl:image-compare 0x55776830
> /<>/tests/compositions/reference/rgbe-save.hdr and 
> /<>/obj-mipsel-linux-gnu/tests/compositions/output/rgbe-save.hdr 
> differ
>   wrong pixels   : 165/12288 (1.34%)
>   max ?e : 
> 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000
>   avg ?e (wrong) : 
> 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000(wrong)
>  
> 57895085948248197003310861778540597530344540911046658743056637836873978536706733178284242874418852779814501765638059266549873720618904958362702683089689120708187862881929758991439906547451878104338721332513031507467342755888365810233077968491152966828328813401751945216.000(total)
> FAIL rgbe-save.xml
> missing reference, assuming SUCCESS
> PASS shift.xml
> missing reference, assuming SUCCESS
> PASS stretch-contrast-hsv.xml
> missing reference, assuming SUCCESS
> PASS tiff-load.xml
> missing reference, assuming SUCCESS
> PASS tile.xml
> === Test Results ===
>  tests passed:  9
>  tests skipped: 0
>  tests failed:  1
> ==  FAIL  ==

We can't get the binary output from a failing build on a buildd, so it's
impossible to say whether this is serious or not unless it can be
reproduced on a porterbox or similar (which I'm trying to do now).

smcv
--- End Message ---
--- Begin Message ---
Source: gegl
Source-Version: 0.4.22-3
Done: Simon McVittie 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Mar 2020 11:54:14 +
Source: gegl
Architecture: source
Version: 0.4.22-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 954196
Changes:
 gegl (0.4.22-3) unstable; urgency=medium
 .
   * Team upload
   * d/rules: Show testlog.txt if tests fail, like dh_auto_test does.
 This is a useful way to correlate tests' output with which tests
 failed.
   * Fix max-diff property name.
 GLib 2.64 validates property names more strictly, resulting in this
 not working as intended, with max_diff left uninitialized. It appears
 this caused test failures that were more likely to happen on mips*.
 (Closes: #954196)
   * Work around #954197.
 GLib has a long-standing bug in which a GFileMonitor that is freed
 wi

Bug#954205: marked as done (src:python-lockfile: Autopkgtest failures with non-default python3 installed)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 13:35:25 +
with message-id 
and subject line Bug#954205: fixed in python-lockfile 1:0.12.2-2.2
has caused the Debian Bug report #954205,
regarding src:python-lockfile: Autopkgtest failures with non-default python3 
installed
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.)


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

Using FTBFS since autopkgtest failures are blocking and it's the closes
tag we have.

The python-lockfile autopkgtest runs against all 'installed' python3
versions, but only depends on python3, not python3-all.  In the case it
failed, python3.7-minimal happened to be in the chroot so it counted as
installed, but the full interpreter wasn't there and the test failed.

This is simple enough to fix (and testing supported versions is a better
idea anyway).  Since this is one of the python3.8 as default transition
blockers, I do not intend to wait to NMU.

I'll send a patch to the bug once I get a number.

Here's the relevent test log extract:

autopkgtest [17:11:20]: test smoke-python3: [---
Python command: python3.7
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.bgufeo9z/downtmp/build.wGa/src/debian/tests/smoke_test.py",
 line 27, in 
import pkg_resources
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 26, in 

import zipfile
ModuleNotFoundError: No module named 'zipfile'
autopkgtest [17:11:21]: test smoke-python3: ---]
autopkgtest [17:11:21]: test smoke-python3:  - - - - - - - - - - results - - - 
- - - - - - -
smoke-python3FAIL non-zero exit status 1
autopkgtest [17:11:21]: test smoke-python3:  - - - - - - - - - - stderr - - - - 
- - - - - -
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.bgufeo9z/downtmp/build.wGa/src/debian/tests/smoke_test.py",
 line 27, in 
import pkg_resources
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 26, in 

import zipfile
ModuleNotFoundError: No module named 'zipfile'
autopkgtest [17:11:21]:  summary
smoke-python3FAIL non-zero exit status 1

Scott K
--- End Message ---
--- Begin Message ---
Source: python-lockfile
Source-Version: 1:0.12.2-2.2
Done: Scott Kitterman 

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated python-lockfile 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Mar 2020 09:13:51 -0400
Source: python-lockfile
Architecture: source
Version: 1:0.12.2-2.2
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Scott Kitterman 
Closes: 954205
Changes:
 python-lockfile (1:0.12.2-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix autopkgtest to work reliably with multiple supported python3 versions
 (Closes: #954205)
Checksums-Sha1:
 ddc195e0e695926cda9b16b9efdf6d50f2ddfb57 2164 python-lockfile_0.12.2-2.2.dsc
 6f688a85fe728c568d1053bff44d0e1ce4d19323 10256 
python-lockfile_0.12.2-2.2.debian.tar.xz
 7a11712a9a5a4969d15e440d5a8edbbf3000f798 7011 
python-lockfile_0.12.2-2.2_source.buildinfo
Checksums-Sha256:
 184330fa53ba60f7e3aaf59edaf13222cddf44c433be7e2213c896ee964e18e5 2164 
python-lockfile_0.12.2-2.2.dsc
 910b2f8319526c7e87d11ecd37f156fa55e0917d995076b2a93685253dba270e 10256 
python-lockfile_0.12.2-2.2.debian.tar.xz
 cc1901b968d0b6474d04a1bf6e8884e4b45491dbd57f555a178baf87ed2274c2 7011 
python-lockfile_0.12.2-2.2_source.buildinfo
Files:
 c851514b9596f1fa69a2ceffeb639bad 2164 python optional 
python-lockfile_0.12.2-2.2.dsc
 8429153c2d3eca31bb67ebf879df5da9 10256 python optional 
python-lockfile_0.12.2-2.2.debian.tar.xz
 6704b22c66fea66eb510414beb73db75 7011 python optional 
python

Bug#954205: Acknowledgement (src:python-lockfile: Autopkgtest failures with non-default python3 installed)

[Scott Kitterman]

NMU diff attached.

Scott Kdiff -Nru python-lockfile-0.12.2/debian/changelog python-lockfile-0.12.2/debian/changelog
--- python-lockfile-0.12.2/debian/changelog	2020-03-13 19:12:13.0 -0400
+++ python-lockfile-0.12.2/debian/changelog	2020-03-18 09:13:51.0 -0400
@@ -1,3 +1,11 @@
+python-lockfile (1:0.12.2-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix autopkgtest to work reliably with multiple supported python3 versions
+(Closes: #954205)
+
+ -- Scott Kitterman   Wed, 18 Mar 2020 09:13:51 -0400
+
 python-lockfile (1:0.12.2-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-lockfile-0.12.2/debian/tests/control python-lockfile-0.12.2/debian/tests/control
--- python-lockfile-0.12.2/debian/tests/control	2020-03-13 19:02:22.0 -0400
+++ python-lockfile-0.12.2/debian/tests/control	2020-03-18 09:06:17.0 -0400
@@ -4,6 +4,7 @@
 
 Tests: smoke-python3
 Depends:
+python3-all,
 python3-pkg-resources,
 python3-lockfile
 
diff -Nru python-lockfile-0.12.2/debian/tests/smoke-python3 python-lockfile-0.12.2/debian/tests/smoke-python3
--- python-lockfile-0.12.2/debian/tests/smoke-python3	2016-08-21 01:59:20.0 -0400
+++ python-lockfile-0.12.2/debian/tests/smoke-python3	2020-03-18 09:07:17.0 -0400
@@ -33,7 +33,7 @@
 test_opts="$test_opts --module=$mod"
 done
 
-for py in $(py3versions -i) ; do
+for py in $(py3versions -s) ; do
 printf "Python command: %s\n" $py
 $py "$program_dir"/smoke_test.py $test_opts
 printf "\n"


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

Bug#954205: src:python-lockfile: Autopkgtest failures with non-default python3 installed

[Scott Kitterman]

Package: src:python-lockfile
Version: 1:0.12.2-2.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Using FTBFS since autopkgtest failures are blocking and it's the closes
tag we have.

The python-lockfile autopkgtest runs against all 'installed' python3
versions, but only depends on python3, not python3-all.  In the case it
failed, python3.7-minimal happened to be in the chroot so it counted as
installed, but the full interpreter wasn't there and the test failed.

This is simple enough to fix (and testing supported versions is a better
idea anyway).  Since this is one of the python3.8 as default transition
blockers, I do not intend to wait to NMU.

I'll send a patch to the bug once I get a number.

Here's the relevent test log extract:

autopkgtest [17:11:20]: test smoke-python3: [---
Python command: python3.7
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.bgufeo9z/downtmp/build.wGa/src/debian/tests/smoke_test.py",
 line 27, in 
import pkg_resources
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 26, in 

import zipfile
ModuleNotFoundError: No module named 'zipfile'
autopkgtest [17:11:21]: test smoke-python3: ---]
autopkgtest [17:11:21]: test smoke-python3:  - - - - - - - - - - results - - - 
- - - - - - -
smoke-python3FAIL non-zero exit status 1
autopkgtest [17:11:21]: test smoke-python3:  - - - - - - - - - - stderr - - - - 
- - - - - -
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.bgufeo9z/downtmp/build.wGa/src/debian/tests/smoke_test.py",
 line 27, in 
import pkg_resources
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 26, in 

import zipfile
ModuleNotFoundError: No module named 'zipfile'
autopkgtest [17:11:21]:  summary
smoke-python3FAIL non-zero exit status 1

Scott K

Processed: severity of 954195 is serious

[Debian Bug Tracking System]

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

> severity 954195 serious
Bug #954195 [gnome-music] gnome-music fails to start
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#954134: [d-i bullseye alpha2] installing grub fails

[Steve McIntyre]

On Wed, Mar 18, 2020 at 01:00:35PM +0100, Holger Wansing wrote:
>Hi,
>
>Holger Wansing  wrote:
>> Hi,
>> 
>> Holger Wansing  wrote:
>> > Hi,
>> > 
>> > Am Dienstag, 17. März 2020 schrieb Steve McIntyre:
>> > Yes, I had it with alpha2, then tested with alpha1 (everything
>> > fine) and then again tested with alpha2 to be able to
>> > provide logs.
>> > 
>> > I can do further tests though, with different partitioning
>> > scheme or filesystem type...
>> 
>> I tried different approaches (use only one ext4 partition + swap; use only 
>> one
>> ext2 partition + swap; use only one xfs partition + swap; create a complete 
>> new parition table and then use only one ext4 partition + swap) and all fail 
>> with the same error.
>> 
>> Now I will test again with alpha1 to make sure it is no hardware issue...
>
>With alpha1 it succeeds without problems.
>So, there is something different with alpha2...
>Note, that this was i386, tested on a real machine (IBM Thinkpad)!
>
>Then I tested an alpha2 netinst amd64 image on QEMU, and it works fine!
>Need to find out where the difference is...

One silly question: what media are you using with the Thinkpad? Is it
the same USB stick (or whatever) every time? Can you verify it's
written OK?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty

Bug#954134: [d-i bullseye alpha2] installing grub fails

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Hi,
> 
> Holger Wansing  wrote:
> > Hi,
> > 
> > Am Dienstag, 17. März 2020 schrieb Steve McIntyre:
> > Yes, I had it with alpha2, then tested with alpha1 (everything
> > fine) and then again tested with alpha2 to be able to
> > provide logs.
> > 
> > I can do further tests though, with different partitioning
> > scheme or filesystem type...
> 
> I tried different approaches (use only one ext4 partition + swap; use only one
> ext2 partition + swap; use only one xfs partition + swap; create a complete 
> new parition table and then use only one ext4 partition + swap) and all fail 
> with the same error.
> 
> Now I will test again with alpha1 to make sure it is no hardware issue...

With alpha1 it succeeds without problems.
So, there is something different with alpha2...
Note, that this was i386, tested on a real machine (IBM Thinkpad)!

Then I tested an alpha2 netinst amd64 image on QEMU, and it works fine!
Need to find out where the difference is...


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Processed: Bug#954196 marked as pending in gegl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954196 [src:gegl] gegl: FTBFS on mipsel: 
tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ
Added tag(s) pending.

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

Bug#954196: marked as pending in gegl

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gegl/-/commit/2913012c3702a5b81d53ac345c6f132cf057bdfa


Fix max-diff property name

GLib 2.64 validates property names more strictly, resulting in this
not working as intended, with max_diff left uninitialized. It appears
this caused test failures that were more likely to happen on mips*.

Closes: #954196


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954196

Bug#954203: Client splash and exit after login in

[gulfstream]

Package: xrdp
Version: 0.9.12-1
Severity: grave

Hello, I want use remote client to connent xrdp server with remmina. But the 
remmina client splashed and closed after its login in xrdp server. I think its 
a bug of xrdp because the same client can connect the xrdp server in Debian 
Buster correctly.

Would you please find what's matter with the xrdp and repair it?

Thank you very much!


Best regards,
Gulfstream



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

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

Versions of packages xrdp depends on:
ii  adduser  3.118
ii  init-system-helpers  1.57
ii  libc62.30-2
ii  libfuse2 2.9.9-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libopus0 1.3-1+b1
ii  libpam0g 1.3.1-5
ii  libssl1.11.1.1d-2
ii  libx11-6 2:1.6.9-2
ii  libxfixes3   1:5.0.3-1
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 11.1.0
ii  ssl-cert 1.0.39

Versions of packages xrdp recommends:
ii  fuse3 [fuse]  3.9.0-2
ii  xorgxrdp  1:0.2.12-1

Versions of packages xrdp suggests:
pn  guacamole  
pn  xrdp-pulseaudio-installer  

Versions of packages xorgxrdp depends on:
ii  libc6  2.30-2
ii  libepoxy0  1.5.4-1
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.7-4

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+20

Versions of packages xrdp is related to:
ii  tightvncserver [vnc-server]  1:1.3.9-9.1
pn  xserver-xorg-legacy  

-- no debconf information

Processed: tagging 953621

[Debian Bug Tracking System]

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

> tags 953621 + bullseye sid
Bug #953621 [sshuttle] sshutle not working in connecting sid boxes due to 
python 3.8 version at endpoint
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#951996: marked as done (gitlint: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 09:49:16 +
with message-id 
and subject line Bug#951996: fixed in gitlint 0.13.1-0.1
has caused the Debian Bug report #951996,
regarding gitlint: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.8 3.7" returned exit code 13
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.)


-- 
951996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlint
Version: 0.12.0-0.1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PYBUILD_SYSTEM=custom dh_auto_test
> I: pybuild base:217: python3.8 -m coverage run 
> --omit='/usr/*,/<>/gitlint/tests/*,/<>/gitlint/qa/*'
>  -m unittest discover -v -s /<>/gitlint/tests
> test_contrib_rule_instantiated (contrib.test_contrib_rules.ContribRuleTests)
> Tests that all contrib rules can be instantiated without errors. ... ok
> test_contrib_rule_naming_conventions 
> (contrib.test_contrib_rules.ContribRuleTests)
> Tests that contrib rules follow certain naming conventions. ... ok
> test_contrib_rule_uniqueness (contrib.test_contrib_rules.ContribRuleTests)
> Tests that all contrib rules have unique identifiers. ... ok
> test_contrib_tests_exist (contrib.test_contrib_rules.ContribRuleTests)
> Tests that every contrib rule file has an associated test file. ... ok
> test_conventional_commits 
> (contrib.test_conventional_commit.ContribConventionalCommitTests) ... ok
> test_enable (contrib.test_conventional_commit.ContribConventionalCommitTests) 
> ... ok
> test_enable (contrib.test_signedoff_by.ContribSignedOffByTests) ... ok
> test_signedoff_by (contrib.test_signedoff_by.ContribSignedOffByTests) ... ok
> test_body_changed_file_mention (rules.test_body_rules.BodyRuleTests) ... ok
> test_body_first_line_empty (rules.test_body_rules.BodyRuleTests) ... ok
> test_body_min_length (rules.test_body_rules.BodyRuleTests) ... ok
> test_body_missing (rules.test_body_rules.BodyRuleTests) ... ok
> test_body_missing_merge_commit (rules.test_body_rules.BodyRuleTests) ... ok
> test_hard_tabs (rules.test_body_rules.BodyRuleTests) ... ok
> test_max_line_length (rules.test_body_rules.BodyRuleTests) ... ok
> test_trailing_whitespace (rules.test_body_rules.BodyRuleTests) ... ok
> test_ignore_by_body (rules.test_configuration_rules.ConfigurationRuleTests) 
> ... ok
> test_ignore_by_title (rules.test_configuration_rules.ConfigurationRuleTests) 
> ... ok
> test_author_valid_email_rule (rules.test_meta_rules.MetaRuleTests) ... ok
> test_author_valid_email_rule_custom_regex 
> (rules.test_meta_rules.MetaRuleTests) ... ok
> test_hard_tabs (rules.test_title_rules.TitleRuleTests) ... ok
> test_leading_whitespace (rules.test_title_rules.TitleRuleTests) ... ok
> test_max_line_length (rules.test_title_rules.TitleRuleTests) ... ok
> test_regex_matches (rules.test_title_rules.TitleRuleTests) ... ok
> test_title_must_not_contain_word (rules.test_title_rules.TitleRuleTests) ... 
> ok
> test_trailing_punctuation (rules.test_title_rules.TitleRuleTests) ... ok
> test_trailing_whitespace (rules.test_title_rules.TitleRuleTests) ... ok
> test_assert_valid_rule_class (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative (rules.test_user_rules.UserRuleTests) 
> ... ok
> test_assert_valid_rule_class_negative_id 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative_name 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative_option_spec 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative_parent 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative_target 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_assert_valid_rule_class_negative_validate 
> (rules.test_user_rules.UserRuleTests) ... ok
> test_empty_user_classes (rules.test_user_rules.UserRuleTests) ... ok
> test_extra_path_specified_by_file (rules.test_user_rules.UserRuleTests) ... ok
> test_failed_module_import (rules.test_user_rules.UserRuleTests) ... ok
> test_find_rule_classes (rules.test_user_rules.UserRuleTests) ... ok
> test_find_rule_classes_nonexisting_path (rules.test_user_rules.UserRuleTests) 
> ... ok
> test_rules_from_init_file (rules.test_user_rules.UserRuleTests) ... ok
> test_config_file (test_cli.CLITests)
> Test for --config option ... ok
> test_config_file_

Bug#954197: gegl: FTBFS (most often on arm64, armhf): gegl:simple / backend-file times out

[Simon McVittie]

Control: reassign -1 libglib2.0-0 2.62.2-3
Control: affects -1 + src:gegl
Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/issues/1941
Control: tags -1 + upstream

On Wed, 18 Mar 2020 at 09:31:50 +, Simon McVittie wrote:
> From the backtrace below it appears that there is a deadlock between
> threads 1 and 6, which are both waiting for the same mutex. This might
> be a GLib bug.

Looks like . The
workaround, which gegl might be able to use, is to always cancel
file monitors before their last-unref is reached.

smcv

Processed: Re: Bug#954197: gegl: FTBFS (most often on arm64, armhf): gegl:simple / backend-file times out

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libglib2.0-0 2.62.2-3
Bug #954197 [src:gegl] gegl: FTBFS (most often on arm64, armhf): gegl:simple / 
backend-file times out
Bug reassigned from package 'src:gegl' to 'libglib2.0-0'.
No longer marked as found in versions gegl/0.4.18-1.
Ignoring request to alter fixed versions of bug #954197 to the same values 
previously set
Bug #954197 [libglib2.0-0] gegl: FTBFS (most often on arm64, armhf): 
gegl:simple / backend-file times out
Marked as found in versions glib2.0/2.62.2-3.
> affects -1 + src:gegl
Bug #954197 [libglib2.0-0] gegl: FTBFS (most often on arm64, armhf): 
gegl:simple / backend-file times out
Added indication that 954197 affects src:gegl
> forwarded -1 https://gitlab.gnome.org/GNOME/glib/issues/1941
Bug #954197 [libglib2.0-0] gegl: FTBFS (most often on arm64, armhf): 
gegl:simple / backend-file times out
Changed Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/glib/issues/1941' from 
'https://gitlab.gnome.org/GNOME/gegl/issues/226'.
> tags -1 + upstream
Bug #954197 [libglib2.0-0] gegl: FTBFS (most often on arm64, armhf): 
gegl:simple / backend-file times out
Added tag(s) upstream.

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

Bug#943238: sshuttle: Python2 removal in sid/bullseye

[Adrian Bunk]

Control: notforwarded -1

On Wed, Feb 19, 2020 at 05:14:46PM +1100, Brian May wrote:
> For reference, upgrading this to Python 3 should be simple. sshuttle
> works fine with Python <= 3.7.
>...

sshuttle already uses Python 3 in stable.

For the Python 2 removal the only problem are the (stale?) build 
dependencies on
  python-pytest-runner, python-pytest-cov

Python 3.8 is a separate issue that can be tracked in #953621.

cu
Adrian

Processed: Re: Bug#943238: sshuttle: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> notforwarded -1
Bug #943238 [src:sshuttle] sshuttle: Python2 removal in sid/bullseye
Unset Bug forwarded-to-address

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

Bug#954197: gegl: FTBFS (most often on arm64, armhf): gegl:simple / backend-file times out

[Simon McVittie]

On Wed, 18 Mar 2020 at 08:29:06 +, Simon McVittie wrote:
> https://gitlab.gnome.org/GNOME/gegl/issues/226 appears to be the same thing
> on x86_64. I suspect it might be a race condition or otherwise
> intermittent: in the past this test also timed out on armel, but my recent
> upload worked fine on armel. Perhaps there is something about the ARM
> family of architectures that makes this more likely to happen there.

I reproduced this on the arm64 porterbox 'amdahl' by running that test
1000 times in a loop. After a while, output stopped.

>From the backtrace below it appears that there is a deadlock between
threads 1 and 6, which are both waiting for the same mutex. This might
be a GLib bug.

smcv

Thread 6 (Thread 0x95366ce0 (LWP 1856)):
#0  syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:38
#1  0x97f6f588 in g_mutex_lock_slowpath (mutex=0x97cee280 
) at ../../../glib/gthread-posix.c:1457
#2  0x97f700b8 in g_mutex_lock (mutex=) at 
../../../glib/gthread-posix.c:1482
#3  0x97c4c00c in _ih_sub_cancel (sub=0xc48fad60) at 
../../../gio/inotify/inotify-helper.c:121
#4  0x97c4c2a8 in g_inotify_file_monitor_cancel (monitor=) at ../../../gio/inotify/ginotifyfilemonitor.c:75
#5  0x97b6b474 in g_file_monitor_cancel (monitor=0xc48fd410 
[GInotifyFileMonitor]) at ../../../gio/gfilemonitor.c:241
#6  g_file_monitor_cancel (monitor=0xc48fd410 [GInotifyFileMonitor]) at 
../../../gio/gfilemonitor.c:235
#7  0x97b6b51c in g_file_monitor_dispose (object=0xc48fd410 
[GInotifyFileMonitor]) at ../../../gio/gfilemonitor.c:123
#8  0x97c409d4 in g_local_file_monitor_dispose (object=0xc48fd410 
[GInotifyFileMonitor]) at ../../../gio/glocalfilemonitor.c:814
#9  0x97e784f8 in g_object_unref (_object=) at 
../../../gobject/gobject.c:3461
#10 g_object_unref (_object=0xc48fd410) at ../../../gobject/gobject.c:3391
#11 0x97c40358 in g_file_monitor_source_handle_event 
(fms=0xc48faa50, 
event_type=event_type@entry=G_FILE_MONITOR_EVENT_CHANGES_DONE_HINT, 
child=0x84001470 "buf_a.gegl", rename_to=rename_to@entry=0x0, 
other=other@entry=0x0, event_time=) at 
../../../gio/glocalfilemonitor.c:455
#12 0x97c4bbe4 in ih_event_callback (event=0x84001430, 
sub=0xc48fad60, file_event=) at 
../../../gio/inotify/inotify-helper.c:206
#13 0x97c4b13c in ip_event_dispatch 
(dir_list=dir_list@entry=0xc48f7d80 = {...}, file_list=0x0, 
event=event@entry=0x84001430) at ../../../gio/inotify/inotify-path.c:492
#14 0x97c4b2f4 in ip_event_dispatch (event=0x84001430, 
file_list=, dir_list=0xc48f7d80 = {...}) at 
../../../gio/inotify/inotify-path.c:547
#15 ip_event_callback (event=0x84001430) at 
../../../gio/inotify/inotify-path.c:547
#16 ip_event_callback (event=0x84001430) at 
../../../gio/inotify/inotify-path.c:529
#17 0x97c4a4f8 in ik_source_dispatch (source=0xc48fa5f0, 
func=0x97c4b210 , user_data=) at 
../../../gio/inotify/inotify-kernel.c:327
#18 0x97f2235c in g_main_dispatch (context=0xc48fa6b0) at 
../../../glib/gmain.c:3309
#19 g_main_context_dispatch (context=context@entry=0xc48fa6b0) at 
../../../glib/gmain.c:3974
#20 0x97f22708 in g_main_context_iterate 
(context=context@entry=0xc48fa6b0, block=block@entry=1, 
dispatch=dispatch@entry=1, self=) at ../../../glib/gmain.c:4047
#21 0x97f227ac in g_main_context_iteration (context=0xc48fa6b0, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:4108
#22 0x97f227fc in glib_worker_main (data=) at 
../../../glib/gmain.c:5996
#23 0x97f4bcec in g_thread_proxy (data=0xc48fbd20) at 
../../../glib/gthread.c:807
#24 0x97a0b998 in start_thread (arg=0xfc63b24f) at 
pthread_create.c:479
#25 0x97dc16ac in thread_start () at 
../sysdeps/unix/sysv/linux/aarch64/clone.S:78

Thread 5 (Thread 0x95b67ce0 (LWP 1855)):
#0  syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:38
#1  0x97f701dc in g_cond_wait (cond=cond@entry=0x981bf9d0 
, mutex=mutex@entry=0x981bf998 ) at 
../../../glib/gthread-posix.c:1540
#2  0x98149d70 in gegl_tile_backend_file_writer_thread 
(ignored=) at ../gegl/buffer/gegl-tile-backend-file-async.c:257
#3  0x97f4bcec in g_thread_proxy (data=0xc4865120) at 
../../../glib/gthread.c:807
#4  0x97a0b998 in start_thread (arg=0xfc63b5ff) at 
pthread_create.c:479
#5  0x97dc16ac in thread_start () at 
../sysdeps/unix/sysv/linux/aarch64/clone.S:78

Thread 4 (Thread 0x96368ce0 (LWP 1854)):
#0  syscall () at ../sysdeps/unix/sysv/linux/aarch64/syscall.S:38
#1  0x97f701dc in g_cond_wait (cond=cond@entry=0x981bd228 
, mutex=mutex@entry=0x981bd220 
) at ../../../glib/gthread-posix.c:1540
#2  0x9811d4e0 in gegl_parallel_distribute_thread_func 
(thread=0x981bd218 ) at 
../gegl/gegl-parallel.c:508
#3  0x97f4bcec in g_thread_proxy (data=0x

Processed: severity of 953621 is serious

[Debian Bug Tracking System]

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

> severity 953621 serious
Bug #953621 [sshuttle] sshutle not working in connecting sid boxes due to 
python 3.8 version at endpoint
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: forcibly merging 952621 934949

[Debian Bug Tracking System]

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

> forcemerge 952621 934949
Bug #952621 [src:clips] clips: FTBFS: build-dependency not installable: 
pdf2htmlex
Bug #934949 [src:clips] clips: build-depends on removed package pdf2htmlex
Added tag(s) ftbfs, sid, and bullseye.
Merged 934949 952621
> thanks
Stopping processing here.

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

Processed: tagging 951624

[Debian Bug Tracking System]

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

> tags 951624 + ftbfs
Bug #951624 [src:webdis] webdis, build-depends on removed package
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: block 951620 with 881009 934949

[Debian Bug Tracking System]

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

> block 951620 with 881009 934949
Bug #951620 [src:clips] clips: fails to migrate to testing for too long
951620 was not blocked by any bugs.
951620 was not blocking any bugs.
Added blocking bug(s) of 951620: 952621, 934949, and 881009
> thanks
Stopping processing here.

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

Bug#950860: marked as done (sfepy fails build2 autopkg test with python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 18 Mar 2020 11:21:38 +0200
with message-id <20200318092138.GA23880@localhost>
and subject line Re: Bug#950860: sfepy fails build2 autopkg test with python 3.8
has caused the Debian Bug report #950860,
regarding sfepy fails build2 autopkg test with python 3.8
to be marked as done.

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

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


-- 
950860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:sfepy
Version: 2019.4-2
Severity: important
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.8

sfepy fails build2 autopkg test with python 3.8. Also the build2 *loops* over
py3versions -d, just the default version.

[...]
autopkgtest [23:30:01]: test build2: [---
run: python3.8
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ubuntu'
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sfepy/postprocess/viewer.py", line 10, in

from enthought.traits.api \
ModuleNotFoundError: No module named 'enthought'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "linear_elastic_interactive.py", line 18, in 
from sfepy.postprocess.viewer import Viewer
  File "/usr/lib/python3/dist-packages/sfepy/postprocess/viewer.py", line 27, in

from tvtk.pyface.scene_editor import SceneEditor
  File "/usr/lib/python3/dist-packages/tvtk/pyface/scene_editor.py", line 12, in

SceneEditor = toolkit_object('scene_editor:SceneEditor')
  File "/usr/lib/python3/dist-packages/pyface/base_toolkit.py", line 144, in
__call__
module = import_module(mname, package)
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "/usr/lib/python3/dist-packages/tvtk/pyface/ui/qt4/scene_editor.py", line
19, in 
from .decorated_scene import DecoratedScene
  File "/usr/lib/python3/dist-packages/tvtk/pyface/ui/qt4/decorated_scene.py",
line 19, in 
from tvtk.api import tvtk
  File "/usr/lib/python3/dist-packages/tvtk/api.py", line 10, in 
from tvtk.tvtk_access import tvtk
  File "/usr/lib/python3/dist-packages/tvtk/tvtk_access.py", line 34, in 

from tvtk.tvtk_classes.vtk_version import vtk_build_version
  File "", line 991, in _find_and_load
  File "", line 971, in _find_and_load_unlocked
  File "", line 914, in _find_spec
  File "", line 1342, in find_spec
  File "", line 1316, in _get_spec
  File "", line 1297, in _legacy_get_spec
  File "", line 414, in spec_from_loader
  File "", line 649, in
spec_from_file_location
  File "", line 191, in get_filename
  File "", line 711, in _get_module_code
  File "", line 611, in _unmarshal_code
NameError: name '_boostrap_external' is not defined
--- End Message ---
--- Begin Message ---
On Fri, Feb 07, 2020 at 02:51:14PM +0100, Matthias Klose wrote:
>...
> from tvtk.pyface.scene_editor import SceneEditor
>...

This is expected to fail when mayavi2 has not been rebuilt for the 
default python3, rebuilding that fixed it:
https://ci.debian.net/packages/s/sfepy/unstable/amd64/

cu
Adrian--- End Message ---

Processed: tagging 949919

[Debian Bug Tracking System]

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

> tags 949919 + bullseye sid
Bug #949919 {Done: =?utf-8?b?U1ogTGluICjmnpfkuIrmmbop?= } 
[src:libgpiod] libgpiod: ftbfs; needs explicit dependency on dh-python
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Bug#954134: [d-i bullseye alpha2] installing grub fails

[Holger Wansing]

Hi,

Holger Wansing  wrote:
> Hi,
> 
> Am Dienstag, 17. März 2020 schrieb Steve McIntyre:
> Yes, I had it with alpha2, then tested with alpha1 (everything
> fine) and then again tested with alpha2 to be able to
> provide logs.
> 
> I can do further tests though, with different partitioning
> scheme or filesystem type...

I tried different approaches (use only one ext4 partition + swap; use only one
ext2 partition + swap; use only one xfs partition + swap; create a complete 
new parition table and then use only one ext4 partition + swap) and all fail 
with the same error.

Now I will test again with alpha1 to make sure it is no hardware issue...


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#951821: gegl: FTBFS on arm*/mips* architectures; testing migration blocked

[Simon McVittie]

On Sat, 22 Feb 2020 at 00:23:13 -0500, Boyuan Yang wrote:
> Looking into the current status, it fails to build on all ARM and MIPS
> architectures. The reasons are mostly timeout in tests. Please make some
> investigation and consider increasing the timeout limit or ignore test errors
> during building.

I recently uploaded gegl_0.4.22-2 which increases the timeout on slower
architectures. This reveals that there were several different failure modes:

- Some tests were genuinely just slow. Previously, they often timed out
  on the slower machines; now they pass.

- gegl:simple / backend-file sometimes times out with no output, especially
  on the arm* family (but an upstream bug report suggests that this can
  also happen on x86_64). I've opened a separate FTBFS bug #954197
  to represent this.

- The "tests/compositions/reference/rgbe-save.hdr" step in
  gegl:compositions / compositions_without_opencl fails on mipsel (only):
  the composed image differs from the reference. I've opened a separate
  FTBFS bug #954196 to represent this.

- gegl:simple / buffer-sharing failing on Hurd appears to be Hurd-specific.
  We already had #892238 (non-RC).

- gegl:ff-load-save / ff-load-save fails on ia64, which appears to be
  because examples/frame-counter segfaults.

I am reluctant to ignore test failures on arm* and mips*, because those
are precisely the sort of architectures where we claim that packages
work, but due to their much smaller number of users, automated tests
are our only actual evidence that those packages really do work.

On Thu, 12 Mar 2020 at 15:36:20 -0400, Boyuan Yang wrote:
> On Sun, 23 Feb 2020 00:05:54 +0100 Andreas Henriksson 
> wrote:
> > I'm disabling parallel tests via 'dh_auto_test --no-parallel' now
> > but it seems there are more test failures on the archs where
> > the build failed previously.
> 
> Any progress on it?  If it still takes much time, I suggest we force single-
> thread build first and investigate later since the current FTBFS is blocking
> many packages.

Forcing serial testing was already done since 2020-02-22, in 0.4.22-1.

smcv

Bug#953540: [Aspectc-developers] Fwd: Bug#953540: aspectc++: FTBFS on armel

[Adrian Bunk]

On Tue, Mar 17, 2020 at 05:35:13PM -0400, Reinhard Tartler wrote:
> Control: forwarded -1 aspectc-develop...@aspectc.org
> 
> Hi Adrian,
> 
> Olaf, the upstream developer, has a question regarding your patch to 
> aspectc++.
> Would you mind having a look and ideally sharing your reply to everyone?
> 
> Thank you!
> -rt
> 
> On 3/17/20 11:05 AM, Olaf Spinczyk wrote:
> > Hi Reinhard!
> > 
> > Do you understand the reasons behind the patch?
> > 
> > The difference is the following addition for linking:
> > 
> >  -Wl,--as-needed -latomic -Wl,--no-as-needed
> > 
> > (1) I wonder why the atomics (e.g. __atomic_fetch_add_4) are not
> > available by default in armel. They seem to be on most other platforms.

Most other platforms have processor instructions for atomics.
Older arm processors do not,[1] they are implemented with a kernel helper.

It is a bug in gcc that linking with libatomic is not done automatically:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81358

> > (2) Why is "--as-needed ... --no-as-needed" necessary?

It is not necessary.
It avoids linking with libatomic when it is not needed on other platforms.

> > (3) Could -latomic also be placed at the end of the list of libraries
> > (behind the additional libraries needed for Clang 9.0.x)?

The further behind the better, it has to come after static libraries
using it.

> > Cheers,
> > 
> > Olaf

cu
Adrian

[1] The Debian armel port currently has a port baseline of armv5,
the Debian armhf port (including the raspbian rebuild) target
more recent processors with atomic instructions.

Bug#954196: gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ

[Simon McVittie]

On Wed, 18 Mar 2020 at 08:16:20 +, Simon McVittie wrote:
> > (gegl-imgcmp:1189): GEGL-WARNING **: 00:03:06.812: max diff is not a valid 
> > property of gegl:image-compare 0x55776830
> > /<>/tests/compositions/reference/rgbe-save.hdr and 
> > /<>/obj-mipsel-linux-gnu/tests/compositions/output/rgbe-save.hdr
> >  differ

Before my recent 0.4.22-2 upload, this test ("gegl:compositions /
compositions_without_opencl") was timing out after 30 seconds on all the
slower buildds, so we did not have any information on whether it would
have passed or failed if we had waited longer. This is almost certainly
not a regression in 0.4.22.

0.4.22-2 increased the timeout from 30 to 300 seconds on the slower
architectures, giving it time to fail properly (it actually took 107
seconds on mipsel).

smcv

Bug#954197: gegl: FTBFS (most often on arm64, armhf): gegl:simple / backend-file times out

[Simon McVittie]

Source: gegl
Version: 0.4.18-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.gnome.org/GNOME/gegl/issues/226
Control: block 951821 by -1

https://buildd.debian.org/status/fetch.php?pkg=gegl&arch=arm64&ver=0.4.22-2&stamp=1584481529&raw=0
>   1/104 gegl:simple / backend-file  TIMEOUT 300.01 s

It isn't trivial to correlate the test's output with which one it is
(this is a legacy test using unstructured output and no particular testing
framework, and I should have made d/rules cat meson-logs/testlog.txt but
didn't), but I don't think it produced any, which means a fairly trivial
GEGL test didn't make any useful progress on these buildds.

https://gitlab.gnome.org/GNOME/gegl/issues/226 appears to be the same thing
on x86_64. I suspect it might be a race condition or otherwise
intermittent: in the past this test also timed out on armel, but my recent
upload worked fine on armel. Perhaps there is something about the ARM
family of architectures that makes this more likely to happen there.

smcv

Processed: gegl: FTBFS (most often on arm64, armhf): gegl:simple / backend-file times out

[Debian Bug Tracking System]

Processing control commands:

> block 951821 by -1
Bug #951821 [src:gegl] gegl: FTBFS on arm*/mips* architectures; testing 
migration blocked
951821 was blocked by: 954196
951821 was not blocking any bugs.
Added blocking bug(s) of 951821: 954197

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

Processed: gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ

[Debian Bug Tracking System]

Processing control commands:

> block 951821 by -1
Bug #951821 [src:gegl] gegl: FTBFS on arm*/mips* architectures; testing 
migration blocked
951821 was not blocked by any bugs.
951821 was not blocking any bugs.
Added blocking bug(s) of 951821: 954196

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

Bug#954196: gegl: FTBFS on mipsel: tests/compositions/reference/rgbe-save.hdr and .../output/rgbe-save.hdr differ

[Simon McVittie]

Source: gegl
Version: 0.4.22-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 951821 by -1

https://buildd.debian.org/status/fetch.php?pkg=gegl&arch=mipsel&ver=0.4.22-2&stamp=1584490046&raw=0
> [swscaler @ 0x5617e750] No accelerated colorspace conversion found from 
> yuv420p to rgb24.
> missing reference, assuming SUCCESS
> PASS color-reduction.xml
> missing reference, assuming SUCCESS
> PASS jpg-load-datauri.xml
> missing reference, assuming SUCCESS
> PASS pnm-ascii-load.xml
> missing reference, assuming SUCCESS
> PASS pnm-raw-load.xml
> missing reference, assuming SUCCESS
> PASS rgbe-load.xml
> 
> (gegl-imgcmp:1189): GEGL-WARNING **: 00:03:06.812: max diff is not a valid 
> property of gegl:image-compare 0x55776830
> /<>/tests/compositions/reference/rgbe-save.hdr and 
> /<>/obj-mipsel-linux-gnu/tests/compositions/output/rgbe-save.hdr 
> differ
>   wrong pixels   : 165/12288 (1.34%)
>   max ?e : 
> 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000
>   avg ?e (wrong) : 
> 67326627421669684888669005176245981626127818201330704240878079155477023449696839256119546828890322554026762884581407459611684012658109431614078423083822172532225793664776343589445197580928856114285850164049130170201566309394530763936055595205809030148151018621390290944.000(wrong)
>  
> 57895085948248197003310861778540597530344540911046658743056637836873978536706733178284242874418852779814501765638059266549873720618904958362702683089689120708187862881929758991439906547451878104338721332513031507467342755888365810233077968491152966828328813401751945216.000(total)
> FAIL rgbe-save.xml
> missing reference, assuming SUCCESS
> PASS shift.xml
> missing reference, assuming SUCCESS
> PASS stretch-contrast-hsv.xml
> missing reference, assuming SUCCESS
> PASS tiff-load.xml
> missing reference, assuming SUCCESS
> PASS tile.xml
> === Test Results ===
>  tests passed:  9
>  tests skipped: 0
>  tests failed:  1
> ==  FAIL  ==

We can't get the binary output from a failing build on a buildd, so it's
impossible to say whether this is serious or not unless it can be
reproduced on a porterbox or similar (which I'm trying to do now).

smcv

Bug#952097: fixed in spice-gtk 0.37-2

[Laurent Bigonville]

On Tue, 17 Mar 2020 22:06:04 + Debian FTP Masters 
 wrote:


> * debian/control: Add libdrm-dev to the build-dependencies (Closes: 
#952097)


FTR, upstream has removed the include, so libdrm-dev can be removed with 
the next upstream release

Bug#936076: marked as done (python3-numba: numba segfaults when run with python 3.7.4 at numba/_dynfunc.c:52)

[Debian Bug Tracking System]

Your message dated Tue, 17 Mar 2020 23:29:28 -0700
with message-id 
and subject line python3-numba: numba segfaults when run with python 3.7.4 at 
numba/_dynfunc.c:52
has caused the Debian Bug report #936076,
regarding python3-numba: numba segfaults when run with python 3.7.4 at 
numba/_dynfunc.c:52
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.)


-- 
936076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-numba
Version: 0.42.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

Attempting to run any numba code immediately segfaults when running with python
3.7.4.

I found this upstream bug report.
https://github.com/numba/numba/pull/4328

"CPython 3.7.3->3.7.4 changed the size of PyGC_Head, the macro
_PyObject_GC_UNTRACK relied on calling sizeof() on that struct, as it is a
macro it got baked in at compile time and then segfaults happen across the
point version change as the struct size changed."

The simplist solution is to rebuild with python 3.7.4... though then it'll
crash with earlier versions.

Diane



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

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

Versions of packages python3-numba depends on:
ii  libc6   2.28-10
ii  libgcc1 1:9.2.1-4
ii  libgomp19.2.1-4
ii  libstdc++6  9.2.1-4
ii  libtbb2 2019~U8-1
ii  python3 3.7.3-1
ii  python3-llvmlite0.27.0-2
ii  python3-numpy [python3-numpy-abi9]  1:1.16.2-1+b1

Versions of packages python3-numba recommends:
ii  numba-doc  0.42.0-1

Versions of packages python3-numba suggests:
pn  nvidia-cuda-toolkit  

-- no debconf information
--- End Message ---
--- Begin Message ---
Package: python3-numba
Version: 0.48.0-1
thanks

Using the released version 0.48.0-1 I was able to run numba without it
segfaulting.

See below for example run.


Package: python3-numba
Status: install ok installed
Priority: optional
Section: python
Installed-Size: 9350
Maintainer: Debian Science Maintainers <
debian-science-maintain...@lists.alioth.debian.org>
Architecture: amd64
Source: numba
Version: 0.48.0-1
Depends: python3 (<< 3.9), python3 (>= 3.7~), python3-llvmlite (>=
0.27.0~), python3-numpy (>= 1:1.16.0~rc1), python3-numpy-abi9, python3-
pkg-resources, python3:any, libc6 (>= 2.29), libgcc-s1 (>= 3.0),
libgomp1 (>= 4.9), libstdc++6 (>= 5), libtbb2 (>= 2017~U7)
Recommends: numba-doc
Suggests: nvidia-cuda-toolkit
Description: native machine code compiler for Python 3
 Numba compiles native machine code instructions from Python programs
at
 runtime using the LLVM compiler infrastructure. It could be easily
employed
 by decorating individual computation intensive functions in the Python
code.
 Numba could significantly speed up the performance of computations,
and
 optionally supports compilation to run on GPU processors through
Nvidia's
 CUDA platform.
 It integrates well with the Python scientific software stack, and
 especially recognizes Numpy arrays.
 .
 This package contains the modules for Python 3.
Homepage: http://numba.pydata.org/
~/proj$ python3
Python 3.8.2 (default, Feb 25 2020, 13:04:52)
[GCC 9.2.1 20200220] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numba
>>> from numba import jit
>>> import numpy as np
>>>
>>> x = np.arange(100).reshape(10, 10)
>>>
>>> @jit(nopython=True) # Set "nopython" mode for best performance,
equivalent to @njit
... def go_fast(a): # Function is compiled to machine code when called
the first time
... trace = 0
... for i in range(a.shape[0]):   # Numba likes loops
... trace += np.tanh(a[i, i]) # Numba likes NumPy functions
... return a + trace  # Numba likes NumPy broadcasting
...
>>> print(go_fast(x))
[[  9.  10.  11.  12.  13.  14.  15.  16.  17.  18.]
 [ 19.  20.  21.  22.  23.  24.  25.  26.  27.  28.]
 [ 29.  30.  31.  32.  33.  34.  35.  36.  37.  38.]
 [ 39.  40.  41.  42.  43.  44.  45.