Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-11 Thread Adrian Bunk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Wed, Jul 11, 2018 at 12:42:09PM +0100, Chris Lamb wrote:
> Adrian,

Chris,

> > This is not the first time that you are blaming me for submitting
> > FTBFS bugs, but it is not required for the submitter to state more
> > than the error message (which I did) - it is the maintainer who
> > is supposed to debug problems.
> 
> This might be true but in Debian aren't we trying to work together as a
> team?
> 
> Whilst you may have submitted this original report with the very best
> of intentions, to reply that you were technically within the rules is
> not a particularly productive response in context and hardly going to
> lead to a quick and amicable conclusion. :)

Does immediate downgrading and closing of the bug without looking
at the contents lead to a quick and amicable conclusion?

And quoting from the two emails by Bas Couwenberg in this bug:

- - "Filing this bug is very premature"
- - "Your bugreports are filed blindly"
- - "your bugreport does not state any specific issue"
- - "I very much hate bugreports like that, which I'm very tempted to just 
   blindly close (with `bts close`) from now on."
- - "Provide better bugreports in the future, or I will start closing them 
   blindly."
- - "The issue that your bugreport template is substandard remains."

Please give a signed answer whether you as DPL consider both the 
contents and the quantity of these statements appropriate for
"working together as a team" in Debian.

> Best wishes,

Thanks in advance
Adrian

- -- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltGZlMACgkQiNJCh6LY
mLHREhAAqfCoi413lV7DoLqgcl31qNblBLqLV7vkWJE9i0RY/Q9C/1cvVVCxe0UC
MeNSukWD1bt0nIg6DF5x0+RPW68m3BnZJCKsCSpwmGtOrBWFfDtl9vQkW0av87Xa
x5DjZ4XLnyNr0e0/CnxPEa3VowDUg6afisp2QeKGFgrWgNOo4wgQ4K1Gj3AOGdsX
fGNNBTUtqgGVHfU3fqQmABoqJ6rLQYDk3HpwRtDtG3Xf+smGn24UDKhl9z64mhKl
bDCaIf3oiGNYjWbEkTa/wucjz3zTfRtVAtw/fBwHyb1DMwbKwTtWjy/6ByxOgdeC
yf70WiXcvt4s3EVIVKo1QSIlPlH9uznlrFlrubQIX61a0QTMoc6ZugAtfevTdpK6
1CeRFT6fh9AX2NUKU9hjynEZQkpF7VNsrI9H6aRJMTNc8xRXVmr0aZF7ho7N7079
82HcfSa3WyjUZQseKhPMht0UrCbblBNGNhLK4y99N156wYyRcWJ7CZYU72UG8jKg
MWtmWQgqBL1UoCDtnDkHXDI8jDuOXLTHzL1fMliwL0FvnpVzbcAmmXHOU1oKxYR5
c0sO+lvEez6PBbuG15OAh29z0yaXtieGWdy8JL/5FaZDJCH8dAyxKo1uUViGUq4r
qeg03kmTjKqaYeqvJJNMLKPmXnZ3+DMkUyGDSVurZOEepwMB1Ug=
=W73T
-END PGP SIGNATURE-

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-11 Thread Chris Lamb
Adrian,

> This is not the first time that you are blaming me for submitting
> FTBFS bugs, but it is not required for the submitter to state more
> than the error message (which I did) - it is the maintainer who
> is supposed to debug problems.

This might be true but in Debian aren't we trying to work together as a
team?

Whilst you may have submitted this original report with the very best
of intentions, to reply that you were technically within the rules is
not a particularly productive response in context and hardly going to
lead to a quick and amicable conclusion. :)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed (with 1 error): Re: Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-11 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #903530 {Done: Sebastiaan Couwenberg } [src:pyresample] 
pyresample FTBFS with Python 3.7 as supported version
Bug reopened
Ignoring request to alter fixed versions of bug #903530 to the same values 
previously set
> severity -1
Unknown command or malformed arguments to command.


-- 
903530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-11 Thread Adrian Bunk
Control: reopen -1
Control: severity -1

On Wed, Jul 11, 2018 at 06:54:58AM +0200, Sebastiaan Couwenberg wrote:
> notfound 903530 pyresample/1.9.3-2
> severity 903530 important
> thanks
> 
> Hi Adrian,

Hi Bas,

> Filing this bug is very premature,

no, it is not.

> 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.

Please don't blindly close bugs.

Your package does FTBFS due to changes in the C headers of python itself.

> 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.

I'm reopening it right away since it is obvious at first sight that
it will still FTBFS when the dependencies have been rebuilt.

> Kind Regards,
> 
> Bas

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Processed: Re: Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> notfound 903530 pyresample/1.9.3-2
Bug #903530 [src:pyresample] pyresample FTBFS with Python 3.7 as supported 
version
No longer marked as found in versions pyresample/1.9.3-2.
> severity 903530 important
Bug #903530 [src:pyresample] pyresample FTBFS with Python 3.7 as supported 
version
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel

Bug#903530: pyresample FTBFS with Python 3.7 as supported version

2018-07-10 Thread Adrian Bunk
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
...

___
Pkg-grass-devel mailing list
Pkg-grass-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel