=== chihchun_afk is now known as chihchun === shuduo is now known as shuduo-afk === shuduo-afk is now known as shuduo === shuduo is now known as shuduo-afk [10:04] hi all :) has anyone had success with snappy on scaleway VPS provisioning? [10:22] what must be the value for "init" in bootargs for an armhf device? is it "init=/lib/systemd/systemd-udevd" ? [10:23] it results in "Failed to read /proc/cmdline, ignsystemd-udevd[1]" error [10:23] anyone? [10:58] prasad, http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-systems/files ... take a look at the uboot.env.in files in the subdirs of the arm based devices there === vrruiz_ is now known as rvr [11:38] 12:19 < popey> http://imgur.com/RNyqX2C [11:38] resolved by pulling power cable out and powering again [11:38] not good [11:40] Good morning! [12:44] jdstrand: I'm getting checksum mismatch when unsquashfs'ing and resquashing my snap. https://myapps.developer.ubuntu.com/dev/click-apps/4710/rev/10/ [12:53] josepht: how did you build your snap? [12:53] jdstrand: with snapcraft on a rpi2 [12:53] jdstrand: 16.04 [12:56] josepht: what version of snapcraft? [12:56] jdstrand: 2.6.1 [12:57] ok, the issue isn't obvious. I'll have to look into it [12:58] jdstrand: ack, thanks. What I tried was to unpack the squashfs and repack it. 'file' showed a 4 byte difference between the two. 'ls' and 'grep' couldn't find any difference between the two unpacked filesystems. [14:27] kyrofa, elopio can we start 10 after? [14:27] sergiusens, no problem :) [14:32] elopio, is there a way to know that a PR is not up-to-date with master, but not make it _required_? [14:38] Is there some way I can force the writable filesystem to resize as it failed on my pi - 16GB card has only 3.4GB writable [14:39] popey, you can do it manually [14:43] how? [14:44] (please don't say take the card out and put it in another computer and use gparted) [14:52] popey: use fdisk, delete the partition, recreate the partition. Reboot. run: sudo resize2fs /dev/mmcblk0p2 [14:57] leftyfb: will i lose any data? [14:58] popey: no [14:58] sweet [14:58] * popey will blame you if I do :) [14:58] actually [14:58] shouldn't need to delete the partition [14:58] /dev/mmcblk0p2 270336 31250000 30979665 14.8G 83 Linux [14:58] it is the right size, just looks like I need the resize2fs ? [15:02] /dev/mmcblk0p2 15G 3.4G 11G 24% /writable [15:02] \o/ [15:02] thanks [15:33] josepht: can you request a manual review? I'm going to accept it for now [15:33] jdstrand: okay, thanks [15:44] jdstrand: hey, you running a xenial core? curious what 'snap find mir' returns you? [15:44] ...or anyone else who might be tinkering today ^ [15:45] i may have found a bug in the store [15:46] so i had mir 1 & 2 published, it returned 2....then published a mir 3, and unpublished 2...so only 1 & 3 are published...now find just says "no snaps found" [15:46] beuno: ^ [15:49] beuno: oops...nvmd...it was me....channels! [15:49] but...i had to pick stable? [15:50] thot, if xenial is still rolling edge...it would appear in edge? [15:52] kgunn: it seems you don't still need me? [16:02] jdstrand: yep, sorry for noise [16:05] jdstrand: sorry, I requested the manual review for a bad upload (arm version with amd64 as the arch.) I re-request a review of revision 9 === chihchun is now known as chihchun_afk [18:10] sergiusens, I hit a snag trying to remove the ld.so.conf stuff. The libs still need to link up at build time, and that code was used for build- and run-time dependencies [18:11] So it appears that we may still need it at least to build stuff with libs in non-standard places [18:12] sergiusens, unless you can think of a better way to do that [18:12] kyrofa, let's just leave it in for now [18:13] sergiusens, okay. Let's keep it in the back of our minds anyway [18:13] kyrofa, can you rebase with master btw (or my branch)? [18:13] kyrofa, yeah let's get a bug report going [18:13] sergiusens, will do [18:55] just updated my pi 2 edge and again it didn't come back after a reboot :( [18:56] Reboot to use canonical-pi2-linux version 4.4.0-1004-raspi2+20160321.17-52. [18:56] Reboot to use ubuntu-core version 16.04+20160321.17-37. [18:56] that update [19:19] kyrofa, did you rebase? [19:22] sergiusens, not yet... ran into another issue... working it out [19:22] ack [19:22] I swear the universe doesn't want me splitting the unpacking of stage packages out to be done in build [20:48] sergiusens, alright, it's been rebased onto your branch and it's all finished [20:48] kyrofa, gonna check it out [20:48] sergiusens, ended up unpacking debs into an intermediate directory in pull and linking them in with build [20:49] kyrofa, but after I get back from aikido which I'm returning to after my 2 month hiatus [20:49] :-) [20:49] sergiusens, sounds great! Want me to make a PR into your branch in your fork? Might make reviewing easier [20:50] sergiusens, or we can push your branch to the official repo and I can make a PR there. Tests run that way [20:53] Let me know-- dinner time, I'll be on telegram [21:53] jdstrand: Are the SNAP_DATA directories mounted NOEXEC? [21:54] they shouldn't be [21:55] jdstrand: Okay, looking for a theory on why this snap isn't working. That's not it :-) [21:55] /dev/vda3 on /var/lib/snaps type ext4 (rw,relatime,data=ordered) [21:56] and there aren't separate mount points for SNAP_DATA for snaps (just verified) so that shouldn't be it [21:56] Ironically the Java library giving me trouble is called Snappy. [22:12] Where do bugs in snappy classic go? [22:18] (I mean, where should I file them) [22:19] * genii sips his coffee and ponders how snappy classic/new snappy reminds him of coke classic/new coke [22:21] Hopefully we don't get a diet snappy [22:22] snappy zero [22:22] you know, for the pi zero :) [22:22] Hehe