pyresample 1.15.0+ds-1 MIGRATED to testing

2020-03-25 Thread Debian testing watch
FYI: The status of the pyresample source package in Debian's testing distribution has changed. Previous version: 1.14.0-4 Current version: 1.15.0+ds-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

Bug#954917: Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX)

2020-03-25 Thread Laurent Bigonville
Le 25/03/20 à 10:54, Sebastiaan Couwenberg a écrit : Control: tags -1 upstream wontfix Control: severity -1 normal On 3/25/20 10:39 AM, Laurent Bigonville wrote: I see that the configure is autodetecting at buildtime whether several CPU optimisations (SSE, SSE3, AVX) should be enabled or not.

Processed: Re: Bug#954917: Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX)

2020-03-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream wontfix Bug #954917 [src:gdal] Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX) Added tag(s) upstream and wontfix. > severity -1 normal Bug #954917 [src:gdal] Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX)

Bug#954917: Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX)

2020-03-25 Thread Sebastiaan Couwenberg
Control: tags -1 upstream wontfix Control: severity -1 normal On 3/25/20 10:39 AM, Laurent Bigonville wrote: > I see that the configure is autodetecting at buildtime whether several > CPU optimisations (SSE, SSE3, AVX) should be enabled or not. > > I feel this is not OK as building the package

Bug#954917: Do not rely on autodetection for CPU optimisations (SSE, SSE3, AVX)

2020-03-25 Thread Laurent Bigonville
Source: gdal Version: 3.0.4+dfsg-1 Severity: important Hello, I see that the configure is autodetecting at buildtime whether several CPU optimisations (SSE, SSE3, AVX) should be enabled or not. I feel this is not OK as building the package on different hardware would result in different