Thanks :-)
kout2".
Please remove the old NBS lbreakout2-data.
lbreakout2 is now a transitional package
built by src:lbreakouthd.
Greetings,
Alexandre Detiste
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
control: tag -1 +fixed-upstream
the SDL2 remake "lbreakouthd" is already packaged
and lbreakout2 is unmaintained upstream
(and this freeze bug is really annoying).
I think lbreakout2 can be removed.
When ?
Should src:lbreakouthd provide a transition helper ?
Greetings
control: tag -1 +wontfix
This bug is really annoying indeed.
Can you please try out the lbreakouthd remake/following ?
As the old lbreakout2 is unmaintained upstream,
there is very little chance that this bug ever get fixed.
Thus tagging accordingly "wontfix".
Greetings
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.
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:
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,
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: 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.
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
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-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
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: 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
$
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
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: 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: 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-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
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-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: 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
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
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".
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: 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-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
I've filled 20-something bugs to task to remove extraneous Build-Dependency.
Follow up next year :-)
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: 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
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
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
The patch submitted upstream also removes extraneous unittest2
https://github.com/sangwonl/python-mpegdash/pull/61/files
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,
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
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:
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.
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),
YPE=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:52 +0100
Subject: [PATCH] remove
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,
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',
Today's 2.9.0 release completes the port to SDL2.
Happy gaming
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 | 3
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
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;
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
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
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.
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
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
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.
Hi,
I ll try to fix this one if you permit.
Greetings
'],
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
APT prefers testing
APT policy: (501
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
Hi,
Can this go in section "oldlibs" instead of the default "python" ?
There are a lot of old libs in python
slated for removal that are hard to track:
zombie-imp, six, future, unittests2
And many undecided override requests;
--buildsystem=qmake6 is perfect
Le lun. 11 déc. 2023, 18:32, Sune Stolborg Vuorela a écrit :
> > > +1 from me. qtchooser is no longer supported for Qt >= 6, so going
> > > this way is just awesome.
> >
> > Many thanks
> > to Helmut for this.
>
> Agreed. Both to approach and to thanks to Helmut
Debian,
Alternatively I publish a Ubuntu PPA here:
https://launchpad.net/~alexandre-detiste/+archive/ubuntu/ppa/+packages
The _releases_ also trickle also in RPMFusion add-on for Fedora.
(RPMFusion is even in worse shape than EPEL ...)
> (Alternatively, feel free to provide a patch resp. merg
Source: emperor
Version: 1.0.3+ds-7
Severity: normal
python3-future is deprecated and being removed from the archive.
Please use attached patch to remove it from the packaging
Please check with upstream to update setup.py
Greetings,
Alexandre Detiste
-- System Information:
Debian Release
Source: python-tuspy
Version: 1.0.0-2
Severity: normal
Upstream has removed usage of python3-future in git.
I proposed a supplementary PR to also remove usage of python3-six.
https://github.com/tus/tus-py-client/pull/90
Greetings,
-- System Information:
Debian Release: trixie/sid
APT
Source: biomaj3
Version: 3.1.23-1
Severity: normal
Dear Maintainers,
This package depends on on Python2->3 transition helper
"python3-future" which has now outlived it's usefulness.
Please remove it's use.
A MR has been submitted upstream to help remove it
and more old Python2 constructs.
Source: graphite2
Version: 1.3.14-1
Severity: important
Dear Maintainer,
The old transition layer python3-future is problematic
and now fails to build with Python 3.12 with 2 RC bugs.
Your package has an old stale dependency on this package.
Please patch-it out to ease python3-future removal.
I have no idea how to do that.
You can MNU it from tomorrow (or the next day?)
and I'll import the changes in git.
Greetings
unshield (1.4.2-1 to 1.5.1-1)
Maintainer: Debian Games Team
Migration status for unshield (1.4.2-1 to 1.5.1-1): Waiting for
test results or another package,
Package: python3-mido
Version: 1.2.10-1
Severity: minor
Dear Maintainer,
I'm doing an archive-wide review of old Python2.7/six/future
that needs a cleanup either in the archive of upstream.
(some things broke with Py3.12)
This package only need a refresh.
> Important
> Removed support for
Source: picopore
Severity: important
Hi,
Upstream mistakenly declares a dependency on `future`
(`from __future__`doesn't need `future).
> setup.py: install_requires=['h5py>2.2.0','watchdog','future'],
> requirements.txt:future
Can you please patch these out and rebuild the package ?
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: qgis
Version: 3.28.13+dfsg-1
Severity: normal
Hi,
Alike python3-six, at a time, python3-future was a
library that helped writing billingual Python2+3 codebases.
I don't see any usage of python3-future.
Please remove it from the dependencies.
("from __future__ import ..." was
Please Recommends: dosbox-x in the metadata
& the free-text Description:
Greetings
Package: ycmd
Version: 0+20230611+git3392251+ds-2
Severity: normal
Dear Maintainer,
It looks like your package has an obsolete, extraneous
dependency on python3-future.
python3-future was a library that helped maintain
python2+3 billingual codebase.
It is now obsolete and mostly unmaintained.
Package: game-data-packager
Version: 76
Severity: wishlist
Tags: newcomer
For games with a 1:1 relationsheep between the free engine
and non-free data, an autogenerated .xml might
of little value or even annoying.
But it could be of great use for a generic engine like ScummVM.
Of course
Hi,
Le sam. 9 déc. 2023 à 07:53, Sebastiaan Couwenberg
a écrit :
>
> qgis has some dependencies for the sake of plugins which cannot pull in
> dependencies on their own.
>
> Are there plans to remove python3-future from Debian or it being
> deprecated upstream?
There's no plan yet.
The default
Package: python3-pygame-sdl2
Version: 8.0.2-2+b1
Severity: normal
This package embeds a copy of a standard font.
It already depends on fonts-dejavu-core.
It's just missing a symlink or something
+ testing.
-- System Information:
Versions of packages python3-pygame-sdl2 depends on:
ii
Source: python-cobra
Version: 0.26.3-2
Severity: important
Dear Maintainers,
python3-future is buggy and being removed out of Debian.
Your package declares an hardcoded dependency in d/control.
Current /setup.cfg also declare such dependency,
so it's better to first try to update to 0.29.
Source: duplicity
Version: 1.2.2-2
Severity: normal
The python3-future library is being removed from Debian:
it is unmaintained upstream & obsolete
and didn't build with Python 3.12.
duplicity is the top 1 remaining user of python3-future
Please package a new version of duplicity.
Greetings,
I'm missing some piece of the puzzle indeed,
we need Gantt chart or something
of the features we want and the missing pieces to get there.
We can still fix the ScummVM problem on the side.
That would mean generating 200-something
dormant .desktop files at build time ?
Unlike
Source: django-q
Version: 1.3.9-5
Severity: important
The python3-future is an old temporary solution
to have a billingual Python 2 + 3 codebase.
django-q doens't need it at all anymore.
The removal of python3-future is being investigated,
so please remove your package from the list to fix :-)
Source: multiqc
Severity: normal
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maintainers,
Your package's setup.py declares an extraneous
dependency on old compatibility layer python3-future.
> setup.py:"future>0.14.0",
But it doesn't need it at all:
no import of "past" or
everything still works.
Greetings,
Alexandre Detiste
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.5.0-5-amd64 (SMP w/2 CPU
Le lun. 11 déc. 2023 à 17:02, Jochen Sprickerhof a écrit :
> I think the right thing here is to package the new uncertainties version
> which drops the past import:
>
> https://github.com/lebigot/uncertainties/releases/tag/3.1.7
+1
> Also we should probably get rid of python-future at some
Source: galpy
Version: 1.8.1-2
Severity: important
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maintainer,
The removal of the python3-future library is being evaluated.
It's obsolete & unmaitained upstream.
Your package seems not to have required python3-future for a long time.
Please
Source: impacket
Severity: important
X-Debbugs-Cc: debian-pyt...@lists.debian.org
Dear Maitainer,
Upstream mistakenly added 'future' to the requirements in setup.py
Maybe they tought it was needed to get the
"from __future__ import ..." statements working.
That would had been "from future
It's officially stated in the upstream changelog:
## [v1.3.1](https://github.com/koed00/django-q/tree/v1.3.1) (2020-07-02)
[Full Changelog](https://github.com/koed00/django-q/compare/v1.3.0...v1.3.1)
--
- How is logging handled [\#209](https://github.com/Koed00/django-q/issues/209)
- ask
Source: insilicoseq
Severity: important
Dear Maintainers,
The removal of old unmaintained python3-future is being investigated.
A quick review of your package show stale references to "future" in:
- setup.py
- debian/control
Please patch them out and also report setup.py upstream.
Greetings,
Source: pyxnat
Severity: normal
Dear Maintainers,
python3-future is being removed from Debian.
The current sources still contain stales references to "future".
These have been removed upstream since,
so any new release would also fix the problem.
Greetings
$ grep future -r
setup.py:
control: tag -1 +patch
I'm checking the code in my previous fork !
So this PR first need to be applied.
https://github.com/pyxnat/pyxnat/pull/179
This can be used as a temporary patch
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,
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
Hi,
I'm systemd-cron maintainer.
It does indeed says in the manual
"One ... can't use systemd-cron to launch long lived forking daemons."
Robert Clay looks MIA,
I will prepare an upload that adds a proper .timer + service
for this package + a bit more cleaning.
Greetings,
Package: weechat-matrix
Severity: normal
Hi,
I stumbled over this disclaimer upstream:
> However, due to some inherent limitations of Weechat scripts,
> development has moved to weechat-matrix-rs, a Weechat plugin written in Rust.
> As such, weechat-matrix is in maintenance mode and will likely
ttps://qa.debian.org/popcon-graph.php?packages=python3-pygame-sdl2+renpy_installed=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1
Greetings,
Alexandre Detiste
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: e...@packages.debian.org, Gilles Dubuc
Control: affects -1 + src:exam
Dear FTP Masters behind the curtain.
I stumbled on this package when reviewing the tasks
needed for
901 - 1000 of 1365 matches
Mail list logo
