Re: Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-29 Thread Andreas Tille
Hi Étienne, Am Sun, Jan 29, 2023 at 09:19:44PM +0100 schrieb Étienne Mollier: > The uname machine name may not have been armv7l on the test bed, > leading to the present crash. This should read like the below > and I consider pushing a "fix" in that direction tomorrow: > > @pytest.mark.ski

Re: Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-29 Thread Étienne Mollier
Hi Andreas, Andreas Tille, on 2023-01-29: > Any idea what might be wrong here? The nibabel 5.0.0-1 migration log[2] and architecture memo[3] show that I have been too strict for my test skipping heuristic: ___ test_a2f_nan2zero_range

Re: python3-openid: autopkgtest must be marked superficial

2023-01-29 Thread Malik Mlitat
Hello DPTeam, I updated python3-openid [1] to close #974502 and I need a maintainer to upload it. [1] https://salsa.debian.org/python-team/packages/python3-openid Regards, Malik On Wed, 11 Nov 2020 10:05:54 -0800 (PST) Sudip Mukherjee wrote: > Source: python3-openid > X-Debbugs-CC: elb

Re: Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-29 Thread Andreas Tille
Hi, the according log[1] says: === FAILURES === ___ test_a2f_nan2zero_range def test_a2f_nan2zero_range(): # array_to_file should check if nan can be represented as ze

Remaining numpy 1.24 issues on 32bit architectures

2023-01-29 Thread Andreas Tille
Hi, I think there are some remaining issues with numpy 1.24 migration on 32 bit architectures[1]. Here is one example: _ TestSequence.test_getitem_with_slice_has_positional_metadata _ self = def test_getitem_with_slice_has_positional_metadata(self): s = "0123456789