[07:29] <doko> RAOF: libmiral-dev/amd64 unsatisfiable Depends: libmirclient-dev (= 2.4.0.1.1.1-0ubuntu2)  did you test-install that? ;p
[08:29] <doko> coreycb, jamespage: swift & Python3 ping
[08:50] <RAOF> doko: argh! Did I upload that version? 😐
[08:51] <RAOF> Tomorrow, tomorrow.
[08:52] <RAOF> Maybe launchpad will notice my gog key isn't expired tomorrow...
[08:54] <RAOF> That's what you get for trying to fix lintian errors in... interesting packaging.
[09:01] <seb128> RAOF, hey, do you need some sponsoring?
[09:04] <RAOF> seb128: thanks, but I'll just generate a temporary key until I resolve whatever's going wrong.
[09:04] <seb128> k
[09:08] <RAOF> Hopefully I'll be less jetlagged tomorrow (!)
[09:13] <doko> RAOF: uploaded
[09:18] <RAOF> doko: um, *what's* uploaded? The (hopefully) obvious fix?
[09:25] <doko> RAOF: http://launchpadlibrarian.net/413134775/mir_1.1.1-0ubuntu2_1.1.1-0ubuntu3.diff.gz
[09:58] <RAOF> doko: ta
[10:00] <doko> oSoMoN: LO autopkg tests are not happy in disco with new openjdk 11.0.3 :-/
[10:07] <oSoMoN> doko, it would be interesting to see the results when run against 1:6.2.1~rc1-0ubuntu3 (in disco-proposed atm, blocked by the glibc migration)
=== led_dark_2 is now known as led_dark_1
=== ricab is now known as ricab|lunch
[14:06] <juliank> ugh, flashes of email notifications. testing current xubuntu daily now to see if the livecd-rootfs fixes worked and we don't break encrypted installs anymore :)
[14:08] <juliank> and it does not boot
[14:11] <juliank> but lvm2 and cryptsetup are manual and autoremove returns nothing, so we're all good
[14:13] <juliank> My code is bad, though
=== ricab|lunch is now known as ricab
[14:39] <doko> oSoMoN: persists
[15:59] <LocutusOfBorg> coreycb, do you think this: https://salsa.debian.org/python-team/modules/python-jmespath/commit/414bcc4154c73716e437e6bb9ae1d5487a3fdeac and this: https://launchpadlibrarian.net/357052308/python-jmespath_0.9.3-1_0.9.3-1ubuntu1.diff.gz can be considered equivalent?
[16:05] <coreycb> doko: sorry i didn't ignore you earlier i just thought you were going to have a question after that
[16:06] <coreycb> LocutusOfBorg: yes that's the same
[16:06] <LocutusOfBorg> can I sync?
[16:07] <coreycb> LocutusOfBorg: yes please, assuming the latter is the only diff
[16:07] <coreycb> thank you
[16:08] <doko> coreycb: I assume you are at the sprint. is swift for Python3 on your agenda?
[16:09] <LocutusOfBorg> coreycb, the diff looks like python3.7 compatibility fixes https://salsa.debian.org/python-team/modules/python-jmespath/commit/e08c8d51f8d39448b62c4e5293481489d6c5a090
[16:10] <coreycb> doko: i believe we're in a holding pattern on that until the May sprint. we discussed with xnox recently and our understanding is that python 2.7 won't move to universe until 19.10
[16:10] <coreycb> if upstream doesn't do anything we will likely handle it ourselves next cycle
[16:11] <doko> ok, good to know
=== velix_inuse is now known as velix
[21:08] <superm1> Hi, I just wanted to make sure bug 1814997 is on someone on the security team's radar.  it's going to block gnome-software, fwupd and fwupd-signed migration in disco
[21:08] <ubottu> bug 1814997 in libxmlb (Ubuntu) "[MIR] libxmlb" [Undecided,Triaged] https://launchpad.net/bugs/1814997
[21:08] <superm1> robert_ancell: ^
[21:09] <robert_ancell> yep
[21:14] <chiluk> thanks for sru approval bdmurray++ I'll validate it this weekend.