[00:14] zyga, you can push https://bodhi.fedoraproject.org/updates/FEDORA-2016-4154def2ea and https://bodhi.fedoraproject.org/updates/FEDORA-2016-c6820c54b1 to stable now [02:03] how to run latest amd64-all-snap.img + LXD Containers ? [02:13] ans also how to get webdm working with latest amd64-all-snap.img ? i get some apparmor error [06:13] hi friends [06:14] what after : do in snapcraft file ? [06:15] artmello, this is the problem man same happening with me , [06:16] QStandardPaths::DataLocation point to container's location instead of user's /home/.local/share/myapp/data [06:21] am getting this error- expected string or bytes-like object [06:27] anyone on ?? [07:19] help [07:26] expected string or bytes-like object [07:26] what does this mean [07:27] bull: From what command? Your questions don't ask enough. [07:27] snapcraft [07:28] bull: Add "--debug" to the end of snapcraft command line. [07:29] my snapcraft file is here - http://paste.ubuntu.com/21494084/ [07:30] and the output of --debug is http://paste.ubuntu.com/21494119/ [07:30] its been 3 hours and more i cant make snap of this application here [07:32] hard journey with snapcraft so far, i cant make my app deskie work after snapping it . it wont work perfectly like it should idk how people gonna use this tool its harder then debian packaging damn [07:33] bull: There is a bug in snapcraft because it should have failed in a better way, but it should have failed because your YAML is bad. Its nor valid at all. [07:33] bull: Indentation matters. Sections matter. [07:33] qengho, whats wrong it should debug line no. etc man [07:34] bull: What does "application:" mean? [07:34] Did you make that up? [07:34] i used the same field in making snap for my previous application it works well [07:35] stage-packages takes a list, but the next line is indented the same amount -- not valid. [07:35] okay let me check [07:35] application is a part ?? [07:36] bull: Notice how "plugs" and "architectures" doesn't look like "stage-packages"? [07:36] bull: Okay, that is good. It needs a plugin, I am pretty sure. Use "plugin: nil", maybe. [07:37] okay but it should output these things instead of such a horrible output [07:37] okay wait let me check [07:39] bro we use tab to make space or spacebar ?? [07:39] bull: that's a bug. It's never seen YAML like this. Please, run "$ ubuntu-bug snapcraft", title "snapcraft crashes with useless message on bad YAML" and attach a link to your YAML. [07:39] bull: It's up to you. Be consistent. [07:40] okay [07:40] i will [07:42] i cant report bug [07:42] how to do that ?? [07:44] my current snapcraft file is this http://paste.ubuntu.com/21494890/ please report the bug [07:45] it still saying same after i fixed the indentions -- expected string or bytes-like object [07:48] its working now after removing architectures [07:52] snapcraft :- downloading icons whille snapping app make no sense or its useless -- Get:41 http://in.archive.ubuntu.com/ubuntu xenial/universe DEP-11 64x64 Icons [7,448 kB] [08:13] wow , am still not able to know what the hack is going on here with snapcraft !!! it still showing me same error at end of building process . [08:14] downloaded 28 mb of cache , 200mb + of packages and at last it fails haha with this line - expected string or bytes-like object [08:15] mhall119, you there ?? [08:50] bull: mhall119 is sleeping right now :) [08:50] tsimonq2, damn === JanC is now known as Guest71834 === JanC_ is now known as JanC [09:14] i reported bug https://bugs.launchpad.net/snapcraft/+bug/1608032 [09:14] Bug #1608032: snapcraft crashes with useless message on bad YAML === oparoz_ is now known as oparoz [12:54] tianon: sorry I missed you (yesterday was a half day for me), the general guidance is that if the snap needs things here and there from other interfaces to use those interfaces *iff* the snap legitimately needs that access. for example, if docker does bind to a port and listen to network connections, then use network-bind, otherwise, add it to your interface [12:58] tianon: also, don't worry about seccomp policy right this second-- I suggest using @unrestricted right now because the way seccomp works, you can't ever get more syscalls than the parent. Perhaps, maybe, you could get away with listing everything in snap-confine.git/debian/README.syscalls and leave out, say, init_module (and others that are kernel module related), keyctl and a few others that are listed as dangerous in the interfaces/seccomp/default [12:59] tianon: point is, docker, like lxd, is quite special in that it can be thought of in some ways as an alternate launcher and it needs a lot of privileges to launch its app containers [13:00] tianon: we can discuss this all next week. I'm happy to answer any questions and provide guidance/tips/etc [16:04] PR snapcraft#698 closed: Add option disable-parallel for autotools plugin [16:25] If I'm just changing security settings in my snapcraft.yaml file, do I just need to run 'snapcraft snap' to test the changes? I'd rather not rebuild the whole thing everytime [16:29] tgm4883, you mean changing the plugs/slots stuff? Indeed, no need to rebuild [16:30] kyrofa: exactly. Right now this app only (semi-)works in --devmode [16:30] tgm4883, anything not in parts you can modify freely and just run `snapcraft` again to get it in a snap. Snapcaft will regenerate the prime/meta directory each time [16:31] oh that is nice [16:31] tgm4883, so apps, snap name, version etc [16:31] that will make adding apps much easier [16:31] Indeed [16:31] speaking of version, can that have a variable in it? Like $DATE [16:31] tgm4883, are you aware of the `snap try` functionality? [16:31] no, what's snap try? [16:31] tgm4883, no, but you're not the first to ask. We'll add something like that soon [16:32] sweet [16:32] Okay, snap try. Hold on I need to move then I'll explain [16:40] Okay, I'm back [16:41] tgm4883, assuming you're running snapcraft on a 16.04 machine, you can just run `snap try prime/` after running `snapcraft prime` [16:41] ok, running a build now, should be done in a few minutes [16:41] tgm4883, that will bind-mount the prime directory and pretend it's a snap installed on the system [16:41] what does that do for security confinement? [16:41] tgm4883, which means you can run all the apps from it and everything, except it's not a squashfs image-- if you change the prime directory, you change the snap [16:42] tgm4883, still works the same way. You can `snap try --devmode` too [16:42] ah cool [16:42] tgm4883, it makes for faster iteration [16:43] yea that will help [16:43] tgm4883, but a word of warning. There's a bug where, if you run `snapcraft clean` or otherwise remove the prime directory, snapd gets confused [16:43] tgm4883, it's been fixed in master, but not released yet [16:43] tgm4883, so if you're going to clean the prime directory, `snap remove` the snap first [16:43] also if I stop running "snapcraft clean" and rebuilding the whole thing :) [16:43] apparently I like to watch it do a git clone of the repo [16:44] tgm4883, you know you can clean individual parts and individual steps of parts, right? [16:44] yea [16:45] I need to look at that part of the documentation again [16:47] Are old versions of snaps ever removed? [16:47] tgm4883, right now, no. But the next version of snapd will prune them [16:47] there are always only two versions kept around [16:47] I doubt they are causing problems, but it's starting to get annoying when I do a 'df -h' and see 20 versions of the same snap mounted [16:48] tgm4883, I think it'll remove once there are three [16:48] hmm [16:48] (unless you sideloaded ... then it is up to you to do tthe clean up) [16:48] tgm4883, agreed [16:48] ah [16:48] Hey ogra_! [16:48] hi [16:48] sideloaded then via snap install [16:48] yeah, that will pile up forever [16:48] you need to run snap remove every once in a while [16:48] tgm4883, indeed, sideloaded = snap install versus snap install [16:49] Is there a limit to the number of snaps you can install? I noticed it started over on the /dev/loop# when it got to 20 [16:49] or maybe that is a coincidence [16:50] I did remove the hello and hello-debug snaps around that time [16:51] well, i guess there is a limit ... i doubt the kernel can handle more than /dev/loop64435 [16:51] err [16:51] 65535 [16:51] that makes sense [16:52] but if you have 65k snap packages installled then i want your HDD too ! [16:52] that would likely be plenty petabytes :) [16:52] cool, going to work on security stuff, then only like 9-10 more things to add/fix before this app is good [16:55] YAY ! [16:55] https://code.launchpad.net/~snappy-dev/+snap/ubuntu-core [16:55] first cronned build ... [16:56] ogra_, awesome! [16:57] now only autoulpoad is missing ... waiting for a store fix for that one [16:57] ogra_, can't auto-upload to a shared snap? [16:57] I've run into that as well [16:57] yeah [16:58] ogra_, is that a store issue or an LP issue? [16:58] i think a store issue ... store people are researching since wed. [16:58] ogra_, have you tried uploading via snapcraft push yourself? [16:59] bug 1607389 [16:59] Bug #1607389: shared snap packages can not be uploaded from LP builds [16:59] kyrofa, nah, only manually through the web ui [17:09] After I create my snap I'm still getting '...log.dir can't be created read only file system' after I've declared the logs as $SNAP_USER_DATA. Any suggestions? [17:10] I did notice the log files are being made in a different directory (user/snap/..) but I'm unsure how to change that [17:11] Cavan, you notice the log files being created in $HOME/snap/... but you're still getting a "read-only" error? [17:13] The snap is being created in /snap/zeppelin/current and the logs are being created in /home/cavan/snap/zeppelin/x33. But if thats the way they're meant to be then yes [17:13] yes, that is the location of $SNAP_USER_DATA [17:14] i.e. /home/$USER/snap/$PACKAGENAME/$VERSION [17:17] Yeah, the file which writes the files needed 'zeppelin-daemon.sh' is returning this everytime I try to run it /snap/zeppelin/x33/bin/zeppelin-daemon.sh: line 180: /snap/zeppelin/x33/zeppelin-cavan-cavan-HP-ENVY-15-Notebook-PC.out: Read-only file system' Is there a way to point it to the $SNAP_USER_DATA to read or a way to create in the main directory? [17:38] heh... snaps are quite big aren't they... [17:39] i'm still trying to figure out if it is even possible for a daemon to play audio [17:39] the funny thing is that the deb package of gmediarender has the same problem... it ships with an init script which doesn't work but if you just run it at a command prompt it works fine [17:55] Cavan, that depends on if the application you're snapping supports that as some sort of config options or cli parameter [18:10] ali1234, daemons aren't session-specific, but I suspect audio is [18:11] (don't know for sure) [18:37] Sheesh sergiusens, take a day off man [18:40] :-) [18:49] may be a simple reason for this, but any help appreciated. see: http://paste.ubuntu.com/21546329/ [19:14] kyrofa: yes, that's the problem [19:16] ali1234, what if you made it an app and configured it to run at startup, similar to how something like skype or the owncloud client fires up? Neither of those are snaps, but I assume it just uses the .desktop files [19:16] Not startup sorry-- login [19:16] kyrofa: it won't work because nobody ever logs in to this system [19:16] ali1234, oh interesting. But you want to play audio? [19:16] yes [19:16] with uPNP [19:17] How would you do that without snaps? [19:17] i don't know [19:18] i would probably rip out all the session permissions management [19:18] or run everything as root [19:18] or something horrible like that [19:19] the point is the system won't even have a monitor [19:19] it will look like a piece of stereo equipment [19:20] another use case would be something like amazon echo or mycroft [19:22] actually doesn't mycroft run on ubuntu? [19:24] https://insights.ubuntu.com/2015/08/14/meet-mycroft-open-source-artificial-intelligence-powered-by-snappy/ [19:24] how does that play audio? [19:27] https://github.com/MycroftAI/snapcraft-mycroft-core/blob/master/snapcraft.yaml [19:27] no daemons defined [19:28] so... i think there should be a proper way to do this [19:29] i should be able to grab the nase image, install my snap, and have it just work... without having to create users and configure auto login [20:04] zyga, did you finally submit the updates to stable? [20:05] and have you done any work to address the fedora-review feedback? [20:05] for snap-confine [21:02] PR snapd#1556 closed: asserts: add Assertion.Prerequisites and SigningKey, Ref and FindTrusted