/srv/irclogs.ubuntu.com/2019/06/19/#snappy.txt

zygaGood morning06:33
zygaIt rains, finally06:33
amurrayzyga: how's your mouth?06:36
mvohey zyga and amurray06:46
mvozyga: yeah, how are you today?06:46
mvogood morning sil210006:47
sil2100Morning o/06:58
=== pstolowski|afk is now known as pstolowski
pstolowskimornings!07:05
zygaHey. It hurts and bleeds but I think it is better than yesterday evening07:37
zygaHad a rough night but I am trying to get back to my feet07:37
pstolowskizyga: sounds scary, hope it's not too terrible.. get some rest07:43
pstolowskimvo: hey, ok to close #7000? i'll propose a new one08:07
mvopstolowski: yes, thats fine08:10
jameshpedronis: hi.  Re: the user session agent PR, I was able to put something together to have xenial's dbus-daemon launch a systemd version of "snap userd" with the right environment.08:10
jameshpedronis: the problem comes when adding unix socket activation, since that provides a new method of starting the service that bypasses the environment load08:10
pedronisjamesh: I see, we should be able to do something about that, no?08:11
jameshpedronis: the normal way the environment gets populated is through /etc/X11/Xsession.d/95dbus_update-activation-env08:17
jameshpedronis: and the dbus-update-activation-environment helper program doesn't seem to handle the case when the systemd user instance is not present on the bus08:18
mvopstolowski: looking forward to see the new one, but fwiw, I think we should not make the perfect the enemy of the good, just dealing with missing "core/current" will already help even though we don't deal with "snapd" yet08:18
pedronisjamesh: my point, can't setup something that runs on sessions that can talk to the systemd userd ?08:19
pedronissorry08:19
jameshit's not clear where we should get the environment from in this case08:19
pedronisjamesh: ?08:20
jameshhmm.  maybe within the "snap userd --autostart" call?08:20
pedronisfor example08:20
jameshpedronis: systemctl can talk to the user instance because it has some private back channel for this case08:20
pedronisjamesh: my main point is that exept userd instances to be able to somehow setup talking to each other08:21
pedronisthey could talk over sume /run files08:21
pedronisor something else08:21
pedronis*some08:21
jameshpedronis: I'm still not entirely sure what the benefit of having these two separate tasks colocated in the same process is though.08:23
pedronisjamesh: how do we do user notifications if they are not?08:23
pedronisit one of the things you said we cannot do we they aren't08:23
pedronismaybe I misunerstood you08:23
jameshpedronis: we can do that with just the session bus address, which I think I can work out a way to get08:24
pstolowskimvo: in the new version of 7000 i'm simply comparing snapd version string and got rid of the entire current symlink & refresh time logic08:24
jameshbeing able to do xdg-open relies on a lot more08:24
pedronisjamesh: but in bionic we could have signle process though?08:25
pedronis*single08:25
jameshpedronis: yes.08:25
pedronisjamesh: as I said I'm a bit worried to have a design that is more meant to accomodate xenial, than bionic08:26
pedronisbut I understand there a trade offs08:26
jameshpedronis: I'd see it more as allowing existing functionality to continue as is.08:27
mvopstolowski: sweet08:28
mvopstolowski: that sounds like the right approach, thank you!08:28
jameshpedronis: also, having some separation between a service performing actions on behalf of untrusted apps and a service performing actions on behalf of snapd doesn't sound like a bad thing08:28
pedronisjamesh: you wrote this: "This also means that we will likely won’t be able to have the REST service post desktop notifications on Xenial. "08:29
pedronisyou are saying this doesn't need to be true?08:29
jameshpedronis: yes.  I noticed afterwards that the Upstart job is writing the bus address to $XDG_RUNTIME_DIR/dbus-session08:31
jameshpedronis: so a hack sufficient to get notifications working on Xenial would be to check for that file when $DBUS_SESSION_BUS_ADDRESS is not set08:32
pedronisjamesh: if it's to fiddly to get one process on xenial, I'm ok with two processes, as long as we keep it can keep their functionality clearly separate, we don't have things we want to do that we can't08:32
jameshthat doesn't generalise to the xdg-open case though (I don't think)08:33
pedronisnotifications and getting user input on them is one of them08:33
pedronispstolowski: thanks for #701408:34
pedronisI'l try to look at it soon08:34
pstolowskiyw, ty08:34
jameshthat's another issue: Unity 7's notifications design explicitly doesn't support actions08:34
pedronisI imagine it's fairly mechanic08:34
pedronis^ this was about #7014 (to be clear)08:35
jameshthat said, I don't think popping up dialogs will be particularly popular as an alternative08:36
jameshanyway.  That's something to test down the road08:36
pedronisyes, in theory it would be better if it was up to the snaps08:38
pedronisto display things08:38
pedronisnot snapd itself08:38
pedronisbut we'll have to see08:38
pedronisjamesh: can you write something about notifications and how to get hold of the session dbus on xenial and bionic in the forum topic08:41
jameshsure.08:42
jameshI need to check what notify-osd actually does if I post a notification with actions.  At one point it converted it to a dialog itself.  Not sure about now.08:43
pedronisjamesh: thank you08:43
seb128jamesh, it still does that, notify-osd didn't change for like 7 years :)08:45
jameshseb128: that's probably a good thing in this case.  Thanks08:45
seb128yw!08:46
jameshpedronis: fwiw, it looks like CentOS 7 doesn't have a user instance of systemd at all, so it is like Ubuntu 14.04 in that respect08:55
pedronisjamesh: ok, we'll need to think about degradation of these features08:57
* zyga just spilled coffee over *everything* on his desk08:58
zygathis is not my day08:58
jameshpedronis: if you only care about CentOS 7 on servers it is probably fine.  CentOS 8 is just around the corner too08:59
* pstolowski school end & early lunch, bbl10:05
Chipacapedronis: should 'snapctl set-health' be usable as non-root?10:13
pedronisChipaca: do we even have that concept for snapctl commands ?10:14
pedronisChipaca: anyway if the cookie is right I don't see why not10:14
pedronisChipaca: am I missing something?10:16
Chipacapedronis: I'm not sure what you're wanting to ask wrt your 1st question10:16
Chipacapedronis: currently 'snapctl set-health' fails with 'error: cannot use "set-health" with uid 1001, try with sudo'10:17
pedronisChipaca: mmh ?10:17
pedronisdid we change something10:17
pedroniswas it always like that?10:17
pedronisI thought for snapctl we used a different socket10:17
pedronisand only the cookie counted10:17
Chipacaoverlord/hookstate/ctlcmd/ctlcmd.go:return &ForbiddenCommandError{Message: fmt.Sprintf("cannot use %q with uid %d, try with sudo", f.Name, f.Uid)}10:17
Chipaca(which is funny because how is sudo going to work 'inside')10:18
Chipaca(from a hook i mean)10:18
Chipacabah, hooks are run as root i guess?10:18
pedronisyes10:18
pedronishooks are run as root10:18
Chipacapedronis: there's a whitelist of not-root things10:19
Chipacaright now it's "get" and "services" that are whitelisted10:19
pedroniswhere is it?10:19
pedronisapparently I didn't know about this10:19
Chipacapedronis: overlord/hookstate/ctlcmd/ctlcmd.go line 12410:19
pedronisinteresting10:20
pedronisbut ok10:20
pedronisChipaca: I sort feel like setting healt should be ok not from root10:20
pedronisthough10:20
pedronis*health10:21
Chipacaok done10:25
Chipacahmm, revision is _not_ getting set :-(10:25
* Chipaca hmms10:25
pedronisChipaca: ephemeralContext sets snap name but not revision10:29
pedronissee hookmgr.go10:29
Chipacapedronis: but I'm also getting unset when it's not ephemeral (ie when it's a hook)10:31
pedronisah10:31
pedronisI feared that, I thought we discussed that10:31
Chipacayeah10:31
ChipacaI got a revision in there at some point10:31
Chipacaoh wait10:31
Chipacapedronis: i'm using 'try', which don't do revisions there10:31
alan_gsergiusens, we thought (apparently wrongly) that the LP builders could handle "layouts", so we dropped "passthrough" for the Mir related snaps and started seeing "Issues while validating snapcraft.yaml: Additional properties are not allowed ('layout' was unexpected)". Any thoughts?10:32
alan_gHere's an example: https://launchpadlibrarian.net/429275346/buildlog_snap_ubuntu_bionic_i386_mir-test-tools-edge_BUILDING.txt.gz10:32
cjwatsonalan_g: This doesn't sound like something where Launchpad has much of an opinion either way ...10:41
cjwatsonalan_g: Looks like you're not using a base?  In that case you'll be using the snapcraft .deb package rather than the snap10:41
cjwatsonalan_g: That probably accounts for whatever difference you're seeing10:42
cjwatsonalan_g: Oh, huh, you are using a base.  How are you requesting these builds exactly?10:43
cjwatsonI think you're probably using an old API method10:43
alan_gSaviq, ^ you probably know how we're starting these10:47
Saviqthat's very likely10:47
* Saviq waits for github10:48
Saviqcjwatson: https://github.com/MirServer/mir/blob/master/tools/process_snaps.py#L24710:49
* Saviq missed the memo that there's new API10:50
cjwatsonOK, so the problem with the API you're using is that it's synchronous so we can't fetch snapcraft.yaml from the source repository and inspect it to decide what to do without a serious risk of timeouts10:52
cjwatson(This was a mistake but we didn't realise it when we designed that API the first time round)10:53
cjwatsonSaviq: You want https://launchpad.net/+apidoc/devel.html#snap-requestBuilds - so instead of "builds = snap_recipe.requestAutoBuilds()", use "snap_recipe.requestBuilds(archive=snap_recipe.auto_build_archive, pocket=snap_recipe.auto_build_pocket, channels=snap_recipe.auto_build_channels)"10:54
cjwatson(Or different values of archive/pocket/channels if you like, but that will preserve existing behaviour)10:55
Saviqcjwatson: ack, thank you10:55
cjwatsonNote that this doesn't and can't return the list of created builds (because it's asynchronous), but you weren't using them anyway10:55
Saviqindeed10:55
zygaI collected my notes from the sprint and published them to the forum: https://forum.snapcraft.io/t/snapcraft-summit-2019-montreal-a-snapd-perspective/1190511:30
zygaWimpress: ^  feedback welcome, I specifically made this separate from the main thread because those are things that are mainly of interest to the snapd development and design team11:32
zygabreak for some water11:32
zygamvo: ^ more less complete11:34
popeyzyga: tweet out a link with a nice description and a photo of your montreal summary and I'll get it shared from snapcraftio11:52
zygapopey: sure, will do :-)11:56
WimpressNice write up zyga :-)11:57
popeyok, just ping us a link when done12:00
pstolowskire12:02
sergiusenszyga: nice, typo alert (Gotod)12:07
zygasergiusens: thanks! I will fix that shortly12:08
zygapopey: https://twitter.com/zygoon/status/1141316717899071489?s=2112:08
popeyhaha.. that's an interesting photo!12:09
WimpressEye catching you might say :-)12:09
zygaEye popping12:09
WimpressI've replied to my post on the internal mailing list with a link to your forum post zyga12:09
popeythanks!12:10
cwayneit feels like zyga is staring into my soul12:10
cwayneand im worried he doesn't like what he sees12:10
WimpressWell, it me stood behind him; so a fair assessment.12:10
cmatsuokamvo: did you just resolve a comment in the slides?12:11
cmatsuoka(it disappeared in front of my eyes)12:13
Pharaoh_Atemzyga: you look like you've drank too much coffee12:41
mvocmatsuoka: I didn't, at least not just now, just returned from lunch :)12:41
cmatsuokamvo: hm, strange, perhaps I deleted it by mistake but undo can't bring it back so -- it was the one about the separate recovery kernel12:42
cmatsuokamvo: I added that because we would need a separate extracted kernel for u-boot, otherwise selecting a new kernel for recovery would affect the next normal boot12:43
cmatsuoka(if it overwrites the existing extracted kernel)12:43
cmatsuokadoes it make sense? otherwise I can just remove that entry from the slides12:44
mvocmatsuoka: aha, I think I know what you mean - but please update and mention it only affects uboot at this point12:46
cmatsuokamvo: done that already12:46
mvota12:47
=== ricab is now known as ricab|lunch
* cachio lunch14:40
=== ricab|lunch is now known as ricab
abeatojdstrand, hey, I have a couple of minor MPs related to interfaces: https://github.com/snapcore/snapd/pull/6962 and https://github.com/snapcore/snapd/pull/697515:01
jdstrandabeato: done, thanks! :)15:07
abeatojdstrand, thank you!15:09
mvopedronis: just fyi, I'm triggering a new edge core build now (will take a little bit until all the bits are ready)15:28
=== pstolowski is now known as pstolowski|afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!