[07:35] good morning [08:04] good morning [08:17] good evening (from Tokyo) [08:23] hey good morning fgimenez and tetor1 [08:23] tetor1: well, good evening for you of course :) still morning here in europe [08:23] hi mvo :) [08:24] I'm looking for ideas how to do git branches similar to bzr pipelines or LPs prerequiste branches model so that I can work on a set of changes but broken into smaller branches [08:25] fgimenez or Chipaca, any ideas? [08:41] mvo, afaik you could branch from a base branch, which would be the equivalent of the prerequisirte, but i think that nothing prevents you from merging the dependent branch before its dependency (which would merge the complete diff) [08:43] mvo, imo the model is different here, the work should be split in small chunks and rebased frequently to master, or the long lived branch taken as base [08:44] mvo: you create a long-lived staging branch, do your work against that, then merge that into trunk? isn't that the git way? [08:45] mvo: what fgimenez said [08:45] mvo: but i'm not a git expert at all [08:45] Chipaca, fgimenez: thanks, I will try that [08:47] good morinng [08:57] good morning all [09:09] noooooooooooooooooooo! [09:13] what on earth is up with that guy [09:13] s/guy/person [09:15] wrong chat, I suppose :D [09:18] is there any string I can get from shell that differentiate Snappy from other Linux distro? [09:34] clobrano: not afaik. I think /etc/ubuntu-build is there on both snappy and click for example [09:35] clobrano: wrt wrong chat, no: Guest42341 comes in every day, shouts something, and goes away [09:36] Chipaca: about Guest42341 I did'n know :D [09:36] clobrano: and now that i've said two things with the same length I've got to try to say more [09:36] Chipaca: ok for the string, I'll ask the user to select the OS ;) === vrruiz_ is now known as rvr [09:45] Chipaca: Hey, i am still having issues with seccomp and Nginx on snappy. Would you eventually have some time to help me figuring out why exactly i see no audit logs for seccomp and Nginx just works when i add @unrestricted to its profle, but does not with snappy common + networking + network-service? [09:46] longsleep: sure, bring it on. At least until somebody more knowledgeable on seccomp/apparmor shows up :) [09:46] Chipaca: ok awesome - first thing i do not understand is if i should get seccomp reject messages in syslog [09:46] (or how they would look) [09:46] longsleep: if seccomp is what's blocking things, yes you should [09:47] Chipaca: yeah i thought so too, but i do not have a single seccomp message in my log [09:47] longsleep: and sc-logresolve should find those for you [09:47] Chipaca: yeah - that command shows nothing unfortunatly [09:48] longsleep: and no DENIED either? [09:48] Chipaca: i only see DENIED when running with @unrestricted in the seccomp profile (apparmor DENIED) [09:49] Chipaca: like this http://paste.ubuntu.com/12988041/ [09:49] interesting! [09:49] but this is with @unrestricted - if i run restricted it just crashes when forking without any message to the logs [09:50] longsleep: and “sudo snappy service logs” doesn't give you anything either? [09:50] Chipaca: nothing related to audit [09:51] Chipaca: i also have a hard time to figure out where it is crashing. The syscalls it is using are all in the seccomp profile. [09:51] Chipaca: so i am trying to figure out why @unrestricted makes it work [09:51] longsleep: have you strace'd it with and without? [09:52] longsleep: (the strace needs to go outside of confinement -- if it's a service, in the .service file) [09:52] Chipaca: How can i strace it when a child process is crashing but the main process works fine? [09:52] Nginx uses a master process, which works fine, that spawns worker processes - and those crash when [09:53] started [09:53] or created - not sure [09:53] longsleep: strace -f follows forks [09:53] ok let me try that [09:53] longsleep: strace -ff splits each fork's trace into a different file [09:53] longsleep: you'll have to copy strace in [09:53] Chipaca: that might help in figureing out why it crashes [09:53] Chipaca: sure - hold on a sec [09:54] What i still do not get is why i do not get seccomp logs though [09:54] longsleep: yeh. You should be seeing logs, so that's a question for jdstrand i think [09:54] I mean i run kernel 3.10 - maybe i am missing something there but i have checked and did not find anything [09:57] oh, that's fairly old isn't it? [09:57] $ uname -r [09:57] 4.2.0-16-generic [09:57] yeesh [09:58] Chipaca: yeah - ODROID is sadly stuck at 3.10 [09:58] longsleep: anyway, strace should shed light on it one way or another [09:58] ok i got strace now [10:01] Chipaca: ok the crash case seems simple: http://paste.ubuntu.com/12988105/ [10:02] longsleep: that's seccomp alright [10:02] longsleep: you need to know what comes *next* though :) [10:02] yeah on it [10:02] :) [10:02] setgid32(0) [10:02] thats next [10:03] ah i see and that is commented in the profile [10:03] # snappy doesn't currently support per-app UID/GIDs so don't allow this family [10:03] # of syscalls. To properly support these, we need to have syscall arg filtering [10:03] # (LP: #1446748) and per-app UID/GIDs. [10:03] Launchpad bug 1446748 in ubuntu-core-security (Ubuntu) "implement seccomp filtering by argument" [Wishlist,Triaged] https://launchpad.net/bugs/1446748 [10:04] Chipaca: that was helpful - thanks! [10:04] Good morning all; happy Wednesday, and happy International Animation Day! 😃 [10:04] Chipaca: so what do i need to do, to get some seccomp profile which allows this? [10:05] longsleep: can't you tell nginx not to switch users? [10:05] Chipaca: no :/ [10:06] Chipaca: it always switches to whatever configured or nobody when run as root [10:06] Chipaca: only way it will not switch is when not run as root [10:06] longsleep: we need to poke jdstrand then [10:07] longsleep: maybe allowing just switching to nobody is possible [10:08] Chipaca: yeah that would be a good idea probably, but as long as bug #1446748 that might be hard [10:08] bug 1446748 in ubuntu-core-security (Ubuntu) "implement seccomp filtering by argument" [Wishlist,Triaged] https://launchpad.net/bugs/1446748 [10:10] Ah i just found why i missed finding the syscall in the first place [10:10] Linux 2.4 added setgid32() supporting 32-bit IDs. The glibc setgid() wrapper function transparently deals with the varia‐ tion across kernel versions [10:10] "transparent wrapper function" ... [10:11] glib is full of those [10:12] Chipaca: so i can fix this by patching Nginx - leaves the issue why i cannot see seccomp denies in the logs [10:19] Chipaca: another approach would be if snappy would somehow run a service as non root [10:19] Chipaca: the check in nginx is simple: if (geteuid() == 0) { === greyback__ is now known as greyback [10:32] mvo: wrt https://travis-ci.org/ubuntu-core/snappy/builds/87841510, comment out or skip the last line in that test [10:35] Chipaca: thanks, I will do that now, I was not sure what its doing [10:35] mvo: trying to test that which go deems unknowable [10:35] Chipaca: yeah, I figured it from your conversation from last night :) === lifeeth_ is now known as lifeeth [10:42] mvo: all the branches are blocked by that, so maybe i should make a separate branch just for this [10:42] mvo: what say you [10:42] Chipaca: yeah, I was thinking the same [10:42] ok, coming up [10:48] Chipaca: how does https://github.com/ubuntu-core/snappy/compare/ubuntu-core:master...mvo5:bugfix/fix-daemon-vet-issue?expand=1 look? [10:48] mvo: that's relying on the same undefined behaviour [10:49] fighting with git now, it doesn't want to push stuff [10:49] but i've got a branch for it [10:49] Chipaca: I have no strong opinion but it seems like we can add a comment and once the undefined behavior actually bites us we remove the test [10:50] Chipaca: it seems right now undefined means "may change in future compiler versions" [10:51] Chipaca: but if removing is the better option, I don't mind [10:51] gah [10:52] how do i set a branch's "upstream"? [10:52] ogra_, mvo: you know if /etc/network/interfaces.d/eth0 is present in all Ubuntu Core snappy images by default? [10:52] Chipaca: not sure I understand the question? hangout? [10:53] morphis: it wil generated on first boot [10:53] morphis, it gets created on firstboot by snappy config [10:53] so lets say, when I have a image with the network-manager snap included I just need to change the snappy configuration of the image at build time? [10:54] if you have an oem snap that defines that the nm-snap gets included you can also set default config options in its yaml file for snappy config [10:54] ok [10:55] i dont think we have a way to not create the file at all though ( Chipaca would know if thats possible) [10:58] other than not having an ethernet device, no there isn't [10:58] morphis: what's breaking? [10:58] Chipaca: nothing [10:59] nobody said anything is broken :) [10:59] Chipaca: however as we have network-manager now we want network-manager to control eth0 rather than ifupdown [10:59] I could just teach networkmanager to still use eth0 even if its configured through eth0 [11:00] i'd rather we taught snappy a new config option [11:00] Chipaca, well, nm is in a snap ... you dont want that option in ubuntu-core i guess [11:01] /etc/NetworkManager/NetworkManager.conf has the "managed=" option for that ... [11:01] so you want to have a config option in the nm snap that sets it and have your oem snap set this to true [11:02] (that way an admin/integrator can still disable it and keep the wired config in ubuntu-core if wanted) [11:04] ogra_: I see [11:05] mvo, so i managed to get the rolling edge images to build again after all of LP was switched to xenial ... [11:06] mvo, can we go over https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages?field.name_filter=&field.status_filter=published&field.series_filter=wily and see what needs to be forward copied for xenial (and what goes to the archive instead) [11:07] since ubuntu-snappy 1.6 was never uploaded to wily i assume we want to forward port it ? apparmor and ubuntu-core-config seem fine to come from the archive ... i'm not sure about the go* packages in that list [11:08] s/forward port/forward copy/ [11:09] (btw, 209 is our first xenial image in rolling/edge, if anyone wants to test that) [11:13] mvo: https://github.com/ubuntu-core/snappy/pull/21 and thanks again [11:14] Chipaca: could you please remove the "fmt" import in there too and just "git commit --amend" and "git push -f"? [11:14] mvo: you mean, actually run tests? [11:14] Chipaca: well, thats not needed :P [11:14] Chipaca: travis is doing that for you and tells you it's failing [11:14] sorry, got carried away with this argh-why-is-push-not-working and forgot i was actually in the middle of it [11:15] Chipaca: no problem at all [11:25] mvo: https://github.com/ubuntu-core/snappy/pull/21 is green [11:29] tedg, will snapcraft move to github too? [11:35] mvo: any idea why git is angry-red-highlighting the second-plus lines in the pot diff in https://github.com/ubuntu-core/snappy/pull/14/files ? [12:05] dholbach, ?? [12:05] ogra: mh? [12:05] (community sync) [12:05] (another meeting that nicely moved 2h) [12:06] oops.... sorry [12:06] I'll be right there [12:15] ogra_: thanks, I think we pretty much want it all in the archive [12:16] Chipaca: I don't know why its angry red, sorry [12:16] mvo: and do you know how to ask travis to do its thing again? [12:17] there's supposed to be a "rebuild" button, but i can't even find the build tab :) [12:17] Chipaca: I'm dong that now, there is a retry button [12:18] * ogra_ notes down "mvo is dong now" [12:19] ogra_: "dong that"* [12:19] *cough* [12:19] doing [12:19] DOING [12:19] *sigh* [12:19] mvo: too late, your profile has been updated [12:20] * ogra_ grins evil [12:42] Chipaca: Patch to make Nginx run on snappy: http://paste.ubuntu.com/12989119/ [12:51] morning! [12:51] question: how can I know (manually, like browsing a web page) which version of a snap is published? thanks! [12:55] Facu: are you the owner of the snap? [12:56] Chipaca, nop [12:56] Facu: GET -H "Accept: application/hal+json" -H 'X-Ubuntu-Frameworks: ubuntu-core-15.04-dev1' -H 'X-Ubuntu-Architecture: armhf' -H 'X-Ubuntu-Release: 15.04-core' -H "X-Ubuntu-Device-Channel: stable" https://search.apps.ubuntu.com/api/v1/package/webdm [12:56] Facu: for example [12:57] Chipaca, ah, no web page? [12:57] Chipaca, thanks! [12:57] Facu: i'm not sure web pages know about channels yet [12:57] Facu, https://uappexplorer.com/apps?type=snappy [12:57] (thats a community page for phone apps, but it also lists snaps) [12:57] yeah, was just about to point at https://uappexplorer.com/app/webdm.canonical [12:58] Facu: version is in the "info" tab [12:58] but, no channels [12:58] awesome! [13:00] Chipaca, ogra_, thank you very much [13:00] Facu: that'll be (another) beer [13:01] Chipaca, we don't drink enough beers together :/ [13:01] Facu: i agree [13:03] sergiusens: hey === chihchun_afk is now known as chihchun [13:17] zyga, ho [13:20] sergiusens: hey, I have a question [13:21] sergiusens: building a snap I ran across an error I'm not familiar with [13:21] sergiusens: Failed doing pull for foo: [Errno 1] Operation not permitted: '/home/zyga/foo/parts/foo/install/sbin/mount.ntfs' [13:22] sergiusens: does that sound familiar? [13:22] sergiusens: this is snapcraft trunk [13:23] sergiusens: dholbach was asking whether snapcraft will move to github. Thoughts? [13:36] tedg, heh; soonish, lets get 0.4 out the door first [13:36] zyga, that's from a stage package, right? Are you in a container? [13:36] zyga, if you are in a container, check if it is suid; that might be it [13:41] sergiusens: not in a container [13:41] sergiusens: vanilla wily [13:43] zyga, what snapcraft are you using and I guess this is from a deb, right? [13:43] not all debs just work [13:44] zyga, btw, I was pinging you yesterda as guacamole and trusty and maybe first moving our current cli to it and then do the new one [13:45] sergiusens: I'm using snapcraft trunk [13:45] sergiusens: mmm, yeah that's doable [13:46] sergiusens: I'm commited to snappy topics as soon as today ends :) [13:46] sergiusens: as for ntfs, not sure, it's nothing new [13:46] sergiusens: I can run snapcraft again and it "works" but I suspect it just didn't notice the problem and marked the prior stage as done [13:46] sergiusens: stage packages have [13:46] stage-packages: [13:46] - libglib2.0-dev [13:46] - libnl-genl-3-dev [13:46] - libssl-dev [13:48] sergiusens: I'll try some more, thanks [13:48] sergiusens: a lot of stuff has changed over the past month :) [13:57] zyga, yeah, bot not deb handling ;-) [13:57] *but [14:03] sergiusens: where did handle source options something go? [14:03] sergiusens: aka def pull() [14:03] zyga, into the base plugin [14:03] zyga, you complained about it, remember ;-) [14:04] zyga, and the implementation is now in sources.py [14:06] sergiusens: yeah, I just realized why it didn't work [14:06] sergiusens: it now relies on schema [14:06] sergiusens: and I had a custom one, no worries now [14:06] sergiusens: thanks! [14:10] zyga, right 'snapcraft help plugins --devel' [14:10] oh [14:10] nice [14:13] sergiusens: I have a problem, I need an extra ppa and so I have this hacky patch, http://bazaar.launchpad.net/~zyga/snapcraft/plainbox/revision/256 [14:13] sergiusens, nice work on 'snapcraft help'! [14:14] I just found a small issue with it: http://pastebin.ubuntu.com/12989697/ - shall I file a bug? [14:14] zyga, look at the ros plugin [14:14] sergiusens: this howerver, now (but not before), started to cause issues with apt [14:14] sergiusens: thanks! [14:14] zyga, it is undocumented, there's and extra sources attrib [14:14] nice [14:16] ogra_, when booting rolling/edge 210: Press Enter for maintenance (or press Control-D to continue): [14:16] tgm4883, do you see an nls codepage error somewhere in the boot lo ? [14:16] *log [14:16] err [14:16] fgimenez, ^^^ [14:17] we usually et that when it cant mount /boot due to missing vfat modules [14:17] dholbach, yeah [14:19] thanks sergiusens [14:19] https://bugs.launchpad.net/snapcraft/+bug/1510954 [14:19] Launchpad bug 1510954 in Snapcraft "Help crashes if specified plugin does not exist" [Undecided,New] [14:20] ogra_, nope http://paste.ubuntu.com/12989745/ [14:22] fgimenez, hmm, it doesnt seem to get to mount /boot at all [14:26] looks like systemd to me [14:27] sigh, so i guess i need to try myself to debug this [14:28] that seems to go deeper [14:33] ogra_, booting from a udf generated image it throws me to emergency mode [14:33] well, the same one as in the paste, right ? [14:34] ogra_, yep, it shows more text anyway, journalctl -xb shows errors about mounting /etc/watchdog.conf, don't know if it might be related [14:34] are you sure thats 210 ? [14:35] the watchdog stuff should be fine in that one [14:36] ogra_, yep, sudo ubuntu-device-flash core rolling -o kvm-rolling-edge.img --channel edge --developer-mode [14:36] hmm, k, i'll check that [14:39] i dont see it starting udev in your paste [14:45] ogra_ the paste comes from autopkgtest, don't know if it's complete, for example booting the image with kvm shows the emergency mode welcoming text that is not present in autopkgtest's output [14:54] sergiusens: http://bazaar.launchpad.net/~zyga/snapcraft/plainbox/revision/256 [14:54] sergiusens: do you think it would be appropriate to just not inspect symlinks at all? [15:01] zyga, we've been asked for the opposite as dangling symlinks in a snap are not allowed [15:12] writing 4G at 20MB/s gets old [15:14] use --faster [15:19] i'm getting dropped into emergency thing [15:19] on bbb rolling/edge [15:19] Chipaca, see above [15:19] sergiusens: ah [15:19] xenial isnt ready yet it seems [15:19] ogra_: ouh [15:20] i'll get to debugging it soon ... [15:20] ogra_: do you know offhand what's the latest edge that boots? [15:20] the last wily image was 208 ... [15:20] good enough :) [15:20] thanks [15:20] 209 was completely broken, 210 is the first actual xenial image [15:22] ogra_: i got to see "welcome to ubuntu 16.04", so that's nice :) [15:22] ah, it moves on properly when you hit ctrl-d ? [15:22] no, it prints that before emerg mode [15:22] ah [15:23] in other news, if you don't plug in the sd card, dd is super fast! 843MB/s!! [15:23] lol [15:23] and you get a new device node in /dev for free as well ! [15:24] dholbach, https://code.launchpad.net/~sergiusens/snapcraft/1510954/+merge/276013 [15:25] ogra@styx:~/Devel/images$ sudo ubuntu-device-flash core --channel edge -o xenial-rolling.img ----developer-mode rolling [15:25] Determining oem configuration [15:25] generic-amd64 failed to install: snappy package not found [15:25] hmpf [15:25] oh [15:26] perhaps i tried to hard to use developer mode :P [15:26] ogra_, how many - do you need? don't waste them [15:26] https://code.launchpad.net/~dholbach/snapcraft/integrate-snappy-tutorials-build-snaps/+merge/276012 [15:27] ogra_: rolling edge #210 amd64 doesn't boot [15:27] elopio, yes [15:27] see above [15:27] i'm u-d-f'ing ... [15:27] to debug [15:28] sorry, I'm late :) [15:28] :) [15:28] sergiusens: I think that's a valid thing to do, maybe the exception could be something that we have in the image already [15:29] sergiusens: I don't even know why ntfs is pulled in, I worry that if we are too strict about it, we'll break a random snap out there that doesn't rely on the symlink, just on some package that pulls it in [15:29] zyga, right, the problem is 'being in the image already' can only be guaranteed for libc6 and that is the only thing we leave dangling today [15:30] zyga, right; ubuntu debs in stage packages are going to need a lot of refinements as we go [15:30] seb128: hey, do you have an ubuntu-personal system available? if so, can you paste the output of 'snappy list' on that system? [15:31] jdstrand, hey, no sorry, the image have been discontinued before wily [15:31] ogra_: 208 also lands me in emergency mode [15:31] Chipaca, uuuh, any error ? [15:31] or Chipaca a quick one https://code.launchpad.net/~sergiusens/snapcraft/1510954/+merge/276013 [15:31] seb128: as in, ubuntu-personal images are no longer being generated or you just happen to not have one? [15:31] jdstrand, they are not longer generated [15:31] I see [15:32] thanks [15:32] yw [15:32] ogra_: some not relevant i think ,but: [15:32] ogra_: etc-watchdog.conf.mount: Mount on symlink /etc/watchdog.conf not allowed. [15:33] Chipaca, yeah, thats known [15:33] ogra_: that's about it [15:34] the fix went in but there were no wily images anymore [15:34] not sure that can block the boot [15:34] will try going back one further [15:34] see what happens [15:35] are there any known issues in u-d-f on trusty? I just got a report that it does not work and fails with error while executing external command kpartx -ds spreedbox-15.04-stable-dev.img: device-mapper: remove ioctl on loop0p4 failed: Device or resource busy [15:35] loop deleted : /dev/loop0 [15:35] anyone seen this before? [15:35] (it works the very first time after boot) [15:36] longsleep: that's an error that comes up often with u-d-f, that we don't have a good way to fix [15:36] longsleep: at least we haven't found it yet [15:36] longsleep: but you can clean up and try again [15:36] Chipaca: oh - it never happend for me [15:36] sergiusens: I agree with both [15:37] Chipaca: how to clean up? losetup -d and kpartx -d did not help [15:37] 1 sec [15:37] longsleep: sudo dmsetup clear loop0p4 && sudo losetup -d /dev/loop0 && sudo kpartx -ds /dev/loop0 [15:38] Chipaca: cool [15:38] longsleep: after that "sudo losetup -l" should be empty [15:38] Chipaca: He will try it in a moment [15:38] Chipaca, the root cause is generally a failure to unmount do to a missing .Close() [15:39] sergiusens: shaaaaame [15:40] ogra_: just in case, am i missing anything? ubuntu-device-flash --revision 207 core rolling --oem=beagleblack --channel edge -o bbb_rolling_edge.img --developer-mode [15:40] Chipaca: i can confirm that your commands do the trick and resolve the issue - thanks. Though for him it is always required. [15:40] Chipaca, right; the snappy tests need to check for left over FDs if easy to do :-) [15:41] Chipaca, should work, yes [15:41] longsleep: it *never* succeeds for him? [15:42] Chipaca: it never seems to clean up after it ran before, though u-d-f does not finish because it does not find a snap defined in the oem yaml [15:42] Chipaca: maybe that is related and it does not properly cleanup in this case [15:43] ok, i found the issue ... [15:43] ogra_: \o/ ? [15:43] seems ubuntu-core-config is broken in xenial [15:43] ogra_: /o\ [15:43] i'm sure i dropped watchdog.conf and /etc/default/watchdog before from it [15:43] but they are in writable-paths so systemd tries to double mount [15:44] yup, removing them both makes it boot fine [15:47] ok, fix uploaded [15:47] next image should boot [15:51] zyga: your landing bot might be a little too verbose :) [15:53] ogra_: 207 *also* lands me in emergency mode [15:53] ogra_: wat [15:53] elopio: https://bugs.launchpad.net/launchpad/+bug/1510993 [15:53] Launchpad bug 1510993 in Launchpad itself "Regression in tracking merged git merge requests" [Undecided,New] [15:54] elopio: perhaps that's the reason [15:54] Chipaca, sure, the fix landed in wily when the buildds were already switched to xenial i fear you have to go far further back to have a booting image [15:54] like ... before watchdoog was added [15:55] * Chipaca goes back to 200 [15:56] as per bug 1503329 187 booted, so that's the farthest back i'll have to go [15:56] bug 1503329 in Snappy "not getting an ipv4 address on the first boot" [Critical,Confirmed] https://launchpad.net/bugs/1503329 [15:56] zyga: I mean that the two messages after the +1 seem unnecessary. The approval generally says thanks. And launchpad will send a message when the merge is done. [15:57] elopio: ah, I see [15:57] elopio: yeah, you are right [15:57] elopio: I can remove that [15:57] elopio: btw, what are you using it for? [15:57] zyga: tarmac by default just talks if something goes wrong. [15:58] zyga: I'm not using anything in there. Somebody subscribed me to those branches, so I woke up to tons of your bot messages. [15:58] well, not tons. [15:58] many. === chihchun is now known as chihchun_afk [16:11] ogra_: could you kick off an image build, at least for armhf? [16:13] bootcharts on the bbb or wiiiiiiiiiide :) [16:22] ogra_: with modprobe + modules in oem, we can make the bbb bring up the option module with the right bits! [16:32] Chipaca, i'll kick an image as soon as https://launchpad.net/ubuntu/+source/ubuntu-core-config/0.6.31 is ready [16:32] proposed migration is sloow atm [16:32] :) ok [16:33] ogra_: anyway, i'm not blocked by that [16:33] have plenty to figure out here :) === fionnan_ is now known as fionnan [16:35] Chipaca, remount / rw ... remove all lines mentioning watchdog from /etc/system-image/writable-paths and be fine ... [16:35] (from the emergency shell) [16:36] next boot will just work [16:38] i'll try that [16:38] which version of snappy do i need for service logs to work? [16:38] system-ifup.service is not present in 208, which is strange [16:40] Chipaca, does that come from snappy ? [16:40] (the ubuntu-snappy package ) [16:40] snappy_: 5 [16:40] ogra_: not afaik [16:40] hmm [16:40] ogra_: i mean 200, not 208, there [16:41] ogra_: am updating to 208 now [16:41] ah [16:41] ogra_: probably part of the systemd changes [16:41] ogra_: but if so, possibly bad news for this fix on stable [16:41] we'll see [16:42] yep [16:47] * ogra_ twiddles thumbs ... [16:47] come on publisher [16:48] sergiusens, why did you unmilestone all the milestone 0.4 bugs ? [16:49]