=== JanC is now known as Guest19389 === JanC_ is now known as JanC [00:21] slangasek: do you have any idea what is going on here? https://launchpad.net/~canonical-foundations/+snap/snappy-first-boot/+build/9495 [00:22] mwhudson: not offhand. Is the livecd-rootfs package in our ppa up-to-date? [00:22] (along with other packages there, generally) [00:22] slangasek: i just deleted all the packages in our ppa :) [00:22] well xenial ones anyway [00:23] so the only other 'manifest' ref I see in the log is: + cp assets/dpkg.list /build/snappy-first-boot/parts/livebuild/build/livecd.ubuntu-core.device.manifest [00:23] ah i think it's getting livecd-rootfs from the primary archive now [00:23] i guess i need to copy it over from ppa:snappy-dev/image [00:50] slangasek: oh wait [00:50] slangasek: so it's hard coding the snap name in lp in there? [00:51] is it? I don't know [00:53] yeah i think so [00:53] look at the line before the failing line [00:53] moving something to /build/snappy-first-boot/... [00:55] hello all [00:56] my raspi2 dont boot with ubuntu-core-16-pi2.img [00:56] only red led is on [00:56] any idea? [00:58] cmdline.txt: [00:58] dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty0 elevator=deadline [01:00] i think cmdline is wrong. can anyone help? [01:10] hello all my raspi2 dont boot with ubuntu-core-16-pi2.img only red led is on any idea? cmdline.txt: [01:10] dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty0 elevator=deadline i think cmdline is wrong. can anyone help? [01:11] yeah, that was it [01:11] overflyer: sorry, don't know, you could try emailing the devices list [01:58] PR snapcraft#893 opened: Add a script to retry autopktests [02:30] slangasek: is http://people.canonical.com/~vorlon/official-models/ still the best place to get model assertions from? === chihchun_afk is now known as chihchun [02:39] Possibly dumb question but is there a way put the core and a few snaps into an image that is easy to install on embedded devices. [02:50] Is there a way put the core and a few snaps into an image that is easy to install on many embedded devices? [03:02] hm my dragonboard image doesn't boot :( [03:21] has anyone successfully followed the blog at http://www.zygoon.pl/2016/06/making-your-first-contribution-to-snapd.html to build the snapd? I succeeded it once. now, I am having this error "can't load package: package snap.amd64: cannot find package "snap.amd64" in any of". the detailed info is at http://paste.ubuntu.com/23449276/ [03:23] I removed "snap.amd64" in my "devtools" dir, and I cannot get it back any more. I thought it was a compiled file from building the snapd. [03:40] ogra_: just to be sure, this what you meant by flashing? https://youtu.be/LDN7QQ1-2c0?t=1m22s [03:42] Didnt seem to work for me. I am using Beaglebone black industrial Rev C [05:58] Bug #1640386 opened: $SNAP_DATA and $HOME are not the same [06:25] nessita: three weeks ago I heard it's something that is being fixed in store (or store checker tools, not sure) trunk, but not yet deployed. and later I got that you are a good one to ask about store topics. [06:56] o/ [07:05] Bug #1619258 changed: netplan should allow NICs to be disconnected and not stall the boot [07:08] bonjello === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [08:09] hey hey [08:23] hey dholbach! [08:27] salut didrocks === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [10:41] zyga, ping [10:45] zyga, I followed your instructions at http://www.zygoon.pl/2016/06/making-your-first-contribution-to-snapd.html to build the snapd at https://github.com/zyga/snapd/tree/hello-iface. The very first time, the build was succeessful. However, i did not see the "reboot" interface. Then I removed the "snap.amd64" file in the "devtools" directory. After that, I get the error like http://paste.ubuntu.com/23450405/. How can I get the "snap.amd64" file back? thanks [10:51] nessita: the problem we have with that is anyway that ubuntu-app-platform (now in store) needs manual review for each upload, because of the warning about the "content:" field in the content interface definition, which is however required for the snap to function === hikiko is now known as hikiko|ln [12:14] Mirv,hey just tested the new package with unity8. Not running yet. Probably we need to export some env variables [12:15] Mirv, probably we need didrocks help [12:21] renato__: try tweaking the launcher and export MIR_CLIENT_PLATFORM_PATH=$SNAP/ubuntu-app-platform/usr/lib/$ARCH/mir/client-platform (if this is shipped by the new content snap) [12:21] this was the only thing to add Mir support [12:21] let me try [12:51] didrocks1, Mirv, http://paste.ubuntu.com/23450827/, do you know where I can find Mir logs? [12:53] I would say you don't access to the socket [12:53] but kgunn would be the one to ping about it === didrocks1 is now known as didrocks [13:05] hi. i'm getting (quite frequently) intermittent errors downloading the ubuntu-core snap while installing a local snap: http://pastebin.ubuntu.com/23450862/ [13:05] any ideas on what's wrong here? sometimes it does work, but mostly it doesn't [13:09] actually, it seems like the CDN is broken. i'm trying in canonistack, and that host name maps to these ips: http://pastebin.ubuntu.com/23450880/ [13:10] if i add an entry in /etc/hosts to map the host name to 95.172.71.38 it works [13:12] ev_: ^^^^ [13:25] renato__: right, ok so the QPA is now there at least [13:26] the new snap is not yet in the store because each upload needs manual review at the moment, but it seems you got it from LP, which is good [13:26] Mirv, yes. I am trying to understand what is causing the app to fail to launch on unity8. Are you test app working? [13:59] BjornT: thank you, I’ve passed that on [13:59] and pointed them here [14:27] renato__: I think we need to check with the U8 team indeed what are the expectations [14:28] renato__: are you testing Unity8 on zesty or xenial overlay? [14:28] I've that separate zesty machine I could try too [14:28] Mirv, xenial [14:29] Mirv, it was working with the old qt5/gtk-launcher. I am trying to find what is missing [14:30] BjornT ev we are seeing this in our testing too fwiw, thanks for looking into it [14:32] Do configure hooks need anything from snapcraft other than copying the hook/configure file and the optional YAML to expand the security permissions? [14:37] renato__: ah, ok, then it must be something relatively small (I hope) [14:37] I have a configure hook I expect to run on "snap set". It doesn't. """- Run configure hook for snapname (cannot snap-exec: cannot find hook "configure" in "snapname")""" [14:40] I peeked with strace. snapd lstat()s the configure hook file (ret 0), but then exits (val 1). [14:41] FWIW, is executable. 0755 [14:42] Mirv, yes, probably is one missing env var :D [15:03] guys how I can solve this: [15:03] - Download snap "ubuntu-core" (423) from channel "stable" (received an unexpected http response code (500) when trying to download https://068ed04f23.site.internapcdn.net/download-snap/b8X2psL1ryVrPt5WEmpYiqfr5emixTd7_423.snap?t=2016-11-10T14:59:42Z&h=f609260aa36b4327500712f9dfdeb8a059cb9b35) [15:03] I removed my snapd and re-installed it, and now I can not install any app [15:09] ok snap login did the trick [15:13] qengho: quite puzzled, it does work for me (on an ubuntu core machine) [15:13] qengho: did you try it there? it seems desktop ubuntu-core snapd doesn't have the same version, that could impact [15:13] PR snapcraft#894 opened: store: send snapcraft version in a header [15:16] didrocks: I have only tried on snapd-on-classic Z. [15:16] qengho: try in a vm, do you mind keeping me posted? [15:17] I definitively got the configure hook working here yesterday on it [15:18] guys, it seems /snap/bin is not in $PATH (environment: Zesty) even though there's a script that does that in profile.d, it seems like it's not used [15:18] known issue? or should I report a bug? [15:18] didrocks: grep "hook" /snap/${snapname}/meta/snap.yaml ? [15:18] faenil: what shell? [15:19] both unity7 and unity8 [15:19] Maybe, echo $SHELL ? [15:19] then snap run works in unity7, but not in unity (returns QXcbConnection error, it's not using Mir) [15:19] qengho: maybe? [15:19] not in unity8* [15:20] qengho: wdym? no, there is nothing to refer in snap.yaml [15:20] didrocks: Thanks. [15:20] qengho: dropping the file as meta/hooks/configure is enough [15:20] didrocks: I was wondering if your yaml had something else. Thanks. [15:20] no, just meta/hooks/configure, shebang (bash script), executable [15:21] qengho: that was a statement, not a question :D both under u7 and u8 PATH does not contain /snap/bin [15:21] didrocks if you need specific interfaces for your hook you need to define them in meta [15:21] (some bad english there, sorry) [15:21] sergiusens: right, but here, I guess qengho just want first to have his configure script running :) [15:21] like basic 1o1 [15:21] ah, well I might take on this tomorrow or this evening as kyle is out this week [15:22] let's see first if qengho reproduces his issue on ubuntu core [15:22] faenil: That profile.d part is the perview of ksh or bash or zsh or csh or tcsh or ipython ... I'm asking which shell you use. [15:22] let me try my snap on desktop 16.04 at the same time [15:23] qengho: ah you mean terminal shell..zsh on unity7, vty on u8 [15:23] sergiusens: qengho: doesn't work with snapd on 16.04 FYI (didn't try the version in -proposed yet) [15:23] unsure if the issue you have in Zesty is similar [15:23] as it's a newer snapd [15:24] qengho: vty, still zsh it is [15:25] faenil: Will you please check if zsh reads from /etc/profile under your circumstances? [15:25] qengho: I will have a look. it's not my laptop and I don't use zsh myself, but let's see [15:25] (it's the team laptop) [15:26] although http://askubuntu.com/a/476435 suggests /etc/profile won't work with zsh [15:28] also https://bugzilla.redhat.com/show_bug.cgi?id=88457 [15:29] faenil: that seems like a real bug. Pleasae advise in a bug report where snapd should also put its PATH alterationsfor ZSH users. [15:29] qengho: I have no idea, I'm not a zsh user :D someone in the team is, I'll ask around [15:29] .zshrc is a good bet, surely [15:29] faenil: you are until you run "chsh"? :D [15:30] zsh is not running on my laptop :D this is a shared laptop [15:30] but sure, I'll report a bug ;) [15:30] faenil: thank you. [15:30] qengho: should it be filed against snapd? [15:34] kgunn, hey, I am having problems to launch a snappy app on unity8:http://paste.ubuntu.com/23450827/, could you help me with that? === matteo` is now known as matteo [15:38] qengho: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1640514 [15:38] Bug #1640514: /snap/bin is not added to the PATH when using zsh [15:41] faenil: you should add the upstream "snappy" project for upstream to consider it [15:41] didrocks: done [15:43] thx! [15:44] Bug #1640514 opened: /snap/bin is not added to the PATH when using zsh [15:50] jdstrand: are you around? [15:53] roadmr: hi! I am [15:53] Bug #1640386 changed: $SNAP_DATA and $HOME are not the same [15:54] jdstrand: I'm testing r796 on staging, for the --plugs/--slots thing. I wanted your help figuring out an error... [15:54] roadmr: ok [15:55] jdstrand: but I figured it out myself :) looks like our click-review invocation fumbles the order of parameters: https://pastebin.canonical.com/170282/ [15:55] jdstrand: still I'd appreciate sanity-check on my theory [15:59] roadmr: yes. overrides must be last after the snap with how argparse is configured [15:59] jdstrand: ok, no problem, we can easily accommodate that in our code. Thanks :D [15:59] cool, np [16:01] renato__: and anyone else that had a problem with ubuntu-core snap (r423 from stable for amd64), the problem is resolved and downloads should be working again. Sorry for the inconvenience. [16:12] ogra_: have you read the bug report I linked? [16:12] (the one on redhat portaL) [16:12] bbl [16:25] PR snapcraft#888 closed: Always respect go-buildtags [16:35] ogra_: the zsh bug about "zsh does not source /etc/profile" was marked NOTABUG [16:35] so I don't think that's going to happen ;) [16:36] the feature was there, and was removed on purpose [16:36] so if you want to support running snaps from zsh, it seems changing zsh behaviour is not an option :/ [16:41] faenil, well, it points to other bugs that were closed with pointing to adding that change in ~/.zshrc [16:41] yes [16:41] (or rather to /etc/skel/.zshrc ) [16:42] did you check if our package ships that file and if it has these changes ? [16:42] if so, it is actually a matter of the user to update his config in the homedir accordingly [16:43] there is no way that is a snappy bug ... snappy uses the agreed shell standard of using /etc/profile.d ... [16:43] ogra_: sure, I agree with you [16:46] ogra_, faenil: We can easily patch the stock zsh profile in Ubuntu to make sure the proper path is included, I'd guess? [16:46] that was what i thought ... [16:46] but it would mean an ubuntu specific delta [16:47] (though perhaps we could get it into debian ... not sure if they'd accept that) [16:48] niemeyer: that would be ubuntu specif though :/ [16:48] specific* [16:49] faenil: Indeed, but it's not uncommon for tooling to have distribution-specific path handling [16:49] faenil: The alternative would be to upstream into the zsh source code itself [16:50] ogra_: we do not seem to ship .zshrc [16:50] faenil: Might be worth attempting to push this upstream [16:50] niemeyer: +1 [16:51] faenil: +1 as well.. who's going to work on that? :) [16:52] not sure, someone whose job task include working on snapd? :) or someone who has enough spare time to add that on top [16:55] faenil: We need help with that sort of thing, as we can't keep our eyes on every single software that might interact with snaps [16:56] The right file to tweak is /etc/zsh/zshenv [16:56] niemeyer: I know, I know..we're in the same company :P each busy on his own bits :D [16:57] sswell, whichever team maintains zsh should do it ... [16:57] :) [16:58] * ogra_ glances in foundations direction ... [16:58] haha :) [17:15] how can you access the user invoking a snappy binary, normal methods such as $SUDO_USER and whoami don't seem to work [17:21] SuperJonotron: You can't. And you can't do anything with it anyway. Don't "sudo". [18:39] how do I use docker with snap? [18:39] I did `snap install docker` [18:39] but, how do I start the daemon? [18:40] sudo service snap.docker.dockerd start [18:40] n0c_ ^ [18:41] thanks! where would I have learned about that? [18:41] the confined docker snap is still pretty new. lool - any hints for n0c_ on where they can follow along at home? [18:42] n0c_m lazyPower: https://lists.ubuntu.com/archives/snapcraft/2016-October/001382.html is the best compilation, the gdoc might not be fully up-to-date but I could fix any issues there [18:43] n0c_: this should soon work out of the box, but a bug prevents it right now [18:43] lool - does uapp explorer not have support for listing things like README's? I would think having a canonicalized wiki style place for this information would be better than a gdoc. [18:43] just my 2 cents though [18:43] lazyPower: yeah good point, link frmo description would be good [18:43] in terms of discoerability, a google doc is the equivalent of not having any information out there, as they dont get indexed by google. [18:44] tyhicks: I decided to take a look at bug #1592022 and think I found the solution. Can you review my comments in trello for sanity? (you should have an email now) [18:44] we ran into this ourselves when we were doing all of our annotation in gdocs, so we just moved to GH + MD and called it a day [18:44] Bug #1592022: 32 bit applications on 64 bit system fail due to seccomp [18:44] Sure, the point is I can update it to keep it up-to-date, it's not meant to be permanent, eventually it will go away [18:44] tyhicks: it seems completely trivial to fix [18:44] * lool => dinner & [18:44] thanks lool, :) <3 === chihchun is now known as chihchun_afk [18:49] PR snapcraft#876 closed: repo: allow for architecture-specific stage-packages [18:50] oh interesting-- that ^ snapcraft PR would've helped in my seccomp investigation === JanC_ is now known as JanC [18:52] popey: do you still have the wine snap around? [18:53] jdstrand there for next time I guess ;-) [18:53] :) [18:53] * jdstrand -> lunch [18:53] FYI, we are still troubleshooting an issue with downloads of ubuntu-core r423 (stable, amd64) [19:00] jdstrand: I have _a_ wine snap, yes. [19:00] jdstrand: the one I currently have is built with --enable-win64. [19:08] jdstrand: http://people.canonical.com/~alan/wine_1.6-git_amd64.snap snapcraft.yaml -> http://paste.ubuntu.com/23452189/ 'wine' launcher -> http://paste.ubuntu.com/23452191/ === thomi_ is now known as thomi [19:46] PR snapcraft#894 closed: store: send snapcraft version in a header [19:55] PR snapcraft#895 opened: Release changelog for 2.22 [20:13] popey: I don't know what --enable-win64 does. does that mean you can't run win32 on amd64 or does that enable 64bit in addition to 32bit? [20:13] I guess I can just build from the yaml [20:14] ah "The problem is that by itself, that build will only run applications compiled for 64-bit Windows" [20:30] jdstrand: yeah [20:51] Update: issue with downloads of ubuntu-core r423 (stable, amd64) has been resolved [21:31] Bug #1595813 changed: implement upower interface

[22:06] hey [22:06] snap create-user leaves a \r at the end of authorized_keys :) [22:54] could anyone help me with first time setup for ubuntu core? [23:19] sergiusens: hey, are there limitations to stage-packages? if I stage 'wine1.6' then it barfs. I have to edit _get() from repo.py to: [23:19] except SystemError: [23:19] logger.debug("ERROR: could not mark '%s' to install") [23:19] sergiusens: but it actually continues and marks it ok [23:29] sergiusens: actually, it didn't seem to mark it ok. I staged wine1.6, wine1.6-amd64 and wine1.6-i386:i386 and it didn't pull wine1.6 (it did pull the other two [23:57] popey: hey, can you build without --enable-win64? I can't get it to build here and can't get snapcraft to stage-packages what is in the archive so I'm stuck