=== mnepton is now known as mneptok
[01:02] <tsimonq2> I haven't been able to find much info on this, but why is it that when someone installs python-foo (for example), it installs the Python 2.7 version? Are we supposed to explicitly say python3-foo as if it's a different programming language, or are we still transitioning to Python 3?
[05:57] <Skuggen> mdeslaur, rbasak: Could you try rerunning the failed tests for MySQL 5.7.18? The only one that seems mysql-related is mysql2, and that's an unstable test (it's testing internal server behavior)
[07:04] <rbasak> Skuggen: OK, requested. Cc: mdeslaur
[07:52] <Skuggen> rbasak: diaspora-installer still failing, but it does for multiple other updates as well (e.g postfix and openssl)
[08:54] <rbasak> ^ can someone force-badtest diaspora-installer 0.6.5.0+debian1 on s390x and armhf please?
[08:55] <rbasak> Looks like it bundles gems that are broken :-/
[08:55] <Unit193> \o/
[08:56] <rbasak> Perhaps that should be force-skiptest
[08:56]  * rbasak doesn't know
[10:18] <rbasak> slashd: around?
[10:21] <sil2100> rbasak: I think he's from Canada, so still a bit too early for him
[10:23] <rbasak> Thanks
=== alan_g is now known as alan_g|lunch
[12:04] <slashd> rbasak, I'm here
[12:42] <rbasak> ^ can someone force-badtest (or whatever is appropriate) on diaspora-installer 0.6.5.0+debian1 on s390x and armhf please? It's blocking mysql-server-5.7.
=== alan_g|lunch is now known as alan_g
[15:03] <nacc> rbasak: heya -- sorry for the reconnect here, iwlwifi had a fatal error (??). In any case, did you see my paste from yesterday?
[15:04] <rbasak> nacc: I missed it, sorry. Looking now.
[15:04] <nacc> rbasak: http://paste.ubuntu.com/24648967/
[15:10] <rbasak> nacc: looks good!
[15:11] <nacc> rbasak: i think 4) indicates a bug (import-local with multiple srcpkgs doesn't really make sense, does it?)
[15:11] <rbasak> nacc: "queue" does need pkg/ubuntu/<series>-devel to exist for whatever is is importing. Perhaps that could be optional though. I think it should validate against only each base ref in the end, and perhaps only warn in case of mismatch.
[15:12] <nacc> rbasak: ah ok, not HEAD, i'll adjust
[15:12] <rbasak> nacc: import-local shouldn't complain about that in case of wanting an orphan commit. I have done that in the past to compare things across package renames etc.
[15:12] <nacc> rbasak: ah true
[15:12] <rbasak> nacc: and for simliar reasons I may import-local a package rename.
[15:12] <rbasak> So I think it should warn but not fail in case of mismatch.
[15:13] <nacc> rbasak: right, i'll be more explicit, i think everything should do the validation, but only 3) should treat it as fatal?
[15:13] <nacc> rbasak: and then as we use it, if some case makes no sense to emit a warning, we can figure out a means to disable it
[15:31] <cyphermox> nacc: bug and a wpa log please? ;)
[15:32] <cyphermox> (well, just filing the bug is going to DTRT)
[15:33] <rbasak> nacc: agreed, thanks
[15:33] <nacc> cyphermox: not wpa, iwlwifi driver itself barfed
[15:33] <nacc> cyphermox: i can file a kernel bug, though, yeah :)
[15:34] <cyphermox> nacc: well, just in case ;)
[15:34] <nacc> cyphermox: grr, i'm worried it might be hw issues ... Microcode SW error detected
[15:34] <sil2100> slangasek, infinity, stgraber: hey! Through a recent e-mail vote the DMB granted cking (LP id colin-king) PPU rights to the zfsutils-linux and spl-linux packages - from what I see this requires action from TB (I get a 401 when trying to add the new sources) - could you add those to his PPU list?
[15:34] <cyphermox> that is a common error, I think, it doesn't necessarily mean a firmware issue
[15:34] <nacc> cyphermox: oh ok, i'll look around to see if it's already reported
[15:34] <sil2100> Thanks!
[15:35] <cyphermox> nacc: however, if you're on a thinkpad, there's new firmware if you want to update.
[15:35] <nacc> cyphermox: oh i see, the actual issue is the "queue 2 stuck for 10000 ms"
[15:35] <cyphermox> (I went looking, I had something weird happening in EFI and thought it might help)
[15:35] <nacc> cyphermox: oh interseting, can we do updates to the fw from ubuntu?
[15:36] <rbasak> sil2100: there's some documentation on this in https://wiki.ubuntu.com/DeveloperMembershipBoard/KnowledgeBase. For TB actions, we're currently filing a bug and emailing the TB list.
[15:36] <cyphermox> nacc: on some hardware you can (there's fwupdate/fwupd for that) but I don't think that's available for thinkpads.
[15:36] <rbasak> sil2100: also please don't forget the announcement (documented there too)
[15:36] <cyphermox> nacc: they just ship an iso you can boot directly, so you don't need to worry about whether the OS is supported.
[15:36] <sil2100> rbasak: I did send out the announcement already
[15:37] <nacc> cyphermox: ok, i'll see if the same exist for the yoga :)
[15:37] <rbasak> sil2100: to ubuntu-news-team@? I didn't see that.
[15:37] <sil2100> Oh, no, not that, but I never sent one there before
[15:37] <rbasak> sil2100: also ubuntu-devel@
[15:37] <rbasak> sil2100: see the documentation, that explains it :)
[15:37] <sil2100> Yeah, see it now, is this something new? I don't remember seeing it there ;p
[15:38] <rbasak> Since August, yes :)
[15:38] <sil2100> Missed it completely
[15:38] <sil2100> ...and I was even part of the meeting where we came up with this, duh
[15:39] <sil2100> Well, I only remembered 'sending announcements' but not the mailing lists we agreed to send it to
[16:38] <ktt9> Hi there. I have a question about libbamf and it's default matcher. Should I really query the default matcher every time I want to get desktop file for some xid?
[16:38] <ktt9> Because if I store matcher in static variable and get it only once, it seems that it produces wrong results in some cases.
[16:41] <gsilvapt> wxl, you around?
[16:44] <nacc> ktt9: i think you want to find a more appropriate channel
[16:45] <ktt9> nacc: sorry. What channel should I ask in?
[16:46] <nacc> ktt9: i'm not sure, but this channel is for the development of ubuntu itself
[16:47] <ktt9> Hmm... Maybe it's #ubunty-unity then. Thanks anyway.
[16:48] <nacc> ktt9: or maybe ask a question about the package on lp? https://answers.launchpad.net/bamf/+addquestion
[16:50] <ktt9> nacc: 5 expired questions, last of which is dated 2013 don't look very promising.
[16:52] <nacc> ktt9: yeah :/
[16:52] <jbicha> nacc: askubuntu.com is likely a lot better than LP answers
[16:52] <nacc> jbicha: good point
=== dupondje_ is now known as dupondje
=== mcasadevall is now known as NCommander
=== JanC_ is now known as JanC
[20:43] <tsimonq2> mitya57: Hey there... what's the plan with Qt 5.9 in Artful?
[20:44] <tsimonq2> mitya57: Would it be bad to land 5.9.0 in Artful then update to 5.9.1 when it's out, or are we waiting several more months for 5.9.1 to come out?
[20:45] <tsimonq2> mitya57: I guess IMHO we should get test packages (of 5.9.0) in a PPA and get some feedback from the flavors using it (Lubuntu Next and Kubuntu) and then land once we've fixed any issues that arise.
[20:46] <tsimonq2> mitya57: But you're more experienced than I am in this area, so I'd like to hear your thoughts. :)
[22:35] <nacc> Logan: do you know why you added a delta to src:twig to b-d on language-pack-fr-base instead of locales-all?
[22:37] <nacc> Logan: i think we can sync it again, if that is not necessary
[22:41] <nacc> rbalint: i wonder if you might be able to spend some systemd cycles on LP: #1624317
[22:41] <ubottu> Launchpad bug 1624317 in systemd (Ubuntu) "systemd-resolved breaks VPN with split-horizon DNS" [High,Confirmed] https://launchpad.net/bugs/1624317
[22:42] <nacc> rbalint: it seems like a relatively highly visible bug that pitti did work a bit before, but it also seems like a behavioral regression from 16.04 for many users (there are other bugs duped back to this one and others still open)
[22:42] <nacc> cyphermox: --^ i'm not sure if it's related to what you were looking at for openvpn
[22:49] <rbalint> nacc: i put it on my list, but most likely those cycles will take place next week :-)
[23:09] <nacc> rbalint: np, thanks!
[23:21] <Unit193> nacc: Like sponsoring, or easy merges to fix security issues?  (Deluge, Debian 862611)
[23:21] <ubottu> Debian bug 862611 in deluge-webui "deluge: CVE-2017-9031: directory traversal attack vulnerability" [Serious,Fixed] http://bugs.debian.org/862611
[23:23] <nacc> Unit193: i can probably do that merge tmrw
[23:23] <Unit193> Ah, cool.  That works, thanks.
[23:23] <nacc> Unit193: is an SRU bug filed already? i guess it's needed everywhere?
[23:24] <Unit193> nacc: Not that I know of, but Debian 857903 wasn't SRU'd either.
[23:24] <ubottu> Debian bug 857903 in deluge-webui "deluge: CVE-2017-7178: WebUI CSRF vulnerability" [Important,Fixed] http://bugs.debian.org/857903
[23:24] <nacc> Unit193: i guess due to being in universe
[23:24] <nacc> Unit193: someone has to care enough :)
[23:25] <Unit193> s/$/ to fix in Ubuntu/ :>
[23:25] <nacc> Unit193: yeah :)
[23:25] <nacc> Unit193: i can merge it now, actually, one sec
[23:25] <Unit193> deluge --version → deluge: 1.3.15
[23:26] <Unit193> nacc: Cool, it's pretty easy, and hopefully one way or another won't be needed for long. Debian #863288
[23:26] <ubottu> Debian bug 863288 in deluge "deluge: Recommend python-appindicator" [Wishlist,Open] http://bugs.debian.org/863288
[23:29] <nacc> Unit193: uploaded to artful
[23:29] <Unit193> Danke.
[23:29] <nacc> Unit193: np
[23:49] <nacc> rbasak: if you happen to be available in the AM, i'd apreciate a few minutes to go through what i have for the srcpkg stuff