veebers | Anyone know what the equiv. link now is for this old one? https://developer.ubuntu.com/api/qml/sdk-1.0/QtQuick.qtquick-qmlscene/ | 03:36 |
---|---|---|
=== chihchun_afk is now known as chihchun | ||
=== vrruiz_ is now known as rvr | ||
=== chihchun is now known as chihchun_afk | ||
jhodapp | balloons, just wanted to update you in case you're curious, figured out a way to conditionally run my integrations tests in the silo for qmake with: "system(uname -a | grep arm):SUBDIRS += integration" | 15:11 |
balloons | jhodapp, ahh you put it in qmake! | 15:17 |
jhodapp | yes :) | 15:17 |
balloons | I'll have to file that away. That's one way to do it :-) | 15:18 |
jhodapp | indeed, could have done a similar thing in the test .cpp file too | 15:18 |
teward | anyone installing wily in a VM environment seeing weird interface names? | 16:42 |
teward | (like, ens## instead of eth##) | 16:45 |
teward | where do we report weirdless like that | 16:48 |
teward | or did i miss a "This is intentional" notice | 16:48 |
balloons | teward, weird interface names? | 19:00 |
teward | balloons: see +1 | 19:00 |
teward | balloons: i figured out it's a systemd predictable interface thing | 19:00 |
teward | but i discovered something even more evil | 19:00 |
teward | o you aren't there | 19:00 |
teward | balloons: anyways, installed system gets interface names by systemd, per http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ is my guess | 19:01 |
teward | balloons: but the installer ISO uses kernel unpredictable, eth## | 19:01 |
teward | so in my VM, it's ens## on the installed... | 19:01 |
balloons | teward, ahh, gotcha | 19:01 |
teward | but in the installer, it's eth## | 19:01 |
balloons | I was going to suggest as much. Names can easily be changed when something decides to name them by default | 19:01 |
teward | so the installed /etc/network/interfaces is wrong | 19:02 |
teward | balloons: the bigger problem is the reboot with the discrepancy in the -server ISOs comes up with broken networking | 19:02 |
teward | because eth0 != systemd naming | 19:02 |
teward | TJ- was poking it in +1 | 19:02 |
balloons | teward, this has the workings of a nice bug report | 19:02 |
teward | where/how shalt I report it? | 19:03 |
teward | balloons: this is with the daily from the 9th | 19:03 |
teward | i haven't used the 10ths daily yet | 19:03 |
teward | my guess is same deal, but we could file bug and "Incomplete" in the interim | 19:03 |
teward | i just don't know where to file it | 19:03 |
balloons | teward, yea, I doubt today's iso is different | 19:03 |
teward | balloons: where/what to file against? | 19:03 |
balloons | seeing as the new systemd JUST landed | 19:04 |
balloons | can you check your version | 19:04 |
teward | one moment | 19:04 |
balloons | do you have systemd (222-1ubuntu1)? | 19:04 |
teward | i have to reboot the VM xD | 19:04 |
balloons | :p | 19:04 |
balloons | I would report against systemd I thin | 19:05 |
teward | ack | 19:05 |
teward | but i was dropped into a busybox shell so heh | 19:05 |
balloons | https://bugs.launchpad.net/ubuntu/+source/systemd/+filebug | 19:05 |
teward | 222-1ubuntu2, balloons | 19:05 |
teward | does ubuntu-bug still work in wily? | 19:05 |
balloons | should, give it a whirl | 19:05 |
teward | oh wait | 19:06 |
balloons | teward, than yes, you have the new version | 19:06 |
teward | pfft it didn't update to it | 19:06 |
teward | one moment | 19:06 |
teward | let me reboot and test | 19:06 |
teward | upgrade* | 19:06 |
teward | balloons: i also assume that's a crit level bug? | 19:08 |
teward | :P | 19:08 |
teward | if it reproduces | 19:08 |
teward | although i'm almost 100% certain this is still valid | 19:08 |
teward | because busybox sysvinit/upstart vs. systemd | 19:09 |
teward | balloons: what generates /etc/network/interfaces during install? | 19:09 |
teward | balloons: also not sure if a security hole, but nonsuperuser can `shutdown -r now` without sudo | 19:10 |
teward | DoS vector | 19:10 |
teward | balloons: confirmed: installer from the 9th's image detects it as eth0, eth1, systemd detects as ens33, ens34 | 19:11 |
teward | and the installed /etc/network/interfaces doesn't work so networking doesn't autoconfigure | 19:12 |
teward | (it installs with eth0, rather than ens33) | 19:12 |
teward | so, less a systemd bug, more an installer failure bug | 19:12 |
balloons | teward, using ubiquity or debian installer? | 19:13 |
teward | balloons: whatever ships with the ISO, since I"m a VMware person | 19:13 |
teward | so my guess is ubiquity | 19:13 |
balloons | teward, yes ubiquity | 19:13 |
balloons | so I perhaps have it affect both | 19:14 |
balloons | systemd might be marked invalid or not | 19:14 |
teward | ack i'll file against systemd and ubiquity | 19:14 |
teward | balloons: my guess is a crit level bug though? | 19:22 |
teward | given that it fails to install the correct settings for networking? | 19:23 |
teward | I've set it to high for now | 19:25 |
teward | but eh | 19:25 |
balloons | yea, definitely high | 19:27 |
teward | balloons: [2015-07-10 15:28:44] <cyphermox> teward: ubiquity when you install in graphical, netcfg otherwise. <-- | 19:29 |
teward | perhaps it needs included against netcfg as well? | 19:29 |
teward | I used the 'text graphical interface' but not sure if that counts as a gui | 19:29 |
cyphermox | I'm not sure, it might just work magically well with netcfg | 19:29 |
balloons | aghh.. http://iso.qa.ubuntu.com/ is down again | 19:29 |
cyphermox | this is all pitti's fault :) | 19:29 |
balloons | that was my thought :-) | 19:30 |
cyphermox | that said | 19:30 |
cyphermox | teward: why should there be an eth* or ens* if you're instlaling with ubiquity? | 19:31 |
cyphermox | (the answer is, normally there shouldn't, as it should be managed by NM) | 19:31 |
teward | cyphermox: confusion of ISO - ubuntu-server-iso | 19:31 |
cyphermox | ah! | 19:31 |
cyphermox | then netcfg it is :) | 19:31 |
cyphermox | I'm somewhat surprised that it doesn't just work too | 19:32 |
cyphermox | perhaps there is a file from systemd/udev or something in the installer environment | 19:32 |
cyphermox | things should just be detecting the interface name and using ifconfig or getifbyname and whatnot | 19:33 |
teward | IDK, i was going to test the 20150710 iso but eh | 19:35 |
teward | probably still going to remain an issue | 19:35 |
jhodapp | when building in a wily armhf silo, is /sbin/stop and /sbin/start present? | 19:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!