[12:50] <ahasenack> xnox: I got two +1s in https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1833039
[12:50] <ahasenack> xnox: I'll prepare the sru
[12:51] <ahasenack> I used https://git.launchpad.net/~ahasenack/ubuntu/+source/apache2/tree/debian/patches/disable-ssl-1.1.1-auto-retry.patch?h=bionic-client-cert-auth-fix
[12:52] <ahasenack> just the first hunk of that upstream commit. The other bit is for tls v1.3 from what I could tell, which is not enabled in that apache version
[12:53] <xnox> nice
[13:58] <xnox> mvo:  do you have the power to approve subiquity.pot on https://translations.launchpad.net/ubuntu/+imports?field.filter_extension=pot&field.filter_status=NEEDS_REVIEW&batch=75&direction=backwards&memo=2400&start=2325 ?
[13:59] <mvo> xnox: let me look
[13:59] <xnox> i think ~katie can, and i guess the launchpad translator admins....
[14:00] <xnox> mvo:  if you can't, i might need to invoke c j watson
[14:00] <mvo> xnox: I just checked, I can't
[14:12] <cjwatson> mvo: I'm pretty terrible with the translations app, but I think I've managed to do it
[14:13] <mvo> xnox: -^
[15:00] <sil2100> !dmb-ping
[15:03] <xnox> mvo:  cjwatson: thanks! it looks like it worked, because https://translations.launchpad.net/ubuntu/+source/subiquity now looks populated
[18:29] <mitya57> infinity, doko: I get this error on arm64 and armhf when building qtquickcontrols-opensource-src in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3709/+packages:
[18:29] <mitya57> /usr/bin/ld: error: /usr/lib/gcc/aarch64-linux-gnu/8/../../../aarch64-linux-gnu/crti.o(.plt) section size (0xf20 bytes) is larger than file size (0x5a0 bytes)
[18:29] <mitya57> Is it a bug in glibc?
[18:31] <mitya57> Oh, now happens with qtwebengine too, with a different file name:
[18:31] <mitya57> /usr/bin/ld: error: /usr/lib/gcc/aarch64-linux-gnu/8/../../../aarch64-linux-gnu/Scrt1.o(.plt) section size (0xa40 bytes) is larger than file size (0x6a8 bytes)
[18:31] <mitya57> Did not happen on Friday 2019-06-28, so something recent broke it.
[18:32]  * mitya57 blames today's binutils upload
[18:53] <doko> mitya57: no, most likely https://sourceware.org/ml/binutils/2019-07/msg00019.html
[18:55] <mitya57> doko: so “no” to my first guess (bug in glibc) but “yes” to my second guess (blaming today's binutils upload), right?
[18:56] <doko> yes, likely
[19:20] <seb128> mitya57, thx for mentioning it, I had a similar error in activity-log-manager today and was wondering what it could be
[19:22] <seb128> oh, and gnome-calendar is the same
[19:23] <seb128> so looks like any armhf build?
[19:24] <seb128> doko, should we remove the binutils from eoan-proposed meanwhile to unscrew archive builds?
[19:24] <doko> seb128: if you remove all depending builds as well, sure
[19:25] <seb128> why would that be needed?
[19:25] <seb128> diff is missing on https://launchpad.net/ubuntu/+source/binutils/2.32.51.20190701-1ubuntu1 :-/
[19:43] <seb128> doko, so what do you suggest doing? we should at least sent a fyi email to the mailing list so others don't waste time trying to understand what's going on
[19:53] <doko> uploading a fixed binutils
[19:57] <mitya57> By the way Debian experimental is affected too.
[20:04] <vorlon> doko: does that mean you are suggesting someone else upload a fixed one, or are you saying that you are uploading a fixed one?
[20:15] <doko> I am currently building
[20:29] <seb128> doko, thx
[23:20] <vorlon> doko: whoopsie still FTBFS w/ binutils 2.32.51.20190701-1ubuntu2