[01:19] <mup> PR snapd#3964 opened: many: implement our own ANSI-escape-using progress indicator <Created by chipaca> <https://github.com/snapcore/snapd/pull/3964>
[07:15] <zyga-ubuntu> o/
[08:08] <mup> Bug #1717900 opened: Confined snap fail for user with homedir in /var/lib <Snappy:Triaged> <snapd (Ubuntu):New> <https://launchpad.net/bugs/1717900>
[12:12] <mup> PR snapd#3965 opened: interfaces/mount: add support for parsing x-snapd-{mode,user,group}= <Created by zyga> <https://github.com/snapcore/snapd/pull/3965>
[13:39] <kalikiana> \o
[13:52] <kyrofa> Hey ogra_, think you might have any free time today to sit down with Chris to talk about gadget snaps?
[13:53] <ogra_> sure
[13:53] <ogra_> kyrofa, any time you like
[13:53] <kyrofa> ogra_, wonderful, thank you, I'll ping you :)
[14:15] <kyrofa> lool, you around?
[14:16] <kyrofa> lool, question about your dnsmasq snap
[14:19] <zyga-ubuntu> hey kyrofa
[14:19] <zyga-ubuntu> how's the event?
[14:19] <kyrofa> zyga-ubuntu, going quite well. Nice to just sit down with these folks and get their stuff working
[14:21] <zyga-ubuntu> kyrofa: what are you working on there?
[14:22] <apol> https://pastebin.com/neAd9iPU
[14:26]  * zyga-ubuntu wonders why removing unused code makes tests fail
[14:26] <zyga-ubuntu> it must have been _slightly_ used :/
[14:28] <zyga-ubuntu> ah wait, master is broken!?
[14:28] <zyga-ubuntu> or artful is broken
[14:29] <Son_Goku> everything is broken, zyga-ubuntu
[14:35] <kyrofa> zyga-ubuntu, got a few roboticists here working on snapcraft updates and snapping their stuff
[14:37] <zyga-ubuntu> kyrofa: sounds great, tweet a few pics, that stuff is very interesting to people
[14:42] <mup> PR snapd#3966 opened: cmd/snap-seccomp,osutil: make user/group lookup functions public <Created by zyga> <https://github.com/snapcore/snapd/pull/3966>
[14:53] <morphis> davidcalle: is there any target date when docs.ubuntu.com will be refreshed?
[14:57] <davidcalle> morphis: afaict, there is a deployment outage since sep 21st, I'm running one now, will ping you when I know more
[15:09] <morphis> davidcalle: ok, thanks
[15:11] <__chip__> zyga-ubuntu: how's things?
[15:11] <zyga-ubuntu> __chip__: hey
[15:11] <zyga-ubuntu> __chip__: climbing out of the rm -rf hole but making progress
[15:12] <__chip__> zyga-ubuntu: sergiusens could use some pointers, i hear
[15:13] <zyga-ubuntu> __chip__: about?
[15:13] <__chip__> zyga-ubuntu: climbing out of the rm -rf hole
[15:13] <__chip__> zyga-ubuntu: although in his case i think it's a "do git clone in the wrong place" hole
[15:13] <__chip__> or git reset?
[15:14] <__chip__> i dunno
[15:14] <__chip__> it sounded nasty so i didn't listen, just in case he wanted me to fix it
[15:16] <cratliff> @ogra_   Hey,  would you be available to look at making a gadget snap with me?
[15:16] <nothal> cratliff: No such command!
[15:16] <zyga-ubuntu> __chip__: I killed my data last week
[15:16] <cratliff> ogra_
[15:23] <ogra_> cratliff, sure, where are you ?
[15:23] <cratliff> ogra_  I'm in the snapcraft room on the conference floor, but it is a little full in here if me coming to you works.
[15:24] <ogra_> ah, i'll come down in 20-0min then (need to finish a test )
[15:24] <ogra_> *20-30
[15:24] <ogra_> and i wanted to see the snapcraft room anyway
[15:24] <cratliff> ogra_ thanks, cya then.
[15:25] <nacc> sergiusens: i found another case of plugins on classic not dtrt -- the python pluginn invokes /usr/bin/env in the rewrite: https://github.com/snapcore/snapcraft/blob/master/snapcraft/plugins/python.py#L370
[15:25] <ogra_> (if it is to full we can go to the ballroom or some such ... )
[15:25] <nacc> sergiusens: the whole code needs to be audited for that, IMO
[15:25] <nacc> *if* one tries to modify LD_LIBRARY_PATH and that wrapper gets invoked, you get segfaults when mismatchinng host and classic snap distribution :)
[15:26] <nacc> and no built-in way to avoid it
[15:31] <nacc> for a classic app, does snapd setup LD_LIBRARY_PATH for the app? To refer to the core snap? Can I assume that in my own environment (so I can say prepend my snap's library paths)?
[15:32] <ogra_> bschaefer, i cant get the card to misbehave :/ so i guess i'll need the one where you are actually seeing the breakage ... were you using it on pi2 or pi3 ?
[15:32] <bschaefer> ogra_, raspi3
[15:32] <ogra_> yeah, thats what i'm trying it on
[15:33] <bschaefer> yeah i got the things installed i need so you can get this one if you want, ive not had the issue
[15:33] <bschaefer> since ive manually mounted the overlay.tar
[15:33] <bschaefer> or ... w/e it was
[15:33] <bschaefer> but yeah umm you can take this one as well and i can use that one
[15:33] <bschaefer> ogra_, what room are you in?
[15:34] <ogra_> bschaefer, at the end of the same corridor you are
[16:06] <mup> PR snapd#3967 opened: release: release snapd 2.28 <Created by mvo5> <https://github.com/snapcore/snapd/pull/3967>
[16:07] <jamesh> nacc: IIRC, snapcraft will set flags to try and link using -rpath to point at the core snap
[16:08] <jamesh> rather than setting LD_LIBRARY_PATH for you
[16:08] <jamesh> depending on your app's build system, that might not take effect though
[16:09] <ogra_> cratliff, sorry, will still take a bit up here ... i'm in 1419 though in case you want to come upstairs
[16:14] <nacc> jamesh: ok, so in theory, do I need to specify LD_LIBRARY_PATH for *classic* snaps to force my app to use only my snap's libs and the core snap's libs?
[16:14] <cratliff> ogra_, no problem.  Does after lunch work well?
[16:17] <nacc> jamesh: specifically, since a 16.04-built classic snap with a 16 core could run on artful, it's *really* important not to use libs from the host.
[16:17] <jamesh> nacc: if your project's build system respects the LDFLAGS environment variable,  it should end up with an rpath that will search common paths in both itself and the core snap
[16:18] <nacc> jamesh: ok, let me try that
[16:18] <jdstrand> kyrofa: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1598309/comments/5
[16:18] <mup> Bug #1598309: The aplay command doesn't work <snapd-interface> <xenial> <snapd (Ubuntu):Fix Released by jdstrand> <https://launchpad.net/bugs/1598309>
[16:21] <jamesh> nacc: try running "objdump -x /path/to/my/exe | grep RPATH"
[16:22] <nacc> jamesh: i have had to do stuff in my own wrappers so far, because I will get thinngs like man in my snap not finding the custom-built /usr/lib/man-db in my snap
[16:22] <nacc> jamesh: will do
[16:22] <jamesh> nacc: that should show up paths that will be searched before the default library locations
[16:22] <jamesh> if it doesn't show anything, then you might need to alter your project build system to make use of LDFLAGS
[16:22] <nacc> jamesh: are you sure what you describe is true for classic snaps?
[16:23] <ogra_> cratliff, sure
[16:23] <ogra_> popey, moop moop
[16:23] <jamesh> nacc: yes.  You can see the logic in Snapcraft's build_env() function at /usr/lib/python3/dist-packages/snapcraft/internal/project_loader/_env.py
[16:24] <ogra_> popey, oh ... unmoop ...
[16:24] <popey> wat wat
[16:25] <nacc> jamesh: ok, man for instance is installed via stage-packages
[16:26] <nacc> in any case, i'll try it
[16:27] <nacc> jamesh: i'm really curious if this is tested with builds on xenial run on artful?
[16:28] <jamesh> nacc: if the executable isn't being built under control of snapcraft (as would be the case if you're pulling executables from the Ubuntu archive), then you wouldn't see the rpath
[16:28] <jamesh> nacc: it would be up to you to handle it
[16:29] <jamesh> either by trying to patch in an rpath, or use a wrapper shell script that configures LD_LIBRARY_PATH instead
[16:30] <jamesh> patchelf can add an rpath to an existing binary, but sometimes fails
[16:30] <nacc> jamesh: ok, so there are two cases, got it
[16:31] <jamesh> (it isn't always possible to modify an already linked executable)
[16:44] <nacc> well, fwiw, (jamesh is gone), the python3 generated in the classic snap by using the pythonn plugin also does nont have any RPATH set
[16:51] <nacc> core snap's ldd references a host path
[16:51] <nacc> (/bin/sh)
[16:52] <nacc> err, /bin/bash
[16:56] <davidcalle> morphis: it will be deployed at some point in the next hours (https://docs.staging.ubuntu.com/core/en/stacks/network/index) , IS is looking into it.
[17:23]  * nacc is super-confused, the bash in the core snap also has no rpath
[17:24] <nacc> so was jamesh wrong earlier?
[17:24] <nacc> and if i try to run binaries from the core snap restricting LD_LIBRARY_PATH i get segfaults (Probably implies I'm being too strict)
[17:25] <ogra_> nacc, snaps do a pivot_root when running ... how do you check ?
[17:26] <ogra_> nacc, http://paste.ubuntu.com/25621829/
[17:26] <nacc> ogra_: classic snaps too?
[17:26] <ogra_> nacc, thats a zyga-ubuntu question
[17:26] <nacc> ogra_: ok
[17:26] <nacc> zyga-ubuntu: --^ :)
[17:26] <nacc> i assume they *don't* otherwise they couldn't use the host at all
[17:27] <nacc> but if they don't, none of the core snap makes much sense
[17:27] <nacc> debugging all of this has really not been fun, and makes me thinks classic snaps on artful may just be sort of broken (even if they happen to work some of the time)
[17:28] <nacc> ogra_: your paste makes total sense on core and with confined snaps (to me)
[17:29] <ogra_> they could use the host if they pivot and then bind-mount half the host ;)
[17:29] <nacc> i hope that isn't how it's done :)
[17:29] <nacc> but it might be, true
[17:29] <nacc> and i guess snapd has privilege to do that before running the app
[17:30] <nacc> ogra_: but i still don't see any actual use of rpath in the core snap's binaries
[17:30] <ogra_> (which they do via /var/lib/snapd/hostfs/ i think)
[17:30] <ogra_> well, the core snap is built from debs ... iirc rpath isnt allowed in debs
[17:30] <nacc> ogra_: ok, so maybe there is snapd voodoo for that on classic, for core snap binaries
[17:31] <nacc> the problem is, I have almost no way of knowing if that is true :)
[17:31] <ogra_> https://wiki.debian.org/RpathIssue
[17:31] <ogra_> "While there's no policy dictating the accepted use of RPATH, it's been a general consensus that RPATH use is discouraged, given the interactions between the above reasons and Debian's way of dealing with libraries and package dependencies. "
[17:53] <pstolowski> jdstrand, hey, what conf room are you in?
[17:53] <zyga-ubuntu> pstolowski: hey
[17:53] <zyga-ubuntu> pstolowski: how's the event?
[17:53] <pstolowski> zyga-ubuntu, it's good!
[17:58] <ogra_> mvo, https://github.com/snapcore/snapd/pull/2105
[17:58] <mup> PR #2105: snapstate: only import defaults from gadget on install <Created by niemeyer> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/2105>
[17:59] <ogra_> mvo, https://github.com/CanonicalLtd/ubuntu-image/pull/72
[17:59] <mup> PR CanonicalLtd/ubuntu-image#72: Make sure <unpack>/image/etc gets into the system-data directory <Created by warsaw> <Merged by warsaw> <https://github.com/CanonicalLtd/ubuntu-image/pull/72>
[18:08] <nacc> is it possible that while building a snap, one part (e.g., mine that builds xz-utils) gets staged/built, and then a subsequent part that depends on it (dpkg), sees the xz binary in stage, but rpath hasn't been modified on it yet, so it, at runtime, tries to load core libs, instead of libs from my snap?
[18:08] <kyrofa> nacc, rpath hasn't been modified one... what? xz?
[18:09] <kyrofa> s/one/on/
[18:09] <nacc> kyrofa: yeah, on the staged xz
[18:09] <nacc> i'm wondering about the order here
[18:09] <nacc> http://paste.ubuntu.com/25622009/
[18:09] <nacc> is the error dpkg's autopoint is spitting out
[18:09] <kyrofa> nacc, the first bit makes total sense: if part A builds "after" part B, part B will be staged before A is built
[18:09] <nacc> which feels like a mismatch between the just built xz and the libs being loaded
[18:10] <kyrofa> Ah, this sounds like an LD_LIBRARY_PATH ordering issue
[18:10]  * __chip__ might be having too much fun right now
[18:10] <mup> PR snapd#3968 opened: daemon: use client.Snap instead of map[string]interface{} for snaps <Created by chipaca> <https://github.com/snapcore/snapd/pull/3968>
[18:10] <nacc> kyrofa: maybe? i'm not setting it at all
[18:11] <nacc> kyrofa: this is during the build
[18:11] <kyrofa> nacc, yeah but snapcraft does. Checking...
[18:11] <nacc> kyrofa: yeah :)
[18:11] <kyrofa> nacc, this is a classic snap, I assume?
[18:11] <nacc> kyrofa: so i can confirm the core snap's liblzma is XZ_5.0 while my built one is XZ_5.2
[18:11] <nacc> kyrofa: yep
[18:16] <davidcalle> morphis: It's live
[18:17] <nacc> kyrofa: would i need to write my own plugin in the short-term?
[18:18] <kyrofa> nacc, I suspect something odd is happening in snapcraft itself, particularly in snapcraft/internal/project_loader/_env.py
[18:18] <kyrofa> Could the LDFLAGS be going wrong there?
[18:19] <nacc> kyrofa: it could be (although i don't know how to debug that) -- but also, how is it finding my just built xz? I don't see PATH manipulation there
[18:21] <kyrofa> nacc, look at runtime_env there
[18:23] <nacc> kyrofa: but that's for runninng binaries, not building them?
[18:23] <nacc> or is the xz now a runtime
[18:23] <nacc> kyrofa: bbiab
[18:24] <kyrofa> nacc, yeah the name is perhaps a bit misleading: it still gets evaluated for the build env
[18:24] <kyrofa> sgclark, SNAPCRAFT_CONTAINER_BUILDS=1 snapcraft
[18:25] <sgclark> thanks!
[18:30] <ogra_> pstolowski, https://docs.ubuntu.com/core/en/reference/interfaces/index
[18:33] <kyrofa> Hey ogra_ any idea why we're using /etc/profile to add /snap/bin to the path? Is there no way to do it without a login shell?
[18:44] <__chip__> kyrofa: hey, what's that about /etc/profile and login shells?
[18:45] <ogra_> kyrofa, the only other way is /etc/environment and that can only be changed for new installs ...
[18:46] <__chip__> well, there is environment.d
[18:46] <ogra_> kyrofa, we could surely talk to foundations (hey slangasek ) about adding /snap/bin to /etc/environment in new artful installs by default as we do since a while on ubuntu core images
[18:47] <ogra_> __chip__, is that finally landed ?
[18:47] <kyrofa> ogra_, yeah it's odd to have different behavior depending on how you're logging in, e.g. we have someone here trying to package mosh
[18:47] <ogra_> (i only know thats a lennart plan but havent heard anyone implemented it yet in a stable distro)
[18:48] <ogra_> kyrofa, if you're logging in it should always work
[18:48] <__chip__> ogra_: I don't think we've got it yet, no, definitely not in x
[18:48] <kyrofa> ogra_, over ssh
[18:48] <kyrofa> mosh doesn't run a login shell, so you have to give it an absolute path to the mosh server
[18:48] <__chip__> kyrofa: fun fact: fedora (and rhel?) load profile.d from non-login shells as well
[18:48] <ogra_> kyrofa, if you're logging in it should always work (and surely does with ssh ... ) if you do *not* log in ssh will strip your path
[18:49] <ogra_> kyrofa, but thats an ssh thing ...
[18:49] <ogra_> kyrofa, anyway ... what needs to happen to have it globally is to add it to /etc/environment ... and by poloicy we do not touch it on installed systems
[18:50] <__chip__> kyrofa: why doesn't mosh run a login shell?
[18:50] <ogra_> *policy
[18:51] <ogra_> kyrofa, the issue is that when using snapd on other distros we can not control /etc/environment (unless they have environment.d support as __chip__ pointed out) ... so there profile.d is the only way
[18:52] <kyrofa> ogra_, this is what needs to work in order for e.g. mosh to work: https://pastebin.ubuntu.com/25622245/
[18:52] <kyrofa> __chip__, no clue
[18:52] <kyrofa> __chip__, https://github.com/mobile-shell/mosh/issues/182
[18:53] <kyrofa> __chip__, not a mosh user myself
[18:53] <kyrofa> More of an SSH+screen guy
[18:58] <jdstrand> pstolowski: 1413
[19:01] <pstolowski> jdstrand, k, will be there in a few minutes
[19:03] <ogra_> kyrofa, well, the only way currently is to make mosh use 'ssh sh -l -c "<command>"' instead of 'ssh "<command>"'  ... there is also elopio's bug 1659719 that explains it
[19:03] <mup> Bug #1659719: ssh can't call a binary from a snap without the full path <isv> <Snappy:Fix Committed by ogra> <livecd-rootfs (Ubuntu):Fix Committed by ogra> <https://launchpad.net/bugs/1659719>
[19:07] <kyrofa> ogra_, how is that fix-committed for snappy?
[19:08] <kyrofa> Or is that just ubuntu core, and it should also apply to snapd?
[19:50] <mup> PR snapcraft#1570 closed: Don't fail over empty or faulty lines <Created by aleixpol> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1570>
[19:50] <mup> PR snapcraft#1571 closed: Make sure we don't try to include an empty set <bug> <Created by aleixpol> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1571>
[19:50] <kyrofa> jdstrand, your alsa workaround got us further, but now we're getting a denial on /dev/snd/controlC0. snappy-debug suggests the alsa plug, but we're already using it
[20:08] <__chip__> niemeyer: https://forum.snapcraft.io/t/2268 <- let me know if that seems reasonable, you
[20:15] <mup> PR snapd#3969 opened: hooks: rename refresh hook to post-refresh <Created by stolowski> <https://github.com/snapcore/snapd/pull/3969>
[20:25] <pstolowski> mvo, ^
[20:25] <mvo> pstolowski: hm? could you please paste it again?
[20:26] <pstolowski> mvo, sorry, sure - https://github.com/snapcore/snapd/pull/3969
[20:26] <mup> PR #3969: hooks: rename refresh hook to post-refresh <Created by stolowski> <https://github.com/snapcore/snapd/pull/3969>
[20:26] <mvo> pstolowski: ta
[20:26] <pstolowski> i hope the branch name is accurate ;P
[20:27] <nacc> kyrofa: i'm here now
[20:32] <kyrofa> cratliff, https://forum.snapcraft.io/t/expose-a-more-consistent-subset-of-systemds-service-directives
[20:33] <nacc> kyrofa: did you have any furhter thoughts? this is a relatively big blocker for me right now
[20:38] <nacc> kyrofa: i'm going to try reordering my build
[20:38] <nacc> we don't really care about usinng the new xz in dpkg's build, I do't think
[20:40] <ogra_> compression is overrated anyway :P
[20:41] <nacc> heh
[20:41] <nacc> well, SOVERSION'd compression ;)
[20:49] <ogra_> kyrofa, the bugy is fix comitted for Ubuntu Core (Snappy) and livecd-rootfs, snapd had at a similar time the fix in profile.d (which was the only sane thing we could do from a cross distro perspective)
[20:50] <ogra_> (sorry, only just noticed you answered above)
[21:01] <kyrofa> cratliff, https://forum.snapcraft.io/t/service-ordering
[21:02] <nacc> kyrofa: cool, i think orderign (after adding some deps), is letting dpkg build
[21:02] <nacc> kyrofa: but it does imply a snapcraft bug if the ordering breaks the build inn a non-obvious way
[21:03] <kyrofa> nacc, yes I'd say so
[21:03] <nacc> kyrofa: i'll add it to my backlog of bugs to file :)
[21:50] <mup> PR snapcraft#1573 opened: WIP project_loader: parse YAML without processing it <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1573>
[21:57] <nacc> kyrofa: any ideas? http://paste.ubuntu.com/25623175/
[22:09] <nacc> kyrofa: that's pygit2 from a part using the python snap
[22:09] <kyrofa> nacc, are you using python from the archive?
[22:11] <nacc> kyrofa: yes
[22:13] <mup> Bug #1719747 opened: Fedora 26 LXD container: cannot load apparmor profile <Snappy:New> <https://launchpad.net/bugs/1719747>
[22:14] <kyrofa> nacc, sergiusens will know more, but I seem to remember an issue with that, e.g. it's hard-coded to the wrong libc or something. We had to build our own Python in snapcraft to get around it