n until i upgraded to xenial.  i *think*
[17:13] <hallyn> no special args,
[17:13] <hallyn> root      2705     1  0 Feb13 ?        00:00:00 /usr/sbin/libvirtd
[17:14] <smb> ok, well still allows for breakage with the xml definitions which would not be new
[17:15] <smb> hallyn, have you tried to virsh edit the config and do a small change then write it back
[17:16] <smb> validation is done for writes... though the error messages for that used to be poor
[17:19] <hallyn> nacc: LGTM, wish i could see the debian bug, but th
[17:19] <hallyn> x
[17:19] <hallyn> nacc: did you do a merge request against anything?  Should I just push the package to x?
[17:21] <arges> hallyn: can you dumpxml the faulty vm and pastebin it somewhere
[17:22] <hallyn> i'll object to "the faulty vm" :-)
[17:22] <hallyn> arges: just a min
[17:23] <arges> hallyn: well the one that libvirt cant parse
[17:23] <arges> and perhaps there is a qemu log somewhere to see if that cmdline it produced looks messed up
[17:24] <hallyn> arges: it can't parse any of several I had.  I deleted all but one, and created one new one.
[17:24] <hallyn> http://paste.ubuntu.com/15101328/
[17:25] <hallyn> arges: the logfile has : libvirt:  error : libvirtd quit during handshake: Input/output error
[17:26] <hallyn> nacc: hm, having trouble building a source pkg
[17:27] <hallyn> why is debuild being stupid and trying to include .git?
[17:28] <hallyn> there msut be  a better way to build than to mv .git .. first
[17:28] <hallyn> that is to ohacky
[17:30] <arges> ok i'll look
[17:33] <hallyn> nacc: ffs can't you file a debian bug to fix the pkging to be 3.0 quilt? :)  kills me
[17:33] <hallyn> anyway, pushing, thx
[17:42] <teward|> rbanffy: ping, if you're around and can give some guidance on the nginx package, that'd be great - gotta pick between two evils :/
[17:42] <teward|> erm
[17:42] <teward|> rbasak: ^
[17:42] <teward|> sorry rbanffy for the mishighlight
[17:43] <nacc> hallyn: :) i can do that for the next release
[17:44] <rbasak> teward|: around but otp. Do you want to provide a summary here please?
[17:45] <teward|> rbasak: FTBFS as is, we have to update the Lua moduel in -extras.  Two options: nitpick the fix from upstream which fixes the missing udp connector struct, or take from Debian's git repository in where they update the entire module to the release candidate version on openresty's github pages, which brings in additional changes to the Lua module (I don't have a complete list)
[17:45] <teward|> rbasak: not sure which is the correct approach, though i can get either done before FeatureFreeze once I get some guidance
[17:46] <teward|> Debian's updating of the package also incorporates the fix, apparently, though that will undergo its own build tests as well
[17:49] <teward|> rbasak: basically, i'm not sure which approach will work better, hence seeking some advice :/
[17:51] <rbanffy> NP, teward. It happens all the time.
[18:15] <hallyn> smb: arges: all right, sorry, focusing on the libvirt thing now
[18:15] <hallyn> oh, one more thing first,
[18:15] <arges> hallyn: no problem, ive downloaded the xml files from you and the bug report, trying to look at what the differences are and repo on my end
[18:15] <arges> hallyn: ok no problem
[18:17] <hallyn> arges: saving xml works fine, sothat's not the problem
[18:17] <hallyn> lemme set up two vms, one with upgrade and one with clean install, and compare...
[18:18] <arges> hallyn: yea that's what I was trying to do, but hopefully that points us in the right area. wondering if its osmething to do with how the disk controllers are setup
[18:18] <arges> that would be my swag
[18:48] <hallyn> arges: wtf.  failed to reproduce in a vm
[18:50] <arges> hallyn: yea i'm not having luck here either.
[18:51] <arges> hallyn: what did you upgrade from? wily?
[18:54] <hallyn> arges: yeah, maybe i need to start from vivid, which my laptop apparently did
[18:54] <hallyn> (though not directly)
[18:54] <hallyn> i'll try from trusty - upstart->systemd seems more likely to e a trigger
[18:55] <arges> hallyn: ok
[19:01] <hallyn> arges: i think when we find the cause we're gonna laaaaaugh
[19:02] <arges> hallyn: : ) progres?
[19:03] <hallyn> wiating on the trusty vm install
[19:03] <hallyn> oh it's done
[19:07] <arges> hallyn: grabbing lunch... keep me posted
[19:07] <hallyn> k
[19:13] <rbasak> teward: extras is in universe, right? So no security team main concern about whether to follow Debian's import or take from nginx upstream.
[19:14] <teward> rbasak: correct - extras is in Universe
[19:14] <teward> rbasak: though, once dynamic modules are applied, we're going to have to scramble to make sure some are in Main, some aren't
[19:14] <teward> because it's not nice when that's taken into account
[19:14] <rbasak> teward: my remaining question would be about user visible differences. Is there a cost to committing to one over the other now? IOW, will any user have a reason to care if you take one approach now and switch later?
[19:14] <teward> (that's the future though)
[19:15] <teward> rbasak: AIUI, no, there won't be any major reasons for Users to care.  However, one reduces the plugin-specific future merge delta by one tiny commit, the other reduces it to zero when merging in from Debian
[19:15] <rbasak> If that's not a concern then I'd pick the easiest thing, which I guess you get to trade off. Following Debian is nice, but the benefit depends on how much we've diverged in this aresa.
[19:15] <rbasak> area
[19:15] <teward> mmm
[19:15] <rbasak> OTOH, cherry-picking a trivial patch may be far easier.
[19:16] <rbasak> That's what we'd probably want to do after FF anyway.
[19:16] <teward> rbasak: they're both available on git - patches are nice anyways :P
[19:16] <teward> indeed
[19:16] <teward> though, every new release of nginx will have to get an FF exception
[19:16] <teward> which is fine, but it's one of those annoying little headaches :)
[19:16] <rbasak> I thought we had an understanding with the release team on the plan? Or did that not get fully resolved?
[19:17] <rbasak> Keep ubuntu-release advised, certainly. I'm not sure if you need an explicit and formal FFe approval for each step though.
[19:17] <teward> i'm not sure we did since the policy change, the TB discussion was one fo "everything still gets standard FF review before upload" iirc
[19:17] <teward> rbasak: well, from this point on, each nginx will likely have some minor feature changes
[19:17] <teward> so it'd need FFe if standard policy is followed
[19:17] <rbasak> Ah, OK.
[19:17] <teward> plus HTTP/2 bugfixes which don't affect the builds currently
[19:17] <teward> (because it's not enabled)
[19:18] <teward> rbasak: i'm going to nitpick the minor change form upstream that enables building and doesn't implement an rc version of the third party module
[19:18] <teward> seems like the lesser evil
[19:19] <rbasak> OK, that sounds good. Thank you for considering carefully, as always!
[19:19] <teward> that's my job :)
[19:19] <teward> and thank you for being a sounding board and for the ongoing advice
[19:19] <teward> it's always nice to bounce opinions off others first :)
[19:19] <rbasak> np
[19:19] <rbasak> I forgot the other option was rc
[19:19] <rbasak> That makes your choice sound even better.
[19:23] <teward> mhm
[19:40] <hallyn> arges: hm, not reproduced in trusty vm either.  so i guess i'll have to look more closely at my own setup.
[19:40] <hallyn> fascinating
[19:41] <arges> hallyn: yikes, ok
[21:40] <hallyn> eureka
[21:42] <hallyn> arges: smb: systemd-machined, provided by systemd-container, is causing the problem
[21:46] <arges> hallyn: so your hunch in the bug earlier was corrupt
[21:46] <arges> correct
[21:46] <hallyn> accuse me of corruption?   I'll sue!
[21:46] <arges> haha
[21:47] <hallyn> yeah i just don't get why systemd-machined woudl ship in systemd-container.  that's weird
[21:47] <hallyn> mind you the bug may still actually be in libvirt
[21:47] <hallyn> but i find that hard to believe, as we're on 1.3.x
[21:47] <hallyn> anyway with that found i'll lower it's priority and defer it :(
[21:51] <arges> cool hopefully we can catch it before release
[22:35] <jak2000> arrrghhh
[22:35] <jak2000> are you there?
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             [06:27] <napsy> jutro
[06:31] <zdobersek> hai
[06:58] <slax0r> jutro
[09:00] <pitastrudl> jutro
[09:03] <CrazyLemon> buhdej
[09:06] <zdobersek> WE MAINSTREAM NOW BOYS http://www.24ur.com/novice/it/mega-racunalniski-hrosc-lahko-prizadane-na-tisoce-naprav.html
[09:06] <Pepelka> 24ur.com - Mega računalniški hrošč lahko prizadane na tisoče n