[00:45] does anyone see what happened here? https://launchpadlibrarian.net/325167198/buildlog_ubuntu-artful-s390x.vim_2%3A8.0.0197-4ubuntu3_BUILDING.txt.gz [00:51] no idea. but I got a giggle out of this "Test BufferLength and BufferAssSlice" [00:58] hah === maclin1 is now known as maclin [03:53] so who's blindly retrying haskell package builds to punish me? :) [03:55] ugh [03:56] I don't know what you did to deserve thjat but that's a mean thing to do to someone [03:56] sarnold: what I did was upload no-change rebuilds for the transition, now someone's retrying them without looking at the build logs ;) [04:00] slangasek: I've been getting emails on artful-changes. [04:00] slangasek: he-who-is-never-on-irc :P [08:06] slangasek: ah. So you think it's appropriate to be there, just not in the minimal seed? I must have got you confused with someone else saying it was deprecated and should be removed altogether. === girish946 is now known as Guest32166 [09:19] Hey! Anyone here could force ignore octave-io's failing armhf test? Checking the logs it's been failing for longer and from the logs (and one re-run) I see that random tests seem to be failing, not the same ones everytime [09:19] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#octave-io [10:24] sil2100: i cannot even see where it was ever successful, but britney seems to think it was [10:26] sil2100: i don't know if it matters, but #ubuntu-release is usually the channel for that [10:30] ginggs: thanks! [12:59] Any MOTUs or core devs here who could take a look at LP: #1699333 and LP: #1699334 please? [12:59] Launchpad bug 1699333 in Ubuntu "[needs-packaging] vala-panel" [Wishlist,Confirmed] https://launchpad.net/bugs/1699333 [12:59] Launchpad bug 1699334 in Ubuntu "[needs-packaging] vala-panel-appmenu" [Wishlist,Confirmed] https://launchpad.net/bugs/1699334 [13:00] I'd like to include there in Ubuntu MATE 17.10 Alpha 1. Ubuntu Budgie are interested in the packages too. [13:00] flexiondotorg, how come you are not MOTU yet? ;-) [13:00] Long term I'll ask the DMB to add them to my packageset so I can maintain them. [13:00] seb128 I know right. [13:01] On the long list of "stuff I should do". [13:01] flexiondotorg, replying to your direct question, I can try to have a look on monday but today is just too busy with things I've to do already [13:02] seb128 Thanks. [13:02] If anyone is able to improve on seb128's kind offer, I'd appreciate it :-) [13:02] flexiondotorg: apply to be a Debian Maintainer too :) [13:02] jbicha In progress :-) [14:23] rbasak: I think I may have said at one point that it was deprecated, but I may have been wrong ;) [14:26] slangasek: no problem. I think we're all clear on it now. Well, to be clear, ethtool is staying seeded, but not in minimal since it doesn't need to be in minima. [14:26] l [14:39] somebody know what's wrong with https://launchpad.net/ubuntu/+source/opencv/3.1.0+dfsg1-1~exp1ubuntu1/+build/12795080 ? [14:39] sbuild-build-depends-opencv-dummy : Depends: libvtk6-dev but it is not going to be installed [14:40] not really geared to test installation issues of !x86 in ubuntu (and I don't use dose, etc) [14:58] awe_, hey, I see that you did some extensive testing on bug #1585863 a while back, would you be able to test Aron's packages in https://launchpad.net/~happyaron/+archive/ubuntu/nm-oem/+packages to confirm the fix on xenial by any chance? [14:58] bug 1585863 in OEM Priority Project xenial "WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it." [Critical,Triaged] https://launchpad.net/bugs/1585863 [15:13] oSoMoN, I can take a look, but from my recollection, the bug was considered fixed when a new version of network-manager was SRU'd [15:13] so Aaron's patches weren't required [15:14] see comment https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/comments/94 [15:14] Launchpad bug 1585863 in OEM Priority Project xenial "WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it." [Critical,Triaged] [15:15] four dollars re-opened the bug based on two comments with zero details [15:25] awe_, yeah, after reading all the comments in the bug it wasn't clear to me either that the patches were required [15:25] if 1.2.6-0ubuntu0.16.04.1 that's in xenial already fixes the issue, then perfect [15:30] FourDollars: I know it's EOW for you, but when you get a chance would you mind commenting on bug #1585863 to clarify the situation? [15:30] bug 1585863 in OEM Priority Project xenial "WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it." [Critical,Triaged] https://launchpad.net/bugs/1585863 [15:30] thanks! [15:32] oSoMoN, I added an additional comment to the bug [15:32] which provides a method for checking whether the bug has been hit or not [15:32] the problem is that sometimes when coming out of S3 [15:33] NM failed to initiate WiFi scanning [15:33] and if it doesn't scan [15:33] it can't detect APs [15:33] which means it's re-connect to APs [15:33] awe_, thanks, that’s very helpful! Hopefully 1.2.6 did fix the issue, and no more work will be needed on that one [15:34] let’s see if F_ourDollars can clarify the situation [15:39] willcooke might also be interested to hear that this has been re-opened [15:39] * willcooke reads [15:39] (maybe "interested" isn't the right word) [15:39] ;)- [15:40] hqa [15:40] ha [15:40] Yeah, so I /think/ it is fixed. But I was confused by that bug as well [15:41] Pretty sure we'd be hearing a lot more about it if it was still broken. But good to be sure [15:41] oSoMoN: Aron's patch is still needed. Please check the bug comments again. [15:42] FourDollars, thanks mate, I’ll work on the SRU then [15:42] based on what evidence? [15:42] oSoMoN: Thx a lot. [15:43] willcooke, can we bring jbicha into the conversation? [15:43] awe_, I don't think he'll know about this one, he's only done the merge from Debian (n-m 1.8) [15:44] the bug doesn't even say *which* patch is required [15:44] yeah, I think this might be a red herring [15:44] I gotta take off for today, I’d appreciate if relevant bits of the conversation could be saved to the bug report [15:44] oSoMoN, sure thing [15:44] thanks! [15:44] I think my comments says it all [15:45] we need proof something is broken before we decide a patch is needed [15:59] somebody can guess what's wrong with https://launchpad.net/ubuntu/+source/opencv/3.1.0+dfsg1-1~exp1ubuntu1/+build/12795080 ? ← slangasek ? (given you seemed so interested ^^) [16:05] mapreri: you might be able to decipher it using chdist to see why it might be uninstallable on that arch [16:13] ok, it's due to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865465 [16:14] Debian bug 865465 in src:openmpi "openmpi FTBFS on s390x: undefined reference to opal_atomic_*" [Serious,Fixed] [16:14] mapreri: http://paste.ubuntu.com/24933694/ [16:14] mapreri: it's uninstallable with artful-proposed on s390x [16:14] yeah, got to it [16:14] eventually [16:14] pity, but should be fixed by the next autosync, theoretically [16:38] mdeslaur: have you seen LP: #1700079 ? I am unconvinced from the description that it's a regression vs. a race-condition in the systemd unit [16:38] Launchpad bug 1700079 in openvpn (Ubuntu) "openvpn broken after unattended security upgrade" [Undecided,New] https://launchpad.net/bugs/1700079 [17:25] slangasek: that's from adac and/or frickler in #ubuntu-server earlier today. Two people reported the same thing, so I asked for a bug report. [17:57] slangasek: btw mdeslaur is out for the weekend [18:29] sarnold: ok. would someone else from security look at this, should I assign the bug to him so he sees it on his return? [18:30] slangasek: probably best to assign it to him, none of us spotted anything in postinsts or unit files or elsewhere. :/ I'm not even sure if this is expected or not. Is it? [18:31] sarnold: it is not expected that restarting the server on upgrade fails? [18:32] slangasek: hrm. I read too quickly I thought that was the hanging clients that everyone experienced.. hrm. [18:40] slangasek: the curious thing is it only happening with unattended upgrades, both reporters in #ubuntu-server last night were unable to reproduce it outside of that. Though it could just be unattended upgrades making it easier to lose whatever race is happening. [18:41] sbeattie: how many times did they try outside of unattended-upgrades? sample size of 4 isn't much to draw conclusions from [18:43] slangasek: unknown [19:06] hello apw, how do you feel about suricata sync/merge?