[07:27] tdaitx: it is fixed [08:12] doko: any news on expected date for the -security copy? [14:02] tdaitx: is the unattended upgrade test done? [14:05] no, not yet done [14:23] tdaitx: there's one new issue saying that gtk3 l+f doesn't look well on bionic [14:23] what else is missing? [14:28] tdaitx: what about #1821235? [14:35] what's the one about gtk3 l+f ? [14:36] ok, found it [14:38] last comment in the big one [14:43] yeah, looking into that... I am not that familiar with the LaF logic for themes and how the GTK LaF actually works [14:43] the user says it is because Ambiance (from ubuntu-themes) does not have a good support [14:48] that does not seem to be the cause though, there's a very small difference between ubuntu-themes in cosmic/bionic and disco, and I don't see problems with the GTK LaF in Disco... will test scilab and jabref in qemu to check that [17:47] now https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1821768 [17:50] tdaitx: so maybe removing the gtk2 support from openjdk-11 was a little bit premature :-/ [18:22] doko: wait, this is the exact same as the one in 1814133, right? you asked Amr to open a new bug [18:24] tdaitx: yes [18:26] tdaitx: so, what needs to be done from your point of view for the push to the -security pocket? [18:31] I think we just need to get the stuff you listed as TODO: check gtk3 and the disco FTBFS [18:33] for gtk3 I am looking if we need additional backports from gtk packages or openjdk upstream [18:33] and the disco ftbs afaics was caused by the build helper (we could move the update ahead without that disco fix, vorlon said before that we don't necessarily need to have every fix in disco as well, as long as we have a plan to fix it)