Package: python3-bibtexparser
Version: 1.1.0+ds-5
Severity: normal
Dear,
Please package version 2.0.0b4
and remove dependency on python3-future.
To play nice the reverse-dependedencies should be
checked against this new v2.0 lib:
python3-bibtexparser
Reverse Depends:
Dépend: qiime
Dépen
Source: buildbot
Version: 3.9.2-2
Severity: normal
Dear Maintainer,
python3-future is RC buggy and being removed from Debian.
It looks likes upstream confused "from __future__ import ..." (stdlib)
with "from future import ..." (python3-future)
and that 3.9.2-2 could already be trivaly patched.
Source: python-pefile
Version: please drop extraneous dependency on python3-future
Severity: important
Dear Maintainer,
The obsolete, RC-buggy python3-future library is being removed
from Debian soon.
It seems your package declare a stale
dependency on python3-future.
Can you remove it ?
Greet
Thanks :-)
Source: toil
Version: 5.12.0-2
Severity: important
X-Debbugs-Cc: Noah Meyerhans
I see on #debian-devel-changes that python3-boto is being removed.
I hope it's not a mandatory dependency :-|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058652
https://salsa.debian.org/med-team/toil/-/commi
kout2".
Please remove the old NBS lbreakout2-data.
lbreakout2 is now a transitional package
built by src:lbreakouthd.
Greetings,
Alexandre Detiste
Source: stomper
Version: 0.4.3-2
Severity: important
Dear maintainer,
python3-future is being removed from the archive.
stomper has a totally unneeded dependency on python3-future.
Upstream probably mixed up 'future' and '__future__' back then.
https://github.com/oisinmulvihill/stomper/issues/
Hi,
I ll try to fix this one if you permit.
Greetings
Package: enigma
Version: 1.30+dfsg-1
Severity: normal
This game embeds a local copy of "fonts-wqy-microhei",
which should be removed using Files-Excluded:
in d/copyright.
Makefile would probably needs patching too.
(and +Depends: fonts-wqy-microhei in d/control of course)
-- System Informatio
Source: junitparser
Version: 3.1.0-1
Severity: normal
Dear Maintainer,
python3-future is being removed from Debian.
The one stale reference upstream has been removed in Septembre
but there hasn't been a release yet.
https://github.com/weiwei/junitparser/commit/7712f6261b1b1e4f931fb2155f4cba9be1
+ install_requires=['six'],
https://github.com/google/textfsm/pull/116/files
PS: another day python3-six will be gone too,
but I don't want to waste time with an CLA
upstream for such trivial thing.
Alexandre Detiste
-- System Information:
Debian Release: trixie/sid
Source: bioxtasraw
Version: 2.2.1-1
Severity: normal
Dear Maintainer,
python3-future is buggy and will be removed from Debian
"bioxtasraw" declares a totally extraneous dependency on "future"
(they want "__future__" not "future").
A copy of the needed patch has already been proposed upstream:
Source: pyferret
Severity: important
Dear Maintainer,
python3-future is buggy and not anymore compatible with python3.12,
it will be removed from Debian soon.
The good thing is that pyferret doesn't use it at all.
"from __future__" was commonly confused with "from future".
So hereunder is al
This is really bad because it also breaks unattended-upgrades,
so I guess the only way out is to run "apt upgrade" by hand
(after it's fixed) on each impacted system.
Package: numptyphysics
Version: 0.3.10-0.2
Severity: normal
X-Debbugs-Cc: debian-devel-ga...@lists.debian.org
This game embbed a possibily outdated/buggy version of Box2D.
Box2D is already packaged and used by LibreOffice and CaveExpress.
Please try to build & run the game with this shared libra
Le sam. 16 déc. 2023 à 15:46, Lisandro Damián Nicanor Pérez Meyer
a écrit :
> The cleanest way is to use CMake, as it can handle this directly in
> code. And I guess qmake will probably not be a thing for Qt 7.
>
Thanks. This just works(TM) for two packages.
control: severity -1 serious
I think until the licensing problem is not resolved,
this old version of the game should not be included in a release.
Source: rocketcea
Severity: minor
The Sphinx documentation should be regenerated
and not taken as-is from the upstream tarball.
Source: python-ipmi
Severity: important
python3-future is not compatible with Python3.12
and will soon be removed from the archive.
luckily it's merely a (quite common) mistake from
upstream.
Here's the simple fix.
--- a/setup.py
+++ b/setup.py
@@ -70,6 +70,5 @@ setup(name=name,
test_sui
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-twit...@packages.debian.org,
debian-devel-ga...@lists.debian.org
Control: affects -1 + src:python-twitter
I'm lazy at time so I just copied the text from #1056614:
>This packa
Source: python-x2go
Version: 0.6.1.3-3
Severity: normal
Dear Maintainer,
python3-future has outlived it's usefullness, is unmaintained
and is incompatible with Python 3.12.
Please make sure it is removed from d/control too.
debian/control: python3-future,
A patch with further cleanup has be
here is a patch that removes extraneous import of future library
& most likely solves this bug
diff --git a/debian/control b/debian/control
index c3fa5b6..12b2535 100644
--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,7 @@ Build-Depends: debhelper-compat (= 13),
dh-python,
The patch submitted upstream also removes extraneous unittest2
https://github.com/sangwonl/python-mpegdash/pull/61/files
Source: python-ldapdomaindump
Version: 0.9.4-1
Severity: important
Dear Maintainer,
python3-future breaks with Python3.12 and is now being removed from Debian.
As of today, the top commit on upstream git fixes it:
https://github.com/dirkjanm/ldapdomaindump/commit/f77193450b6e69584163cd151fc4e2
Package: pre-commit
Version: 3.6.0-1
Severity: normal
Dear Maintainer,
python3-importlib-metadata provides "importlib_metadata"
which is a backport of "importlib.metadata" from the standard library.
pre-commit is modern, fast moving tool, it only uses "importlib.metadata".
"importlib_metadat
Source: logilab-common
Version: please make sure python3-import-metadata is not pulled in
Severity: 1.9.8-1
Dear Maintainer,
Your package is pulling in python3-importlib-metadata
that has no real purpose anymore since release of Python 3.8.
Please ensure this dependency is removed.
Shipping 2.0
Source: python-quantities
Severity: normal
python3-unittest2 was a backport of Python3's unittest to Python2.
It has very littles usage left.
It will be removed soon from Debian.
Greetings,
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'),
Source: neo
Severity: normal
python3-unittest2 was a backport of Python3's unittest to python.
"neo" is now using the real thing.
Please remove the override from debian/control.
Greetings
Source: hdmf
Severity: normal
Dear Maintainer,
You package has an obsolete Build-Dep on "python3-unittest2"
which was a backport of Python3's unittest to Python2.
Please remove it.
Upstream is now using the real thing.
Greetings,
Source: pynwb
Version: 1.2.1-2
Severity: normal
Unittest2 was a backport of Python3's standard "unittest" to Python2.
Upstream is now using the real thing,
please remove this overide from debian/control.
Greetings,
Source: python-biopython
Severity: normal
Dear Maintainer,
python3-unittest2 was a backport of Python3's standard "unittest" to Python2.
Upstream is now using the real thing.
Please remove the override from debian/control.
Greetings,
Source: python-graphviz
Severity: normal
Dear Maintainer,
python3-unittest2 was a backport of Python3's "unittest" to Python2.
Upstream has switched to use the real thing.
Can you please remove the references in:
d/control
d/test/control
Greetings
Source: xrayutilities
Severity: normal
python3-unittest2 was a backport to Python2 of the standard "unittest" Python3.
Please remove if from the Build-Depedencies of your package
so it can late be removed from the archive.
Greetings
Source: pgxnclient
Severity: normal
Dear Maintainer,
python3-unittest2 was a backport of Python3's "unittest"
module to Python2.
Upstream is now using the real "unittest".
Please remove the reference from debian/control.
Greetings
Source: python-yarg
Severity: normal
Dear Maintainer,
"unittest2" was a backport of Python 3's "unittest" to Python2.
It was usefull a long time ago.
Now upstream is using the real thing from the standard library.
Please remove it from d/control.
Greetings,
(PS: please also check python3-mo
Source: recon-ng
Severity: normal
Hi,
"unicodecsv" is a remnant of the Python2 era.
It should eventualy be removed from Debian.
It is also holding off the removal
of other old module "unittest2".
Please consider this patch:
diff --git a/debian/control b/debian/control
index e3fccf0..c87f5f1
Source: python-rsa
Severity: normal
Dear Maintainer,
python3-unittest2 is an old backport of Python3 code to Python2.
It is being removed from Debian.
Please remove it from you debian/control.
Upstream has already moved away:
$ grep
debian/control: , python3-unittest2
CHANGELOG.md:- Removed
Source: python-pyftpdlib
Version: 1.5.7-3
Severity: important
Dear Maintainer,
python3-unittest2 is/was a backport of Python3 standard library "unittest" to
Python2.
There are still some 'crumbs' of it floating in the repository,
but nothing unpatchable.
Hopefully Upstream would have cleaned u
Source: python-unicodecsv
Version: 0.14.1-7
Severity: normal
Dear Maintainers,
First thanks I use this package a lot on my Wheezy ... computers at work.
It is now almost not needed anymore on Debian,
but it's only of removal of other outdated package "python3-unittest2".
More generaly users
Source: python-jedi
Severity: important
Dear Maintainer,
python3-unittest2 was a backport of Python3 "unittest" to Python2.
Upstream now uses the real thing.
Please drop the old stale dependency from your package:
$ grep unittest2 -r
debian/control: python3-unittest2,
Greetings
Source: python-googleapi
Version: 1.7.12-1
Severity: normal
Dear Maintainer,
The libraries python3-six & python3-unittest2 once helped
to maintain Python2+3 billingual codebases but are now EOL.
Can you please consider consider the new 2.x release
and see if these can be removed from debian/con
Source: python-ciso8601
Severity: normal
Dear Maintainer,
python3-unittest2 was a port of Python3 "unittest" to Python2.
It has now no purpose and it's being removed from Debian.
Please remove it from debian/control.
Upstream has moved away a long time ago.
Greetings
Source: pyclipper
Severity: normal
Dear Maintainer,
python3-unittest2 is being removed from Debian
it was a backport of "unittest" to Python2.
Upstream source will handle this just fine,
one only need to tweak debian/control.
Upstream (old but ok):
>try:
> from unittest2 import TestCase, main
Source: nwdiag
Version: 2.0.0+dfsg-1.1
Severity: normal
Dear Maintainer,
python3-unittest2 is being removed from Debian.
It was a backport of Python3 "unittest" to Python2
It may have been used by Upstream project ... before.
It can now safely be removed from debian/control.
Greetings
$ gre
Source: h5py
Severity: normal
Dear Maintainer,
python3-unittest2 is obsolete: it was an
old backport of Python3's "unittest" to Python2.
Upstream does not use at all it anymore.
Please remove it from "debian/control" & "debian/tests/control",
so this library can be removed from Debian.
Greetin
Source: gitinspector
Severity: normal
Dear Maintainer,
I see that the whole Python3 port is carried as a patch
"port-to-python3.patch".
Could this patch be reworked to use plain 'unittest' from
the standard library instead of old fork
'python3-unittest2' ?
The goal is to remove python3-unittest
Source: flake8-noqa
Severity: normal
Dear Maintainer,
python3-unittest2 is being removed from the archive.
It was a backport of Python3's "unittest" to Python2.
Upstream is already using the real 'unittest'.
Greetings,
flake8-noqa $ grep unittest -r
test.py:import unittest
test.py:class
Source: blockdiag
Severity: normal
Dear Maintainer,
python3-unittest2 is being removed from the archive.
It was a port of Python3's "unittest" to Python2.
Your package hasn't required it for a long time.
Please remove it from debian/control.
Greetings
I've filled 20-something bugs to task to remove extraneous Build-Dependency.
Follow up next year :-)
Source: radon
Version: 5.1.0-2
Severity: normal
Dear Maintainer,
The library python3-future is buggy/unmaintained and is being
removed from Debian. Luckily your project don't really need it:
It seems packaging v6 is enough to solve this:
https://github.com/rubik/radon/pull/234
Greetings
Alexa
Source: scikit-rf
Version: 0.15.4-2.1
Severity: normal
Hi,
v0.15 requires python3-future which is now being removed
from the archive, please package v0.30.0
https://github.com/scikit-rf/scikit-rf/releases/tag/v0.30.0
Greetings,
Alexandre
Source: turing
Severity: normal
Dear Maintainter,
Please remove "python3-future" from debian/control;
your package will cope just fine.
python3-future is an old python2>3 transaltion layer
that is now being removed from Debian.
>try:
>from future.builtins import str, super
>except:
>#
Source: grapefruit
Severity: normal
python3-future is an old Python2 -> 3 translation layer.
It does not build with Python 3.12
90% of the packages dependy on it are like this one:
one just need to remove one or two lines from d/control;
(or maybe also patch setup.py).
So that's what I ask you
Source: pyhamtools
Severity: normal
Dear Maintainer,
python3-future is buggy with Python 3.12 and is being
removed from Debian.
Upstream website states they want to drop Py2.7 support "in 2023".
I've created an issue to activate this plan.
https://github.com/dh1tw/pyhamtools/issues/26
Even if
Source: flask-autoindex
Version: 0.6.6-3
Severity: important
Forwarded: https://github.com/general03/flask-autoindex/issues/71
Dear Maintainer,
by using python3-future, your project is not compatible with Python3.12.
This issue is already tracked upstream at:
https://github.com/general03/flask-
control: severity -1 important
Dear Maintainer,
python3-future is RC buggy and will likely be removed
soon from the archive.
Updating to at least 0.22 solves this issue.
Please also remove " python3-future ," form debian/control.
Greetings,
## [0.22.0] - 2023-10-6
### Miscellaneous Tasks
-
Here is the patch.
It's just about hacking out the referencesto python3-future.
Greetings
python-lzstring $ git diff
diff --git a/debian/control b/debian/control
index 727100d..1d1d4aa 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,6 @@ Build-Depends: debhelper-compat (= 13),
SER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
>From ee30a679fec81221352445e1e09f0a7e4947c955 Mon Sep 17 00:00:00 2001
From: Alexandre Detiste
Date: Wed, 20 Dec 2023 10:27:
Source: python-arabic-reshaper
Severity: important
Dear Maintainer,
Your package has an extraneous dependency on python3-future.
This package is RC buggy and will be removed from Debian soon.
Here's a patch to solve this.
Please forward it upstream.
Most of the time people mixed up 'from __fu
Source: python-pattern
Severity: important
python3-future is RC buggy with Python3.12 and being removed
from the archive.
Hopefully it's not required at all anymore by your package.
Please consider this patch to remove it.
Greetings,
Alexandre
diff --git a/debian/control b/debian/control
ind
control: tag -1 +patch
Hi,
Here's a patch.
Greetings
From a2dfc8434492368b4e299411c97f0f2aecab8e80 Mon Sep 17 00:00:00 2001
From: Alexandre Detiste
Date: Wed, 20 Dec 2023 10:54:16 +0100
Subject: [PATCH] fix FTBFS with Py3.12
---
debian/control
Source: python-pysaml2
Version: 7.2.1-2
Severity: important
Dear Maintainer,
python3-future is now buggy with Python3.12 and will be removed
from the archive soon.
Please remove this extraneous dependency from your package.
This can either be done now on top of 7.2.1
or later on top of 7.4.2.
Source: gnocchi
Severity: important
python3-future is RC buggy and being removed from the archive
please remove the hardcoded dependencies in debian/control
to help untangle this removal.
Greetings,
tchet@brix /tmp/gnocchi $ grep future -r | grep -v __future__
setup.cfg:futures; python_ve
control: tag -1 +wontfix
control: tag -2 +wontfix
Patches have been provided to all reverse dependencies.
Please don't loose time trying to fix this _huge_ one;
fix the reverse dependencies instead.
(it's more tedious, but still easier)
Greetings
The actual culprit is python3-future which won't be fixed.
Please patch-out it's usage or see if it's already done upstream.
Greetings
$ grep future -r | grep -v __future__
setup.py: install_requires = ['numpy', 'future'],
mdp/utils/templet.py:from future.utils import with_metaclass
md
Source: plaso
Version: 20201007-2
Severity: important
python3-future is RC buggy and being removed.
please remove the 2 extraneous dependencies declared in debian/control.
Greetings
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'u
Source: chirp
Severity: important
both upstream & debian packaging declare
an old stale extraneousdepency on python3-future.
This lib is RC buggy and being removed.
Please remove these references.
$ grep future -r
test-requirements.txt:future
setup.py: 'future',
requirements.txt:futur
Today's 2.9.0 release completes the port to SDL2.
Happy gaming
Hi Helmut.
Xaos started this Qt6/QMake6 discussion and turned out to be a good testbed
for checking debhelper versus Qt6 compatibility.
A someone pointed out (sorry cannot find his name browsing on the phone),
the generic first thing to try would be to try CMake instead.
But I don't want to depr
Hi,
I have briefly discussed the situation of the Scummvm plugin
with Simon last month in Cambridge.
We agreed that there is too much intelligence in the generated, "unfixable"
(unless someone takes the time to repack the game), generated .deb's;
and that some or most of this intelligence should
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: chausse...@packages.debian.org, David Douard
Control: affects -1 + src:chaussette
Dear Maitainer, FTP-Masters,
I was thinking of preparing a NMU to help python3-unittest2 removal,
bu
Source: dfvfs
Version: 20201219-1
Severity: normal
A new version has been published recentyl online.
https://github.com/log2timeline/dfvfs
Just a little reminder in the absence of working d/watch.
(I'm interrested on updating "plaso" that depends on dfvfs).
Greetings
-- System Information:
S'il vous plaît.
Package: lepton-eda
Severity: minor
This does not looks like a metapackage.
Maybe this is an holdover from ancient times.
Greetings,
Alexandre
Source: python-mock
Severity: normal
Upstreams should have already migrated to STDLIB unittest.mock
a long time ago... this is only a old leftover from Python2 era.
This is a tracker to identify stragglers.
At the end of the way this RM will be forwarded to ftp-masters.
Greetings,
Source: python-future
Severity: normal
python3-future is not comptible with Python 3.12
This bug is tracker to help fix package that still
depends on python3-future.
(mostly obsolete info in setup.py or debian/control)
g=1059934
(list is not complete)
There might be some nmu needed too if maintainers don't react.
@Vincent: this one package "gtextfsm" is yours
do you green light an upload ?
Greetings,
https://salsa.debian.org/python-team/packages/gtextfsm/-/pipelines/621238
gtextfsm $
Source: dioptas
Version: 0.5.2-4
Severity: normal
python3-future was a compatibility layer that enabled to have both
python2 & 3 compatibility with the same codebase.
It is not compatible with Python3.12 and is being removed from the archive.
Your package use it only on a single line that could
Source: toil
Severity: normal
python3-future is RC buggy and being removed from the archive.
It is still in debian/control but not needed anymore by upstream.
Please remove this stale reference.
Greetings,
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (
Source: plip
Severity: normal
python3-future is RC buggy and being removed from the archive.
Source: cnvkit
Severity: normal
python3-future is an obsolete, RC-buggy, library
that is being removed from the archive.
Greetings
Source: python-biom-format
Severity: normal
python3-future is an obsolete library that is now RC buggy with python 3.12
please remove it from debian/control
Greetings
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400
Source: biomaj3-core
Severity: normal
python3-future is RC buggy and being removed from the archive,
please remove it's reference from debian/control.
Greetings,
Source: rows
Severity: normal
Forwarded: https://github.com/turicas/rows/pull/367
Dear Maintainer,
"python3-unicodecsv" is a remnant of the python2+3 dual suppor codebasese.
It depends on another package being itself removed too: "python3-unittest2"
Both are now builtin in the Python3 standard
Source: python-bioblend
Severity: important
Dear Maintainer,
The obsolete python3-boto library is being removed from the archive.
Please remove the extraneous, stale, reference in debian/control.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058652
CHANGELOG.md-
CHANGELOG.md-* Added depen
Package: qgis
Version: 3.28.14+dfsg-1
Severity: normal
Dear Maintainer,
Upstream is still using the old (python3-)mock in a single place:
> python/testing/mocked.py:import mock
It as switched elsewhere to unittest.mock (stdlib).
python3-mock is unmaintained and will be removed some day.
The
Source: python-django-pyscss
Version: 2.0.3-1
Severity: normal
Tags: ftbfs
This is the last thing pulling python3-six in.
The implentation of this inside six.py is quite straitforward:
if PY3:
def u(s):
return s
Less is more
Greetings
-- Forwarded message -
De : Carsten Schoenert
Date: dim. 17 mars 2024 à 08:19
Subject: #1066146 RM: flask-basicauth (Re: morph's abandoned packages (list))
To:
Hi,
Am 16.03.24 um 18:37 schrieb Alexandre Detiste:
> Hi,
>
> The arguments to remove flask-basicauth
Source: hyperkitty
Version: 1.3.7-1
Severity: normal
HyperKitty has switched to "unittest.mock" from
the standard library since 1.3.6.
python3-mock is now being slowly removed from Debian.
Greetings
This one is dead upstream too... it should be removed.
https://qa.debian.org/popcon.php?package=python-ppmd
"This repository has been archived by the owner on Apr 14, 2022. It is
now read-only."
Source: python-certbot-dns-rfc2136
Version: 2.9.0-1
Severity: normal
Dear Maintainers,
"mock is now part of the Python standard library,
available as unittest.mock in Python 3.3 onwards."
https://github.com/testing-cabal/mock
So please remove python3-mock from the build-dependencies.
As an ext
Source: python-rioxarray
Version: 0.15.1-2
Severity: normal
Dear Maintainers,
"mock" has been integrated into the python standard library as "unittest.mock".
Please remove the stale reference in dd/control.
This projects uses the new unittest.mock.
Greetings
python-rioxarray $ grep mock -r
d
Source: matrix-synapse
Version: 1.100.0-1
Severity: important
"mock" was merged into the standard library as "unittest.mock"
years ago.
Please remove the extranoues python3-mock build dependency.
Greetings,
Alexandre Detiste
Source: click
Version: 0.5.2-1
Severity: normal
Dear Maintainer,
It turns out the old python3-mock build dependency is
now also extraneous and should be removed from d/control.
This software will prefer the newer unittest.mock
from the standard library.
Greetings
(I didn't knew about this when
Source: opensnitch
Version: 1.5.8.1-1
Severity: normal
python3-six is an obsolete python2+3 transilition layer
that was once use by opensnitch.
Please remove the leftover reference from d/control.
Greetings
tchet@brix /tmp/opensnitch $ grep six -r
debian/control: python3-six,
tchet@brix /tmp
Source: kraft
Version: 1.1-1
Severity: important
Dear Maintainer,
It seams "six" was used during the Py2->3 transition,
but it's not used anymore by "kraft".
May you please remove the leftover reference in d/control ?
Greetings,
Alexandre
tchet@brix /tmp/kraft $ grep six -r
debian/changelog
Source: python-releases
Version: 1.6.3-2
Severity: normal
Dear Maintainer,
Please upgrade this package to 2.x to allow for python-invoku upgrade.
Alternatively you can swap the contents of the Maintainer: & Uploaders:
fields and let the team handle this. (*)
A third option is to green light me
I dug more:
The original ITP states it was a hard dependency of "rich".
Now 'rich' does all that and more all by itself.
(and more importantly is maintained)
Sure, please help if you want, I've granted you access to
https://salsa.debian.org/python-team/packages/mu-editor/
to salvage this package.
For long temps maintainer ship it's better
to either join Python Team or adopt package.
Greetings
Source: python-karborclient
Version: 2.1.0-3
Severity: wishlist
Maybe this package should be removed some day, I don't know.
I use this ticket to track python3-six & python3-mock removal TODO's;
please keep it open.
Greetings,
-
https://opendev.org/openstack/karbor/src/branch/master/READM
701 - 800 of 1482 matches
Mail list logo
