[00:28] sergiusens: there should be a new image for both rolling and 15.04 [00:28] including your changes [00:28] sergiusens: do we need any extra udf change for azure or is it going to consume the grub data from the rootfs? [00:33] rsalveti: I already tested in the card [00:34] rsalveti: https://trello.com/c/YkdrYyX6/79-rootdelay-300-for-azure-images [00:34] oh, great [00:34] sergiusens: for udf just do one of the options slangasek gave and we should be fine [00:36] rsalveti: I'm going with this one http://paste.ubuntu.com/11659708/ [00:36] great, easy enough [01:38] slangasek: rsalveti I think it needs manual intervention still http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [01:38] delete the powerpc binaries I guess [01:42] right, hopefully slangasek can give us a hand with that [02:00] sergiusens, rsalveti: correct; looking at it now [02:01] binaries removed [03:59] qrl? [04:00] hello? [04:01] good moaning [04:02] how can I begin porting snappy to my desktop [04:03] not like running it virtualized, but actually standalone, with mir or something [04:44] Chipaca: replied to the MP, LGTM [07:03] hey there, does anyone know how to build a working image from device and rootfs tarballs? [07:04] seb128: ubuntu-device-flash will do that, but it will use the system-image server, so it needs to be imported there first [07:04] mvo_, no way to do that locally? [07:05] mvo_, we got a working desktop-next build [07:05] mvo_, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-desktop-next/+build/29166 [07:05] seb128: that is a good question [07:05] not sure what to do from the generated files though now ;-) [07:06] seb128: sergiusens will know if thats possible to do it locally you could shove it into system-image (create a temp channel or something) [07:08] mvo_, well *I* can't I guess, somebody needs to do it for me [07:08] but it's not very handy for local testing [07:09] seb128: agreed [07:09] mvo_, when is sergiusens usually online? [07:09] seb128: sergio will be around in ~4h or so [07:09] k, thanks [07:17] good morning [07:18] hey dholbach [07:18] dholbach, https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-desktop-next/+build/29166 for you [07:18] thanks seb128! :) [07:18] popey, ^ [07:18] dholbach, here is a first working personnal build, good luck trying to make an image from it to put on a device :p [07:19] dholbach, joke aside, waiting for sergiusens now to see how to transform those tarballs in an img that one can dd to a stick [07:19] cool [07:23] good morning [07:24] hi fgimenez, hi willcooke [07:25] hey dholbach [07:28] hi dholbach [07:39] seb128: we need to talk about how we can share code, I am about to fix a bug in one of the hook scripts for ubuntu core and you will have to do exactly the same fix - maybe you can simplify symlink for hooks that are unchanged? [07:39] mvo_, which ppa am I supposed to be using, is it beta? [07:39] with beta I get this: [07:39] ubuntu-snappy : Hängt ab von: ubuntu-snappy-cli (= 1.0.1-0ubuntu1build1) aber 1.0.1-1+439~ubuntu15.04.1 soll installiert werden [07:39] dholbach: yeah ppa:snappy-dev/beta (confusing, right) [07:39] dholbach: please only install ubuntu-snappy-cli [07:39] ok [07:54] good morning mvo_, have a minute? [07:54] fgimenez: sure [07:54] fgimenez: good morning! [07:55] mvo_, :) i'm getting today this output from u-d-f http://paste.ubuntu.com/11666666/ [07:56] mvo_, not sure if it may be related to some misconfiguration on my side? [07:57] fgimenez: *ick* let me see if I can reproduce. what version of ubuntu-device-flash are you using right now? I wonder if there was a new version recently [07:57] fgimenez: this looks a lot like "upstream" [07:57] fgimenez: I'm curious about the version and the ppa you use so that I can try to figure out more [07:58] mvo_, yeah, symlink would make sense, Colin had some comments about that on the merge request for desktopnext, unsure why didrocks didn't do it though [07:58] mvo_, http://paste.ubuntu.com/11666692/ no ppa, just wily [07:59] fgimenez: aha, I think thats the culprit then, hold on a sec, Chipaca fixed this probably but u-d-f will need a rebuild [08:00] mvo_, ok thx! can i use some ppa in the meantime? [08:00] fgimenez: yes - https://launchpad.net/~snappy-dev/+archive/ubuntu/tools should work [08:01] fgimenez: I will do a rebuild in the meantime in wily [08:02] mvo_, ack, i'll try it thanks! :) [08:05] fgimenez: uploaded, should be in the archve later today [08:05] (the fix) [08:15] mvo_, mm i'm not able to install the package from the ppa, it seems that there was a problem with the build https://launchpad.net/~snappy-dev/+archive/ubuntu/tools/+packages [08:18] mvo_, this is what i get from apt-get update after adding the ppa repository http://paste.ubuntu.com/11666876/ [08:29] fgimenez: one sec, let me see if I ca nfix it [08:34] mvo_, thx, no rush at all [08:35] fgimenez: should be in the ppa now [08:36] fgimenez: well, might take some minutes until its published but I copied it to the wily pocket now [08:48] Morning folks, maybe now somebody here to point me to the head tree of Apparmor3 / latest version / patches? [08:49] Good morning all; happy Cars Day! 😃 [09:03] asac, FYI http://paste.ubuntu.com/11667823/ (needed a depmod run, i need to see why thats not in the package) [09:05] mvo_, ok, i have u-d-f 0.22-1+177~ubuntu15.04.1 properly installed :) but i'm still getting the same error http://paste.ubuntu.com/11667736/ [09:06] hmm, owncloud has a broken icon in webdm [09:06] ogra_: phenomenal :) ... yay! [09:06] just ping me and ricmm when the new image up :) [09:06] that works great [09:06] how do i test it ? i have never used owncloud [09:06] thanks so much [09:06] fgimenez: meh, ok, let me try harder [09:06] just check the website is working [09:07] on which port ? webdm doesnt show any info [09:07] oh [09:07] * ogra_ notes 80 in the docker cmdline [09:07] bah, lies [09:09] aha 443 works [09:10] nice ! [09:10] fgimenez: hm, odd. this appears to be working for me (wily with u-d-f from ppa:snappy-dev/tools). anything unusual on your system? ecryptfs? tmpfs for /tmp or anything that you could think of thats might give a clue? [09:13] mvo_, nothing special, this was working as of yesterday [09:14] fgimenez: ok, maybe you can downgrade to the version in ppa:snappy-dev/beta? thats 0.20-something ? and then we tak to sergiusens if he has a idea [09:15] ogra_: can you point me to the git tree i should use for backporting Apparmor3 to my kernel. I would use http://kernel.ubuntu.com/git/jj/ubuntu-vivid.git/log/?h=apparmor , but the tree at http://kernel.ubuntu.com/git/ppisati/ubuntu-vivid.git/log/?h=snappy_odroidc seems to contain a bunch of additional patches. Any idea? [09:15] longsleep: it needs the additional patches [09:15] well the backport does [09:16] jjohansen: Thanks! But where do they come from? [09:16] mvo_, ok thanks [09:16] longsleep, well, i always used ppisati's tree for that [09:16] git clone -b snappy_odroidc git://kernel.ubuntu.com/ppisati/ubuntu-vivid.git [09:16] (see http://people.canonical.com/~ogra/snappy/odroidc/README) [09:16] how the apparmor backport works, is it starts with the base apparmor patchset and then on top of that the backport patches are applied [09:16] ogra_: Right, but i would prefer to understand where the patches actually come from first. [09:16] but i guess that has fallen behind a bit [09:17] longsleep, that you have to ask ppisati ... i was only a consumer of his tree [09:17] yes we need to update the backports kernel tree, I just haven't found the time to do it yet [09:17] (for my first tests i used unpatched BSP kernels, he added the magic for me) [09:17] jjohansen: all right, so the source is somewhere internal for eg apparmor: 3.12 backport mtd: Move major number f83c3838 [09:19] longsleep, give me a sec, I have a repo that is the basis of those patches [09:19] and yes it needs to be updated as well [09:21] longsleep: http://kernel.ubuntu.com/git/jj/ubuntu-utopic.git/ [09:21] * longsleep takes a look [09:21] you can see there are android kernel branches like goldfish-aa3-backport [09:21] yes [09:21] and goldfish-aa3-presquash [09:21] so in some of these branches are the backport fixes? [09:22] the presquash branches have the backport patches split out [09:22] got it - awesome thanks [09:22] yes, you can see the individual changes, and they document which kernel changes they are adjusting for [09:22] i guess i can use that [09:23] this means i grab apparmor3 rc1 tag, and the additional patches with numbers greated than the kernel i base on correct? [09:23] longsleep: updating this to a new better tree against an updated 3.1 kernel is on my todo list [09:23] longsleep basically [09:24] jjohansen: thanks - i guess i have an idea now. Lets see how it goes :) [09:24] how I usually do a backport, is take the whole apparmor dir with the snapshot I want, say from ubuntu-vivid [09:24] just copy the whole dir, over the old apparmor dir, and git add it [09:24] that avoids all kinds of merge conflicts [09:24] jjohansen: yes that is how the docs suggest to do it too. [09:25] mvo_, should I be worried: http://pastebin.ubuntu.com/11667946/? [09:25] then I apply the backport patches on top, working my way backwards [09:25] jjohansen: meaning you start with newer patches first? [09:25] backwards as in 2.10, then 2.9, then 2.8 backport patches, it is the order that the presquash trees use [09:26] yes [09:26] dholbach: it sounds alarming, but should be ok [09:26] all right that is really helpful stuff [09:26] longsleep look at the commit messages for the backborts it will be things like revert 2.10 xxx [09:26] dholbach: its the error that there is a clickpkg user already [09:27] I don't know... [09:27] do you need a bug for it or should I ignore it? [09:27] longsleep: so if you backport to 3.2 you will have a longer patch list than say going back to 3.10 [09:27] dholbach: either is fine, feel free to file a bug [09:27] jjohansen: yes i see that. I need to get the stuff in Kernel 3.10 - so there are only two required as i can see [09:27] thanks mvo_, will do [09:28] ta [09:29] longsleep: hrmm, well that depends on where you start from, vivid and wily have one more patch that needs reverted, I haven't done a backport for that yet [09:29] jjohansen: does it matter where i start from, or can i start say from trusty as well? [09:31] longsleep: vivid and wily are the same, vivid is almost the same as utopic and utopic is a big step over trusty [09:31] jjohansen: ok - a big step for apparmor? But for snappy i it should be vivid/wily ? [09:31] mvo_, bug 1463329 [09:32] bug 1463329 in ubuntu-snappy (Ubuntu) "/nonexistent does not exist, system user clickpkg exists" [Undecided,New] https://launchpad.net/bugs/1463329 [09:32] longsleep: yes for snappy I would start from vivid/wily. [09:33] jjohansen: all right - i have the plan then. [09:33] longsleep: if you can wait a day I will try to get a vivid and wily backport up today [09:33] jjohansen: yeah - i will continue to work on it tonight CEST [09:37] by the way, i suggest that 3.10 upstream Kernel should be a default backport target for apparmor3 as many ARM device Kernel trees are based on 3.10. [09:38] yep [09:40] sergiusens, hmm, is there a way to disable autopilot from u-d-f ? that would really be handy when building for unsupported arches [09:44] ogra_: i learned you can disable it in the oem snap. [09:44] oh [09:45] ogra_: just add autopilot: off to ubuntu-core section or something [09:45] cant remember the exact details [09:46] ogra_: autopilot: false it was [09:47] ogra_: below ubuntu-core tree in config section of package.yaml [09:54] hm, what am I doing wrong with u-d-f? http://paste.ubuntu.com/11668527/ [09:55] pitti, looks like the wily bug with go i hit yesterday [09:55] are you running that on wily ? [09:55] yes [09:55] that might be it then [09:55] dholbach: ta [09:55] . o O { is there anything else? } :) [09:55] someone said wily's go is screwed [09:55] ogra_: ah, I'll try u-d-f from vivid then? [09:56] yeah [09:56] thanks ogra [09:58] ogra_: that fails differently [09:58] weird [09:58] 2015-06-09 09:57:48 ERROR snappy logger.go:199 generic-amd64 failed to install: snappy package not found [09:58] generic-amd64 failed to install: snappy package not found [09:58] it should be self contained i thought [09:58] the "snappy" command exists [09:58] oh, you might also need the snappy from vivid [09:58] (I opened a schroot and installed u-d-f [09:59] it is go as well :) [09:59] ah, not just ubuntu-snappy-cli then [10:00] hm, not the "snappy" package for sure [10:01] mvo_: ok, if you can tell me how one creates a snappy image these days, I'll look at bug 1462954 [10:01] bug 1462954 in Snappy trunk " systemd-random-seed fails to start because /var/lib/systemd/random-seed is read only" [High,Triaged] https://launchpad.net/bugs/1462954 [10:02] mvo_, i've finally got u-d-f working pheww :) it was related to the version of ubuntu-snappy-cli in wily [10:03] mvo_, downloading and installing it from here http://packages.ubuntu.com/vivid/ubuntu-snappy-cli works again, don't ask me why :) [10:05] fgimenez: oh, you have that problem as well? how did you flash snappy? [10:05] fgimenez: (see my backscroll from 5 mins ago) [10:06] fgimenez: so that's u-d-f from wily plus ubuntu-snappy-cli from vivid? [10:06] pitti, i was unable to use u-d-f in wily, this was the error http://paste.ubuntu.com/11667736/ [10:06] fgimenez: yep, exactly what I got and asked [10:06] pitti, yep, ubuntu-snappy-cli 1.0.1-0ubuntu1build1 seems to be somehow broken [10:07] fgimenez: I tried u-d-f (and u-snappy-cli) from vivid, and that fails too [10:07] pitti, unstalling u-snappy-cli and installing vivid's deb worked for me [10:10] I still get "generic-amd64 failed to install: snappy package not found" [10:13] grep -r 'package not found' in goget-ubuntu-touch doesn't have any results [10:13] pitti, it seems to be a different error, mine was "generic-amd64 failed to install: unpack /tmp/generic-amd64310762128 to /tmp/oem535521461/oem/generic-amd64/1.1.1 failed with exit status 1" [10:14] fgimenez: right, I got that with wily's ubuntu-snappy-cli, now I downgraded to vivid's [10:16] ok, I installed parted and ca-certificates, and now it's "generic-amd64 failed to install: exit status 2" [11:01] pitti: what're you doing? [11:01] Chipaca: I'm trying to build a snappy VM image with u-d-f [11:01] pitti: which u-d-f are you using? [11:02] ogra_: needs to be in the oem config [11:02] Chipaca: first I tried wily's, which fails with //paste.ubuntu.com/11667736/ (for ogra, fgimenez and me) [11:02] Chipaca: then I tried in vivid, where it first failed with "generic-amd64 failed to install: snappy package not found" [11:02] sergiusens: is wily's u-d-f the same as the tools ppa's? [11:03] Chipaca: then I installed parted and ca-certificates which got it a bit further, but now it fails with "exit status 2"; that's even with --verbose [11:03] Chipaca: no, it was let through last night [11:03] pitti: you need the tools ppa's one, i guess [11:03] Chipaca: what fails is snappy unpack which is using go 1.4 [11:03] certainly on vivid [11:03] sergiusens: but that's fixed [11:03] it used to work with vivid's version a few months ago (when vivid was still devel) [11:03] Chipaca: in wily? [11:04] Chipaca: as in, in wily with no ppa? [11:04] sergiusens: oahdunno [11:04] sergiusens: but it was failing with vivid's too [11:05] ok, which PPA should I add? [11:05] pitti: i don't think it's ever worked with vivid's since i've been on the project [11:05] pitti: which is... ok, a few months, but with few > 3 i think [11:05] it seemed to work for fgimenez to use vivid's ubuntu-snappy-cli, but I suppose u-d-f is missing a dependency or so [11:05] for sure it's missing parted and ca-certificates [11:05] pitti, not for me, i had the snappy errors on a wily image [11:05] $ cat /etc/apt/sources.list.d/snappy-dev-ubuntu-tools-vivid.list [11:05] deb http://ppa.launchpad.net/snappy-dev/tools/ubuntu vivid main [11:05] is there a --verboserer? [11:05] pitti: ^^ [11:06] Chipaca: thanks [11:06] (i build my images on a trusty machine ... so i have no build issues here) [11:06] pitti: ca-certificates yes, parted no http://paste.ubuntu.com/11669751/ [11:07] hmm, ubuntu-snappy-cli also misses the dep on ca-certificates [11:08] Chipaca, sergiusens pitti in my case downgrading ubuntu-snappy-cli from 1.0.1-0ubuntu1build1 (wily) to 1.0.1-0ubuntu1 (vivid) worked, tested with u-d-f from the archive and from the ppa [11:08] fgimenez: thanks for confirming [11:08] 2015-06-09 11:08:41 ERROR snappy logger.go:199 generic-amd64 failed to install: exit status 2 [11:08] still the same with the PPA [11:09] $ sudo ubuntu-device-flash core --output=/tmp/snappy.img --developer-mode --channel=edge rolling [11:09] mvo_: can you release a new ubuntu-snappy into wily? [11:09] same with "--channel=stable 15.04" [11:09] ogra_, hello, do you want us to start updating the raspi2 section with your image on https://developer.ubuntu.com/en/snappy/start/ or do you think it's better to wait a little for user feedback? [11:09] is there a $DEBUG/--debug or so? [11:10] pitti: only --verbose: u-d-f --verbose core rolling ... [11:10] davidcalle, we should wait for the actual release ... i also plan to push it to http://people.canonical.com/~platform/snappy/ instead of hosting it in my homedir [11:10] sergiusens: I have that already, but it doesn't say much, just http://paste.ubuntu.com/11669805/ [11:11] ogra_, actual release as in "official image"? [11:11] pitti: but I suspect you are going to have issues with ubuntu-snappy-cli [11:11] davidcalle, as in the 15.04.1 release for the rest of the world :) [11:11] ogra_, yay :) [11:11] Hello, I was wondering could somebody clarify steps 2 and 3 from https://developer.ubuntu.com/en/snappy/guides/filesystem-layout/#updating-the-system [11:11] davidcalle, BBB and amd64 images will soon have a point release [11:11] seb128: I'm online [11:11] "Apply the latest system image to the other root partition." [11:12] I assumed the only time when this can be done is from initramfs during boot? because you have to remount read-only partition to read-write [11:12] is that correct? [11:12] [pid 21480] connect(3, {sa_family=AF_LOCAL, sun_path="/run/udev/control"}, 19) = -1 ENOENT (No such file or directory) [11:12] [pid 21480] close(3) = 0 [11:12] gatisp, that is how it works, yes [11:12] [pid 21480] exit_group(2) = ? [11:12] pitti: why did you repeat the same comment on bug 1462954 ? [11:12] bug 1462954 in Snappy trunk " systemd-random-seed fails to start because /var/lib/systemd/random-seed is read only" [High,Triaged] https://launchpad.net/bugs/1462954 [11:12] sergiusens: ^ ah, this might be it? it used to work in a schroot, but maybe not any more [11:13] seb128: mvo_ no easy mechanism for local testing, but livecd-rootfs local building isn't easy to do either [11:13] longsleep: sorry, pressed enter accidentally, and firefox still had my last reply in the input box [11:13] pitti: ah - i was just wondering if i was wrong about the problem. [11:13] ogra_, ok but then docs are are bit confusing, at least when I read it :) because the next steps says "Update the bootloader configuration such that the next boot.." [11:14] ogra_, but what it actually means is not the next boot [11:14] but the ongoing boot? [11:14] gatisp, after "flashing" the bootloader needs to be told to bot from the new partition [11:14] *boot [11:15] ogra_, but doesn't all the happen from the same boot sequence? [11:15] no [11:16] oh, wait, the unpacking on upgrade doesnt actually happen from the initrd ... that happens indeed from the running system before the reboot [11:16] (sorry, my brain was thinking phone updates :) ) [11:17] ogra_: we have inOS updates here [11:17] yeah [11:17] so it unpacks in some read-write partition first? [11:17] gatisp: it's like solaris' live upgrade mechanism [11:17] it uses three partitions [11:17] a is the one you run from ... readonly [11:17] then you have a rw partition for all the writable bits you need [11:18] and then there is b ... b is unmounted when you run from a [11:18] so you can mount it and unpack your stuff [11:18] then tell the bootloader about that and reboot [11:18] ogra_: it's actually mounter in /writable/cache/system (we are getting rid of 'cache' in that path though) [11:19] ah, i didnt know [11:19] i thought we dynamically mount it [11:19] Chipaca, sergiusens: FTR, bind-mounting /run into the schroot helped; now it's working (in vivid) [11:19] * pitti pats strace [11:20] pitti: ot1h, awesome; otoh, why didn't it work wihtout that? [11:20] ok, that clarifies some things, in me head I saw A and B both mounted as read-only at all times when system is running [11:20] Chipaca: I don't know; it used to a few months ago, but not any more [11:21] sergiusens, "/writable/cache/system" is that part open sourced somewhere? [11:21] gatisp: what does "open sourced" somewhere mean? [11:22] I mean can I see that code :) [11:22] gatisp: lp:snappy [11:22] where is that? its my first time here [11:23] bzr branch lp:snappy [11:23] gatisp: http://launchpad.net/snappy [11:23] running that on an ubuntu system gets you the source [11:23] ok, thanks, I will take a look [11:23] (or use a browser to browse it with sergiusens' url) [11:23] ogra_: I bet if someone doesn't know what lp: is, less they know of bzr :-P [11:24] true true [11:24] these days they are equivalent to the sme thing :-) [11:24] longsleep: indeed, works perfectly when touching the file, thanks! (<- mvo) [11:24] sergiusens: otoh, typing bzr will tell you how to get it [11:24] Chipaca: if you are on ubuntu ;-) [11:24] sergiusens: no other operating system exists [11:25] Chipaca: what phone do you use again? ;-) [11:25] sergiusens: an ubuntu phone of course [11:25] * Chipaca hides his android [11:26] * ogra_ shakes head [11:26] * Chipaca ides ogra_'s android too [11:26] hides* [11:26] i'm going to have to change this keyboard soon. or maybe my fingers. [11:27] anyway! back to work [11:27] i havent run any android in about a year now :) [11:27] ogra_: you are a better person than i [11:28] i just dont get along with it anymore after using the ubuntu phone for a while [11:28] the UX feels so clunky [11:28] and swiping from the right never does what i expect ! [11:29] yep [11:29] ogra_: _1 [11:29] +1 I meant [11:29] heh [11:30] I will have to buy Ubuntu phone, its about time to change my Nokia N9 :) [11:42] sergiusens: I did some update to your noUpdateGrub branch, did you already push your new grub.cfg somewhere? [11:43] sergiusens: I think thats the bit missing at this point :) [11:44] hmm our owncloud installation tells me to upgrade it [11:49] mvo_: only thing missing? [11:50] mvo_: sorry haven't checked my email yet, was dealing with irc first :-) [11:56] sergiusens: well, the transition too, but its looking promising [11:56] sergiusens: no worries, its not urgent at all [11:56] sergiusens, hey [11:57] mvo_: looking now [11:57] seb128: hello [11:57] seb128: for s-i we should just get ubuntu-personal/rolling/edge in place, we are going to need it anyways [11:58] sergiusens, we are trying to get a desktop snappy image going, we made cdimage build an image similar to the ubuntu-core one, see https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-desktop-next [11:58] sergiusens, well, wfm if you want, but being able to test locally would be convenient [11:59] seb128: you probably want cprov's branch [11:59] sergiusens, what branch is that and what does it do? [11:59] seb128: https://code.launchpad.net/~canonical-ci-engineering/goget-ubuntu-touch/local_image/+merge/260531 [12:00] sergiusens, thanks [12:00] seb128: I'm not sure it's working yet (given the WiP), the resulting tarball might need some massaging (e.g.; putting the rootfs into /system) [12:02] sergiusens, any recommendation on what I can do with the tarballs from https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/wily/ubuntu-desktop-next/+build/29166 to test the output? [12:02] sergiusens, or where/to who can I request ubuntu-personal/rolling/edge to be configured [12:02] sergiusens: seb128: it seems to work fine (so far), we mangle the rootfs to install packages from -proposed and josepht can help you with further tweaks [12:03] cprov, thanks, see ^ for what I'm trying to do [12:04] seb128: yup, a 'personal' rootfs [12:05] cprov, right :-) [12:05] morning [12:06] hey rsalveti [12:07] hm, goget-ubuntu-touch ftbfs for all archs [12:07] seb128: hey! [12:08] After running bzr branch lp:snappy [12:08] go get -d -v launchpad.net/snappy/... [12:08] I still don't see /writable/cache/system [12:08] rsalveti: that's in the ppa; I'm disabling that building now that wily is working [12:09] sergiusens, ogra_ ^ am i missing some step? [12:13] sergiusens: ftbfs in the archive: https://launchpad.net/ubuntu/+source/goget-ubuntu-touch/0.22-0ubuntu3 [12:14] after mvo_ uploaded a new version [12:14] rsalveti: that's fine [12:15] rsalveti: this is why I wanted it updated in the archive, to play API change catchup ;) [12:15] sergiusens: how can a ftbfs be fine? :-) [12:15] rsalveti: I never asked you to rebuild u-d-f ;-) [12:15] haha, guess that happened yesterday already once you uploaded a newer version [12:16] oh, mvo_ that u-d-f rebuild isnt' needed [12:16] sergiusens: is this because of go 1.4? [12:16] mvo_: snappy unpack needed fixing and getting a rebuild of ubuntu-snappy-cli is enough for that [12:16] rsalveti: no, because lp:snappy has changed a lot with all the refactor that's going on [12:17] seb128: yeah, would also point you to the ci guys, since they have a way to use the rootfs (from live-build) when flashing with u-d-f [12:17] don't remember if we had an MR for it [12:17] rsalveti: already dealt with ;-) [12:17] seb128: the system-image server was also modifying the image, but ogra pushed the changes into the initrd now [12:17] just don't know if you're using the same initrd [12:17] rsalveti: but would be good for someone to setup ubuntu-personal/rolling/edge in any case [12:18] rsalveti, there was nothing to push for core ... only touch [12:18] ogra_: link for mtab? [12:18] that wasnt in the initrd :) [12:19] don't remember where you landed that :-) [12:19] livecd-rootfs [12:19] then seb128 should already be using that, I'd imagine [12:19] * ogra_ checks before talking nonsense [12:20] yeah [12:20] 2.304 and 2.305 have the changes [12:20] cool then [12:21] mtab, /lib/modules, /lib/formware and /userdata|/writable (depending on the flavour) [12:21] *firm [12:22] seb128: and to auto import ubuntu-desktop-next in system-image I guess you'd need to ping slangasek [12:22] or sil2100 [12:22] rsalveti, ok, thanks [12:24] mvo_: sergiusens: what is still missing to get https://bugs.launchpad.net/snappy/+bug/1462916 fixed for 15.04.1? [12:24] Ubuntu bug 1462916 in Snappy 15.04 "Simplify TMPDIR handling" [High,In progress] [12:24] rsalveti: I'll defer to Chipaca [12:25] iirc this is the last standing bug we have [12:27] mvo_: with lp:~mvo/ubuntu-core-launcher/tmpdir-simplify-lp1462916 merged and the associated u-c-security also in, tmpdir handling is done, right? [12:28] rsalveti: (afaik it's done) [12:28] where done means 'on trunk' [12:28] Chipaca: guess that everything is pushed to trunk, but nothing released yet [12:28] not 'on 15.04' [12:28] right [12:28]