/srv/irclogs.ubuntu.com/2017/03/03/#ubuntu-devel.txt

valoriecyphermox: I spoke too soon -- returned home from shopping to find it frozen again00:19
valorie:(00:19
valorievalorie-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 MB00:20
valorieplenty of memory here, and plasma runs flawlessly until the freeze00:20
valoriefooey00:21
=== mwsb is now known as chuuu
=== chuuu is now known as chu
=== pavlushka is now known as whizzkid
=== whizzkid is now known as pavlushka
=== maclin1 is now known as maclin
=== n1ce_ is now known as n1ce
Unit193sil2100: G'morning!  How's the thunar SRU looking?09:06
sil2100Unit193: morning! All good, will publish it in a few minutes!09:06
sil2100Just need to wake up09:06
Unit193\o/09:06
Unit193Hah, get some good coffee.  We were just trying to make sure it gets in well before our Trusty EOL.09:07
Laneypitti: want to try resubmitting a systemd request?10:20
LaneyI just built some bodged up adt images10:20
pittiLaney: ♥10:27
pittiLaney: https://github.com/systemd/systemd/pull/5528 is running from 20 mins ago, that might just have missed it10:28
pittiLaney: I'll retry that one if/after it fails10:28
Laneydepends if it hit lcy01/amd64 :P10:29
pittihttps://github.com/systemd/systemd/pull/5529 is from 6 mins ago, that should have caught it10:29
Laneyok, nice10:29
pittiLaney: I'll retry https://github.com/systemd/systemd/pull/5510 now, that already failed (yesterday-ish)10:30
Laneypitti: 5528 seems to be building10:31
Laneyso that's past where it would have broken already10:31
pittinice!10:31
LaneyIIUC10:31
pittiyeah, it would have failed early, during setup-commands10:31
Laneyi386/lgw01 amd64 came a bit later10:31
Laney-y --allow-downgrades FTW10:32
pittiLaney: so we published a kernel update, the daily cloud images grabbed it, then we pulled the kernel update?10:33
Laneyright10:33
pitti"nice" timing10:33
Laneythen you couldn't install linux-* because of the = depends10:33
pittithanks for debugging that10:33
Laneynp, I knew it had happened so it didn't take me long to connect once I saw a failing log10:34
pittiLaney: https://github.com/systemd/systemd/pull/5528 i386 failed; I think that's the one that missed your update by a few minutes, retrying10:36
Laneynod10:36
xnoxsmoser, xe-daemon.service has weird stanzas w.r.t. cloud-init units and it ends up a dependency loop.11:22
xnoxBefore=network.target cloud-init.service cloud-init-local.service seems wrong to me11:22
xnoxi would have thought it should be After=cloud-config.target Wants=cloud-config.target instead11:22
=== hikiko is now known as hikiko|bbl
=== _salem is now known as salem_
=== marcoceppi_ is now known as marcoceppi
=== powersj` is now known as powersj
=== boiko_ is now known as boiko
smoserxnox, did you get sorted on that ?14:23
xnoxsomewhat14:24
xnoxsmoser, i think xe-daemon encodes correctly everything it needs without cloud-init as well.14:25
xnoxbut i will test that out14:25
smoserxnox, it quite possibly does.14:27
smoserjosvaz, was just not interested in pushing an sru at that point.14:27
=== hikiko|bbl is now known as hikiko\
javier4Sorry If I ask the same question again: is there a way to make sbuild ignore checksum of sources inside a .dsc?15:01
tjaaltonLocutusOfBorg: hi, what's up with virtualbox autopkgtests failing?15:14
LocutusOfBorglooking15:14
LocutusOfBorgapw, please merge virtualbox kernel drivers? ^^15:15
LocutusOfBorgtjaalton, seems that the kernel module is already provided in the driver itself, so installing the dkms package is useless15:16
LocutusOfBorgusually kernel people were behind virtualbox version, so the dkms packages was overriding the kernel one15:16
LocutusOfBorgright now this isn't the case15:16
tjaaltonok15:17
tjaaltonthe dkms failure was seen on erlier tests too that passed iirc15:18
apwtjaalton, that is one of those where i need to fix the tests to understand that the kernel also has versions of the driver15:19
apwif the error is "already installed" it should be ignorable15:20
tjaaltonah ok15:24
=== hikiko\ is now known as hikiko
naccrbasak: around?16:40
rbasaknacc: o/16:56
naccrbasak: wondered if you had some time to talk about the -devel pointers?16:56
rbasakSure!16:57
naccrbasak: HO ok?16:57
rbasakYeah. Two minutes please.16:57
naccrbasak: of course16:57
forehelphi 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:14
naccforehelp: wrong channel?17:37
forehelpnacc: yes sorry i asked on the right one17:38
=== ejat_ is now known as ejat
=== hikiko_ is now known as hikiko
=== Dmitrii-Sh_ is now known as Dmitrii-Sh
=== wolsen_ is now known as wolsen
=== tarpman_ is now known as tarpman
=== FourDollars_ is now known as FourDollars
=== maxb_ is now known as maxb
=== apw_ is now known as apw
=== karstensrage_ is now known as karstensrage
=== infinity1 is now known as infinity
=== bigon_ is now known as bigon
=== JanC_ is now known as JanC
=== BrAsS_mOnKeY is now known as g2
=== josepht` is now known as josepht
=== salem_` is now known as _salem
powersjinfinity: slangasek: similar to the server amd64,i386 ISOs, can we get our automated tests blocking the release of those for ppc64el as well?23:17
bulletxt|2hi, can someone be kind enough to see if ubuntu kernel 3.16.x series has the intel i219-lm network driver?  Thanks a lot23:42
bulletxt|2or, how can I see if the intel e1000 loaded driver has such support?23:45
sarnoldbulletxt|2: if I'm reading this correctly, that kernel hasn't had any updates since july https://launchpad.net/ubuntu/+source/linux-lts-utopic23:48
bulletxt|2ok but23:49
bulletxt|2does it have support for the driver? sarnold23:49
bulletxt|2how can I discover this info?23:49
bulletxt|2http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.40/23:49
sarnoldah here we go, here's the git tree http://kernel.ubuntu.com/git/ubuntu-archive/ubuntu-utopic.git/23:50
sarnoldthey apparently move the no-longer-supported ones to ubuntu-archive23:50
sarnoldoh hrm that .. looks too old.23:51
bulletxt|2sarnold: I just need to know if the driver is included in the 3.16 series23:52
bulletxt|2how can I discover this?23:52
wxlbulletxt|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.5923:55
wxllooks like support has existed in that driver since 2012 https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=2fbe4526e5aafc9ffa5d85fa4749a7c5b22af6b223:55
bulletxt|2wxl: no23:56
bulletxt|2its not i21723:56
bulletxt|2its i21923:56
bulletxt|2which came out in 201523:56
wxli quote "e1000e: initial support for i217"23:56
bulletxt|2in my case the card is i219-lm23:57
wxlah23:57
bulletxt|2can you check when that has been added in the official linux kernel? I guess its 4.0 series23:58
sbeattieLooking 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 kernel23:58

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!