On Sun, May 16, 2021 at 12:52 PM Luke Kenneth Casson Leighton <l...@lkcl.net> wrote:
> to fix this, there needs to be a stable overlap where multiple compiled > versions > are installed and maintained. to fix the problem, the rule needs to be set: > > * any given version of python *MUST* cross over from one debian/stable > to another debian/stable. > * only when a given version of python has been in TWO versions of > debian/stable may it be considered for retirement / removal sorry, correction / clarification: any given version of python *and all python packages* must cross over from and be permanently and irrevocably available across two versions of debian/stable. this will sove in one fell swoop all of the issues that have been reported multiple times by multiple people for many years, creating a long-term reliable and stable distribution. you will be able to *SAFELY* do what you just did - back out of python 3.8 and deploy 3.9 - *WITHOUT* completely destroying people's systems because 3.7 was force-removed and they were given absolutely no choice in the matter. btw please, please, i am anticipating responses of the type "it's your problem, you shouldn't be using debian/testing, if you do you get everything you deserve". if that thought crossed your mind, please reconsider, and ask instead "why is this person using debian/testing for 20 years". l.
