Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Dmitry Shachnev
On Sat, Oct 26, 2019 at 10:35:37AM +0200, Sebastiaan Couwenberg wrote: > On 10/26/19 10:19 AM, Dmitry Shachnev wrote: > > Thanks for fixing this! Unfortunately it still FTBFS on mipsel. Do you know > > what could cause this? > > My gut says it just inherent to the arch, mips* tends to be

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Sebastiaan Couwenberg
On 10/26/19 10:19 AM, Dmitry Shachnev wrote: > Thanks for fixing this! Unfortunately it still FTBFS on mipsel. Do you know > what could cause this? My gut says it just inherent to the arch, mips* tends to be problematic. I don't know how to fix the "Error: branch out of range" issues, so I'll

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-26 Thread Dmitry Shachnev
Hi Sebastiaan, On Wed, Oct 23, 2019 at 04:52:47PM +0200, Sebastiaan Couwenberg wrote: > The log implies the problem is with OpenCL, it may be the same as > #942015 which is already fixed in git. > > The next upstream release will be on Friday, since this issue will also > break their builds, a

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-23 Thread Dmitry Shachnev
On Wed, Oct 23, 2019 at 04:52:47PM +0200, Sebastiaan Couwenberg wrote: > The log implies the problem is with OpenCL, it may be the same as > #942015 which is already fixed in git. > > The next upstream release will be on Friday, since this issue will also > break their builds, a fix from upstream

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-23 Thread Sebastiaan Couwenberg
Control: tags -1 confirmed On 10/23/19 4:34 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > Your package FTBFS while rebuilding it against Qt 5.12.5, although from the > build log > I can not tell for sure if the problem lies in Qt itself. I know, and I'm waiting for pyqt5 (5.12.3+dfsg-3) to

Bug#943331: qgis: FTBFS with Qt 5.12.5

2019-10-23 Thread Lisandro Damián Nicanor Pérez Meyer
Source: qgis Version: 3.4.12+dfsg-1 Severity: serious Justification: FTBFS Hi! Your package FTBFS while rebuilding it against Qt 5.12.5, although from the build log I can not tell for sure if the problem lies in Qt itself. An excerpt from it: FAILED: