[00:19] <valorie> cyphermox: I spoke too soon -- returned home from shopping to find it frozen again
[00:19] <valorie> :(
[00:20] <valorie> valorie-GT60-2PC': Running inside KDE Plasma 5.9.2 on Ubuntu 17.04 (Zesty Zapus) powered by Linux 4.10.0-9-generic, CPU: Intel(R) Core(TM) i7-4810MQ CPU @ 2.80GHz at 1899/3800 MHz, RAM: 2620/24027 MB
[00:20] <valorie> plenty of memory here, and plasma runs flawlessly until the freeze
[00:21] <valorie> fooey
[09:06] <Unit193> sil2100: G'morning!  How's the thunar SRU looking?
[09:06] <sil2100> Unit193: morning! All good, will publish it in a few minutes!
[09:06] <sil2100> Just need to wake up
[09:06] <Unit193> \o/
[09:07] <Unit193> Hah, get some good coffee.  We were just trying to make sure it gets in well before our Trusty EOL.
[10:20] <Laney> pitti: want to try resubmitting a systemd request?
[10:20] <Laney> I just built some bodged up adt images
[10:27] <pitti> Laney: ♥
[10:28] <pitti> Laney: https://github.com/systemd/systemd/pull/5528 is running from 20 mins ago, that might just have missed it
[10:28] <pitti> Laney: I'll retry that one if/after it fails
[10:29] <Laney> depends if it hit lcy01/amd64 :P
[10:29] <pitti> https://github.com/systemd/systemd/pull/5529 is from 6 mins ago, that should have caught it
[10:29] <Laney> ok, nice
[10:30] <pitti> Laney: I'll retry https://github.com/systemd/systemd/pull/5510 now, that already failed (yesterday-ish)
[10:31] <Laney> pitti: 5528 seems to be building
[10:31] <Laney> so that's past where it would have broken already
[10:31] <pitti> nice!
[10:31] <Laney> IIUC
[10:31] <pitti> yeah, it would have failed early, during setup-commands
[10:31] <Laney> i386/lgw01 amd64 came a bit later
[10:32] <Laney> -y --allow-downgrades FTW
[10:33] <pitti> Laney: so we published a kernel update, the daily cloud images grabbed it, then we pulled the kernel update?
[10:33] <Laney> right
[10:33] <pitti> "nice" timing
[10:33] <Laney> then you couldn't install linux-* because of the = depends
[10:33] <pitti> thanks for debugging that
[10:34] <Laney> np, I knew it had happened so it didn't take me long to connect once I saw a failing log
[10:36] <pitti> Laney: https://github.com/systemd/systemd/pull/5528 i386 failed; I think that's the one that missed your update by a few minutes, retrying
[10:36] <Laney> nod
[11:22] <xnox> smoser, xe-daemon.service has weird stanzas w.r.t. cloud-init units and it ends up a dependency loop.
[11:22] <xnox> Before=network.target cloud-init.service cloud-init-local.service seems wrong to me
[11:22] <xnox> i would have thought it should be After=cloud-config.target Wants=cloud-config.target instead
[14:23] <smoser> xnox, did you get sorted on that ?
[14:24] <xnox> somewhat
[14:25] <xnox> smoser, i think xe-daemon encodes correctly everything it needs without cloud-init as well.
[14:25] <xnox> but i will test that out
[14:27] <smoser> xnox, it quite possibly does.
[14:27] <smoser> josvaz, was just not interested in pushing an sru at that point.
[15:01] <javier4> Sorry If I ask the same question again: is there a way to make sbuild ignore checksum of sources inside a .dsc?
[15:14] <tjaalton> LocutusOfBorg: hi, what's up with virtualbox autopkgtests failing?
[15:14] <LocutusOfBorg> looking
[15:15] <LocutusOfBorg> apw, please merge virtualbox kernel drivers? ^^
[15:16] <LocutusOfBorg> tjaalton, seems that the kernel module is already provided in the driver itself, so installing the dkms package is useless
[15:16] <LocutusOfBorg> usually kernel people were behind virtualbox version, so the dkms packages was overriding the kernel one
[15:16] <LocutusOfBorg> right now this isn't the case
[15:17] <tjaalton> ok
[15:18] <tjaalton> the dkms failure was seen on erlier tests too that passed iirc
[15:19] <apw> tjaalton, that is one of those where i need to fix the tests to understand that the kernel also has versions of the driver
[15:20] <apw> if the error is "already installed" it should be ignorable
[15:24] <tjaalton> ah ok
[16:40] <nacc> rbasak: around?
[16:56] <rbasak> nacc: o/
[16:56] <nacc> rbasak: wondered if you had some time to talk about the -devel pointers?
[16:57] <rbasak> Sure!
[16:57] <nacc> rbasak: HO ok?
[16:57] <rbasak> Yeah. Two minutes please.
[16:57] <nacc> rbasak: of course
[17:14] <forehelp> hi all, how can i have two machines that are updating from the same repo (an internal repo), new ones show 14.04.5 and old ones show 14.04.3 ? kernel is the same... what package is making this change ?
[17:37] <nacc> forehelp: wrong channel?
[17:38] <forehelp> nacc: yes sorry i asked on the right one
[23:17] <powersj> infinity: slangasek: similar to the server amd64,i386 ISOs, can we get our automated tests blocking the release of those for ppc64el as well?
[23:42] <bulletxt|2> hi, can someone be kind enough to see if ubuntu kernel 3.16.x series has the intel i219-lm network driver?  Thanks a lot
[23:45] <bulletxt|2> or, how can I see if the intel e1000 loaded driver has such support?
[23:48] <sarnold> bulletxt|2: if I'm reading this correctly, that kernel hasn't had any updates since july https://launchpad.net/ubuntu/+source/linux-lts-utopic
[23:49] <bulletxt|2> ok but
[23:49] <bulletxt|2> does it have support for the driver? sarnold
[23:49] <bulletxt|2> how can I discover this info?
[23:49] <bulletxt|2> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.40/
[23:50] <sarnold> ah here we go, here's the git tree http://kernel.ubuntu.com/git/ubuntu-archive/ubuntu-utopic.git/
[23:50] <sarnold> they apparently move the no-longer-supported ones to ubuntu-archive
[23:51] <sarnold> oh hrm that .. looks too old.
[23:52] <bulletxt|2> sarnold: I just need to know if the driver is included in the 3.16 series
[23:52] <bulletxt|2> how can I discover this?
[23:55] <wxl> bulletxt|2: looks like, using the most recent 3.16 tag and searching the tree, there's e1000e http://kernel.ubuntu.com/git/ubuntu-archive/ubuntu-utopic.git/tree/drivers/net/ethernet/intel?h=Ubuntu-3.16.0-44.59
[23:55] <wxl> looks like support has existed in that driver since 2012 https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2fbe4526e5aafc9ffa5d85fa4749a7c5b22af6b2
[23:56] <bulletxt|2> wxl: no
[23:56] <bulletxt|2> its not i217
[23:56] <bulletxt|2> its i219
[23:56] <bulletxt|2> which came out in 2015
[23:56] <wxl> i quote "e1000e: initial support for i217"
[23:57] <bulletxt|2> in my case the card is i219-lm
[23:57] <wxl> ah
[23:58] <bulletxt|2> can you check when that has been added in the official linux kernel? I guess its 4.0 series
[23:58] <sbeattie> Looking at http://cateee.net/lkddb/web-lkddb/E1000E.html seems to indicate the first upstream kernel to support it (device: 156f) is the 4.1 kernel