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 <ow...@bugs.debian.org> 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 <deb...@kitterman.com>. > > 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 > <deb...@kitterman.com> 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 <deb...@kitterman.com> > To: 958166-d...@bugs.debian.org > Cc: 958...@bugs.debian.org > Bcc: > Date: Sun, 19 Apr 2020 12:32:31 +0000 > 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 <l...@lkcl.net> > To: Debian Bug Tracking System <sub...@bugs.debian.org> > 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 python3 3.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
