[00:04] <teward> so, is Lua 5.1 going to continue to be in 'main' in Xenial or are there plans to make it Universe or something going forward?
[00:11] <doko_> teward, any action on demoting this would be appreciated
[00:13] <teward> doko_: the reason I asked is because nginx-extras will lose a feature I know a ton of people use
[00:13] <teward> i think that and Apache were reasons for it staying in Main with 14.04
[00:13] <sarnold> "ton"? :)
[00:13] <teward> sarnold: substantial percentage of people using nginx
[00:13] <teward> exact # unknown, but i've posed questions to the world 'bout the lua dropping and it was met with negativeness
[00:13] <sarnold> teward: interesting. I still haven't run into any mentions of it casually..
[00:13]  * teward yawns
[00:14] <teward> sarnold: your name isn't on the 'last uploaded by' field
[00:14]  * teward gets a lot of emails :/
[00:14] <sarnold> hehe
[00:14] <teward> point not withstanding
[00:14] <teward> if lua 5.1 is demoted, it drops from nginx as a build dep
[00:14] <teward> which means dropping Lua module in the universe packages
[00:14] <teward> which I don't particularly mind (Lua module users have the PPA which isn't bound to the Main restricts)
[00:15] <teward> but while i'm stabbing the merge right now... :P
[00:15] <teward> thought i'd ask about the state of lua 5.1 and whether dropping is planned by 16.04 release
[00:15] <teward> (dropping from Main, that is)
[00:15] <sarnold> teward: obligatory reminder, please keep http/2 off for now..
[00:15] <teward> sarnold: ack
[00:16] <teward> sarnold: note that the SPDY users will hate you and the Sec team for that
[00:16] <sarnold> I'd really rather that code have a few more eyes and fuzzers thrown at it before we throw it live into an lts :)
[00:16] <teward> since there's no SPDY in nginx
[00:16] <sarnold> I know, heh
[00:16] <teward> sarnold: um... you were here for the Tech Board meeting right?
[00:16] <teward> sarnold: by release it'll be near the 1.9.x branch, with 1.10.x as an after-release update
[00:16] <sarnold> but I feel marginally good about getting SPDY removed from libmicrohttpd before that moved to main..
[00:16] <teward> at least, as it was discussed with the TB before the "SRU" changes
[00:16] <teward> HATE my laptop >.<
[00:17] <sarnold> but I feel marginally good about getting SPDY removed from libmicrohttpd before that moved to main..
[00:17] <teward> sarnold: perhaps you, me, and rbasak should butt heads before I upload
[00:17] <sarnold> teward: yeah, I know it's not ideal, but turning it on via sru feels much better to me than shipping with it on before the start :)
[00:17] <teward> 'cause I understand the Sec Team's opinion, but the users will kill me :P
[00:19] <doko_> tedg, seriously, can you remove the dependy on lua5.1?
[00:19] <doko_> teward, ^^^
[00:22] <teward> i reiterate: hate hate hate hate HATE my laptop sometimes
[00:22] <teward> doko_: not without dropping the Lua module from nginx-extras
[00:22] <teward> which rbasak and i have argued about in the past
[00:22] <teward> namely with the impending liblua5.1 'demotion'
[00:23] <teward> doko_: doesn't address the Apache dependency though
[00:23] <teward> doko_: if it's an 'order from above' I'll drop the Lua 5.1 dep
[00:23] <teward> but it's getting a release notes notice
[00:23] <teward> sarnold: i'll drop HTTP2 support then
[00:23] <teward> sarnold: it's your fault i now have to maintain even *more* of a delta
[00:23] <sarnold> teward: sorry...
[00:23] <teward> until 1.10.x
[00:23]  * teward yawns
[00:23] <sarnold> teward: but thanks for that :)
[00:23] <teward> sarnold: also not my fault Debian enabled it
[00:24] <sarnold> it makes perfect sense for it to be enabled in e.g. debian unstable, debian testing, etc. maybe a bit premature for a debian-stable..
[00:24] <teward> (the HTTP/2 stuff also is getting a release notes note too, I believe)
[00:24] <sarnold> sure, feel free to blame us if it helps :)
[00:24] <teward> sarnold: well, there's a backports-failure problem there
[00:24] <teward> sarnold: my mind's on low-coffee mode
[00:24] <doko_> teward,we should resolve to at least two lua versions for xenial
[00:25] <teward> send me $5, coffee will be in my system, and the blaming goes away
[00:25] <teward> doko_: what's currently in Main then for Xenial, 5.1 and 5.2?
[00:25] <teward> (I remember 5.2 was a headache at 14.04 because it's essentially a different beast)
[00:25] <doko_> teward, it would be 5.3 and another version
[00:26] <doko_> currently we have three, 5.1, 5.2 and 5.3
[00:26] <teward> doko_: has the Apache package managed to resolve the liblua5.1 depends, or dropped Lua entirely?
[00:26] <teward> doko_: the reason I ask that is the initial "Lua 5.1 dependency" issue was in a bug against both
[00:26]  * teward digs it up
[00:26] <teward> ... it'd help if Chrome weren't slow
[00:26] <teward> and my computer didn't hard-reboot on me
[00:27] <teward> https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1324062
[00:27] <teward> doko_: that's got an nginx and an Apache message
[00:27] <teward> filed by rbasak of course
[00:27] <teward> it looks like Apache's resolved it
[00:27] <teward> or not
[00:28] <teward> doko_: the options for nginx are "keep lua5.1 or drop Lua module"
[00:28] <doko_> teward, lua is insane, so getting everything to 5.3 would be preferred. if that's not possible, have *one* legacy version
[00:28] <teward> it's a third party module
[00:29] <teward> doko_: 5.1 would have to be the legacy then, if only to satisfy Apache and nginx headaches
[00:29] <teward> but here's the real reason my options are "Drop Lua module" or "Convince 5.1 to be kept": https://github.com/openresty/lua-nginx-module/issues/343
[00:29] <teward> the third-party authors have "Won't Fix"'d the "Support 5.2+" thing
[00:31] <doko_> teward, so what needs to be done to remove 5.2?
[00:33] <teward> doko_: nothing
[00:33] <teward> at least, not from me
[00:33] <teward> nginx doesn't depend on 5.2
[00:34] <teward> doko_: nginx-extras and the Lua module depends on 5.1
[00:34] <teward> so if 5.1 is the legacy version kept, then I don't have to do anything
[00:34] <teward> and then I get concerned at 18.04 or next LTS about 5.1 dying
[00:34] <teward> i would check the Apache deps though
[00:35] <teward> they may need 5.2
[00:35] <teward> doko_: the question is, do we keep 5.1 or 5.2
[00:36] <teward> and if the answer is 5.2, then nginx-extras (universe) loses the Lua module
[00:36] <teward> and a notice goes out to those users to switch to the PPAs instead
[00:36] <teward> sarnold: oh, i reminded myself, any chance the SRU to turn on HTTP/2 can go out as a sec update as well as SRU?  Odd request, but the reason I ask is that 1.10.x is supported when 1.9.x is 'dead' come 1.10.x's release and SRUing
[00:37] <teward> sarnold: those who only use the security repos in addition to the base main repos would miss
[00:37] <sarnold> teward: though missing it would be part of the reason for sticking with -security rather than -updates :)
[00:38] <teward> sarnold: well, you have two issues then:
[00:38] <teward> (1) HTTP/2 is never available
[00:38] <teward> (2) last minute fixes between 1.9.x final and 1.10.x which could be security in nature are missed
[00:38] <teward> and esp. if dynamic module support becomes a thing then that's seriously missed
[00:38] <teward> (and a major hell-hole is opened)
[00:38] <sarnold> teward: if there's bits in #2 that justify an update, then it could be included
[00:38] <doko_> teward, I disagree, please see http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.txt
[00:38] <Unit193> Didn't you just claim a lot of the users use the PPA anyway?
[00:38] <teward> Unit193: 14.04 users, mostly
[00:39] <teward> Unit193: because it's outdated in the repos
[00:39] <doko_> teward, I don't care about 5.1/5.2
[00:39] <teward> doko_: what do i look for under the mismatches
[00:39]  * teward isn't pro at reading yet :/
[00:40] <doko_> teward, getting 5.1 or 5.2 demoted
[00:41] <sarnold> doko_: there are no references to "5.2" in that file and the only references to "52" appear unrelated (a52dec, golang-gettext)
[00:43] <doko_> sarnold, teward: "appear unrelated", please can you explain?
[00:43] <teward> doko_: wasn't sure what you wanted me to look for is all
[00:43]  * teward yawns
[00:43] <teward> though sarnold knows more about that file
[00:43] <teward> i don't see Lua 5.2 in there though
[00:43] <teward> nor 5.1
[00:43] <sarnold> doko_: I do not know how a52dec or golang-gettext are at all related to lua 5.2.
[00:43] <teward> and the only Lua stuff I see there is libluajit
[00:44] <teward> which isn't a factor in nginx (and dropped actually during the merge)
[00:44] <teward> (though Debian has that for one of the 'rare' arches)
[00:45] <doko_> sorry guys, I'm afk. will look at that tomorrow
[00:45] <sarnold> night doko_ :)
[00:45] <teward> 'night
[00:45] <teward> sarnold: build-testing the no-http2 stuff now
[00:45] <teward> and in other news my hands hurt
[00:49] <teward> sarnold: mind doing me a favor by the way and state it's a Sec Team mandate on the merge bug to disable HTTP/2
[00:49] <teward> (https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1510096)
[00:49] <teward> that way if users complain I point there
[00:52] <teward> ehh, nevermind, i'll add it myself
[00:52] <sarnold> done
[00:52] <teward> oop speed is speed xD
[00:52] <teward> that works
[00:52] <teward> though SPDY is *gone*
[00:53] <sarnold> yay :)
[00:53] <sarnold> heh
[00:54] <teward> been gone since HTTP/2 was introduced
[00:55] <teward> sarnold: i'm ACKing that but adding in a note on SPDY.  I assume we'd be OK with HTTP/2 being enabled in 1.10.x when it lands, SRU or otherwise?
[00:55] <sarnold> teward: preferable 1.10.1 or .2 :)
[00:55] <teward> ok
[00:55] <teward> ehh
[00:56] <teward> sarnold: i question that, because theres zero guarantee of a 1.10.1
[00:56] <teward> consider the current stable branch
[00:56] <teward> 1.8.0 has received no updates, bugfixes, etc. since April release
[00:56] <sarnold> hmm. that's either really good or really bad :)
[00:56] <teward> and in April 2016, it gets torpedoed
[00:57] <teward> and the next stable is released
[00:57] <teward> sarnold: indeed, this was brought up in the TB discussion as well
[00:57] <teward> sarnold: security patches can probably be done easily
[00:57] <sarnold> If my pessism is correct, there'll be a .1 :)
[00:57] <teward> but that doesn't resolve the number of 16.04 LTS users who are going to be "Hey, where's HTTP/2?"
[00:57] <teward> (and after 16.04 release, I'll be pointing at the Sec Team, and saying "all complaints to there")
[00:57] <teward> or rather, the users will
[00:57]  * teward yawns
[00:58] <teward> i need to stop working on this at some point, i've been working on this since 11AM :/
[00:59] <teward> sarnold: i think Stable only gets fixes if there's a huge security hole that needs patching, or a major bug
[00:59] <teward> but I can pass that to NGINX and ask
[00:59] <teward> (or you can, if you can get LinuxJedi when he's around xD)
[01:03] <rbasak> doko_: AIUI, 5.1 and 5.2 are essentially different incompatible languages. Like Python 2 and Python 3. Or so I've been told.
[01:04] <rbasak> doko_: I understand that you don't want to maintain 5.1 and 5.2 and 5.3. That's reasonable.
[01:04] <rbasak> doko_: but OTOH pushing upstreams to move up is difficult because of the backwards incompatibility.
[01:05] <rbasak> doko_: I think Ubuntu should pick one, file bugs with upstreams as needed, and then drop support if that version is not supported by upstream.
[01:05] <rbasak> doko_: I don't think the latest is necessarily the right one to pick though. The most commonly supported version is maybe a better criterion.
[01:06] <doko_> rbasak, I agree, so should it be 5.1 or 5.2?
[01:06] <rbasak> doko_: I don't know enough about lua or what upstreams support to answer that unfortunately.
[01:07] <rbasak> doko_: whatever we pick, I'd like a researched statement to point people to if they complain about lack of support.
[01:08] <rbasak> Eg. (I'm making this up) "lua 5.1 was supported by A, B and C upstreams, but not D, lua 5.2 was supported by X, Y and Z, so we decided to go with 5.1 to maximise upstream support, and your upstream lost out, sorry".
[01:08] <teward> oh hey rbasak is alive
[01:08] <sarnold> I haven't heard of any complaints about migrating from 5.2 to 5.3. I think people have the emotional attachment to 5.1 and want to keep that one.
[01:08] <teward> rbasak: check PMs
[01:08] <teward> sarnold: actually, 5.1 -> 5.2 is like dealing with almost completely different languages, from the Lua coders I know when I posed them that question
[01:08] <teward> (they use Lua for a lot of things, not just nginx)
[01:09] <sarnold> I just don't htink anyone would cry about losing 5.2. They're either on 5.1 or they paid the price and moved forward, and moving again to 5.3 is probably no big deal.
[01:10] <teward> +1 for sarnold's interpretation here
[01:10] <rbasak> sarnold: the trouble is that we have to pick one version for all upstreams in main. If the upstream doesn't happen to support that (too new or too old for them) then that's unfortunate.
[01:10] <rbasak> Eg. a diligent upstream could have moved to 5.3 and dropped support for anything older.
[01:10] <rbasak> And we might end up with only 5.1 in main.
[01:11] <sarnold> rbasak: both 5.1 and 5.2 are in main from T through X
[01:11] <sarnold> rbasak: 5.3 is in main since W
[01:12] <sarnold> rbasak: doko wants at most two :) I think 5.1 and 5.3 would please maximal number of people, but you're right, some research would be worthwhile.
[01:12] <rbasak> sarnold: we can arbitrarily change that for X though, if doko agrees. Eg. if we decide 5.1 is best, then we could just ship 5.1 in main in X.
[01:13] <sarnold> rbasak: heh, in the case that 5.2 and 5.3 basically killed the lua community?
[01:13] <rbasak> I get the impression it's just fragmented a little. The lua use case doesn't need to stick to one version across all projects that use lua.
[01:14] <rbasak> But general distributions do need that.
[01:15] <rbasak> So that comes down to "if you want general distros to ship projects with lua support, then move together, otherwise we'll be forced to pick for you".
[01:15] <rbasak> MOre specifically, this applies to Ubuntu with a main/universe distinction. But Debian probably doesn't want to release three at once either.
[01:16] <sarnold> "we're sorry your upstreams pulled a python"
[01:17] <rbasak> I don't think it's quite the same. We'd have to compare to projects using libpython for it to be a fair comparison.
[01:19] <doko_> rbasak, teward: any foreward progress on 5.1 and any of 5.2 or 5.3?
[01:19] <teward> doko_: zero for the nginx lua module
[01:19] <teward> upstream's outright rejected the notion
[01:20] <teward> for going off of 5.1
[01:20] <teward> rbasak has better gauge of the state of Server in general
[01:22] <rbasak> doko_: I'm not aware of any progress whatsoever. I'm not interested in pushing upstreams either though. I'm happy with going with the popular choice and dropping lua support at build time for any upstreams that don't support that choice.
[01:23] <teward> ^ that's my opinion as well
[05:38] <pitti> Good morning
[07:11] <alkisg> Good morning
[07:11] <alkisg> pitti: Hi, I'm around if you need any more feedback or vnc for https://bugs.launchpad.net/bugs/1492546
[07:14] <pitti> alkisg: thanks for the journal, looks good now!
[07:14] <pitti> alkisg: I'll ponder that
[07:14] <alkisg> Thank you
[08:10] <dholbach> good morning
[08:22] <xnox> Laney, i wonder if i broke transition tracker
[08:29] <xnox> Laney, nah, all is good.
[08:29] <xnox> jodh, morning =)
[08:50] <ginggs> pitti: good morning. i'm having issues with julia autopkgtest again. amd64 is good now, but i386 has a regression (it runs, but very slowly) that might only be fixed by a new llvm. is it possible to disable autopkgtests for i386, or forget that it was ever successful?
[09:07] <pitti> ginggs: we can do the latter, yes; or it needs a sourceful upload to skip the test on i386, but I guess we rather want to avoid introducing a delta for that
[09:08] <pitti> ginggs: indeed, 5h 42??
[09:08] <pitti> ah, that's a regression from the new julia or from the toolchain?
[09:09] <ginggs> pitti: both, apparently
[09:21] <juliank> pitti: The apt tests work on ppc64el and s390x now and those could be enforced now - the armhf and i386 ports have some timing issues (probably too slow)
[09:29]  * juliank is not sure if they were automatically ignored, if there was a setting to ignore !amd64 architectures, but anyway: ppc64el and s390x works now, and we should ensure that they remain that way.
[09:32] <pitti> juliank: they are automatically enforced -- once they succeed on an architecture, they must continue to succeed
[09:32] <juliank> Ah OK
[09:32] <pitti> juliank: i. e. we differ between "always failed" (which is not blocking) vs. "regression" (which is blocking)
[09:33] <pitti> juliank: and track that per-architecture
[09:33] <juliank> pitti: But only within in release series, right, because other archs also worked in vivid, for example.
[09:33] <pitti> ginggs: but if that's an actual regression on i386, wouldn't it be right to hold it back until this gets fixed?
[09:33] <pitti> ginggs: if julia is awfully slow on i386, that's a real problem, not just a test problem?
[09:34] <pitti> juliank: for wily->xenial we enforce it across the release, but we didn't retroactively do that for vivid
[09:34] <juliank> OK
[09:34] <pitti> juliank: so in general we do, just not vivid as we only set up that whole cloud testing system during wily
[09:36] <juliank> So if I understood things correctly, apt uploads need to be manually accepted right now, because one reverse dep (sbuild) currently fails the test suite (listed as Regression)
[09:37] <pitti> juliank: right; or more precisely, we ignore test failures of the current version of sbuild
[09:38] <juliank> OK. BTW, The python-apt and autopkgtest tests tmpfail on s390x currently
[09:38] <juliank> W: Target Sources (restricted/source/Sources) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list.d/proposed.list:2
[09:38] <juliank> and other warnings
[09:40] <pitti> juliank: yes, I just saw, I'm looking at that now
[09:50] <pitti> ah, bad container, fixed now
[09:50] <pitti> next britney run will re-trigger all the bad ones (http://autopkgtest.ubuntu.com/status/alerts/)
[09:55] <ginggs> pitti: yes, it is a real problem, not just a test problem, but i don't believe it is much of a problem - i don't think think many people are doing serious julia work on i386, and if you use it interactively the regression is not noticeable
[09:56] <LocutusOfBorg1> hi cjwatson, syncpackage ghc?
[11:04] <cjwatson> LocutusOfBorg1: not worth the build time right now
[11:04] <cjwatson> LocutusOfBorg1: will do it sometime when it isn't going to get in people's way
[11:04] <LocutusOfBorg1> ack sure
[11:06] <pitti> xnox: btw, amd64 finished yesterday, do the stats look better  now?
[11:07] <xnox> pitti, yes they do =) thank you
[11:12] <Mirv> xnox: hey! bzoltan_ has a s390x linker issue he doesn't know how to resolve, and it's a regression so he'd ask for removal of the ubuntu-ui-toolkit s390x from archives if there's no quick solution. https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-060/+build/8438344
[11:12] <bzoltan_> Mirv:  thanks
[11:15] <xnox> bzoltan_, if you have issues, you can talk about them yourself here, no? =)
[11:15] <bzoltan_> xnox:  I am not brave enough :)
[11:15] <xnox> bzoltan_, i don't bite  =))))) too hard.... ;-)
[11:16] <bzoltan_> xnox: I am more araid of the smiling hunters :)
[11:16] <bzoltan_> afraid I mean
[11:16] <xnox> warning: libUbuntuGestures.so.5 .... not found
[11:17] <xnox> looking where it should come from.
[11:19] <cjwatson> Mirv: is it OK if I remove qtenginio-opensource-src?  removed from Debian, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802788
[11:21] <Mirv> cjwatson: yes, that's what I tried to ask at bug #1512737
[11:21] <xnox> but it is there.... ln -s libUbuntuGestures.so.5.5.0 libUbuntuGestures.so
[11:22] <cjwatson> Mirv: ah, thanks - done
[11:22] <Mirv> cjwatson: thank you
[11:29] <xnox> Mirv, bzoltan_ it seems like libUbuntuGestures.so* are placed into ./lib/ at the top level of the build dir, yet linker -Llib/ is not specified?!
[11:29] <bzoltan_> xnox:  would that fix the issue?
[11:30] <xnox> bzoltan_, it should. this doesn't look like an arch specific issue at all, and just a generic typo/error somewhere in the build system. I want to pop out for lunch, but then i can spin a build of this on s390x (i have access) and check what's going on.
[11:32] <xnox> how it build on other arches is what gets me wondering. unless something else is going on.
[11:34] <Laney> xnox: ok to re-merge mono?
[11:34] <Laney> seems quick enough
[11:54] <pete-woods> pitti: do you know how long I should expect to wait for dbusmock 0.16.3 to migrate into xenial?
[11:55] <pitti> pete-woods: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-dbusmock
[11:55] <pitti> pete-woods: it's currently blocking on unity-scope-click regression on armhf; I  already retried it twice
[11:55] <pete-woods> dammit
[11:55] <pitti> pete-woods: ah, last retry actually succeeded, so next britney run should get it
[11:55] <pitti> and promote it
[11:56] <pete-woods> pitti: awesome, thanks!
[11:56] <pitti> pete-woods: it only got autosynced into xenial this morning
[11:56] <pete-woods> seems reasonable to ignore that failure anyway
[11:56] <pete-woods> those errors pretty clearly look unrelated
[11:59] <Laney> having a shoddy baseline means you have to repeatedly make that kind of assessment
[11:59] <Laney> would be better to tests to be reliable
[12:00] <pete-woods> yeah
[12:00] <pete-woods> they aren't mine
[12:00] <pete-woods> my tests do not print out 6k lines of errors
[12:00] <Laney> "Failed" :P
[12:19] <xnox> bzoltan_, Mirv, sil2100 - builds fine https://launchpad.net/~xnox/+archive/ubuntu/nonvirt/+build/8442437 http://paste.ubuntu.com/14026402/
[12:20] <xnox> i would have expected that any of you could read the original build log failure, that a library was not found and add it to be linked in.
[12:22] <pitti> pete-woods: just landed
[12:22] <pete-woods> pitti: awesome, thanks!
[12:25] <pete-woods> can re-enable my functional tests in my silo now :)
[12:31] <sil2100> xnox: I have no context regarding that
[12:33] <xnox> sil2100, earlier bzoltan_ & Mirv complained about s390x build failure as seen in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-060/+build/8438344 when in fact it has a trivial fix that anybody should be able to do.
[12:33] <xnox> sil2100, shouldn't build-failures like that be noticed quickly? (especially since it happened like 4 minutes after the upload)
[12:40] <sil2100> xnox: well, I'm not involved in that silo and I don't really scan all silos for build failures, that's up to the lander to take care of that ;)
[12:54] <jdstrand> pitti: hi! I uploaded libseccomp yesterday. it showed a ppc64el lxc regression and an i386 systemd regression. looking at them, I don't think the failures are related to the upload
[12:59] <Mirv> xnox: all I know is that bzoltan_ was hitting a similar issue on other archs earlier but the trick they did for that did not help on s390x
[13:00] <Mirv> xnox: it's great if there's a solution that works on s390x too
[13:01] <xnox> Mirv, i wonder what they have done on other arches.... the error is that library foo is required for a test, but has not been linked the same way all other libraries were linked. see the one-line diff i pasted.
[13:47] <seb128> mdeslaur, hey, is https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1518035 on your merges list?
[13:47] <mdeslaur> seb128: it's not, no
[13:47] <seb128> :-(
[13:47] <seb128> mdeslaur, it has your name on https://merges.ubuntu.com/main.html ... ;-)
[13:48] <mdeslaur> seb128: see "please take" comment on the right
[13:48] <seb128> oh, right
[13:48] <seb128> :-(
[13:48] <mdeslaur> seb128: someone needs to investigate why we've diverged from debian, and then do a whole transition for it
[13:48] <seb128> I guess we should at least backport the Conflicts for that files conflicts
[13:48] <seb128> even if we don't update nor merge
[13:52] <xnox> pitti, halo =) koonnen sie bitte autopkgtest im English benutzen? =)
[13:52] <xnox> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/j/juju-core/20151215_104022@/log.gz
[13:52] <xnox> pitti, ich liebe alle "Lese Datenbank" =)
[13:53] <pitti> xnox: bah -- that must be ssh again, forwarding my host's locale to the remote
[13:53] <pitti> what a silly anti-feature
[13:54] <pitti> xnox: I guess that locale further made it into the container
[13:54] <Laney> haha
[13:54] <Laney> we should keep it that way
[13:54] <xnox> pitti, das ist normal. Aber, Ich kann nich verstehen was is loss mit http://autopkgtest.ubuntu.com/packages/j/juju-core/xenial/s390x/ =(
[13:55] <xnox> pitti, koonen sie bitte dass noch ein mal gefahren?
[13:55] <pitti> xnox: ah, missing universr
[13:55] <pitti> xnox: yes, I'll rety; I think I fixed that this morning
[13:55]  * xnox wonders if pitti, doko, mvo, dholbach find my german funny at all =)
[13:55] <pitti> xnox: it is indeed! :-)
[13:56] <pitti> xnox: it's really good enough to comprehend, but funny all the same
[13:57] <Laney> ich verstehe alles!
[13:57] <dholbach> xnox: haha, great :)
[14:08] <ginggs> pitti: it appears here http://autopkgtest.ubuntu.com/packages/j/julia/xenial/i386/ that julia 0.4.2-3 built on i386, but that was actually 0.3.12-2ubuntu1.  Am i just reading that wrong?
[14:08] <xnox> didrocks, no comment on this bug https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1521984 -> so it's perfect right?! =)
[14:11] <pitti> Get:27 http://ftpmaster.internal/ubuntu xenial-proposed/universe i386 julia i386 0.4.2-3 [3,767 kB]
[14:12] <pitti> ginggs: ^ what do you mean? seems the version was correct
[14:12] <didrocks> xnox: I think doko told he had time to do some MIR
[14:12] <didrocks> xnox: but don't worry, you have enough to do to fix the others first :p
[14:12] <didrocks> s/to do//
[14:12] <xnox> didrocks, true that
[14:13] <pitti> jdstrand: hey! Looking
[14:13] <pitti> jdstrand: the three nspawn tests failed on i386, which do use seccomp, and there's an error message: Failed to add audit seccomp rule: Bad address
[14:13] <pitti> jdstrand: so it's by far not obvious that this is unrelated
[14:14] <pitti> jdstrand: (it rather looks quite relevant)
[14:14] <pitti> jdstrand: lxc has failed on ppc64el for a while, so we can ignore that indeed
[14:15] <pitti> jdstrand: I'll run it locally and investigate
[14:16] <pitti> jdstrand: ah, indeed it has started failing 4 days ago already, so it's not that; I'll wave it through then
[14:23] <xnox> pitti, so are we building lxd images for s390x? and what needs doing to achieve that? or shall i talk to stgraber about it? are they built in launchpad?
[14:29] <pitti> xnox: no, stgraber having access to an s390x machine, stgraber, no
[14:30] <pitti> xnox: for bug 1524618 I created an LXC container with the "ubuntu" template (i. e. debootstrap), created the metadata manually, and imported the image into lxd
[14:30] <pitti> xnox: that works fine, it's just a bit elaborate to do, particularly as you'd need to do it every day
[14:30] <pitti> (can certainly be automated, though)
[14:31] <pitti> xnox: lxd can use two ready-made types of images -- the ones on http://images.linuxcontainers.org (built on stgraber's linuxcontainers.org infra) and our regular cloud images
[14:31] <pitti> xnox: but neither are available for s390x so far
[14:31] <xnox> pitti, we have dev machines ready... which i can do stuff on. e.g. build images and publish them.
[14:32]  * xnox kind of likes lxd too.
[14:32] <pitti> xnox: yeah, me too; it so rocks on btrfs
[14:32] <pitti> and image handling, transparent caching etc. make it really simple to use
[14:32] <xnox> pitti, and zfs will make it soooo much better =)
[14:33] <pitti> xnox: lxc does seem to support zfs indeed
[14:34] <pitti> I haven't tried that yet, though; I think the jump from ext4 to btrfs is quite a bit more interesting than btrfs → zfs, from my POV
[14:39] <jdstrand> pitti: thanks! yes, it wasn't obvious to me either for the i386 one. there were other errors around the seccomp bad address one, so I wasn't sure if it was cascading failures, etc. thanks for the archaeology and accepting it :)
[14:40] <pitti> jdstrand: so the i386 seccomp regression is in xenial already, I reproduced it without -proposed
[14:40]  * jdstrand nods
[14:40] <pitti> jdstrand: I'm now downgrading stuff step by step to see what broke it
[14:40] <jdstrand> cool
[14:40] <pitti> i. e. it's a real regression, not just a test issue
[14:52] <ginggs> pitti: i see Get:26 http://ftpmaster.internal/ubuntu xenial/universe i386 julia i386 0.3.12-2ubuntu1 [2,935 kB] - this is where it says version 0.4.2-3, triggers mpfr4 3.1.302
[14:52] <pitti> ginggs: ah right, for other triggers it'll run against the xenial-release version, as 0.4 isn't in -release yet
[14:53] <pitti> ginggs: the bug there is that it runs the tests from the 0.4.2 *source* package (from -proposed) against the 0.3 binary packages in -release
[14:53] <pitti> ginggs: that's known, and this needs working around in apt as apt pinning doesn't apply to source packages
[14:54] <ginggs> pitti: ok, thanks
[15:00] <jamespage> !regression-alert
[15:00] <jamespage> bug 1526271 - the recent SRU to 14.04 for haproxy introduced a regression where the return code from the init script is now always 0
[15:01] <jamespage> not great when other tools rely on return codes being lsb compliant :(
[15:01] <jamespage> working a fix now
[15:01] <jamespage> thats and interesting list of people...
[15:05] <pitti> jamespage: so a quick followup SRU should be fine for that, right? it's been out in the wild for 6 days already, and fixable with another update, so I don't think that warrants pulling the update from teh servers
[15:05] <jamespage> pitti, agreed - its pretty much a one line change to resolve
[15:05] <pitti> bdmurray: ^ maybe you can reset its propgagation percentage to 0%?
[15:06] <pitti> jamespage: ack, so let's get that in ASAP and release tomorrow after testing?
[15:06] <pitti> i. e. 0.5 or 1 day instead of 7
[15:06] <jamespage> pitti, ack
[15:10] <jamespage> pitti, fix uploaded to trusty-proposed - bug updated with reproduction details.
[15:10] <jamespage> only impacts trusty - all other releases got a better version of the fix....
[15:12] <jamespage> caribou, hey - just so you are aware ^^ ;-)
[15:13] <caribou> jamespage: thanks!
[15:24] <apw> cjwatson, hey, britney is saying (cached yaml here: http://paste.ubuntu.com/14028195/) that arm64 has old binaries, but it does not have any up to date binaries so it should be saying that... confused ?
[15:27] <cjwatson> apw: which source?
[15:27] <apw> cjwatson, sorry, linux itself
[15:28] <apw> cjwatson, which would have been at -4.13 at the time, and failed utterly to produce anything on arm64: https://launchpad.net/ubuntu/+source/linux/4.3.0-4.13/+build/8427529
[15:29] <xnox> apw, hence my earlier comment about linux[-meta] on #ubuntu-kernel. it is rather confusing. i believe there was an intermittend build that was hence superseeded, but never migrated to -release pocket that is still visible. or some such.
[15:31] <xnox> apw, linux-meta is 4.3.0.2.5 in release, and 4.3.0.5.6 in proposed, yet there was a successful build 4.3.0.2.4 of arm64 in -proposed.... which didn't get removed. huh, should it not have had migrated to release and be removed (?!)
[15:31] <xnox> something is really odd.
[15:32] <xnox> apw, i think we simply need to ask AAs to purge stale arm64 things from -proposed.
[15:32] <cjwatson> apw: that seems normal if there was a previous unmigrated thing in -proposed
[15:33] <apw> cjwatson, but for it to complain about cruft it should think there are builds for arm64 in there at the source package version it is expecting "uptodatebins = True" as it were
[15:34] <coreycb> cjwatson: there are several openstack packages in universe that I work on frequently but I can't upload.  any chance they could be seeded somehow so that I can upload them with my ubuntu server per-package upload rights?
[15:34] <cjwatson> coreycb: not up to me
[15:35] <apw> xnox, yes, we have NBS in there, i am happy it is complaining about that indeed, but i am not expecting it to tell me about NBS it finds if there are no uptodate binaries, that overrides the cruft complaint
[15:35] <cjwatson> apw: err possibly?  that code is deeply twisty
[15:35] <xnox> coreycb, please email to developer membership board to grant upload rights and/or update seeds.
[15:35] <apw> yeah, its like the epochroful maze and no mistake
[15:35] <xnox> coreycb, do you know where to send such request?
[15:35] <cjwatson> apw: some time since I stared at it in any depth
[15:35] <coreycb> xnox, ok yeah I can figure that out
[15:36] <cjwatson> apw: the NBS of linux-source-4.2.0 that hasn't yet been removed due to build-dep from user-mode-linux may not be helping
[15:36] <xnox> coreycb, https://wiki.ubuntu.com/DeveloperMembershipBoard devel-permissions@lists.ubuntu.com list will used. Check out archives for previous requests about it.
[15:36] <cjwatson> apw: indeed that may be the main problem here
[15:36] <xnox> coreycb, or if you are ready, apply to become a MOTU =)
[15:36] <apw> cjwatson, yeah, prolly not worth thinking too hard on.  it probabally needs debugging one time it is in that state, but i just uploaded over it :)
[15:36] <coreycb> xnox, thanks
[15:36] <coreycb> xnox, that's an option :)
[15:36] <apw> cjwatson, ahh thanks
[15:37]  * apw puts that on the list of things which are broke
[15:39] <pitti> apw: argh, that's what we get with ignoring REGN.. bug 1526358 :(
[15:39] <pitti> apw: i. e. on i386, 4.3 broke something in linux-libc-dev wrt. seccomp
[15:40] <pitti> apw: not sure if that affects lxc as well, but at least lxd is using seccomp too
[15:41] <pitti> jdstrand: ^ FYI, I bisected the change, it was the new linux-libc-dev (see bug)
[15:41] <pitti> jdstrand: so if you hear about seccomp trouble on i386, it's likely that
[15:41] <jdstrand> pitti: yeah, just finished reading the bug. nice triage work
[15:41] <jdstrand> apw: also, fyi, seccomp is used on snappy, but i386 aren't official
[15:42] <pitti> there's now an < 1 s reproducer,  but unfortunately it involves building systemd
[15:42] <apw> pitti, though to be fair we started ignoring it because it was a networkd thing, which we thought was fixed
[15:42] <pitti> apw: it's not networkd, it's nspawn, i. e. containers
[15:43] <pitti> I added a comment how to build systemd in the minimal time
[15:43] <apw> pitti, right, i assume that is the boot-and-services test failure ?
[15:43] <pitti> apw: yes, I know, I'm certainly guilty of ignoring it too :) (just saying)
[15:43] <pitti> apw: yes, that's part of it
[15:44] <pitti> apw: but in the bug I have a simple copy&paste 1 second reproducer which doesn't involve autopkgtest
[15:44] <apw> pitti, as that got away i think because networkd was fail in the previous one, and then got fixed and at the same time boot-and-services went fail
[15:44] <pitti> apw: yeah, probably that
[15:44] <apw> pitti, so i thkn that means we should have marked the the first one "fixed" so it was ignored
[15:44] <apw> pitti, or rerun it so it went green, and then it would have stopped us correctly
[15:44] <pitti> apw: so, this isn't critical for sure, so we might even have landed the kernel if we had known about it before
[15:45] <pitti> but it's a nice exercise to improve our process
[15:45] <apw> pitti, oh yeah, absolutly, but i want to figure out how we should have reacted to have caught it, that indeed
[15:54] <coreycb> hello, any chance an archive admin can drop python-cryptography 1.1.1-1ubuntu1 from proposed?  we've changed our mind on how we want to handle it.
[16:15] <bdmurray> pitti: only archive admins, which I'm not, can set the phased-update-percentage
[16:17] <bdmurray> pitti: the change-override script allows one to set the percentage
[16:19] <infinity> bdmurray: What need PuPing?
[16:19] <infinity> s/need/needs/
[16:20] <bdmurray> infinity: haproxy for trusty see bug 1526271
[16:21] <infinity> bdmurray: Looking.
[16:22] <infinity> bdmurray: Oh.  It's not even in proposed yet.
[16:23] <infinity> A bit of gun-jumping on phasing. ;)
[16:24] <bdmurray> infinity: I think jamespage was saying 1.4.24-2ubuntu0.3 is bad.
[16:25] <infinity> bdmurray: Oh, you want to phase .3 to 0?  Check.
[16:25] <infinity> Well.  Not that it will matter.
[16:25] <infinity> haproxy is a server thing, who runs update-manager on servers?
[16:25] <infinity> We really just need to push the next one through ASAP.
[16:25] <jamespage> ha
[16:25]  * infinity goes to review it.
[16:28] <infinity> jamespage: Is this tested for sanity?
[16:30] <infinity> jamespage: Accepted, if you can get it tested ASAP and let me know, I can release and phase it to 100.
[16:30] <jamespage> infinity, ack - thanks
[17:03] <TJ-> Anyone familiar with PAM? I'd like some confirmation that on user logout close_session should be called for "common-session", specifically for pam_exec ?
[17:04] <seb128> TJ-, slangasek or robert_ancell might be able to help you
[17:05] <TJ-> seb128: thanks :)
[17:07] <slangasek> it's up to the PAM application to make sure it calls close_session().  But any session modules configured for the service, and that were called for open_session, should also be called for close_session.
[17:09] <seb128> barry, bug #1526450 seems a regression from your apt-xapian-index update
[17:10] <barry> seb128: thanks, will investigate
[17:10] <seb128> yw!
[17:18] <nagromlt> channel for audio help?
[17:20] <seb128> barry, Trevinho, also https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1526455 seems a regression from the recent landing/python3 port
[17:21] <Trevinho> seb128: yes
[17:24] <Trevinho> seb128: i can't reproduce that locally though... Maybe cmdline is containng something weird
[17:26] <seb128> Trevinho, I can reproduce here
[17:26] <Trevinho> seb128: me too now
[17:26] <seb128> what did you change? ;-)
[17:27] <Trevinho> seb128: i was debugging that, and I was using a bad cmdline definition
[17:27] <seb128> k
[17:30] <xnox> stgraber, can i trigger image builds via iso tracker? and i would like to be able to do so for server/s390x
[17:33] <TJ-> slangasek: thanks. I was helping a user and suggested using pam_exec in common-session and it only receives open_session, never close_session. I've tested it on 15.10 and confirmed the same thing. auth.log shows the open_session, as does the program being executed, but as I say, no sign of close_session
[17:34] <Trevinho> seb128: for your pleasure https://code.launchpad.net/~3v1n0/unity/unity-script-fix-byte-regex/+merge/280624
[17:39] <seb128> Trevinho, looks fine to me but I would prefer for barry to ack it as well, python encoding issues are always confusing to me
[17:43] <TJ-> slangasek: so we have "session optional        pam_exec.so debug /bin/bash /usr/local/bin/pam_exec_test.sh"  with the script just doing "env >> /tmp/pam_exec.log" and we never see anything else other than "PAM_TYPE=open_session"
[18:01] <barry> Trevinho: can you provide some context for this change?
[18:02] <barry> ah, LP: #1526455 probably
[18:05] <seb128> barry, right
[18:14] <Trevinho> barry: yeah, that it
[18:17] <barry> Trevinho, seb128 remind me where /usr/bin/unity comes from? ;)  i think the patch is good, but i want to understand why cmdline is a bytes
[18:17] <barry> "comes from" in lp:unity
[18:22] <nagromlt> help with audio?
[18:22] <barry> ah, found it
[18:22]  * barry will comment on the mp
[18:22] <nagromlt> or audio help channel?
[18:23] <geofft> nagromlt: try #ubuntu
[18:24] <nagromlt> geofft: thx
[18:41] <xnox> Mirv, bzoltan_ you did see my pastebin debdiff, right? i didn't hear anything back, but my irc was cut off.
[18:42] <bzoltan_> xnox:  sorry mate, I was dead busy with other stuff.. reading now
[18:43] <xnox> bzoltan_, you asked for a quick fix and i provided one in like less than an hour....
[18:43] <bzoltan_> xnox:  I do not see any pastebin debdiff
[18:43] <xnox> bzoltan_, xnox> bzoltan_, Mirv, sil2100 - builds fine https://launchpad.net/~xnox/+archive/ubuntu/nonvirt/+build/8442437 http://paste.ubuntu.com/14026402/
[18:43] <xnox> bzoltan_, that's url to a build log and a diff.
[18:44] <xnox> bzoltan_, e.g. a test file tries to link with a library, that depends on UbuntuGestures and was not found.
[18:44] <bzoltan_> xnox:  that looks logical indeed
[18:44] <xnox> bzoltan_, it's located in $top/lib dir, which is not specified in linker flags.
[18:44] <xnox> bzoltan_, it's a perphaps new dependency, which should be added to be linked with.
[18:44] <bzoltan_> xnox:  I will put it to our staging and land it with the next round
[18:44] <xnox> maybe there is some other location for it, but it seems to be moved to $(top)/lib anyway, so used that.
[18:45] <xnox> bzoltan_, your package will not migrate.
[18:45] <xnox> bzoltan_, i have it fully built for xenial, in a devirt ppa on all arches.
[18:45] <xnox> bzoltan_, https://launchpad.net/~xnox/+archive/ubuntu/nonvirt/+build/8442437
[18:45] <xnox> sorry
[18:45] <xnox> https://launchpad.net/~xnox/+archive/ubuntu/nonvirt
[18:45] <xnox> you may copy from there....
[18:46] <bzoltan_> xnox: I have a QA granted landing silo ready to migrate... I think it is smartet to integrate this fix with the next landing
[18:47] <bzoltan_> xnox: plus I have no power to copy these fine packages to the landing silo
[18:48] <xnox> i can.
[18:48] <xnox> bzoltan_, but as you wish.
[18:48]  * bzoltan_ admires people with power :)
[18:48] <xnox> bzoltan_, it's just we will not remove binaries for s390x. and your xenial packages will be stuck in xenial-proposed.
[18:49] <xnox> at which point i will copy my build over into xenial-proposed only, to get it to migrate.
[18:49] <bzoltan_> xnox:  sounds good
[18:49] <xnox> but then, it will not be binaries that were tested from the silo.
[18:49] <xnox> which is a tradeoff we have to take.
[18:49] <xnox> cause removing s390x binaries will cause caos, as loads of things have built and depend on it already on s390x =/
[18:49] <bzoltan_> xnox:  fine... it will be only a temp issue... as I am lanidng this fix on Thursday
[18:51] <xnox> bzoltan_, ack.
[18:54] <bzoltan_> xnox: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/link_Gestures_more_explicitely/+merge/280630
[18:54]  * xnox chuckles at review type
[19:18] <tkamppeter> morphis, hi
[19:18] <tkamppeter> morphis, sorry.
[19:20] <tkamppeter> morphis, are you doing Ubuntu Phone stuff?
[19:30] <RobertDupont> hello guys
[19:30] <RobertDupont> not sure if it's the right channel but I'm working with the alpha iso of 16.04 and for some weird reason, I can SFTP to the machine but not SSH (command line)
[19:31] <RobertDupont> on a stock ssh config
[19:32] <RobertDupont> is it on purpose or not?
[19:33] <sarnold> RobertDupont: what error messages do you get? check both client and server..
[19:33] <teward> RobertDupont: i can't replicate and my 16.04 ISO I used was from yesterday's 'current' folder, though with a server iso.  do you get any kind of error when you try and SSH in ?  (on either side)
[19:33] <teward> blah
[19:34] <teward> oh sarnold good you're alive
[19:34] <sarnold> rumours of my death are greatly exaggerated
[19:34] <RobertDupont> sarnold: no error message on the client. It times out after some time
[19:35] <RobertDupont> I'm using VMware if that's any useful and 16.04 fails but 14.04 works fine
[19:35] <RobertDupont> I can give you pcap done from the server if it helps
[19:35] <RobertDupont> I can make connections no problem from that machine, update, do whatever that requires network
[19:36] <teward> RobertDupont: i've got a VMware Workstation here, i wasn't able to replicate either
[19:36] <teward> i'll re-zsync down to test with a new ISO, but meh
[19:37] <RobertDupont> I got 'kex protocol error' in the logs, let me google that
[19:37] <RobertDupont> looks like my client is too old (even though I updated recently)
[19:38] <RobertDupont> let me try updating it
[19:38] <teward> RobertDupont: what's the system you're SSHing from?
[19:38] <teward> what version?
[19:38] <teward> (I'm 14.04 if it matters)
[19:38] <RobertDupont> from Win7, using putty
[19:39] <RobertDupont> Apparently, I'm using a snapshot version from last year
[19:39] <teward> eww
[19:42] <RobertDupont> I guess the installer failed to update it :/
[19:43] <teward> potentially
[19:43] <RobertDupont> updating it worked
[19:43] <RobertDupont> sorry for the trouble
[19:43] <teward> no problem :)
[19:43] <teward> i need the updated ISO anyways :)
[19:45] <RobertDupont> thanks for your help
[19:47] <teward> you're welcome
[19:47] <teward> i should note that my ISO didn't update openssh either, so it went KABLOOEY.  Though, my VMs get managed by Landscape anyways so... :P
[19:48] <teward> (daily security update application schedule, is nice)
[19:49] <RobertDupont> I wish I could justify buying Landscape
[19:49] <RobertDupont> I managed to get to a point where I barely have to take care of my machines, automatic updates has been working flawlessly
[19:52] <teward> doko: did
[19:52] <teward> oops
[19:52] <teward> doko: not sure if the discussion resolved, did the Lua legacy version issue ever get determined?  I went offline before I could see a resolution
[19:52] <teward> (just checking)
[20:23] <morphis> tkamppeter: yes
[20:24] <tkamppeter> morphis, how can I let cups-browsed have different default settings (in /etc/cups/cups-browsed.conf) on the phone and on the desktop?
[20:26] <morphis> tkamppeter: add an .override to lxc-android-config
[20:27] <morphis> tkamppeter: you're in DE, right?
[20:27] <tkamppeter> morphis, I am in Brazil.
[20:27] <morphis> ah
[20:28] <morphis> tkamppeter: like you did here https://code.launchpad.net/~till-kamppeter/lxc-android-config/cups-override
[20:29] <morphis> tkamppeter: lets talk tomorrow, I am on the way
[20:30] <tkamppeter> morphis, a .override allows me to apply another method to start a daemon, but not to use a modified config file. What I need is that on the phone /etc/cups/cups-browsed.conf gets the lines "IPBasedDeviceURIs IPv4" and "CreateIPPPrinterQueues Yes" added.
[20:30] <morphis> ah I see
[20:30] <tkamppeter> morphis, where are you located?
[20:30] <morphis> DE
[20:31] <tkamppeter> morphis, which city?
[20:31] <morphis> lets talk tomorrow, we could also talk quickly on an hangout tomorrow
[20:31] <morphis> close to Bremen
[20:31] <tkamppeter> morphis, cu tomorrow.
[20:31] <morphis> cya!
[20:36] <tkamppeter> On a merge proposal I got the answer "Review: Approve; LGTM but needs proper landing through the citrain", what do I have to do now?
[22:20] <sarnold> what's the tag to prevent proposed->released migration in xenial?
[22:50] <doko> teward, no, we should continue that discussion early next year
[22:50] <teward> ok
[23:18] <Logan> sarnold: block-proposed
[23:20] <sarnold> Logan: thanks