Source: qpxtool
Version: 0.8.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -O2 -fPIC -DOFFT_64BIT -DHAVE_FOPEN64 -DHAVE_FSEEKO 
> -DUSE_LIBPNG   -O2 -D_REENTRANT -Wall -Wextra -fPIC -DQT_NO_DEBUG 
> -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_SQL_LIB -DQT_CORE_LIB -I. -I../lib/include -I. -Iinclude -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o obj/resultsio.o 
> src/resultsio.cpp
> In file included from include/resultsio.h:18,
>                  from src/resultsio.cpp:13:
> include/device.h:434:12: error: ‘QIODevice’ has not been declared
>   434 |  void save(QIODevice*);
>       |            ^~~~~~~~~
> include/device.h:437:12: error: ‘QIODevice’ has not been declared
>   437 |  void load(QIODevice*);
>       |            ^~~~~~~~~
> In file included from src/resultsio.cpp:13:
> include/resultsio.h:28:20: error: ‘QIODevice’ has not been declared
>    28 |  inline void setIO(QIODevice *io) { this->io = io; };
>       |                    ^~~~~~~~~
> include/resultsio.h:32:2: error: ‘QIODevice’ does not name a type; did you 
> mean ‘QPxIODevice’?
>    32 |  QIODevice *io;
>       |  ^~~~~~~~~
>       |  QPxIODevice
> include/resultsio.h: In constructor ‘ResultsIO::ResultsIO(device*)’:
> include/resultsio.h:25:88: error: ‘io’ was not declared in this scope
>    25 |  ResultsIO(device *dev)  :QThread((QObject*)dev) { this->dev = dev; 
> this->res = false; io = NULL; }
>       |                                                                       
>                  ^~
> include/resultsio.h: In member function ‘void ResultsIO::setIO(int*)’:
> include/resultsio.h:28:43: error: ‘class ResultsIO’ has no member named ‘io’
>    28 |  inline void setIO(QIODevice *io) { this->io = io; };
>       |                                           ^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:45:7: error: ‘io’ was not declared in this scope
>    45 |  if (!io || !io->isOpen() || !io->isReadable()) { return; }
>       |       ^~
> src/resultsio.cpp:46:16: error: ‘io’ was not declared in this scope
>    46 |  xml.setDevice(io);
>       |                ^~
> src/resultsio.cpp: In member function ‘virtual void ResultsWriter::run()’:
> src/resultsio.cpp:300:7: error: ‘io’ was not declared in this scope
>   300 |  if (!io || !io->isOpen() || !io->isWritable()) { return; }
>       |       ^~
> src/resultsio.cpp:302:16: error: ‘io’ was not declared in this scope
>   302 |  xml.setDevice(io);
>       |                ^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:251:5: warning: this statement may fall through 
> [-Wimplicit-fallthrough=]
>   251 |     if (isQpxData && xml.name() == "qpxdata") {
>       |     ^~
> src/resultsio.cpp:276:4: note: here
>   276 |    case QXmlStreamReader::Invalid:
>       |    ^~~~
> make[3]: *** [Makefile.qmake:1091: obj/resultsio.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/qpxtool_0.8.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.

Reply via email to