No, this was just an observation of a webbrowser-app rebuild. But at the time of when I reported this bug, there already was a new oxide-qt built in yakkety which was built against the new glibc.
No, this was just an observation of a webbrowser-app rebuild. But at the time of when I reported this bug, there already was a new oxide-qt built in yakkety which was built against the new glibc.