If the package is gone, but it was the only manually installed package to get Python, then the whole Python distribution becomes auto-removable, unless people manually mark the python2 and/or python3 as manually installed.
Many people will just find out that they don't have python support anymore, even though they installed python manually in the past. There should have been some change log to notify people about this change and the needed manual intervention. On Wed, Sep 16, 2020 at 4:50 AM Matthias Klose <[email protected]> wrote: > Control: severity -1 important > Control: merge -1 970375 > > On 9/16/20 3:45 AM, Koutheir Attouchi wrote: > > Package: python > > Version: 2.7.17-2 > > Severity: grave > > Justification: renders package unusable > > X-Debbugs-Cc: [email protected] > > > > Dear Maintainer, > > > > What led up to the situation? > > > > ``` > > $ sudo apt-get install python > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Some packages could not be installed. This may mean that you have > > requested an impossible situation or if you are using the unstable > > distribution that some required packages have not yet been created > > or been moved out of Incoming. > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to > be > > installed > > Depends: libpython-stdlib (= 2.7.17-2) but it is not going to > be > > installed > > Depends: python2 (= 2.7.17-2) but 2.7.18-2 is to be installed > > E: Unable to correct problems, you have held broken packages. > > ``` > > > > In order to keep other python packages, I marked the `python2` and > `python3` > > packages as manually installed. > > > no, the python package is gone. > -- Dr. Koutheir Attouchi.
