A few notes. I don't know if it helps: The Debian maintainer tried building graphite2 with gcc-14 on ppc64el because the nametabletest was failing with gcc-15: https://github.com/silnrsi/graphite/issues/96
See the 1.3.14-5 logs at https://buildd.debian.org/status/logs.php?pkg=graphite2&arch=ppc64el At the time, Ubuntu's ppc64el was not failing with gcc-15, so that's why I synced 1.3.14-5 instead of later revisions: https://launchpad.net/ubuntu/+source/graphite2/1.3.14-5 Debian's build was failing with gcc-15 15.2.0-4. Ubuntu's was passing with 15.2.0-4ubuntu2 ** Bug watch added: github.com/silnrsi/graphite/issues #96 https://github.com/silnrsi/graphite/issues/96 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/2120856 Title: graphite2: questing autopkgtest failures Status in graphite2 package in Ubuntu: New Bug description: The autopkgtests for graphite2 have started failing in questing, with the following summary: 246s The following tests FAILED: 246s 82 - featuremaptest (Not Run) 246s 83 - grlist (Not Run) 246s 84 - jsontest (Not Run) 246s 85 - jsontestOutput (Failed) 246s 86 - nametabletest (Not Run) 246s 87 - sparsetest (Not Run) 246s 88 - utftest (Not Run) 246s 89 - vm-test-call-threading (Not Run) 246s 90 - vm-test-direct-threading (Not Run) See full logs: https://autopkgtest.ubuntu.com/results/autopkgtest- questing/questing/amd64/g/graphite2/20250818_080559_20996@/log.gz#S8 This is likely a fallout from the gcc-15 transition. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/2120856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
