Your message dated Thu, 31 Jan 2019 12:22:27 +0100
with message-id <95471e20-5052-6d34-d09b-d39621fbb...@debian.org>
and subject line Re: Bug#920681: atropy ftbfs with numpy 1.16
has caused the Debian Bug report #920681,
regarding atropy ftbfs with numpy 1.16
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
920681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:astropy
Version: 3.1.1-1
Severity: serious
Tags: sid buster
atropy ftbfs with numpy 1.16
at least there are deprecation warnings popping up ...
> 'a.item() instead', DeprecationWarning, stacklevel=1)
E DeprecationWarning: np.asscalar(a) is deprecated since NumPy v1.16, use
a.item() instead
/usr/lib/python3/dist-packages/numpy/lib/type_check.py:546: DeprecationWarning
====== 23 failed, 11633 passed, 358 skipped, 66 xfailed in 640.43 seconds ======
--- End Message ---
--- Begin Message ---
On 28.01.19 12:57, Ole Streicher wrote:
> Control: tags -1 moreinfo
>
> Hi Matthias,
>
> could you point me to a complete build log? 3.1.1-1 compiled fine with
> numpy_1.16.0~rc2, and I just successfully tried with numpy 1.16.0. The
> failure you mentioned happened in 3.1 and was the main reason for
> upstream to make a 3.1.1 release.
sorry for the noise. I don't see it failing anymore.
--- End Message ---
