/srv/irclogs.ubuntu.com/2019/03/12/#snappy.txt

zygaGood morning06:08
mborzeckimorning06:19
zygaHey06:22
zygaHow are you?06:22
mborzeckizyga: fine, thanks06:23
mborzeckizyga: it's cold outside :/06:24
zygaYeah06:24
zygaI was walking with the dog for two hours last night06:24
zygaAll the way until midnight06:25
mborzeckizyga: nice06:25
zygamborzecki: quick review to start the day? https://github.com/snapcore/snapd/pull/658706:31
mupPR #6587: interfaces/apparmor: factor out test boilerplate <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6587>06:31
mborzeckizyga: sure, why not06:31
zygamborzecki: I changed some of the test function names but that is all sensibile in the follow-up patch06:34
zygamborzecki: pushed06:48
mborzeckizyga: thanks!06:52
zygathanks06:52
zygaI will push something that  enables apparmor on all of suse next06:52
zygathen I'll look at debian06:53
zygaI think we can handle debian (and derivatives), suse (and derivatives if any) to cover most of apparmor land06:53
zygamborzecki: https://lwn.net/Articles/782786/07:05
zygamaybe mvo should apply07:05
zyga;D07:05
pedroniszyga: hi, when are you going to address 6360 feedback ?07:21
zygapedronis: hi07:21
zygapedronis: most likely today07:22
mborzeckiguys, think we can land this now if everyone is happing with the current phrasing? https://github.com/snapcore/snapd/pull/655607:22
mupPR #6556: cmd/snap: hide 'interfaces' command, show deprecation notice <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6556>07:22
zygapedronis: I already started yesterday but haven't finished yet07:22
pedronismborzecki: I didn't see all the bikeshedding there07:25
mvogood morning07:26
mvomborzecki: hey, yay (or :cry:) at 658507:27
pedronismborzecki: I fear the new sentence is too long07:27
mvohey pedronis07:27
pedronismborzecki: I would like John input on htat07:28
pedronis*that07:29
zygahey mvo07:29
pedronismborzecki: I commented there07:30
mborzeckipedronis: thans07:30
mvohey zyga07:30
pedronismvo: hi07:30
zygamvo: quick review to start the day? https://github.com/snapcore/snapd/pull/658707:31
mupPR #6587: interfaces/apparmor: factor out test boilerplate <Simple 😃> <Created by zyga> <https://github.com/snapcore/snapd/pull/6587>07:31
mvozyga: sure07:31
mvo(when typing this the mouse focus was still on mutt - typing random chars into mutt is really scary)07:31
zygamvo: lol07:32
zygayes07:32
zygakind of like vi but then git prevents critical damage07:32
zygano such thing for mutt07:32
zygamvo: do you want to travel more, apply now for the position of debian leader: https://lwn.net/Articles/782786/07:33
mvozyga: *cough*07:33
mvozyga: and no07:34
zyga:D07:34
zygajoin debian they said07:34
zygasee the world the said07:34
mvozyga: but it would be interessting, pushing some ideas to moderinize things would be nice07:34
mvozyga: hahaha07:34
zygayeah07:34
zygamvo: I see the reference was recognized :)07:34
=== pstolowski|afk is now known as pstolowski
pstolowskimorning08:06
zygahey pawel08:13
mupPR snapd#6587 closed: interfaces/apparmor: factor out test boilerplate <Simple 😃> <Created by zyga> <Merged by zyga> <https://github.com/snapcore/snapd/pull/6587>08:37
mupPR snapd#6580 closed: cmd/snap-confine: drop unused dependency on libseccomp <Created by zyga> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/6580>08:38
mupPR snapd#6588 opened: interfaces/apparmor: partial confinement on openSUSE <Created by zyga> <https://github.com/snapcore/snapd/pull/6588>08:41
pedroniszyga: did you change 6575 since I reviewed it?09:14
zygapedronis: I applied the changes you asked for, fixed a typo that broke he build then merged master and pushed09:15
zygaI then noticed that I left duplicate include line and force pushed to clear it09:15
zygathat's all09:15
pedroniszyga: no, sc_init_invocation was not there when I reviewed it09:16
zygaoh? but it is added before your review?09:16
pedronisno09:16
zygaplease double check, perhaps you reviewed a view that was stale09:17
zygait is so according to the github timeline09:17
pedroniszyga: you force pushed, not point debating this09:17
zygayes, I said that09:17
zygabut that was in the morning  after some things landed and the branch conflicted09:18
zygayou can compare the revisions if you want09:18
pedronisanyway I removed my +109:19
mvozyga: yeah, 6575 changed quite a bit since I looked at it - or so it felt to me this morning but I have not looked at the details09:20
mvoslightly sad because the previous one was ready for merging afaict09:20
zygamvo: I implemented the changes you suggested09:21
zygamvo: and made it clear in the log as well09:21
pedroniszyga: my emails says that stuff was pushed 20 hours ago, and my review was 21 hours ago09:22
pedronisbut as I said hard to tell with force push09:22
zygapedronis: but that force push was done this morning09:22
zygaand after I pushed yesteray I was happy to see your review09:22
mvozyga: sorry, I'm confused, in 6575 I just wrote "looks good" - am I mixing something up?09:23
zygaI'm 100% sure github showed this the same way before i did that in the morning09:23
zygamvo: we discussed this durinig the standup and  you suggested that I put additional patches to the same branch09:23
pstolowskipedronis: hello, sample output of new timings to discuss - https://paste.ubuntu.com/p/gXrk8sBwwB/ - contains timings of some tasks, ifacemgr startup, snapmgr ensure loop (nb, do we really run ensure so often?). combines doing/undoing times from tasks09:23
zygapedronis: this is especially clear since the three patches starting with cmd/snap-confine: tweak ordering of fields in sc_invocation are added in response to your review09:24
mvozyga: oh, sorry. my bad then. maybe we can go back to the point in time (via a PR) that had the +1 from pedronis  and the "looks good" from me and then land those bits easily?09:25
ondrazyga hey09:25
ondrazyga wanna talk about those PR for gadget snaps?09:25
zygamvo: but the unclear aspect is what pedronis actually had reviewed09:26
ondrazyga unless you already had chat with pedronis09:26
zygaondra: hey, I asked about it yestereday09:26
pedroniszyga: I didn't review the init helper09:26
zygaondra: I don't know what I can do to help09:26
pedronismaybe it was stale09:26
pedroniswhatever09:26
ondrazyga yeah I was already off when I saw you message09:26
pedronisit needs a review from scratch from both of us09:26
ondrazyga nothing apart of +1 :D09:26
zygaondra: I don't fully understand the consequence of that, it is  something perdronis should look at first09:27
ondrazyga I think rest is on foundation09:27
ondrazyga yeah we already talked with him09:27
pedroniszyga: if I have too be honest I find snap-confine is starting to be too much split out in helpers, it's a maze to follow09:30
pedronisI'm sure they all make sense locally but if in a 2nd time you need to find out what's going on is a chase09:31
Chipacamborzecki: I pushed a tweak to the interfaces deprecation pr09:35
Chipacapedronis: ^09:35
pstolowskipedronis: let me know when/if you have a moment to discuss this09:35
mborzeckiChipaca: thanks!09:35
pedronispstolowski: we call ensure loop each 5 mins but also each time we need to run more task with EnsureBefore(0)09:36
mborzeckiChipaca: is fill() aware of a sequence '..' and will not break it?09:36
Chipacamborzecki: it is not09:36
Chipacamborzecki: ¯\_(ツ)_/¯09:37
ChipacaI mean, breaking it isn't ideal but isn't the end of the world either09:37
mborzeckiChipaca: fits unboken in my term so :)09:37
Chipacamborzecki: also breaks just right on 8009:38
mborzeckimhm09:38
pedronisChipaca: I don't understand how using fill helps09:38
pedronisit's going to take up vertical space anyway09:39
Chipacapedronis: your issue was with vertical space, not with improper word-splitting?09:39
pedronisyes09:39
mborzeckipedronis: https://paste.ubuntu.com/p/7qzSqPM4Zc/09:39
pstolowskiah, right, EnsureBefore(0)09:39
Chipacapedronis: but the deprecation is only shown on 'snap interfaces'09:40
pedronispstolowski: we really need to be careful with it09:40
Chipacapedronis: which is not concerned with vertical space09:40
pedronisChipaca: no, but is a table09:41
Chipacapedronis: so?09:41
mborzeckithe message goes to stderr09:41
pedronisI know09:42
pedroniswe are still eating 3 lines09:42
pedronisseems too much09:42
Chipacagrah09:43
pstolowskiChipaca: have you by an chance implemented our TabWriter?09:43
Chipacapstolowski: we don't have a TabWriter09:44
Chipacapstolowski: why?09:44
Chipacapstolowski: we do have a tabWriter, I think, that wraps TabWriter09:44
Chipacaas a helper function i mean09:44
Chipacanot as a type09:44
pedronisChipaca: 'snap interfaces' is deprecated and replaced by the 'snap connections' command.  is 7909:45
Chipacapedronis: in English09:45
pedronisChipaca: they we just hide it09:45
pstolowskiChipaca: ah, nvm, it's a standard go lib thing09:45
pedronisthne09:45
pedronisChipaca: then we just hide it09:45
Chipacapedronis: I don't understand why09:46
ChipacaI don't understand why 3 lines are too many, on a command that produces 121 lines of output by default09:46
pedronisChipaca: it doesn always produces 121 lines09:47
pedronisChipaca: consider snap interfaces gnome-logs09:48
Chipacapedronis: ok09:48
Chipacapedronis: so what's the issue09:48
pedronisChipaca: we started here  "The 'snap interfaces' command is deprecated, try the new 'snap connections'."09:52
Chipacapedronis: yes09:54
mborzeckii don't mind going back to the first version09:54
ChipacaWe could even go with09:55
Chipaca'snap interfaces' is deprecated; use 'snap connections'.09:55
Chipacathis incorporates all the feedback so far09:55
mborzeckiworks for me09:55
mborzeckipedronis: ^^ wdyt?09:55
mvoChipaca: +109:56
Chipacamborzecki: I'll push the change, plus adding the notice to the long help09:56
mvo(fwiw)09:56
mborzeckiChipaca: thank you!09:57
mvoI updated 6401 fwiw09:57
pedronisChipaca: the last version is very long, but it's all facts, it doesn't recommend anything09:58
pedronis(except implicitly)09:58
Chipacapedronis: the _last_ version? “'snap interfaces' is deprecated; use 'snap connections'.”?09:59
pedronisChipaca: the last version in the PR09:59
Chipacapedronis: you ok with the last one here? i think it covers all the issues we've come across so far09:59
pedronisChipaca: it's very terse10:00
pedronissorry, that's not the problem10:01
ChipacaI'd also add10:01
ChipacaNOTE this command is deprecated and has been replaced with the 'connections'10:01
Chipaca     command.10:01
Chipacato the longHelp10:01
pedronisthanks10:01
pedronisChipaca: have we goon too far the other way around though? is the new one too prompt?10:12
Chipacapedronis: nah, it's fine10:14
Chipacapedronis: adding 'please' and 'try' are both problematic for reasons degville explained in the pr10:14
pedronisChipaca: wondering if we want "the new" , issue with that is that at some point we would need to remove "new" because is untrue10:15
Chipacapedronis: I really think it's fine as is10:16
pedronisok10:16
mupPR snapd#6589 opened: daemon: support returning assertion information as JSON with the "json" query parameter <Created by pedronis> <https://github.com/snapcore/snapd/pull/6589>10:28
pedronisChipaca: ^  something for you when you have a bit of time10:29
* Chipaca looks at next year's calendar10:29
Chipacaok10:29
pedronisheh10:30
Chipaca:-)10:30
mupPR snapcraft#2499 closed: many: support for "base: core" in snapcraft.yaml <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2499>10:54
ogramvo, here is another core18 regression https://bugs.launchpad.net/snappy/+bug/181962910:56
mupBug #1819629: no default locale in core18 causes pam errors <Snappy:New> <https://launchpad.net/bugs/1819629>10:56
mupBug #1819629 opened: no default locale in core18 causes pam errors <Snappy:New> <https://launchpad.net/bugs/1819629>10:56
mvoogra: thanks - that sounds hopefully straightforward to fix, maybe sil2100  can give 1819629  a stab10:57
ograyeah, just some "echo C.UTF-8 >/etc/default/locale" somewhere would be enough10:59
ogra(in the build)10:59
sil2100Oh, indeed11:00
mvoogra, sil2100 yeah, the new build system has a "static" dir, we could simply drop static/etc/default/locale into the core18 tree and its fixed :)11:01
ograawesome11:01
ograsil2100, also https://forum.snapcraft.io/t/cant-find-the-spi-interface/7523 ... you might need to pull the latest upstream into the CanonicalLtd branch for the pi3 gadget SPI interface fix11:02
ograi wonder if we could put the snapcore/pi3-gadget tree to rest somehow witout breaking all the forks of it (not sure if github supports re-owning branches and keeps the references)11:03
ondrazyga what happens when I change base in snap between revisions, will snapd correctly run new revision agains different base?11:26
zygaondra: when all processes of that snap terminate, yes11:27
ondrazyga is there way to check what base it's working11:28
zygaondra: yes, sure, just nsenter and look11:28
=== alan_g_ is now known as alan_g
ondrazyga hmm for me refresh failed, because I think in post-refresh hook it collided on libc versio11:29
zygaondra: can you provide a reproducer?11:30
ondrazyga testing now, let me make sure I have it all right11:31
zygaondra: you can set SNAPD_DEBUG=1 and see what happens11:31
zygabut I don't know how to set that to see hook output11:31
zygaondra: there's a spread test for this feature if you want to see how it behaves11:32
ondrazyga I get hook error and that indicates there was libc collision, but let me validate clean install first11:32
zygahttps://github.com/snapcore/snapd/blob/master/tests/main/stale-base-snap/task.yaml11:33
cachiojamesh, hey11:33
cachiojamesh, yesterday I was working with a test error11:34
cachiojamon,11:34
cachiojamesh, the test desktop-portal-filechooser on snapsd11:34
cachiojamesh, https://paste.ubuntu.com/p/wMhG5vdyzK/11:34
cachiothe test just fails like this on ubuntu 18.0411:35
ondrazyga OK so install opengrok from stable, then try to refresh to edge11:35
cachiothe error itself is that the snap can't write in the mount dir because of lack of permissions11:36
cachiojamesh, any idea if this has been already seen/reported?11:36
ondrazyga stable is with core16, edge it base core18, there is libpthread library which depends on libc version, this is used in post-refresh hook, which fails11:37
cachiojamesh, in ubuntu 18.10 works fine11:37
ondrazyga clean install from edge works11:37
ondrazyga so only difference I can think og11:37
zygaondra: perhaps something was still running?11:39
zygait's interesting11:39
zygathat post  refresh hook can run with old libc11:39
zygaI mean11:39
zygait's possible to craft this11:39
zygaso that it will happen as you described11:39
zygaperhaps snapd should disallow base changes that don't discard the mount namespace11:39
zygapedronis: ^11:40
ondrazyga so post-refresh runs with previous base?11:40
zygaondra: please report this11:40
zygaondra: yes, it is possible that this happens11:40
zygaondra: when an app is still active11:40
zygaondra: or perhaps hooks don't depend on their teremination and  we start post refresh hook while  another hook is running11:40
ondrazyga doesn't it stop all services before refresh?11:40
zygaondra: it does, but there are hooks and apps11:40
zygathose can run longer11:41
zygaand there are enduring services11:41
zygait warrants a bug11:41
zygathis is funny actually11:41
ondrazyga there should not be any app running, so just hooks11:41
zygabecause it means we cannot correctly refresh in some cases11:41
zygaondra: perhaps more than one bug  then (base awareness across refresh and hook ordering)11:41
ondrazyga have you managed to reproduce it?11:41
zygano11:41
zygaI have not tried11:42
zygaI just explained how it is 100% possible to do that11:42
ondrazyga right :)11:42
zygaondra: curious, what was the base change?11:42
zygacore -> core1811:42
zygaor back?11:42
ondrazyga core->core1811:44
ondrazyga a bit related, what is correct base in snap.yaml for core16? core16 or core?11:46
zygaondra: and is libc incompatible across that hop?11:51
ondrazyga I'm using custom libpthread which I ship in snap, so it's missing things from libc11:52
zygaahh11:54
ondrazyga this is error I'm getting mkdir: relocation error: /snap/opengrok/34/lib/x86_64-linux-gnu/libpthread.so.0: symbol __tunable_get_val, version GLIBC_PRIVATE not defined in file ld-linux-x86-64.so.2 with link time reference11:55
zygaondra: please report a bug, after an errand later today I will write a test that reproduces thiis11:59
zygaondra: it's unfortunate because it's a design omission11:59
ondrazyga sure I will file bug for it12:00
zygathank you for another interesting case :-)12:00
ondrazyga you are welcome :)12:01
pedroniszyga: we always run at most one hook per single snap12:11
pedronisat a time12:11
zygapedronis: and we consider the hook "done" when the initial process exits12:12
pedroniszyga: ?12:12
zygapedronis: we probably can craft a hook that leaves a background process behind12:12
pedronisprobably12:12
pedronisis that the case here though?12:12
mupPR snapd#6562 closed: timings: base API for recording timings in state <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/6562>12:13
zygano, I don't think so, unless that was accidentally what had occurred12:13
zygabut regardless of what happened here the issue of running a revision that clearly demands base snap  X with the stale base snap Y needs addressing12:13
pedronisyes12:13
pedronisshouldn't stale detection find that out?12:13
pedronisdifferent base, different device?12:14
zygait is different12:14
zygaI bet it's not changed because the namespace is still used12:14
zygahowerver here I'd argue that different base snap name should be detected12:14
zygabut we have no logic to recover base snap name from the mount namespace12:14
zyga(or if it can be done, in general, reliably, apart from parsing path names)12:15
pedronispstolowski: the doc comments in the branch you merged still say Timing a lot12:20
pedronisinstead of Span12:20
pedronisunless I'm confused12:20
pstolowskipedronis: uhm you're right, sorry.. i'll address in a followup, this doc will be updated anyway with new helpers12:22
pedronispstolowski: yes, fine for a follow up12:22
pedronisChipaca: the failure on the deprecate interface PR is real, something going with xgettext-go12:26
pedronisand the warning12:26
pedronispanic: unknown type: interfacesDeprecationNotice12:26
* Chipaca kills all tests12:27
Chipacapedronis: I'll fix12:27
Chipacaafter lunch tho12:27
pedronis:)12:27
Chipacaniemeyer: https://pbs.twimg.com/media/D1dQcvqXcAAaQKs?format=jpg&name=large12:29
Chipacasince you were asking about this yesterday12:30
cachiomvo, is it ok to move 2.37.4 to stable right?12:30
niemeyerChipaca: There we go.. :)12:30
mborzeckianyone up for a review on #6485 ?12:30
mupPR #6485: interfaces/seccomp: regenerate changed profiles only <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6485>12:30
pedronismborzecki: it has grown quite a lot12:41
zygamborzecki: I can enqueue that for later today12:41
zygaI need to leave in ~15 minutes12:42
mborzeckithanks!12:42
zygamborzecki: enqueued :)12:42
pedronismborzecki: it would be easier to review if the new package added was its own PR12:44
mborzeckipedronis: i can split it12:45
pedronismborzecki: if it's not too much painful, I would prefer, it would go faster on the review side that way12:45
* zyga goes to the doctor 12:46
=== ricab is now known as ricab|lunch
pedroniscachio: let's chat about 2.37.4 in the standup12:50
cachiopedronis, ok12:51
mborzeckiChipaca: https://github.com/snapcore/snapd/pull/6556#issuecomment-471990121 could that be because of ; in the message?13:02
mupPR #6556: cmd/snap: hide 'interfaces' command, show deprecation notice <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6556>13:02
Chipacamborzecki: no, we use ; elsewhere13:02
Chipacamborzecki: it's probably the i18n.G() of const13:02
=== nessita_ is now known as nessita
Chipacachecking now13:03
mborzeckioff to pick up the kids13:03
Chipacahow13:04
Chipacahow does update-pot work any more13:04
dot-tobiasogra / mvo: I'm trying to rebase my fork of ogra's kiosk gadget snap (https://github.com/ogra1/pi-kiosk-gadget) onto the core18-related changes of the “universal Pi gadget snap” (https://github.com/snapcore/pi-gadget). Building the core18 gadget works fine, but my Pi 3B does not boot at all … green LED flickers shortly and then dies, no HDMI output whatsoever. I tried to selectively apply changes from both repos from the point where13:04
dot-tobias they diverted (commit 013c2931230a4b4de419080f8499fca27c51727d), but no success. Do you know if the current revision of the universal Pi gadget works?13:04
Chipaca'go install' now installs binaries in ~/bin/13:04
Chipaca:-|13:04
ogradot-tobias, got a link to your current code ?13:04
Chipacaoh wait, no, i have GOBIN set for some reason13:05
Chipacahrmm13:05
ograarent you in england ? shouldnt that be GOWASTEBASKET instead ? :P13:05
Chipacaogra: https://en.oxforddictionaries.com/definition/bin13:06
Chipacaogra: 'rubbish bin' is british (vs 'trash')13:07
ograoops13:07
Chipacaogra: bloody europeans, coming over here, stealing our language13:07
ogralol13:08
dot-tobiasogra: https://gitlab.com/glancr/gadget-snap-pi-kiosk/ -> master builds fine with LXD container without base (though the attempt to feed mir-kiosk the whole config file does not validate in ubuntu-image); branch core18-WIP has the core18 changes in snapcraft.yaml: https://gitlab.com/glancr/gadget-snap-pi-kiosk/commit/d91cc2386af0da24a8942e52053469f4b920ec7b (other files can be ignored)13:11
ogradot-tobias, the linux-modules package contains dtb files ?!?13:13
ogra(i highly doubt that)13:14
ograis that a change made by you or did you copy it from the universal branch ?13:14
dot-tobiasogra: Got that from the snapcore/pi-gadget upstream, see https://github.com/snapcore/pi-gadget/blame/988ee427691177de5cee84370b096be3c6a07951/snapcraft.yaml#L8913:15
dot-tobiasbut that would indeed explain why it's not booting … (I have close to zero knowledge about this stuff, so apologies and thank you for beginner explanations  in advance 😊 )13:16
ogradot-tobias, ok, i checked, devicetrees are in that package, so this is fine13:18
ograo dont see anything else significant that could prevent booting apart from the fact that you use the distro compiler, but that should be v7 or newer anyway in bionic13:20
ogras/o/i/13:20
ograhow does your prime folder look like after build ?13:21
ograyou should fine the RPi bootloader blobs in there as well as uboot2.img and uboot3.img13:21
dot-tobiasre: compiler: yeah, that's what I gathered from https://github.com/snapcore/pi-gadget/pull/913:21
mupPR pi-gadget#9: RFC: use ubuntu cross gcc to build uboot <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/pi-gadget/pull/9>13:21
dot-tobiaslet me check13:21
ograactually in prime/boot-assets/13:22
ogra$ ls ../../pi3/pi3-gadget/prime/boot-assets/13:23
ograbcm2709-rpi-2-b.dtb  bcm2710-rpi-cm3.dtb  cmdline.txt  COPYING.linux  fixup.dat     fixup_x.dat       overlays     start_cd.elf  start.elf    uboot.bin13:23
ograbcm2710-rpi-3-b.dtb  bootcode.bin         config.txt   fixup_cd.dat   fixup_db.dat  LICENCE.broadcom  psplash.img  start_db.elf  start_x.elf13:23
ograthast what you want to see13:23
ogra*that's13:23
dot-tobiasOk, thanks. Rebuilding the snap just to be sure, BRB13:23
dot-tobiasogra: Side-note – Do you happen to know how I can feed a multiline file to a “defaults” entry in gadget.yaml? I'm trying to accomplish setting mir-kiosk's display config file through the device hook (see https://forum.snapcraft.io/t/prepare-device-hook-questions/9626/5?u=tobias , current attempt at https://gitlab.com/glancr/gadget-snap-pi-kiosk/blob/master/gadget.yaml#L12)13:26
Chipacadot-tobias: > will mangle things for you13:27
Chipacadot-tobias: also the quotes are spurious13:27
Chipacadot-tobias: paste your yaml into http://yaml-online-parser.appspot.com to see what works :-)13:27
Chipacadot-tobias: note these are comments about the yaml itself, I don't know if what you're trying to do should work :-)13:29
ograi'm also not sure if the mir team has even tested this13:29
ograprobably ask in #mir-server13:29
dot-tobiasI tried with a pipe before and the parser complained while building the snap, but maybe I did something else wrong. The online parser shows valid JSON with \n linebreaks at least, will test with ubuntu-image 😊 Yeah, but having a valid yaml result is at least one step closer to the goal 😄 Thank you!13:30
mvocachio: 2.37.4 stable> yes - I see no reason why not13:32
dot-tobiasogra: Snap build fore core18 version is complete, here's the boot-assets folder:13:33
dot-tobias➜ ls boot-assets/13:34
dot-tobiasbcm2708-rpi-0-w.dtb     bcm2709-rpi-2-b.dtb       bcm2835-rpi-a.dtb       bcm2835-rpi-b-rev2.dtb  bcm2837-rpi-3-b.dtb  COPYING.linux  fixup_x.dat       start_cd.elf  uboot2.bin13:34
dot-tobiasbcm2708-rpi-b.dtb       bcm2710-rpi-3-b.dtb       bcm2835-rpi-a-plus.dtb  bcm2835-rpi-zero.dtb    bootcode.bin         fixup_cd.dat   LICENCE.broadcom  start_db.elf  uboot3.bin13:34
dot-tobiasbcm2708-rpi-b-plus.dtb  bcm2710-rpi-3-b-plus.dtb  bcm2835-rpi-b.dtb       bcm2835-rpi-zero-w.dtb  cmdline.txt          fixup.dat      overlays/         start.elf13:34
dot-tobiasbcm2708-rpi-cm.dtb      bcm2710-rpi-cm3.dtb       bcm2835-rpi-b-plus.dtb  bcm2836-rpi-2-b.dtb     config.txt           fixup_db.dat   psplash.img       start_x.elf13:34
ogradot-tobias, you are missing the files from the config dir (config.txt and cmdline.txt)13:34
ograoh, no, i'm just blind13:34
zygamvo: standup update: I’m working on splitting the big refactoring PR; going well and I have several patches that can be proposed but I’m waiting till the whole complete “split” branch is functioning. Apart from that I briefly interacted and tested MX Linux where there is some desire to run snapd. I will try one more time with init system set to systemd. I plan to re-review Maciej’s seccomp optimization PR.13:35
mvozyga:13:36
zygaAnd as I shared I’m at a doctor undergoing small surgery (all is good, no limbs lost)13:36
dot-tobiasogra: I don't see uboot{3}.img however, or did you mean uboot.bin?13:36
mvozyga: uh get well!13:36
zygaNo no, all is good, nothing to worry about13:36
ogradot-tobias, yeah13:36
ograif this same stuff ends up properly in the system-boot partition of your image i dont really know what to say ... this should definitely boot13:37
ogrado you see these files in the toplevel of the boot partition if you plug the SD into your desktop ?13:37
mvoChipaca: "there are files left in the git tree after the tests:" ?? cmd/snap-seccomp/... you talked aobut this before, didn't you?13:40
Chipacamvo: where are you getting this?13:41
mvoChipaca: at the end of a unit test spread run13:41
mvoChipaca: I thought I saw you talking about something similar earlier13:41
mvoChipaca: did I misremember?13:41
Chipacamvo: not today, not for ages13:41
mvoChipaca: ok, then please ignore me13:42
Chipacamvo: 'git status' should list things13:42
mvoChipaca: yeah, it happend on spread13:42
mvoChipaca: maybe it was a hickup, no worries13:42
zygapedronis: about that branch from this morning. I can split it exactly where it was approved before13:43
ondrazyga so I can only reproduce it on one machine, on other machines when I do clean install and then refresh it just works13:43
zygaondra: very interesting13:43
zygaIs one machine slower?13:43
ondrazyga very likely much slower13:43
zygapedronis: I didn’t mean to introduce bumps into the review process13:43
ondrazyga I can try to repro on other slow machine13:44
zygaondra: can you please tell me more about the hooks in play13:44
zygaWhat kind of hooks are used13:44
zygaAnd how are the hooks implemented13:44
ondrazyga https://github.com/kubiko/opengrok-snap/blob/master/snap/hooks/install13:45
ondrazyga install and post-refresh are same13:45
zygaondra: it’s hard for me to look now (I only have my phone and cannot move)13:45
zygaSo please walk me through this13:45
ondrazyga nothing special there, couple of cp and mkdir and then snapctl get and snapctl set13:46
ondranothing else13:46
zygaAh13:46
zygaHmmm13:46
zygaAnything using &?13:46
zyga(Shell job control and stuff)13:46
ondrazyga nope13:47
ondrazyga all running in straight line13:47
zygaSo there are install and post-refresh only, right?13:47
ondrazyga also error is from first line of that hook13:47
zygaAre there any services?13:47
zygaPerhaps we don’t wait enough for service shutdown13:47
zygaWe now kill just the main process, right?13:48
ondrazyga there is configure which does nothing13:48
zygaInside services13:48
ondrazyga yes there is service13:48
zyga(Or am I mistaken?)13:48
ondrazyga I have stopped service with systemctl and it still happened13:48
zygaAha13:48
zygaThat is very useful data13:49
zygaCan you reproduce it on the slow machine if you remove the service from snap yaml?13:49
ondrazyga there is one time activated service and tomcat, I stopped both and same thing13:49
zygaI wonder if you can reduce this to just the hooks13:50
zygaOr if services play a role13:50
ondrazyga but if I remove service it will be new revision, so would that make difference as service from new snap should not be running before post-refresh hook, or am I missing sometning?13:55
ondrazyga so I cannot repro on another slow machine with clean istall13:55
ondrazyga BTW unrelated bug: ERROR cannot discard snap namespace "opengrok", will retry in 3 mins: cannot discard preserved namespace of snap "opengrok": cannot unlink opengrok.mnt: Device or resource busy13:58
ondrazyga not able to remove snap which was installed with try13:58
ondrazyga Remove security profile for snap "opengrok" (x4) (cannot find installed snap "opengrok" at revision x4: missing file /snap/opengrok/x4/meta/snap.yaml)13:58
ondrazyga but /snap/opengrok is empty dir, so something out of sync13:59
jameshcachio: was out an event earlier.  I haven't seen that error before.  It looks like it is coming from the xdg-document-portal FUSE file system though14:01
=== epod is now known as luk3yx
degvillemvo: I'm having trouble connecting to the stand up! I'll keep trying (I'm in London)14:05
ondrazyga removing service made no difference14:05
jameshcachio: I suspect the ENOSYS is this one: https://github.com/flatpak/xdg-desktop-portal/blob/master/document-portal/document-portal-fuse.c#L730 -- but I'm not sure why the test would trigger that code path: the test should be running with a clean document portal DB14:06
dot-tobiasogra: So I rebuilt the core18 gadget from scratch, added “base: 18” to my model assertion and dd'd the image to an SD card. All files show up in the root folder, but there's an additional folder “pi2-kernel_83.snap” which I didn't notice before. Contains additional dtbs. And unfortunately, the Pi still won't boot 😞 HDMI output turns the screen on, but nothing visible and green LED doesn't blink once. IIRC that means “no no” …14:06
zygaondra: excellent14:07
mupPR snapd#6556 closed: cmd/snap: hide 'interfaces' command, show deprecation notice <Created by bboozzoo> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/6556>14:07
zygaondra: please report the try issue as well14:07
ondrazyga but as I said, this was service in snap to be installed, so it'd not affect already installed snap14:07
zygaI’m happy that the hook is sufficient to reproduce14:08
zygaAh14:08
zygaDid you try removing the service from both revisions?14:08
ogradot-tobias, anything on serial (i forgot if u-boot actually prints to the display or serial only)14:08
dot-tobiasogra: Bummed to say that I don't really know (or even have the necessary hardware?) how to do that. Will read up a bit on that and get back to you. Thank you!14:09
=== Kamilion|ZNC is now known as Kamilion
=== aleksander_ is now known as aleksander
cachiojamesh, I suppose it is something not being cleaned up corrently in that case14:10
ogradot-tobias, https://www.amazon.de/SainSmart-USB-TTL-Console-Raspberry/dp/B00KVUSI30 you want something like this14:10
cachiojamesh, it is weird because the package is installed/uninstall as part of the test14:11
jameshcachio: I used to have some paranoid clean up in the prepare for these tests, but was asked to remove it and trust other tests to leave things in a pristine state14:11
mvodegville: thanks for letting me know14:11
* dot-tobias tips hat to ogra14:11
jameshcachio: I suspect it is some user-level configuration rather than something that would be affected by package install/uninstall14:12
cachiojamesh, it is weird that I can't reproduce that error on ubuntu 18.1014:14
cachiowith the same code14:14
=== ricab|lunch is now known as ricab
jameshcachio: yeah.  We've got 1.0.3 on both 18.04 and 18.1014:15
jameshcachio: scratch that.  On bionic 1.0.3 is still waiting in proposed14:16
cachiojamesh, mmm, I'll try to test with 1.0.3 on bionic to see it that fix the issue14:17
cachiojamesh, I'll let you know the results}14:17
jameshcachio: we definitely had problems when Cosmic had xdg-desktop-portal 1.0.2, which were fixed by 1.0.3.  Bionic seemed fine with the older 0.11, but we've been trying to get 1.0.3 rolled out to all the old releases.14:18
jameshIt wouldn't surprise me if there is some other corner case in the older version that I didn't hit when testing14:19
ondrazyga and when I return 0 as result of the hook, then snapd is tricked and refresh works14:23
zygaondra: well, that's expected14:23
ondrazyga though of course there are all the errors there14:23
zygathe beauty(*) of  shell14:23
ondrazyga yep14:23
ondrazyga so I have only one machine I'm able to reproduce this one14:24
ondrazyga ha, was did you say was trick to check what core I'm running against if I can snap run --shell14:26
zygaondra: it's easier to use nsenter14:26
zygaondra: nsenter -m/run/snapd/ns/foo.mnt14:26
zygathen see what / is14:26
ondrazyga nsenter: neither filename nor target pid supplied for ns/mnt14:27
zyga-marg, not -m ar14:27
ondrazyga because even now installed, it still seems to run with wrong base14:28
zyganesenter cli parsing is very strict14:28
ondrazyga nsenter: reassociate to namespace 'ns/mnt' failed: Invalid argument14:29
zygawhat is the command you ran exactly?14:29
ondrazyga when running nsenter -m/run/snapd/ns/opengrok.mnt14:29
zygasudo?14:29
zygaactually14:29
zygano14:29
ondrazyga same with sudo14:29
zygaEINVAL means it's not mounted anymore14:29
zygathat's ... odd14:29
zygawe used to unmount but keep the file14:29
zygabut recently we always unlink it for clarity14:29
zygaondra: note that snap-confine may not save a new mount namespace if construction fails14:31
zygaondra: and may discard a mount namespace when it is stale14:31
zygaondra: but that should not happen here (construction should not fail)14:32
ondrazyga so I still get into that namespace despite the error14:33
ondrazyga and it's indeed using core16 base14:33
zygaondra: uh?14:34
zygathe erorr is ... od14:34
zygaeither setns worked or it did not work14:34
zygaondra: I'm at risk of getting lost here, can you please collect this information in the bug report14:35
ondrazyga https://paste.ubuntu.com/p/99Pz3wQ79P/14:35
zygaondra: I think the bug may be separate from the core -> core18 bug14:35
zygaondra: that is, there is something wonky with hook dependency (CC pstolowski)14:35
ondrazyga on machine where it works I get: https://paste.ubuntu.com/p/jhCTxk7mwH/14:35
zygaondra: that nsenter looks ok14:36
zygano EINVAL anymore14:36
ondrazyga see the difference in library version14:36
zyga2.23?14:36
ondrazyga yep, that is wrong glibc14:36
ondrazyga should be 2.2714:36
zygaondra: please refresh my memory,  core16 has 2.23 and core18 has 2.27?14:36
zygaondra: can you run findmnt and tell me what / is please?14:37
ondrazyga correct14:37
zygaondra: so, one observation, it would be neat to always have logging in snap-confine and log that to syslog or something14:37
zygaondra: this way we would know what happened for sure14:37
ondrazyga /                                              /dev/loop014:37
zygalosetup  -l?14:37
zygaoh14:38
zygaone sec14:38
zygaso14:38
ondrazyga /dev/loop0         0      0         1  1 /var/lib/snapd/snaps/core_6130.snap (deleted)14:38
zygaSNAP_CONFINE_DEBUG=yes snap run --shell ...14:38
zygaoh?14:38
zygadeleted is certainly interesting14:38
zyga(the plot thickens)14:38
zygaondra: that will now tell you what snap-confine detected14:38
zygait should tell you that the mount namespace is stale but occupied14:39
ondrazyga on other machine it looks correct14:39
zygais that snap really deleted on the fs?14:39
ondrazyga already seeing loop0 indicates something is hanged :)14:39
zygadeleted is very nasty :/14:39
zygawait, this is core!14:40
zygaright?14:40
zygaooooh14:40
zygaman I know14:40
zygaso14:40
zygawe have a bug14:40
* zyga slows down to think 14:40
ondrazyga /var/lib/snapd/snaps/core_6130.snap does not exist at all14:40
zygaondra: specifically this is ubuntu-core 16 right?14:40
zygaa core system14:40
ondrazyga classic14:40
zygaaha14:41
zygain that case it's back to regularly interestngi14:41
ondrazyga 18.0414:41
zygaI suspected there  are bugs in core->core18 sans reboot refreshes14:41
zygabut let's think14:41
zygado you have snap changes that indicate something happening to revision 6130?14:41
zygaI suspect it was just garbage collected14:42
ondrazyga yeah nothing in changes14:42
zygaok14:42
zygaSNAP_CONFINE_DEBUG=yes snap run --shell ...14:43
zygawhat does that say?14:43
zyga(use the  real snap name there)14:43
zygaondra: (suspense music plays)14:44
ondrazyga https://paste.ubuntu.com/p/7w6nRX4Y4J/14:45
zygaDEBUG: sending information about the state of the mount namespace (discard)14:45
cachiojamesh, same error with 1.0.314:45
zygaDEBUG: the mount namespace is stale and should be discarded14:45
cachiojamesh, I have a debug session open, do you want to take a look?14:45
zygawhen you do this you must  keep something in there running14:45
zyganow you should see core18 /14:46
zygaondra: as I said, when the error happens there are still some processes lingering14:46
zygaondra: so snap-confine knows it's supposed to discard but chooses not to14:46
zygaondra: can you confirm that / is now core18?14:47
ondrazyga no / is core16 still in that name space14:47
zygaondra: DEBUG: found process 6540 belonging to user 014:48
zygaI missed that14:48
zygawhat is that process14:48
ondrazyga funny ps -aux does not show anything running from old revision14:49
zygaondra: coin on the edge14:49
zygaondra: it's a thread14:49
zygacan you find that in /proc please?14:49
zygaondra: a bit of go thread is running and it inhabits that namespace somehow (wild guess)14:49
ondrazyga I assume reboot will fix this as whatever is hanging will die, that stale core revision seems pretty old14:51
zygaondra: don't reboot14:51
zygaondra: find out what process 6540 is14:51
zygawhat's /proc/6540/exe ?14:51
zygaondra: inspect it from the outside please)14:52
ondrazyga I refreshed back to base core18 snap, debug log was from revision running against core16 and that was functioning14:53
zygaondra: can you reproduce this enough to see the dangling process and find out what it was please?14:53
zygaondra: you can look at /sys/fs/cgroup/freezer/snap.$SNAP_NAME/cgroup.procs for the list of inhabitants14:54
zygaondra: (to avoid using snap-confine)14:54
ondrazyga now same on broken revision, process id I see from snap confine is ssh-agent14:54
zygaoh14:55
zygahow did that get there?14:55
pedronisChipaca: thanks for the review14:55
ondrazyga snap is running ssh-agent14:55
zygaondra: so there's a ssh-agent running in that mount namespace14:55
zygaondra: and that is a "service" (but not)14:55
zygaondra: who starts it?14:55
ondrazyga it's forked14:55
zygais that a service / app in the snap>?14:55
ondrazyga service will check if it's running and starts it14:56
zygathe service that is a part of the snap?14:56
ondrazyga I suppose I can add it as service14:56
zygaondra: if you forgete refreshes for a second14:56
zygaif you stop the service who started i14:56
zygadoes it stop ssh-agent?14:56
zygaor is that a process that is not stopped across restart (effectively)14:56
ondrazyga no it will not stop it when you stop service14:56
zygaondra: so that's that14:56
zygaondra: it's a feature14:56
zygaondra: we don't discard the mount namespace when there are apps or hooks running that would then observe old/new fs together with other processes in that snap14:57
ondrazyga shall I kill the process and test refresh?14:57
zygaondra: refresh-app-awareness would refuse to refresh your snap14:57
zygaondra: please14:57
zygaondra: we do have a bug14:57
zygaondra: about core / core1814:57
ondrazyga not yet14:57
zygaor in general where base snap name changes14:57
zygathat should behave in a different (yet undesigned way)14:58
mupPR # closed: snapd#5644, snapd#5822, snapd#5915, snapd#6098, snapd#6108, snapd#6177, snapd#6238, snapd#6258, snapd#6270, snapd#6325, snapd#6327, snapd#6329, snapd#6341, snapd#6347, snapd#6360, snapd#6367, snapd#6401, snapd#6404, snapd#6410, snapd#6418, snapd#6436, snapd#6485, snapd#6491,14:58
mupsnapd#6502, snapd#6541, snapd#6553, snapd#6559, snapd#6564, snapd#6575, snapd#6577, snapd#6583, snapd#6585, snapd#6588, snapd#658914:58
ondrazyga lol different error cannot unlink opengrok.mnt: Device or resource busy14:59
zygaondra: uname -r?14:59
zygaondra: that's a known kernel behavior on old (3.10) kernels14:59
mupPR # opened: snapd#5644, snapd#5822, snapd#5915, snapd#6098, snapd#6108, snapd#6177, snapd#6238, snapd#6258, snapd#6270, snapd#6325, snapd#6327, snapd#6329, snapd#6341, snapd#6347, snapd#6360, snapd#6367, snapd#6401, snapd#6404, snapd#6410, snapd#6418, snapd#6436, snapd#6485, snapd#6491,14:59
mupsnapd#6502, snapd#6541, snapd#6553, snapd#6559, snapd#6564, snapd#6575, snapd#6577, snapd#6583, snapd#6585, snapd#6588, snapd#658914:59
ondrazyga I'm on 4.1515:00
zygaondra: that's new then :)15:00
zygaondra: new and not fun15:00
zygaondra: can you run SNAPD_DEBUG=1  snap-discard-ns15:00
zygawith the snap name15:00
zygawell15:00
zygaspecifically15:00
zygaunlink is expected to fail15:00
zygabut we should have unmounted it before15:01
zygarun stat on that file15:01
zygaand stat -f please15:01
zygaperhaps before you discard it15:01
ondrazyga but since I killed that process I'm now running core1815:01
zygato see what's currently there15:01
ondrazyga nothing with stat -f15:03
zyganothing as in?15:03
ondrazyga https://paste.ubuntu.com/p/7DmG45TYnz/15:06
zyga    ID: 0        Namelen: 255     Type: nsfs15:06
zygathis is relevant15:07
zygait's a mounted namespace15:07
zygaso it cannot be unlinked15:07
zygathe question is: why did  snap-discard-ns not unmount it>15:07
ondrazyga so I will redo snap to run ssh-agent as service, I guess this should then fix it15:07
zygawhich version of snapd are you on?15:07
ondrazyga 2.37.215:08
zygaI forgot when snap-confine started  using snap-discard-ns but I suspect it's been before than that15:09
zygawhat happens if you want to discard the mount namespace and use SNAPD_DEBUG=1 SNAP_CONFINE_DEBUG=yes snap-discard-ns?15:09
zyga(note: make sure to use the right binary, reexec wise)15:10
ondrazyga where do I get snap-discard-ns15:11
zygaondra: it's right next to snap-confine15:11
zygaeither in /usr/lib/snapd or in the core snap in the same path15:11
ondrazyga https://paste.ubuntu.com/p/fGPY9WNRrp/15:12
zygaondra: what's the version of snapd on the hostt?15:12
zygawoah15:12
zygathat's neat15:12
mupPR snapd#6590 closed: daemon/api: filter connections with hotplug-gone=true <Created by stolowski> <https://github.com/snapcore/snapd/pull/6590>15:12
zygaso it unmounted it, supposedly without erorrs15:12
ondrazyga 2.37.215:12
zygaand then it ... failed to unlink it because it is still mounted15:13
zygacan you re-run15:13
zygawith strace  please?15:13
zyga(ditch the debug options)15:13
zygaand report this as a new bug15:13
zygait's a weird kernel behavior, unless we're missing something15:13
* zyga cannot wait for the strace15:15
ondrazyga https://paste.ubuntu.com/p/SkBMzTPpHX/15:15
ondrazyga so you want bug with which exactly? :)15:15
ondrazyga I will paste those longs in, jut to know how to call it15:15
zygawoah15:15
zygaI see15:15
zygafstatfs(5, {f_type=TMPFS_MAGIC, f_bsize=4096, f_blocks=255810, f_bfree=255557, f_bavail=255557, f_files=1279048, f_ffree=1278375, f_fsid={val=[0, 0]}, f_namelen=255, f_frsize=4096, f_flags=ST_VALID|ST_NOSUID|ST_NOEXEC|ST_RELATIME}) = 015:15
zygaso...15:16
zygafindmnt?15:16
zygait looks like a kernel bug15:16
zygawe look at the .mnt file, see it's a TMPFS (not nsfs), try to unlink it and hit a EBUSY error15:17
zygacan you repeat the stat -f call on the file agani15:17
zygayou reported it was nsfs before15:17
zygais it still?15:17
mupPR core18#119 opened: Add a default locale <Created by sil2100> <https://github.com/snapcore/core18/pull/119>15:18
zygaondra: ?15:20
* zyga is dying from suspense15:20
mupPR snapd#6590 opened: daemon/api: filter connections with hotplug-gone=true <Created by stolowski> <https://github.com/snapcore/snapd/pull/6590>15:20
ondrazyga yeah now it's tmpfs15:22
zygaondra: findmnt15:22
zygais it a bind mount?15:22
zygaor /proc/self/mountinfo if you fancy that instead15:23
ondrazyga findmnt in the namespace?15:23
zygaoutside, all of discard should be done outside15:23
zygainside that _IS_ expected to happen15:23
zyga(AFAIK)15:23
ondrazyga https://paste.ubuntu.com/p/4S3VJyJJCv/15:23
zyga│   └─/run/snapd/ns/opengrok.mnt      nsfs[mnt:[4026532246]] nsfs       rw15:24
zygaoutside it is mounted15:24
zygawere you running discard from within the mount namespace by any chance?15:24
ondrano from outside15:24
zygaand that strace where it showed to be a tmpfs, that was outside as well?15:24
ondrayes15:25
zygaondra: please report this15:25
ondraall from outside15:25
zygaondra: one bug for base core -> core18 design change on running processes15:25
zygaondra: one bug on discard that we just talked about15:26
zygaondra: I think there are no other things to report at this time, do you agree?15:26
ondrazyga agree15:26
ondrazyga I will do bugs tonight, now meetings15:26
zygaondra: *thank you*15:26
zygathis is super valuable15:27
* zyga hugs ondra 15:27
pstolowskizyga: sorry, i saw you ping but haven't followed the long discussion you had with ondra, is there anything i should look at re hooks?15:27
zygapstolowski: no, it's all clear now15:27
zygathere was a hidden app running15:27
zygaall is good15:27
* zyga heads home15:28
zygaafk for some time15:28
pstolowskiok15:28
pedroniszyga: I'm not sure that PR needs to be resplit but I made some comments there15:29
ondrazyga you are welcome and thank you!  this was intense :D15:29
cachiomvo, we have core 2.37.4 on stable now15:36
cachiopedronis, ~15:36
pedronisthx15:36
mvocachio: thank you!15:37
* cachio lunch15:39
=== cjwatson_ is now known as cjwatson
mupPR core18#120 opened: Backport wpa_supplicant.service.d/snap.conf from core <Created by sil2100> <https://github.com/snapcore/core18/pull/120>15:48
mupPR core18#119 closed: Add a default locale <Created by sil2100> <Merged by sil2100> <https://github.com/snapcore/core18/pull/119>15:50
mvosil2100: thanks!15:50
sil2100mvo: yw! The locale one was very trivial so I just ekhm, self-merged it15:51
sil2100We'll make sure it goes out with the nearest snap15:51
mvoxnox: do you mind if I do a systemd SRU? with the timedatectl fix and the new 1819728 fix?15:52
mvosil2100: thank you!15:52
xnoxmvo, go go go =)15:52
xnoxmvo, but also if mark files a proposed regression bug report, it will be on you to revert ;-)15:53
mvoxnox: cool, thank you15:53
mvoxnox: sure, its perfectly safe ;)15:53
mvoxnox: already in the upstream systemd etc15:53
xnoxyeah yeah, ddstreet thought so too =)15:54
mvo(since 1y almost)15:54
xnoxyet got caught up by missing pieces of things =)))))15:54
xnoxmvo, most of them do go through fine.15:54
mvoxnox: heh - thats fine, I need to prepare the details and then I will show you the final debdiff15:55
mvoxnox: so tomorrow15:55
mvoxnox: still thanks for the green light15:56
* zyga is home16:06
mupPR snapd#6591 opened: [RFC] managers: basic measurements <Created by stolowski> <https://github.com/snapcore/snapd/pull/6591>16:17
=== devil is now known as Guest10579
mupPR snapcraft#2498 closed: python plugin: graceful ret when no packages set <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2498>16:22
=== pstolowski is now known as pstolowski|afk
jdstrandpedronis: hey, just for my own prioritizing, when are you shooting for a 2.38 upload to disco?18:36
jdstrandmvo: hey, maybe that is a question for you: just for my own prioritizing, when are you18:39
jdstrandshooting for a 2.38 upload to disco?18:39
mupPR snapcraft#2500 opened: DRAFT: Add remote build <Created by cmatsuoka> <https://github.com/snapcore/snapcraft/pull/2500>18:41
mvojdstrand: probably end of this week, why? anything pending?18:42
jdstrandmvo: nothing for you. I can't upload apparmor 2.13 without 2.38 is all18:43
jdstrand(2.13 will break snap removes with system where apparmor is enabled)18:43
mvojdstrand: ok18:47
* cachio afk19:04
mupPR snapcraft#2501 opened: nodejs pluging: support for type str bin entries <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2501>19:17
=== Eleventh_Doctor is now known as Pharaoh_Atem
mupPR snapcraft#2496 closed: many: support the use of build-aux/snap <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2496>19:26
Pharaoh_AtemI was hoping that 2.38 would have the selinux stuff :(19:26
popeyjdstrand:  is it possible personal-files could grow exec to go with read and write?20:50
popeyjdstrand: i have an app which uses a go library called byteexec which writes go byte arrays as executables in ~/.byteexec, but fails for me because while it can write, it can't exec20:50
jdstrandpopey: it isn't really meant for that and that could easily lead to exec transition conflicts. why can't it write to SNAP_USER_DATA (which is $HOME to the snap)?20:55
popeyjdstrand: no, this doesn't seem to work https://github.com/getlantern/byteexec/blob/master/byteexec.go#L11121:00
jdstrandpopey: patch that or file a bug to have them look at HOME?21:01
jdstrandpopey: alternatively, the snap could use personal-files for ~/.bytecode and then create a symlink from there to SNAP_USER_DATA. it is a hack, but should work21:03
popeyhuh, that's interesting21:04
* popey breaks out the wrapper scripts21:04
sergiusensjdstrand: layouts!21:05
sergiusensuser.Current opens up /etc/passwd to find out the user, so a code patch could work too21:06
sergiusensjdstrand: if we are going to commit to HOME being SNAP_USER_DATA perhaps it would be a good idea to have the bind mounted /etc/passwd path to that as home21:07
jdstrandsergiusens: it won't work for the user's home atm21:08
jdstrandbetter than bind mounting is likely an nss module that is snap aware21:08
sergiusensjdstrand: yeah, but the go std lib opens /etc/passwd and reads straight from there (I haven't looked in detail or seen how they solve nis and such)21:13
jdstrandthat a dumb way to do it. the home may not even be in /etc/passwd21:14
jdstrandmaybe they have a fallback that does nss21:14
popeyshould $HOME point to the users outside home dir?21:20
popeybecause now I'm wondering how my launcher can know what the home dir outside the snap is named21:20
jdstrandpopey: $HOME should be set to SNAP_USER_DATA when the snap starts. you can use 'getent passwd $(id -u) | cut -d : -f 6' to see what the system has to say about it21:22
popeyhah, that's memorable21:23
popeyjdstrand:  ok, moving things and symlinking helped my next issue is that the binary which runs is trying to set the system proxy. I don't see any interfaces which can do that. Is it something I should request?22:13
jdstrandpopey: that is a surprising request for your app but I see no reason why we couldn't have an interface for it. of course, it depends on what it is trying to actually do, but a forum post is good22:21
popeyWhat should I capture? strace? :)22:21
popeyit's a blob which tries to set the proxy22:22
popeyhmm, looks like it rummages in gsettings. I'll start a thready, thanks22:26
Guest92hi all. i'm trying to build a snap that depends on mono. the version of mono from apt is too old, so trying to work out how to pull in the latest versions directly23:23
Guest92something roughly equivalent to => echo 'deb https://download.mono-project.com/repo/ubuntu stable-bionic main' | sudo tee /etc/apt/sources.list.d/mono-official-stable.list23:23
Guest92from what i've read so far, this doesn't seem to be possible?23:24

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