> What about Cosmic? Has anyone actually checked that > the packages still work on Cosmic?
why should we? We cannot afford doing test rebuilds for every supported release at the same time. And this is such an issue found for the test rebuilds. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact ------ libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case --------- Does libunistring build successfully? Regression Potential -------------------- We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report ------------------- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create ======================== glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
