[05:25] <jamespage> doko: async being invalid syntax for an argument name with python 3.7 is biting us a bit
[05:25] <jamespage> doko: do we have a cosmic rebuilt test that covers that yet?
[05:26] <jamespage> i.e. with py 37 as part of python3-all
=== maclin1 is now known as maclin
[11:32] <doko> jamespage: no. so for now it's tracking upstream for these patches
[11:40] <rbasak> nghttp2 is stuck in proposed. Valid candidate. update_output.txt reports: "* armhf: nghttp2-client, nghttp2-proxy, nghttp2-server". apt-get seems happy with each of those individually in an armhf cosmic-proposed chdist. Does it need hinting through?
[11:41] <rbasak> Ah, it's tied to jemalloc.
[11:41] <rbasak> Which I think is blocked on a bunch of other things on armhf.
[11:42] <rbasak> Still, I think some attention might be needed to get jemalloc through
[11:43] <Laney> Yep. jemalloc.
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
[13:02] <danialbehzadi> Is there a problem with launchpad?
[13:03] <danialbehzadi> my builds got fail with weird logs:
[13:03] <danialbehzadi> https://launchpadlibrarian.net/377127491/buildlog.txt.gz
[13:08] <danialbehzadi> And that happen only for artful and bionic. Cosmic is fine: https://code.launchpad.net/~dani.behzi/+recipe/traktor
[15:32] <rbasak> ahasenack: so in your opinion bug 1766186 is ready for release to both Xenial and Artful?
[15:32] <ubottu> bug 1766186 in apache2 (Ubuntu Artful) "IncludeOptional fails when a directory does not exist" [Low,Fix committed] https://launchpad.net/bugs/1766186
[15:33] <ahasenack> rbasak: yes,and for the remaining (single) test failure, which is valid, I have an MP and associated sru bug
[15:33] <rbasak> OK thanks
[15:34] <ahasenack> and I have a run that it passes with my fix
[15:34] <ahasenack> showing that*
[15:58] <rbasak> jbicha: any opinion on bug 1778782 please? I'm not particularly familiar with ostree/flatpak from an SRU review perspective, and would appreciate your input.
[15:58] <ubottu> bug 1778782 in ostree (Ubuntu Bionic) "[SRU] New upstream microrelease ostree 2018.6" [Low,In progress] https://launchpad.net/bugs/1778782
[16:23] <rbasak> seb128: still around? On bug 1762595. The Cosmic fixed hasn't migrated yet. Not a problem for an SRU in itself, but the version in the Cosmic release pocket is still 1.36.1-0ubuntu1. If the version in proposed gets deleted, that would cause a problem.
[16:23] <ubottu> bug 1762595 in gvfs (Ubuntu Cosmic) "Thunar incorrectly thinks USB storage device hasn't finished ejecting" [High,Fix committed] https://launchpad.net/bugs/1762595
[16:24] <rbasak> I've not hit this case before. Not sure what to suggest.
[16:25] <rbasak> Anyone have an opinion on how to handle this or whether we need to care? ^
[16:26] <Laney> rbasak: gstreamer was/is in this case, and it was accepted to -proposed without any trouble. There was some debate as to whether it should be released to -updates while it wasn't in cosmic-release, but eventually it was.
[16:28] <Laney> Agreed that it's easy to lose track of uploads in such a situation though.
[16:28] <Laney> I have an SQL query in my UDD history that finds uploads where stable > dev, but it's not really surfaced anywhere.
[16:28] <Laney> s/really //
[16:33] <rbasak> Thanks.
[16:34] <rbasak> We probably don't want to block SRUs for this in the general case.
[16:34] <rbasak> But I'd like another SRU member +1 before accepting I think, seeing as I'm still quite new.
[16:35] <Laney> https://paste.ubuntu.com/p/G6WMZqTMHD/
[16:35] <Laney> that's bionic{-updates} > cosmic
[16:36] <Laney> Most of them have an upload in -proposed, but not e.g. swauth
[16:51] <seb128> rbasak, oh ok, thanks for letting me know but I don't think there is much I can do. I understand if you skip it, let's just hope that the cosmic version doesn't get stucked for too long and make us risk missing bionic .1
[16:55] <mr_lou> Can someone tell me a fix for getting Ubuntu to detect my burner again?
[17:04] <wxl> mr_lou: #ubuntu for support
[17:05] <mr_lou> wxl, Well I asked there too, but last time I had the same problem, they referred me to this channel, which makes sense since it's obviously a bug that was introduced very recently.
[17:06] <wxl> mr_lou: i'd start there, at least
[17:06] <mr_lou> I had the same problem when kernel 4.4.0-98 came. But I could solve it back then by booting an earlier kernel, like 4.4.0-97.
[17:07] <mr_lou> Can't do that anymore. No matter which kernel I boot on, my burner just isn't detected. :-(
[17:07] <rbasak> seb128: I certainly think it's wrong for us to block Bionic over this. I just want to make sure that there isn't some other solution that is preferable.