Submitted: https://github.com/prusa3d/PrusaSlicer/issues/11429
While I have a MP that hides the problem by making tests verbose, I do not want to proceed with it unless absolutely necessary as this is a quite breaking bug for the GUI. ** Bug watch added: github.com/prusa3d/PrusaSlicer/issues #11429 https://github.com/prusa3d/PrusaSlicer/issues/11429 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gmp in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
