Your message dated Wed, 11 Jul 2018 06:54:58 +0200
with message-id <[email protected]>
and subject line Re: Bug#903530: pyresample FTBFS with Python 3.7 as supported
version
has caused the Debian Bug report #903530,
regarding pyresample FTBFS with Python 3.7 as supported version
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 [email protected]
immediately.)
--
903530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903530
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pyresample
Version: 1.9.3-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyresample.html
...
creating build/temp.linux-amd64-3.7
creating build/temp.linux-amd64-3.7/pyresample
creating build/temp.linux-amd64-3.7/pyresample/ewa
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.7m
-I/usr/lib/python3/dist-packages/numpy/core/include -c pyresample/ewa/_ll2cr.c
-o build/temp.linux-amd64-3.7/pyresample/ewa/_ll2cr.o -O3 -Wno-unused-function
In file included from /usr/include/python3.7m/numpy/ndarraytypes.h:1816:0,
from /usr/include/python3.7m/numpy/ndarrayobject.h:18,
from /usr/include/python3.7m/numpy/arrayobject.h:4,
from pyresample/ewa/_ll2cr.c:279:
/usr/include/python3.7m/numpy/npy_1_7_deprecated_api.h:15:2: warning: #warning
"Using deprecated NumPy API, disable it by " "#defining NPY_NO_DEPRECATED_API
NPY_1_7_API_VERSION" [-Wcpp]
#warning "Using deprecated NumPy API, disable it by " \
^~~~~~~
pyresample/ewa/_ll2cr.c: In function '__Pyx__ExceptionSave':
pyresample/ewa/_ll2cr.c:22410:21: error: 'PyThreadState {aka struct _ts}' has
no member named 'exc_type'; did you mean 'curexc_type'?
*type = tstate->exc_type;
^~~~~~~~
curexc_type
pyresample/ewa/_ll2cr.c:22411:22: error: 'PyThreadState {aka struct _ts}' has
no member named 'exc_value'; did you mean 'curexc_value'?
*value = tstate->exc_value;
^~~~~~~~~
curexc_value
pyresample/ewa/_ll2cr.c:22412:19: error: 'PyThreadState {aka struct _ts}' has
no member named 'exc_traceback'; did you mean 'curexc_traceback'?
*tb = tstate->exc_traceback;
^~~~~~~~~~~~~
curexc_traceback
...
--- End Message ---
--- Begin Message ---
notfound 903530 pyresample/1.9.3-2
severity 903530 important
thanks
Hi Adrian,
Filing this bug is very premature, the Python 3.7 transition is still
ongoing (#902582) and several build dependencies of pyresample have not
been rebuilt with Python 3.7 yet, specifically cython, pykdtree & cartopy.
I'm closing this issue for the time being.
Once the build dependencies have been rebuilt and pyresample still fails
to build with Python 3.7 you're welcome to reopen this issue.
Kind Regards,
Bas
--- End Message ---
