| 2016-05-26 12:40:11 |
Timo Jyrinki |
bug |
|
|
added bug |
| 2016-05-26 12:50:24 |
Timo Jyrinki |
description |
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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 |
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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
So, nine source packages should be the final list. |
|
| 2016-05-27 10:54:04 |
Timo Jyrinki |
description |
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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
So, nine source packages should be the final list. |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino itksnap libqglviewer mudlet qwtplot3d sdrangelove sleepyhead tulip vite
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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
So, nine source packages should be the final list. |
|
| 2016-05-30 06:46:50 |
Timo Jyrinki |
description |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino itksnap libqglviewer mudlet qwtplot3d sdrangelove sleepyhead tulip vite
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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
So, nine source packages should be the final list. |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino sdrangelove tulip vite
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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). |
|
| 2016-05-31 15:33:50 |
Timo Jyrinki |
description |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino sdrangelove tulip vite
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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). |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino sdrangelove tulip vite
todo: cross-check list of packages where armhf build is omitted on purpose instead of ftbfs?
todo2: See https://launchpad.net/ubuntu/+source/goldencheetah/3.3.0-3build1/+build/9805094 - however qwtplot3d did/would rebuild on arm64. Would the successful rebuild of qwtplot3d help rebuilding goldencheetah on arm64?
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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). |
|
| 2016-05-31 17:51:10 |
Jeremy Bícha |
bug |
|
|
added subscriber Jeremy Bicha |
| 2016-06-01 11:50:12 |
Timo Jyrinki |
description |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino sdrangelove tulip vite
todo: cross-check list of packages where armhf build is omitted on purpose instead of ftbfs?
todo2: See https://launchpad.net/ubuntu/+source/goldencheetah/3.3.0-3build1/+build/9805094 - however qwtplot3d did/would rebuild on arm64. Would the successful rebuild of qwtplot3d help rebuilding goldencheetah on arm64?
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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). |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino goldencheetah sdrangelove tulip vite
candidates: openscad ovito yade
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
|
| 2016-06-01 11:50:19 |
Timo Jyrinki |
bug task added |
|
bino (Ubuntu) |
|
| 2016-06-01 11:50:43 |
Timo Jyrinki |
description |
Summary of archive operations:
On yakkety, remove arm64 binaries from the following source packages:
bino goldencheetah sdrangelove tulip vite
candidates: openscad ovito yade
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
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 sdrangelove tulip vite
candidates: openscad ovito yade
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
|
| 2016-06-01 11:50:56 |
Timo Jyrinki |
bug task added |
|
goldencheetah (Ubuntu) |
|
| 2016-06-01 11:51:35 |
Timo Jyrinki |
bug task added |
|
sdrangelove (Ubuntu) |
|
| 2016-06-01 11:51:44 |
Timo Jyrinki |
bug task added |
|
tulip (Ubuntu) |
|
| 2016-06-01 11:51:56 |
Timo Jyrinki |
bug task added |
|
vite (Ubuntu) |
|
| 2016-06-01 11:52:06 |
Timo Jyrinki |
bug task deleted |
qtbase-opensource-src (Ubuntu) |
|
|
| 2016-06-01 11:52:35 |
Timo Jyrinki |
description |
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 sdrangelove tulip vite
candidates: openscad ovito yade
---
Qt build for arm64 recently switched to using OpenGL ES in yakkety, similar to armhf.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
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 sdrangelove tulip vite
candidates: openscad ovito yade
--- 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.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
|
| 2016-06-01 11:55:46 |
Timo Jyrinki |
description |
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 sdrangelove tulip vite
candidates: openscad ovito yade
--- 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.
Currently I've gotten 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 (even if failing on other architectures) from http://qa.ubuntuwire.org/ftbfs/.
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
Update: 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:
goldencheetah
openscad
ovito
qtconnectivity-opensource-src
yade |
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 sdrangelove tulip vite
candidates: openscad ovito yade
--- 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 |
|
| 2016-06-01 11:58:30 |
Timo Jyrinki |
description |
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 sdrangelove tulip vite
candidates: openscad ovito yade
--- 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 |
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 sdrangelove ovito tulip vite
candidates: openscad yade
--- 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 |
|
| 2016-06-01 11:58:34 |
Timo Jyrinki |
bug task added |
|
ovito (Ubuntu) |
|
| 2016-06-01 11:58:49 |
Timo Jyrinki |
description |
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 sdrangelove ovito tulip vite
candidates: openscad yade
--- 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 |
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 sdrangelove ovito tulip vite
candidates: openscad yade
--- 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 |
|
| 2016-06-01 12:05:59 |
Timo Jyrinki |
description |
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 sdrangelove ovito tulip vite
candidates: openscad yade
--- 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 |
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: yade
--- 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 |
|
| 2016-06-01 12:06:03 |
Timo Jyrinki |
bug task added |
|
openscad (Ubuntu) |
|
| 2016-06-01 13:48:12 |
Sebastien Bacher |
goldencheetah (Ubuntu): status |
New |
Fix Released |
|
| 2016-06-01 13:56:55 |
Timo Jyrinki |
description |
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: yade
--- 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 |
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: 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 |
|
| 2016-06-01 14:02:33 |
Timo Jyrinki |
description |
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: 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 |
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 |
|
| 2016-06-03 11:09:18 |
Timo Jyrinki |
description |
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 |
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
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. |
|
| 2016-06-03 11:10:00 |
Timo Jyrinki |
description |
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
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. |
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 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. |
|
| 2016-06-03 11:10:08 |
Timo Jyrinki |
description |
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 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. |
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. |
|
| 2016-06-03 11:10:41 |
Timo Jyrinki |
bug |
|
|
added subscriber Ubuntu Package Archive Administrators |
| 2016-06-03 11:11:26 |
Timo Jyrinki |
description |
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. |
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 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. |
|
| 2016-06-03 12:18:07 |
Timo Jyrinki |
description |
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 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. |
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 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 source packages having binaries depending on libqt5core5a package:
goldencheetah # noticed manually first, but also gotten from this filtering
openscad
ovito
qtconnectivity-opensource-src
yade
Of these goldencheetah openscad ovito failed arm64 rebuild. |
|
| 2016-06-21 12:12:25 |
Gianfranco Costamagna |
bug |
|
|
added subscriber LocutusOfBorg |
| 2017-04-01 04:48:58 |
Steve Langasek |
bino (Ubuntu): status |
New |
Fix Released |
|
| 2017-04-01 04:56:32 |
Steve Langasek |
openscad (Ubuntu): status |
New |
Fix Released |
|
| 2017-04-01 04:59:57 |
Steve Langasek |
ovito (Ubuntu): status |
New |
Fix Released |
|
| 2017-04-01 05:00:39 |
Steve Langasek |
sdrangelove (Ubuntu): status |
New |
Fix Released |
|
| 2017-04-01 05:00:51 |
Steve Langasek |
tulip (Ubuntu): status |
New |
Incomplete |
|
| 2017-04-01 05:01:18 |
Steve Langasek |
tulip (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2017-04-01 05:07:24 |
Steve Langasek |
vite (Ubuntu): status |
New |
Fix Released |
|
