[00:14] cprov is this hooked up already? https://bugs.launchpad.net/snapcraft/+bug/1619819 https://bugs.launchpad.net/software-center-agent/+bug/1619818 [00:14] Bug #1619819: It is possible to release a devel snap to candidate and stable [00:14] Bug #1619818: Error when trying to push and release a snap with devel grade === JanC_ is now known as JanC [00:16] sergiusens: grade is fully supported by current SCA & CRT [00:16] sergiusens: I have to check 19 [00:18] sergiusens: right, 18 is something else as elopio pointed in the last comment [00:20] sergiusens: just checked the code, the release endpoint needs update to restrict channels according to grade :-/ [00:23] cprov: yes, I updated 18. Sorry about that. [00:25] elopio: no problem, thanks for playing with it and discovering 19. Michael Nelson (our man in the future) will tackle this his early Monday and we will release the fix on SCA until Monday EOD [00:25] it will probably require some publishing cleanup [00:28] Autralians are amazing [01:03] cprov elopio no rush, this won't make it to -updates until late Monday/early Tuesday [09:21] anyone interested in a code review for snap-confine? [09:26] hello guys. how to use in cmake config flags variable $SNAP_VERSION? [09:28] zyga: ? [09:32] zyga, what do you need reviewed? [10:06] Son_Goku: hey, I need some help on this one https://github.com/snapcore/snap-confine/pull/123 [10:06] PR snap-confine#123: Add mountinfo module [10:06] Son_Goku: sosrry for the lag, I was busy writing and dind't notice I didn't paste URL initially [10:07] eldarkg: I don't know about that, what are you trying to achieve? [10:08] zyga: I want to compile app with set to him $SNAP_VERSION value [10:08] eldarkg: for informative purpose? [10:10] zyga: https://bugs.launchpad.net/snapcraft/+bug/1619877 [10:10] Bug #1619877: $SNAP_VERSION is empty when I set cmake vars [10:12] eldarkg: $SNAP_VERSION is set at runtime [10:13] zyga: can I to define user variables in a snapcraft file? [10:16] eldarkg: the plan is to allow that, it relies on a set of bits to be in place, I don't remember if this is all available from snapcraft all the way to snap-confine [10:16] eldarkg: I think it might have gone live this week [10:16] * zyga was busy under the hood [10:16] zyga: ok. thank you [10:17] eldarkg: but $SNAP_VERSION is set by snappy automatically [10:17] eldarkg: based on the version field from snapcraft.yaml [10:17] zyga: ok [10:18] zyga, I don't see anything nuts about your PR [10:22] Son_Goku: thanks [10:53] Bug #1619888 opened: Snap should be able to run chown [11:39] PR snapd#1842 opened: asserts: don't have Add/Check panic in the face of unsupported no-authority assertions [12:02] PR snapd#1843 opened: snap: switch to the new agreed regexp for snap names [12:37] PR snapd#1842 closed: asserts: don't have Add/Check panic in the face of unsupported no-authority assertions [12:56] zyga: how to do that snap app can to list FS tree? [12:59] eldarkg: hmm, that depends on what you mean [12:59] zyga: https://github.com/eldarkg/kicad-snap/issues/7 [13:00] eldarkg: use the home interface for this snap, when connected it will grant access to most of the users home directory [13:00] zyga: home interface used [13:02] zyga: app is using files that contributed from snap tree ($SNAP/usr/share/kicad) [13:11] eldarkg: I don't think I know what the problem is [13:12] zyga: how resolve this? [13:27] eldarkg: the home interface gives access to /home/$LOGNAME [13:27] eldarkg: the $HOME variable is redirected so that might fool some applications (it points to snap-private home) [13:28] eldarkg: I don't know what you mean when you talk about $SNAP/usr/share/kicad [13:28] eldarkg: is this one or separate multiple issues? [13:29] zyga: I want to take access to $SNAP file system to read and to list content [13:31] eldarkg: can you be more specific? which location do you want to access [13:32] zyga: content like footprints, 3d models, libraries of components, demos [13:32] zyga: to $SNAP/usr/share [13:34] eldarkg: that directory is available by defautl [13:36] zyga: https://github.com/eldarkg/kicad-snap/issues/8 [13:37] eldarkg: can you add some kind of information to the bug report? [13:38] eldarkg: I don't understand how you determine that something is denied [13:38] eldarkg: do you get an apparmor denial? [13:38] eldarkg: the $SNAP directory is typically /snap/$SNAP_NAME/$SNAP_REVISION [13:38] eldarkg: so the data you are after is in /snap/kicad-dev-snap/$SNAP_REVISION/usr/share [13:39] zyga: isn't accessible from gui? see previous issue link [13:39] eldarkg: the gui is a part of the application, [13:40] eldarkg: snappy has no influence over that [13:41] PR snapd#1820 closed: many: start services only after the snap is fully ready (link-snap was run) [13:42] zyga: How I can to do that app works correctly? [13:42] eldarkg: I don't know much about kicad, perhaps you can work with kicad developers on this [13:43] zyga: ok. Maybe I can to list files from '/' (root)? [13:46] eldarkg: yes, you should be [13:48] zyga: why next? snapd-hacker-toolbelt sh; ls / . Message: ls: can't open '/': Permission denied [13:48] eldarkg: hmm, interesting [13:49] eldarkg: that may be the cause of some of the things you saw [13:49] eldarkg: does kicad snap work better in devmode? [13:49] zyga: sorry snapd-hacker-toolbelt.busybox sh [13:50] zyga: I don't check this in devmode. [13:51] zyga: wait. I am trying [13:55] zyga: Yes kicad in --devmode works fine but it isn't what I want. I want that snap app works in strict confine [13:58] eldarkg: in devmode, it should permit but log your apps missteps in syslog in /var/log/ . [14:00] eldarkg: Though, working in devmode and not in strict sounds like it is probably some syscall that is not allowed, unless you have another kicad installed from another package like deb. [14:01] qengho: Sep 3 17:00:13 EP43-DS3L kernel: [30646.624140] audit: type=1400 audit(1472911213.426:1200): apparmor="DENIED" operation="open" profile="snap.snapd-hacker-toolbelt.busybox" name="/" pid=31164 comm="busybox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [14:02] qengho: snap app in strict mode doesn't accesible to '/' (root) [14:03] qengho: only in $SNAP [14:04] zyga: I go away to ~1 hour. If you found some info ping me [14:04] eldarkg: with devmode, it should (?!) still warn. What else does it warn about? [14:05] qengho: see my previous msg to you. I use $ snapd-hacker-toolbelt.busybox sh; $ ls / [14:07] eldarkg: Yeah. But that is not your app. I want to make sure you're asking for what you really want, and not what you think is a path to the answer. [14:08] Tell us you want your car tire changed. Don't ask where we keep the screwdrivers. [14:11] qengho: see https://github.com/eldarkg/kicad-snap/issues/7. I go away [14:16] eldarkg: I'm debugging a few things in snapd [14:16] eldarkg: but not related to this [15:11] PR snapd#1844 opened: tests: adjust test setup after ubuntu user removal [15:39] PR snapd#1844 closed: tests: adjust test setup after ubuntu user removal [15:41] qengho: Do you see? [15:49] Bug #1619928 opened: snap app: access denied: list a FS tree [17:24] PR snapd#1843 closed: snap: switch to the new agreed regexp for snap names === chihchunl is now known as chihchun === StoneTable is now known as aisrael