/srv/irclogs.ubuntu.com/2015/07/10/#ubuntu-quality.txt

veebersAnyone 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
jhodappballoons, 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
balloonsjhodapp, ahh you put it in qmake!15:17
jhodappyes :)15:17
balloonsI'll have to file that away. That's one way to do it :-)15:18
jhodappindeed, could have done a similar thing in the test .cpp file too15:18
tewardanyone installing wily in a VM environment seeing weird interface names?16:42
teward(like, ens## instead of eth##)16:45
tewardwhere do we report weirdless like that16:48
tewardor did i miss a "This is intentional" notice16:48
balloonsteward, weird interface names?19:00
tewardballoons: see +119:00
tewardballoons: i figured out it's a systemd predictable interface thing19:00
tewardbut i discovered something even more evil19:00
tewardo you aren't there19:00
tewardballoons: anyways, installed system gets interface names by systemd, per http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ is my guess19:01
tewardballoons: but the installer ISO uses kernel unpredictable, eth##19:01
tewardso in my VM, it's ens## on the installed...19:01
balloonsteward, ahh, gotcha19:01
tewardbut in the installer, it's eth##19:01
balloonsI was going to suggest as much. Names can easily be changed when something decides to name them by default19:01
tewardso the installed /etc/network/interfaces is wrong19:02
tewardballoons: the bigger problem is the reboot with the discrepancy in the -server ISOs comes up with broken networking19:02
tewardbecause eth0 != systemd naming19:02
tewardTJ- was poking it in +119:02
balloonsteward, this has the workings of a nice bug report19:02
tewardwhere/how shalt I report it?19:03
tewardballoons: this is with the daily from the 9th19:03
tewardi haven't used the 10ths daily yet19:03
tewardmy guess is same deal, but we could file bug and "Incomplete" in the interim19:03
tewardi just don't know where to file it19:03
balloonsteward, yea, I doubt today's iso is different19:03
tewardballoons: where/what to file against?19:03
balloonsseeing as the new systemd JUST landed19:04
balloonscan you check your version19:04
tewardone moment19:04
balloonsdo you have systemd (222-1ubuntu1)?19:04
tewardi have to reboot the VM xD19:04
balloons:p19:04
balloonsI would report against systemd I thin19:05
tewardack19:05
tewardbut i was dropped into a busybox shell so heh19:05
balloonshttps://bugs.launchpad.net/ubuntu/+source/systemd/+filebug19:05
teward222-1ubuntu2, balloons19:05
tewarddoes ubuntu-bug still work in wily?19:05
balloonsshould, give it a whirl19:05
tewardoh wait19:06
balloonsteward, than yes, you have the new version19:06
tewardpfft it didn't update to it19:06
tewardone moment19:06
tewardlet me reboot and test19:06
tewardupgrade*19:06
tewardballoons: i also assume that's a crit level bug?19:08
teward:P19:08
tewardif it reproduces19:08
tewardalthough i'm almost 100% certain this is still valid19:08
tewardbecause busybox sysvinit/upstart vs. systemd19:09
tewardballoons: what generates /etc/network/interfaces during install?19:09
tewardballoons: also not sure if a security hole, but nonsuperuser can `shutdown -r now` without sudo19:10
tewardDoS vector19:10
tewardballoons: confirmed: installer from the 9th's image detects it as eth0, eth1, systemd detects as ens33, ens3419:11
tewardand the installed /etc/network/interfaces doesn't work so networking doesn't autoconfigure19:12
teward(it installs with eth0, rather than ens33)19:12
tewardso, less a systemd bug, more an installer failure bug19:12
balloonsteward, using ubiquity or debian installer?19:13
tewardballoons: whatever ships with the ISO, since I"m a VMware person19:13
tewardso my guess is ubiquity19:13
balloonsteward, yes ubiquity19:13
balloonsso I perhaps have it affect both19:14
balloonssystemd might be marked invalid or not19:14
tewardack i'll file against systemd and ubiquity19:14
tewardballoons: my guess is a crit level bug though?19:22
tewardgiven that it fails to install the correct settings for networking?19:23
tewardI've set it to high for now19:25
tewardbut eh19:25
balloonsyea, definitely high19:27
tewardballoons: [2015-07-10 15:28:44] <cyphermox> teward: ubiquity when you install in graphical, netcfg otherwise.  <--19:29
tewardperhaps it needs included against netcfg as well?19:29
tewardI used the 'text graphical interface' but not sure if that counts as a gui19:29
cyphermoxI'm not sure, it might just work magically well with netcfg19:29
balloonsaghh.. http://iso.qa.ubuntu.com/ is down again19:29
cyphermoxthis is all pitti's fault :)19:29
balloonsthat was my thought :-)19:30
cyphermoxthat said19:30
cyphermoxteward: 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
tewardcyphermox: confusion of ISO - ubuntu-server-iso19:31
cyphermoxah!19:31
cyphermoxthen netcfg it is :)19:31
cyphermoxI'm somewhat surprised that it doesn't just work too19:32
cyphermoxperhaps there is a file from systemd/udev or something in the installer environment19:32
cyphermoxthings should just be detecting the interface name and using ifconfig or getifbyname and whatnot19:33
tewardIDK, i was going to test the 20150710 iso but eh19:35
tewardprobably still going to remain an issue19:35
jhodappwhen 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!