** Description changed: Summary of archive operations: On yakkety, remove arm64 binaries from the following source packages that would now fail the arm64 build if rebuilt: bino goldencheetah openscad sdrangelove ovito tulip vite - - candidates (build test not yet finished): yade Since Qt is now using OpenGL ES, Qt 5 applications directly using OpenGL features not available in the ES subset may have build failures since OpenGL ES headers are now used instead. Such applications didn't build on armhf either which has used OpenGL ES from the beginning. Similar to armhf, all or most arm64 hardware graphics (like Adreno, Mali) have only ES support. --- below is background regarding how the package list was created Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf. I've output of packages building against Qt 5 (qtbase5-dev, qt5-qmake, qtdeclarative5-dev or qt5-default), and a list of packages failing to build on armhf - formerly from from http://qa.ubuntuwire.org/ftbfs/ and then again via launchpadlib. Combining those results in this list: itksnap klog libqglviewer mudlet sdrangelove sleepyhead thumbnailer tulip Of which I already knew tulip was affected. klog and thumbnailer seem false positive, making the following candidates of removing arm64 binaries of: itksnap libqglviewer mudlet sdrangelove sleepyhead tulip To get absolutely everything, I got a list of all binaries depending on libqt5core5a, got the source package for them and cross-checked. This got me the list of the six above plus the following three: bino qwtplot3d vite However, rebuilding all of the nine resulted in discovery that not all that failed on armhf fail on arm64: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-035/+packages The failures for 5 armhf packages seem to be not related to the choice of Qt's OpenGL configuration options, so the arm64 builds succeeded (in case of itksnap, would have succeeded if not for other FTBFS problem). -- Same but for depwait and not ftbfs (list gotten via launchpadlib), cross-checking against libqt5core5a depending packages: goldencheetah # noticed manually first, but also gotten from this filtering openscad ovito qtconnectivity-opensource-src yade + + Of these goldencheetah openscad ovito failed arm64 rebuild.
** Description changed: Summary of archive operations: On yakkety, remove arm64 binaries from the following source packages that would now fail the arm64 build if rebuilt: - bino goldencheetah openscad sdrangelove ovito tulip vite + bino goldencheetah openscad ovito sdrangelove tulip vite Since Qt is now using OpenGL ES, Qt 5 applications directly using OpenGL features not available in the ES subset may have build failures since OpenGL ES headers are now used instead. Such applications didn't build on armhf either which has used OpenGL ES from the beginning. Similar to armhf, all or most arm64 hardware graphics (like Adreno, Mali) have only ES support. --- below is background regarding how the package list was created Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf. I've output of packages building against Qt 5 (qtbase5-dev, qt5-qmake, qtdeclarative5-dev or qt5-default), and a list of packages failing to build on armhf - formerly from from http://qa.ubuntuwire.org/ftbfs/ and then again via launchpadlib. Combining those results in this list: itksnap klog libqglviewer mudlet sdrangelove sleepyhead thumbnailer tulip Of which I already knew tulip was affected. klog and thumbnailer seem false positive, making the following candidates of removing arm64 binaries of: itksnap libqglviewer mudlet sdrangelove sleepyhead tulip To get absolutely everything, I got a list of all binaries depending on libqt5core5a, got the source package for them and cross-checked. This got me the list of the six above plus the following three: bino qwtplot3d vite However, rebuilding all of the nine resulted in discovery that not all that failed on armhf fail on arm64: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-035/+packages The failures for 5 armhf packages seem to be not related to the choice of Qt's OpenGL configuration options, so the arm64 builds succeeded (in case of itksnap, would have succeeded if not for other FTBFS problem). -- Same but for depwait and not ftbfs (list gotten via launchpadlib), cross-checking against libqt5core5a depending packages: goldencheetah # noticed manually first, but also gotten from this filtering openscad ovito qtconnectivity-opensource-src yade Of these goldencheetah openscad ovito failed arm64 rebuild. ** Description changed: - Summary of archive operations: + Summary of requested archive operations: On yakkety, remove arm64 binaries from the following source packages that would now fail the arm64 build if rebuilt: bino goldencheetah openscad ovito sdrangelove tulip vite Since Qt is now using OpenGL ES, Qt 5 applications directly using OpenGL features not available in the ES subset may have build failures since OpenGL ES headers are now used instead. Such applications didn't build on armhf either which has used OpenGL ES from the beginning. Similar to armhf, all or most arm64 hardware graphics (like Adreno, Mali) have only ES support. --- below is background regarding how the package list was created Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf. I've output of packages building against Qt 5 (qtbase5-dev, qt5-qmake, qtdeclarative5-dev or qt5-default), and a list of packages failing to build on armhf - formerly from from http://qa.ubuntuwire.org/ftbfs/ and then again via launchpadlib. Combining those results in this list: itksnap klog libqglviewer mudlet sdrangelove sleepyhead thumbnailer tulip Of which I already knew tulip was affected. klog and thumbnailer seem false positive, making the following candidates of removing arm64 binaries of: itksnap libqglviewer mudlet sdrangelove sleepyhead tulip To get absolutely everything, I got a list of all binaries depending on libqt5core5a, got the source package for them and cross-checked. This got me the list of the six above plus the following three: bino qwtplot3d vite However, rebuilding all of the nine resulted in discovery that not all that failed on armhf fail on arm64: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-035/+packages The failures for 5 armhf packages seem to be not related to the choice of Qt's OpenGL configuration options, so the arm64 builds succeeded (in case of itksnap, would have succeeded if not for other FTBFS problem). -- Same but for depwait and not ftbfs (list gotten via launchpadlib), cross-checking against libqt5core5a depending packages: goldencheetah # noticed manually first, but also gotten from this filtering openscad ovito qtconnectivity-opensource-src yade Of these goldencheetah openscad ovito failed arm64 rebuild. ** Description changed: Summary of requested archive operations: On yakkety, remove arm64 binaries from the following source packages that would now fail the arm64 build if rebuilt: bino goldencheetah openscad ovito sdrangelove tulip vite - Since Qt is now using OpenGL ES, Qt 5 applications directly using OpenGL - features not available in the ES subset may have build failures since - OpenGL ES headers are now used instead. Such applications didn't build - on armhf either which has used OpenGL ES from the beginning. Similar to - armhf, all or most arm64 hardware graphics (like Adreno, Mali) have only - ES support. + Since Qt is now using OpenGL ES on arm64, Qt 5 applications directly + using OpenGL features not available in the ES subset may have build + failures since OpenGL ES headers are now used instead. Such applications + didn't build on armhf either which has used OpenGL ES from the + beginning. Similar to armhf, all or most arm64 hardware graphics (like + Adreno, Mali) have only ES support. --- below is background regarding how the package list was created Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf. I've output of packages building against Qt 5 (qtbase5-dev, qt5-qmake, qtdeclarative5-dev or qt5-default), and a list of packages failing to build on armhf - formerly from from http://qa.ubuntuwire.org/ftbfs/ and then again via launchpadlib. Combining those results in this list: itksnap klog libqglviewer mudlet sdrangelove sleepyhead thumbnailer tulip Of which I already knew tulip was affected. klog and thumbnailer seem false positive, making the following candidates of removing arm64 binaries of: itksnap libqglviewer mudlet sdrangelove sleepyhead tulip To get absolutely everything, I got a list of all binaries depending on libqt5core5a, got the source package for them and cross-checked. This got me the list of the six above plus the following three: bino qwtplot3d vite However, rebuilding all of the nine resulted in discovery that not all that failed on armhf fail on arm64: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-035/+packages The failures for 5 armhf packages seem to be not related to the choice of Qt's OpenGL configuration options, so the arm64 builds succeeded (in case of itksnap, would have succeeded if not for other FTBFS problem). -- Same but for depwait and not ftbfs (list gotten via launchpadlib), cross-checking against libqt5core5a depending packages: goldencheetah # noticed manually first, but also gotten from this filtering openscad ovito qtconnectivity-opensource-src yade Of these goldencheetah openscad ovito failed arm64 rebuild. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586026 Title: Remove arm64 binaries for packages failing to build with Qt compiled with OpenGL ES To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bino/+bug/1586026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
