On Sat, 26 Sep 2020 10:34:04 +0200 Matthias Klose wrote:
please stop spreading fud. this message is full of wrong assumptions and
spreading fud.
> Matthias Klose wrote:
>> there are *no* packages in testing depending on python.
running unstable is not recommended, and there are no security updates in a
dependency package.
> Wouldn't it at least be possible to get some mass-bug-filing against
> all packages that depend strictly on "python" or any other of the no
> longer built packages, asking them to simply add the "2" as an
> intermediate solution (till they'll anyway need to migrate to 3)?
These are filed, and I'm not repeating what was communicated on the
debian-python ML. So please just stop it.
when trying to remove the removed python package from my testing system,
109 programs are to be deleted, those:
sudo apt remove python
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Die folgenden Pakete wurden automatisch installiert und werden nicht mehr
benötigt:
grub2-theme-mint python-hamcrest python-matplotlib2-data
Verwenden Sie »sudo apt autoremove«, um sie zu entfernen.
Die folgenden Pakete werden ENTFERNT:
android-tools-fsutils debian-system-adjustments fgo fslint gimp-python
gnome-doc-utils gst-entrans libgcj-common mintupdate-debian ndisgtk
nemo-compare pyside-tools python python-asn1crypto python-astroid
python-backports.functools-lru-cache python-beautifulsoup python-brlapi
python-bugbuddy python-colorama python-configobj python-constantly
python-cryptography python-cssselect python-debianbts python-defer
python-distlib python-dnspython python-ecdsa python-enum34 python-feedparser
python-gconf python-gdata python-glade2 python-gmenu python-gnome2
python-gnomekeyring python-gnupginterface python-gst0.10 python-gtk2
python-gtksourceview2 python-html5lib python-imaging python-ipaddress
python-isodate python-isort python-keybinder python-lazy-object-proxy
python-libdiscid python-matplotlib python-nevow python-notify python-ntdb
python-openssl python-paramiko python-parted python-pexpect python-ptrace
python-ptyprocess python-pyasn1 python-pyasn1-modules python-pyatspi
python-pygoocanvas python-pyinotify python-pyorbit python-pyside.qtcore
python-pyside.qtdeclarative python-pyside.qtgui python-pyside.qthelp
python-pyside.qtnetwork python-pyside.qtopengl python-pyside.qtscript
python-pyside.qtsql python-pyside.qtsvg python-pyside.qttest
python-pyside.qtuitools python-pyside.qtwebkit python-pyside.qtxml
python-pyside2uic python-pysimplesoap python-qt4 python-qt4-gl python-rdflib
python-serial python-service-identity python-singledispatch python-sip
python-subprocess32 python-support python-talloc python-twisted
python-twisted-core python-twisted-web python-webencodings python-webkit
python-webob python-wnck python-wrapt python-wxgtk3.0 python-wxversion
startupmanager youtube-dl
so saying that "there are *no* packages in testing depending on python"
seems to be incorrect at least ... and calling this "FUD" or asking to
stop this is not helpful either.
If I don't want to loose significant functionality, I cannot remove the
python package, and as such python2 2.7.18-2 and python2-minimal
2.7.18-2 cannot be installed / upgraded. The reason for this is that the
python package depends on python2 (= 2.7.17-2) and libpython2-stdlib (=
2.7.17-2), python-minimal depends on python2-minimal (= 2.7.17-2), and
likewise libpython-stdlib depends on libpython2-stdlib (= 2.7.17-2) -
watch the "=", NOT ">=". So what should I do?
Apparently you delivered python/python-minimal/libpython-stdlib packages
that depend only on exactly version 2.7.17-2. Than you removed this
package from debian repositories, and added the "last" version 2.7.18-2,
that cannot be installed on any testing system. The correct thing to do
would be to deliver python/python-minimal/libpython-stdlib packages that
depend on (>= 2.7.18-2) *before* removing these packages.
Heinz
