[09:35] <doko> smb: you merged iproute2 last. Please could you have a look at the failing autopkg tests? or maybe merge it again before ff ?
[09:35] <smb> doko, ack, will have a look
[10:03] <smb> doko, hm, would /bin/sh change of argument list size ring any bells? That seems to be the cause. I am not sure another merge will help, though I want to do it regardless to sync with kernel versions
[10:13] <doko> smb: aren't these practically unlimited these days?
[10:14] <smb> doko, I would have thought so... but "make: execvp: /bin/sh: Argument list too long" sounds differently
[10:19] <smb> anyhow, will dig a bit more after lunch
[12:14] <jbicha> doko: pygobject builds (except on s390x) once we sync glib2.0 from experimental, but I was told to be more cautious about syncing until the big qt/ffmpeg transition finishes
[12:14] <jbicha> doko: see bug 1787474
[12:21] <doko> jbicha: cautiousness seems to be a good advice =)
[12:24] <jbicha> I'm not working on the s390x issue. https://gitlab.gnome.org/GNOME/pygobject/issues/247 upstream wishes we had a pytest-faulthandler package
[13:27] <ahasenack> doko: hi, good morning/afternoon. ldb is a sync, and stuck in proposed because it needs talloc >= 2.1.13, are you about to merge that by any chance?
[13:27] <ahasenack> debian has 2.1.14
[13:52] <abeato> sil2100, https://github.com/CanonicalLtd/ubuntu-image/pull/158 is ready for review - there are some CI error but those do not look related to the PR
[17:32] <wxl> i just notice the live cd for lubuntu (and kubuntu, haven't tested others) has an empty menuentry in grub for "boot to first hard disk." what do i change to fix this?
[17:33] <ahasenack> hi, can someone please sync ldb from debian? It fixes the FTBFS for arm, ppc and s390x
[17:33] <ahasenack> ldb (2:1.4.0+really1.3.5-2) unstable; urgency=high
[17:33] <ahasenack>   * Add patch from upstream to fix FTBFS on some arches (arm64, armhf, mips,
[17:33] <ahasenack>     mipsel, s390x, ...)
[17:33] <ahasenack> ours: https://launchpad.net/ubuntu/+source/ldb/2:1.4.0+really1.3.5-1 (see the build failures)
[17:37] <ahasenack> https://salsa.debian.org/samba-team/ldb/commit/81ac821d1ba0c7b39c53b5e7174155a559063e0d patch debian used
[17:40] <mdeslaur> ahasenack: sure, one sec
[17:40] <ahasenack> mdeslaur: thx!
[17:40] <mdeslaur> ahasenack: synced
[17:40] <ahasenack> \o/
[17:44] <ahasenack> mdeslaur: \o/ it build successfully on s390 and ppc already: https://launchpad.net/ubuntu/+source/ldb/2:1.4.0+really1.3.5-2
[17:44] <ahasenack> built*
[17:44] <mdeslaur> sweet :)
[17:45] <ahasenack> that was fast
[18:42] <wxl> ^^ regarding the issue booting to first disk on the live cd, it affects ubuntu as well. as far as supported releases go, it seems that has been this way since xenial
[18:42] <wxl> trusty works. it's possible utopic, vivid, wily didn't.
[19:25] <Odd_Bloke> GNOME have moved some of their bug tracking from Bugzilla to Gitlab, do we have a way of linking to such upstream bug reports from Launchpad?
[19:35] <jbicha> Odd_Bloke: not yet, see bug 1738870
[19:39] <aleb> Hi, I see this bug: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1748787 "pitivi crashed with AttributeError in ..." but I don't see any C backtrace, only a Python traceback in the bug description. The traceback cannot cause a crash/segfault, so I'm wondering why the bug title says "crash", any clue?
[21:31] <ahasenack> hi, can someone please accept the xenial task of this bug? https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1771340
[21:32] <sarnold> looks like osmeone beat me to it :)
[21:32] <ahasenack> thanks anyway :)
[21:34] <Unit193> Hm, that reminds me of the whole openssl 1.1 / openssh thing...
[23:23] <mwhudson> how much ram do the ppc64el autopkgtest workers have?