Processed: Re: [R-pkg-team] Bug#947001: r-base blocked by r-bioc-{iranges, s4vectors}
Processing control commands: > severity -1 serious Bug #947004 [r-bioc-s4vectors] Tests segfaults (since the r-base-core update?) Severity set to 'serious' from 'normal' -- 947004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947004 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: [R-pkg-team] Bug#947001: r-base blocked by r-bioc-{iranges, s4vectors}
Processing control commands: > severity -1 serious Bug #947001 [r-bioc-iranges] Tests segfaults (since the r-base-core update?) Severity set to 'serious' from 'normal' -- 947001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#942487: [Pkg-rust-maintainers] Bug#942487: Bug#942487: rust-web-sys: Provides header is more than 256K long and it breaks reprepro...
* Ximin Luo [191223 12:58]: > dpkg and all other debian tools support it right now. It is only reprepro > with this artifical constraint, which makes it not work for packages that are > processable by dpkg and other debian tools. If it is artifical, then it is artifically high. It is 128 times more than what almost every single package needs and more than five times what the most absurd package before needed and twice what other tools are said to have had as limit there. I will increase it in reprepro (and maybe might make it configurable to some extent), but there will always be an upper limit. > Are you suggesting that dpkg and other tools have a concrete security problem? dpkg does not check checksums of index files, so it is likely uneffected. If apt has no limit then that likely makes some attacks needlessly easy (though it might have other mitigations in that regard, and there are less things apt has to care about the way it is typically used). Accepting absurd input without confirmation is never a secure way to handle things, though. Bernhard R. Link
Processed: tagging 937212
Processing commands for cont...@bugs.debian.org: > tags 937212 + fixed-upstream Bug #937212 [src:opensips] opensips: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 937212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947303: marked as done (pygopherd: Python2 removal in sid/bullseye)
Your message dated Tue, 24 Dec 2019 06:22:26 + with message-id and subject line Bug#937449: Removed package(s) from unstable has caused the Debian Bug report #947303, regarding pygopherd: 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.) -- 947303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pygopherd Version: 2.0.18.5 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests, in details: (source:pygopherd)Build-Depends-Indep->python (binary:pygopherd)Depends->python (binary:pygopherd)Depends->python-simpletal (binary:pygopherd)Depends->python:any (binary:pygopherd)Depends->python:any (binary:pygfarm)Depends->python-dictclient Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 2.0.18.5+rm Dear submitter, as the package pygopherd 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/937449 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#938507: marked as done (snappea: Python2 removal in sid/bullseye)
Your message dated Tue, 24 Dec 2019 06:23:40 + with message-id and subject line Bug#947232: Removed package(s) from unstable has caused the Debian Bug report #938507, regarding snappea: 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.) -- 938507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:snappea Version: 3.0d3-24 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:snappea 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: 3.0d3-24+rm Dear submitter, as the package snappea 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/947232 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#938783: marked as done (virtio-forwarder: Python2 removal in sid/bullseye)
Your message dated Tue, 24 Dec 2019 06:23:10 + with message-id and subject line Bug#947231: Removed package(s) from unstable has caused the Debian Bug report #938783, regarding virtio-forwarder: 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.) -- 938783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938783 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:virtio-forwarder Version: 1.1.99.51-1~unstable 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:virtio-forwarder 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.1.99.51-1~unstable+rm Dear submitter, as the package virtio-forwarder 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/947231 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 ---
Processed: retitle 937174 to RM: nwsserver -- removal triggered by the Python2 removal
Processing commands for cont...@bugs.debian.org: > retitle 937174 RM: nwsserver -- removal triggered by the Python2 removal Bug #937174 [ftp.debian.org] nwsserver: Python2 removal in sid/bullseye Changed Bug title to 'RM: nwsserver -- removal triggered by the Python2 removal' from 'nwsserver: Python2 removal in sid/bullseye'. > thanks Stopping processing here. Please contact me if you need assistance. -- 937174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 937174 to ftp.debian.org
Processing commands for cont...@bugs.debian.org: > reassign 937174 ftp.debian.org Bug #937174 [src:nwsserver] nwsserver: Python2 removal in sid/bullseye Bug reassigned from package 'src:nwsserver' to 'ftp.debian.org'. No longer marked as found in versions nwsserver/2.0.0-2. Ignoring request to alter fixed versions of bug #937174 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 937174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937174 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 937170 with 941228
Processing commands for cont...@bugs.debian.org: > block 937170 with 941228 Bug #937170 [src:nvpy] nvpy: Python2 removal in sid/bullseye 937170 was not blocked by any bugs. 937170 was blocking: 937695 937907 938168 938198 Added blocking bug(s) of 937170: 941228 > thanks Stopping processing here. Please contact me if you need assistance. -- 937170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937170 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936992: maradns: diff for NMU version 2.0.13-1.3
Control: tags 936992 + patch
Control: tags 936992 + pending
Dear maintainer,
I've prepared an NMU for maradns (versioned as 2.0.13-1.3) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru maradns-2.0.13/debian/changelog maradns-2.0.13/debian/changelog
--- maradns-2.0.13/debian/changelog 2016-08-09 22:39:43.0 +0300
+++ maradns-2.0.13/debian/changelog 2019-12-24 07:48:25.0 +0200
@@ -1,3 +1,11 @@
+maradns (2.0.13-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fixes to make bind2csv2.py compatible with Python 3,
+thanks to Sam Trenholme. (Closes: #936992)
+
+ -- Adrian Bunk Tue, 24 Dec 2019 07:48:25 +0200
+
maradns (2.0.13-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru maradns-2.0.13/debian/control maradns-2.0.13/debian/control
--- maradns-2.0.13/debian/control 2015-10-03 10:37:13.0 +0300
+++ maradns-2.0.13/debian/control 2019-12-24 07:48:25.0 +0200
@@ -4,7 +4,7 @@
Maintainer: Dariusz Dwornikowski
Build-Depends:
debhelper (>= 9),
- python-dev (>= 2.6.6-3~)
+ python3-dev
Standards-Version: 3.9.6
Homepage: http://maradns.org
Vcs-Git: git://anonscm.debian.org/collab-maint/maradns.git
@@ -17,10 +17,10 @@
duende (>= 1.4.12),
lsb-base,
${misc:Depends},
- ${shlibs:Depends}
+ ${shlibs:Depends},
+ ${python3:Depends}
Recommends:
- maradns-zoneserver,
- ${python:Depends}
+ maradns-zoneserver
Suggests:
maradns-deadwood
Description: simple security-focused authoritative Domain Name Service server
diff -Nru maradns-2.0.13/debian/patches/bind2csv2-py3.patch maradns-2.0.13/debian/patches/bind2csv2-py3.patch
--- maradns-2.0.13/debian/patches/bind2csv2-py3.patch 1970-01-01 02:00:00.0 +0200
+++ maradns-2.0.13/debian/patches/bind2csv2-py3.patch 2019-12-24 07:48:25.0 +0200
@@ -0,0 +1,437 @@
+Description: Upstream fixes to make bind2csv2.py compatible with Python 3
+Author: Adrian Bunk
+Bug-Debian: https://bugs.debian.org/936992
+
+--- maradns-2.0.13.orig/tools/bind2csv2.py
maradns-2.0.13/tools/bind2csv2.py
+@@ -1,6 +1,8 @@
+ #!/usr/bin/python
+
+-# Copyright (c) 2006-2007 Sam Trenholme
++# Note: As of 2019, this script will run both in python2 and python3
++
++# Copyright (c) 2006-2007,2019 Sam Trenholme
+ #
+ # TERMS
+ #
+@@ -173,7 +175,7 @@ class buf:
+ elif self.l == "/origin":
+ return "preorigin"
+ else:
+- print "Unknown directive " + self.l
++ print("Unknown directive " + self.l)
+ return "error"
+
+ # Add a current RR to a stream (private method)
+@@ -282,7 +284,7 @@ def process_comment(i,o):
+ z = 0
+ op(o,"#")
+ while z < 1000:
+- a = i.read(1)
++ a = i.read(1).decode('utf-8')
+ if is_newline.match(a):
+ return a
+ else:
+@@ -294,7 +296,7 @@ def process_comment(i,o):
+ # in next
+
+ def get_rr_type(rrname):
+- rrname = string.lower(rrname)
++ rrname = rrname.lower()
+ if rrname == "in":
+ return "error"
+ elif rrname == "a":
+@@ -357,7 +359,7 @@ def get_rr_type(rrname):
+ #return "rr_loc" # Complicated RR with variable # of fields
+ return "rr_variargs" # I'll just let the csv2 code parse this
+ else:
+- print "Error: Unknown RR " + rrname
++ print("Error: Unknown RR " + rrname)
+ return "error"
+
+ # Generic handler that handles parenthesis in a zone file
+@@ -366,10 +368,10 @@ def handle_paren(a,o,state,buffer):
+ if is_pstate.search(state):
+ paren = "_paren"
+ if paren == "" and is_newline.match(a):
+- print "Error: Premature termination of RR"
++ print("Error: Premature termination of RR")
+ return ("error", "", 1, paren)
+ if paren == "_paren" and a == "(":
+- print "Error: Parens don't nest"
++ print("Error: Parens don't nest")
+ retrun ("error", "", 1, paren)
+ if paren == "" and a == "(":
+ op(o," ")
+@@ -413,7 +415,7 @@ def postrr(a,o,state,buffer):
+ (state, buffer, paren, pstr) = handle_paren(a,o,state,buffer)
+ if paren == 1:
+ return (state, buffer)
+- print "Error: Unexpected character after RR " + a
++ print("Error: Unexpected character after RR " + a)
+ return("error","")
+
+ # After the first non-escaped newline at the end of a rr in the
+@@ -433,7 +435,7 @@ def pre_rr(a,o,state,buffer):
+ o.label_reset()
+ o.label_add(a)
+ return("dlabel",buffer)
+- print "Error: Unexpected character before RR " + a
++ print("Error: Unexpected character before RR " + a)
+ return("error","")
+
+ # In the whitespace before a default TTL ("/ttl 12345")
+@@ -445,7 +447,7 @@ def prettl(a,o,state,buffer):
+ op(o,a)
+ o.slash_ttl_set(a)
+ return ("sttl", buffer)
+- print "Error: unexpected character before TTL " + a
++ print("Error: unexpected character before TTL " + a)
+ return("error","")
+
+ # In a default TTL ("/ttl 12345")
+@@ -457,7 +459,7 @@ def sttl(a,o,state,buffer):
+ op(o,a)
+ o.slash_ttl_append(a)
+ return ("sttl", buffer)
+- print "Error: unexpected character in TTL " + a
++ print("Error: unexpected character in TTL " + a)
+
Processed: maradns: diff for NMU version 2.0.13-1.3
Processing control commands: > tags 936992 + patch Bug #936992 [src:maradns] maradns: Python2 removal in sid/bullseye Added tag(s) patch. > tags 936992 + pending Bug #936992 [src:maradns] maradns: Python2 removal in sid/bullseye Added tag(s) pending. -- 936992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936839
Processing commands for cont...@bugs.debian.org: > tags 936839 + fixed-upstream Bug #936839 [src:lepton-eda] lepton-eda: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal blocks updates - 2019-12-24 05:36:24.729691+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # ipython-genutils > block 936744 by 947298 Bug #936744 [src:ipython-genutils] ipython-genutils: Python2 removal in sid/bullseye 936744 was blocked by: 936743 938716 936774 938116 937119 936775 936744 was blocking: 937156 937695 Added blocking bug(s) of 936744: 947298 > # mgltools-geomutils > block 937023 by 947301 Bug #937023 [src:mgltools-geomutils] mgltools-geomutils: Python2 removal in sid/bullseye 937023 was blocked by: 937029 937022 937023 was blocking: 937695 937960 Added blocking bug(s) of 937023: 947301 > # mgltools-mglutil > block 937025 by 947301 Bug #937025 [src:mgltools-mglutil] mgltools-mglutil: Python2 removal in sid/bullseye 937025 was blocked by: 937039 937029 937025 was blocking: 937034 937569 937695 938036 938922 Added blocking bug(s) of 937025: 947301 > # mercurial > block 937009 by 947296 947299 Bug #937009 [src:mercurial] mercurial: Python2 removal in sid/bullseye 937009 was blocked by: 937808 938363 943032 938699 937011 938462 936701 936249 938353 811180 937273 883145 938470 938771 936700 936573 938544 937013 937012 936699 937009 was blocking: 936700 937011 937012 937446 937499 937569 937695 937715 937936 938147 938578 Added blocking bug(s) of 937009: 947296 and 947299 > # mgltools-dejavu > block 937022 by 947301 Bug #937022 [src:mgltools-dejavu] mgltools-dejavu: Python2 removal in sid/bullseye 937022 was blocked by: 937029 937026 937022 was blocking: 937023 937028 937032 937695 937960 Added blocking bug(s) of 937022: 947301 > # mgltools-molkit > block 937026 by 947301 947294 Bug #937026 [src:mgltools-molkit] mgltools-molkit: Python2 removal in sid/bullseye 937026 was blocked by: 937029 937030 936165 937026 was blocking: 937019 937021 937022 937031 937034 937262 937695 937960 Added blocking bug(s) of 937026: 947294 and 947301 > # mgltools-pyautodock > block 937030 by 947294 Bug #937030 [src:mgltools-pyautodock] mgltools-pyautodock: Python2 removal in sid/bullseye 937030 was blocked by: 936165 937030 was blocking: 937026 937695 937960 Added blocking bug(s) of 937030: 947294 > # mgltools-utpackages > block 937037 by 947301 947294 Bug #937037 [src:mgltools-utpackages] mgltools-utpackages: Python2 removal in sid/bullseye 937037 was blocked by: 937029 936165 937037 was blocking: 937695 937960 Added blocking bug(s) of 937037: 947301 and 947294 > # pickleshare > block 937286 by 947297 947298 Bug #937286 [src:pickleshare] pickleshare: Python2 removal in sid/bullseye 937286 was blocked by: 936742 937117 936743 936774 937286 was blocking: 937695 938004 938168 Added blocking bug(s) of 937286: 947298 and 947297 > # python-backports-shutil-get-terminal-size > block 937600 by 947298 Bug #937600 [src:python-backports-shutil-get-terminal-size] python-backports-shutil-get-terminal-size: Python2 removal in sid/bullseye 937600 was blocked by: 936774 936743 937117 937600 was blocking: 937695 938168 Added blocking bug(s) of 937600: 947298 > # python-defaults > block 937695 by 947296 947297 947298 947299 947300 947301 947302 947303 947294 Bug #937695 [src:python-defaults] python-defaults: Python2 removal in sid/bullseye 937695 was blocked by: 938781 936123 937169 945644 937692 938837 936657 937784 936798 945745 938558 937328 938866 942924 943119 936489 943134 936785 937931 937007 936792 937255 943024 938613 937480 937757 936778 943258 936909 945664 936881 938380 937666 937672 936951 936235 937900 937149 938428 936737 936926 936132 937333 937678 937417 938231 936772 938549 936177 937703 935208 936307 938846 937234 937053 938892 938885 936269 938587 938379 936325 938874 943235 943140 945648 936467 936695 946849 937260 937788 936794 938036 937324 938554 936863 942928 938691 945630 943138 937499 936820 937551 937187 937694 936155 938743 945642 937806 943210 936688 937297 936774 943033 943254 937456 937891 937240 936447 945668 937421 937025 937232 936249 936531 942933 938923 937135 938510 938070 943287 945676 943197 938763 937479 938671 936843 937238 936119 938720 938047 936564 938689 936707 943075 937092 938853 946928 937085 937996 938276 936914 938484 938262 936366 936939 943183 942975 937942 936161 938259 937204 943227 937733 937565 849087 936337 938573 938013 938457 938780 938268 936392 942982 937193 942995 936385 937962 938807 936346 936753 943273 938230 936544 937728 936211 937066 937072 943095 937968 937889 938248 936950 942988 936398 937037 937901 943104 938593 943016 936628 937586 937078 936880 937959 938381 937847 937105 936821 937202 937550 936501 936273 938690 938488 936918 938416 938363 943003 936945 936559 938799 937870 943141 937094 936562 937261 937443 938505 937944 938150 936912 938114 936183 938006 938756 936293 942957 938670 937867 943205 943057 936548 937724 934870 937625 945726 943102 938029 937463 938511
Processed: py2removal RC severity updates - 2019-12-24 05:36:24.806320+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # for more details on this severity bump > # hgsubversion is an application, has low popcon (60 < 300), and has 0 > external rdeps or not in testing > severity 947299 serious Bug #947299 [src:hgsubversion] hgsubversion: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # sparkleshare is an application, has low popcon (99 < 300), and has 0 > external rdeps or not in testing > severity 947300 serious Bug #947300 [src:sparkleshare] sparkleshare: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-ipykernel is a module and has 0 external rdeps or not in testing > severity 947297 serious Bug #947297 [src:ipykernel-py2] ipykernel-py2: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # pygfarm is an application, has low popcon (1 < 300), and has 0 external > rdeps or not in testing > severity 947303 serious Bug #947303 [src:pygopherd] pygopherd: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # mercurial-keyring is an application, has low popcon (76 < 300), and has 0 > external rdeps or not in testing > severity 947296 serious Bug #947296 [src:mercurial-keyring] mercurial-keyring: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 947296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947296 947297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947297 947299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947299 947300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947300 947303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936830
Processing commands for cont...@bugs.debian.org: > tags 936830 + fixed-upstream Bug #936830 [src:ldaptor] ldaptor: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: lcm: diff for NMU version 1.3.1+repack1-2.3
Processing control commands: > tags 936829 + patch Bug #936829 [src:lcm] lcm: Python2 removal in sid/bullseye Added tag(s) patch. > tags 936829 + pending Bug #936829 [src:lcm] lcm: Python2 removal in sid/bullseye Added tag(s) pending. -- 936829: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936829 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936829: lcm: diff for NMU version 1.3.1+repack1-2.3
Control: tags 936829 + patch
Control: tags 936829 + pending
Dear maintainer,
I've prepared an NMU for lcm (versioned as 1.3.1+repack1-2.3) and
uploaded it to DELAYED/15. Please feel free to tell me if I should
cancel it.
cu
Adrian
diff -Nru lcm-1.3.1+repack1/debian/changelog lcm-1.3.1+repack1/debian/changelog
--- lcm-1.3.1+repack1/debian/changelog 2019-08-08 05:19:29.0 +0300
+++ lcm-1.3.1+repack1/debian/changelog 2019-12-24 07:22:19.0 +0200
@@ -1,3 +1,10 @@
+lcm (1.3.1+repack1-2.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove the Python2 bindings. (Closes: #936829)
+
+ -- Adrian Bunk Tue, 24 Dec 2019 07:22:19 +0200
+
lcm (1.3.1+repack1-2.2) unstable; urgency=medium
* Replace previous NMU with a new source-only upload.
diff -Nru lcm-1.3.1+repack1/debian/control lcm-1.3.1+repack1/debian/control
--- lcm-1.3.1+repack1/debian/control 2019-08-08 03:49:36.0 +0300
+++ lcm-1.3.1+repack1/debian/control 2019-12-24 07:22:13.0 +0200
@@ -5,7 +5,6 @@
Build-Depends: debhelper (>= 9), dh-autoreconf,
libglib2.0-dev, libtool,
liblua5.2-dev, lua5.2,
- python, python2.7-dev,
default-jdk-headless | java-sdk, libjchart2d-java, libhamcrest-java, junit,
doxygen
Standards-Version: 3.9.8
@@ -63,21 +62,6 @@
.
This package provides the lua interface.
-Package: python-liblcm
-Architecture: any
-Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
- ${python:Depends},
- liblcm-bin
-Provides: ${python:Provides}
-Description: Lightweight Communications and Marshalling
- LCM is a set of libraries and tools for message passing and data marshalling,
- targeted at real-time systems where high-bandwidth and low latency are
- critical. It provides a publish/subscribe message passing model and automatic
- marshalling/unmarshalling code generation with bindings for applications in a
- variety of programming languages.
- .
- This package provides the python interface.
-
Package: liblcm-java
Architecture: any
Depends: liblcm1 (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
diff -Nru lcm-1.3.1+repack1/debian/python-liblcm.install lcm-1.3.1+repack1/debian/python-liblcm.install
--- lcm-1.3.1+repack1/debian/python-liblcm.install 2019-08-08 03:49:36.0 +0300
+++ lcm-1.3.1+repack1/debian/python-liblcm.install 1970-01-01 02:00:00.0 +0200
@@ -1 +0,0 @@
-usr/lib/python2.7
diff -Nru lcm-1.3.1+repack1/debian/rules lcm-1.3.1+repack1/debian/rules
--- lcm-1.3.1+repack1/debian/rules 2019-08-08 03:49:36.0 +0300
+++ lcm-1.3.1+repack1/debian/rules 2019-12-24 07:22:19.0 +0200
@@ -1,7 +1,7 @@
#!/usr/bin/make -f
%:
- dh $@ --with autoreconf --with python2
+ dh $@ --with autoreconf
override_dh_auto_build:
dh_auto_build
Processed: tagging 936825
Processing commands for cont...@bugs.debian.org: > tags 936825 + fixed-upstream Bug #936825 [src:lazyarray] lazyarray: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936825: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936966: londonlaw: Python2 removal in sid/bullseye
Am Sonntag, den 22.12.2019, 22:11 +0200 schrieb Juhani Numminen: > On Fri, 30 Aug 2019 07:25:11 + Matthias Klose > wrote: > > Package: src:londonlawVersion: 0.2.1-20Severity: normalTags: sid > > bullseyeUser: debian-pyt...@lists.debian.org > > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to > > removePython2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > Hello Fuddl, > Do you think we should remove londonlaw from Debian?As far as I know, > there is and will be no python3 support, becauseupstream seems to be > gone.Fedora retired londonlaw in August. > https://bugzilla.redhat.com/show_bug.cgi?id=1731636 > > Regards,Juhani Hi Juhani, I'm fine with the removal of londonlaw due to missing Python 3 support. In case any upstream adds Python 3 support in the future I'll happily package it and upload it to NEW. Cheers - Bruno signature.asc Description: This is a digitally signed message part
Bug#938231: marked as done (python-tunigo: Python2 removal in sid/bullseye)
Your message dated Tue, 24 Dec 2019 04:37:08 + with message-id and subject line Bug#938231: fixed in python-tunigo 1.0.0-4 has caused the Debian Bug report #938231, regarding python-tunigo: 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.) -- 938231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938231 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-tunigo Version: 1.0.0-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-tunigo If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-tunigo Source-Version: 1.0.0-4 We believe that the bug you reported is fixed in the latest version of python-tunigo, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-tunigo package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 23:17:04 -0500 Source: python-tunigo Architecture: source Version: 1.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938231 Changes: python-tunigo (1.0.0-4) unstable; urgency=medium . [ Ondřej Nový ] * d/control: Remove ancient X-Python-Version field * Convert git repository from git-dpm to gbp layout * Use debhelper-compat instead of debian/compat. . [ Sandro Tosi ] * Drop python2 support; Closes: #938231 Checksums-Sha1: 0d164dfadae9ceac47fccd66a0d20b71d90b742e 2109 python-tunigo_1.0.0-4.dsc 5dbc491e0eef91320edcec42082f4e304c158b22 1888 python-tunigo_1.0.0-4.debian.tar.xz d9fce150d216de2026b5777f2ef8119ce95a0de8 7013 python-tunigo_1.0.0-4_source.buildinfo Checksums-Sha256: 9eecc268e137fc857ea6f2c4a6278f2c95be14503131e94235f339f48724895e 2109 python-tunigo_1.0.0-4.dsc
Bug#947266: python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*
Control: tags -1 moreinfo On 12/23/19 10:01 PM, Andreas Beckmann wrote: > python3-geopandas ships files with generic names at the generic location > /usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on > README.txt) with other packages doing the same wrong thing. > Moving this to /usr/lib/python3/dist-packages/examples/geopandas/ should > probably be OK. The packages doesn't install the examples there itself, it seems that pybuild does that without being explicitly told to. This seems to be a bug in pybuild not geopandas. Are you sure this is a bug in geopandas? Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Processed: Re: Bug#947266: python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*
Processing control commands: > tags -1 moreinfo Bug #947266 [python3-geopandas] python3-geopandas: ships /usr/lib/python3/dist-packages/examples/* Added tag(s) moreinfo. -- 947266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947266 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938887: zfec: diff for NMU version 1.5.2-2.1
Sandro Tosi writes: > > I've prepared an NMU for zfec (versioned as 1.5.2-2.1). The diff > is attached to this message. Thanks Sandro. I've merged your patch into Git. Cheers, Vasudev
Processed: py2removal RC severity updates - 2019-12-24 03:36:55.984459+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # for more details on this severity bump > # python-ecasound is a module and has 0 external rdeps or not in testing > severity 936463 serious Bug #936463 [src:ecasound] ecasound: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-liblo is a module and has 0 external rdeps or not in testing > severity 937467 serious Bug #937467 [src:pyliblo] pyliblo: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-logutils is a module and has 0 external rdeps or not in testing > severity 937899 serious Bug #937899 [src:python-logutils] python-logutils: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-pyknon is a module and has 0 external rdeps or not in testing > severity 938072 serious Bug #938072 [src:python-pyknon] python-pyknon: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-tunigo is a module and has 0 external rdeps or not in testing > severity 938231 serious Bug #938231 [src:python-tunigo] python-tunigo: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # python-csound is a module and has 0 external rdeps or not in testing > severity 942972 serious Bug #942972 [src:csound] csound: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > # mma is an application, has low popcon (147 < 300), and has 0 external rdeps > or not in testing > severity 943120 serious Bug #943120 [src:mma] mma: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 936463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936463 937467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937467 937899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937899 938072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938072 938231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938231 942972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942972 943120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947293: libkate: autopkgtest failures due to libkate-tools removal
Package: libkate
Version: 0.4.1-10
Severity: serious
Tags: patch
Justification: autopkgtest regression
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear maintainers,
With the removal of libkate-tools in libkate 0.4.1-10, the libkate
autopkgtest consistently fails, because all of the commands it previously
attempted to run were in the libkate-tools package:
[...]
autopkgtest [12:55:24]: test test-cmd-tools: - - - - - - - - - - stderr - - -
- - - - - - -
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
25: kateenc: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
31: katalyzer: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
37: katedec: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools:
40: errorunable to run katedec: not found
[...]
(https://ci.debian.net/data/autopkgtest/unstable/amd64/libk/libkate/3520793/log.gz)
I think the autopkgtest should simply be dropped, since there is nothing
left for it to do at present. Please see the attached patch.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libkate-0.4.1/debian/tests/control libkate-0.4.1/debian/tests/control
--- libkate-0.4.1/debian/tests/control 2019-11-26 16:03:42.0 -0600
+++ libkate-0.4.1/debian/tests/control 1969-12-31 18:00:00.0 -0600
@@ -1,2 +0,0 @@
-Depends: @
-Tests: test-cmd-tools
diff -Nru libkate-0.4.1/debian/tests/test-cmd-tools
libkate-0.4.1/debian/tests/test-cmd-tools
--- libkate-0.4.1/debian/tests/test-cmd-tools 2019-11-26 16:03:42.0
-0600
+++ libkate-0.4.1/debian/tests/test-cmd-tools 1969-12-31 18:00:00.0
-0600
@@ -1,49 +0,0 @@
-#!/bin/sh
-#
-# Test the kate command line tools to ensure they can run without
-# returning an error.
-
-set -e
-
-retval=0
-
-success() { echo "success:" "$@"; }
-error() { echo "error:" "$@"; retval=1; }
-
-cat > input.srt < 00:00:14,000
-This is a simple subtext block
-that will be encoded into an ogg file.
-
-2
-00:00:15,000 --> 00:00:16,000
-This is the second subtext block.
-
-EOF
-
-if kateenc -t srt -l cy -c SUB -o output.ogg input.srt ; then
-success "kateenc could encode an SRT file to OGG"
-else
-error "unable to run kateenc"
-fi
-
-if katalyzer output.ogg ; then
-success "running katalyzer worked"
-else
-error "unable to run katalyser"
-fi
-
-if katedec output.ogg ; then
-success "running katedec worked"
-else
-error"unable to run katedec"
-fi
-
-if KateDJ --version ; then
-success "running KateDJ worked"
-else
-error "unable to run KateDJ"
-fi
-
-exit $retval
Bug#947292: nyancat-server: package does not include needed systemd file
Package: nyancat-server Version: 1.5.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, After installing nyancat-server and connecting to the socket, the client is disconnected and the following log entries are produced: nyancat-server.socket: Failed to queue service startup job (Maybe the service file is missing or not a template unit?): Invalid argument nyancat-server.socket: Failed with result 'resources'. Found the package does not include the file /lib/systemd/system/nyancat-server@.service This file is in the source, and is included when rebuilding the package. -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages nyancat-server depends on: ii init-system-helpers 1.57 ii nyancat 1.5.1-1+b1 nyancat-server recommends no packages. nyancat-server suggests no packages. -- no debconf information
Bug#945679: marked as done (osc-plugins-dput: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:43:29 -0500 with message-id and subject line Re: osc-plugins-dput: Python2 removal in sid/bullseye has caused the Debian Bug report #945679, regarding osc-plugins-dput: 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.) -- 945679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: osc-plugins-dput Version: 20180227.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 20180227.1-1 On Wed, 27 Nov 2019 23:58:51 + Sandro Tosi wrote: > Source: osc-plugins-dput > Version: 20180227.1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal--- End Message ---
Bug#937809: marked as done (python-hidapi: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 23:36:54 + with message-id and subject line Bug#937809: fixed in python-hidapi 0.7.99.post21-1.1 has caused the Debian Bug report #937809, regarding python-hidapi: 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.) -- 937809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-hidapi Version: 0.7.99.post21-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-hidapi If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-hidapi Source-Version: 0.7.99.post21-1.1 We believe that the bug you reported is fixed in the latest version of python-hidapi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-hidapi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 18:22:52 -0500 Source: python-hidapi Architecture: source Version: 0.7.99.post21-1.1 Distribution: unstable Urgency: medium Maintainer: Richard Ulrich Changed-By: Sandro Tosi Closes: 937809 Changes: python-hidapi (0.7.99.post21-1.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #937809 Checksums-Sha1: 5901ad18146de1031772a1ea7c4001d6cb85cb56 1971 python-hidapi_0.7.99.post21-1.1.dsc c4df6382e5a07da10394b339f96afa74701fcf9f 2092 python-hidapi_0.7.99.post21-1.1.debian.tar.xz a1b5eb3507acf80c9d1521aa24f58f918d8e6811 6374 python-hidapi_0.7.99.post21-1.1_source.buildinfo Checksums-Sha256: d0e3637fc205a578c0d63adbe74ee8e26254398a343c3390cef150bd37ff5f73 1971 python-hidapi_0.7.99.post21-1.1.dsc f0c7ecb8643f39fab02c7c2968fae3652f08a6b0514cb2d57abb5ee064962006 2092 python-hidapi_0.7.99.post21-1.1.debian.tar.xz
Bug#947216: marked as done (yapps2: should this package be removed?)
Your message dated Mon, 23 Dec 2019 18:29:05 -0500 with message-id and subject line Re: Bug#947216: yapps2: should this package be removed? has caused the Debian Bug report #947216, regarding yapps2: should this package be removed? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 947216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947216 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yapps2 Severity: serious Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but python3-yapps2 seems broken beyond repair: #911753, #911752. I believe this is a good enough reason to have this package removed from debian. if i dont hear back within a week with a good reason to keep it, i'll file for its removal. Thanks, Sandro -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- > I've made a DELAYED/10 NMU to fix these bugs, as well as removing the > Python 2 binary package and fixing #911730. I think that gets things thanks for quickly addressing this. I think you can upload your NMU directly to unstable, the maintainer doesnt seem responsive and you're fixing an RC bug. > back into decent shape; will you withdraw this removal request? doing so now -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi--- End Message ---
Processed: python-hidapi: diff for NMU version 0.7.99.post21-1.1
Processing control commands: > tags 937809 + patch Bug #937809 [src:python-hidapi] python-hidapi: Python2 removal in sid/bullseye Added tag(s) patch. -- 937809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937809: python-hidapi: diff for NMU version 0.7.99.post21-1.1
Control: tags 937809 + patch
Dear maintainer,
I've prepared an NMU for python-hidapi (versioned as 0.7.99.post21-1.1). The
diff
is attached to this message.
Regards.
diff -Nru python-hidapi-0.7.99.post21/debian/changelog python-hidapi-0.7.99.post21/debian/changelog
--- python-hidapi-0.7.99.post21/debian/changelog 2017-12-11 03:27:02.0 -0500
+++ python-hidapi-0.7.99.post21/debian/changelog 2019-12-23 18:22:52.0 -0500
@@ -1,3 +1,10 @@
+python-hidapi (0.7.99.post21-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #937809
+
+ -- Sandro Tosi Mon, 23 Dec 2019 18:22:52 -0500
+
python-hidapi (0.7.99.post21-1) unstable; urgency=medium
* New upstream release.
diff -Nru python-hidapi-0.7.99.post21/debian/control python-hidapi-0.7.99.post21/debian/control
--- python-hidapi-0.7.99.post21/debian/control 2017-12-11 03:27:02.0 -0500
+++ python-hidapi-0.7.99.post21/debian/control 2019-12-23 18:22:41.0 -0500
@@ -5,15 +5,12 @@
Priority: optional
Homepage: https://github.com/trezor/cython-hidapi
Build-Depends:
- cython,
cython3,
debhelper (>=9),
dh-python,
libhidapi-dev,
libudev-dev,
libusb-1.0-0-dev,
- python-all-dev,
- python-setuptools,
python3-all-dev,
python3-setuptools,
Standards-Version: 4.1.2
@@ -37,23 +34,3 @@
file (per platform) and a single header.
.
This package contains HIDAPI for Python 3.
-
-Package: python-hid
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Provides: ${python:Provides}
-Description: cython interface to hidapi
- This has been tested with:
- .
- * the PIC18F4550 on the development board from CCS with their example program.
- * the Fine Offset WH3081 Weather Station.
- .
- It works on Linux, Windows XP and OS X.
- .
- HIDAPI is a multi-platform library which allows an application to interface
- with USB and Bluetooth HID-Class devices on Windows, Linux, FreeBSD, and Mac
- OS X. HIDAPI can be either built as a shared library (.so or .dll) or
- can be embedded directly into a target application by adding a single source
- file (per platform) and a single header.
- .
- This package contains HIDAPI for Python 2.
diff -Nru python-hidapi-0.7.99.post21/debian/rules python-hidapi-0.7.99.post21/debian/rules
--- python-hidapi-0.7.99.post21/debian/rules 2017-12-11 03:27:02.0 -0500
+++ python-hidapi-0.7.99.post21/debian/rules 2019-12-23 18:22:48.0 -0500
@@ -11,6 +11,6 @@
rm -f hid.c hidraw.c
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
Bug#947288: freshplayerplugin: FTBFS: No package 'libdrm' found
Source: freshplayerplugin Version: 0.3.9-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, freshplayerplugin cannot be built in a current sid environment any more: -- Checking for modules 'alsa;gio-2.0;x11;xrandr;xrender;xcursor;gl;libdrm;libevent;libevent_pthreads;cairo;pango;pangocairo;pangoft2;freetype2;openssl;icu-uc' -- No package 'libdrm' found CMake Error at /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:458 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-3.15/Modules/FindPkgConfig.cmake:637 (_pkg_check_modules_internal) CMakeLists.txt:45 (pkg_check_modules) -- Configuring incomplete, errors occurred! Andreas freshplayerplugin_0.3.9-2.log.gz Description: application/gzip
Bug#936736: marked as done (input-pad: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 23:05:04 + with message-id and subject line Bug#936736: fixed in input-pad 1.0.3-4 has caused the Debian Bug report #936736, regarding input-pad: 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.) -- 936736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:input-pad Version: 1.0.3-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:input-pad 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: input-pad Source-Version: 1.0.3-4 We believe that the bug you reported is fixed in the latest version of input-pad, 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. Changwoo Ryu (supplier of updated input-pad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 24 Dec 2019 07:47:35 +0900 Source: input-pad Architecture: source Version: 1.0.3-4 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Changwoo Ryu Closes: 936736 Changes: input-pad (1.0.3-4) unstable; urgency=medium . * Team upload. * Upload to unstable * Remove python*-input-pad binary package (Closes: #936736) - Not worth to fix issues. There's no rdep. Checksums-Sha1: e2f087a68d7ab6337621fe57573f248ab1311183 2427 input-pad_1.0.3-4.dsc de22d35203f487af413f8a1c76b12e59d27f4b4c 4944 input-pad_1.0.3-4.debian.tar.xz b27bb3dd2a20c21083d8dba39287467fc0f4f75e 14591 input-pad_1.0.3-4_source.buildinfo Checksums-Sha256: b686c69455b099ac95ec2ca5110663454797794d6643fd808026f1034bfcdce8 2427 input-pad_1.0.3-4.dsc ede3a193cd466d27f3ef439b3c7215bdfc906eafbcd34e38a47673796b5d047b 4944 input-pad_1.0.3-4.debian.tar.xz 398a29aef2648ecc6e3ba688d4d523b4cc16feb7919e0a00075be0f1375ed9b4 14591
Processed: bug 936804 is forwarded to https://github.com/guelfoweb/knock/issues/9
Processing commands for cont...@bugs.debian.org: > forwarded 936804 https://github.com/guelfoweb/knock/issues/9 Bug #936804 [src:knockpy] knockpy: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/guelfoweb/knock/issues/9'. > thanks Stopping processing here. Please contact me if you need assistance. -- 936804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 936803
Processing commands for cont...@bugs.debian.org: > tags 936803 + fixed-upstream Bug #936803 [src:kmodpy] kmodpy: Python2 removal in sid/bullseye Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 936803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938015: marked as done (python-pecan: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 22:51:12 + with message-id and subject line Bug#938015: fixed in python-pecan 1.3.3-2 has caused the Debian Bug report #938015, regarding python-pecan: 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.) -- 938015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pecan Version: 1.3.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-pecan If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pecan Source-Version: 1.3.3-2 We believe that the bug you reported is fixed in the latest version of python-pecan, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pecan package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 20 Oct 2019 19:28:03 +0200 Source: python-pecan Architecture: source Version: 1.3.3-2 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Closes: 938015 Changes: python-pecan (1.3.3-2) unstable; urgency=medium . * Uploading to unstable: * Removes Python 2 support (Closes: #938015). Note that the old Ceph package still needs it, but version 14.2.4, currently in NEW, has Py2 support removed. * Add disable-failing-tests.patch. Checksums-Sha1: 29c7d840eaec828bebd0a00439f671f872ec1014 2454 python-pecan_1.3.3-2.dsc bef1f37fe712948c3f4c1b23fe6f864e6e6d38c5 6052 python-pecan_1.3.3-2.debian.tar.xz a2018baa32e6fe3cd160372e20eb0080ab3eb7a7 8199 python-pecan_1.3.3-2_amd64.buildinfo Checksums-Sha256: 728b0d9eae2057f54161e4285405812ab908f13f636c6c2f08a3c09fb2864fc1 2454 python-pecan_1.3.3-2.dsc 27569a040befeed074ae76eb2dc164888a2073b3d4c18756009e51b72e5c 6052
Bug#938010: marked as done (python-pbkdf2: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 22:35:39 + with message-id and subject line Bug#938010: fixed in python-pbkdf2 1.3+20110613.git2a0fb15~ds0-3.1 has caused the Debian Bug report #938010, regarding python-pbkdf2: 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.) -- 938010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pbkdf2 Version: 1.3+20110613.git2a0fb15~ds0-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-pbkdf2 If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pbkdf2 Source-Version: 1.3+20110613.git2a0fb15~ds0-3.1 We believe that the bug you reported is fixed in the latest version of python-pbkdf2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated python-pbkdf2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 16:51:11 -0500 Source: python-pbkdf2 Architecture: source Version: 1.3+20110613.git2a0fb15~ds0-3.1 Distribution: unstable Urgency: medium Maintainer: Alessio Treglia Changed-By: Sandro Tosi Closes: 938010 Changes: python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python3 support; Closes: #938010 Checksums-Sha1: 14670a165bbb108ddf51916c2d29aa32f777369d 2137 python-pbkdf2_1.3+20110613.git2a0fb15~ds0-3.1.dsc 0465475c9a8ea4772de2cee24244c348e13118e1 4592 python-pbkdf2_1.3+20110613.git2a0fb15~ds0-3.1.debian.tar.xz f6ab56dd66d29077d4b6ad68ec674c493618de9d 6405 python-pbkdf2_1.3+20110613.git2a0fb15~ds0-3.1_source.buildinfo Checksums-Sha256: 02c9fdefd058c3ef540e135c2d80ba423ac164f7397d2ec07acc11fc58572c2b 2137 python-pbkdf2_1.3+20110613.git2a0fb15~ds0-3.1.dsc
Bug#938818: marked as done (whatthepatch: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 22:36:12 + with message-id and subject line Bug#938818: fixed in whatthepatch 0.0.5-2.1 has caused the Debian Bug report #938818, regarding whatthepatch: 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.) -- 938818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:whatthepatch Version: 0.0.5-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:whatthepatch 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: whatthepatch Source-Version: 0.0.5-2.1 We believe that the bug you reported is fixed in the latest version of whatthepatch, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated whatthepatch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 17:21:31 -0500 Source: whatthepatch Architecture: source Version: 0.0.5-2.1 Distribution: unstable Urgency: medium Maintainer: Reinhard Tartler Changed-By: Sandro Tosi Closes: 938818 Changes: whatthepatch (0.0.5-2.1) unstable; urgency=medium . * Non-maintainer upload. * Drop python2 support; Closes: #938818 Checksums-Sha1: 216bcbde31ae2a6df9a8b74fb80e01c13e87b58a 1851 whatthepatch_0.0.5-2.1.dsc 3aa0b2426437d733a64b1622b200e3d9c2b84fe4 2184 whatthepatch_0.0.5-2.1.debian.tar.xz b05afca8f3eda28ca8f3f325a3dea9288cff5488 6319 whatthepatch_0.0.5-2.1_source.buildinfo Checksums-Sha256: 74b759c60496b2e8ccac7b562a06ca2a34e34cbc83115006070f8c4f76d20a6f 1851 whatthepatch_0.0.5-2.1.dsc 579de7c6d89d0d847f6e4cfd8bc3772f43b129e3e988a16cc81df11030c1244b 2184 whatthepatch_0.0.5-2.1.debian.tar.xz e2696ce94986fc8d23d58277b32036b912aa58fea17a9c0f04d75a7614f90798 6319 whatthepatch_0.0.5-2.1_source.buildinfo Files:
Bug#938818: whatthepatch: diff for NMU version 0.0.5-2.1
Control: tags 938818 + patch
Dear maintainer,
I've prepared an NMU for whatthepatch (versioned as 0.0.5-2.1). The diff
is attached to this message.
Regards.
diff -Nru whatthepatch-0.0.5/debian/changelog whatthepatch-0.0.5/debian/changelog
--- whatthepatch-0.0.5/debian/changelog 2018-04-23 08:37:16.0 -0400
+++ whatthepatch-0.0.5/debian/changelog 2019-12-23 17:21:31.0 -0500
@@ -1,3 +1,10 @@
+whatthepatch (0.0.5-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python2 support; Closes: #938818
+
+ -- Sandro Tosi Mon, 23 Dec 2019 17:21:31 -0500
+
whatthepatch (0.0.5-2) unstable; urgency=medium
* Bug fix: "Please drop override of
diff -Nru whatthepatch-0.0.5/debian/control whatthepatch-0.0.5/debian/control
--- whatthepatch-0.0.5/debian/control 2018-04-23 08:34:40.0 -0400
+++ whatthepatch-0.0.5/debian/control 2019-12-23 17:21:14.0 -0500
@@ -2,23 +2,11 @@
Section: python
Priority: extra
Maintainer: Reinhard Tartler
-Build-Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, python3-all, python3-setuptools
+Build-Depends: debhelper (>= 9), dh-python, python3-all, python3-setuptools
Standards-Version: 4.0.0
Homepage: https://github.com/cscorley/whatthepatch
-X-Python-Version: >= 2.6
-X-Python3-Version: >= 3.2
Testsuite: autopkgtest-pkg-python
-Package: python-whatthepatch
-Architecture: all
-Depends: ${python:Depends}, ${misc:Depends}
-Description: Library for parsing patch files (Python 2)
- What The Patch!? is a library for parsing patch files. Its only purpose
- is to read a patch file and get it into some usable form by other
- programs.
- .
- This package installs the library for Python 2.
-
Package: python3-whatthepatch
Architecture: all
Depends: ${python3:Depends}, ${misc:Depends}
diff -Nru whatthepatch-0.0.5/debian/rules whatthepatch-0.0.5/debian/rules
--- whatthepatch-0.0.5/debian/rules 2018-04-23 08:34:40.0 -0400
+++ whatthepatch-0.0.5/debian/rules 2019-12-23 17:21:25.0 -0500
@@ -6,7 +6,7 @@
export PYBUILD_NAME=whatthepatch
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
# If you need to rebuild the Sphinx documentation
Processed: whatthepatch: diff for NMU version 0.0.5-2.1
Processing control commands: > tags 938818 + patch Bug #938818 [src:whatthepatch] whatthepatch: Python2 removal in sid/bullseye Added tag(s) patch. -- 938818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947216: yapps2: should this package be removed?
On Mon, Dec 23, 2019 at 06:42:00PM +, Colin Watson wrote: > On Sun, Dec 22, 2019 at 06:57:24PM -0500, Sandro Tosi wrote: > > Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but > > python3-yapps2 seems broken beyond repair: #911753, #911752. > > > > I believe this is a good enough reason to have this package removed from > > debian. > > if i dont hear back within a week with a good reason to keep it, i'll file > > for > > its removal. > > Please don't - keymapper needs it and isn't itself useless, and I > successfully ported keymapper to Python 3 despite the bugs in yapps2. > The bugs (which I filed) are annoying but not fatal. I've made a DELAYED/10 NMU to fix these bugs, as well as removing the Python 2 binary package and fixing #911730. I think that gets things back into decent shape; will you withdraw this removal request? -- Colin Watson [cjwat...@debian.org]
Processed: found 936854 in 20171104-1, severity of 936854 is serious, tagging 936854
Processing commands for cont...@bugs.debian.org:
> # FTBFS in experimental
> found 936854 20171104-1
Bug #936854 {Done: Raphaël Hertzog }
[src:libewf] libewf: Python2 removal in sid/bullseye
Marked as found in versions libewf/20171104-1 and reopened.
> severity 936854 serious
Bug #936854 [src:libewf] libewf: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> tags 936854 + experimental
Bug #936854 [src:libewf] libewf: Python2 removal in sid/bullseye
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: NMU fix pending in #947282
Processing commands for cont...@bugs.debian.org: > tags 911730 patch pending Bug #911730 [src:yapps2] yapps2: writes __future__ import after preparser Added tag(s) pending and patch. > tags 911752 patch pending Bug #911752 [src:yapps2] yapps2: half of examples in source package broken with Python 3 port Added tag(s) pending and patch. > tags 911753 patch pending Bug #911753 [python3-yapps] python3-yapps: error reporting completely broken in Python 3 port Added tag(s) pending and patch. > tags 938864 patch pending Bug #938864 [src:yapps2] yapps2: Python2 removal in sid/bullseye Added tag(s) pending and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 911730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911730 911752: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911752 911753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911753 938864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python-pbkdf2: diff for NMU version 1.3+20110613.git2a0fb15~ds0-3.1
Processing control commands: > tags 938010 + patch Bug #938010 [src:python-pbkdf2] python-pbkdf2: Python2 removal in sid/bullseye Added tag(s) patch. -- 938010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#938010: python-pbkdf2: diff for NMU version 1.3+20110613.git2a0fb15~ds0-3.1
Control: tags 938010 + patch
Dear maintainer,
I've prepared an NMU for python-pbkdf2 (versioned as
1.3+20110613.git2a0fb15~ds0-3.1). The diff
is attached to this message.
Regards.
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog 2013-07-05 17:48:26.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/changelog 2019-12-23 16:51:11.0 -0500
@@ -1,3 +1,10 @@
+python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Drop python3 support; Closes: #938010
+
+ -- Sandro Tosi Mon, 23 Dec 2019 16:51:11 -0500
+
python-pbkdf2 (1.3+20110613.git2a0fb15~ds0-3) unstable; urgency=low
[ Martin Pitt ]
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/control python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/control
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/control 2013-03-25 08:16:46.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/control 2019-12-23 16:51:11.0 -0500
@@ -4,36 +4,15 @@
Maintainer: Alessio Treglia
Build-Depends:
debhelper (>= 9~),
- python-all,
- python-setuptools,
+ dh-python,
python3-all,
python3-setuptools
-X-Python-Version: >= 2.6
-X-Python3-Version: >= 3.2
XS-Testsuite: autopkgtest
Standards-Version: 3.9.4
Homepage: http://www.dlitz.net/software/python-pbkdf2/
Vcs-Git: git://anonscm.debian.org/collab-maint/python-pbkdf2.git
Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/python-pbkdf2.git
-Package: python-pbkdf2
-Architecture: all
-Depends:
- ${misc:Depends},
- ${python:Depends}
-Description: Python RSA PKCS#5 v2.0 module (Python 2)
- This module implements the password-based key derivation
- function, PBKDF2, specified in RSA PKCS#5 v2.0.
- .
- PKCS#5 v2.0 Password-Based Key Derivation is a key derivation
- function which is part of the RSA Public Key Cryptography
- Standards series. The provided implementation takes a password
- or a passphrase and a salt value (and optionally a iteration
- count, a digest module, and a MAC module) and provides a file-like
- object from which an arbitrarly-sized key can be read.
- .
- This is the Python 2 version of the package.
-
Package: python3-pbkdf2
Architecture: all
Depends:
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python3-pbkdf2.install python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python3-pbkdf2.install
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python3-pbkdf2.install 2013-03-25 08:16:46.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python3-pbkdf2.install 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-usr/lib/python3
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python-pbkdf2.install python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python-pbkdf2.install
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python-pbkdf2.install 2013-03-25 08:16:46.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/python-pbkdf2.install 1969-12-31 19:00:00.0 -0500
@@ -1 +0,0 @@
-usr/lib/python2*
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/rules python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/rules
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/rules 2013-03-25 08:11:43.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/rules 2019-12-23 16:50:52.0 -0500
@@ -2,30 +2,8 @@
export REPACK_SH=$(CURDIR)/debian/repack.sh
-PYTHON2=$(shell pyversions -vr)
-PYTHON3=$(shell py3versions -vr)
-
%:
- dh $@ --with python2,python3
-
-ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-test-python%:
- python$* setup.py test -vv
-
-override_dh_auto_test: $(PYTHON2:%=test-python%) $(PYTHON3:%=test-python%)
-endif
-
-build-python%:
- python$* setup.py build
-
-override_dh_auto_build: $(PYTHON3:%=build-python%)
- dh_auto_build
-
-install-python%:
- python$* setup.py install --root=$(CURDIR)/debian/tmp --install-layout=deb
-
-override_dh_auto_install: $(PYTHON3:%=install-python%)
- dh_auto_install
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_auto_clean:
dh_auto_clean
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control 2013-03-25 08:10:02.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/control 2019-12-23 16:51:04.0 -0500
@@ -1,5 +1,2 @@
-Tests: python-pbkdf2
-Depends: python-pbkdf2
-
Tests: python3-pbkdf2
Depends: python3-pbkdf2
diff -Nru python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python-pbkdf2 python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python-pbkdf2
--- python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python-pbkdf2 2013-07-05 16:07:24.0 -0400
+++ python-pbkdf2-1.3+20110613.git2a0fb15~ds0/debian/tests/python-pbkdf2
Bug#947220: Root cause
I just tested it and the problem is that the dm_cache_smq module is missing from initramfs. Adding it to "/etc/initramfs-tools/modules" and running "update-initramfs -u" addresses the problem. I guess that lvm2 should add dm_cache and dm_cache_smq to /usr/share/initramfs-tools/hooks/lvm2, just like it has dm_mirror and dm_raid.
Bug#947280: src:paraview: FTBFS on armel an mipsel: undefined reference to `__atomic_fetch_add_8'
Package: src:paraview
Version: 5.7.0-3
Severity: serious
Tags: patch
Justification: FTBFS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The same error is spotted in the logs of failed paraview 5.7.0 builds for
armel[1] and mipsel[2]:
/usr/bin/ld: ../../../../lib/mipsel-linux-gnu/libvtkprotobuf-pv5.7.so.5.7:
undefined reference to `__atomic_fetch_add_8'
[1]
https://buildd.debian.org/status/fetch.php?pkg=paraview=armel=5.7.0-3=1576169428=0
[2]
https://buildd.debian.org/status/fetch.php?pkg=paraview=mipsel=5.7.0-1=1570637214=0
Please find attached a patch aiming to solve this problem. Not sure it'll
be sufficient to build successfully, but it should solve this issue at
least.
Thanks,
_g.
- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAl4BOnkACgkQ7+hsbH/+
z4Mb8gf/Zv+G/8fE0SNC1wR9l81HtcduHKpMzvaDV7cuk35kAMr/W60ieLqfaT7p
Z9PPgi3YD+CqElw317qbGwwxQI0VuMDxiSVKEXJsZePrg2Ff25wgy4pwSBpSjel+
9kljY0vTp0QxbO2ryZi846aH46PnQF9bppdhUocNg6igeSB/x9TUHICvyhVQ5ZNS
gKDnR5jcKlk5DIr2TRA9Xa/TEIONfoQAjGs+tNwWDYpLQnwYHQ+vT+9gL80U6MkO
jRnVKbHI0V7KQj4saoQf4eqSz2tX29hecrMQcut43YxCX3YDiomV9CxrWDWAbIOf
rzWBeG0mAHxtzdD55XqbtuN+R8jEQQ==
=z9To
-END PGP SIGNATURE-
diff -Nru paraview-5.7.0/debian/changelog paraview-5.7.0/debian/changelog
--- paraview-5.7.0/debian/changelog 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/changelog 2019-12-23 22:33:43.0 +0100
@@ -1,3 +1,10 @@
+paraview (5.7.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * New patch libatomic.patch: tentative fix for FTBFS on armel and mipsel
+
+ -- Gilles Filippini Mon, 23 Dec 2019 22:33:43 +0100
+
paraview (5.7.0-3) unstable; urgency=medium
* Hard-code Build-Dep on python3.8-dev. This wasn't being pulled in correctly
diff -Nru paraview-5.7.0/debian/patches/libatomic.patch
paraview-5.7.0/debian/patches/libatomic.patch
--- paraview-5.7.0/debian/patches/libatomic.patch 1970-01-01
01:00:00.0 +0100
+++ paraview-5.7.0/debian/patches/libatomic.patch 2019-12-23
22:33:43.0 +0100
@@ -0,0 +1,22 @@
+Index: paraview-5.7.0/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
+===
+--- paraview-5.7.0.orig/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
paraview-5.7.0/ThirdParty/protobuf/vtkprotobuf/src/CMakeLists.txt
+@@ -312,10 +312,16 @@ if (CMAKE_SYSTEM_NAME STREQUAL "Linux")
+ endif ()
+ endif ()
+
++if ((DEB_HOST_MULTIARCH STREQUAL "arm-linux-gnueabi") OR (DEB_HOST_MULTIARCH
STREQUAL "mipsel-linux-gnu"))
++ set(ATOMIC_LIB atomic)
++else ()
++ set(ATOMIC_LIB "")
++endif ()
++
+ target_link_libraries(vtkprotoc
+ PRIVATE
+ ${vtkprotoc_no_as_needed}
+ vtklibprotoc
+ ParaView::protobuf
+-Threads::Threads)
++Threads::Threads ${ATOMIC_LIB})
+ add_executable(ParaView::protoc ALIAS vtkprotoc)
diff -Nru paraview-5.7.0/debian/patches/series
paraview-5.7.0/debian/patches/series
--- paraview-5.7.0/debian/patches/series2019-12-11 10:16:00.0
+0100
+++ paraview-5.7.0/debian/patches/series2019-12-23 22:33:43.0
+0100
@@ -2,3 +2,4 @@
security-format.patch
override-fix.patch
python3.8.patch
+libatomic.patch
diff -Nru paraview-5.7.0/debian/rules paraview-5.7.0/debian/rules
--- paraview-5.7.0/debian/rules 2019-12-11 10:16:00.0 +0100
+++ paraview-5.7.0/debian/rules 2019-12-23 22:33:43.0 +0100
@@ -73,7 +73,8 @@
-DPARAVIEW_ENABLE_PDAL=ON \
-DPARAVIEW_ENABLE_XDMF3=ON \
-DPARAVIEW_ENABLE_MOTIONFX=ON \
- -DPARAVIEW_PLUGIN_ENABLE_EyeDomeLighting=ON
+ -DPARAVIEW_PLUGIN_ENABLE_EyeDomeLighting=ON \
+ -DDEB_HOST_MULTIARCH=$(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
override_dh_auto_configure:
dh_auto_configure -- $(extra_flags)
Bug#947278: xmlelements: missing Build-Depends: dh-python
Source: xmlelements Version: 1.0~prerelease-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, xmlelements/experimental FTBFS: fakeroot debian/rules clean dh clean --with=python2,python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/i386-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base) at (eval 13) line 1. BEGIN failed--compilation aborted at (eval 13) line 1. make: *** [debian/rules:35: clean] Error 255 Andreas xmlelements_1.0~prerelease-2.log.gz Description: application/gzip
Bug#947277: arriero: missing Build-Depends: dh-python
Source: arriero Version: 0.7~20161228-1+build1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, arriero/experimental FTBFS: fakeroot debian/rules clean dh clean --with python3 dh: unable to load addon python3: Can't locate Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl /usr/local/lib/i386-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 /usr/lib/i386-linux-gnu/perl5/5.30 /usr/share/perl5 /usr/lib/i386-linux-gnu/perl/5.30 /usr/share/perl/5.30 /usr/local/lib/site_perl /usr/lib/i386-linux-gnu/perl-base) at (eval 10) line 1. BEGIN failed--compilation aborted at (eval 10) line 1. make: *** [debian/rules:9: clean] Error 255 Andreas arriero_0.7~20161228-1+build1.log.gz Description: application/gzip
Bug#943194: marked as done (raccoon: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 21:54:13 + with message-id and subject line Bug#943194: fixed in raccoon 1.0b-5 has caused the Debian Bug report #943194, regarding raccoon: 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.) -- 943194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: raccoon Version: 1.0b-4 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: raccoon Source-Version: 1.0b-5 We believe that the bug you reported is fixed in the latest version of raccoon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated raccoon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 22:29:04 +0100 Source: raccoon Binary: raccoon Architecture: source all Version: 1.0b-5 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Description: raccoon- preparation of in silico drug screening projects Closes: 943194 Changes: raccoon (1.0b-5) unstable; urgency=medium . * Use 2to3 to port from Python2 to Python3 Closes: #943194 * debhelper-compat 12 * Standards-Version: 4.4.1 * Set upstream metadata fields: Bug-Database. * Build-Depends: dh-python Checksums-Sha1: 7b0be518952b57937545ade8613738e24a85a12a 2009 raccoon_1.0b-5.dsc da3498132e3cf16554a4fb4e0b55e2b662ab6750 24876 raccoon_1.0b-5.debian.tar.xz b16e0633cb332d0772192e0fb260c40553ffe755 55040 raccoon_1.0b-5_all.deb 63792002f4e6c2a6b584323828b0d4cef7ea750e 5793 raccoon_1.0b-5_amd64.buildinfo Checksums-Sha256: 710422cb801d8b58252d99548fbae7326e21ba770a2a823aa6aa579d5caa0619 2009 raccoon_1.0b-5.dsc 3bc58d90f2994160f5824a1c4d6619f8c57ef2d98eea33b1ce11b406b1bc4137 24876 raccoon_1.0b-5.debian.tar.xz 4c915b5baa4d9ffa7925ac99315227988e2f3edd8dceb7232beb7c4dbba624f1 55040
Bug#947211: Regression in libsoxr0 0.1.3-2 makes ffmpeg segfault
> (gdb) bt > #0 __memmove_avx_unaligned_erms () at > ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:416 > #1 0x706c6dcd in memcpy (__len=3556, __src=, > __dest=0x0) at /usr/include/x86_64-linux-gnu/bits/string_fortified.h:34 > #2 _soxr_interleave_f (data_type=, > dest0=0x556386c0, src=, n=889, ch=1, > seed=0x55635e00) at ./src/data-io.c:204 Interesting. It apparently calls a subroutine to perform an *unaligned* memmove on x86. I wonder whether this crash is x86-specific. Thanks for the reproducer, I will look at it after Christmas. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#947274: singularity: missing Build-Depends: python3-setuptools
Source: singularity
Version: 1.0a1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
singularity/experimental FTBFS in a minimal chroot:
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean
Traceback (most recent call last):
File "setup.py", line 5, in
from setuptools import setup, find_packages
ModuleNotFoundError: No module named 'setuptools'
E: pybuild pybuild:341: clean: plugin distutils failed with: exit code=1:
python3.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:4: clean] Error 255
Andreas
singularity_1.0a1-1.log.gz
Description: application/gzip
Processed: reassign 947212 to src:wordpress, forcibly merging 946905 947212
Processing commands for cont...@bugs.debian.org: > reassign 947212 src:wordpress Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release available. Bug reassigned from package 'wordpress' to 'src:wordpress'. No longer marked as found in versions wordpress/5.2.4+dfsg1-1. Ignoring request to alter fixed versions of bug #947212 to the same values previously set > forcemerge 946905 947212 Bug #946905 [src:wordpress] wordpress: WordPress 5.3.1 Security and Maintenance Release Bug #947212 [src:wordpress] wordpress: 5.3.2 new upstream bug-fixing release available. Severity set to 'important' from 'grave' Marked as found in versions wordpress/5.2.4+dfsg1-1. Merged 946905 947212 > thanks Stopping processing here. Please contact me if you need assistance. -- 946905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946905 947212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947273: odhcp6c: FTBFS with GCC 9: error: '__builtin_strncpy' specified bound 16 equals destination size
Source: odhcp6c Version: 1.1+git20160131-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, odhcp6c FTBFS with GCC 9: [ 33%] Building C object CMakeFiles/odhcp6c.dir/src/dhcpv6.c.o /usr/bin/cc -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/build/odhcp6c-1.1+git20160131=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -std=c99 -Wall -Werror -Wextra -pedantic -o CMakeFiles/odhcp6c.dir/src/dhcpv6.c.o -c /build/odhcp6c-1.1+git20160131/src/dhcpv6.c In file included from /usr/include/string.h:494, from /build/odhcp6c-1.1+git20160131/src/dhcpv6.c:22: In function 'strncpy', inlined from 'init_dhcpv6' at /build/odhcp6c-1.1+git20160131/src/dhcpv6.c:132:2: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: error: '__builtin_strncpy' specified bound 16 equals destination size [-Werror=stringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ cc1: all warnings being treated as errors Andreas odhcp6c_1.1+git20160131-1.log.gz Description: application/gzip
Processed: py2removal RC severity updates - 2019-12-23 21:36:41.427720+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # for more details on this severity bump > # python-hglib is a module and has 0 external rdeps or not in testing > severity 937808 serious Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 937808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947272: blt: FTBFS with GCC 9: error: argument 'argv' doesn't match prototype
Source: blt
Version: 2.5.3+dfsg-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
blt/experimental FTBFS, most likely due to GCC 9 bieng the default
compiler nowadays:
x86_64-linux-gnu-gcc -c -Wall -g -O2 -fdebug-prefix-map=/build/blt-2.5.3+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -I. -I.
-I/usr/include/tcl8.7/tk-private/generic
-I/usr/include/tcl8.7/tk-private/generic -I/usr/include/tcl8.7/tk-private/unix
-I/usr/include/tcl8.7 -I/usr/include/tcl8.7/tcl-private/generic
-I/usr/include/tcl8.7/tcl-private/unix bltBgexec.c
In file included from /usr/include/tcl8.7/tcl.h:2383,
from bltInt.h:39,
from bltBgexec.c:30:
bltBgexec.c: In function 'DisableTriggers':
bltBgexec.c:1451:3: warning: passing argument 5 of 'Tcl_UntraceVar2' from
incompatible pointer type [-Wincompatible-pointer-types]
1451 | VariableProc, bgPtr);
| ^~~~
| |
| char * (*)(void *, Tcl_Interp *, char *, char *, int) {aka char *
(*)(void *, struct Tcl_Interp *, char *, char *, int)}
/usr/include/tcl8.7/tclDecls.h:3998:48: note: in definition of macro
'Tcl_UntraceVar'
3998 | Tcl_UntraceVar2(interp, varName, NULL, flags, proc, clientData)
|^~~~
In file included from /usr/include/tcl8.7/tcl.h:2383,
from bltInt.h:39,
from bltBgexec.c:30:
/usr/include/tcl8.7/tclDecls.h:800:34: note: expected 'char * (*)(void *,
Tcl_Interp *, const char *, const char *, int)' {aka 'char * (*)(void *, struct
Tcl_Interp *, const char *, const char *, int)'} but argument is of type 'char
* (*)(void *, Tcl_Interp *, char *, char *, int)' {aka 'char * (*)(void *,
struct Tcl_Interp *, char *, char *, int)'}
800 | int flags, Tcl_VarTraceProc *proc,
|~~^~~~
bltBgexec.c: In function 'BgexecCmd':
bltBgexec.c:1914:12: error: argument 'argv' doesn't match prototype
1914 | char **argv; /* Argument strings. */
|^~~~
bltBgexec.c:50:20: error: prototype declaration
50 | static Tcl_CmdProc BgexecCmd;
|^
In file included from /usr/include/tcl8.7/tcl.h:2383,
from bltInt.h:39,
from bltBgexec.c:30:
bltBgexec.c:2011:59: warning: passing argument 5 of 'Tcl_TraceVar2' from
incompatible pointer type [-Wincompatible-pointer-types]
2011 | if (Tcl_TraceVar(interp, bgPtr->statVar, TRACE_FLAGS, VariableProc,
bgPtr) != TCL_OK) {
| ^~~~
| |
| char *
(*)(void *, Tcl_Interp *, char *, char *, int) {aka char * (*)(void *, struct
Tcl_Interp *, char *, char *, int)}
/usr/include/tcl8.7/tclDecls.h:3995:46: note: in definition of macro
'Tcl_TraceVar'
3995 | Tcl_TraceVar2(interp, varName, NULL, flags, proc, clientData)
| ^~~~
In file included from /usr/include/tcl8.7/tcl.h:2383,
from bltInt.h:39,
from bltBgexec.c:30:
/usr/include/tcl8.7/tclDecls.h:770:23: note: expected 'char * (*)(void *,
Tcl_Interp *, const char *, const char *, int)' {aka 'char * (*)(void *, struct
Tcl_Interp *, const char *, const char *, int)'} but argument is of type 'char
* (*)(void *, Tcl_Interp *, char *, char *, int)' {aka 'char * (*)(void *,
struct Tcl_Interp *, char *, char *, int)'}
770 | Tcl_VarTraceProc *proc,
| ~~^~~~
make[3]: *** [Makefile:270: bltBgexec.o] Error 1
Andreas
blt_2.5.3+dfsg-5.log.gz
Description: application/gzip
Bug#947268: gnat-gps-common: ships /usr/share/javascript/prototype/prototype.js
Package: gnat-gps-common Version: 19.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships a file owned by libjs-prototype: /usr/share/javascript/prototype/prototype.js >From the attached log (scroll to the bottom...): Preparing to unpack .../gnat-gps-common_19.2-1_all.deb ... Unpacking gnat-gps-common (19.2-1) ... dpkg: error processing archive /var/cache/apt/archives/gnat-gps-common_19.2-1_all.deb (--unpack): trying to overwrite '/usr/share/javascript/prototype/prototype.js', which is also in package libjs-prototype 1.7.1-3 Errors were encountered while processing: /var/cache/apt/archives/gnat-gps-common_19.2-1_all.deb Andreas libjs-prototype=1.7.1-3_gnat-gps-common=19.2-1.log.gz Description: application/gzip
Bug#936729: imgsizer: diff for NMU version 2.10-0.1
Control: tags 936729 + patch Control: tags 936729 + pending Dear maintainer, I've prepared an NMU for imgsizer (versioned as 2.10-0.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru imgsizer-2.7/control imgsizer-2.10/control --- imgsizer-2.7/control 1970-01-01 02:00:00.0 +0200 +++ imgsizer-2.10/control 2019-06-12 17:36:12.0 +0300 @@ -0,0 +1,25 @@ +# This is not a real Debian control file, though the syntax is compatible. +# It's project metadata for the shipper tool + +Package: imgsizer + +Description: Fill in WIDTH and HEIGHT attributes for IMG tags. + This tool auto-generates or corrects WIDTH and HEIGHT parameters + into HTML IMG tags, making page loading faster. + +XBS-Destinations: ubuntu-devel-disc...@lists.ubuntu.com + +Homepage: http://www.catb.org/~esr/imgsizer + +X-Repository-URL: https://gitlab.com/esr/imgsizer + +XBS-HTML-Target: index.html + +XBS-Debian-Packages: imgsizer + +XBS-Logo: crate.png + +#XBS-Project-Tags: HTML + +XBS-VC-Tag-Template: %(version)s + diff -Nru imgsizer-2.7/COPYING imgsizer-2.10/COPYING --- imgsizer-2.7/COPYING 2004-08-06 02:59:17.0 +0300 +++ imgsizer-2.10/COPYING 2019-06-12 17:36:12.0 +0300 @@ -1,340 +1,27 @@ - GNU GENERAL PUBLIC LICENSE - Version 2, June 1991 + BSD LICENSE - Copyright (C) 1989, 1991 Free Software Foundation, Inc. - 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA - Everyone is permitted to copy and distribute verbatim copies - of this license document, but changing it is not allowed. +Copyright (c) 2015, Eric S. Raymond +All rights reserved. - Preamble - - The licenses for most software are designed to take away your -freedom to share and change it. By contrast, the GNU General Public -License is intended to guarantee your freedom to share and change free -software--to make sure the software is free for all its users. This -General Public License applies to most of the Free Software -Foundation's software and to any other program whose authors commit to -using it. (Some other Free Software Foundation software is covered by -the GNU Library General Public License instead.) You can apply it to -your programs, too. - - When we speak of free software, we are referring to freedom, not -price. Our General Public Licenses are designed to make sure that you -have the freedom to distribute copies of free software (and charge for -this service if you wish), that you receive source code or can get it -if you want it, that you can change the software or use pieces of it -in new free programs; and that you know you can do these things. - - To protect your rights, we need to make restrictions that forbid -anyone to deny you these rights or to ask you to surrender the rights. -These restrictions translate to certain responsibilities for you if you -distribute copies of the software, or if you modify it. - - For example, if you distribute copies of such a program, whether -gratis or for a fee, you must give the recipients all the rights that -you have. You must make sure that they, too, receive or can get the -source code. And you must show them these terms so they know their -rights. - - We protect your rights with two steps: (1) copyright the software, and -(2) offer you this license which gives you legal permission to copy, -distribute and/or modify the software. - - Also, for each author's protection and ours, we want to make certain -that everyone understands that there is no warranty for this free -software. If the software is modified by someone else and passed on, we -want its recipients to know that what they have is not the original, so -that any problems introduced by others will not reflect on the original -authors' reputations. - - Finally, any free program is threatened constantly by software -patents. We wish to avoid the danger that redistributors of a free -program will individually obtain patent licenses, in effect making the -program proprietary. To prevent this, we have made it clear that any -patent must be licensed for everyone's free use or not licensed at all. - - The precise terms and conditions for copying, distribution and -modification follow. - - GNU GENERAL PUBLIC LICENSE - TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION - - 0. This License applies to any program or other work which contains -a notice placed by the copyright holder saying it may be distributed -under the terms of this General Public License. The "Program", below, -refers to any such program or work, and a "work based on the Program" -means either the Program or any derivative work under copyright law: -that is to say, a work containing the Program or a portion of it, -either verbatim or with modifications and/or translated into another -language. (Hereinafter, translation is included without limitation in -the term "modification".) Each licensee is addressed as "you". - -Activities other than
Bug#936924: Moving libsvm to Debian Science team
On Mon, Dec 23, 2019 at 03:06:37PM -0500, Chen-Tse Tsai wrote: > I have a quick question. Previously the python modules are installed to > /usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead > if I change it to python3? I see this in the policy and this is also what > liblinear uses. Just want to double check. Yes, follow liblinear example. Thanks for your work on this Andreas. -- http://fam-tille.de
Processed: imgsizer: diff for NMU version 2.10-0.1
Processing control commands: > tags 936729 + patch Bug #936729 [src:imgsizer] imgsizer: Python2 removal in sid/bullseye Added tag(s) patch. > tags 936729 + pending Bug #936729 [src:imgsizer] imgsizer: Python2 removal in sid/bullseye Added tag(s) pending. -- 936729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936729 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Fixed
Processing commands for cont...@bugs.debian.org:
> fixed 943923 4.4.0-4
Bug #943923 {Done: Sandro Tosi } [src:python-apptools]
python-apptools: please stop build-depending on python-pandas
Marked as fixed in versions python-apptools/4.4.0-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
943923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#947265: python3-lmfit: ships /usr/lib/python3/dist-packages/examples/*
Package: python3-lmfit Version: 1.0.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, python3-lmfit ships files with generic names at the generic location /usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on README.txt) with other packages doing the same wrong thing. Moving this to /usr/lib/python3/dist-packages/examples/lmfit/ should probably be OK. Andreas
Bug#945660: closed by Sylvestre Ledru (Bug#945660: fixed in llvm-defaults 0.49~exp2)
> python-clang - transitional package to python3-clang > python-lldb - transitional package to python3-lldb i dont think that's how you're supposed to use python- packages - what's the reason for keeping them around as transitionals? people either gets them as a dependency or will need to migrate their code to python3 anyhow; i think it's better to simply remove them Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#947266: python3-geopandas: ships /usr/lib/python3/dist-packages/examples/*
Package: python3-geopandas Version: 0.6.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, python3-geopandas ships files with generic names at the generic location /usr/lib/python3/dist-packages/examples/ causing file clashes (e.g. on README.txt) with other packages doing the same wrong thing. Moving this to /usr/lib/python3/dist-packages/examples/geopandas/ should probably be OK. Andreas
Processed: Reassign to src
Processing commands for cont...@bugs.debian.org:
> reassign 943923 src:python-apptools 4.4.0-3
Bug #943923 {Done: Sandro Tosi } [python-apptools]
python-apptools: please stop build-depending on python-pandas
Bug reassigned from package 'python-apptools' to 'src:python-apptools'.
No longer marked as found in versions python-apptools/4.4.0-3.
No longer marked as fixed in versions python-apptools/4.4.0-4.
Bug #943923 {Done: Sandro Tosi } [src:python-apptools]
python-apptools: please stop build-depending on python-pandas
Marked as found in versions python-apptools/4.4.0-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
943923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#943923: (no subject)
Control: reassign -1 src:python-apptools 4.4.0-3
Bug#947263: python3-iniparse: missing Breaks+Replaces: python-iniparse
Package: python3-iniparse Version: 0.4-2.3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-iniparse_0.4-2.3_all.deb ... Unpacking python3-iniparse (0.4-2.3) ... dpkg: error processing archive /var/cache/apt/archives/python3-iniparse_0.4-2.3_all.deb (--unpack): trying to overwrite '/usr/share/doc-base/python-iniparse', which is also in package python-iniparse 0.4-2.2 Errors were encountered while processing: /var/cache/apt/archives/python3-iniparse_0.4-2.3_all.deb cheers, Andreas python-iniparse=0.4-2.2_python3-iniparse=0.4-2.3.log.gz Description: application/gzip
Bug#943923: (no subject)
Control: found -1 src:python-apptools/4.4.0-3 Control: fixed -1 src:python-apptools/4.4.0-4 Attempting to get this package to migrate, which I think it failing because the python-apptools binary package is now gone.
Bug#944043: marked as done (q2-types: autopkgtest fail with pandas 0.25)
Your message dated Mon, 23 Dec 2019 20:39:42 + with message-id and subject line Bug#944043: fixed in q2-types 2019.10.0-1 has caused the Debian Bug report #944043, regarding q2-types: autopkgtest fail with pandas 0.25 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.) -- 944043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: q2-types Version: 2019.7.0-1 Control: block 931557 by -1 https://ci.debian.net/data/autopkgtest/unstable/amd64/q/q2-types/3322976/log.gz --- End Message --- --- Begin Message --- Source: q2-types Source-Version: 2019.10.0-1 We believe that the bug you reported is fixed in the latest version of q2-types, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Liubov Chuprikova (supplier of updated q2-types package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 23 Dec 2019 19:12:50 +0100 Source: q2-types Architecture: source Version: 2019.10.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Liubov Chuprikova Closes: 944043 Changes: q2-types (2019.10.0-1) unstable; urgency=medium . [ Liubov Chuprikova ] * Minor changes in autopkgtest * New upstream version Closes: #944043 * Standards-Version: 4.4.1 . [ Andreas Tille ] * Set upstream metadata fields: Bug-Database, Repository, Repository- Browse. Checksums-Sha1: 75334e104fa1c51c6ba14f8ccef4b02e45437ef4 2164 q2-types_2019.10.0-1.dsc 98ab57d9106b663dd23fc1ca7d6e1e35482dc0de 303549 q2-types_2019.10.0.orig.tar.gz 3b6b4ba4d12b5011fd3301095cdc27655942fab9 5264 q2-types_2019.10.0-1.debian.tar.xz 7db206aeb941e2d85d653af7fd040e4d3ae62378 10102 q2-types_2019.10.0-1_amd64.buildinfo Checksums-Sha256: 0fe24ace451451ba5a447cc16553d9f5434fde59a1a8a91a39f2eb8fb23bee9e 2164 q2-types_2019.10.0-1.dsc cece031130f4213362b902bcf6a8879c62a629ea8a48c786ae84a87a43fbb642 303549 q2-types_2019.10.0.orig.tar.gz ef813045df0fa0e6a8c2beb545059125ab771bb846b57444209bad2a73b3dae3 5264 q2-types_2019.10.0-1.debian.tar.xz 9177fc52df6ad171d31e5e5b35284ed0b67f09d8033b9119f93c1433ded36428 10102 q2-types_2019.10.0-1_amd64.buildinfo Files: 8f114ff90104b8573b4d67969de767c8 2164 science optional q2-types_2019.10.0-1.dsc 8e563e07d3709726f44c638bf40e08b6 303549 science optional q2-types_2019.10.0.orig.tar.gz a5957fa09926a3a70b189c365edccb3b 5264 science optional q2-types_2019.10.0-1.debian.tar.xz cfdf0038ad66a7a540497f77643fed02 10102 science optional q2-types_2019.10.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl4BHUwOHHRpbGxlYUBy a2kuZGUACgkQV4oElNHGRtF3vA//ZGthXf09soDahW98WMr/JiIwvPgFlf5LQqYU 7W5KH1b1kBIpMRGKVfkUBwUiCbw82fYRK3kDq7VprEf5eIgU/v3G1/g7kiHrRD4U Tdqnt7DsMtdwXBPdLntPu+pJf2rh8tftq4UONEKyd//r7pSfeXRmKq7qcBRiUQxL bJngg5B1dZ6KKokbUdvLjrmnTYZuzN8RMLpSL2pse45DrvJTr7gwY3UGxts9UQl2 pQa6L1HiURFS8otrS8svW/lOJywTJXEt3ItkIgn/UimwR7wZhwmsEQz4i7150CZI wmra4s2XBXBn6uFSnRStn4UcGLURHUfIXSONUUxtknDY+FYyh/y7lZL/30664jCN WNUX0lqUPATEyA8TWdQEld9wPNL0J/WeTk+i4im47xF7MlXXnLquT0ev5Lxr5NyE 5/4M2ztCR5+9FoBYxfhpy/DE1vPCXWU0+igrNvTbl0emi56PaIErDkXQsm9y7sIN Lae7ocNJMg8SdaOzAPFyBVd+ZpWiQRsKTq4a+ccV2B4OxI4NA/wfoAkG9IxqWanb Br9P5/90QcgTejpLv+s49G7iRxD7EFl7vhdQyxOD+FNE+iLolDCM8yq33FO2Y0TT 6InTkPDiODknLaCV56/rT4qQjl+3aEK8mdZLxqOWLk4qr8bi5usbfC+oJmEfBrxJ BFum71k= =gQQE -END PGP SIGNATURE End Message ---
Processed: Re: Bug#947211: Regression in libsoxr0 0.1.3-2 makes ffmpeg segfault
Processing control commands: > fixed 944017 0.1.3-1 Bug #944017 [src:libsoxr] libsoxr: autopkgtest regression: segmentation fault Marked as fixed in versions libsoxr/0.1.3-1. > reassign -1 src:libsoxr Bug #947211 [libsoxr0] Regression in libsoxr0 0.1.3-2 makes ffmpeg segfault Bug reassigned from package 'libsoxr0' to 'src:libsoxr'. No longer marked as found in versions libsoxr/0.1.3-2. No longer marked as fixed in versions libsoxr/0.1.3-1. > forcemerge 944017 -1 Bug #944017 [src:libsoxr] libsoxr: autopkgtest regression: segmentation fault Bug #947211 [src:libsoxr] Regression in libsoxr0 0.1.3-2 makes ffmpeg segfault Severity set to 'serious' from 'normal' Marked as fixed in versions libsoxr/0.1.3-1. Marked as found in versions libsoxr/0.1.3-2. Merged 944017 947211 -- 944017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944017 947211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#944486: marked as done (libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev (<< 12.14))
Your message dated Mon, 23 Dec 2019 20:16:04 + with message-id and subject line Bug#944486: fixed in trilinos 12.14.1-2~exp1 has caused the Debian Bug report #944486, regarding libtrilinos-belos-dev: missing Breaks+Replaces: libtrilinos-muelu-dev (<< 12.14) 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.) -- 944486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944486 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtrilinos-belos-dev Version: 12.14.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libtrilinos-belos-dev_12.14.1-1_amd64.deb ... Unpacking libtrilinos-belos-dev:amd64 (12.14.1-1) ... dpkg: error processing archive /var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb (--unpack): trying to overwrite '/usr/include/trilinos/BelosOperatorT.hpp', which is also in package libtrilinos-muelu-dev:amd64 12.12.1-8 Errors were encountered while processing: dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) /var/cache/apt/archives/libtrilinos-belos-dev_12.14.1-1_amd64.deb cheers, Andreas libtrilinos-muelu-dev=12.12.1-8_libtrilinos-belos-dev=12.14.1-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: trilinos Source-Version: 12.14.1-2~exp1 We believe that the bug you reported is fixed in the latest version of trilinos, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 944...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nico Schlömer (supplier of updated trilinos package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Dec 2019 08:51:34 + Source: trilinos Binary: libtrilinos-amesos-dev libtrilinos-amesos12 libtrilinos-amesos2-12 libtrilinos-amesos2-dev libtrilinos-anasazi-dev libtrilinos-anasazi12 libtrilinos-aztecoo-dev libtrilinos-aztecoo12 libtrilinos-belos-dev libtrilinos-belos12 libtrilinos-epetra-dev libtrilinos-epetra12 libtrilinos-epetraext-dev libtrilinos-epetraext12 libtrilinos-galeri-dev libtrilinos-galeri12 libtrilinos-globipack-dev libtrilinos-globipack12 libtrilinos-ifpack-dev libtrilinos-ifpack12 libtrilinos-ifpack2-12 libtrilinos-ifpack2-dev libtrilinos-intrepid-dev libtrilinos-intrepid12 libtrilinos-intrepid2-12 libtrilinos-intrepid2-dev libtrilinos-isorropia-dev libtrilinos-isorropia12 libtrilinos-kokkos-dev libtrilinos-kokkos-kernels-dev libtrilinos-kokkos-kernels12 libtrilinos-kokkos12 libtrilinos-komplex-dev libtrilinos-komplex12 libtrilinos-ml-dev libtrilinos-ml12 libtrilinos-moertel-dev libtrilinos-moertel12 libtrilinos-muelu-dev libtrilinos-muelu12 libtrilinos-nox-dev libtrilinos-nox12 libtrilinos-optipack-dev libtrilinos-optipack12 libtrilinos-pamgen-dev libtrilinos-pamgen12 libtrilinos-phalanx-dev libtrilinos-phalanx12 libtrilinos-pike-dev libtrilinos-pike12 libtrilinos-piro-dev libtrilinos-piro12 libtrilinos-pliris-dev libtrilinos-pliris12 libtrilinos-rol-dev libtrilinos-rol12 libtrilinos-rtop-dev libtrilinos-rtop12 libtrilinos-rythmos-dev libtrilinos-rythmos12 libtrilinos-sacado-dev libtrilinos-sacado12 libtrilinos-shards-dev libtrilinos-shards12 libtrilinos-shylu-dev libtrilinos-shylu12 libtrilinos-stokhos-dev libtrilinos-stokhos12 libtrilinos-stratimikos-dev libtrilinos-stratimikos12 libtrilinos-teko-dev libtrilinos-teko12 libtrilinos-teuchos-dev libtrilinos-teuchos12 libtrilinos-thyra-dev libtrilinos-thyra12 libtrilinos-tpetra-dev libtrilinos-tpetra12 libtrilinos-trilinoscouplings-dev libtrilinos-trilinoscouplings12 libtrilinos-trilinosss-dev libtrilinos-trilinosss12 libtrilinos-triutils-dev libtrilinos-triutils12 libtrilinos-xpetra-dev
Bug#944688: marked as done (trilinos: intrepid2 package is not shipped)
Your message dated Mon, 23 Dec 2019 20:16:04 +
with message-id
and subject line Bug#944688: fixed in trilinos 12.14.1-2~exp1
has caused the Debian Bug report #944688,
regarding trilinos: intrepid2 package is not shipped
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.)
--
944688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.1.1-6
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear maintainer,
Your package is part of the assimp transition. I scheduled binNMU's but you
package fails to build everywhere it build in the past.
Looking at the reproducible-builds infra, it seems your package started to
FTBFS before this transition with the same error. Maybe this is related to the
gcc-9 change?
Paul
https://buildd.debian.org/status/package.php?p=deal.ii
Tail of log for deal.ii on amd64:
Source file was:
#include
int main()
{
int *i = new int;
std::auto_ptr x(i);
return 0;
}
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu
"-DDEAL_II_CXX_FLAGS=-Wno-nonnull-compare -Wno-address"
-DCMAKE_PREFIX_PATH=/usr/lib/x86_64-linux-gnu/hdf5/openmpi\;/usr/include/hdf5/openmpi
-DCMAKE_BUILD_TYPE=DebugRelease -DDEAL_II_ALLOW_AUTODETECTION=OFF
-DDEAL_II_ALLOW_BUNDLED=OFF -DDEAL_II_ALLOW_PLATFORM_INTROSPECTION=OFF
-DDEAL_II_HAVE_FP_EXCEPTIONS=FALSE -DDEAL_II_COMPONENT_DOCUMENTATION=ON
-DDEAL_II_WITH_ARPACK=ON -DDEAL_II_WITH_ASSIMP=ON -DDEAL_II_WITH_BOOST=ON
-DDEAL_II_WITH_BZIP2=ON -DDEAL_II_WITH_GMSH=ON -DDEAL_II_WITH_GSL=ON
-DDEAL_II_WITH_HDF5=ON -DDEAL_II_WITH_LAPACK=ON -DDEAL_II_WITH_MPI=ON
-DDEAL_II_WITH_MUPARSER=ON -DDEAL_II_WITH_NETCDF=ON
-DDEAL_II_WITH_OPENCASCADE=ON -DDEAL_II_WITH_P4EST=ON -DDEAL_II_WITH_PETSC=ON
-DDEAL_II_WITH_SCALAPACK=ON -DDEAL_II_WITH_SLEPC=ON -DDEAL_II_WITH_SUNDIALS=ON
-DDEAL_II_WITH_THREADS=ON -DDEAL_II_WITH_TRILINOS=ON -DDEAL_II_WITH_UMFPACK=ON
-DDEAL_II_WITH_ZLIB=ON -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=OFF
-DDEAL_II_BASE_NAME=deal.ii
-DDEAL_II_DOCHTML_RELDIR=share/doc/libdeal.ii-doc/html
-DDEAL_II_DOCREADME_RELDIR=share/doc/libdeal.ii-doc
-DDEAL_II_EXAMPLES_RELDIR=share/doc/libdeal.ii-doc/examples
-DDEAL_II_LIBRARY_RELDIR=lib/x86_64-linux-gnu
-DDEAL_II_PROJECT_CONFIG_RELDIR=share/cmake/deal.II
-DDEAL_II_SHARE_RELDIR=share/deal.ii/ .. returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-arch] Error 2
- -- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-BEGIN PGP SIGNATURE-
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3MWl4ACgkQnFyZ6wW9
dQrxEAf8CG69Mbfvso8sU1HZrRrDy4Qq7RB+vWDaWYd3MPuXGgsAS+B+h7oyqvJL
G6aCdWz9Z1YOXw5KLDi31R72O24GtBW5wqb9KKDWC049H3ACMXXIf6NU6+13Fsd+
iJZNOWn0C2MJ3KyJL5yrpTze+JAMOYHZXUqaT38EWcI1JoLqf7EchKKdTVPuNJLt
f9reZDe7/25D6e47BHOq5r1/PAkG5HhRe48v72adRW3LPIFY3l2NEv86nxzdfCoA
B4oQS+bDQTSHsct2y96ORkOpGfTBiwr9rq5uLU1dF66YXQQ+V7a09ZhOboUa48+x
+QeCc/XcN+/LADOH8dFWb0RnNhsECw==
=RTT1
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: trilinos
Source-Version: 12.14.1-2~exp1
We believe that the bug you reported is fixed in the latest version of
trilinos, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 944...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nico Schlömer (supplier of updated trilinos package)
(This message was generated automatically at their request; if you
Bug#946984: marked as done (yade: Ships python3.8 scripts, without any python3 or python3.8 deps)
Your message dated Mon, 23 Dec 2019 20:16:14 + with message-id and subject line Bug#946984: fixed in yade 2019.12~git~0~e74819ea-6 has caused the Debian Bug report #946984, regarding yade: Ships python3.8 scripts, without any python3 or python3.8 deps 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.) -- 946984: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946984 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: yade Version: 2019.12~git~0~e74819ea-4 Severity: grave Dear Maintainer, Autopkgtest correctly points out that `yade` cannot be executed in testing, upon migration. yade appears to be switched from python2 to python3 incorrectly as follows. Package yade builds scripts as python3.8, yet depends on python-yade (py2 name by policty) and python:Depends => meaning that --with python3 (dh_python3) does nothing and doesn't generate neither python3 nor python3.8 depends. Then python-yade package is missnamed too, it must be named python3-yade for dh_python3 to process it, and for example correct any scripts shebangs from python3.8 to just python3 (if appropriate). Overall this package will not migrate, and will not work in testing as is. Please 1) correct Package: yade dependency from python:Depends, to python3:Depends 2) correct Package: yade dependency from python-yade, to python3-yade 3) correct Package: python-yade name to python3-yade 4) Rename relevant debian/python-yade.* to debian/python3-yade.* Please do this soon, as yade is due to be autoremoved from testing! Regards, Dimitri. --- End Message --- --- Begin Message --- Source: yade Source-Version: 2019.12~git~0~e74819ea-6 We believe that the bug you reported is fixed in the latest version of yade, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated yade package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Dec 2019 22:17:21 +0100 Source: yade Binary: libyade libyade-dbgsym python3-yade yade yade-doc Architecture: source ppc64el all Version: 2019.12~git~0~e74819ea-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Description: libyade- Platform for discrete element modeling. Libraries python3-yade - Platform for discrete element modeling. Python bindings yade - Platform for discrete element modeling yade-doc - Platform for discrete element modeling. Documentation Closes: 946984 Changes: yade (2019.12~git~0~e74819ea-6) unstable; urgency=medium . * [e6ab441] Rename python-yade -> python3-yade. (Closes: #946984) * [1eb721d] One more try to build yade in parallel mode Checksums-Sha1: c63bbe0d2d2455f3a5196ee5b87e45a5282074f7 3101 yade_2019.12~git~0~e74819ea-6.dsc 4d6551caed8756700ba571433f881ba82558bd58 21360 yade_2019.12~git~0~e74819ea-6.debian.tar.xz 612bf8f4af3a75ea0f28c0306574e4e8089f5190 857867756 libyade-dbgsym_2019.12~git~0~e74819ea-6_ppc64el.deb d900f3e8573f71feb4b2f16ed428716e7f2cd639 10858976 libyade_2019.12~git~0~e74819ea-6_ppc64el.deb 38699dd133f40b74fe6a2f28e28cbf7bc40f4ad0 252836 python3-yade_2019.12~git~0~e74819ea-6_ppc64el.deb 401ff4522051b3e606f064c0d3bc3106b5fcfa21 4906584 yade-doc_2019.12~git~0~e74819ea-6_all.deb f0710d8c61f1dd50396adec75f724a05cbe238fc 29641 yade_2019.12~git~0~e74819ea-6_ppc64el.buildinfo 634d97032c4e79d8acb4d30c642ab795134e13e1 1991888 yade_2019.12~git~0~e74819ea-6_ppc64el.deb Checksums-Sha256: be2f1e231a8b66b171a54c9bed222e8a81534ffdf22408a132eeddd14ba501a4 3101 yade_2019.12~git~0~e74819ea-6.dsc 0e35c3d65e1aa0232eee566846296a881bcecb7136f697c6a43cbae7f21127c9 21360 yade_2019.12~git~0~e74819ea-6.debian.tar.xz 261221e7c49e5321b3b1df0d7ec4172e2fe11008e7836b911cec05612fa93208 857867756 libyade-dbgsym_2019.12~git~0~e74819ea-6_ppc64el.deb 25d35a2530b9f4f7276efb21f2402523fea93e4307f523536cbf4b08afa48519 10858976 libyade_2019.12~git~0~e74819ea-6_ppc64el.deb 6ceb4b64b242f8c7552e883120bcc3706e249f78d512bcd5603872bfe2f1ef2c 252836 python3-yade_2019.12~git~0~e74819ea-6_ppc64el.deb
Bug#938559: marked as done (squaremap: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:15:39 + with message-id and subject line Bug#938559: fixed in squaremap 1:1.0.5-1 has caused the Debian Bug report #938559, regarding squaremap: 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.) -- 938559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:squaremap Version: 1:1.0.4-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:squaremap 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: squaremap Source-Version: 1:1.0.5-1 We believe that the bug you reported is fixed in the latest version of squaremap, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Federico Ceratto (supplier of updated squaremap package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 17 Dec 2019 17:09:59 + Source: squaremap Binary: python3-squaremap Architecture: source all Version: 1:1.0.5-1 Distribution: unstable Urgency: medium Maintainer: Federico Ceratto Changed-By: Federico Ceratto Description: python3-squaremap - wxPython control to display hierarchic data as nested squares Closes: 938559 Changes: squaremap (1:1.0.5-1) unstable; urgency=medium . * New upstream release * Remove Python 2 dependencies (Closes: #938559) Checksums-Sha1: f47bbe4142f9bd1c30c1e141489b55cfd41372b8 1906 squaremap_1.0.5-1.dsc 209cc2ab23f310fbff8e56b22669363535819a3b 7708 squaremap_1.0.5.orig.tar.gz 1dacc200fba43030f75bbe0cca27fc88b83f3597 1712 squaremap_1.0.5-1.debian.tar.xz 5db0e0ba7266a9c61d5e3f8f3ae0a4045528186e 8820 python3-squaremap_1.0.5-1_all.deb accff8c1f670d09b8978d34f4bae1ace90b19883 6000 squaremap_1.0.5-1_amd64.buildinfo Checksums-Sha256: ea718f437da8a875d7b9e4e51b96b95b2bd2f5f75bd6fac92efb3cffb89a1968 1906
Bug#945660: marked as done (llvm-defaults: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:14:39 + with message-id and subject line Bug#945660: fixed in llvm-defaults 0.49~exp2 has caused the Debian Bug report #945660, regarding llvm-defaults: 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.) -- 945660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-defaults Version: 0.48.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 (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: llvm-defaults Source-Version: 0.49~exp2 We believe that the bug you reported is fixed in the latest version of llvm-defaults, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-defaults package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 22 Dec 2019 12:02:55 +0100 Source: llvm-defaults Binary: clang clang-format clang-tidy clang-tools clangd libc++-dev libc++1 libc++abi-dev libc++abi1 libclang-dev libclang1 liblldb-dev libllvm-ocaml-dev libomp-dev libomp5 lld lldb llvm llvm-dev llvm-runtime python-clang python-lldb python3-clang python3-lldb Architecture: source amd64 Version: 0.49~exp2 Distribution: experimental Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Description: clang - C, C++ and Objective-C compiler (LLVM based) clang-format - Tool to format C/C++/Obj-C code clang-tidy - clang-based C++ linter tool clang-tools - clang-based tools clangd - Language server that provides IDE-like features to editors libc++-dev - LLVM C++ Standard library (development files) libc++1- LLVM C++ Standard library libc++abi-dev - LLVM low level support for a standard C++ library (development fi libc++abi1 - LLVM low level support for a standard C++ library libclang-dev - clang library - Development package libclang1 - C, C++ and Objective-C compiler (LLVM based)
Bug#938224: marked as done (python-traitsui: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:15:16 + with message-id and subject line Bug#938224: fixed in python-traitsui 6.1.3-1 has caused the Debian Bug report #938224, regarding python-traitsui: 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.) -- 938224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-traitsui Version: 4.5.1-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:python-traitsui If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-traitsui Source-Version: 6.1.3-1 We believe that the bug you reported is fixed in the latest version of python-traitsui, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Talbert (supplier of updated python-traitsui package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Dec 2019 20:26:19 -0500 Source: python-traitsui Binary: python3-traitsui Architecture: source all Version: 6.1.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Scott Talbert Description: python3-traitsui - traits-capable user interfaces Closes: 938224 Changes: python-traitsui (6.1.3-1) unstable; urgency=medium . [ Scott Talbert ] * Team Upload. * d/watch: switch to https and remove orig-tar * Update to new upstream release 6.1.3 * Remove d/orig-tar.sh * Switch to Python 3 and modernize packaging (Closes: #938224) * Remove wxpython3.0 patch - we are now using Qt backend * d/source/options: ignore changes in _version.py file * d/rules: Remove Windows Thumbs.db file * d/copyright: Convert to DEP5 format . [ Ondřej Nový ] * Fixed homepage (https) * Fixed VCS URL (https) * d/control: Set Vcs-* to salsa.debian.org *
Bug#943961: marked as done (ceph: autopkgtest needs update for new version of python3.7: deprecation warning)
Your message dated Mon, 23 Dec 2019 20:13:28 + with message-id and subject line Bug#943961: fixed in ceph 14.2.4-1 has caused the Debian Bug report #943961, regarding ceph: autopkgtest needs update for new version of python3.7: deprecation warning 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.) -- 943961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceph Version: 12.2.11+dfsg1-2.1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, python...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3.7 Dear maintainers, With a recent upload of python3.7 the autopkgtest of ceph fails in testing when that autopkgtest is run with the binary packages of python3.7 from unstable. It passes when run with only packages from testing. In tabular form: passfail python3.7 from testing3.7.5-2 ceph from testing12.2.11+dfsg1-2.1 all others from testingfrom testing I copied some of the output at the bottom of this report, the failure is on a deprecation *warning*. Please disable warnings like that, or enable the allow-stderr restriction in your test as we don't want autopkgtest to fail on warning in the Debian setup. Currently this regression is blocking the migration of python3.7 to testing [1]. Of course, python3.7 shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in python3.7 was intended and your package needs to update to the new situation. I'll mark your test as allowed to fail to enable python3.7 to migrate. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=python3.7 https://ci.debian.net/data/autopkgtest/testing/amd64/c/ceph/3308028/log.gz autopkgtest [02:14:20]: test python3-ceph: [--- /tmp/autopkgtest-lxc.w6gyq64p/downtmp/build.p0D/src/debian/tests/python3-ceph:8: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated since Python 3.3,and in 3.9 it will stop working import rbd python3-ceph: OK autopkgtest [02:14:20]: test python3-ceph: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: ceph Source-Version: 14.2.4-1 We believe that the bug you reported is fixed in the latest version of ceph, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Nov 2019 14:18:10 +0100 Source: ceph Binary: ceph ceph-base ceph-base-dbgsym ceph-common ceph-common-dbgsym ceph-fuse ceph-fuse-dbgsym ceph-mds ceph-mds-dbgsym ceph-mgr ceph-mgr-dashboard ceph-mgr-dbgsym ceph-mgr-diskprediction-cloud ceph-mgr-diskprediction-local ceph-mgr-rook ceph-mgr-ssh ceph-mon ceph-mon-dbgsym ceph-osd ceph-osd-dbgsym ceph-resource-agents cephfs-shell libcephfs-dev libcephfs-java libcephfs-jni libcephfs-jni-dbgsym libcephfs2 libcephfs2-dbgsym librados-dev librados-dev-dbgsym librados2 librados2-dbgsym libradospp-dev libradosstriper-dev libradosstriper1 libradosstriper1-dbgsym librbd-dev librbd1 librbd1-dbgsym librgw-dev librgw2 librgw2-dbgsym python3-ceph-argparse python3-cephfs python3-cephfs-dbgsym python3-rados python3-rados-dbgsym python3-rbd python3-rbd-dbgsym python3-rgw python3-rgw-dbgsym rados-objclass-dev radosgw radosgw-dbgsym rbd-fuse rbd-fuse-dbgsym rbd-mirror rbd-mirror-dbgsym rbd-nbd rbd-nbd-dbgsym Architecture: source amd64 all Version: 14.2.4-1 Distribution: unstable Urgency: medium Maintainer: Ceph Maintainers Changed-By: Bernd Zeimetz Description: ceph - distributed storage and file system ceph-base - common ceph daemon libraries and management tools
Bug#943014: marked as done (derpconf: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:13:49 + with message-id and subject line Bug#943014: fixed in derpconf 0.8.2-3 has caused the Debian Bug report #943014, regarding derpconf: 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.) -- 943014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943014 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: derpconf Version: 0.8.2-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take2.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: derpconf Source-Version: 0.8.2-3 We believe that the bug you reported is fixed in the latest version of derpconf, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 943...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Marcelo Jorge Vieira (supplier of updated derpconf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 26 Nov 2019 21:00:06 -0300 Source: derpconf Binary: python3-derpconf Architecture: source all Version: 0.8.2-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Marcelo Jorge Vieira Description: python3-derpconf - Python module to abstract loading configuration files for your ap Closes: 936386 943014 Changes: derpconf (0.8.2-3) unstable; urgency=medium . [ Ondřej Nový ] * d/copyright: Use https protocol in Format field. * Use debhelper-compat instead of debian/compat. . [ Marcelo Jorge Vieira ] * py3 support (Closes: #943014, #936386) Checksums-Sha1: a84f1a10b470600a81985056792873487a1c0616 2166 derpconf_0.8.2-3.dsc b321de71cf85501120755f64bd3b5079542d2163 2972 derpconf_0.8.2-3.debian.tar.xz cc37eaf2c1b512ce1263d02b79d1c8927d28b16e 7404 derpconf_0.8.2-3_amd64.buildinfo 90db3452f9d7cd54670f4e0287cda51980d7f39e 9072 python3-derpconf_0.8.2-3_all.deb Checksums-Sha256: 32216824bfa53e41ab6ce80e2cdb6fbc6279ea7e941e18126969170ce3ffd3d3 2166 derpconf_0.8.2-3.dsc 7c5589948180059b19322af906d3f8c787b21f2d735b7351f7aa975bf64e4e23 2972
Bug#938058: marked as done (python-pydot-ng: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:15:15 + with message-id and subject line Bug#938058: fixed in python-pydot-ng 1.0.0-4 has caused the Debian Bug report #938058, regarding python-pydot-ng: 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.) -- 938058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-pydot-ng Version: 1.0.0-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-pydot-ng If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: python-pydot-ng Source-Version: 1.0.0-4 We believe that the bug you reported is fixed in the latest version of python-pydot-ng, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated python-pydot-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 20 Dec 2019 11:24:48 +0100 Source: python-pydot-ng Binary: python3-pydot-ng Architecture: source all Version: 1.0.0-4 Distribution: unstable Urgency: medium Maintainer: Debian OpenStack Changed-By: Thomas Goirand Description: python3-pydot-ng - interface to Graphviz's Dot Closes: 938058 Changes: python-pydot-ng (1.0.0-4) unstable; urgency=medium . [ Daniel Baumann ] * Updating copyright format url. * Updating maintainer field. * Running wrap-and-sort -bast. * Removing gbp.conf, not used anymore or should be specified in the developers dotfiles. * Updating standards version to 4.1.0. . [ Ondřej Nový ] * d/control: Set Vcs-* to salsa.debian.org * d/control: Use team+openst...@tracker.debian.org as maintainer * Use debhelper-compat instead of debian/compat. . [ Thomas Goirand ] * Switch the package to Python 3 (Closes: #938058). Checksums-Sha1:
Bug#936282: marked as done (ceph: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:13:28 + with message-id and subject line Bug#936282: fixed in ceph 14.2.4-1 has caused the Debian Bug report #936282, regarding ceph: 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.) -- 936282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936282 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ceph Version: 12.2.11+dfsg1-2.1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:ceph 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: ceph Source-Version: 14.2.4-1 We believe that the bug you reported is fixed in the latest version of ceph, 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. Bernd Zeimetz (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Nov 2019 14:18:10 +0100 Source: ceph Binary: ceph ceph-base ceph-base-dbgsym ceph-common ceph-common-dbgsym ceph-fuse ceph-fuse-dbgsym ceph-mds ceph-mds-dbgsym ceph-mgr ceph-mgr-dashboard ceph-mgr-dbgsym ceph-mgr-diskprediction-cloud ceph-mgr-diskprediction-local ceph-mgr-rook ceph-mgr-ssh ceph-mon ceph-mon-dbgsym ceph-osd ceph-osd-dbgsym ceph-resource-agents cephfs-shell libcephfs-dev libcephfs-java libcephfs-jni libcephfs-jni-dbgsym libcephfs2 libcephfs2-dbgsym librados-dev librados-dev-dbgsym librados2 librados2-dbgsym libradospp-dev libradosstriper-dev libradosstriper1 libradosstriper1-dbgsym librbd-dev librbd1 librbd1-dbgsym librgw-dev librgw2 librgw2-dbgsym python3-ceph-argparse python3-cephfs python3-cephfs-dbgsym python3-rados python3-rados-dbgsym python3-rbd python3-rbd-dbgsym python3-rgw python3-rgw-dbgsym rados-objclass-dev radosgw radosgw-dbgsym rbd-fuse rbd-fuse-dbgsym rbd-mirror rbd-mirror-dbgsym rbd-nbd rbd-nbd-dbgsym Architecture: source amd64
Bug#945633: marked as done (debian-multimedia: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 20:13:48 + with message-id and subject line Bug#945633: fixed in debian-multimedia 0.7+nmu1 has caused the Debian Bug report #945633, regarding debian-multimedia: 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.) -- 945633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: debian-multimedia Version: 0.7 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: debian-multimedia Source-Version: 0.7+nmu1 We believe that the bug you reported is fixed in the latest version of debian-multimedia, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated debian-multimedia package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Dec 2019 11:40:31 -0500 Source: debian-multimedia Binary: multimedia-all multimedia-ambisonics multimedia-animation multimedia-audio-plugins multimedia-audio-utilities multimedia-broadcasting multimedia-csound multimedia-devel multimedia-djing multimedia-drums multimedia-firewire multimedia-graphics multimedia-guitar multimedia-jack multimedia-ladi multimedia-looping multimedia-midi multimedia-mixing multimedia-musiciantools multimedia-photography multimedia-players multimedia-puredata multimedia-recording multimedia-samplers multimedia-soundsynthesis multimedia-supercollider multimedia-tasks multimedia-video Architecture: source all Version: 0.7+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sandro Tosi Description: multimedia-all - Default selection of tasks for Debian Multimedia multimedia-ambisonics - Packages for working with ambisonics (3D surround sound) multimedia-animation - Packages for creating animations multimedia-audio-plugins - Audio processing plugins, synths and virtual instruments
Bug#934251: marked as done (coinor-dylp: unbuildable in testing due to B-D on texlive-omega)
Your message dated Mon, 23 Dec 2019 20:13:45 + with message-id and subject line Bug#934251: fixed in coinor-dylp 1.10.4-1 has caused the Debian Bug report #934251, regarding coinor-dylp: unbuildable in testing due to B-D on texlive-omega 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.) -- 934251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: coinor-dylp Version: 1.6.0-1.1 Severity: serious src:texlive-base no longer builds binary package texlive-omega, which has been removed from testing (and will be removed from unstable at some point in the future, even if other packages still depend on it). As a result, coinor-dylp is unbuildable in testing (and eventually is going to be in unstable as well). Please fix this by changing the build-dependency in coinor-dylp to texlive-formats-extra instead. --- End Message --- --- Begin Message --- Source: coinor-dylp Source-Version: 1.10.4-1 We believe that the bug you reported is fixed in the latest version of coinor-dylp, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sudip Mukherjee (supplier of updated coinor-dylp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Dec 2019 20:09:38 + Source: coinor-dylp Binary: coinor-libdylp-dev coinor-libdylp-doc coinor-libdylp1 coinor-libdylp1-dbgsym Architecture: source amd64 all Version: 1.10.4-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Description: coinor-libdylp-dev - Linear programming solver using of the dynamic simplex algorithm coinor-libdylp-doc - Linear programming solver using of the dynamic simplex algorithm coinor-libdylp1 - Linear programming solver using the dynamic simplex algorithm Closes: 934251 Changes: coinor-dylp (1.10.4-1) unstable; urgency=medium . * QA upload * Mark maintainer to QA. * Update to upstream 1.10.4 * Remove Uploaders entry. * Update compat level to 12 * Update Standards-Version to 4.4.1 * Drop coinor-libdylp1-dbg package. * Enadle DOT in configuration and drop the patch. * Fix build-depends (Closes: #934251) * Update copyright * Remove build dependency on cdbs. * Rename package to coinor-libdylp1. * Add source to salsa and update Vcs links Checksums-Sha1: 802b11dd7b350530f58b7e18d3ad749d09dcdda3 2067 coinor-dylp_1.10.4-1.dsc 698194a6257fee96f4f0b9485d1e6b212bfaa06a 9063684 coinor-dylp_1.10.4.orig.tar.gz 799772b8a5c915c0c37b49edaec60e95a98df541 9144 coinor-dylp_1.10.4-1.debian.tar.xz d85dda1f028ea1db0592d6e9551e4d76fa6814d6 10580 coinor-dylp_1.10.4-1_amd64.buildinfo 36831fa0436670bf26c7aecbb8e08f1b7a021334 416300 coinor-libdylp-dev_1.10.4-1_amd64.deb 1e318d3bb66fa7b73448083baebcd0cbded6cbf9 16902704 coinor-libdylp-doc_1.10.4-1_all.deb 25132725f97014711de139a95f49d8bb3514485a 380380 coinor-libdylp1-dbgsym_1.10.4-1_amd64.deb a7769514257c9ae7662e35d9c7e33a8aca9bb217 203564 coinor-libdylp1_1.10.4-1_amd64.deb Checksums-Sha256: 057f81988107421f3021d25d55860f78fa3f53928a21825d6814c50d06665bc3 2067 coinor-dylp_1.10.4-1.dsc 185f0b600a418a0c5c8ad076a3c7b045876ec0b4d14bbd9b2e224f79826d935b 9063684 coinor-dylp_1.10.4.orig.tar.gz 5e48241da1cc5bbb671f247bae27282f166cc3f2090a41f6321fda57adba3214 9144 coinor-dylp_1.10.4-1.debian.tar.xz ab2731d68af94a88664be384138c134b36dc345b242245b0a92d2443cfe13f34 10580 coinor-dylp_1.10.4-1_amd64.buildinfo 64fa61b96447f18322428f82a58aa086970cf1954a948c8b2ccb333d7665b68e 416300 coinor-libdylp-dev_1.10.4-1_amd64.deb 4c253a4c447b4bf01f99b84116c4d13c18a09d61077bf28121c4a53c4572b8c9 16902704 coinor-libdylp-doc_1.10.4-1_all.deb d445e3be7c52278e9dc5d6c429df3ae768fc2271c9bb42200c9f9c872a17ea6a 380380 coinor-libdylp1-dbgsym_1.10.4-1_amd64.deb 2973d7a217f3b7dbff3ca0c38edda1a90ac66e9c27a5ebd812904c34f6078831 203564 coinor-libdylp1_1.10.4-1_amd64.deb Files: eee31a10920fa241c58ea7dc883fdf8f 2067 science optional coinor-dylp_1.10.4-1.dsc 0b0590d689eaba0c344f064f83f52c88 9063684 science optional
Bug#936015: marked as done (ceph: CVE-2019-10222)
Your message dated Mon, 23 Dec 2019 20:13:28 + with message-id and subject line Bug#936015: fixed in ceph 14.2.4-1 has caused the Debian Bug report #936015, regarding ceph: CVE-2019-10222 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.) -- 936015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936015 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ceph Version: 12.2.11+dfsg1-2.1 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/ceph/ceph/pull/2996 Hi, The following vulnerability was published for ceph. CVE-2019-10222[0]: unauthenticated clients can crash RGW For the 12.2.x series this is only triggerable if an experimental feature is enabled. Thus I think this does not warrant a DSA but would be potentially nice to have fixed in the next point release. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-10222 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10222 [1] https://github.com/ceph/ceph/pull/2996 [2] https://www.openwall.com/lists/oss-security/2019/08/28/9 Regards, Salvatore --- End Message --- --- Begin Message --- Source: ceph Source-Version: 14.2.4-1 We believe that the bug you reported is fixed in the latest version of ceph, 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. Bernd Zeimetz (supplier of updated ceph package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 18 Nov 2019 14:18:10 +0100 Source: ceph Binary: ceph ceph-base ceph-base-dbgsym ceph-common ceph-common-dbgsym ceph-fuse ceph-fuse-dbgsym ceph-mds ceph-mds-dbgsym ceph-mgr ceph-mgr-dashboard ceph-mgr-dbgsym ceph-mgr-diskprediction-cloud ceph-mgr-diskprediction-local ceph-mgr-rook ceph-mgr-ssh ceph-mon ceph-mon-dbgsym ceph-osd ceph-osd-dbgsym ceph-resource-agents cephfs-shell libcephfs-dev libcephfs-java libcephfs-jni libcephfs-jni-dbgsym libcephfs2 libcephfs2-dbgsym librados-dev librados-dev-dbgsym librados2 librados2-dbgsym libradospp-dev libradosstriper-dev libradosstriper1 libradosstriper1-dbgsym librbd-dev librbd1 librbd1-dbgsym librgw-dev librgw2 librgw2-dbgsym python3-ceph-argparse python3-cephfs python3-cephfs-dbgsym python3-rados python3-rados-dbgsym python3-rbd python3-rbd-dbgsym python3-rgw python3-rgw-dbgsym rados-objclass-dev radosgw radosgw-dbgsym rbd-fuse rbd-fuse-dbgsym rbd-mirror rbd-mirror-dbgsym rbd-nbd rbd-nbd-dbgsym Architecture: source amd64 all Version: 14.2.4-1 Distribution: unstable Urgency: medium Maintainer: Ceph Maintainers Changed-By: Bernd Zeimetz Description: ceph - distributed storage and file system ceph-base - common ceph daemon libraries and management tools ceph-common - common utilities to mount and interact with a ceph storage cluste ceph-fuse - FUSE-based client for the Ceph distributed file system ceph-mds - metadata server for the ceph distributed file system ceph-mgr - manager for the ceph distributed file system ceph-mgr-dashboard - dashboard plugin for ceph-mgr ceph-mgr-diskprediction-cloud - diskprediction-cloud plugin for ceph-mgr ceph-mgr-diskprediction-local - diskprediction-local plugin for ceph-mgr ceph-mgr-rook - rook plugin for ceph-mgr ceph-mgr-ssh - ssh orchestrator plugin for ceph-mgr ceph-mon - monitor server for the ceph storage system ceph-osd - OSD server for the ceph storage system ceph-resource-agents - OCF-compliant resource agents for Ceph cephfs-shell - interactive shell for the Ceph distributed file system libcephfs-dev - Ceph distributed file system client library (development files) libcephfs-java - Java library for the Ceph File System libcephfs-jni - Java Native Interface library for CephFS Java bindings libcephfs2 - Ceph distributed file system client library librados-dev - RADOS distributed object store client library (development files) librados2 - RADOS distributed object store client library
Bug#936924: Moving libsvm to Debian Science team
I have a quick question. Previously the python modules are installed to /usr/share/pyshared/. Should I use /usr/lib/python3/dist-packages instead if I change it to python3? I see this in the policy and this is also what liblinear uses. Just want to double check. Thanks, Chen-Tse On Mon, Dec 23, 2019 at 2:29 AM Andreas Tille wrote: > Hi Chen-Tse, > > On Sun, Dec 22, 2019 at 09:47:44PM -0500, Chen-Tse Tsai wrote: > > I'm working on an update which removes dependency on cdbs and python2. > I'm > > using liblinear package as the reference. I'll send you something for > > review some time this week. > > Thanks a lot. That's really appreciated > > Andreas. > > -- > http://fam-tille.de >
Bug#947212: Bug#947143: RFS: wordpress/5.3.2+dfsg1-0.1 [NMU] [RC] -- weblog manager
Hi Markus, Yes Nils was doing a nmu for me. Unless they are very keen I'll handle the backports. As you said the confusion is on the sponsorship. We were using a Mentors as a way of getting the package from him to me in the standard way. - Craig On Tue, 24 Dec. 2019, 4:27 am Markus Koschany, wrote: > Hello Niels, > > Am 23.12.19 um 15:04 schrieb DebBug: > > > Anyone to chime in? Craig? Markus? > > There is a bit of confusion here, so I try to explain the situation and > how we should proceed. Thank you for filing bug report #947212 to track > the security issues in Wordpress. This will help to answer those > questions raised by Adam. However there was already #946905 that you > could have been used as well. > > You have only recently added me to CC, presumably because I have done > some security uploads in the past for Wordpress. I don't know what you > have discussed with Craig and if he wants to review your work and > sponsor it later. Then you actually don't need to open a sponsorship > request on debian-mentors. > > Sponsorship requests are either of severity normal or important. Here it > would be ok to use important but the severity is merely an indicator and > it doesn't automatically guarantee that a bug is prioritized. Security > related bugs like #947212/#946905 are either of severity important or > grave. > > Version 5.3.2 seems to fix a couple of security vulnerabilities. No CVE > has been assigned yet. This version should be uploaded to unstable. > > If you want to fix Wordpress in Buster and Stretch as well, then you > have to go a different route. The security team is responsible for that. > As previously discussed I recommend to base security updates on upstream > releases for specific Wordpress branches. > > https://wordpress.org/download/releases/ > > Buster should be updated to version 5.0.8 and Stretch to 4.7.16. In both > cases you would base your work on the Wordpress packages in Buster and > Stretch. The changes to the debian files should be minimal, you would > merely rebase existing patches and repack the tarball to make it > compliant with the DFSG. > > In short: > > Version 5.3.2 -> unstable > Did Craig agree with the upload? > If there is simply no response because of the holiday season we could do > a NMU with a delay of 5 to 10 days. I assume you haven't made any major > changes to the package. > > After that: > Version 5.0.8 -> buster-security > Version 4.7.16 -> stretch-security > > You can already prepare the packages, then we contact the security team > and ask for approval. > > Regards, > > Markus > >
Bug#937259: marked as done (pcapy: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 19:00:11 + with message-id and subject line Bug#937259: fixed in pcapy 0.11.4-1 has caused the Debian Bug report #937259, regarding pcapy: 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.) -- 937259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pcapy Version: 0.10.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:pcapy 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: pcapy Source-Version: 0.11.4-1 We believe that the bug you reported is fixed in the latest version of pcapy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 937...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated pcapy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 26 Nov 2019 10:34:20 +0100 Source: pcapy Binary: python3-pcapy python3-pcapy-dbgsym Architecture: source amd64 Version: 0.11.4-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Raphaël Hertzog Description: python3-pcapy - Python interface to the libpcap packet capture library (Python 3) Closes: 895787 937259 Changes: pcapy (0.11.4-1) unstable; urgency=medium . * Team upload. . [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. . [ Ondřej Nový ] * Fixed VCS URL (https) * d/control: Set Vcs-* to salsa.debian.org * d/changelog: Remove trailing whitespaces * Remove debian/pycompat, it's not used by any modern Python helper * Convert git repository from git-dpm to gbp layout * Bump Standards-Version to 4.4.1. * Use debhelper-compat instead of debian/compat. . [ Sophie Brun ] * Update to recommend the Python 3 package . [ Emmanuel Arias ] * new upstream version to 0.11.4 *
Processed: your mail
Processing commands for cont...@bugs.debian.org: > # please stop raising the severity > severity 937808 important Bug #937808 [src:python-hglib] python-hglib: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 937808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947216: yapps2: should this package be removed?
On Sun, Dec 22, 2019 at 06:57:24PM -0500, Sandro Tosi wrote: > Python 2 is end-of-life, and there are no more rdeps for python-yapps2, but > python3-yapps2 seems broken beyond repair: #911753, #911752. > > I believe this is a good enough reason to have this package removed from > debian. > if i dont hear back within a week with a good reason to keep it, i'll file for > its removal. Please don't - keymapper needs it and isn't itself useless, and I successfully ported keymapper to Python 3 despite the bugs in yapps2. The bugs (which I filed) are annoying but not fatal. -- Colin Watson [cjwat...@debian.org]
Bug#946732: marked as done (python-django-braces: autopkgtest failure: No module named 'django_braces')
Your message dated Mon, 23 Dec 2019 18:37:04 + with message-id and subject line Bug#946732: fixed in python-django-braces 1.13.0-2 has caused the Debian Bug report #946732, regarding python-django-braces: autopkgtest failure: No module named 'django_braces' 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.) -- 946732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946732 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-django-braces Version: 1.13.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Dear maintainers, With a recent upload of python-django-braces you added an autopkgtest to your package, great. However, it fails. I copied some of the output at the bottom of this report. The layout of your package doesn't seem to be working with autodep8 out of the box. However, autodep8 recently grew support [1] for modules named differently than the package name suggest. Please follow the documentation. Currently this regression is blocking the migration to testing [2]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://salsa.debian.org/ci-team/autodep8/commit/f05b0babe551ac512a3543758d21ec329ec0e58d [2] https://qa.debian.org/excuses.php?package=python-django-braces https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-braces/3483366/log.gz autopkgtest [15:23:51]: test autodep8-python3: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c "import django_braces; print(django_braces)" ; done autopkgtest [15:23:51]: test autodep8-python3: [--- Testing with python3.7: Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'django_braces' autopkgtest [15:23:52]: test autodep8-python3: ---] signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-django-braces Source-Version: 1.13.0-2 We believe that the bug you reported is fixed in the latest version of python-django-braces, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 946...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Arias (supplier of updated python-django-braces package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 15 Dec 2019 00:29:31 -0300 Source: python-django-braces Architecture: source Version: 1.13.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Emmanuel Arias Closes: 946732 Changes: python-django-braces (1.13.0-2) unstable; urgency=medium . * Team upload * Override module name to import (Closes: #946732) Checksums-Sha1: fb73bd0390cae8461f97f92b86cce47925269297 2378 python-django-braces_1.13.0-2.dsc caec7bc2ca890780364a51ee32102cc4d71ea3da 41743 python-django-braces_1.13.0.orig.tar.gz e4c594906e35b8718136063bddb4967a3e5fb92d 7172 python-django-braces_1.13.0-2.debian.tar.xz 90f77fc79d6eb1004da0ac89b355f90807170ee7 6738 python-django-braces_1.13.0-2_source.buildinfo Checksums-Sha256: 03d1037c76e0d40355c5f248bffb7c01d9bafa72a90fbc96494a9ddf83bdacd8 2378 python-django-braces_1.13.0-2.dsc ba68e98b817c6f01d71d10849f359979617b3fe4cefb7f289adefddced092ddc 41743 python-django-braces_1.13.0.orig.tar.gz bcd6485134908fdba8f4f484cb60846aad8a6dd138ef9ad9b2c13cd88336983c 7172 python-django-braces_1.13.0-2.debian.tar.xz a32f712d45deeb067f05dcd8d480e25c5f3aa44e29f459bfd0e9b48178e8375f 6738 python-django-braces_1.13.0-2_source.buildinfo Files: 1e38ac14c1a0b5633923fa0040918624 2378 python optional python-django-braces_1.13.0-2.dsc a4b5ee19343ea91adf298b3224ba1cbd 41743 python optional python-django-braces_1.13.0.orig.tar.gz 245cc7308f7a40246b74f57756f525e1 7172 python optional python-django-braces_1.13.0-2.debian.tar.xz 5d4b1da18edb5cc747ce9ebab55f0900 6738 python optional
Bug#938515: marked as done (sortedcontainers: Python2 removal in sid/bullseye)
Your message dated Mon, 23 Dec 2019 18:06:02 + with message-id and subject line Bug#938515: fixed in sortedcontainers 2.1.0-2 has caused the Debian Bug report #938515, regarding sortedcontainers: 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.) -- 938515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sortedcontainers Version: 2.1.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:sortedcontainers 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: sortedcontainers Source-Version: 2.1.0-2 We believe that the bug you reported is fixed in the latest version of sortedcontainers, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 938...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sandro Tosi (supplier of updated sortedcontainers package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 23 Dec 2019 12:40:04 -0500 Source: sortedcontainers Architecture: source Version: 2.1.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Sandro Tosi Closes: 938515 Changes: sortedcontainers (2.1.0-2) unstable; urgency=medium . * Team upload. * Drop python2 support; Closes: #938515 Checksums-Sha1: 82c92f6b5cfca16f2ead75f590cfec618b746618 2260 sortedcontainers_2.1.0-2.dsc 30cefc1ccbc2867a4b71f10b14b6fe211e3bae82 3052 sortedcontainers_2.1.0-2.debian.tar.xz 553ef348d764fd298512e562489202987af8d9c5 8946 sortedcontainers_2.1.0-2_source.buildinfo Checksums-Sha256: cd5642a45ae73f72b8c40716aade7f07e9779ed6a6db4019ef14cb5daff54f9d 2260 sortedcontainers_2.1.0-2.dsc 3a0d53f3c6fb3f071cade1f91afa8901a0089cbbb5bd3ee21fa5263a024583fd 3052 sortedcontainers_2.1.0-2.debian.tar.xz af8de2cfcc385acf9a15da960df27ae4ef6d2c6f5eb669e4dd382ae648b4acce 8946
Processed: bug 940199 is forwarded to https://github.com/mate-desktop/pluma/issues/305, tagging 940199
Processing commands for cont...@bugs.debian.org: > forwarded 940199 https://github.com/mate-desktop/pluma/issues/305 Bug #940199 [src:pluma] pluma: Python2 removal in sid/bullseye Bug #945690 [src:pluma] pluma: Python2 removal in sid/bullseye Set Bug forwarded-to-address to 'https://github.com/mate-desktop/pluma/issues/305'. Set Bug forwarded-to-address to 'https://github.com/mate-desktop/pluma/issues/305'. > tags 940199 + upstream Bug #940199 [src:pluma] pluma: Python2 removal in sid/bullseye Bug #945690 [src:pluma] pluma: Python2 removal in sid/bullseye Added tag(s) upstream. Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 940199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940199 945690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#734557: severity of 734557 is serious
Control: fixed -1 0.4.1-2 I can reproduce it in wheezy, but not in jessie or later releases. Andreas
Processed: Re: severity of 734557 is serious
Processing control commands:
> fixed -1 0.4.1-2
Bug #734557 {Done: Sandro Tosi } [python-augeas]
python-augeas: doesn't depend on libpython2.7
Marked as fixed in versions python-augeas/0.4.1-2.
--
734557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 946926 to ftp.debian.org ...
Processing commands for cont...@bugs.debian.org: > reassign 946926 ftp.debian.org Bug #946926 [src:pysparse] pysparse: should this package be removed? Bug reassigned from package 'src:pysparse' to 'ftp.debian.org'. No longer marked as found in versions pysparse/1.1.1-2. Ignoring request to alter fixed versions of bug #946926 to the same values previously set > retitle 946926 RM: pysparse -- RoQA; python2-only; no upstream release in 8+ > years; python3-sparse exists Bug #946926 [ftp.debian.org] pysparse: should this package be removed? Changed Bug title to 'RM: pysparse -- RoQA; python2-only; no upstream release in 8+ years; python3-sparse exists' from 'pysparse: should this package be removed?'. > thanks Stopping processing here. Please contact me if you need assistance. -- 946926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: py2removal RC severity updates - 2019-12-23 17:36:47.955560+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # for more details on this severity bump > # python-sortedcontainers is a module and has 0 external rdeps or not in > testing > severity 938515 serious Bug #938515 [src:sortedcontainers] sortedcontainers: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 938515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#947212: Bug#947143: RFS: wordpress/5.3.2+dfsg1-0.1 [NMU] [RC] -- weblog manager
Hello Niels, Am 23.12.19 um 15:04 schrieb DebBug: > Anyone to chime in? Craig? Markus? There is a bit of confusion here, so I try to explain the situation and how we should proceed. Thank you for filing bug report #947212 to track the security issues in Wordpress. This will help to answer those questions raised by Adam. However there was already #946905 that you could have been used as well. You have only recently added me to CC, presumably because I have done some security uploads in the past for Wordpress. I don't know what you have discussed with Craig and if he wants to review your work and sponsor it later. Then you actually don't need to open a sponsorship request on debian-mentors. Sponsorship requests are either of severity normal or important. Here it would be ok to use important but the severity is merely an indicator and it doesn't automatically guarantee that a bug is prioritized. Security related bugs like #947212/#946905 are either of severity important or grave. Version 5.3.2 seems to fix a couple of security vulnerabilities. No CVE has been assigned yet. This version should be uploaded to unstable. If you want to fix Wordpress in Buster and Stretch as well, then you have to go a different route. The security team is responsible for that. As previously discussed I recommend to base security updates on upstream releases for specific Wordpress branches. https://wordpress.org/download/releases/ Buster should be updated to version 5.0.8 and Stretch to 4.7.16. In both cases you would base your work on the Wordpress packages in Buster and Stretch. The changes to the debian files should be minimal, you would merely rebase existing patches and repack the tarball to make it compliant with the DFSG. In short: Version 5.3.2 -> unstable Did Craig agree with the upload? If there is simply no response because of the holiday season we could do a NMU with a delay of 5 to 10 days. I assume you haven't made any major changes to the package. After that: Version 5.0.8 -> buster-security Version 4.7.16 -> stretch-security You can already prepare the packages, then we contact the security team and ask for approval. Regards, Markus signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#936966: londonlaw: Python2 removal in sid/bullseye
Processing control commands: > severity -1 serious Bug #936966 [src:londonlaw] londonlaw: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' -- 936966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Merge 947212 and 946905
Processing commands for cont...@bugs.debian.org: > forcemerge 947212 946905 Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release available. Unable to merge bugs because: package of #946905 is 'src:wordpress' not 'wordpress' Failed to forcibly merge 947212: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 946905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946905 947212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Severity is grave
Processing commands for cont...@bugs.debian.org: > severity 947212 grave Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release available. Severity set to 'grave' from 'critical' > tags 947212 security upstream Bug #947212 [wordpress] wordpress: 5.3.2 new upstream bug-fixing release available. Added tag(s) upstream and security. > thanks Stopping processing here. Please contact me if you need assistance. -- 947212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947212 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
