/srv/irclogs.ubuntu.com/2017/08/28/#snappy.txt

andschwaI need some help. I'm looking for the global configurations so I can change SNAP_DATA and SNAP_COMMON for all my snaps (so I can install them to a separate drive).01:49
andschwaBut my god, I've searched and searched. There's docs on what the environment variables are, but not how to set them for snapd.01:49
andschwaShould I really perhaps be looking at mounting my drive to /var/snap?01:50
andschwaThis seems like a super straightforward thing to do.01:56
andschwaAnd I cannot find it.01:56
andschwaIs anyone here, or is everyone on "Rocket"?01:59
andschwaIs what I want to do against snappy's design or something?02:05
andschwaIt doesn't seem like it, since it's all centered around environment variables set at runtime by snapd for a snap.02:05
andschwaSo it seems almost explicitly setup such that you can change what snapd sets those variables to.02:05
andschwaYet I cannot find it.02:06
=== chihchun_afk is now known as chihchun
mupPR # closed: snapd#2807, snapd#3120, snapd#3260, snapd#3372, snapd#3398, snapd#3484, snapd#3502, snapd#3556, snapd#3573, snapd#3616, snapd#3617, snapd#3621, snapd#3625, snapd#3635, snapd#3642, snapd#3697, snapd#3719, snapd#3720, snapd#3727, snapd#3734, snapd#3748, snapd#3750, snapd#3755,04:25
mupsnapd#3759, snapd#3760, snapd#3773, snapd#3777, snapd#3779, snapd#3780, snapd#3781, snapd#3795, snapd#3797, snapd#3804, snapd#3805, snapd#3807, snapd#3810, snapd#381204:25
mupPR # opened: snapd#2807, snapd#3120, snapd#3260, snapd#3372, snapd#3398, snapd#3484, snapd#3502, snapd#3556, snapd#3573, snapd#3616, snapd#3617, snapd#3621, snapd#3625, snapd#3635, snapd#3642, snapd#3697, snapd#3719, snapd#3720, snapd#3727, snapd#3734, snapd#3748, snapd#3750, snapd#3755,04:26
mupsnapd#3759, snapd#3760, snapd#3773, snapd#3777, snapd#3779, snapd#3780, snapd#3781, snapd#3795, snapd#3797, snapd#3804, snapd#3805, snapd#3807, snapd#3810, snapd#381204:26
abeatoogra_, do you know which is the current status of https://forum.snapcraft.io/t/updating-bootloader-assets-in-the-gadget-snap ?06:24
=== JoshStrobl is now known as JoshStrobl|zzz
mupPR snapd#3759 closed: add spread test for wayland <Created by jdstrand> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/3759>07:39
zyga-susegood morning07:41
zyga-susesorry for being late, I was the last one at breakfast, along with my sleepwalking daugther07:41
zyga-susemvo: how are you doing today?07:44
mvozyga-suse: hey, good morning. doing fine, how are you?07:45
zyga-susepstolowski: hey, I think there's something you want to look into07:45
zyga-susemvo: perhaps ^ before release07:45
zyga-susemvo: downgrading from master to stable fails if you have any changes in flight that involves hooks07:45
zyga-susebecause of the new hooks that don't have handlers07:46
mvo zyga-suse hm, interessting. what does the error look like? can you pastebin the session?07:47
pstolowskizyga-suse, hey07:47
zyga-susemvo: I _may_ I ran into it over weekend07:48
* zyga-suse scrolls back07:48
mvozyga-suse: thank you07:48
zyga-susemvo: essentially this looks like the "CE cannot rollback" problem we had07:48
mvozyga-suse: I'm mostly curious about the exact effect, if we really cannot rollback that is a problem07:49
zyga-susemvo: aha, maybe that wording was too strong, I think the given change will fail but rollback as a whole will work (still just guessing)07:49
mupPR core#38 closed: Add another pi-config option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/38>07:50
mupPR core#54 closed: Use io.snapcraft.Launcher instead of com.canonical.SafeLauncher <Created by mvo5> <https://github.com/snapcore/core/pull/54>07:50
mvozyga-suse: yeah, if that is the case its bad but not a blocker for the release. still something we want to fix07:51
mupPR core#38 opened: Add another pi-config option <Created by sergey-borovkov> <https://github.com/snapcore/core/pull/38>07:51
mupPR core#54 opened: Use io.snapcraft.Launcher instead of com.canonical.SafeLauncher <Created by mvo5> <https://github.com/snapcore/core/pull/54>07:51
pstolowskizyga-suse, what do I do exactly to reproduce?07:51
mvozyga-suse, pstolowski: please keep me updated :)07:51
zyga-susepstolowski: wait, let me find it07:51
zyga-susemvo: one more thing, I merged that PR with apparmor probing code07:52
zyga-susemvo: I re-designed it after your comment07:52
zyga-susemvo: please have a look if you like that07:52
mvozyga-suse: you merged it and then re-designed it?07:55
zyga-susemvo: no, I read your comment, re-designed and merged07:55
mvozyga-suse: ok, I have a look. but I would prefer to look before it gets merged (two +1 and all that)07:56
zyga-susemvo: it's very similar to your suggestion and I had +1 from jamie so I merged it but I'll wait for re-affirmation next time07:57
* zyga-suse still looks for that hook info07:57
zyga-susedarn, where was that...08:02
zyga-susepstolowski: sorry I cannot find it08:06
zyga-suseI think it was on IRC but you were already off08:06
zyga-susebut I cannot see it in my backlog08:06
zyga-susepstolowski, the situation is as follows, start installing a snap using master, stop snapd and revert to stable08:07
pedronisI don't see many solutions here except changing the handling of hooks slightly in 2.2608:10
zyga-suseI think being more graceful, as if the task was done in 2.26 would be good08:11
zyga-suseessentially you cannot rely on the hook08:11
zyga-susesince old snapd may run it08:11
zyga-suseand if you want to rely, use assumes08:12
pedronisis the revert of core itself that explodes?08:12
zyga-suseI don't remember, I think it was not the core but then again, it may be08:12
zyga-suseand in that case it would be unfortunate08:12
mvozyga-suse: I put some comments into the PR 3808, nothing criticial but worth considering IMO08:14
zyga-susesure,08:14
mvozyga-suse: don't get me wrong, I appreciate the work on this feature and I know its frustrating to wait for reviews :)08:16
zyga-susemvo: the nil result is something I copied from Chipaca's PR08:18
zyga-susemvo: I can undo that, I was just surprised that you can call methods on typed nil just fine08:18
zyga-susemvo: and I did it here08:18
mvozyga-suse: right, its fine, I was also surprised about it (haven't seen that pattern) and that is one good reason to have it in code review to spread the knowledge etc :)08:19
* zyga-suse got a telemarketer call now08:19
mvozyga-suse: do you remember what PR it was where Chipaca used this nil check pattern? curious to see how/why it was used there too08:19
mvozyga-suse: meh, I hate those08:19
zyga-susewith a 500GB 3G/LTE data plan08:19
zyga-susemvo: no, but maybe Chipaca remembers, it was very recent08:20
zyga-suseat 23euro / month08:20
* zyga-suse is considering that 08:20
zyga-susethey also bundle some crap laptop08:20
mvoChipaca: do you think you could have a look at 3795? it probably also needs a review from niemeyer but if we are happy with the code that will help I think (we need gustavo mostly for the concecpt behind it)08:22
mvoChipaca: its also short :)08:22
zyga-susemvo: replied08:23
zyga-susemvo: let me know if you want me to change the nil pointer thing08:23
zyga-suseman, clouds == crap network08:24
pstolowskizyga-suse, you mean install a deb with master, then revert to debs from the distro?08:26
pstolowski(pardon my ignorance, but I'm not sure if it should involve some images from edge etc.)08:27
zyga-susepstolowski: I think just install edge and go to stable08:29
zyga-susepstolowski: and have the right snap install pending08:29
pstolowskik08:40
* mwhudson waves08:40
zyga-susehey mwhudson08:43
Chipacazyga-suse: mvo: good morning!08:49
Chipaca*technically* it's a national holiday here08:49
zyga-suseChipaca: ohhh, nice08:49
zyga-suseso what are you doing here?08:49
Chipacazyga-suse: having breakfast, and also i've been trying to snap a rather gnarly application08:49
zyga-suse+10008:50
zyga-suseI love trying to snap things08:50
zyga-suseto see how that feels like08:50
zyga-suseand to see what issues I run into08:50
Chipacait's looking like i can't make this one work without either bases or layouts08:50
Chipacaand that assumes layouts lets me replace /lib08:50
Chipacazyga-suse: mvo: which PR were you two discussing?08:54
zyga-suseChipaca: remember when you showed me a PR where you did methods on nils?08:57
zyga-suseChipaca: and I was surprised this is doable in go08:57
Chipacayes08:58
mupPR snapcraft#1512 opened: pluginhandler: clean error for BasePlugin.run{,_output} <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1512>09:00
zyga-susemvo: ^09:01
ogra_abeato, no idea, perhaps ask in the thread ?09:04
pedronisafaik it's been postponed09:05
abeatoogra_, ok, will do09:05
mvoChipaca: context is my review of 3808, most specically https://github.com/snapcore/snapd/pull/3808/files#r13546324009:06
mupPR snapd#3808: apparmor,release: add better apparmor detection/mocking code <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/3808>09:06
mvoChipaca: and was curious in what context you use it. in the context of this pr I was mostly wondering why not just return by-value but mostly I wanted some context as this is/was a new pattern for me09:07
mupPR core-build#11 closed: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>09:07
mupPR core-build#11 opened: remove cruft from the writable-paths <Created by mvo5> <https://github.com/snapcore/core-build/pull/11>09:08
zyga-susemvo, Chipaca: please let me know if you want me to change that code, otherwise I'll move on to other work09:10
mvomeh, it looks like our update to github.com/snapcore/snapd/vendor/golang.org/x/sys/unix broke powerpc09:10
* mvo looks09:10
zyga-suseaww, sucks09:10
zyga-susemvo: btw, golang 1.9 had some support changes for that arch09:10
zyga-susethey dropped some older HW09:10
pedronismvo: we updated it because of the golang/x/crypto update, I don't even think we needed it before09:11
pedronisfwiw09:11
* pstolowski amazed by mvo's code review09:13
zyga-suseChipaca: hmm, why doesn't logger.Noticef print stuff?09:14
pstolowskimvo, thank you for taking time & proposing the changes09:14
pstolowski!09:14
mvopedronis: aha, thanks, that is good to know, I will investigate, its a bit of a bummer09:14
zyga-suseChipaca: but it does later09:14
zyga-suse2017/08/28 11:13:52.385942 daemon.go:275: started snapd/2.27.3+git744.gd34c3ddc6 (series 16; classic; devmode) opensuse/20170823 (amd64) linux/4.12.8-1-default.09:14
zyga-susethat's the first message I see09:14
mvopstolowski: your welcome, my pleasure09:14
zyga-susebut before that I call noticef + println in another spot and only the println shows up09:14
mwhudsonzyga-suse: 1.9 changed stuff around ppc64 big endian, which has never been an ubuntu architecture09:14
mvozyga-suse: go-1.9> things we should land?09:14
mvozyga-suse: in master I mean?09:14
zyga-susemwhudson: ah, good09:14
mwhudsonzyga-suse: this failure is about powerpc09:14
mwhudsoni.e. 32-bit09:14
zyga-suseaha09:15
* zyga-suse shuts up then09:15
mwhudsonwhich stopped being an ubuntu architecture in ... zesty?09:15
mwhudsonit ought to be possible to add gccgo / powerpc support to sys/unix, i never figured out how to do it thouh09:15
mwhudson(also didn't care overly much)09:16
mvomwhudson: powerpc we probably still need to support because of 16.04, the failures look slightly nasty: http://paste.ubuntu.com/25416387/09:16
* zyga-suse sees SetLogger09:16
mwhudsonmvo: x/sys/unix just doesn't support powerpc at all09:16
mvomwhudson: aha, great that you know more about this, so what are our options? can we avoid sys/unix somehow?09:16
mwhudsonmvo: i don't know which bit of crypto is using it09:16
Chipacamvo: sitting in the top of the tree, try: find -type f -name \*.go -print0 | xargs -0 perl -wne 'BEGIN{$n=0}; if ($n!=0) {$n=0; print "$ARGV: $f$ARGV: $_" if /if $v == nil/ }; if (/^func \((\S+) \*/) {$n=1; $f=$_; $v=$1}'09:17
Chipacazyga-suse: where doesn't logger.Noticef print stuff?09:17
mwhudsonmvo: support for other arches with gccgo has been added, so presumably the same can be done for ppc09:18
zyga-susewoah09:18
zyga-susethat's nice09:18
Chipacazyga-suse: it might be trying to print stuff before it's initialised?09:18
ogra_mvo, i just noticed that the initramfs-tools-ubuntu-core deb is behind the git tree, androidboot is missing and there was no deb build after the unit tests branch landed ... if i push that to the PPA today do i disturb any release ?09:18
zyga-suseChipaca: I patched an init() function in a module to call it09:18
zyga-suseChipaca: I understand that during startup we actually init the logger09:18
Chipacayes09:18
zyga-suseChipaca: and I got the short end of the ordering stick09:18
Chipacaprobably09:18
zyga-susehmmm09:18
* zyga-suse wants the user warning framework09:19
zyga-suseI could really use it now09:19
Chipacazyga-suse: is this in debugging snapd?09:19
zyga-suseyes09:19
zyga-susewell09:19
Chipacazyga-suse: just print it?09:19
mvoogra_: thanks for checking, things should be fine today09:19
zyga-suseI want something more sticky09:19
zyga-susejdstrand requested that we log that we are on partial apparomr09:19
ogra_mvo, ok, then i'll upload09:19
zyga-suse"prominently" logged09:19
zyga-suseChipaca: I'll just print it with a comment09:20
pedronisso the failing test now is passing, so probably a bunch of other tests might start failing, will see09:20
Chipacamvo: that pattern is used in our code in a few places where the expected use of a something includes it sometimes being nil09:21
ogra_so i built a wine snap last night ...09:22
mvoChipaca: thanks, interessting, it escaped me so far09:22
ogra_and since wine currently only does i386 i actually had to build for i386 ...09:22
Chipacamvo: so rather than having “artifact:=default; if thing != nil {artifact = thing.GetArtifact()}”, you move the check into GetArtifact09:23
ogra_and i must say i have never had such a painful experience with snapcraft :/09:23
ogra_(trying to build for i386 on amd64 host)09:23
pedronisChipaca: mvo:  go does it by static typing, but it exists as pattern since smalltalk (maybe even earlier), afaik it is liked/disliked ever since though09:24
Chipacaogra_: you know you can ship i386 binaries in an amd64 snap, yes?09:24
Chipacamaybe that wasn't your issue :-)09:25
ogra_Chipaca, but when buiolding from source you still need a i386 build env09:25
Chipacaanyway, i'll shut up now, seeing as how i'm not really working09:25
mvoChipaca, pedronis: thanks, it makes perfect sense was mostly wondering a bit when/how to use it. thanks for your input on this :)09:25
Chipacaogra_: “apt install build-essential:i386”?09:25
ogra_and i dont want the 79234846 build deps wine needs installed on my host ...09:25
Chipacaah09:25
ogra_so i use cleanbuild09:25
ogra_and then things explode09:26
ogra_even using a plain lxd container as i386 system doesnt work properly09:26
ogra_(there is an unfixed bug in libc)09:26
mwhudsonpedronis: smalltalk is a bit different though, messages sent to nil are all ignored, iirc?09:26
* zyga-suse suffers terrible network09:28
zyga-susejust 2 days left09:28
zyga-suseI'll be home by Wednesday09:28
pedronismwhudson: well, I was more referring to people adding implementation of things to nil09:30
pedroniswhich you can09:30
mwhudsonah09:31
pedronis(unless I'm totally misremembering this)09:31
pstolowskizyga-suse, - Run refresh hook of "core" snap if present (internal error: no registered handlers for hook "refresh")09:31
pstolowskizyga-suse, ^ is that what you saw when refreshing core from stable to edge and back to stable?09:31
zyga-suseyes09:34
zyga-susethat's what I saw09:34
mupPR snapd#3814 opened: interfaces: enable partial apparmor support <Created by zyga> <https://github.com/snapcore/snapd/pull/3814>09:34
zyga-susepstolowski: is that a release blocker?09:34
mvo3781 needs a second review, its very nice and not very long09:37
pstolowskizyga-suse, afaict we don't have this hook in release/2.2709:39
pedronispstolowski: a blocker for 2.2809:40
* zyga-suse looks at 378109:40
mvoChipaca: 3748 has a conflict09:40
pstolowskipedronis, oh, for 2.28 yes09:40
pedronisor for 2.27 if we decide we need to do something there09:40
pedronisit seems this a problem that will show up again and again with new hooks09:41
pstolowskiyes09:43
zyga-susepedronis, pstolowski: are you suggesting a 2.27.5 with some future-proofing for hooks in general?09:44
zyga-suseahead of 2.28 release?09:44
pedronisI don't know09:44
pedronisI'm mostly musing09:44
* zyga-suse nods09:47
pstolowskii'm not sure. i need to fully understand the problem. hook machinery is a little bit deceptive with the 'Optional' flag. clearly the registration of hook handlers is critical09:48
zyga-suseoptional feels like "may fail"09:49
zyga-susebut we need to know it exists09:49
zyga-susewhich poses a problem for each added hook09:50
pstolowskii have a feeling that the only way around this is to make a missing handler non-critical09:50
pedronisif it's optional and the hooks doesn't exist in the snap, we don't care if the hook is registered or not09:50
pedronisinternally09:50
pedronisbut I don't remember the internal details to know if this is easy or not to tweak that way09:50
pedronisit probably breaks abstractions09:51
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
pstolowskiuh oh we have a logic like this in place already, but i think it has a bug10:22
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
* tbr slaps chihchun_afk around a bit with a large and slimy trout. Dude, turn off your nick-changes. That annoys the crap out of people.10:38
zyga-susewhee10:41
zyga-suselet me try it on ubuntu now10:42
zyga-susemvo: I'm almost ready with 2.28 branches :)10:42
zyga-susemvo: how are we doing with release freeze/fork10:42
ogra_zyga-suse, oh, did you tell pstolowski about the "refresh back to beta" image we found on the weekend ?10:43
ogra_(i didnt file a bug)10:43
zyga-suseogra_: yes, I was wondering where I saw that10:43
ogra_pstolowski, http://paste.ubuntu.com/25416803/10:43
zyga-suseogra_: was that on IRC? I couldn't find the discussion10:44
zyga-suseogra_: woot, thank you :)10:44
ogra_this is when moving to edge (for a test) and then trying to go back to beta10:44
zyga-susemvo: ^ given this I would say we need to fix that for 2.2810:45
pstolowskiogra_, yeah, that's the issue i'm looking on. nb, you can of course snap revert core10:46
ogra_a revert would switch channels ?10:46
mvozyga-suse: sounds like something we need to 2.28, yes. I understand pstolowski is looking into it(?)10:47
pstolowskiogra_, no, just mentioning, it won't fail that way10:47
ogra_right10:47
pstolowskimvo, yes, i think i've a fix10:47
ogra_it only fails when moving to edge and trying to go back though ...10:47
ogra_(i doubt it affects the beta/candidate or stable channels yet)10:48
zyga-suseogra_: and by extension it will fail when CE will test rollback from 2.2810:48
ogra_right10:48
fgimenezhey mvo, looks like CE QA found an issue with 2.27.4, i've just forwarded you the message10:55
mvoChipaca: http://paste.ubuntu.com/25416853/ is probably something we need to fix for 2.2810:55
mvofgimenez: thanks, let me have a look10:56
zyga-susefgimenez: can this be public somewhere please?10:56
zyga-susemvo: also FYI, not for 2.28 (needs research first) but important as it breaks containers: https://bugs.launchpad.net/snapd/+bug/171293010:57
mupBug #1712930: snap-confine: mounts happen in the wrong order <snapd:In Progress by zyga> <https://launchpad.net/bugs/1712930>10:57
fgimenezzyga-suse: not sure better ask them, they are posting to snap-update-verification@lists.canonical.com, maybe you can subscribe?10:57
zyga-susefgimenez: I mean, I could do that but then again we have https://forum.snapcraft.io/t/in-progress-snapd-2-27-4/572 that everybody should post to10:58
mvozyga-suse: hm, is this just changing the order of things (ideally switching two lines). or is there more work involved here?10:59
fgimenezzyga-suse: yeap, i already mentioned them about the forum and the release threads but don't know about how (or if) they make their test results public, they can explain better for sure :)11:03
zyga-susemvo: not sure if this is just two lines :)11:05
zyga-susemvo: could be trivial or very complex, I didn't look yet11:06
mvook11:06
mupPR snapcraft#1513 opened: lifecycle: outdated step should raise SnapcraftError <Created by kalikiana> <https://github.com/snapcore/snapcraft/pull/1513>11:06
mupPR snapd#3815 opened: tests: install test-snapd-complexion on core <Created by mvo5> <https://github.com/snapcore/snapd/pull/3815>11:18
mvoChipaca: trivial reproducer -^11:18
zyga-susehmmmmmmm11:22
* zyga-suse is unhappy about https://travis-ci.org/snapcore/snapd/builds/269141620?utm_source=github_status&utm_medium=notification11:22
pedronismvo: I think it's an holiday for John11:22
zyga-suseis that just another bug in apparmor profile loading for tests11:22
zyga-suseor a real issue11:22
zyga-suseindeed11:22
mwhudsonmvo: i wrote up that dput linter wrapper thing I talked about before https://gist.github.com/mwhudson/616499edb1191bd99c987bbbd8781ce911:22
zyga-susehe is off11:22
mvopedronis: oh, thanks11:22
mvoChipaca: weeeh, sorry - you are off today? I won't bother you anymore11:22
mvomwhudson: nice11:23
zyga-susemvo: question, will we re-load snap-confine's apparmor profile before configuring core?11:23
=== yofel_ is now known as yofel
mupPR snapd#3816 opened: hooks: do not error out when hook is optional and no hook handler is registered <Created by stolowski> <https://github.com/snapcore/snapd/pull/3816>11:45
pstolowskizyga-suse, mvo ^ this should fix the problem with hooks, but I only tested with unit test11:45
mupPR snapd#3817 opened: tests: wait more and more debug info about fakestore start issues <Created by pedronis> <https://github.com/snapcore/snapd/pull/3817>11:51
mupPR snapcraft#1510 closed: ci: disable the travis deploy stage for docs <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1510>11:54
mupPR snapcraft#1508 closed: schema: version should have a max length of 32 <bug> <Created by kyrofa> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/1508>12:12
cachiomvo, did you see the email I fw?12:52
mvozyga-suse, spineau, jdstrand: so I think I have an idea about the problem with "sudo network-manager.nmcli d show eth0" getting denies on 2.27 - we enabled seccomp argument filtering for socket. and the profile has "#  socket AF_NETLINK - -" and I assume that nmcli uses the netlink socket12:52
mvocachio: indeed I did and after a small panic I started debugging12:52
cachiomvo, ohhh, any finding?12:53
mvocachio: yes, maybe, I think I need jdstrand to help me, but I suspect we need to enable socket AF_NETLINK at least for nmcli, maybe for more.12:54
cachiomvo, is this caused because the last change done for 2.27.4?12:55
zyga-susemvo: there's a new set of netlink interfaces12:55
zyga-susemvo: maybe those are sufficient there12:55
zyga-susemvo: I wish we knew the values of other arguments but I suspect I can easily check that locally12:55
zyga-susemvo: (if it is netlink or not)12:55
zyga-susemvo: AFAIK it used KOBJECT_UEVENT but perhaps I'm wrong12:56
spineaumvo: like mmcli? that's the first one I can think of12:56
zyga-susemvo: note that jamie is off today, I'll check it out after checking out one other thing12:56
zyga-susemvo: if you can strace it on your machine and pastebin that it would be sufficient12:56
spineauzyga-suse: mvo: I'm still connected to our test device, if I can help you by providing more logs, just ask12:59
zyga-susespineau: thank you, if you know how to run strace under snap confinement (not trivial) then please do that12:59
zyga-susespineau: you need to edit the seccomp/apparmor profiles, allow extra stuff and run strace you get from the host somehow13:00
zyga-susespineau: don't worry if you don't want to go through those hoops13:00
spineauzyga-suse: unfortunately, I'm still a snap newbie13:00
mvozyga-suse: strace is not working for me, hangs13:01
mvozyga-suse: when I enable AF_NETLINK things work13:01
zyga-susemvo: strace needs some love, ok13:01
mvozyga-suse: socket AF_NETLINK - -13:02
mvozyga-suse: if that is part of the profile things work13:02
zyga-susemvo: note that we don't have any interfaces that add that13:03
zyga-susemvo: we have "socket AF_NETLINK - NETLINK_AUDIT" and similarly NETLINK_CONNECTOR13:03
zyga-susewe need to know which one is really required13:03
zyga-susemvo: and perhaps consider an approach (new release of network-manager or a snap-id specific quirk)13:03
willdeberryso it seems that everything was passing, but since I have been rebasing just to keep things fresh, travis build now fails: https://github.com/snapcore/snapd/pull/381213:26
mupPR snapd#3812: Expose bluez interface on classic OS <Created by willdeberry> <https://github.com/snapcore/snapd/pull/3812>13:26
zyga-susemvo: offtopic13:34
pedronisniemeyer: will you create a tracker topic in the forum for the current PRs?13:34
zyga-susemvo: I updated my x250 to zesty13:34
zyga-susemvo: and ... the update removed xorg-input-all13:34
zyga-susemvo: that was curious to debug13:34
zyga-susemvo: apparently people ran into this too and I found lots of forum posts and what not13:35
zyga-susemvo: so now things work13:35
zyga-susemvo: when you don't have xorg-input-all and its deps you have GDM/lightdm with *no* keyboard interaction at all13:35
zyga-susenot even alt-ctrl-f2 to get out13:35
niemeyerpedronis: I'm on the fence about it.. I want to make sure we take it as an actual sprint if it's added, and given all the work on the release we may not be able to do it13:36
zyga-suseaha, so I know what is wrong with the spread setup, nothing, it looks like a very odd and curious apparmor behavior13:36
niemeyerpedronis: Perhaps we can kick it off once the release is clean?13:36
pedronisniemeyer: ok, just wondering because I start to have a bit of hard time finding/remembering what to review13:36
niemeyerpedronis: Aha, I see13:37
niemeyerpedronis: Let me create one then13:37
mupPR snapd#3818 opened: interfaces: fix network-manger plug <Created by mvo5> <https://github.com/snapcore/snapd/pull/3818>13:37
mupPR snapd#3819 opened: hooks: do not error out when hook is optional and no hook handler is registered (2.27) <Created by stolowski> <https://github.com/snapcore/snapd/pull/3819>13:38
mvo3260 needs a second review, tests are green now13:38
mvozyga-suse: 3818 is maybe what we need to fix the nmcli issue, an early look  is appreciated, I mostly opened it to get spread tests running13:39
zyga-susemvo: ack13:43
pedronissnapd#3817 needs quick a review (it's about the fakestore tests that were sill failing sometimes for me in autopkgtests)13:43
mupPR snapd#3817: tests: wait more and more debug info about fakestore start issues <Created by pedronis> <https://github.com/snapcore/snapd/pull/3817>13:43
zyga-susere-started something else and looking13:43
niemeyerForgot to ask.. did we have any other issues on the testing infra after the Spread changes I did on Friday?13:43
ogra_wow, cool ...13:43
ogra_seems my wine snap really works with all exe installers i have lying around ... and all install just go fine to SNAP_USER_DATA13:44
ogra_*all installs13:44
mvoogra_: thats very neat, wine is a nice snap to have13:45
ogra_well, needs --devmode13:45
ogra_(or --classic, but i didnt feel like making a classic snap)13:45
ogra_it wants to read / and /boot13:45
mvomakes one wonder why that :)13:46
ogra_but it it really cool that you can just install wine 2.15 next to the deb one13:46
ogra_because it can put .desktop files in place and such13:46
ogra_for apps it installs13:46
mvoyeah, also wine might be perfect for tracks, i.e. being able to install 2.0, 2.1, etc13:46
ogra_yeah13:46
ogra_i only did it out of curiosity ... but there is a snapcraft source tree now that someone can take and make something real out of it13:47
ogra_our forum doesnt work with the sippped wine IE :/13:47
ogra_*shipped13:47
* mvo nods13:48
ogra_"your browser is to old" :P13:48
ogra_snapcraft.io itself and ubuntu.com work fine13:49
mupPR snapd#3817 closed: tests: wait more and more debug info about fakestore start issues <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3817>13:53
zyga-susemvo: re, thank you for checking it is UEVENT13:55
zyga-suselet me look at something related and I will review this13:55
mvozyga-suse: no real rush, I want to see the test results first, maybe its actually not working13:57
zyga-suseI commented13:58
mvozyga-suse: aha, indeed, silly me, you are right. I will fix13:59
zyga-susethanks!13:59
zyga-suseI checked other interfaces14:00
zyga-susethey all use permanent snippet but for slot14:00
zyga-susefor plug I think it's fine to keep this on connected14:00
mupPR snapcraft#1514 opened: docs: add github processed templates <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/1514>14:07
=== JanC is now known as Guest96910
=== JanC_ is now known as JanC
mupPR snapd#2807 closed: snap: add new `snap switch` command <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/2807>14:11
mupPR snapd#3820 opened: spread: don't set HTTPS?_PROXY for linode <Created by zyga> <https://github.com/snapcore/snapd/pull/3820>14:25
zyga-susemvo: ^ trivial one14:26
zyga-susetested locally14:31
zyga-susemvo: looking at the ordering issue now14:33
mvozyga-suse: great, thank you!14:33
mvozyga-suse: I'm waiting for tests and I think 3818 will need a review from jamie as well, right?14:34
zyga-suseyes14:34
zyga-susenote that jamie is off today14:34
niemeyerpedronis: https://forum.snapcraft.io/t/review-sprint-3/188014:43
pedronisniemeyer: thanks14:49
niemeyerpedronis: No problem.. tweaked the format slightly as apparently the recent changes in Discourse modified some of the old icons we were using, but still same thing14:52
mupPR snapd#3821 opened: tests: new regex used to validate the core version on extra snaps ass <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3821>14:52
* zyga-suse moved indoors, too cold 15:08
=== JoshStrobl|zzz is now known as JoshStrobl
soeehi, i have installed an app via snap and have this: snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks15:45
soeeany idea what is wrong ?15:46
zyga-susehey16:00
zyga-susesoee: let me try to help you16:00
zyga-susesoee: can you start by running "snap version" and pasting the result16:00
Chipacamvo: ah! so on core we need to not do the snippets (and source complete.sh)16:01
* Chipaca disappears again16:01
cachiopedronis, hey, any idea why this error could be happening runing tests on staging ?16:27
cachioerror: cannot fetch snap signatures/assertions: circular assertions are not expected: account (canonical)16:27
pedroniscachio: sounds it's not using the right kind of snapd16:41
pedronismaybe reexec doing something wrong16:41
pedroniscachio: fwiw I used a correctly built snapd against staging on Friday and things worked16:42
pedronissnapd built from master16:42
cachiopedronis, how did you setup the tests?16:43
cachiopedronis, which variables did you use?16:43
cachioI want to replicate that into the sread-cron tests against staging16:44
pedroniscachio:  afair  the test setup should do the right thing, there are two part to this,  you need a snapd built with withtestkeys or withstagingkeys16:44
pedroniscachio: then you need SNAPPY_USE_STAGING_STORE=116:44
cachiopedronis, I have that16:45
cachioexport SPREAD_REMOTE_STORE=staging16:45
cachioit is traduced into  SNAPPY_USE_STAGING_STORE=116:45
pedronisand DEB_BUILD_OPTIONS='nocheck testkeys' dpkg-buildpackage -tc -b -Zgzip16:46
pedronisthe testkeys should do the other part16:46
pedronisI need a bit more details where this exactly is breaking? breaking early or in some specific test?16:47
pedronisanyway I need to go have dinner16:48
cachiopedronis, on those tests https://travis-ci.org/snapcore/spread-cron/builds/268521976#L122416:52
cachiothere are many tests failing for he same reason16:52
pedroniscachio: I'll look in my morning17:11
cachiopedronis, sure, tx17:11
cachioI am taking a look right now too17:11
pedronisnotice that some are other platforms17:13
pedronisI mean != ubuntu17:13
pedronisI don't think it makes sense to run those tests against staging17:13
pedronislike that failure is for opensuse17:14
pedronisI don't know if it knows how to build a staging snapd17:14
cachiook17:16
cachiopedronis, i'll change that too, thanks17:16
pedroniscachio: I mean until we understand more I would skip anything not ubuntu  for staging tests17:16
cachiopedronis, sure17:20
pedronisthe main user of these tests would be store after a staging deployment17:21
pedronisI think they have been too flaky to use them tough :/17:21
cachiopedronis, yes, agree17:24
cachiomost of them have been failing for a while17:24
cachiopedronis, I think staging should be used just to validate some specific stuff17:25
cachiopedronis, so it is easier to keep it in green17:25
zyga-suse_hmm17:44
zyga-suse_- Run install hook of "core" snap if present (internal error: no registered handlers for hook "install")17:44
zyga-suse_https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-image/xenial/i386/s/snapd/20170828_165347_9cd1b@/log.gz17:44
zyga-suse_from upgrade/basic17:44
=== cachio is now known as cachio_afk
=== JoshStrobl is now known as JoshStrobl|Work
stormmoreHow difficult would it be to write a snap that can read /etc with making using --classic?19:14
=== cachio_afk is now known as cachio
mupPR snapd#3821 closed: tests: new regex used to validate the core version on extra snaps ass <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/3821>19:34
niemeyerstormmore: With classic or without classic?19:41
niemeyerpedronis, zyga-suse_, cachio: Review board now has details on who's reviewing or needs to review19:42
cachioniemeyer, nice19:43
stormmoreniemeyer: preferably without19:43
niemeyerstormmore: That needs an interface for the specific need you have.. many are already available, but it may need to be created as well if it's not yet there19:47
niemeyerstormmore: With classic, it's just a matter of opening the files.. nothing fancy to be done19:48
stormmoreniemeyer: whats a good place to see a list of interfaces. I did look there as that was what I was suspecting but I didn't find one that would give even read-only (not sure that is going to be sufficient for my needs yet but gotta start somewhere) access to /etc from their desc19:49
niemeyerstormmore: No interface will give access to all of /etc19:50
niemeyerstormmore: Some will give access to specific bits inside /etc, according to their described purpose19:50
stormmoreniemeyer: ah that is why I am probably leaning towards making this a classic snap (at least initially)19:51
niemeyerstormmore: Yeah, it's a fine way to get started19:51
stormmoreniemeyer: thanks, just wanted to see if there was a "better way" but looks like I was on the right track19:52
mupPR snapd#3120 closed: [WIP] interfaces/hooks: expose attrs to the interface API, snapctl enhancements (step #4) <Created by stolowski> <Closed by niemeyer> <https://github.com/snapcore/snapd/pull/3120>20:00
zyga-suse_niemeyer: wow, that's nice20:08
zyga-suse_WOW, way nicer than I expected :D20:08
zyga-suse_really nice work :)20:10
zyga-suse_niemeyer: I wonder what will happen when we have initial clashes in the team20:10
niemeyerzyga-suse_: Wow, thanks :)20:11
niemeyerzyga-suse_: You mean more than 26 reviewers? ;P20:11
zyga-suse_well, if we get another zygmunt, will we call him z^1 ;D20:12
niemeyerzyga-suse_: We already have clashes.. look closely20:12
niemeyerand apparently we also have a bug.. something is wrong with #3260.. looking20:13
zyga-suse_ah, indeed20:13
* zyga-suse_ is happy that zygmunt is an uncommon word and his life is simple here20:14
cachioniemeyer, do you know which is the job to sync prod with staging stores?20:19
pedroniscachio: there's no such job20:21
cachiopedronis, ok, is it a manual procedura?20:22
pedronisyes, we typically add relevant snaps to staging20:22
pedronisstaging store and prod store are fairly indepedent20:22
cachiook, so I should download/upload the snaps20:23
cachiopedronis, I'll try that20:23
pedronisanyway probably another good reason to cut down staging tests20:24
cachiopedronis, yes20:25
cachiopedronis, if it is not automatic, it does not scale20:25
pedronisnot sure how to do that though, spread doesn't have more tagging than manual20:25
pedronisskipping support is also missing, our skips atm ad hoc20:25
pedronisone approach could be just have a different suite and symlinks20:27
cachiopedronis, why we are running tests against staging?20:29
cachiopedronis, if there is not something new to test on there the best we can do is to remove those execution from spread-cron as you suggested20:30
pedroniscachio: ?  the idea was to run them each time one of the store services gets a new staging deploy ?20:30
pedronisthat's what triggers runs20:31
pedronisto check that changes to the store don't break the contract with snapd20:31
pedronisthat was the idea20:31
cachiopedronis, makes sense20:31
pedronisyes, it's a sound idea, the executation hasn't been amazing so far though, also probably too many not relevant tests20:32
cachioso, we just need to keep the databases synchronized20:32
pedronisand also the store has changed, so we need different checks20:32
pedroniscachio: ?20:32
pedronisdon't think that's going to happen20:32
cachiopedronis, I mean, perhaps the solution is to add a job to keep both in sync20:34
pedroniswe can add something that keeps some subset of snaps in sync20:34
pedronisbut in general afaik there's no plan to keep them generally in sync20:34
cachiopedronis, otherwise always when we do a change in a snap we need to make that same change in staging20:35
cachiois it correct?20:35
pedronisthat's how we did so far, yes20:35
cachiopedronis, ok20:36
cachiopedronis, what do you suggest, disable the staging jobs? or continue doing that sync manually? or start doing something to keep it on sync20:37
pedroniscachio: I think we need to take a step back and setup a meeting with the stakeholder interested in that20:38
pedronisit's not about what *I* suggest 20:38
pedronis*stakeholders20:39
cachiopedronis, ok, makes sense, how are the interested stakeholders?20:39
cachiowho20:39
cachiocelso?20:39
pedronisI can ask tomorrow20:40
cachiopedronis, sure20:40
cachiolet's talk about that tomorrow20:40
niemeyerOkay, figured the issue and fixed.. board updated again, with correct data.21:16
=== matteo is now known as matteo`
=== matteo` is now known as matteo
=== matteo is now known as matteo_
=== matteo_ is now known as matteo|
=== matteo| is now known as matteo
mupPR snapd#3760 closed: Allow snap-confine to be confined even with --disable-apparmor <Created by mwhudson> <Closed by mwhudson> <https://github.com/snapcore/snapd/pull/3760>22:30
mupPR snapd#3260 closed: cmd/snap: implement userd command as replacement for snapd-xdg-open <Created by morphis> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3260>23:36

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