Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)
On April 19, 2020 1:55:20 PM UTC, Luke Kenneth Casson Leighton wrote: >On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System > wrote: > >> #958166: python3-all: python3 can't import gmpy2 >> Python3.7 is no longer supported in Debian Unstable and Testing and >will be removed shortly. > >if you were talking about python 3.6, there would be absolutely no >problem, because python 3.6 is not the default version of python3 >that's installed in the current LTS stable release (debian 10). > >the fact that python 3.7 is the default LTS stable *and is being >removed* leaves an extremely serious situation for anyone that >attempts to dist-upgrade from debian 10 to debian 11. > >that was the lesson learned - the mistake made - by the ubuntu team, >made all the more serious that the entire apt packaging system was >critically dependent on a version of python that was *being removed* >(!!) > >forget for one moment that i'm using debian/testing (which you should >not in any way find it "acceptable" to callously dismiss people in the >position that i am in such an unthinking fashion) - people doing >*stable* dist-upgrades will end up with broken systems. > >and it's part of debian that stable-to-stable dist-upgrades must >*always work*, ok? you should know this. > >and *that* is why i raised this as a critical bugreport, ok? > >*please think* before arbitrarily closing critical bugreports, ok? > >l. That's completely wrong. The existence proof is the aforementioned Debian 10. It only supports python3.7. Not the version that was in Debian 9. If you need more, look at Debian 9; it only supports python3.5, which is not the version in Debian 8 (the actual LTS release). Scott K
Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)
On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > #958166: python3-all: python3 can't import gmpy2 > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. if you were talking about python 3.6, there would be absolutely no problem, because python 3.6 is not the default version of python3 that's installed in the current LTS stable release (debian 10). the fact that python 3.7 is the default LTS stable *and is being removed* leaves an extremely serious situation for anyone that attempts to dist-upgrade from debian 10 to debian 11. that was the lesson learned - the mistake made - by the ubuntu team, made all the more serious that the entire apt packaging system was critically dependent on a version of python that was *being removed* (!!) forget for one moment that i'm using debian/testing (which you should not in any way find it "acceptable" to callously dismiss people in the position that i am in such an unthinking fashion) - people doing *stable* dist-upgrades will end up with broken systems. and it's part of debian that stable-to-stable dist-upgrades must *always work*, ok? you should know this. and *that* is why i raised this as a critical bugreport, ok? *please think* before arbitrarily closing critical bugreports, ok? l.
Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)
here is a package that contains a build system that, unlike the python3-numpy team, relies exclusively on python3-all. like python3-gmpy2, note that it does not contain enumeration of the minor versions of python. its control file does not list multiple versions of python3, either, choosing instead to rely on the macros. thus this particular package is critically subject to your arbitrary and unthinking "whims", where python3-numpy is not. i strongly suggest that you investigate precisely and exactly what happened, historically, when ubuntu tried to do what you are forcing onto people in an unthinking and inconsiderate way. l. rules-pythonmagick Description: Binary data
Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)
you do realise, scott, that python3-numpy has been forced into a position of bypassing the careless unthinking decision that you've made, by including the capability to manually enumerate and compile up multiple versions for different versions of python3? instead of closing the bugreport and making a callous "declaration", you could instead have said, "um, that's really strange, because we have done this several times in the past. what do *you* think makes this situation different, which warrants a critical bugreport status?" and we could have worked TOGETHER to find the answer. people don't raise critical bugreports without good justification, scott. it's the first time i've ever considered it, in over 16 years of continuously using debian. would you like to reconsider, or do i have to escalate this further? l. On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Scott Kitterman > by > replying to this email. > > > -- > 958166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Scott Kitterman > To: 958166-d...@bugs.debian.org > Cc: 958...@bugs.debian.org > Bcc: > Date: Sun, 19 Apr 2020 12:32:31 + > Subject: Re: [Python-modules-team] [critical] #958166 - python3-all has had > python3.7 removed > Alternately, you could just update python3-gmpy2 to the latest version of the > package, which is built to support python3.8: > > https://packages.debian.org/sid/amd64/python3-gmpy2/filelist > > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. > > What you are observing is a perfectly normal transition to a newer version of > python3. If such things bother you this much, you should probably stick to a > Debian Stable release. > > This is the 7th time we've done this for Python3. It happens once or twice a > release cycle. There's no bug at all here. > > Scott K > > > -- Forwarded message -- > From: lkcl > To: Debian Bug Tracking System > Cc: > Bcc: > Date: Sun, 19 Apr 2020 09:28:54 +0100 > Subject: python3-all: python3 can't import gmpy2 > Package: python3-all > Version: 3.8.2-2 > Severity: important > > see #958043 > > it has now become impossible to install python3-gmpy2. however that > is just one symptom of this serious issue. > > with python3-all no longer dependent on both python3.7 and python3.8, > transitioning from python3.7 to python3.8 has just become a nightmare. > > with some packages being built that are dependent on 3.7 and some on 3.8, > any packages which have dependencies that import from both sets during > the transition will cause a serious install failure > > > > -- System Information: > Debian Release: 8.1 > APT prefers oldoldstable > APT policy: (500, 'oldoldstable'), (500, 'testing'), (500, 'stable'), (500, > 'oldstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-6-amd64 (SMP w/16 CPU cores) > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages python3-all depends on: > ii python33.8.2-2 > ii python3-distutils 3.8.2-2 > ii python3.7 3.7.2-1 > ii python3.8 3.8.2-1+b1 > > python3-all recommends no packages. > > python3-all suggests no packages. > > -- no debconf information rules Description: Binary data
Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)
On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Scott Kitterman > by > replying to this email. > > > -- > 958166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > > -- Forwarded message -- > From: Scott Kitterman > To: 958166-d...@bugs.debian.org > Cc: 958...@bugs.debian.org > Bcc: > Date: Sun, 19 Apr 2020 12:32:31 + > Subject: Re: [Python-modules-team] [critical] #958166 - python3-all has had > python3.7 removed > Alternately, you could just update python3-gmpy2 to the latest version of the > package, which is built to support python3.8: > > https://packages.debian.org/sid/amd64/python3-gmpy2/filelist > > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. this is a serious mistake. did you not read what i wrote? did you not learn from the lesson of ubuntu when it made the same mistake, with apt depending on the version that was removed, at the time? > What you are observing is a perfectly normal transition to a newer version of > python3. If such things bother you this much, you should probably stick to a > Debian Stable release. that's absolutely impossible. i cannot believe that you are seriously asking that people quotes stick to debian stable quotes as a quotes solution quotes. did you not read that i have over 5 million source code files on this system? did you imagine that as a software developer i would be *able* to quotes use debian stable quotes? software developers *need* to be able to use debian/testing, if debian/stable does not do what they need. expecting them to compile up packages and custom-maintain vast swathes of packages from source in /usr/local is hopelessly unrealistic and is precisely why distros exist in the first place. do you not understand how seriously cavalier and unthinking your response is? > This is the 7th time we've done this for Python3. that would explain why i have encountered problems like this in the past. question. was a version removed that happened to also be the "stable" version? did you not read what i wrote? > It happens once or twice a release cycle. > There's no bug at all here. that is false: what it means is that you do not understand the serious consequences of the decision that's being made. you have completely failed to acknowledge what i wrote, choosing instead to selectively quote your own past experience. not only that, you've closed this critical bugreport without a wider consultation. why did you do that? l.
