Bug#1025788: transition: numpy
> On Mon, 12 Dec 2022 at 23:27, Sandro Tosi wrote: > > thanks, numpy/1.23.5-2 has just been uploaded to unstable. > > \o/ In the meantime, since upstream released it, i've uploaded numpy/1.24.0 to experimental and the autopkgtest results are https://qa.debian.org/excuses.php?experimental=1=numpy now, there's a lot of red in there but almost all of the errors come in the format of AttributeError: module 'numpy' has no attribute 'X' with X being [float, int, bool, object, ...]. This is because, numpy upstream in 1.24.0, finally decided to expire https://numpy.org/doc/stable/release/1.24.0-notes.html#:~:text=The%20deprecation%20for%20the%20aliases some deprecations introduced in 1.20.0 https://numpy.org/doc/stable/release/1.20.0-notes.html#using-the-aliases-of-builtin-types-like-np-int-is-deprecated (released almost 2 years ago). All of those are quite straightforward to fix, since often it's just necessary to stop importing them from numpy and use the python native types. There are handful more errors in the form of: * ValueError: setting an array element with a sequence. The requested array has an inhomogeneous shape after 1 dimensions. The detected shape was (2,) + inhomogeneous part. * Too many indices for array: array is 0-dimensional, but 1 were indexed which will need to be looked at in more details, likely by individual projects upstream. This additional transition seems to be comfortably in the reach for Bullseye and will place us in a better position to get support from upstream. I also anticipate that a few more patch releases (fixing bugs etc) for the 1.24.x series will be published before Bullseye is released and we would like to update numpy to them in Debian if reasonable. Please let me know if i can proceed with a numpy upload to unstable. Regards, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1025788: transition: numpy
Hi Sandro On Mon, 12 Dec 2022 at 23:27, Sandro Tosi wrote: > thanks, numpy/1.23.5-2 has just been uploaded to unstable. \o/ > thanks! on the same line, i'm planning on upgrading matplotlib > (another foundation package) from 3.5.x in unstable to 3.6.x (latest > upstream release). Do you want me to submit a transition bug report > when ready? Yes please. Filing it now would be even better, then additional information e.g. ETA, links to autopkgtest results, etc. can be added as it becomes available. Regards Graham
Bug#1025788: transition: numpy
> Since the ABI package python3-numpy-abi9 was not bumped, I don't > believe any rebuilds are needed. Please go ahead and upload to > unstable. thanks, numpy/1.23.5-2 has just been uploaded to unstable. > > Was i just too conservative in asking for a transition slow while i > > should have uploaded to unstable (as done several other times) and > > handle the autopkgtests one by one? > > Although this is not a transition in the way a C library transition > requires rebuilding all reverse-dependencies, a transition to a new > Python module often requires updating reverse-dependencies, of which > numpy has many, so it's good to bring these to the attention of the > release team. Thanks for the headsup! thanks! on the same line, i'm planning on upgrading matplotlib (another foundation package) from 3.5.x in unstable to 3.6.x (latest upstream release). Do you want me to submit a transition bug report when ready? Cheers, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1025788: transition: numpy
Control: tags -1 + confirmed - moreinfo Hi Sandro On Sun, 11 Dec 2022 at 19:39, Sandro Tosi wrote: > numpy provides 2 virtual packages, to track the ABI/API version as > advertised by the upstream project. Between unstable and experimental, > we did not bump the ABI package (which stays at `python3-numpy-abi9`) > while we bumped the API package (from `python3-numpy-api14` to > `python3-numpy-api16`). > > In the past times we asked for a transition (f.e. #658289 or #616364), > we referred to the -abiXX package, but in this case we cannot rely on > it since it was not bumped. Since the ABI package python3-numpy-abi9 was not bumped, I don't believe any rebuilds are needed. Please go ahead and upload to unstable. > Was i just too conservative in asking for a transition slow while i > should have uploaded to unstable (as done several other times) and > handle the autopkgtests one by one? Although this is not a transition in the way a C library transition requires rebuilding all reverse-dependencies, a transition to a new Python module often requires updating reverse-dependencies, of which numpy has many, so it's good to bring these to the attention of the release team. Thanks for the headsup! Regards Graham
Bug#1025788: transition: numpy
On Sun, Dec 11, 2022 at 1:26 PM Sebastian Ramacher wrote: > Which packages would be needed to be rebuilt for this transition? I'm not sure how to answer this question. numpy provides 2 virtual packages, to track the ABI/API version as advertised by the upstream project. Between unstable and experimental, we did not bump the ABI package (which stays at `python3-numpy-abi9`) while we bumped the API package (from `python3-numpy-api14` to `python3-numpy-api16`). In the past times we asked for a transition (f.e. #658289 or #616364), we referred to the -abiXX package, but in this case we cannot rely on it since it was not bumped. Was i just too conservative in asking for a transition slow while i should have uploaded to unstable (as done several other times) and handle the autopkgtests one by one? Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1025788: transition: numpy
Control: tags -1 moreinfo On 2022-12-08 22:36:41 -0500, Sandro Tosi wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > X-Debbugs-Cc: nu...@packages.debian.org, mo...@debian.org > Control: affects -1 + src:numpy > > Hello, > i would like to request a transition slot for numpy. > > numpy/1.23.5 is in experimental, the autopkgtest for it are: > > https://qa.debian.org/excuses.php?experimental=1=numpy > > I gave a look at the failures and several of them are due to other reasons > (uninstallable packages and the like), others may be attributed to python3.11 > being added to unstable; issues related to the newer numpy are of the type > > AttributeError: module 'numpy' has no attribute 'asscalar' > > which has been removed after being deprecated for 7 releases: > > https://numpy.org/doc/1.22/reference/generated/numpy.asscalar.html > > > Please let me know when i can upload numpy/1.23.5 to unstable. Which packages would be needed to be rebuilt for this transition? Cheers -- Sebastian Ramacher
Bug#1025788: transition: numpy
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: nu...@packages.debian.org, mo...@debian.org Control: affects -1 + src:numpy Hello, i would like to request a transition slot for numpy. numpy/1.23.5 is in experimental, the autopkgtest for it are: https://qa.debian.org/excuses.php?experimental=1=numpy I gave a look at the failures and several of them are due to other reasons (uninstallable packages and the like), others may be attributed to python3.11 being added to unstable; issues related to the newer numpy are of the type AttributeError: module 'numpy' has no attribute 'asscalar' which has been removed after being deprecated for 7 releases: https://numpy.org/doc/1.22/reference/generated/numpy.asscalar.html Please let me know when i can upload numpy/1.23.5 to unstable. Thanks, Sandro
