Bug#933631: Looks like fixed
On 1/17/20 6:35 PM, Gianfranco Costamagna wrote: > control: reopen -1 > > On Wed, 8 Jan 2020 10:17:23 +0100 Thomas Goirand wrote: >> I'm closing this bug. Feel free to reopen if there's still a problem. >> > > sorry for the late answer! > > https://ci.debian.net/packages/k/kazoo/unstable/amd64/ > > looks like something is missing or not working properly on autopkgtests > environments. > It might be a restriction that sbuild doesn't have, or something different in > your testing and the autopkgtest testing. > > I'm not talking about a "build" issue but an "autopkgtest" issue. (something > related to "debian/tests" directory). > > Trying to launch the test on a pbuilder environment shows the issue, as well > as sbuild. > > Please let me know if something is still not clear, > > Gianfranco Hi, I believe I fixed this with the latest upload. Please check. Cheers, Thomas Goirand (zigo)
Bug#948990: marked as pending in python-testtools
Control: tag -1 pending Hello, Bug #948990 in python-testtools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-testtools/commit/5bec4c60ccf4708ca3eb01f74cc93db5f1977ff7 Removed Py2 tests (Closes: #948990). (this message was generated automatically) -- Greetings https://bugs.debian.org/948990
Bug#933631: kazoo: test failures
Hi, I don't understand why there's still this bug, and it's being set to severity serious: when I build the package locally using sbuild, there's no issue and the package builds fine, at least with version 2.6.1-1. Gianfranco, could you help me understand? Cheers, Thomas Goirand (zigo)
Bug#937617: Debdiff, and NMU with DELAYED/7
Hi,
Here's the proposed NMU debdiff. I'm uploading it to delayed/7 since the
bug has been opened for so long, there's no reverse dependency for the
py2 only package, and the package will be AUTORM in 22 days.
Cheers,
Thomas Goirand (zigo)
diff -u python-boto-2.49.0/debian/changelog python-boto-2.49.0/debian/changelog
--- python-boto-2.49.0/debian/changelog
+++ python-boto-2.49.0/debian/changelog
@@ -1,3 +1,10 @@
+python-boto (2.49.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #937617).
+
+ -- Thomas Goirand Wed, 25 Dec 2019 21:28:06 +0100
+
python-boto (2.49.0-2) unstable; urgency=medium
* Re-enable boto.vendored package (for regions sub-pacakge).
diff -u python-boto-2.49.0/debian/control python-boto-2.49.0/debian/control
--- python-boto-2.49.0/debian/control
+++ python-boto-2.49.0/debian/control
@@ -3,11 +3,8 @@
Priority: optional
Maintainer: Eric Evans
Build-Depends: debhelper-compat (= 12),
- python-all (>= 2.6.6-3),
- python-setuptools,
python3-all (>= 3.2),
python3-setuptools,
- python-six,
python3-six,
dh-python
XS-Testsuite: autopkgtest
@@ -16,34 +13,6 @@
Vcs-Git: https://salsa.debian.org/eevans/python-boto.git
Standards-Version: 4.4.0
-Package: python-boto
-Architecture: all
-Depends: python-requests, ${misc:Depends}, ${python:Depends}, python-six
-Provides: ${python:Provides}
-Description: Python interface to Amazon's Web Services - Python 2.x
- Boto is a Python interface to the infrastructure services available from
- Amazon.
- .
- Boto supports the following services:
- * Elastic Compute Cloud (EC2)
- * Elastic MapReduce
- * CloudFront
- * DynamoDB
- * SimpleDB
- * Relational Database Service (RDS)
- * Identity and Access Management (IAM)
- * Simple Queue Service (SQS)
- * CloudWatch
- * Route53
- * Elastic Load Balancing (ELB)
- * Flexible Payment Service (FPS)
- * Simple Storage Service (S3)
- * Glacier
- * Elastic Block Store (EBS)
- * and many more...
- .
- This package provides the Python 2.x module.
-
Package: python3-boto
Architecture: all
Depends: python3-requests, ${misc:Depends}, ${python3:Depends}, python3-six
reverted:
--- python-boto-2.49.0/debian/gbp.conf
+++ python-boto-2.49.0.orig/debian/gbp.conf
@@ -1,7 +0,0 @@
-[DEFAULT]
-upstream-branch = upstream
-debian-branch = master
-
-[buildpackage]
-pbuilder = True
-pbuilder-options = --source-only-changes
diff -u python-boto-2.49.0/debian/rules python-boto-2.49.0/debian/rules
--- python-boto-2.49.0/debian/rules
+++ python-boto-2.49.0/debian/rules
@@ -1,6 +1,5 @@
#!/usr/bin/make -f
-PYTHONS:=$(shell pyversions -vr)
PYTHON3S:=$(shell py3versions -vr)
clean:
@@ -19,7 +18,7 @@
build-stamp:
dh_testdir
- python setup.py build
+ python3 setup.py build
touch build-stamp
@@ -27,18 +26,6 @@
dh_testdir
dh_installdirs
- # Python 2.x
- set -e ; for pyvers in $(PYTHONS); do \
- python$$pyvers setup.py install --root
$(CURDIR)/debian/python-boto \
- --install-scripts usr/share/doc/python-boto/examples/ \
- --install-layout=deb ; \
- done
-
- for f in `find $(CURDIR)/debian/python-boto -name \*.py`; do \
- sed -e '\,^#!/usr/bin/env python,d' < $$f > $$f.tmp; \
- mv $$f.tmp $$f; \
- done
-
# Python 3.x
set -e ; for pyvers in $(PYTHON3S); do \
python$$pyvers setup.py install --root
$(CURDIR)/debian/python3-boto \
@@ -54,7 +41,6 @@
dh_installchangelogs
dh_compress
dh_fixperms
- dh_python2
dh_python3
dh_gencontrol
dh_installdeb
diff -u python-boto-2.49.0/debian/tests/control
python-boto-2.49.0/debian/tests/control
--- python-boto-2.49.0/debian/tests/control
+++ python-boto-2.49.0/debian/tests/control
@@ -1,3 +1,3 @@
Tests: unit
-Depends: python-boto, python-nose (>= 1.3.0), python-mock (>= 1.0.1),
python-httpretty (>= 0.6.3)
+Depends: python3-boto, python3-nose (>= 1.3.0), python3-mock (>= 1.0.1),
python3-httpretty (>= 0.6.3)
Restrictions: allow-stderr
diff -u python-boto-2.49.0/debian/tests/unit
python-boto-2.49.0/debian/tests/unit
--- python-boto-2.49.0/debian/tests/unit
+++ python-boto-2.49.0/debian/tests/unit
@@ -5,5 +5,5 @@
cd "$ADTTMP"
-for python in $(pyversions -i); do
+for python in $(py3versions -i); do
$python tests/test.py unit > /dev/null
done
Bug#938058: marked as pending in python-pydot-ng
Control: tag -1 pending Hello, Bug #938058 in python-pydot-ng reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pydot-ng/commit/e0fe53a24d165143a2ba741864e4fe1de4489987 Switch the package to Python 3 (Closes: #938058). (this message was generated automatically) -- Greetings https://bugs.debian.org/938058
Bug#946614: marked as pending in keystone
Control: tag -1 pending Hello, Bug #946614 in keystone reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/keystone/commit/12f37be150f85197a083ef656961f301a5bb9dfc * CVE-2019-19687: project members and readers can list any credentials with the /v3/credentials API when enforce_scope is false. Add upstream patch: CVE-2019-19687_Fix_credential_list_for_project_members.patch. (Closes: #946614). (this message was generated automatically) -- Greetings https://bugs.debian.org/946614
Bug#946614: keystone: CVE-2019-19687
On 12/11/19 11:10 PM, Salvatore Bonaccorso wrote: > Source: keystone > Version: 2:16.0.0-4 > Severity: grave > Tags: security upstream > Forwarded: https://bugs.launchpad.net/keystone/+bug/1855080 > > Hi, > > The following vulnerability was published for keystone. > > CVE-2019-19687[0]: > | OpenStack Keystone 15.0.0 and 16.0.0 is affected by Data Leakage in > | the list credentials API. Any user with a role on a project is able to > | list any credentials with the /v3/credentials API when enforce_scope > | is false. Users with a role on a project are able to view any other > | users' credentials, which could (for example) leak sign-on information > | for Time-based One Time Passwords (TOTP). Deployments with > | enforce_scope set to false are affected. (There will be a slight > | performance impact for the list credentials API once this issue is > | fixed.) > > > 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-19687 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19687 > [1] https://bugs.launchpad.net/keystone/+bug/1855080 > > Regards, > Salvatore Hi Salvatore, As ugly as it may look like for somebody that doesn't know about what the "credentials" thing is for Keystone, the Keystone "credentials" API is *not* the main auth API part of Keystone/OpenStack. Anyone using the OpenStack API doesn't need this, and it may not even be activated by default on some deployments (one need to create special credentials keys in the /etc/keystone/credential-keys for the "openstack ec2 credential create" command to work). This API is "only" used when using the EC2 API plugin for Nova, which isn't packaged in Debian (and which I don't want to work on, as I don't think that's necessary), and if using the S3 API for Swift (this one is more commonly used and IMO more useful...). I'm writing this for anyone looking at the BTS and not knowing what this all is about. That being said, I'm applying upstream fix right away now. Cheers, Thomas Goirand (zigo)
Bug#946238: marked as pending in horizon
Control: tag -1 pending Hello, Bug #946238 in horizon reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/horizon/commit/c62c238be3757baf7f749c944f141d04eafb432c * Do not install files in debian/local_settings.d/* as CONFFILE, as by definition, these files are to be modified by the Debian packaging. Also, do the copy only a single time for the life of the package (ie: until the package is purged) so that users can continue to tweak the way they want including removing files (Closes: #946238). (this message was generated automatically) -- Greetings https://bugs.debian.org/946238
Bug#927137: src:tumgreyspf: Please port to python3 or remove
On 12/4/19 10:30 PM, Moritz Mühlenhoff wrote: > On Sat, Aug 24, 2019 at 02:07:26AM -0400, Scott Kitterman wrote: >> On Mon, 15 Apr 2019 09:01:29 -0400 Scott Kitterman >> wrote: >>> Package: src:tumgreyspf >>> Version: 1.36-4.1 >>> Severity: important >>> >>> Python2.7 will go out of upstream security support during the Bullseye >>> development cycle. It is not safe to assume it will be included in the >>> next release, so if you want to be sure tumgreyspf can stay in Debian, >> please >>> port it to python3. >>> >>> Alternately, it's close to 8 years without a new release and there are >>> certainly alternatives for SPF checking and greylisting. Removal might be >> in >>> order. >>> >>> Personally, I want to remove some packages I maintain, particularly python- >>> ipaddr, which tumgreyspf depends on (indirectly via python-spf - which I >> will >>> change to python3 only) during the Bullseye cycle, regardless of what >>> happens to python2.7, so please update (python3 includes the ipaddress >> module, >>> which was developed from ipaddr, in the standard library). >> >> Bumping to serious since python2 removals are going on in earnest and this >> will need to be ported or removed soon. > > Thomas, > tumgreyspf seems dead upstream, the last commit on Github is from April 2015, > should we remove it from the archive? > > Cheers, > Moritz Hi, This is a small codebase, which I am able to maintain by myself. I started the porting to Python 3 already locally. In the mean time, it's very much OK to remove the package from testing (which will be done with autoremove anyway). I'll get in touch with upstream to see if I can take over the maintenance of the code and become upstream. Cheers, Thomas Goirand (zigo)
Bug#945262: marked as pending in python-misaka
Control: tag -1 pending Hello, Bug #945262 in python-misaka reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-misaka/commit/1966f882417bece453171a4da2b4efa41b4b023e Remove the Python2 autopkg test. (Closes: #945262). (this message was generated automatically) -- Greetings https://bugs.debian.org/945262
Bug#944705: Wrong patch for mako?
Hi Steve, Thanks for this, however, the patch you've provided for this bug is for Alembic, not for Mako. Do you have a patch available for Mako? Has a bug correctly been filled for Alembic? Cheers, Thomas Goirand (zigo)
Bug#944160: marked as pending in python-pulp
Control: tag -1 pending Hello, Bug #944160 in python-pulp reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pulp/commit/b41ad4d380319ed967615f61c1fdf9aac8ff519d Fix time.clock import for python3.8 (Closes: #944160). (this message was generated automatically) -- Greetings https://bugs.debian.org/944160
Bug#942688: NMU for elixir-lang
On 11/4/19 12:11 PM, Santiago Vila wrote: > On Mon, Nov 04, 2019 at 11:40:08AM +0100, Thomas Goirand wrote: >> Hi Evgeny, >> >> As elixir-lang is going to be AUTORM if nobody takes care of it, I >> already added a bit of code in debian/rules to make it retry unit tests >> if they fail. It will retry 3 times, meaning that if it used to fail 10% >> of the time, making it retry 3 times makes the unit tests fail 0.01% of >> the times, which is IMO acceptable. The recent failures on some arch >> shows that my debian/rules hack works well! :) > > Please don't do that sort of thing. It makes things gratuitously painful > for people like me doing QA. > > Either a unit test is to be trusted or it's not (by "trusted" I mean > here that a failure in the test means the package is unsuitable for > release). > > If the test is trusted but it fails, accept that it fails and do not > let the package to propagate to testing. > > If it's not trusted, there is no point in making it to fail with any > probability. Not 10%, and not 0.01%. Just disable the test. > > Thanks. I don't agree with this view. Yes, this makes your work harder. But running tests improve the quality of the package. Removing them is in no way an improvement. Thomas Goirand (zigo)
Bug#942688: NMU for elixir-lang
Hi Evgeny,
As elixir-lang is going to be AUTORM if nobody takes care of it, I
already added a bit of code in debian/rules to make it retry unit tests
if they fail. It will retry 3 times, meaning that if it used to fail 10%
of the time, making it retry 3 times makes the unit tests fail 0.01% of
the times, which is IMO acceptable. The recent failures on some arch
shows that my debian/rules hack works well! :)
Now, I noticed that the build reliably fails on arm64 and mips64el:
https://buildd.debian.org/status/fetch.php?pkg=elixir-lang&arch=arm64&ver=1.9.1.dfsg-1.2&stamp=1572476904&raw=0
https://buildd.debian.org/status/fetch.php?pkg=elixir-lang&arch=mips64el&ver=1.9.1.dfsg-1.2&stamp=1572491696&raw=0
Therefore, I've removed the failing test.
Attached to this email, you'll find the debdiff for the change between
version 1.9.1.dfsg-1.1 and 1.9.1.dfsg-1.3.
Please let me know if you want to revert these upload. I can always do
that. The reason why I've done a non-delayed NMU is because otherwise,
it would be AUTORM, but of course, everything can be reverted if you
feel like it. Anyways, I'm always available for anything related to
these uploads, so just let me know.
Cheers,
Thomas Goirand (zigo)
diff -Nru elixir-lang-1.9.1.dfsg/debian/changelog
elixir-lang-1.9.1.dfsg/debian/changelog
--- elixir-lang-1.9.1.dfsg/debian/changelog 2019-10-13 08:39:24.0
+0200
+++ elixir-lang-1.9.1.dfsg/debian/changelog 2019-11-04 11:27:07.0
+0100
@@ -1,3 +1,18 @@
+elixir-lang (1.9.1.dfsg-1.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add remove-test-executes-rpc-instructions.patch, as this test reliably
+ fails on arm64 and mips64el.
+
+ -- Thomas Goirand Mon, 04 Nov 2019 11:27:07 +0100
+
+elixir-lang (1.9.1.dfsg-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Re-attempt unit testing (up to 3 times) if failed (Closes: #942688).
+
+ -- Thomas Goirand Wed, 30 Oct 2019 12:23:33 +0100
+
elixir-lang (1.9.1.dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru
elixir-lang-1.9.1.dfsg/debian/patches/remove-test-executes-rpc-instructions.patch
elixir-lang-1.9.1.dfsg/debian/patches/remove-test-executes-rpc-instructions.patch
---
elixir-lang-1.9.1.dfsg/debian/patches/remove-test-executes-rpc-instructions.patch
1970-01-01 01:00:00.0 +0100
+++
elixir-lang-1.9.1.dfsg/debian/patches/remove-test-executes-rpc-instructions.patch
2019-11-04 11:26:42.0 +0100
@@ -0,0 +1,36 @@
+Description: Removes test "executes rpc instructions"
+ This test fails reliably on arm64 and misp64el.
+Author: Thomas Goirand
+Forwarded: no
+Last-Update: 2019-11-04
+
+--- elixir-lang-1.9.1.dfsg.orig/lib/mix/test/mix/tasks/release_test.exs
elixir-lang-1.9.1.dfsg/lib/mix/test/mix/tasks/release_test.exs
+@@ -268,27 +268,6 @@ defmodule Mix.Tasks.ReleaseTest do
+ end)
+ end
+
+- @tag :epmd
+- test "executes rpc instructions" do
+-in_fixture("release_test", fn ->
+- config = [releases: [permanent1: [include_erts: false]]]
+-
+- Mix.Project.in_project(:release_test, ".", config, fn _ ->
+-root = Path.absname("_build/dev/rel/permanent1")
+-Mix.Task.run("release")
+-script = Path.join(root, "bin/permanent1")
+-
+-open_port(script, ['start'])
+-wait_until_decoded(Path.join(root, "RELEASE_BOOTED"))
+-assert System.cmd(script, ["rpc", "ReleaseTest.hello_world"]) ==
{"hello world\n", 0}
+-assert System.cmd(script, ["stop"]) == {"", 0}
+-
+-assert {pid, 0} = System.cmd(script, ["pid"])
+-assert pid != "\n"
+- end)
+-end)
+- end
+-
+ test "runs eval and version commands" do
+ # In some Windows setups (mostly with Docker), `System.cmd/3` fails
because
+ # the path to the command/executable and one or more arguments contain
spaces.
diff -Nru elixir-lang-1.9.1.dfsg/debian/patches/series
elixir-lang-1.9.1.dfsg/debian/patches/series
--- elixir-lang-1.9.1.dfsg/debian/patches/series2019-10-13
08:39:24.0 +0200
+++ elixir-lang-1.9.1.dfsg/debian/patches/series2019-11-04
11:25:44.0 +0100
@@ -1,3 +1,4 @@
remove-utf8-warning.patch
remove_rebar3_related_tests.patch
use_rebar_instead_of_rebar3_in_tests.patch
+remove-test-executes-rpc-instructions.patch
diff -Nru elixir-lang-1.9.1.dfsg/debian/rules
elixir-lang-1.9.1.dfsg/debian/rules
--- elixir-lang-1.9.1.dfsg/debian/rules 2019-10-13 08:39:24.0 +0200
+++ elixir-lang-1.9.1.dfsg/debian/rules 2019-10-30 22:22:46.0 +0100
@@ -8,8 +8,18 @@
%:
dh $@
+
override_dh_auto_test: .home
- rc=0; HOME=$(CURDIR)/.home dh_auto_test || rc=$$?; epmd -kill; exit $$rc
+ CNT=3 ; rc=1 ; while [ $$CNT != 0 ] && [ $$rc != 0 ] ; d
Bug#943990: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #943990 in openvswitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/a2c40a6184f3421ec288b283e1acf109129e1337 Fix moving ovs-vswitchd (Closes: #943990). (this message was generated automatically) -- Greetings https://bugs.debian.org/943990
Bug#943767: yotta: FTBFS
x27;truncate'
>> begin captured logging <<
components: Level 2: Component: /tmp/tmpxtbejlya spaces in path
installed_linked=False
target: DEBUG: satisfy target: bar,
access: DEBUG: check path /tmp/tmpxtbejlya spaces in path/yotta_targets/bar for
bar
- >> end captured logging << -
==
ERROR: test_matches (yotta.test.test_versions.VersionTestCase)
--
Traceback (most recent call last):
File "/<>/yotta/test/test_versions.py", line 71, in test_matches
v in spec,
File "/<>/yotta/lib/version.py", line 183, in __contains__
return self.match(version)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 630, in
match
return self.clause.match(version)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 745, in
match
return all(clause.match(version) for clause in self.clauses)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 745, in
return all(clause.match(version) for clause in self.clauses)
File "/usr/lib/python3/dist-packages/semantic_version/base.py", line 892, in
match
version = version.truncate('prerelease')
AttributeError: 'Version' object has no attribute 'truncate'
--
Ran 41 tests in 2.022s
FAILED (SKIP=2, errors=4)
make[1]: *** [debian/rules:38: override_dh_auto_test] Error 1
Please fix your package.
Cheers,
Thomas Goirand (zigo)
Bug#926997: Fixed
I believe this bug is not relevant anymore to the version in Sid (though I'm not sure when this FTBFS issue was fixed). Thomas
Bug#943476: Package was fixed, but uploaded with binaries
Hi, It appears it was fixed indeed, but uploaded with binaries, and therefore didn't migrate to testing. I'm re-uploading to fix that. Cheers, Thomas Goirand (zigo)
Bug#933781: marked as pending in django-pagination
Control: tag -1 pending Hello, Bug #933781 in django-pagination reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/django-pagination/commit/fb0b8261493ca6b1268502b9325404d77de32d0c * Team upload. * Add python3-fix-for-except.patch (Closes: #933781). (this message was generated automatically) -- Greetings https://bugs.debian.org/933781
Bug#943476: django-reversion: Python2 removal in sid/bullseye + Django 2.2 support
Source: django-reversion Version: 3.0.3-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Dear maintainer, 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. Moreover, this package needs to add support for Django 2.2 which is is SID since 3 days after Buster is released. Your package will be AUTORM if you don't do anything to fix the situation. Cheers, Thomas Goirand (zigo) -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#936418: Please add support for Django 2.2
Hi, Your package also needs to support Django 2.2, which is in Sid, and which your package is blocking the transition. At this point, as there's only 4 Django packages remaining, your package may be left behind and AUTORM from Testing. Cheers, Thomas Goirand (zigo)
Bug#943474: Doesn't build with Django 2.2
Source: django-modeltranslation Version: 0.12.2-1 Severity: serious Hi, Your package doesn't build with Django 2.2, which is blocking is transition to Testing. Please fix this ASAP. This also means fixing Py2 removal, as there's no Py2 support in Django 2.2. Cheers, Thomas Goirand (zigo)
Bug#936219: diff of the NMU for this bug
Hi,
Since you haven't replied to the previous mail, I've uploaded this
without delay, fixing the RC bug on blockdiag.
Cheers,
Thomas Goirand (zigo)
diff -Nru blockdiag-1.5.3+dfsg/debian/changelog
blockdiag-1.5.3+dfsg/debian/changelog
--- blockdiag-1.5.3+dfsg/debian/changelog 2018-07-16 18:07:06.0
+0200
+++ blockdiag-1.5.3+dfsg/debian/changelog 2019-10-24 09:23:00.0
+0200
@@ -1,3 +1,12 @@
+blockdiag (1.5.3+dfsg-5.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #936219).
+ * Switched to debhelper-compat (= 11), as the package was using
+debian/compat with version 7, and debhelper >= 8.
+
+ -- Thomas Goirand Thu, 24 Oct 2019 09:23:00 +0200
+
blockdiag (1.5.3+dfsg-5.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru blockdiag-1.5.3+dfsg/debian/compat blockdiag-1.5.3+dfsg/debian/compat
--- blockdiag-1.5.3+dfsg/debian/compat 2017-05-29 05:24:55.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/compat 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-7
diff -Nru blockdiag-1.5.3+dfsg/debian/control
blockdiag-1.5.3+dfsg/debian/control
--- blockdiag-1.5.3+dfsg/debian/control 2017-05-26 15:06:27.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/control 2019-10-24 09:23:00.0 +0200
@@ -2,23 +2,12 @@
Section: python
Priority: optional
Maintainer: Kouhei Maeda
-Build-Depends: debhelper (>= 8.0.0),
+Build-Depends: debhelper-compat (= 11),
dh-python,
- python-all,
- python-setuptools,
- python-configparser,
- python-unittest2,
- pep8 (>= 1.3),
- python-nose,
- python-zc.buildout,
- python-funcparserlib (>= 0.3.4),
- python-docutils,
- python-pil,
- python-webcolors,
- python-reportlab,
- python-mock,
- python-wand,
- python-pep8,
+ libmagickcore-6.q16-3-extra,
+ python3-unittest2,
+ python3-docutils,
+ python3-pep8,
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -30,26 +19,11 @@
python3-reportlab,
python3-mock,
python3-wand,
- libmagickcore-6.q16-3-extra,
+ python3-zc.buildout,
fonts-vlgothic | fonts-japanese-gothic
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://blockdiag.com/
-Package: python-blockdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-funcparserlib (>= 0.3.4),
- python-pil,
- python-docutils,
- python-reportlab,
- python-webcolors
-Description: generate block-diagram image file from spec-text file
- Generate block-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. It is able to embed to sphinx with
- using python-sphinxcontrib-blockdiag.
-
Package: python3-blockdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages
blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages
--- blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages 2011-10-08
08:20:33.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/python-blockdiag.manpages 1970-01-01
01:00:00.0 +0100
@@ -1 +0,0 @@
-blockdiag.1
diff -Nru blockdiag-1.5.3+dfsg/debian/rules blockdiag-1.5.3+dfsg/debian/rules
--- blockdiag-1.5.3+dfsg/debian/rules 2017-06-04 05:04:56.0 +0200
+++ blockdiag-1.5.3+dfsg/debian/rules 2019-10-24 09:23:00.0 +0200
@@ -8,7 +8,7 @@
export PYBUILD_AFTER_TEST=rm -rf {build_dir}/circle.*
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3 --shebang=/usr/bin/python3
Bug#937926: Lowered severity
Hi, I've re-introduced python-pbr, so the severity of this bug can be lowered back to just 'important'. We'll revisit Py2 removal from this package once these are fixed: http://sandrotosi.me/debian/py2removal/python-mock_1.svg Cheers, Thomas Goirand (zigo)
Bug#942613: Please go ahead?
Hi, Thanks for addressing this bug, Could you go ahead and upload the fixed version of rabbit to close this bug? This is the only remaining bit needed to fix #936219 and a long chain of (build-)dependency. Cheers, Thomas Goirand (zigo)
Bug#936219: Uploaded the fixed
Hi, I very much know the maintainer of the blockdiag suite isn't very fast to react to issues, and sometimes completely unresponsive (I've seen this in the past), and also these packages haven't been updated since oldstable. So I've uploaded fixes to the DELAYED/2 queue for: actdiag nwdiag seqdiag sphinxcontrib-actdiag sphinxcontrib-blockdiag sphinxcontrib-nwdiag sphinxcontrib-seqdiag (debdiffs attached to the matching bugs). I've also filed a bug for rabbit since it looks like Matthias forgot to file a bug for that package. Let's give rabbit maintainers a bit of time to see if they fix it. Once they are done, then we can safely remove Python 2 support from blockdiag. If nothing happens on the rabbit maintainer side (hopefully, they will react soon...), then maybe we can NMU the fix there too. IMO, that's a much better approach than just stalled things, or reverting the work done on python-zc.buildout. Cheers, Thomas Goirand (zigo)
Bug#936106: Debdiff for Python 2 removal from actdiag
Hi,
Please find attached to this message the debdiff for the removal of
Python 2 support from actdiag. I've uploaded it to DELAYED/2. Let me
know if you want me to cancel this upload, or sponsor another version.
Cheers,
Thomas Goirand (zigo)
diff -Nru actdiag-0.5.4+dfsg/debian/changelog
actdiag-0.5.4+dfsg/debian/changelog
--- actdiag-0.5.4+dfsg/debian/changelog 2016-10-11 06:38:49.0 +0200
+++ actdiag-0.5.4+dfsg/debian/changelog 2019-10-19 02:54:15.0 +0200
@@ -1,3 +1,11 @@
+actdiag (0.5.4+dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add missing dh-python build-depends.
+ * Removed Python 2 support (Closes: #936106).
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:54:15 +0200
+
actdiag (0.5.4+dfsg-1) unstable; urgency=medium
* New upstream release
diff -Nru actdiag-0.5.4+dfsg/debian/control actdiag-0.5.4+dfsg/debian/control
--- actdiag-0.5.4+dfsg/debian/control 2016-10-11 06:38:47.0 +0200
+++ actdiag-0.5.4+dfsg/debian/control 2019-10-19 02:54:15.0 +0200
@@ -3,12 +3,7 @@
Priority: optional
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 8.0.0),
- python-all,
- python-setuptools,
- python-unittest2,
- python-pep8 (>= 1.3),
- python-nose,
- python-blockdiag (>= 1.5.0),
+ dh-python,
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -16,25 +11,13 @@
python3-blockdiag (>= 1.5.0),
fonts-vlgothic | fonts-japanese-gothic
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://blockdiag.com/
-Package: python-actdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0)
-Description: generate activity-diagram image file from spec-text file
- Generate activity-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. It is able to embed to sphinx with
- using python-sphinxcontrib-actdiag.
-
Package: python3-actdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
python3-blockdiag (>= 1.5.0)
-Description: generate activity-diagram image file from spec-text file (Python3)
- For Python3.
+Description: generate activity-diagram image file from spec-text file
Generate activity-diagram from dot like text with multilingualization for
node-label. But this supports utf-8 only. It is able to embed to sphinx with
using python3-sphinxcontrib-actdiag.
diff -Nru actdiag-0.5.4+dfsg/debian/pydist-overrides
actdiag-0.5.4+dfsg/debian/pydist-overrides
--- actdiag-0.5.4+dfsg/debian/pydist-overrides 2011-06-05 18:38:58.0
+0200
+++ actdiag-0.5.4+dfsg/debian/pydist-overrides 1970-01-01 01:00:00.0
+0100
@@ -1,3 +0,0 @@
-PIL python-imaging
-funcparserlib python-funcparserlib
-blockdiag python-blockdiag
diff -Nru actdiag-0.5.4+dfsg/debian/python-actdiag.manpages
actdiag-0.5.4+dfsg/debian/python-actdiag.manpages
--- actdiag-0.5.4+dfsg/debian/python-actdiag.manpages 2011-11-03
17:22:00.0 +0100
+++ actdiag-0.5.4+dfsg/debian/python-actdiag.manpages 1970-01-01
01:00:00.0 +0100
@@ -1 +0,0 @@
-actdiag.1
diff -Nru actdiag-0.5.4+dfsg/debian/rules actdiag-0.5.4+dfsg/debian/rules
--- actdiag-0.5.4+dfsg/debian/rules 2014-09-01 00:37:08.0 +0200
+++ actdiag-0.5.4+dfsg/debian/rules 2019-10-19 02:54:15.0 +0200
@@ -7,7 +7,7 @@
export PYBUILD_NAME=actdiag
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
Bug#942613: rabbit: Python2 removal in sid/bullseye
Package: src:rabbit Version: 3.0.0-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Dear maintainer, It looks like no bug has been sent against your package, probably Matthias Klose forgot this package. So I'm doing it. Also, since Python 2 support has been removed from a dependency of blockdiag (which your package depends on), I'm afraid this bug has to be of severity: serious (as we'll remove Python 2 support from blockdiag ASAP, maybe after you fix rabbit). Cheers, Thomas Goirand (zigo) Below the standard text for Py2 removal bugs: 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:actdiag 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.
Bug#937172: Debdiff for nwdiag python 2 removal
Hi,
Please find attached the debdiff for fixing this bug. I'm uploading it
to the DELAYED/2 queue. Let me know if you want me to cancel this upload
and/or sponsor something else.
Cheers,
Thomas Goirand (zigo)
diff -Nru nwdiag-1.0.4+dfsg/debian/changelog nwdiag-1.0.4+dfsg/debian/changelog
--- nwdiag-1.0.4+dfsg/debian/changelog 2016-10-11 06:47:37.0 +0200
+++ nwdiag-1.0.4+dfsg/debian/changelog 2019-10-19 02:40:47.0 +0200
@@ -1,3 +1,10 @@
+nwdiag (1.0.4+dfsg-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove Python 2 support (Closes: #937172).
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:40:47 +0200
+
nwdiag (1.0.4+dfsg-1) unstable; urgency=medium
* New upstream release
diff -Nru nwdiag-1.0.4+dfsg/debian/control nwdiag-1.0.4+dfsg/debian/control
--- nwdiag-1.0.4+dfsg/debian/control2016-10-11 06:47:26.0 +0200
+++ nwdiag-1.0.4+dfsg/debian/control2019-10-19 02:37:12.0 +0200
@@ -4,36 +4,17 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 8.0.0),
dh-python,
- python-all,
- python-setuptools,
- python-nose,
- python-pep8 (>= 1.3),
- python-unittest2,
- python-reportlab,
- python-blockdiag (>= 1.5.0),
python3-all,
python3-setuptools,
python3-nose,
python3-pep8 (>= 1.3),
python3-reportlab,
+ python3-unittest2,
python3-blockdiag (>= 1.5.0),
fonts-vlgothic | fonts-japanese-gothic
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://blockdiag.com/
-Package: python-nwdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-docutils,
- python-reportlab
-Description: generate network-diagram image file from spec-text file
- Generate network-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. And get some examples and generated
- images.
-
Package: python3-nwdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru nwdiag-1.0.4+dfsg/debian/pydist-overrides
nwdiag-1.0.4+dfsg/debian/pydist-overrides
--- nwdiag-1.0.4+dfsg/debian/pydist-overrides 2011-06-12 16:40:31.0
+0200
+++ nwdiag-1.0.4+dfsg/debian/pydist-overrides 1970-01-01 01:00:00.0
+0100
@@ -1,3 +0,0 @@
-PIL python-imaging
-funcparserlib python-funcparserlib
-blockdiag python-blockdiag
diff -Nru nwdiag-1.0.4+dfsg/debian/python-nwdiag.manpages
nwdiag-1.0.4+dfsg/debian/python-nwdiag.manpages
--- nwdiag-1.0.4+dfsg/debian/python-nwdiag.manpages 2013-06-08
17:08:12.0 +0200
+++ nwdiag-1.0.4+dfsg/debian/python-nwdiag.manpages 1970-01-01
01:00:00.0 +0100
@@ -1,3 +0,0 @@
-nwdiag.1
-rackdiag.1
-packetdiag.1
diff -Nru nwdiag-1.0.4+dfsg/debian/rules nwdiag-1.0.4+dfsg/debian/rules
--- nwdiag-1.0.4+dfsg/debian/rules 2015-10-28 01:52:25.0 +0100
+++ nwdiag-1.0.4+dfsg/debian/rules 2019-10-19 02:37:43.0 +0200
@@ -7,7 +7,7 @@
export PYBUILD_BEFORE_BUILD=cp -a $(CURDIR)/src/nwdiag.egg-info {build_dir}
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
diff -Nru nwdiag-1.0.4+dfsg/debian/test-runner
nwdiag-1.0.4+dfsg/debian/test-runner
--- nwdiag-1.0.4+dfsg/debian/test-runner2013-06-08 17:06:55.0
+0200
+++ nwdiag-1.0.4+dfsg/debian/test-runner2019-10-19 02:39:29.0
+0200
@@ -1,11 +1,9 @@
-#!/usr/bin/python
+#!/usr/bin/python3
import os.path
import sys
sys.path[0:0] = [
os.path.abspath('src'),
-'/usr/lib/python2.7/dist-packages',
-'/usr/lib/pymodules/python2.7',
-'/usr/lib/python2.7/dist-packages/PIL',
+'/usr/lib/python3/dist-packages',
]
Bug#938466: Debdiff for fixing python2 removal from seqdiag
Hi,
Please find attached a debdiff to fix #938466 which I'm uploading to
DELAYED/2 queue. Please let me know if you need the sponsoring of the
upload of another debian release, or if I should cancel my upload.
Cheers,
Thomas Goirand (zigo)
diff -Nru seqdiag-0.9.5+dfsg/debian/changelog
seqdiag-0.9.5+dfsg/debian/changelog
--- seqdiag-0.9.5+dfsg/debian/changelog 2018-07-16 10:57:18.0 +0200
+++ seqdiag-0.9.5+dfsg/debian/changelog 2019-10-19 02:28:25.0 +0200
@@ -1,3 +1,10 @@
+seqdiag (0.9.5+dfsg-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #938466).
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:28:25 +0200
+
seqdiag (0.9.5+dfsg-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru seqdiag-0.9.5+dfsg/debian/control seqdiag-0.9.5+dfsg/debian/control
--- seqdiag-0.9.5+dfsg/debian/control 2016-10-11 06:33:57.0 +0200
+++ seqdiag-0.9.5+dfsg/debian/control 2019-10-19 02:28:15.0 +0200
@@ -4,13 +4,7 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 8.0.0),
dh-python,
- python-all,
- python-setuptools,
pep8 (>= 1.3),
- python-nose,
- python-unittest2,
- python-reportlab,
- python-blockdiag (>= 1.5.0),
python3-all,
python3-setuptools,
python3-pep8 (>= 1.3),
@@ -19,25 +13,13 @@
python3-blockdiag (>= 1.5.0),
fonts-vlgothic | fonts-japanese-gothic
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://blockdiag.com/
-Package: python-seqdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0)
-Description: seqdiag generate sequence-diagram image file from spec-text file
- Generate sequence-diagram from dot like text with multilingualization for
- node-label. But this supports utf-8 only. And get some examples and generated
- images.
-
Package: python3-seqdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
python3-blockdiag (>= 1.5.0)
-Description: seqdiag generate sequence-diagram image file for Python3
- For Python3.
+Description: seqdiag generate sequence-diagram image file from spec-text file
Generate sequence-diagram from dot like text with multilingualization for
node-label. But this supports utf-8 only. And get some examples and generated
images.
diff -Nru seqdiag-0.9.5+dfsg/debian/rules seqdiag-0.9.5+dfsg/debian/rules
--- seqdiag-0.9.5+dfsg/debian/rules 2014-09-01 04:31:04.0 +0200
+++ seqdiag-0.9.5+dfsg/debian/rules 2019-10-19 02:26:21.0 +0200
@@ -7,7 +7,7 @@
export PYBUILD_NAME=seqdiag
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
Bug#938535: Debdiff for sphinxcontrib-nwdiag python 2 removal
Hi,
I've uploaded the fix to DELAYED/2 as this bug is now RC. Let me know if
you want me to sponsor a better fix (or any subsequent debian release).
Cheers,
Thomas Goirand (zigo)
diff -Nru sphinxcontrib-nwdiag-0.9.5/debian/changelog
sphinxcontrib-nwdiag-0.9.5/debian/changelog
--- sphinxcontrib-nwdiag-0.9.5/debian/changelog 2016-11-01 01:12:35.0
+0100
+++ sphinxcontrib-nwdiag-0.9.5/debian/changelog 2019-10-19 02:18:16.0
+0200
@@ -1,3 +1,11 @@
+sphinxcontrib-nwdiag (0.9.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Remove Python 2 support (Closes: #938535).
+ * Add dh-python as build-depends.
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:18:16 +0200
+
sphinxcontrib-nwdiag (0.9.5-1) unstable; urgency=medium
* New upstream release
diff -Nru sphinxcontrib-nwdiag-0.9.5/debian/control
sphinxcontrib-nwdiag-0.9.5/debian/control
--- sphinxcontrib-nwdiag-0.9.5/debian/control 2016-11-01 01:12:32.0
+0100
+++ sphinxcontrib-nwdiag-0.9.5/debian/control 2019-10-19 02:18:14.0
+0200
@@ -3,12 +3,7 @@
Priority: optional
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 9.0.0),
- python-all,
- python-setuptools,
- python-sphinx (>= 0.6),
- python-mock,
- python-blockdiag (>= 1.5.0),
- python-nwdiag (>= 1.0.3),
+ dh-python,
python3-all,
python3-setuptools,
python3-sphinx (>= 0.6),
@@ -16,21 +11,8 @@
python3-blockdiag (>= 1.5.0),
python3-nwdiag (>= 1.0.3),
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://github.com/blockdiag/sphinxcontrib-nwdiag
-Package: python-sphinxcontrib.nwdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-nwdiag (>= 1.0.3),
- python-sphinx (>= 0.6)
-Description: Sphinx "nwdiag" extension
- This package contains the nwdiag Sphinx extension. This extension enable
- you to insert network diagrams in your Sphinx document. This renders block
- diagrams by using python-nwdiag.
-
Package: python3-sphinxcontrib.nwdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru sphinxcontrib-nwdiag-0.9.5/debian/pydist-overrides
sphinxcontrib-nwdiag-0.9.5/debian/pydist-overrides
--- sphinxcontrib-nwdiag-0.9.5/debian/pydist-overrides 2011-06-12
17:02:30.0 +0200
+++ sphinxcontrib-nwdiag-0.9.5/debian/pydist-overrides 1970-01-01
01:00:00.0 +0100
@@ -1,3 +0,0 @@
-PIL python-imaging
-nwdiag python-nwdiag
-sphinx python-sphinx
diff -Nru sphinxcontrib-nwdiag-0.9.5/debian/rules
sphinxcontrib-nwdiag-0.9.5/debian/rules
--- sphinxcontrib-nwdiag-0.9.5/debian/rules 2014-11-22 18:41:59.0
+0100
+++ sphinxcontrib-nwdiag-0.9.5/debian/rules 2019-10-19 02:18:16.0
+0200
@@ -8,12 +8,8 @@
export PYBUILD_DISABLE=test
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
find $(CURDIR)/debian/python3-sphinxcontrib.nwdiag -name tests -a -type
d | xargs rm -rf
-
-override_dh_python2:
- dh_python2
- find $(CURDIR)/debian/python-sphinxcontrib.nwdiag -name tests -a -type
d | xargs rm -rf
Bug#938530: Debdiff for fixing this bug in sphinxcontrib-actdiag
Hi,
I've uploaded the attached debdiff to DELAYED/2. Let me know if you want
to upload another version, which I may sponsor if you need.
Cheers,
Thomas Goirand (zigo)
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/changelog
sphinxcontrib-actdiag-0.8.5/debian/changelog
--- sphinxcontrib-actdiag-0.8.5/debian/changelog2016-11-01
00:58:04.0 +0100
+++ sphinxcontrib-actdiag-0.8.5/debian/changelog2019-10-19
02:05:46.0 +0200
@@ -1,3 +1,10 @@
+sphinxcontrib-actdiag (0.8.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #938530).
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:05:46 +0200
+
sphinxcontrib-actdiag (0.8.5-1) unstable; urgency=medium
* New upstream release
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/control
sphinxcontrib-actdiag-0.8.5/debian/control
--- sphinxcontrib-actdiag-0.8.5/debian/control 2016-11-01 00:58:02.0
+0100
+++ sphinxcontrib-actdiag-0.8.5/debian/control 2019-10-19 02:05:43.0
+0200
@@ -4,12 +4,6 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 9.0.0),
dh-python,
- python-all,
- python-setuptools,
- python-sphinx (>= 0.6),
- python-blockdiag (>= 1.5.0),
- python-actdiag (>= 0.5.3),
- python-mock,
python3-all,
python3-setuptools,
python3-sphinx (>= 0.6),
@@ -17,21 +11,8 @@
python3-actdiag (>= 0.5.3),
python3-mock
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: http://github.com/blockdiag/sphinxcontrib-actdiag
-Package: python-sphinxcontrib.actdiag
-Architecture: all
-Provides: ${python:Provides}
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-actdiag (>= 0.5.3),
- python-sphinx (>= 0.6)
-Description: Sphinx "actdiag" extension
- This package contains the actdiag Sphinx extension. This extension enable you
- to insert activity diagrams in your Sphinx document. This is a sphinx
- extension which render block diagrams by using python-actdiag.
-
Package: python3-sphinxcontrib.actdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru sphinxcontrib-actdiag-0.8.5/debian/rules
sphinxcontrib-actdiag-0.8.5/debian/rules
--- sphinxcontrib-actdiag-0.8.5/debian/rules2014-11-22 18:00:08.0
+0100
+++ sphinxcontrib-actdiag-0.8.5/debian/rules2019-10-19 02:05:46.0
+0200
@@ -8,12 +8,8 @@
export PYBUILD_DISABLE=test
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
find $(CURDIR)/debian/python3-sphinxcontrib.actdiag -name tests -a
-type d | xargs rm -rf
-
-override_dh_python2:
- dh_python2
- find $(CURDIR)/debian/python-sphinxcontrib.actdiag -name tests -a -type
d | xargs rm -rf
Bug#938532: Debdiff for fixing #938532
Hi,
Here's the debdiff for fixing #938532. I've uploaded to DELAYED/2. Let
me know if you want to upload it yourself (and I'm volunteering for
sponsoring if you need).
Cheers,
Thomas Goirand (zigo)
diff -Nru sphinxcontrib-blockdiag-1.5.5/debian/changelog
sphinxcontrib-blockdiag-1.5.5/debian/changelog
--- sphinxcontrib-blockdiag-1.5.5/debian/changelog 2016-11-01
00:36:05.0 +0100
+++ sphinxcontrib-blockdiag-1.5.5/debian/changelog 2019-10-19
02:13:26.0 +0200
@@ -1,3 +1,10 @@
+sphinxcontrib-blockdiag (1.5.5-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #938532).
+
+ -- Thomas Goirand Sat, 19 Oct 2019 02:13:26 +0200
+
sphinxcontrib-blockdiag (1.5.5-1) unstable; urgency=medium
* New upstream release
diff -Nru sphinxcontrib-blockdiag-1.5.5/debian/control
sphinxcontrib-blockdiag-1.5.5/debian/control
--- sphinxcontrib-blockdiag-1.5.5/debian/control2016-11-01
00:35:53.0 +0100
+++ sphinxcontrib-blockdiag-1.5.5/debian/control2019-10-19
02:13:12.0 +0200
@@ -4,31 +4,14 @@
Maintainer: Kouhei Maeda
Build-Depends: debhelper (>= 9.0.0),
dh-python,
- python-all,
- python-setuptools,
- python-sphinx,
- python-mock,
- python-blockdiag (>= 1.5.0),
python3-all,
python3-setuptools,
python3-sphinx,
python3-mock,
python3-blockdiag (>= 1.5.0),
Standards-Version: 3.9.8
-X-Python-Version: 2.7
Homepage: https://github.com/blockdiag/sphinxcontrib-blockdiag
-Package: python-sphinxcontrib.blockdiag
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends},
- python-blockdiag (>= 1.5.0),
- python-sphinx (>= 0.6)
-Provides: ${python:Provides}
-Description: Sphinx "blockdiag" extension
- This package contains the blockdiag Sphinx extension. This extension enable
- you to insert block diagrams in your Sphinx document. This renders block
- diagrams by using python-blockdiag.
-
Package: python3-sphinxcontrib.blockdiag
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends},
diff -Nru sphinxcontrib-blockdiag-1.5.5/debian/rules
sphinxcontrib-blockdiag-1.5.5/debian/rules
--- sphinxcontrib-blockdiag-1.5.5/debian/rules 2014-11-22 18:13:16.0
+0100
+++ sphinxcontrib-blockdiag-1.5.5/debian/rules 2019-10-19 02:13:23.0
+0200
@@ -8,13 +8,8 @@
export PYBUILD_DISABLE=test
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
override_dh_python3:
dh_python3
find $(CURDIR)/debian/python3-sphinxcontrib.blockdiag -name tests -a
-type d | xargs rm -rf
-
-override_dh_python2:
- dh_python2
- find $(CURDIR)/debian/python-sphinxcontrib.blockdiag -name tests -a
-type d | xargs rm -rf
-
Bug#936219: blockdiag: Python2 removal in sid/bullseye
Those 15 reverse dependencies are really only 6 source packages to work on, so I think we should go ahead and fix those ASAP, rather than reverting. I've raised severity for the 6 affected packages. I haven't found any package using the Python 2 flavor of the sphinx extension, so it seems safe to do the work now. Thomas Goirand (zigo)
Bug#937855: python-jsonext: Python2 removal in sid/bullseye (now this is an RC bug...)
Hi Ben,
Attached is a debdiff fixing this RC bug. There's other clean-up
necessary for this package (like removing the X-Python{3,}-Version:)
which I think should be done before the upload.
Let me know if you're ok for me to NMU this package.
Cheers,
Thomas Goirand (zigo)
diff -Nru python-jsonext-0.4.1/debian/changelog
python-jsonext-0.4.1/debian/changelog
--- python-jsonext-0.4.1/debian/changelog 2017-08-26 13:11:04.0
+0200
+++ python-jsonext-0.4.1/debian/changelog 2019-10-18 14:23:09.0
+0200
@@ -1,3 +1,10 @@
+python-jsonext (0.4.1-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support (Closes: #937855).
+
+ -- Thomas Goirand Fri, 18 Oct 2019 14:23:09 +0200
+
python-jsonext (0.4.1-1) unstable; urgency=medium
* The “علي محمد باقر النمر (Ali Mohammed Baqir al-Nimr)” release.
diff -Nru python-jsonext-0.4.1/debian/control
python-jsonext-0.4.1/debian/control
--- python-jsonext-0.4.1/debian/control 2017-08-26 13:11:04.0 +0200
+++ python-jsonext-0.4.1/debian/control 2019-10-18 14:23:07.0 +0200
@@ -9,11 +9,6 @@
python3-six,
python3-setuptools,
python3-all,
-python-pytest-runner,
-python-arrow,
-python-six,
-python-setuptools,
-python-all (>= 2.7~),
dh-python,
debhelper (>= 10~)
Homepage: https://pypi.org/project/jsonext/
@@ -32,14 +27,3 @@
the standard Python built-in-types.
.
This package installs the library for Python 3.
-
-Package: python-jsonext
-Architecture: all
-Depends:
-${python:Depends},
-${misc:Depends}
-Description: serialisation to/from JSON for extra types — Python 2
- ‘jsonext’ makes easy JSON serialisation of Python objects outside of
- the standard Python built-in-types.
- .
- This package installs the library for Python 2.
diff -Nru python-jsonext-0.4.1/debian/rules python-jsonext-0.4.1/debian/rules
--- python-jsonext-0.4.1/debian/rules 2017-08-26 13:11:04.0 +0200
+++ python-jsonext-0.4.1/debian/rules 2019-10-18 14:23:09.0 +0200
@@ -14,11 +14,11 @@
export PYBUILD_NAME = jsonext
-
+
%:
- dh $@ --with python3,python2 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
+
-
.PHONY: get-packaged-orig-source
get-packaged-orig-source:
$(uscan-download-source) --download-current-version
@@ -46,12 +46,12 @@
--check-dirname-level=0 ${package_dir}
endef # uscan-download-source
-
+
override_dh_auto_clean:
dh_auto_clean
$(RM) -r ${GENERATED_FILES}
-
+
# Local variables:
# mode: makefile
# coding: utf-8
diff -Nru python-jsonext-0.4.1/debian/tests/control
python-jsonext-0.4.1/debian/tests/control
--- python-jsonext-0.4.1/debian/tests/control 2017-08-26 13:11:04.0
+0200
+++ python-jsonext-0.4.1/debian/tests/control 2019-10-18 14:23:09.0
+0200
@@ -2,17 +2,12 @@
# Control file for Debian ‘autopkgtests’.
# Documentation: ‘/usr/share/doc/autopkgtest/README.package-tests.rst.gz’.
-Tests: smoke-python2
-Depends:
-python-pkg-resources,
-python-jsonext
-
Tests: smoke-python3
Depends:
python3-pkg-resources,
python3-jsonext
-
+
# Local variables:
# coding: utf-8
# mode: conf
diff -Nru python-jsonext-0.4.1/debian/tests/smoke-python2
python-jsonext-0.4.1/debian/tests/smoke-python2
--- python-jsonext-0.4.1/debian/tests/smoke-python2 2017-08-26
13:11:04.0 +0200
+++ python-jsonext-0.4.1/debian/tests/smoke-python2 1970-01-01
01:00:00.0 +0100
@@ -1,39 +0,0 @@
-#! /bin/bash
-#
-# debian/tests/smoke-python2
-# Part of Debian ‘python-jsonext’ package.
-#
-# Copyright © 2016–2017 Ben Finney
-# This is free software; you may copy, modify and/or distribute this work
-# under the terms of the GNU General Public License, version 3 or later.
-# No warranty expressed or implied.
-#
-# Smoke test for package in Python 2 environments.
-
-set -o errexit
-set -o errtrace
-set -o nounset
-
-DISTRIBUTION_NAME=jsonext
-MODULE_NAMES=(
-jsonext
-)
-
-test_opts="--distribution=$DISTRIBUTION_NAME"
-for mod in ${MODULE_NAMES[@]} ; do
-# Accumulate the module names.
-test_opts="$test_opts --module=$mod"
-done
-
-for py in $(pyversions -i) ; do
-printf "Python command: %s\n" $py
-$py debian/tests/smoke_test.py $test_opts
-printf "\n"
-done
-
-
-# Local variables:
-# coding: utf-8
-# mode: shell-script
-# End:
-# vim: fileencoding=utf-8 filetype=sh :
Bug#936270: Please fix calibre, or get it out of Debian
Hi Norbert, I wrote to you not to be aggressive, because I've seen so many posts of yours toward everyone. Yet, you still call me a liar. On top of this, you give yourself the permission to lecture me about the CoC. Well done! Now, let be still, despite your tone, to go to the bottom of the issue. On 10/15/19 12:12 AM, Norbert Preining wrote: > Hi Thomas, > > thanks for your email. > In case you decide to return to generally agreed upon community > standards of communication, including the CoC, and stop spreading > FUD and lies, I will happily discuss with you the issues at hand. > > FUD and lie: >> particularly counter-productive, since we're not seeing any progress >> being done on calibre, neither upstream or in Debian. It's been nearly a month that the calibre package is in this shape, ie not converted to Python 3. Besides this: https://github.com/kovidgoyal/calibre/blob/master/setup.py#L20 How is this a lie? There's no FUD either, just facts. There's also this, from the author itself: https://bugs.launchpad.net/calibre/+bug/1714107 I don't see any sign that the upstream author has changed his mind, and is willing to do the work of moving to Python 3. Or has this changed? If so, please point to some upstream commit showing there's ongoing work. Then you'll be able to tell me I was *mistaking* (and not lying). BTW, if you're not aware, we just discussed, within the Python team, about raising the severity of packages using Python 2 to serious. That's regardless of what happened the dependency of the package. So even if I revert the upload of cherrypy3 (which, again, can only happen if tumbleweed does it on objgraph), your package will have to continue to be RC. I very much have the same opinion as Neil Williams here: https://lists.debian.org/debian-python/2019/10/msg00043.html Also, IMO you are mistaking when referring to Doko's mail about keeping python 2 application. I don't think this would include something like Calibre, unfortunately, especially it if has many Python 2 dependencies. > Lie: >> to, this wont help. Doing BTS ping-pong wont help either. I completely fail to see where the lie is... You've downgraded the severity for your package to normal, cloned it to cherrypy3 where you've set the severity to serious. That's BTS ping-pong to me. Or did I miss something? In any case, CC-ing the community team is a good idea, especially when gratuitously calling me a liar publicly. Thomas Goirand (zigo)
Bug#936270: Please fix calibre, or get it out of Debian
Hi Norbert, cherrypy3 got python2 removed because the same happened to objgraph before that. See: https://tracker.debian.org/news/1060068/accepted-objgraph-341-2-source-into-unstable/ I don't mind reverting the change to cherrypy3, but the the work must be done on objgraph first, otherwise cherrypy3 wont build. Though I find it particularly counter-productive, since we're not seeing any progress being done on calibre, neither upstream or in Debian. There's no need to drag your feet, or complain, it wont change the fact that Python2 is being removed from Bullseye because it's dead upstream on the 1st of January next year. Making artificially cherrypy3 RC buggy, while the package is in perfect shape isn't helpful either, and this needs to be reverted. Your thoughts? Cheers, Thomas Goirand (zigo) P.S: Please don't be aggressive with me or anyone else, as you are used to, this wont help. Doing BTS ping-pong wont help either.
Bug#935621: Bug935621: openstack-dashboard: incompatible with django 2.2
On 10/11/19 7:42 PM, Boyuan Yang wrote: > Hi zigo, Michael, > > On Wed, 9 Oct 2019 18:02:16 +0200 Thomas Goirand wrote: >> Hi, >> >> This was fixed with the last upload of Horizon. > > Unfortunately the last upload was not a source-only upload. As a result, the > fixed version will never migrate to testing. > > Could you please make another source-only upload as described in > https://wiki.debian.org/SourceOnlyUpload at your convenience? > > Thanks, > Boyuan Ynag It looks like Michal didn't know. I've re-uploaded source-only. Cheers, Thomas Goirand (zigo)
Bug#942056: openvswitch: Incomplete debian/copyright?
On 10/9/19 6:32 PM, Chris Lamb wrote: > Source: openvswitch > Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-1 > Severity: serious > Justication: Policy §12.5 > X-Debbugs-CC: Thomas Goirand , ftpmas...@debian.org > > Hi, > > I just ACCEPTed openvswitch from NEW but noticed it was missing > attribution in debian/copyright for at least Ericsson. > > This is in no way exhaustive so please check over the entire package > carefully and address these on your next upload. Hi, Thanks again. My last upload, which fixes it, goes again through NEW, as we (re-)added the support for ipsec. Cheers, Thomas Goirand (zigo)
Bug#942056: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #942056 in openvswitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/8879acc9c2223940cb30f530213eec32c2572540 Fixed d/copyright (Closes: #942056). (this message was generated automatically) -- Greetings https://bugs.debian.org/942056
Bug#939288: marked as pending in python-os-vif
Control: tag -1 pending Hello, Bug #939288 in python-os-vif reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-vif/commit/5e1c238522b1b136208d3ed7d0c866d9a97f7977 * New upstream release: - Fixes CVE-2019-15753 (Closes: #939288). (this message was generated automatically) -- Greetings https://bugs.debian.org/939288
Bug#941644: marked as pending in python-debtcollector
Control: tag -1 pending Hello, Bug #941644 in python-debtcollector reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-debtcollector/commit/c0388a7c7d530f555d65527d01c3c1c8ee123717 Do not use Python2 in autopkgtest (Closes: #941644). (this message was generated automatically) -- Greetings https://bugs.debian.org/941644
Bug#941478: Package python3-apscheduler is empty
Package: python3-apscheduler Version: 3.6.1-1 Severity: grave Tags: patch Hi, Since my last NMU, the package is empty, because of override_dh_auto_install being in debian/rules .PHONY: target. I hope you don't mind, but I intend to NMU this quick fix. Sorry for my mistake. Cheers, Thomas Goirand (zigo)
Bug#941030: marked as pending in python-os-apply-config
Control: tag -1 pending Hello, Bug #941030 in python-os-apply-config reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-apply-config/commit/cef8678afe476e2fc2a49aab891d7b7b3937c0f8 Add Breaks+Replaces for python-os-apply-config (Closes: #941030). (this message was generated automatically) -- Greetings https://bugs.debian.org/941030
Bug#941028: marked as pending in python-os-refresh-config
Control: tag -1 pending Hello, Bug #941028 in python-os-refresh-config reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-refresh-config/commit/a087c03588ac4ed5187479dff1138e555beda050 Add Breaks+Replaces python-os-refresh-config (Closes: #941028). (this message was generated automatically) -- Greetings https://bugs.debian.org/941028
Bug#939881: marked as pending in rabbitmq-server
Control: tag -1 pending Hello, Bug #939881 in rabbitmq-server reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/rabbitmq-server/commit/996b2a7a86e27ad605df0229a8ce4c92625e5d61 Now packaging 3.7.18: Can be built with Elixir 1.9.x (Closes: #939881). (this message was generated automatically) -- Greetings https://bugs.debian.org/939881
Bug#933581: marked as pending in python-networkx
Control: tag -1 pending Hello, Bug #933581 in python-networkx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/modules/python-networkx/commit/30d95daa7c707fb89ccb6cae4863e0661a9aadf5 Removed build-depends on texlive-generic-extra (Closes: #933581). (this message was generated automatically) -- Greetings https://bugs.debian.org/933581
Bug#939439: marked as pending in websockify
Control: tag -1 pending Hello, Bug #939439 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/commit/ca536f822021784bdbd4afdf321bf77adb60c5f9 Fix deleting manpage (Closes: #939439). (this message was generated automatically) -- Greetings https://bugs.debian.org/939439
Bug#939439: marked as pending in websockify
Control: tag -1 pending Hello, Bug #939439 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/commit/e4d2f2f8db2b5f6c5d6f235c578bd2e2b81f7ca9 Remove duplicate manpage from python3-websocify (Closes: #939439). (this message was generated automatically) -- Greetings https://bugs.debian.org/939439
Bug#939439: marked as pending in websockify
Control: tag -1 pending Hello, Bug #939439 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/commit/ca536f822021784bdbd4afdf321bf77adb60c5f9 Fix deleting manpage (Closes: #939439). (this message was generated automatically) -- Greetings https://bugs.debian.org/939439
Bug#880154: python-turbogears2: please provide Python3 module
On 9/7/19 6:05 AM, Sandro Tosi wrote: > control: severity -1 serious > > On Mon, 30 Oct 2017 10:46:21 +0800 Drew Parsons wrote: >> python-turbogears2 is currently only provided as a python2 module. >> >> Could you please also package the python3 version? >> i.e. provide python3-turbogears2 > > Raising severity as we need to assess and draw a path forward for tg > > currently: > * upstream claims https://github.com/TurboGears/tg2/ compatibility > with python3.7 > * python-turbogears2 has no reverse dependencies > * it has quite low popcon of 16 > * we are actually shipping version 2.3.7, that was released in October 2015 > (!) > > Here i see only 2 ways: > > * remove turbogears2 (let's face it, it _lost_ the web frameworks > battle; back in the days you could hear people talking about tg, > nowadays, iet's either django or flask..) > * move tg to python3. > > given the relative low interest for tg in debian (see popcon) it's > probably easier to just remove it, but i would not be against > upgrading it to the latest version and provide *only* the python3 > package, if this is done in the next few weeks. > > I'll follow up in a week if i dont hear anything back. > > Thanks, > Sandro Hi Sandro, I agree with what you wrote, let's remove tg from Debian, unless Laszlo has interest in upgrading and continuing the maintenance. Thomas
Bug#940313: marked as pending in python-osprofiler
Control: tag -1 pending Hello, Bug #940313 in python-osprofiler reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-osprofiler/commit/4d412c5272c4ffb7cfb6c12073c3df326cd6084a * Removed python3-osprofiler.postinst which had update-alternatives for dual Python support (Closes: #940313). (this message was generated automatically) -- Greetings https://bugs.debian.org/940313
Bug#936189: Packages depending on python-testtools are now RC: is bzr still a thing?
On 9/15/19 2:26 PM, Mattia Rizzolo wrote: > Considering that this is bzr we are talking about, a package that is > already entering the graveyard, I think it would be easiest to just > disable the test suite and move on. > > But I would be happier it Thomas at least checked the rdeps before > dropping packages, at least evaluating if breaking things is alrightif > he really likes to break packages :/ You mean check *better*. Because I do carefully check each time, as much as I can, but in this occurrence, it looks like I didn't check well enough. Mistakes unfortunately do happen when you work on a lot of packages. Moreover, the current tooling we have at our disposal is kind of broken. reverse-depends takes sometimes forever in Sid for a reason I can't figure out. And if I'm not mistaking, that's the only tool we have that can check reverse dependencies in a meaningful way. Or is there a better way? I've read others using a dak command, how? On 9/15/19 5:17 PM, Jelmer Vernooij wrote: > It's not just bzr, it's also a bunch of plugins for bzr that we'd have > to disable the testsuite for - as well as a bunch of other non-bzr-related packages - python-subunit, python-fixtures, python-testscenarios, python-daemon, python-fastimport. I've already removed Python 2 support from subunit, python-fixtures, and python-testscenarios. Now, as I wrote in the bug report, what worries me aren't these, but the other packages that are depending on python-daemon: Packages without Python 3 support upstream: - bcfg2 doesn't seem to have Python 3 support upstream, neither the Debian package. - nss-pam-ldapd isn't Python 3 ready upstream. Note that the debian maintainer the same person as upstream. - There's been zero upstream work on this repository: https://github.com/Yubico/python-pyhsm so the package has no change to be Python 3 ready anytime soon. Packages that simply need an upgrade from latest upstream release: - lavapdu-daemon should be upgraded to latest upstream release to have Python 3 support. - mini-buildd in Experimental has been converted to Python 3, while the version in Sid is still Python 2. - I haven't been able to tell for lava-coordinator. So, for bcfg2, nss-pam-ldapd, and python-pyhsm, I'm really not convinced that waiting for longer will help. That's a general problem that we btw need to address: how are we going to deal with this? There's going to be a lot of it, and we need to find a way out if we really are going to get Python 2 out. For the other 3, I shouldn't be hard to address by the current maintainers. I've raised the severity of #936189 #937165 #938069 #936819 #937049 #936818 to serious, and included them as Cc to this reply, in order to warn the maintainers. I haven't done it for the BZR stuff, as obviously, the package maintainer is aware now. Again, sorry that it happened this way. Cheers, Thomas Goirand (zigo)
Bug#940283: Done
Hi, So, I've uploaded python-fixtures with Python 2 support removed. Now, it looks like python-fastimport is part of a dependency chain for BZR. Since, as I wrote, BZR is probably going to be removed from Debian, I'm not sure if we should fix python-fastimport or just get it removed from Debian as well (I'd vote for the later). So, now we still have the problem to fix with python-daemon, which has, as reverse dependency: - bcfg2 doesn't seem to have Python 3 support upstream, neither the Debian package. - mini-buildd in Experimental has been converted to Python 3, while the version in Sid is still Python 2. - nss-pam-ldapd isn't Python 3 ready upstream. Note that the debian maintainer the same person as upstream. - There's been zero upstream work on this repository: https://github.com/Yubico/python-pyhsm so the package has no change to be Python 3 ready anytime soon. - lavapdu-daemon should be upgraded to latest upstream release to have Python 3 support. - I haven't been able to tell for lava-coordinator. I suppose we could raise the severity to serious for the Python 2 removal bug of these packages, and get the work done for python-daemon, which is otherwise useful (in Python 3). Your thoughts? Cheers, Thomas Goirand (zigo)
Bug#938215: marked as pending in python-testtools
Control: tag -1 pending Hello, Bug #938215 in python-testtools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-testtools/commit/5544d31c5c3905ee7295c6af398094d65fb0efd4 Removed Python 2 support (Closes: #938215). (this message was generated automatically) -- Greetings https://bugs.debian.org/938215
Bug#914481: marked as pending in python-pylxd
Control: tag -1 pending Hello, Bug #914481 in python-pylxd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-pylxd/commit/a2e30d5e5d0a9ad6b1731786174ccfe86b94cd56 * New upstream release (Closes: #914481). * Removed Python 2 support (Closes: #938074). (this message was generated automatically) -- Greetings https://bugs.debian.org/914481
Bug#937590: marked as pending in python-autobahn
Control: tag -1 pending Hello, Bug #937590 in python-autobahn reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-autobahn/commit/8ae6100ca9ec1e90ebf37e76c57541e2af07a0e4 Removed Python 2 support (Closes: #937590). (this message was generated automatically) -- Greetings https://bugs.debian.org/937590
Bug#937590: marked as pending in python-autobahn
Control: tag -1 pending Hello, Bug #937590 in python-autobahn reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-autobahn/commit/8ae6100ca9ec1e90ebf37e76c57541e2af07a0e4 Removed Python 2 support (Closes: #937590). (this message was generated automatically) -- Greetings https://bugs.debian.org/937590
Bug#938875: yum-utils: Python2 removal in sid/bullseye
On 9/5/19 9:18 PM, Mike Miller wrote: > The upstream replacement for the combination of yum + yum-utils (Python > 2 only) is dnf (Python 3). > > The only reverse dependency of yum-utils is mock. It looks like the > version of mock already in Debian supports either dnf or yum. Once dnf > is in Debian, mock can drop the dependency on yum and yum-utils, and > yum-utils can be removed. > And then I believe yum should also be removed. Your thoughts? Cheers, Thomas Goirand (zigo)
Bug#926250: marked as pending in python-json-patch
Control: tag -1 pending Hello, Bug #926250 in python-json-patch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-json-patch/commit/cb2da24b42bc3fab99a2eceb3c496d1148ca44ff * Manage /usr/bin/jsondiff with update-alternatives to avoid clash with python3-jsondiff (Closes: #926250). (this message was generated automatically) -- Greetings https://bugs.debian.org/926250
Bug#939439: marked as pending in websockify
Control: tag -1 pending Hello, Bug #939439 in websockify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/websockify/commit/e4d2f2f8db2b5f6c5d6f235c578bd2e2b81f7ca9 Remove duplicate manpage from python3-websocify (Closes: #939439). (this message was generated automatically) -- Greetings https://bugs.debian.org/939439
Bug#928791: marked as pending in congress
Control: tag -1 pending Hello, Bug #928791 in congress reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/congress/commit/92cb080108bdfa87f21029adc87dcbca3515d587 Correctly clean-up builds (Closes: #928791). (this message was generated automatically) -- Greetings https://bugs.debian.org/928791
Bug#934644: marked as pending in openstack-meta-packages
Control: tag -1 pending Hello, Bug #934644 in openstack-meta-packages reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/debian/openstack-meta-packages/commit/828cae7351604dd1dd3f96fb2fadd60ab662ec3f Fix dependency on keystoneclient (Closes: #934644). (this message was generated automatically) -- Greetings https://bugs.debian.org/934644
Bug#934930: marked as pending in novnc
Control: tag -1 pending Hello, Bug #934930 in novnc reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/novnc/commit/c5f7d344274668ce740601e192f705d73b4ab71a Removed python 2 support (Closes: #934930). (this message was generated automatically) -- Greetings https://bugs.debian.org/934930
Bug#935657: Please port and switch this package to Python 3 or remove it from Debian
Package: calendarserver Version: 9.2+dfsg-1 Severity: serious Hi, We're trying to remove Python 2 from Bullseye. And I came across your package, which is still py2 only. Please switch it to Python 3. If that's not possible, then it's probably the time for your package to get removed from Debian, unfortunately. Cheers, Thomas Goirand (zigo)
Bug#935621: openstack-dashboard: incompatible with django 2.2
Hi, I'm very much aware of this issue, but can't find a way to fix it myself. openstack_auth/views.py is using a login() function instead of the now required LoginView class. I'm not skilled enough in Django to do this myself, and upstream unfortunately doesn't feel it's urgent. Until this is fixed, it's useless to work on anything else regarding Horizon (I do believe I could fix the rest of the Django 2.2 related issues). Cheers, Thomas Goirand (zigo)
Bug#935432: marked as pending in kazoo
Control: tag -1 pending Hello, Bug #935432 in kazoo reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/kazoo/commit/644979c932faa7624ed0af1ae3d5c8e5c118faf9 Removed Pyhton 2 support (Closes: #935432). (this message was generated automatically) -- Greetings https://bugs.debian.org/935432
Bug#934903: Please switch to Python 3 or remove the package from Sid/Bullseye
Package: pycmail Version: 0.1.6 Severity: serious Hi, As we're removing Python 2 from Bullseye, we're working on removing all trace of Python 2 on all leaf packages (first). I've tried to port pycmail to Python 3, but it's non-trivial. Please do the work, or get the package removed from Sid/Bullseye. Cheers, Thomas Goirand (zigo)
Bug#934901: Please switch to Python 3 or remove your package from Sid/Bullseye
Package: python-gpiv Version: 2.0.0-4.2 Severity: serious Hi, As we're removing Python 2 from Bullseye, we need your package to be either switched to Python 3, or removed from Sid/Bullseye. Please let everyone know your intention ASAP. Cheers, Thomas Goirand (zigo)
Bug#934858: Please port viewvc to Python 3 or get it removed from Sid/Bullseye
Source: viewvc Version: 1.1.26 Severity: serious Hi, Viewvc seems to be Python 2 only, and having a quick look, it needs a lot of work to make it work under Python 3. Since we want to get Python 2 removed from Bullseye, you have no choice but to either port it to Python3, convince upstream to do so, or drop the package from Bullseye (and continue to maintain it for the next 5 years in Buster). Your thoughts? Cheers, Thomas Goirand (zigo)
Bug#934711: Please package latest upstream, and switch to Python 3
Package: python-googleapi Version: 1.5.5-1 Severity: serious Hi, We're trying to remove Python 2 for Bullseye. python-monotonic support for Python 2 is removed, and therefore, your package depends on a cruft package. Please package the latest version upstream which has support for Python 3, and remove Python 2 support / use. Cheers, Thomas Goirand (zigo)
Bug#934442: marked as pending in python-gabbi
Control: tag -1 pending Hello, Bug #934442 in python-gabbi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/python/python-gabbi/commit/6a3e62ddf6ba5ba9186b07e01875d4172ed9a83a Removed Python 2 support (Closes: #934442). (this message was generated automatically) -- Greetings https://bugs.debian.org/934442
Bug#934095: marked as pending in python-os-testr
Control: tag -1 pending Hello, Bug #934095 in python-os-testr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/libs/python-os-testr/commit/1653e1fe95bebfb2f2402f6435a50b678805a146 Removed Python 2 support (Closes: #934095). (this message was generated automatically) -- Greetings https://bugs.debian.org/934095
Bug#933921: src:python-tablib: Unsafe use of yaml.load()
On 8/6/19 1:58 AM, Joseph Herlant wrote: > Hi, > > Thanks Scott for the report. > Tomas: the repository in Openstack was archived long ago because it > was ported to https://salsa.debian.org/python-team/modules/python-tablib > The module is used by other packages than openstack (like > django-tables if I remember correctly), so could you please hold off > the removal request please? > If the repo in the openstack group bother you, you can drop it but > please don't drop tablib (at least not the python3 version). > > Thanks, > Joseph > Indeed, it has a single reverse build-depends. Closing the RM bug then. I'd still advise upstream against using this library which is of lower code quality. Cheers, Thomas Goirand (zigo)
Bug#933821: python-tuskarclient (build-)depends on cruft package.
On 8/4/19 1:07 AM, Peter Michael Green wrote: > Package: python-tuskarclient > Severity: serious > Version: 0.1.18-1 > Tags: bullseye, sid > > python-tuskarclient depends on the python-cliff, python-keystoneclient, > python-openstackclient and python-stevedore binary packages which are no > longer built by the corresponding source packages. > > If this is going to stay around it looks like it needs to migrate to > python 3. Hi, I've filled an RM bug for this package, so it will go away... The Tuskar project has been retired a long time ago, so this is overdue. Thomas Goirand (zigo)
Bug#933921: src:python-tablib: Unsafe use of yaml.load()
On 8/5/19 7:35 AM, Scott Kitterman wrote: > Package: src:python-tablib > Version: 0.12.1-2 > Severity: grave > Tags: security > Justification: user security hole > > The new version of pyyaml no longer allows use of yaml.load() without a > loader being specifed. This raises a deprecation warning which has > caused and autopkgtest failure on this package. These are generally > trivial to fix, see the upstream guidance [1]. > > Scott K > > [1] https://github.com/yaml/pyyaml/wiki/PyYAML-yaml.load(input)-Deprecation > > Hi, FYI, I have just filed a removal bug for this one, as it's not used by any OpenStack things anymore. Cheers, Thomas Goirand (zigo)
Bug#933318: python-os-cloud-config (build-)depends on cruft packages.
On 7/29/19 8:44 AM, Peter Michael Green wrote: > Package: python-os-cloud-config > Severity: serious > Tags: bullseye, sid > > python-os-cloud-config depends on a number of binary packages that are > no longer built by their corresponding source packages, including > > python-glanceclient > python-ironicclient > python-keystoneclient > python-neutronclient > python-novaclient > python-oslo.config > python-oslo.i18n > python-pbr > > Presumablly this package needs to migrate to python3 if it is going to > stay around at all. Hi! Good catch. I just requested its removal, it's of no use in Debian. Cheers, Thomas Goirand (zigo)
Bug#933146: FTBFS, not Django 2.2 ready
Package: python-django-rosetta
Version: 0.7.6-1
Severity: serious
Tags: patch
Hi,
Please find attached patch for the Python 2 removal part.
The package still FTBFS after this patch:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd
/<>/.pybuild/cpython3_3.7_django-rosetta/build; python3.7 -m
unittest discover -v
rosetta.tests (unittest.loader._FailedTest) ... ERROR
==
ERROR: rosetta.tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: rosetta.tests
Traceback (most recent call last):
File "/usr/lib/python3.7/unittest/loader.py", line 470, in _find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.7/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File
"/<>/.pybuild/cpython3_3.7_django-rosetta/build/rosetta/tests/__init__.py",
line 1, in
from .tests import *
File
"/<>/.pybuild/cpython3_3.7_django-rosetta/build/rosetta/tests/tests.py",
line 3, in
from django.contrib.auth.models import User, Group
File "/usr/lib/python3/dist-packages/django/contrib/auth/models.py", line 2,
in
from django.contrib.auth.base_user import AbstractBaseUser, BaseUserManager
File "/usr/lib/python3/dist-packages/django/contrib/auth/base_user.py", line
47, in
class AbstractBaseUser(models.Model):
File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 103, in
__new__
app_config = apps.get_containing_app_config(module)
File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 252, in
get_containing_app_config
self.check_apps_ready()
File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 134, in
check_apps_ready
settings.INSTALLED_APPS
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 79, in
__getattr__
self._setup(name)
File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 64, in
_setup
% (desc, ENVIRONMENT_VARIABLE))
django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS,
but settings are not configured. You must either define the environment
variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing
settings.
--
Ran 1 test in 0.000s
FAILED (errors=1)
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.7_django-rosetta/build; python3.7 -m
unittest discover -v
dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:10: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2019-07-26T21:43:50Z
diff -u -N -r debian/changelog ../debian/changelog
--- debian/changelog2019-07-26 23:44:33.561224883 +0200
+++ ../debian/changelog 2019-07-26 23:43:01.840631647 +0200
@@ -1,4 +1,4 @@
-python-django-rosetta (0.7.6-1) UNRELEASED; urgency=medium
+python-django-rosetta (0.7.6-1) unstable; urgency=medium
[ Michael Fladischer ]
* New upstream release.
@@ -24,7 +24,14 @@
* d/watch: Use https protocol
* Convert git repository from git-dpm to gbp layout
- -- Michael Fladischer Tue, 04 Aug 2015 09:47:58 +0200
+ [ Thomas Goirand ]
+ * Team upload.
+ * Ran wrap-and-sort -bast.
+ * Switch to debhelper-compat=11.
+ * Removed Python 2 support.
+ * Add missing build-depends: python3-django, python3-polib.
+
+ -- Thomas Goirand Fri, 26 Jul 2019 23:35:51 +0200
python-django-rosetta (0.7.2-1) unstable; urgency=low
diff -u -N -r debian/compat ../debian/compat
--- debian/compat 2019-07-26 23:44:33.561224883 +0200
+++ ../debian/compat1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-7
diff -u -N -r debian/control ../debian/control
--- debian/control 2019-07-26 23:44:33.561224883 +0200
+++ ../debian/control 2019-07-26 23:42:33.088444857 +0200
@@ -1,50 +1,29 @@
Source: python-django-rosetta
Maintainer: Debian Python Modules Team
-Uploaders: Michael Ziegler
+Uploaders:
+ Michael Ziegler ,
Section: python
Priority: optional
-Build-Depends: debhelper (>= 7.0.50~),
- dh-python,
- python,
- python-setuptools,
- python3-all,
- python3-setuptools
+Build-Depends:
+ debhelper-compat (= 11),
+ dh-python,
+ python3-all,
+ python3-django,
+ python3-polib,
+ python3-setuptools,
Standards-Version: 3.9.6
Vcs-Browser: https://salsa.debian.org/python-team/modules/python-django-rosetta
Vcs-Git: https://salsa.debian.org/python-team/modules/python-django-rosetta.git
Homepage: http://code.google.co
Bug#933143: FTBFS, not Django 2.2 ready
Package: python-django-mptt
Version: 0.8.7-1
Severity: serious
Tags: patch
Hi,
Please find attached patch to do the Python 2 removal.
After this patch, your package continues to FTBFS. Please
get a fix for it.
Cheers,
Thomas Goirand (zigo)
From 373d818427a37e26e91b5e39084c634ce1d3c613 Mon Sep 17 00:00:00 2001
From: Thomas Goirand
Date: Fri, 26 Jul 2019 23:21:21 +0200
Subject: [PATCH] * Team upload. * Removed Breaks+Replaces:
python-django-mptt (<< 0.6.1-1~) after Buster release. * Removed Python
2 support.
---
debian/changelog | 11 --
debian/control | 52 +++-
debian/links | 1 -
debian/rules | 2 +-
4 files changed, 35 insertions(+), 31 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 19ded1a..9cbaf5d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,15 @@
-python-django-mptt (0.8.7-2) UNRELEASED; urgency=medium
+python-django-mptt (0.8.7-2) unstable; urgency=medium
+ [ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat.
- -- Ondřej Nový Sat, 20 Jul 2019 00:11:07 +0200
+ [ Thomas Goirand ]
+ * Team upload.
+ * Removed Breaks+Replaces: python-django-mptt (<< 0.6.1-1~) after Buster
+release.
+ * Removed Python 2 support.
+
+ -- Thomas Goirand Fri, 26 Jul 2019 23:19:09 +0200
python-django-mptt (0.8.7-1) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 8abd33b..aaea1a8 100644
--- a/debian/control
+++ b/debian/control
@@ -2,20 +2,25 @@ Source: python-django-mptt
Section: python
Priority: optional
Maintainer: Debian Python Modules Team
-Uploaders: Brian May
-Build-Depends: debhelper-compat (= 9), dh-python, python3-sphinx,
- python-all (>= 2.6.6-3~), python-setuptools, python-django (>= 1.6),
- python3-all, python3-setuptools, python3-django (>= 1.6),
+Uploaders:
+ Brian May ,
+Build-Depends:
+ debhelper-compat (= 9),
+ dh-python,
+ python3-all,
+ python3-django (>= 1.6),
+ python3-setuptools,
+ python3-sphinx,
Standards-Version: 3.9.7
Homepage: https://github.com/django-mptt/django-mptt
Vcs-Git: https://salsa.debian.org/python-team/modules/python-django-mptt.git
Vcs-Browser: https://salsa.debian.org/python-team/modules/python-django-mptt
-Package: python-django-mptt
+Package: python-django-mptt-doc
+Section: doc
Architecture: all
-Suggests: python-django-mptt-doc
-Depends: ${misc:Depends}, ${python:Depends}, libjs-jquery, python-django,
libjs-underscore
-Provides: ${python:Provides}
+Depends:
+ ${misc:Depends},
Description: Modified Preorder Tree Traversal Django application
Django MPTT is a reusable/standalone Django application which aims to
make it easy for you to use Modified Preorder Tree Traversal with your
@@ -23,26 +28,21 @@ Description: Modified Preorder Tree Traversal Django
application
.
It takes care of the details of managing a database table as a tree
structure and provides tools for working with trees of model instances.
-
-Package: python3-django-mptt
-Architecture: all
-Suggests: python-django-mptt-doc
-Depends: ${misc:Depends}, ${python3:Depends}, libjs-jquery, python3-django,
libjs-underscore
-Provides: ${python3:Provides}
-Description: Modified Preorder Tree Traversal Django application
- Django MPTT is a reusable/standalone Django application which aims to
- make it easy for you to use Modified Preorder Tree Traversal with your
- own Django models in your own applications.
.
- It takes care of the details of managing a database table as a tree
- structure and provides tools for working with trees of model instances.
+ This package contains the documentation.
-Package: python-django-mptt-doc
-Section: doc
+Package: python3-django-mptt
Architecture: all
-Depends: ${misc:Depends}
-Breaks: python-django-mptt (<< 0.6.1-1~)
-Replaces: python-django-mptt (<< 0.6.1-1~)
+Suggests:
+ python-django-mptt-doc,
+Depends:
+ libjs-jquery,
+ libjs-underscore,
+ python3-django,
+ ${misc:Depends},
+ ${python3:Depends},
+Provides:
+ ${python3:Provides},
Description: Modified Preorder Tree Traversal Django application
Django MPTT is a reusable/standalone Django application which aims to
make it easy for you to use Modified Preorder Tree Traversal with your
@@ -50,5 +50,3 @@ Description: Modified Preorder Tree Traversal Django
application
.
It takes care of the details of managing a database table as a tree
structure and provides tools for working with trees of model instances.
- .
- This package contains the documentation.
diff --git a/debian/links b/debian/links
index bf454c2..ab7e0de 100644
--- a/debian/links
+++ b/debian/links
@@ -1,3 +1,2 @@
/usr/share/javascript/jquery/jquery.js
usr/share/doc/python-django-mptt/html/static/jquery.js
/usr/share/javascript/underscore/underscore.js
usr/share/doc/python-django-mptt/html/static/underscore.js
-
diff --git a/debian/rules b/debian/rules
index 97b51ee..f7154df 100755
--- a/debian/rules
+++ b/
Bug#933130: FTBFS, not Django 2.2 ready
d pybuild:341: test: plugin custom failed with: exit code=1:
PYTHONPATH=. DJANGO_SETTINGS_MODULE=tests.settings django-admin test tests
dh_auto_test: pybuild --test -i python{version} -p 3.7 returned exit code 13
make[1]: *** [debian/rules:13: override_dh_auto_test] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Build finished at 2019-07-26T20:34:30Z
Finished
From 9c6245ffaae2f1c5dd62937f137c7cb0c31283ad Mon Sep 17 00:00:00 2001
From: Thomas Goirand
Date: Fri, 26 Jul 2019 22:31:05 +0200
Subject: [PATCH] * Team upload. * wrap-and-sort -bast. * Removed Python
2 support. * Removed version in python3-sqlparse, useless after Buster.
---
debian/changelog | 9 -
debian/control | 79
debian/rules | 7 ++--
debian/tests/control | 10 +-
4 files changed, 49 insertions(+), 56 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 0dd1075..6b7c7e1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,5 +1,6 @@
python-django-debug-toolbar (1:1.9.1-2) UNRELEASED; urgency=medium
+ [ Ondřej Nový ]
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/changelog: Remove trailing whitespaces
@@ -8,7 +9,13 @@ python-django-debug-toolbar (1:1.9.1-2) UNRELEASED;
urgency=medium
* Convert git repository from git-dpm to gbp layout
* Use debhelper-compat instead of debian/compat.
- -- Ondřej Nový Tue, 13 Feb 2018 10:08:38 +0100
+ [ Thomas Goirand ]
+ * Team upload.
+ * wrap-and-sort -bast.
+ * Removed Python 2 support.
+ * Removed version in python3-sqlparse, useless after Buster.
+
+ -- Thomas Goirand Fri, 26 Jul 2019 22:29:45 +0200
python-django-debug-toolbar (1:1.9.1-1) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 5dd2c80..6f961b6 100644
--- a/debian/control
+++ b/debian/control
@@ -2,35 +2,30 @@ Source: python-django-debug-toolbar
Section: python
Priority: optional
Maintainer: Debian Python Modules Team
-Uploaders: Andrew Starr-Bochicchio
-Build-Depends: debhelper-compat (= 9),
- dh-python,
- python-all,
- python3-all,
- python-django,
- python3-django,
- python-django-jinja,
- python3-django-jinja,
- python-html5lib,
- python3-html5lib,
- python-setuptools,
- python3-setuptools,
- python-sphinx (>= 1.0.7+dfsg-1~),
- python-sqlparse (>= 0.2.0),
- python3-sqlparse
+Uploaders:
+ Andrew Starr-Bochicchio ,
+Build-Depends:
+ debhelper-compat (= 9),
+ dh-python,
+ python3-all,
+ python3-django,
+ python3-django-jinja,
+ python3-html5lib,
+ python3-setuptools,
+ python3-sphinx,
+ python3-sqlparse,
Standards-Version: 4.1.2
Homepage: https://github.com/django-debug-toolbar/django-debug-toolbar
Vcs-Git:
https://salsa.debian.org/python-team/modules/python-django-debug-toolbar.git
Vcs-Browser:
https://salsa.debian.org/python-team/modules/python-django-debug-toolbar
-Package: python-django-debug-toolbar
+Package: python-django-debug-toolbar-doc
Architecture: all
-Depends: python-sqlparse (>= 0.2.0),
- ${misc:Depends},
- ${python:Depends}
-Recommends: python-pygments
-Suggests: libjs-jquery, python-django-debug-toolbar-doc
-Description: Embedded debugging toolbar for Django projects
+Section: doc
+Depends:
+ ${misc:Depends},
+ ${sphinxdoc:Depends},
+Description: Embedded debugging toolbar for Django projects (documentation)
The Django Debug Toolbar is a plug-in Django application that displays a set
of panels which conveys information about the current request at the top of
the
rendered page. It can show:
@@ -45,14 +40,20 @@ Description: Embedded debugging toolbar for Django projects
* HTTP headers
* Total requests, time, hits and misses of the cache.
* Which templates were rendered the context provided to each template.
+ .
+ This is the common documentation package.
Package: python3-django-debug-toolbar
Architecture: all
-Depends: python3-sqlparse (>= 0.2.0),
- ${misc:Depends},
- ${python3:Depends}
-Recommends: python3-pygments
-Suggests: libjs-jquery, python-django-debug-toolbar-doc
+Depends:
+ python3-sqlparse,
+ ${misc:Depends},
+ ${python3:Depends},
+Recommends:
+ python3-pygments,
+Suggests:
+ libjs-jquery,
+ python-django-debug-toolbar-doc,
Description: Embedded debugging toolbar for Django projects (Python 3 version)
The Django Debug Toolbar is a plug-in Django application that displays a set
of panels which conveys information about the current request at the top of
the
@@ -70,25 +71,3 @@ Description: Embedded debugging toolbar for Django
Bug#932985: Please remove Python 2 support
Source: django-session-security
Version: 2.6.5+dfsg-1
Severity: serious
Tags: patch
Hi,
Please remove Python 2 support. Attached patch may help.
Thomas
diff --git a/debian/changelog b/debian/changelog
index 50bbfe1..e9b3fe2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,15 @@
-django-session-security (2.6.5+dfsg-2) UNRELEASED; urgency=medium
+django-session-security (2.6.5+dfsg-2) unstable; urgency=medium
+ [ Ondřej Nový ]
* Use debhelper-compat instead of debian/compat.
* Bump Standards-Version to 4.4.0.
+ [ Thomas Goirand ]
+ * Team upload.
+ * Removed Python 2 support.
+ * Correctly overrides override_dh_sphinxdoc rather than auto_build.
+ * Add missing (build-)depends python3-six.
+
-- Ondřej Nový Sat, 20 Jul 2019 00:30:59 +0200
django-session-security (2.6.5+dfsg-1) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 7542d93..fab6569 100644
--- a/debian/control
+++ b/debian/control
@@ -3,10 +3,9 @@ Section: python
Priority: optional
Build-Depends: debhelper-compat (= 9),
dh-python,
- python-all,
- python-setuptools,
python3-all,
python3-setuptools,
+ python3-six,
python3-django,
python3-sphinx
Maintainer: Debian Python Modules Team
@@ -16,23 +15,10 @@ Vcs-Git:
https://salsa.debian.org/python-team/modules/django-session-security.gi
Standards-Version: 4.4.0
Homepage: http://django-session-security.rtfd.org/
-Package: python-django-session-security
-Architecture: all
-Depends: ${python:Depends},
- ${misc:Depends},
- ${sphinxdoc:Depends}
-Recommends: libjs-jquery
-Description: Python2 Django module to log a user out after X minutes
- A little javascript and middleware work together to ensure that the
- user was active during the past X minutes in any tab he has open.
- Otherwise, display a warning leaving a couple of minutes to show any
- kind of activity like moving the mouse. Otherwise, logout the user.
- .
- This is the Python 2 version.
-
Package: python3-django-session-security
Architecture: all
-Depends: ${python3:Depends},
+Depends: python3-six,
+ ${python3:Depends},
${misc:Depends},
${sphinxdoc:Depends}
Recommends: libjs-jquery
diff --git a/debian/python-django-session-security.install
b/debian/python-django-session-security.install
deleted file mode 100644
index dbdb301..000
--- a/debian/python-django-session-security.install
+++ /dev/null
@@ -1 +0,0 @@
-/usr/lib/python2*
diff --git a/debian/python-django-session-security.links
b/debian/python-django-session-security.links
deleted file mode 100644
index 67da37a..000
--- a/debian/python-django-session-security.links
+++ /dev/null
@@ -1 +0,0 @@
-/usr/share/javascript/jquery/jquery.js
/usr/lib/python2.7/dist-packages/session_security/tests/project/static/jquery.js
diff --git a/debian/rules b/debian/rules
index a655966..3842756 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,8 +1,10 @@
#!/usr/bin/make -f
#DH_VERBOSE=1
%:
- dh "$@" --with python2,python3,sphinxdoc --buildsystem=pybuild
+ dh "$@" --with python3,sphinxdoc --buildsystem=pybuild
-override_dh_auto_build:
- dh_auto_build -O--buildsystem=python_distutils
+override_dh_sphinxdoc:
+ifeq (,$(findstring nodoc, $(DEB_BUILD_OPTIONS)))
python3 setup.py build_sphinx
+ dh_sphinxdoc
+endif
Bug#932983: Please remove python2 support from your package
Source: django-restricted-resource
Version: 2016.8-2
Severity: serious
Tags: patch
Hi,
Please see attached quick and dirty patch to remove Python 2 support from
your module, which is needed since the upload of Django 2.2. in Sid.
Cheers,
Thomas Goirand (zigo)
diff --git a/debian/changelog b/debian/changelog
index 10909c0..ac7a04c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+django-restricted-resource (2016.8-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support.
+
+ -- Thomas Goirand Thu, 25 Jul 2019 14:49:40 +0200
+
django-restricted-resource (2016.8-2) unstable; urgency=medium
* Reduce build-depends to assist python3 transition.
diff --git a/debian/control b/debian/control
index 7358028..035b2bb 100644
--- a/debian/control
+++ b/debian/control
@@ -13,16 +13,6 @@ Homepage: http://www.linaro.org/engineering/validation
Vcs-Browser: https://github.com/Linaro/pkg-django-restricted-resource
Vcs-Git: https://github.com/Linaro/pkg-django-restricted-resource.git
-Package: python-django-restricted-resource
-Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
-Provides: ${python:Provides}
-Description: Django Base model for ownership and access control (Python 2)
- Restricted resources can have owners, users or groups of users,
- organised within the django admin interface. Resources can be
- public or private to allow an app to provide access control
- over model objects.
-
Package: python3-django-restricted-resource
Architecture: all
Depends: ${misc:Depends}, ${python3:Depends}
diff --git a/debian/rules b/debian/rules
index 45ed112..b16845e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,17 +1,15 @@
#!/usr/bin/make -f
%:
- dh $@ --with python2,python3
+ dh $@ --with python3
.PHONY: override_dh_auto_test
override_dh_auto_test:
# Run the bundled tests (in-memory database) when building the package
- LC_ALL=C python ./django_restricted_resource/test_project/manage.py test
LC_ALL=C python3 ./django_restricted_resource/test_project/manage.py
test
override_dh_auto_install:
dh_auto_install
- python setup.py install
--root=$(CURDIR)/debian/python-django-restricted-resource/ --install-layout=deb
python3 setup.py install
--root=$(CURDIR)/debian/python3-django-restricted-resource/ --install-layout=deb
override_dh_auto_clean:
Bug#932981: Please remove Python 2 support for this package
Source: django-ranged-response
Version: 0.2.0-1
Severity: serious
Tags: patch
Hi,
Attached is a patch to remove Python 2 support for this package,
needed since the upload of Django 2.2 in Sid.
Please apply and upload.
Cheers,
Thomas Goirand (zigo)
diff -Nru django-ranged-response-0.2.0/debian/changelog
django-ranged-response-0.2.0/debian/changelog
--- django-ranged-response-0.2.0/debian/changelog 2018-03-15
21:11:02.0 +0100
+++ django-ranged-response-0.2.0/debian/changelog 2019-07-25
14:34:43.0 +0200
@@ -1,3 +1,10 @@
+django-ranged-response (0.2.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Removed Python 2 support.
+
+ -- Thomas Goirand Thu, 25 Jul 2019 14:34:43 +0200
+
django-ranged-response (0.2.0-1) unstable; urgency=low
[ Sunil Mohan Adapa ]
diff -Nru django-ranged-response-0.2.0/debian/control
django-ranged-response-0.2.0/debian/control
--- django-ranged-response-0.2.0/debian/control 2018-03-15 21:11:02.0
+0100
+++ django-ranged-response-0.2.0/debian/control 2019-07-25 14:34:43.0
+0200
@@ -9,9 +9,6 @@
Build-Depends:
debhelper (>=11~),
dh-python,
- python-all,
- python-django,
- python-setuptools,
python3-all,
python3-django,
python3-setuptools
@@ -19,25 +16,6 @@
Homepage: https://pypi.python.org/pypi/django-ranged-response/
Vcs-Browser: https://salsa.debian.org/freedombox-team/django-ranged-response
Vcs-Git: https://salsa.debian.org/freedombox-team/django-ranged-response.git
-X-Python-Version: >= 2.7
-X-Python3-Version: >= 3.5
-
-Package: python-django-ranged-response
-Architecture: all
-Depends:
- python-django,
- ${misc:Depends},
- ${python:Depends}
-Provides:
- ${python:Provides}
-Recommends:
- ${python:Recommends}
-Description: Django file response to stream to browsers properly (Python 2)
- Provides RangedFileResponse that is a modified FileResponse that returns
- Content-Range headers with the response, so browsers that request the file,
- can stream the response properly.
- .
- This package installs the library for Python 2.
Package: python3-django-ranged-response
Architecture: all
diff -Nru django-ranged-response-0.2.0/debian/rules
django-ranged-response-0.2.0/debian/rules
--- django-ranged-response-0.2.0/debian/rules 2018-03-15 21:11:02.0
+0100
+++ django-ranged-response-0.2.0/debian/rules 2019-07-25 14:34:43.0
+0200
@@ -4,4 +4,4 @@
export PYBUILD_NAME=django-ranged-response
%:
- dh $@ --with python2,python3 --buildsystem=pybuild
+ dh $@ --with python3 --buildsystem=pybuild
Bug#932827: django-compat: broken with Django 2.2, FTBFS, not ready
Source: django-compat Version: 1.0.15-2 Severity: serious Hi, Django-compat is broken in may ways currently. 1/ It's using the loginview function instead of the LoginView class, as per the deprecation in Django 1.11. 2/ The tests/settings.py is missing lots of declarations. 3/ Python 2 support has to be removed from this package. I tried to work on this, but it doesn't look trivial. Cheers, Thomas Goirand (zigo)
Bug#932543: Please switch to Python 3
Package: python-pbcommand Version: 1.1.1-1 Severity: serious Hi, Your package is Python 2 only, please switch it to Python 3 (only), as I'm removing Python 2 support in python-xmlbuilder which is a reverse build dependency. Cheers, Thomas Goirand (zigo)
Bug#932542: Please switch to Python 3
Source: nipype Severity: serious Hi, Please make nipype use Python 3, as it wont have python-xvfbwrapper support for Python 2 in a few minutes (I'll be uploading in a few minutes a version of python-xvfbwrapper that removes Python 2 support). Cheers, Thomas Goirand
Bug#931104: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #931104 in openvswitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/1c99397def53892af9091eb1a3cad4db009837f4 Correct dependency on python3-six instead of python-six (Closes: #931104). (this message was generated automatically) -- Greetings https://bugs.debian.org/931104
Bug#931104: marked as pending in openvswitch
Control: tag -1 pending Hello, Bug #931104 in openvswitch reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/1c99397def53892af9091eb1a3cad4db009837f4 Correct dependency on python3-six instead of python-six (Closes: #931104). (this message was generated automatically) -- Greetings https://bugs.debian.org/931104
Bug#931214: ImportError: No module named oslo.config
On 6/30/19 7:40 AM, Paul Gevers wrote: > Hi Thomas, > > On 29-06-2019 23:02, Thomas Goirand wrote: >> On 6/29/19 10:12 AM, Paul Gevers wrote: >>> On Fri, 28 Jun 2019 13:52:43 +0200 =?iso-8859-1?Q?J=F6?= Fahlke >>> wrote: >>>> Package: python-os-collect-config >>>> Version: 0.1.15-1 >>>> Severity: grave >>> >>> This is on the radar of the release team, due to the very late time in >>> the release. Please, any comment from your side helps judging what to do. >>> >>>> I'm trying to use os-collect-config in a Debian stretch instance in an >>>> openstack cluster. However, running it immediately leads to an import >>>> error: >>> >>> [...] >>> >>>> ImportError: No module named oslo.config > >> It looks like it's just missing a runtime dependency. Just manually >> installing oslo.config would fix this. So I do contest that the package >> is not usable. It is, as long as you install pyhon-oslo.config. > > Did you check that that dependency is missing? I checked before and I > believe that python-oslo.config is in the listed dependencies *and* > installed on the machine where the log came from. What am I missing? > > Paul Hi Paul, Looking further, it looks like python-os-collect-config is a *very* old package in Debian (ie: no update since 2014), and it's not adapted anymore to the version of python-oslo.config that is in Debian. ie: oslo.config has moved away from a namespace based system to a non-namespace, so it should now be "import oslo_config" and not "import oslo.config". So, as a result, there's no way python-os-collect-config will work in Buster unless we update it to a much newer version, like for example version 9.2.1. Of course, it's already too late in the release process to do this, so we may just remove os-collect-config from Buster to fix the current situation. I'm sorry the OpenStack team failed to maintain this leaf package, however, my understanding is that this package is for TripleO, which isn't, and wont ever, work in Debian. Jo, could you explain what your use case is for os-collect-config in Debian? I really don't get how it can be useful for you. Cheers, Thomas Goirand (zigo)
Bug#931214: ImportError: No module named oslo.config
On 6/29/19 10:12 AM, Paul Gevers wrote: > Control: tags -1 sid buster stretch > > Dear OpenStack maintainers, > > On Fri, 28 Jun 2019 13:52:43 +0200 =?iso-8859-1?Q?J=F6?= Fahlke > wrote: >> Package: python-os-collect-config >> Version: 0.1.15-1 >> Severity: grave > > This is on the radar of the release team, due to the very late time in > the release. Please, any comment from your side helps judging what to do. > >> I'm trying to use os-collect-config in a Debian stretch instance in an >> openstack cluster. However, running it immediately leads to an import error: > > [...] > >> ImportError: No module named oslo.config > > Paul > Hi Paul, It looks like it's just missing a runtime dependency. Just manually installing oslo.config would fix this. So I do contest that the package is not usable. It is, as long as you install pyhon-oslo.config. Of course, this needs to be fixed, as since it's too late for fixing before buster, I can do such a fix for the first point release. Cheers, Thomas Goirand (zigo)
Bug#930996: Bug#929321: Update for SQLAlchemy to address CVE-2019-7164 CVE-2019-7548
On 6/27/19 8:39 PM, Paul Gevers wrote: > Hi Thomas, > > On 31-05-2019 01:34, Thomas Goirand wrote: >> Dear package maintainer, >> >> We're about to upgrade SQLAlchemy in Buster to address an SQL injection >> issue. The fixed package is in unstable, under the version 1.2.18+ds1-2. >> >> In some rare cases, this update may break reverse depenencies, leading >> to non-working SQL queries. >> >> This is why I'm writing this email to you today: to ask you to please >> test your application with SQLAlchemy 1.2.18+ds1-2 ASAP, to address any >> potential unforecast issue before the Buster release. >> >> Details about the discussion can be seen here in the Debian bug #929321. >> >> Best regards, > > Is this explaining the FTBFS of cloudkitty? We're looking at all the RC > bugs to see what needs to happen and cloudkitty is about to be removed > due this FTBFS. (I am not promising anything, but if the fix is clear, > we may leave it in an let you fix it in the first point release). > > Paul > Hi Paul, I applied upstream patch, released today: https://review.opendev.org/#/c/668120/ Debdiff attached. I've opened an unblock bug too: #931220 Cheers, Thomas Goirand (zigo) diff -Nru cloudkitty-8.0.0/debian/changelog cloudkitty-8.0.0/debian/changelog --- cloudkitty-8.0.0/debian/changelog 2019-01-24 14:45:39.0 +0100 +++ cloudkitty-8.0.0/debian/changelog 2019-06-28 15:01:45.0 +0200 @@ -1,3 +1,11 @@ +cloudkitty (8.0.0-5) unstable; urgency=medium + + * Add upstream patch to fix FTBFS after we updated SQLAlchemy to fix +CVE-2019-7164 CVE-2019-7548 (SQL injection) (see debian bug 922669 and +929321 for more info) (Closes: #930996). + + -- Thomas Goirand Fri, 28 Jun 2019 15:01:45 +0200 + cloudkitty (8.0.0-4) unstable; urgency=medium * Correct default path to metrics.yml in [collect]/metrics_conf. diff -Nru cloudkitty-8.0.0/debian/patches/Fix_sqlalchemy_grouping_on_v1_storage.patch cloudkitty-8.0.0/debian/patches/Fix_sqlalchemy_grouping_on_v1_storage.patch --- cloudkitty-8.0.0/debian/patches/Fix_sqlalchemy_grouping_on_v1_storage.patch 1970-01-01 01:00:00.0 +0100 +++ cloudkitty-8.0.0/debian/patches/Fix_sqlalchemy_grouping_on_v1_storage.patch 2019-06-28 15:01:45.0 +0200 @@ -0,0 +1,39 @@ +Description: Fix sqlalchemy grouping on v1 storage (Fixes FTBFS in Buster) + This fixes "CompileError: Can't resolve label reference for + ORDER BY / GROUP BY." error messages raised by sqlalchemy when the groupby + expression includes a comma. +Author: Luka Peschke +Date: Tue, 4 Jun 2019 15:21:05 +0200 +Change-Id: Ia253175b45b8222aaee415ea535fa4102312be5a +Bug-Debian: https://bugs.debian.org/930996 +Origin: upstream, https://review.opendev.org/668120 +Last-Update: 2019-06-28 + +diff --git a/cloudkitty/storage/v1/sqlalchemy/__init__.py b/cloudkitty/storage/v1/sqlalchemy/__init__.py +index 77403e3..7b56da6 100644 +--- a/cloudkitty/storage/v1/sqlalchemy/__init__.py b/cloudkitty/storage/v1/sqlalchemy/__init__.py +@@ -127,7 +127,7 @@ class SQLAlchemyStorage(storage.BaseStorage): + self.frame_model.end <= end, + self.frame_model.res_type != '_NO_DATA_') + if groupby: +-q = q.group_by(groupby) ++q = q.group_by(sqlalchemy.sql.text(groupby)) + + # Order by sum(rate) + q = q.order_by(sqlalchemy.func.sum(self.frame_model.rate)) +diff --git a/releasenotes/notes/fix-v1-storage-groupby-e865d1315bd390cb.yaml b/releasenotes/notes/fix-v1-storage-groupby-e865d1315bd390cb.yaml +new file mode 100644 +index 000..02c1e4d +--- /dev/null b/releasenotes/notes/fix-v1-storage-groupby-e865d1315bd390cb.yaml +@@ -0,0 +1,6 @@ ++--- ++fixes: ++ - | ++``CompileError: Can't resolve label reference for ORDER BY / GROUP BY.`` ++errors that were sometimes raised by SQLAlchemy when using the v1 storage ++backend and grouping on ``tenant_id`` and ``res_type`` have been fixed. +-- +2.7.4 + diff -Nru cloudkitty-8.0.0/debian/patches/series cloudkitty-8.0.0/debian/patches/series --- cloudkitty-8.0.0/debian/patches/series 2019-01-24 14:45:39.0 +0100 +++ cloudkitty-8.0.0/debian/patches/series 2019-06-28 15:01:45.0 +0200 @@ -1,3 +1,4 @@ allow-any-sqla-version.patch missing-files.patch remove-mathjax-extention-from-sphinx-doc.patch +Fix_sqlalchemy_grouping_on_v1_storage.patch
Bug#930996: marked as pending in cloudkitty
Control: tag -1 pending Hello, Bug #930996 in cloudkitty reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/cloudkitty/commit/e9d880a5f9885d0660d6bfd7df36ea4a3d762b9e * Add upstream patch to fix FTBFS after we updated SQLAlchemy to fix a CVE (Closes: #930996). (this message was generated automatically) -- Greetings https://bugs.debian.org/930996
Bug#930996: Bug#929321: Update for SQLAlchemy to address CVE-2019-7164 CVE-2019-7548
On 6/27/19 8:39 PM, Paul Gevers wrote: > Hi Thomas, > > On 31-05-2019 01:34, Thomas Goirand wrote: >> Dear package maintainer, >> >> We're about to upgrade SQLAlchemy in Buster to address an SQL injection >> issue. The fixed package is in unstable, under the version 1.2.18+ds1-2. >> >> In some rare cases, this update may break reverse depenencies, leading >> to non-working SQL queries. >> >> This is why I'm writing this email to you today: to ask you to please >> test your application with SQLAlchemy 1.2.18+ds1-2 ASAP, to address any >> potential unforecast issue before the Buster release. >> >> Details about the discussion can be seen here in the Debian bug #929321. >> >> Best regards, > > Is this explaining the FTBFS of cloudkitty? We're looking at all the RC > bugs to see what needs to happen and cloudkitty is about to be removed > due this FTBFS. (I am not promising anything, but if the fix is clear, > we may leave it in an let you fix it in the first point release). > > Paul Hi Paul, Yes, I can try to fix it in the next point release. I very much would prefer if cloudkitty could stay in Buster. Cheers, Thomas Goirand (zigo)
Bug#922669: fixed in sqlalchemy 1.2.18+ds1-2
On 6/1/19 1:40 PM, Hideki Yamane wrote: > Hi, > > Do you file unblock for sqlalchemy? It's already migrated to Buster. > Or also add debian/NEWS file to indicate potential incompatibility for > applications? No, I haven't. However, the risk is just an SQL query not working, and apparently, only in rare edge cases where there's already an issue. Cheers, Thomas Goirand (zigo)
Bug#930050: miniupnpd: CVE-2019-12107 CVE-2019-12108 CVE-2019-12109 CVE-2019-12110 CVE-2019-12111
On 6/6/19 9:38 AM, Salvatore Bonaccorso wrote: > Source: miniupnpd > Version: 2.1-5 > Severity: grave > Tags: security upstream > Justification: user security hole > Control: found -1 1.8.20140523-4.1+deb9u1 > Control: found -1 1.8.20140523-1 > > Hi, > > The following vulnerabilities were published for miniupnpd. > > CVE-2019-12107[0]: > | The upnp_event_prepare function in upnpevents.c in MiniUPnP MiniUPnPd > | through 2.1 allows a remote attacker to leak information from the heap > | due to improper validation of an snprintf return value. > > > CVE-2019-12108[1]: > | A Denial Of Service vulnerability in MiniUPnP MiniUPnPd through 2.1 > | exists due to a NULL pointer dereference in GetOutboundPinholeTimeout > | in upnpsoap.c for int_port. > > > CVE-2019-12109[2]: > | A Denial Of Service vulnerability in MiniUPnP MiniUPnPd through 2.1 > | exists due to a NULL pointer dereference in GetOutboundPinholeTimeout > | in upnpsoap.c for rem_port. > > > CVE-2019-12110[3]: > | An AddPortMapping Denial Of Service vulnerability in MiniUPnP > | MiniUPnPd through 2.1 exists due to a NULL pointer dereference in > | upnpredirect.c. > > > CVE-2019-12111[4]: > | A Denial Of Service vulnerability in MiniUPnP MiniUPnPd through 2.1 > | exists due to a NULL pointer dereference in copyIPv6IfDifferent in > | pcpserver.c. > > > If you fix the vulnerabilities please also make sure to include the > CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2019-12107 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12107 > [1] https://security-tracker.debian.org/tracker/CVE-2019-12108 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12108 > [2] https://security-tracker.debian.org/tracker/CVE-2019-12109 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12109 > [3] https://security-tracker.debian.org/tracker/CVE-2019-12110 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12110 > [4] https://security-tracker.debian.org/tracker/CVE-2019-12111 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12111 > > Please adjust the affected versions in the BTS as needed. > > Regards, > Salvatore > Hi Salvatore and the rest of the security team, I have prepared the Stretch update for the new Stretch update: miniupnpd/1.8.20140523-4.1+deb9u2 The debdiff is attached to this mail. The resulting package is available here on this site: http://sid.gplhost.com/stretch-proposed-updates/miniupnpd/ Please allow me to upload this Stretch update to security-master. As the Jessie version is the same as the Stretch one, I guess the LTS team can just pick-up what's in the git and rebuild. I'd prefer if someone form the LTS team does it, as I'm not familiar with the procedures. Cheers, Thomas Goirand (zigo) diff -Nru miniupnpd-1.8.20140523/debian/changelog miniupnpd-1.8.20140523/debian/changelog --- miniupnpd-1.8.20140523/debian/changelog 2018-02-07 12:18:50.0 +0100 +++ miniupnpd-1.8.20140523/debian/changelog 2019-06-07 09:16:03.0 +0200 @@ -1,3 +1,11 @@ +miniupnpd (1.8.20140523-4.1+deb9u2) stretch-security; urgency=medium + + * Applied upstream patches for CVE-2019-12107, CVE-2019-12108, +CVE-2019-12109, CVE-2019-12110. This version looks like not affected by +CVE-2019-12111. (Closes: #930050). + + -- Thomas Goirand Fri, 07 Jun 2019 09:16:03 +0200 + miniupnpd (1.8.20140523-4.1+deb9u1) stretch; urgency=medium * Apply patch from upstream for CVE-2017-1000494 (Closes: #887129). diff -Nru miniupnpd-1.8.20140523/debian/gbp.conf miniupnpd-1.8.20140523/debian/gbp.conf --- miniupnpd-1.8.20140523/debian/gbp.conf 2014-12-09 15:37:29.0 +0100 +++ miniupnpd-1.8.20140523/debian/gbp.conf 2019-06-07 09:16:03.0 +0200 @@ -1,6 +1,6 @@ [DEFAULT] -upstream-branch = upstream-sid -debian-branch = debian-sid +upstream-branch = upstream-stretch +debian-branch = debian-stretch pristine-tar = True [git-buildpackage] diff -Nru miniupnpd-1.8.20140523/debian/patches/CVE-2019-12107_upnp_event_prepare_check_the_return_value_of_snprintf.patch miniupnpd-1.8.20140523/debian/patches/CVE-2019-12107_upnp_event_prepare_check_the_return_value_of_snprintf.patch --- miniupnpd-1.8.20140523/debian/patches/CVE-2019-12107_upnp_event_prepare_check_the_return_value_of_snprintf.patch 1970-01-01 01:00:00.0 +0100 +++ miniupnpd-1.8.20140523/debian/patches/CVE-2019-12107_upnp_event_prepare_check_the_return_value_of_snprintf.patch 2019-06-07 09:16:03.0 +0200 @@ -0,0 +1,57 @@ +Description: CVE-2019-12107: upnp_event_prepare(): check the return value of snprintf() +Author: Thomas Bernard +Date: Tue, 18 Dec 2018
Bug#929332: marked as pending in ironic-inspector
Control: tag -1 pending Hello, Bug #929332 in ironic-inspector reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/openstack-team/services/ironic-inspector/commit/07b571df2e84514751146e89a6671c73a0b55e0c * CVE-2019-10141: SQL Injection vulnerability when receiving introspection data. Applied upstream fix: Eliminate SQL injection vulnerability in node_cache (Closes: #929332). (this message was generated automatically) -- Greetings https://bugs.debian.org/929332
Bug#922669: Debdiff to fix this
Hi,
Here's, attached to this message, the debdiff to fix this CVE. Note that
the patch was backported to 1.2 by upstream himself, so it's kind of
safe to apply, however, it may potentially impact SQLAlchemy reverse
dependencies. It should be safe for OpenStack applications though.
Please, either allow me to upload as-is, or build and upload yourself
ASAP (preferably, in time for Buster).
Cheers,
Thomas Goirand (zigo)
diff -Nru sqlalchemy-1.2.18+ds1/debian/changelog
sqlalchemy-1.2.18+ds1/debian/changelog
--- sqlalchemy-1.2.18+ds1/debian/changelog 2019-02-25 00:01:50.0
+0100
+++ sqlalchemy-1.2.18+ds1/debian/changelog 2019-05-21 16:23:35.0
+0200
@@ -1,3 +1,11 @@
+sqlalchemy (1.2.18+ds1-2) unstable; urgency=high
+
+ * Team upload.
+ * CVE-2019-7164 CVE-2019-7548: SQL injection. Apply upstream backported patch
+for this. Note: This potentially impacts applications (Closes: #922669).
+
+ -- Thomas Goirand Tue, 21 May 2019 16:23:35 +0200
+
sqlalchemy (1.2.18+ds1-1) unstable; urgency=medium
* New upstream release
diff -Nru
sqlalchemy-1.2.18+ds1/debian/patches/CVE-2019-7164_and_7548_Illustrate_fix_for_4481_in_terms_of_a_1.2_patch.patch
sqlalchemy-1.2.18+ds1/debian/patches/CVE-2019-7164_and_7548_Illustrate_fix_for_4481_in_terms_of_a_1.2_patch.patch
---
sqlalchemy-1.2.18+ds1/debian/patches/CVE-2019-7164_and_7548_Illustrate_fix_for_4481_in_terms_of_a_1.2_patch.patch
1970-01-01 01:00:00.0 +0100
+++
sqlalchemy-1.2.18+ds1/debian/patches/CVE-2019-7164_and_7548_Illustrate_fix_for_4481_in_terms_of_a_1.2_patch.patch
2019-05-21 16:23:35.0 +0200
@@ -0,0 +1,331 @@
+Description: CVE-2019-7164 / CVE-2019-7548: Illustrate fix for #4481 in terms
of a 1.2 patch
+ Release 1.2 has decided (so far) not to backport 1.3's fix for #4481 as it is
+ backwards-incompatible with code that relied upon the feature of automatic
text
+ coercion in SQL statements. However, for the specific case of order_by() and
+ group_by(), we present a patch that backports the specific change in compiler
+ to have 1.3's behavior for order_by/group_by specifically. This is much more
+ targeted than the 0.9 version of the patch as it takes advantage 1.0's
+ architecture which runs all order_by() / group_by() through a label lookup
that
+ only warns if the label can't be matched.
+ .
+ For an example of an application that was actually impacted by 1.3's change
+ and how they had to change it, see:
+ .
+ https://github.com/ctxis/CAPE/commit/be0482294f5eb30026fe97a967ee5a768d032278
+ .
+ Basically, in the uncommon case an application is actually using the text
+ coercion feature which was generally little-known, within the order_by()
+ and group_by() an error is now raised instead of a warning; the application
+ must instead ensure the SQL fragment is passed within a text() construct.
+ The above application has also been seeing a warning about this since 1.0
+ which apparently remained unattended.
+ .
+ The patch includes adjustments to the tests that were testing for the
+ warning to now test that an exception is raised. Any distro that wants
+ to patch the specific CVE issue resolved in #4481 to SQLAlchemy 1.0, 1.1
+ or 1.2 can use this patch.
+Author: Mike Bayer
+Date: Mon, 08 Apr 2019 22:07:35 -0400
+Change-Id: I3363b21428f1ad8797394b63197375a2e56a0bd7
+References: #4481
+Bug-Debian: https://bugs.debian.org/922669
+Origin: upstream,
https://gerrit.sqlalchemy.org/#/c/sqlalchemy/sqlalchemy/+/1184/
+Last-Update: 2019-05-21
+
+diff --git a/lib/sqlalchemy/sql/compiler.py b/lib/sqlalchemy/sql/compiler.py
+index 5a11ed1..4780bab 100644
+--- a/lib/sqlalchemy/sql/compiler.py
b/lib/sqlalchemy/sql/compiler.py
+@@ -757,12 +757,11 @@
+ else:
+ col = with_cols[element.element]
+ except KeyError:
+-# treat it like text()
+-util.warn_limited(
+-"Can't resolve label reference %r; converting to text()",
+-util.ellipses_string(element.element),
++elements._no_text_coercion(
++element.element,
++exc.CompileError,
++"Can't resolve label reference for ORDER BY / GROUP BY.",
+ )
+-return self.process(element._text_clause)
+ else:
+ kwargs["render_label_as_label"] = col
+ return self.process(
+diff --git a/lib/sqlalchemy/sql/elements.py b/lib/sqlalchemy/sql/elements.py
+index 299fcad..ff86deb 100644
+--- a/lib/sqlalchemy/sql/elements.py
b/lib/sqlalchemy/sql/elements.py
+@@ -4432,6 +4432,17 @@
+ )
+
+
++def _no_text_coercion(element, exc_cls=exc.ArgumentError, extra=None):
++raise exc_cls(
++"%(extra)sTextual SQL expression %(expr)r should be "
++"explicitly declared as text(%(expr)r)"
++% {
++"expr": util.ellipses_string(element),
++
Bug#929297: minissdpd: CVE-2019-12106
On 5/21/19 8:06 AM, Chris Lamb wrote: > Package: minissdpd > Version: 1.2.20130907-3+deb8u1 > X-Debbugs-CC: t...@security.debian.org > Severity: grave > Tags: security > > Hi, > > The following vulnerability was published for minissdpd. > > CVE-2019-12106[0]: > | The updateDevice function in minissdpd.c in MiniUPnP MiniSSDPd 1.4 and > | 1.5 allows a remote attacker to crash the process due to a Use After > | Free vulnerability. > > > 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-12106 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12106 > > > Regards, > Hi Chris & the security team, The version in Sid / Buster isn't affected, as version 1.5.20190210 from upstream already has the patch (ie: *pp = p->next). The security tracker seems to know about it already. Chris, thanks for your proposal to update Stretch, I very much appreciate it. Cheers, Thomas Goirand (zigo)
Bug#927722: fixed in ipset 6.38-1.1
On 5/5/19 1:58 PM, Ivo De Decker wrote: > Control: reopen -1 > > Hi, > > On Thu, May 02, 2019 at 10:18:33AM +, Cyril de Bourgues wrote: >>* Non maintainer upload. >>* use dpkg-maintscript-helper rm_conffile to clean up old bash-completion >> file in /etc (Closes: #927722). > > You added > > dpkg-maintscript-helper rm_conffile conffile 6.25.1-1~ ipset -- "$@" > > This is wrong. The 'conffile' argument needs to be the full path of the > conffile you want to remove. The 'ipset' at the end shouldn't be there. > > Thanks, > > Ivo Looks like it took the previous upload I did. I did a dcut and re-uploaded, though the old one got in. I'm fixing and re-uploading (this time without delay). Cheers, Thomas Goirand (zigo)
Bug#927722: fixed in ipset 6.38-1.1
On 5/5/19 1:58 PM, Ivo De Decker wrote: > Control: reopen -1 > > Hi, > > On Thu, May 02, 2019 at 10:18:33AM +, Cyril de Bourgues wrote: >>* Non maintainer upload. >>* use dpkg-maintscript-helper rm_conffile to clean up old bash-completion >> file in /etc (Closes: #927722). > > You added > > dpkg-maintscript-helper rm_conffile conffile 6.25.1-1~ ipset -- "$@" > > This is wrong. The 'conffile' argument needs to be the full path of the > conffile you want to remove. The 'ipset' at the end shouldn't be there. > > Thanks, > > Ivo Which was fixed on the upload (ie: conffile was replaced). Adding "ipset" at the end should work, as that's the name of the package. Or am I wrong there? Cheers, Thomas Goirand (zigo)
