/srv/irclogs.ubuntu.com/2020/03/19/#snappy.txt

mupPR snapcraft#2984 opened: plugins: move the existing plugin to a new package <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2984>00:59
mborzeckimorning06:48
zygaUh06:52
zygaMorning06:52
zygaIā€™m so tired today06:52
zygaToo much work yesterday06:53
zygaIs mvo around?06:53
mborzeckizyga: hey06:54
mborzeckizyga: he doesn't seem to be online yet06:54
pedronismvo: hi, #8278 can be merged if you are ok with my last bit of changes07:49
mupPR #8278: devicestate: disable cloud-init by default on uc20 <UC20> <Created by mvo5> <https://github.com/snapcore/snapd/pull/8278>07:49
mvopedronis: let me check, I just summarzied the core refresh issue but that's summarized now, still in the dark about it07:57
mvopedronis: how are tests looking? lots of red yesterday I noticed07:58
pedronismvo: snapd-failover still fails sometimes, Ian knows07:58
pedronismvo: other tests are flaky as well, the cgroup named one fails sometimes07:58
mvopedronis: meh, that one is really a tough one07:58
* mvo nods07:58
mvopedronis: I go over the prs and see if there is anything I can do07:59
pedronismvo: there are some uc20 that need 2nd reviews, I need to re-review some as well08:00
pedronismvo: zyga left a comment in #8295 about 14.0408:02
mupPR #8295: osutil: do not leave processes behind after the test run <Created by mvo5> <https://github.com/snapcore/snapd/pull/8295>08:02
pedronismvo: there might be 2.44 things to backport for .1 ?08:03
pedronisI mean things landed on master08:04
pstolowskimorning08:04
mvopedronis: yeah, checking that too, thank you08:05
mvopstolowski: good morning08:05
mvohm,snap-confine-undesired-mode-group seems to fail fairly often, should we disable it until we have a fix?08:26
mupPR snapd#8292 closed: travis.yml: run unit tests on master as well <Squash-merge> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8292>08:28
mupPR snapd#8291 closed: packaging,tests: ensure debian-sid builds without vendor/ <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8291>08:30
pedronismvo: it does08:30
mupPR snapd#8290 closed: run-checks: tweak formatting checks <Simple šŸ˜ƒ> <Skip spread> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8290>08:31
pstolowskipedronis: hi, re search v2 pr & 400s, i think they were temporary (proxies catching up with latest fix?), i  think i saw them before when working on this after Tony deployed new fix. i've re-run two of the failing tests a moment ago and they passed. just kicked travis on that PR again, let's see how it goes today08:31
mupPR snapd#8278 closed: devicestate: disable cloud-init by default on uc20 <UC20> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8278>08:32
pedronispstolowski: ok, please also sync with him because I think they are discusing s/search/find/ in the endpoint08:34
pedronisas well08:35
pstolowskiyes i saw the email08:35
pedronismborzecki: hi, can you look at #8159 again, I don't think it's doing what we discussed, but maybe I'm confused08:40
mupPR #8159: snap-bootstrap: remove created partitions on reinstall <UC20> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/8159>08:40
ackkzyga, hi, do you need any other info WRT #1841137 ?08:53
mupBug #1841137: /dev/loopX devices left around for removed snap revisions <snapd:Confirmed for zyga> <https://launchpad.net/bugs/1841137>08:53
mborzeckipedronis: yeah, tweaking it a bit already, idk but sfdisk manpage is super confusing abut the attrs format08:59
mborzeckiat least the way it's printed seems stable, even if not 'well defined'09:00
pedronismborzecki: ok, if you are working on it, let's drop forcing the luks type (I think overriding the gadget content without thinking it through is risky/unexpected)09:00
pedronisthis was discussed already anyway yesterday09:00
zygaackk: hey09:01
* zyga is so tired today09:01
zygamvo: about that issue affecting that customer device09:01
zygamvo: I was wondering09:01
zygais it the only one that crashes?09:02
zygaor is it affecting other identical devices09:02
zygamvo: please don't disable it, I'll filter out files that are not made by this test from it09:02
zygamvo: it really shows we leak cgroups/sessions across tests09:03
zygamvo: not that the test is broken per se09:03
mvozyga: in a meeting, will get back to you09:03
mvozyga: multiple identically devices are not refreshig (3/3)09:04
zygamvo: in that case it's a real bug :|09:04
mupPR snapd#8298 opened: many: enumerate system seeds, return them on the /v2/systems API endpoint <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8298>09:31
mborzeckipedronis: mvo: ^^09:31
mvomborzecki: thanks, in a meeting right now09:32
ackkzyga, fwiw it seems the snap-discard-ns trick doesn't always work before removing the snap. I had to run it multiple times09:32
ackkzyga, also: https://paste.ubuntu.com/p/dcwFrV6yxp/ (the script does a bunch of snap connect)09:37
zygaackk: oh?09:46
zygaackk: I'm in a call09:46
ackksorry09:47
zygauh09:54
zyga360 reviews are due today09:54
pedroniszyga: they were due, the window is closed10:03
zygayeah, I noticed now :/10:03
zygaoh bummer10:03
zygamvo: I'm connected to Tw VPN10:07
mupPR snapd#8286 closed: tests: cleanup various uc20 boot tests from previous PR <Test Robustness> <UC20> <Created by anonymouse64> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/8286>10:30
mupPR snapd#8293 closed: packaging: add README.source for debian <Skip spread> <Created by mvo5> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8293>10:43
zygabrb10:47
mborzeckimvo: an idea to play with in https://github.com/snapcore/snapd/pull/8295#discussion_r39494182710:56
mupPR #8295: osutil: do not leave processes behind after the test run <Created by mvo5> <https://github.com/snapcore/snapd/pull/8295>10:56
mborzeckimvo: seems to work locally here10:56
mvomborzecki: nice one, do you think that's easier/more reliable? I have no strong opinion either way10:58
mborzeckimvo: we could turn it into a cleanup helper and reuse ;)10:58
mvomborzecki: sure, works for me11:02
mborzeckimvo: hmm still, it's not enough for mocks, we should probably track the main pid in the template11:03
mvomborzecki: yeah, let's not spend too much time on this until we have more time (unless it's quick :) we have some bigger fish to fry right now11:05
mborzeckimvo: otoh, when we exec.Command(), we ought to take care of the child process too and kill the whole group11:05
mvomborzecki: (if you have something relatively quick and clean, by all means, that's fine of course, use your judgement)11:05
ackkzyga, fwiw I'm getting that "read only" error even in a VM (so no snapfuse)11:05
mvomborzecki: indeed11:05
mupPR snapd#8299 opened: devicestate,sysconfig: support "cloud.cfg.d" in uc20 for grade: dangerous <Created by mvo5> <https://github.com/snapcore/snapd/pull/8299>11:07
mborzeckimvo: oh, and we even have a osutil.KillProcessGroup helper ;)11:09
ackkzyga, n/m, I didn't have robust namespace on11:14
zyga:)11:14
mborzeckimvo: wdyt about this: https://github.com/snapcore/snapd/compare/master...bboozzoo:bboozzoo/process-fun-fun ?11:19
mvomborzecki: +111:27
mvomborzecki: that looks pretty neat11:27
mvomborzecki: looks like the exit 1 on gofmt makes a bunch of stuff red11:30
mborzeckimvo: which PR?11:30
mvomborzecki: the most recent two ones, mine and yours11:31
mborzeckihmm wth is the diff output trimmed?11:31
mborzeckimvo: ehh https://github.com/snapcore/snapd/pull/830011:34
mupPR #8300: boot: apply Go 1.10 formatting <Simple šŸ˜ƒ> <Skip spread> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8300>11:34
mupPR snapd#8300 opened: boot: apply Go 1.10 formatting <Simple šŸ˜ƒ> <Skip spread> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8300>11:34
mborzeckiat least we can skip spread now ;)11:35
mvomborzecki: indeed, thanks for that!11:39
mborzeckiuhh11:44
mborzecki#8300 is green12:00
mupPR #8300: boot: apply Go 1.10 formatting <Simple šŸ˜ƒ> <Skip spread> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8300>12:00
mupPR snapd#8269 closed: apparmor: use rw for uuidd request to default and remove from elsewhere <Created by jdstrand> <Merged by bboozzoo> <https://github.com/snapcore/snapd/pull/8269>12:02
pstolowskimvo: restarted #8251, would be nice to land it after it gets 2nd review12:04
mupPR #8251: overlord: remove unneeded overlord.MockPruneInterval() mocks <Created by mvo5> <https://github.com/snapcore/snapd/pull/8251>12:04
mvopstolowski: yeah, thank you!12:10
mupPR snapd#8300 closed: boot: apply Go 1.10 formatting <Simple šŸ˜ƒ> <Skip spread> <Created by bboozzoo> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/8300>12:16
pstolowskizyga: do we have any plan to move https://github.com/snapcore/snapd/pull/7205 forward? should we close it and re-open when needed?12:17
mupPR #7205: rfc: introduce confinement options failsafe flag <Needs Samuele review> <Created by zyga> <https://github.com/snapcore/snapd/pull/7205>12:17
zygaI think the plan is to emit warnings indeed12:18
pedronispstolowski: thanks for the review of 8277 , I haven't yet looked at why/which of the spread tests fail12:29
pstolowskisure12:30
pstolowskipedronis: btw #8283 has a conflict12:30
mupPR #8283: overlord,timings,daemon: separate timings from overlord/state <Created by pedronis> <https://github.com/snapcore/snapd/pull/8283>12:30
pedronisfun, not12:31
pedronisanyway I'll look when it gets a 2nd review12:31
pedronisthanks for noticing it though12:31
mupPR snapd#8191 closed: [RFC] cmd/snap-recovery-chooser: add a recovery chooser <Needs Samuele review> <UC20> <ā›” Blocked> <Created by bboozzoo> <Closed by bboozzoo> <https://github.com/snapcore/snapd/pull/8191>12:33
ijohnsonmorning folks12:42
cmatsuokagood morning ijohnson12:44
ijohnsonhey cmatsuoka12:44
pstolowskihi ijohnson12:46
ijohnsono/ pstolowski12:47
pstolowskiand hi cmatsuoka !12:47
pstolowski#8251 needs 2nd review (and is super simple)12:47
mupPR #8251: overlord: remove unneeded overlord.MockPruneInterval() mocks <Created by mvo5> <https://github.com/snapcore/snapd/pull/8251>12:47
mupPR snapcraft#2985 opened: static: ignore direnv created artifacts <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2985>13:13
pedronispstolowski: I did another pass on search v2, looking good, still some comments/questions though13:16
pstolowskipedronis: thanks13:17
pedronispstolowski: also seems they are going ahead with /find, sync with Tony about timeline for that13:17
pedroniswe'll have to bump the version check as well13:17
jdstrandmvo: hey, are you still collecting PRs for 2.44 or is it baked?13:19
pedronisjdstrand: 2.44 itself is kind of baked, but we'll do a .1 very likely13:27
pedronisjdstrand: OTOH we are looking only for really neccesary or low risk even for .113:28
pedronismborzecki: I reviewed #8298, thank you13:28
mupPR #8298: many: enumerate system seeds, return them on the /v2/systems API endpoint <UC20> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/8298>13:28
mborzeckipedronis: thanks!13:28
jdstrandpedronis: I may have something that meets that criteria to address an issue in the firefox snap that kenvandine and jamesh highlighted elsewhere13:31
pedroniscmatsuoka: I re-reviewed #815913:41
mupPR #8159: snap-bootstrap: remove created partitions on reinstall <UC20> <Created by cmatsuoka> <https://github.com/snapcore/snapd/pull/8159>13:41
cmatsuokapedronis: thanks, re-checking it...13:41
mvojdstrand: still collecting for a 2.44.1 that will happen13:56
jdstrandmvo: ok, don't wait on me. if I get you something fine, if not, also fine :)13:56
jdstrandmvo: thanks!13:56
mvojdstrand: yeah, 2.44 is out but we already know we will do a point release with some tweaks we want to have in 20.04-final13:57
jdstrandkenvandine: hey, can you read and comment on my assessment in https://bugs.launchpad.net/snapd/+bug/1868051 ?14:14
mupBug #1868051: browser-support[allow-sandbox=true] should not grant access to /var/lib/snapd/desktop/applications <snapd:Triaged> <https://launchpad.net/bugs/1868051>14:14
mupPR snapcraft#2986 opened: packaging: use find_namespace_packages in setup.py <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2986>14:34
jdstrandkenvandine: to be clear, I'd like your (or jamesh) feedback in a bug comment in bug #1868051 before I do anything14:34
mupBug #1868051: browser-support[allow-sandbox=true] should not grant access to /var/lib/snapd/desktop/applications <snapd:Triaged> <https://launchpad.net/bugs/1868051>14:34
kenvandinejdstrand: thanks!14:39
kenvandinejamesh: can you please comment on that?14:40
kenvandinejdstrand: another issue is what to do when firefox wants to open a file rather than download it15:02
kenvandineright now that goes in TMPDIR15:02
kenvandinewhich of course apps do not have access too15:02
jdstrandkenvandine: I think you mean that the file goes in firefox's /tmp but the other app isn't able to open it because either a) firefox says it is in /tmp when it is actually in /tmp/snap.firefox and b) the permissions on /tmp/snap.firefox are such that non-root can't access it15:05
jdstrandkenvandine: IME, firefox plugs 'home'. patch it to default to ~/Downloads instead15:05
jdstrandkenvandine: there is another option using the content interface to export 1777 $SNAP_COMMON/tmp or similar, but then other snaps need to know to plugs it so not really scalable15:06
kenvandineyeah15:07
kenvandinejdstrand: i've played with setting TMPDIR and have proven it works15:07
kenvandinebut, $HOME/Downloads has a couple issues15:07
kenvandine$HOME isn't $REALHOME in the snap15:08
kenvandineand15:08
kenvandine~/Downloads could be translated15:08
jdstrandkenvandine: other options are what were discussed before, a special way to opt out of per-snap tmp. this needs design and snapd changes. that also doesn't work for other snaps since we actually want per-snap /tmp and they wouldn't be able to access host /tmp15:08
kenvandineI guess I could add a script to the command-chain to get $REALHOME and the translated Downloads dir15:09
kenvandinejust worry about that being fragile15:09
jdstrandkenvandine: well, yes, of course you would have to do reall hame (getent passwd $(id -u) | cut -f 6 -d ':')15:09
jdstrandreal home*15:09
jdstrandkenvandine: and the snap would be free to use a translated Downloads15:10
kenvandineyeah, that's well known.  just need a script to set that.  can't do it in the yaml15:10
kenvandinei'd need to shell out to xdg to get the translated Downloads15:10
kenvandineshould work fine... but i worry about corner cases :)15:10
jdstrandkenvandine: iirc, you only need to do this once since firefox remembers the last one15:11
jdstrandkenvandine: I know that is true for when downloading a file15:11
jdstrandkenvandine: it might not be for /tmp itself15:11
jdstrandkenvandine: but, it could be adjusted to follow the download location15:11
jdstrandkenvandine: perhaps it honors TMPDIR?15:12
kenvandineit does15:12
kenvandineso i just need to set TMPDIR in the snap15:12
jdstrandkenvandine: in which case, on snap startup you could in a wrapper, calculate realhome, calculate the translated dir name and then set TMPDIR before firefox starts15:13
kenvandinei'm just thinking through what i want to set that too before submitting a patch to mozilla15:13
jdstrandkenvandine: maybe you want to set it to realhome/Downloads/firefox.tmp.15:14
jdstrandkenvandine: in this manner, actually temp files don't clutter Downloads and if things don't get cleaned up like they should, someone can clean it out15:15
jdstrandactual*15:15
kenvandinei like that idea15:15
jdstrandkenvandine: or even .firefox.tmp15:15
jdstrandkenvandine: firefox itself (or the wrapper), could clean up things, deleting stuff older than say, a week15:16
jdstrand(be careful doing that, don't follow symlinks!!)15:16
jdstrandkenvandine: basically, there is no clear way to make /tmp work that works will with other snaps too (not without some rather deep and/or super magical integration with snapd), but home is shared by most everything that would open a file in this manner15:18
jdstrandman typos15:18
jdstrandworks well*15:18
kenvandine:)15:18
kenvandinejdstrand: ok, thanks for the feedback.  i'll continue with my original plan15:19
kenvandinebut add firefox.tmp to it15:19
jdstrandnp15:19
jdstrandkenvandine: fyi, from with snap run --shell firefox:15:23
jdstrand$ xdg-user-dir DOWNLOAD15:23
jdstrand/home/jamie/Downloads15:23
kenvandineyeah15:23
jdstrandso you don't need the getent at all15:23
kenvandine# Set TMPDIR to be under the user's default Downloads dir15:24
kenvandineexport TMPDIR=$(xdg-user-dir DOWNLOAD)/firefox.tmp15:24
kenvandinehandy15:24
kenvandineand i'll add that to command-chain after desktop-launch to ensure xdg user dirs are all setup15:24
jdstrandkenvandine: you probably know this, but xdg-user-dir just looks at ~/.config/user-dirs.dirs whish in the case of firefox is $SNAP_USER_DATA/.config/user-dirs.dirs15:26
kenvandinejdstrand: yeah, desktop-launch does some stuff to ensure those are set properly15:27
jdstrandkenvandine: I guess so long as that user-dirs.dirs is setup right, you're good15:27
jdstrandcool15:27
jdstrandkenvandine: this should really help. the wrapper may want to mkdir that directory. it is too bad that the snap probably needs to keep it clean, but hey, not a terrible solution to the problem overall15:28
pstolowskipedronis: hey, do you have a moment for HO?15:29
kenvandinefirefox does create it if it doesn't exist15:29
pedronispstolowski: yes15:32
pstolowskipedronis: joining standup HO15:33
tkamppeterjdstrand, hi15:41
tkamppeterjdstrand, what about a meeting about the interface for the new CUPS Snap?15:42
kyrofaijohnson, any insight into how to make https://forum.snapcraft.io/t/no-interfaces-without-core-snap a better experience?15:54
kyrofaIt's an unfortunate situation15:54
ijohnsonkyrofa: upgrade snapd everywhere ?15:58
ijohnsonkyrofa: the issue is that its a bug we have solved everywhere in new snapd, and devices keep hitting the bug because there seems to be old snaps in many places15:59
kyrofaijohnson, that's not a solution I'm afraid15:59
kyrofaijohnson, not one that scales15:59
kyrofaijohnson, the problem is that it's standard practice to only install security updates in prod16:00
ijohnsonI mean whatever solution I can come up with involves changes to snapd, which only happens if you get an upgraded snapd ... hence the problem16:00
ijohnsonperhaps others have thoughts, but I don't know how we can make old snapd's change behavior without updating old snapd16:00
kyrofaijohnson, we have abused the security component in the past, is that an option?16:01
ijohnsonkyrofa: you mean push an update to -security ?16:01
kyrofaIndeed16:01
ijohnsonyeah that doesn't sound like a bad idea to me, I think there is some precedent for that, we have done that to solve this exact problem on trusty for example16:01
ijohnsonthat would be a mvo request though16:02
kyrofaExactly my thinking. Not pretty, not ideal, but not unprecedented16:02
ijohnsonyep16:02
kyrofamvo, you should consider that as core18 becomes the standard16:02
kyrofaijohnson, mvo, I'll add a comment about this to the forum post16:03
ijohnsonkyrofa: thanks16:04
pedroniskyrofa: we do need the agreement of the security team to do that16:06
pstolowskipedronis: --mask/unmask work with --root šŸ‘16:08
pedronispstolowski: good16:08
jdstrandtkamppeter: hey, I saw the discussions. can you put something in the calendar for sometime next week? Tue, Wed or Thu is best for me16:16
jdstrandtkamppeter: I've been wanting to review all the discussions again (I've read them) and think through everything in preparation for the meeting16:17
tkamppeterijohnson, around?16:19
ijohnsontkamppeter: yes16:20
ijohnsonNext week is fine for me16:20
ijohnsontkamppeter Please include pedronis in the meeting though16:20
pedronisI will not be available Thu or Fri16:20
tkamppeterOK, should we do wed, 25, at 3pm UTC?16:22
tkamppeterjdstrand, ijohnson, pedronis, me, someone else?16:22
tkamppeterOr better mon, 23, at 3pm UTC?16:23
ijohnsontkamppeter: I don't think we need anyone else in the meeting, and 3 pm UTC works for me, but I prefer Wed instead of Mon16:23
tkamppeterSo let us do Wed then.16:24
tkamppeterjdstrand, ijohnson, pedronis: Done. You should have gotten an invitation.16:30
ijohnsongot it, thanks tkamppeter16:31
mvokyrofa: sorry, lacking context16:31
mvokyrofa: can you give me a tl;dr16:31
* cachio lunch16:33
kyrofamvo, quick read: https://forum.snapcraft.io/t/no-interfaces-without-core-snap . tl;dr if you have a bionic install with a snapd that hasn't been updated, you can't install a core18 snap16:33
jdstrandtkamppeter: you didn't check for meeting conflicts :(16:33
kyrofaAt least, not without also manually installing the core snap or manually updating snapd first so it installs the snapd snap16:34
tkamppeterjdstrand, so I hit another meeting of yours? I will go through all three where I find a slot.16:34
jdstrandtkamppeter: that is in conflict for me. all day tuesday is open for me, and most of thursday. wednesday my morning has a conflict16:34
jdstrandtk thanks16:34
jdstrandtkamppeter: thanks :)16:34
* jdstrand lunch16:35
tkamppeterjdstrand, pedronis, ijohnson: How do I check the participant's meeting schedules?16:36
tkamppeterijohnson, pedronis, what do you prefer? Tue, or Thu?16:36
pedronisThu I'm off16:37
tkamppeterSo Tue is left, ijohnson, does it work for you?16:37
jdstrandtuesday, again, is good for me at around the same time up to two hours earlier or 6 hours later16:39
jdstrandtkamppeter: (to answer your question, I temporarily add people to Other calendars to see if there is a conflict. there might be a better way)16:40
mvokyrofa: yes, that's correct, we fixed this a while ago but not everybody got the fix :(16:40
jdstrandok, really going to lunch now16:40
kyrofamvo, right, exactly16:40
mvokyrofa: it's a good question what we can do, we could (ab)use the security pocket so that people get the update via unattended-upgrades but it's a bit borderline16:41
tkamppeterSo let me do a time guess which should hit a slot on all of you: Tue, 24, 1pm UTC16:41
ijohnsontkamppeter: sorry I was away16:41
tkamppeterijohnson, jdstrand, pedronis: Is  Tue, 24, 1pm UTC OK for all of you?16:42
ijohnsontkamppeter: yes that's fine for me16:42
kyrofamvo, indeed. Is there any other option?16:42
jdstrandtkamppeter: yes16:43
tkamppeterpedronis?16:43
pedronistkamppeter: doesn't work for me, but maybe you should have a first meeting just with ijohnson and jdstrand and see how far you get16:44
mvokyrofa: we could grow something in the wrapper/command-chain that detect snap versions older than the fixed one (2.41? need to check changelog) and warn but that won't work so well for gui apps and is also not a amazing UX16:44
tkamppeterpedronis, do you have another slot, which could hit a free slot of jdstrand?16:45
kyrofamvo, wouldn't that also be a snapd update, though?16:46
pedronisTue 3p pm UTC16:46
mupPR snapcraft#2985 closed: static: ignore direnv created artifacts <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2985>16:46
ijohnsontkamppeter: I looked at everybody's calendars and propsoed a time which should work for everybody16:46
kyrofamvo, or is that something you can put in core18?16:47
ijohnsontkamppeter: pedronis ah I think I proposed the same time that pedronis said16:47
tkamppeterijohnson, which one is that time?16:47
ijohnsonit's 10 am cst, I don't know what UTC time it is16:47
tkamppeterijohnson, could you create a meeting at that hour, and invite me, so I will see where it falls.16:48
ijohnsontkamppeter: if you check your email you should get an email with the proposed time16:48
mvokyrofa: a warning from the installed snap would be on the snap side, i.e. when you install snap foo and run "foo.bar" it would detect in the wrapper/command-chain. but it's not a great experience, I'm not really advocating it, just trying to come up with ideas16:48
mvokyrofa: oh, maybe we could put "assumes: [snapd2.41]" into core1816:49
mvokyrofa: I wonder if that would work16:49
tkamppeterijohnson, nothing appeared yet.16:49
kyrofamvo, ah, which implies a snapcraft change, and an assumption that the snap being installed was built recently16:49
kyrofamvo, the assumes would just prevent install, right?16:50
mvokyrofa: correct, not a great option16:50
kyrofaBut at least it TELLS them something16:50
mvokyrofa: it would but with a somewhat useful message16:50
kyrofaIndeed16:50
mvokyrofa: it might be worth a shot16:50
kyrofaRight now it's just broken, and the user is left holding the pieces wondering what to do16:50
kyrofasergiusens, you around?16:50
mvokyrofa: exactly, we would have to test it, not sure how exactly the UX looks like but I think it's probably better than what we do right now16:51
mvokyrofa: thank you for raising this btw16:51
ijohnsontkamppeter: I sent an invite, I guess you have a meeting that goes til 10:30, I think a 30 minute meeting is enough for now16:51
kyrofamvo, my pleasure. I think it would be trivial to add this to snapcraft, which will move things in the right direction. Mull over the -security abuse, though16:53
kyrofamvo, I'll update the forum thread with this16:53
sergiusenskyrofa: yes16:53
tkamppeterijohnson, could we move it to half an hour later?16:53
sergiusenskyrofa: a bit hectic today though... the country is closing down and I am dealing with accomodations for a period where we do not know what will stay open16:54
tkamppeterOr is it really the only 1-hour hole in the week for all the 3 of you?16:54
kyrofasergiusens, then ignore me. I'll ping you in the forum, look when you can16:54
sergiusenskyrofa: it is fine now :-) Might not be later :-)16:54
tkamppeterIf so, our Desktop team meeting is only IRC and usually ends after 30 minutes.16:54
mvokyrofa: thank you!16:55
ijohnsontkamppeter: I moved it16:55
tkamppeterijohnson, I have moved it again, WDYT about this time?16:56
ijohnsontkamppeter: which meeting, the tuesday one I set up or the monday one you set up ?16:57
kyrofasergiusens, to save you the scrollback then, I pinged you anyway: https://forum.snapcraft.io/t/no-interfaces-without-core-snap16:57
tkamppeterijohnson, the tuesday one, I did not realize that I have put mine on monday, because the Calendar is starting weeks with Sun.16:58
ijohnsonokay so the tuesday meeting is the one we will do16:58
tkamppeterijohnson, so I will remove my meeting and let the rest up to you. OK?16:59
ijohnsonsure sounds good16:59
mupPR snapd#8159 closed: snap-bootstrap: remove created partitions on reinstall <UC20> <Created by cmatsuoka> <Merged by cmatsuoka> <https://github.com/snapcore/snapd/pull/8159>17:00
sergiusenskyrofa: replied on forum, short answer: we can17:00
tkamppeterijohnson, done.17:01
tkamppeterCould you add the link https://forum.snapcraft.io/t/interface-request-cups-control-on-cups-snap-and-including-d-bus/ to the description? Thanks.17:02
ijohnsondone17:03
cmatsuokacachio: #8260 is still failing, shellcheck didn't like some stuff there17:04
mupPR #8260: tests: enable nested on core20 and test current branch <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8260>17:04
abeatoijohnson, hey, is it possible lready to run UC20 on kvm?17:33
tkamppeterijohnson, jdstrand, pedronis, I have sent you all an e-mail with the final settlement for the meeting. Please check.17:37
jdstrandtkamppeter: ack, thanks! (accepted)17:58
cachiocmatsuoka, fixed17:58
ijohnsonabeato: yes, do you have a dire need to boot uc20 on kvm soon? it's easy enough to seup but building images and such may change a bit from now until the release, so rather than have you get caught up in those changes if you can wait until the release that would be best17:58
abeatoijohnson, I'm starting to develop snaps with base: core20, and I'd like to do some testing. But it looks like I can run them on UC18, it downloads core20. Is that a good enough environment for some initial testing?18:00
ijohnsonabeato yes for now that's probably good enough, as we can get closer we can help you run on actual uc2018:23
tkamppeterjdstrand, thanks for the feedback.18:29
abeatoijohnson, ok, then I have all I need, thanks18:34
mupPR snapd#8260 closed: tests: enable nested on core20 and test current branch <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/8260>20:01
mupPR snapd#8301 opened: interfaces/many: deny arbitrary desktop files and misc from /usr/share <ā›” Blocked> <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8301>20:18
jdstrandmvo: fyi, ^ was the PR I was thinking of for 2.44.1. after implementing it, I think it is too much for 2.44.1 and have milestoned if for 2.45 instead20:23
jdstrandjamesh (cc kenvandine): I referenced https://github.com/snapcore/snapd/pull/8301 in https://github.com/snapcore/snapd/pull/830120:23
mupPR #8301: interfaces/many: deny arbitrary desktop files and misc from /usr/share <ā›” Blocked> <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8301>20:24
mvojdstrand: thanks20:25
jdstranderf20:25
jdstrandjamesh (cc kenvandine): sorry, mispaste. I referenced https://github.com/snapcore/snapd/pull/8301 in https://bugs.launchpad.net/snapd/+bug/186805120:25
mupPR #8301: interfaces/many: deny arbitrary desktop files and misc from /usr/share <ā›” Blocked> <Created by jdstrand> <https://github.com/snapcore/snapd/pull/8301>20:26
mupBug #1868051: browser-support[allow-sandbox=true] should not grant access to /var/lib/snapd/desktop/applications <snapd:In Progress by jdstrand> <https://launchpad.net/bugs/1868051>20:26
kenvandinejdstrand: thanks!  I dropped jamesh and email earlier asking him to comment when he's back online20:27
mupPR snapd#8302 opened: interfaces/greengrass-support: fix typo <Simple šŸ˜ƒ> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8302>20:52
mupPR snapd#8303 opened: interfaces/greengrass-support: fix typo <Simple šŸ˜ƒ> <Created by anonymouse64> <https://github.com/snapcore/snapd/pull/8303>20:53
mupPR snapd#8283 closed: overlord,timings,daemon: separate timings from overlord/state <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/8283>20:54
jdstrandzyga: for tomorrow's standup. I wonder if bug #1866932 and bug #1867952 are dupes of bug #186506321:40
mupBug #1866932: package snapd 2.44~pre1+20.04 failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 <amd64> <apport-package> <focal> <snapd (Ubuntu):New> <https://launchpad.net/bugs/1866932>21:40
mupBug #1867952: package snapd 2.44+20.04 failed to install/upgrade: installed snapd package post-installation script subprocess was killed by signal (Terminated)  <amd64> <apport-package> <focal> <snapd (Ubuntu):New> <https://launchpad.net/bugs/1867952>21:40
mupBug #1865063: snapd package hangs on deb postinst <focal> <snapd (Ubuntu):Confirmed> <https://launchpad.net/bugs/1865063>21:40
jdstrandzy21:40
jdstrandoh, ijohnson is here. zyga, nm21:40
jdstrandijohnson: fyi ^21:40
jdstrandijohnson: that might be something for 2.44.1. I don't have any more info to add; just fyi21:41
ijohnsonjdstrand: sorry what's this21:44
jdstrandijohnson: it is just so mvo is aware that there might be an issue with 2.44 and (at least) deb upgrades21:44
ijohnsonjdstrand: ack I'll make sure it's in the SU notes, but I don't have bandwidth to investigate right now unfortunately21:45
jdstrandijohnson: postinst isn't finishing21:45
jdstrandijohnson: oh, I wasn't asking you to look :) just bubbling it up so you can maybe mention it in standup21:45
mwhudsonwhat is the expected lag between pushing to an automatically built branch in launchpad and the build starting?21:45
mwhudsoni never quite know what to expect21:46
ijohnsonjdstrand: also did you see I needed to open another greengrass-support PR ? apparently what I had was insufficient21:46
ijohnsonthey needed a slightly different access21:46
jdstrandmwhudson: that is a good question. sometimes it seems fast and other times less so21:46
jdstrandijohnson: oh, not yet21:46
* jdstrand looks21:46
ijohnson8302 and 8303 IIRC21:47
jdstrandijohnson: approved21:49
ijohnsonthanks jdstrand !21:49
jdstrandnp21:50
mwhudsonjdstrand: i wonder if it's a */15 cron or something21:51
mwhudsonanyway my snap is now building21:51
jdstrandmwhudson: it probably is cron. I had a fanciful idea that it would do it quickly if you hadn't committed in a while and then back off if you had :)21:58
jdstrandmwhudson: sometimes I'm impatient and trigger it manually21:59
mwhudsonyeah i thought there was a threshold like that too but idk21:59
mwhudsonyeah and then you end up with two builds going at once :)21:59
jdstrandit makes it twice as fun that way :)21:59
cjwatsonmwhudson,jdstrand: There is indeed a */15 cron job; it runs for any snap that's configured to build automatically, whose source branch has been modified since the last automatic build was dispatched, and which hasn't had an automatic build dispatched in the last hour.23:00
cjwatsonWhen the build actually *starts* after that will of course depend on build farm load etc.23:00
mwhudsoncjwatson: does pushing a new tag count as modification?23:01
mwhudsoncjwatson: and, hah for me guessing the frequency23:01
cjwatsonmwhudson: No.23:01
cjwatsonmwhudson: Modification is detected per-ref, so you'd need to actually change the specific branch that the snap builds from.23:02
mwhudsoncjwatson: makes sense23:03
cjwatson(More specifically, when you push changes to a git repository in LP, any snaps based on refs that have changed are marked as stale.)23:04
cjwatsonIt's fairly similar to the recipe staleness logic, which you may distantly remember from bzr.23:04
mwhudsonvery distantly :)23:05

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