[01:44] PR snapcraft#2437 opened: repo,baseplugin: support trusting repo keys [05:35] Good morning [06:07] morning [06:34] hey mborzecki :) [06:34] zyga: hey hey [06:35] I'd love to land some boring stuff today [06:35] most blocked by https://github.com/snapcore/snapd/pull/6353 [06:35] PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions [06:35] zyga: which pr should i start with first? [06:35] I think this one is the only one I really need [06:35] though all the ones should be a moment to review [06:36] ack [06:40] PR snapd#6355 closed: release: 2.37~pre1 [07:02] zyga: one suggestion under #6349, other than that it's +1 [07:02] PR #6349: cmd/snap-update-ns: move XDG code to dedicated file [07:02] looking [07:03] nice :) [07:05] pushed [07:06] I prepared another branch but I will need https://github.com/snapcore/snapd/pull/6346 as well [07:06] PR #6346: osutil: add helper for loading fstab from string [07:08] mborzecki: updated https://github.com/snapcore/snapd/pull/6346 based on your comment [07:08] PR #6346: osutil: add helper for loading fstab from string [07:54] zyga: regarding #6345 none of the patches that start to make use of FromSnapConfine in s-u-n user mounts are up yet, right? [07:54] PR #6345: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user [07:54] zyga: same for freezer [07:55] mborzecki: the main branch is [07:55] mborzecki: the only use of --from-snap-confine is to lock/freeze [07:55] but that is arguably one of the last patches in this pile [07:55] zyga: mhm [07:57] btw. have dropped codecov? [07:57] s/have/have we/ [08:01] I ... don't remember we did [08:01] but perhaps? [08:02] idk, haven't seen any coments being added to the new PRs === pstolowski|afk is now known as pstolowski [08:02] morning [08:04] pstolowski: heya [08:04] hey Pawel [08:13] pstolowski: hey, could you do a 2nd review for https://github.com/snapcore/snapd/pull/6353 [08:13] zyga: sure [08:13] PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions [08:20] moin moin [08:20] hey chipaca :) [08:21] Chipaca: can I bug you for one little review in the morning please? https://github.com/snapcore/snapd/pull/6346 [08:21] PR #6346: osutil: add helper for loading fstab from string [08:21] zyga: you can bug me all you want [08:21] * Chipaca adds zyga to his ignore list [08:22] Chipaca: hey [08:34] re [08:45] should I have another coffee? [08:45] I should have another coffee. [08:45] * Chipaca obeys [08:57] Chipaca: I hear you [08:57] coffee is good [08:57] PR snapd#6356 opened: overlord/snapstate: during refresh, re-refresh on epoch bump [08:58] pedronis: ^_^ [08:58] Chipaca: thx [08:58] pedronis: and good morning [08:59] we'll see if I get to it today [08:59] pstolowski: https://github.com/snapcore/snapd/pull/6353#issuecomment-453438414 [08:59] PR #6353: cmd/snap-update-ns: move existing code around, renaming some functions [09:00] zyga: sure [09:00] thanks! [09:00] I didn't notice 2017 :) [09:00] PR snapd#6353 closed: cmd/snap-update-ns: move existing code around, renaming some functions [09:01] Chipaca: the pic in your response is lovely === chihchun_afk is now known as chihchun [09:01] feels like the way to spend time :) [09:01] zyga: :-) [09:01] PR snapd#6346 closed: osutil: add helper for loading fstab from string [09:03] Chipaca: next on your list, I think, is snapshot user docs? and maybe picking up/rework #6348? does that sounds right? [09:03] PR #6348: snap: split alignment calculation and display for channels [09:04] pedronis: I'd like to know what to do about #6034 also [09:04] PR #6034: many: save media info when installing, show it when listing <⛔ Blocked> [09:04] pedronis: but, yes, snapshot user docs, info refactor, then maybe per-architecture info [09:05] Chipaca: yes, I'm aware of 6034, but indeed needs discussion so it's blocked atm [09:05] pedronis: we're not going to have time to have that discussion before the town of capes, right? [09:05] * Chipaca hopes everybody packed capes [09:06] likely not but we'll see [09:07] Chipaca: also next week sprint is organized a bit differently, with lots of everybody sessions all in the morning, so I might not be busy all the time, just almost all the time [09:07] pedronis: also I notice you removed the block on #6280, does that mean it's gtg (pending 2nd review)? [09:07] PR #6280: cmd/snap: make 'snap warnings' output yamlish [09:07] pedronis: you're going to a sprint, and think you might not be busy all the time [09:07] *giggle* [09:09] Chipaca: I should probably look at it again (6280) but is not blocked about the --unicode oddities vs non-ttys [09:09] pedronis: ah :-) ok [09:09] Chipaca: mvo asked for gustavo's input but if I understand it is something that was discussed with him, no? [09:09] pedronis: yep [09:09] at the london sprint (!) [09:09] also the general principle, if too wide for tabular/naive output, be yaml-like/parsable [09:13] Heya [09:14] niemeyer: hi [09:48] brb [09:51] Chipaca: can you remind me how to poke at the API with http ? [09:52] pedronis: http snapd:///v2/find name==go [09:52] pedronis: or, http --pretty=all snapd:///v2/find name==go | less -R [09:53] Chipaca: thank you [10:16] huh, I thought snapshots were in 2.36 [10:17] just had a user on 2.36.3 tell me it didn't work there [10:31] Chipaca: no, they are not, not they client bits [10:31] they are in 2.37 [10:34] 2.37 is going to be a big'un [10:39] pstolowski: hi, btw I started yesterday looking again at the hotplug-connect PR but didn't finish, we'll try to do so today [10:40] pedronis: ack, thanks [10:59] pedronis: added one suggestion to the doc you just shared, it was something on the back of my mind for several interfaces (e.g. optical drive is the same) [11:02] why isn't architecture in `snap version`? [11:02] zyga: add it "all" to what? [11:02] the plug, the slot? [11:02] to the interface, I will clarify my comment [11:03] well, to the slot side [11:03] if you have "all" you are the old legacy camera [11:03] if you don't have that you are a precise camera [11:03] either hotplug or gadget [11:03] I was basing that on having a path or not [11:04] but we can do both [11:04] on the slot side, anyway this is a discussion to have [11:04] those were just jumping points [11:07] that's good, it's the same idea [11:07] ah, I see it's on the following line [11:08] I'll retract my suggestion [11:29] any clue if we'll be merging master to 2.37 again? [11:31] master to 2.37? [11:31] never? [11:31] I think it is cherry picking from now on [11:31] hm ok [11:31] proxy leaking from test to test? https://www.irccloud.com/pastebin/cw3P0RWp/ [11:33] soliciting 2nd review for https://github.com/snapcore/snapd/pull/6349 [11:33] PR #6349: cmd/snap-update-ns: move XDG code to dedicated file [11:33] pstolowski: do you have a moment? [11:38] zyga: ok [11:42] mborzecki: https://github.com/snapcore/snapd/pull/6352#discussion_r [11:42] PR #6352: many: remove .user-fstab files from /run/snapd/ns [11:43] zyga: yup [11:44] zyga: wonder if that should use rm -f {} \: instead, so that find does not stop if there's a failure to remove [11:45] those are plain files [11:45] should remove fine [11:45] pushed [11:45] I think we only had -f to "fix" rm -f *.foo expanding to "*.foo" [11:46] it'd be good if Chipaca could take a look too [11:46] +1 [11:46] I added him to the review now [11:46] +4, -16 [11:46] :) [11:47] pstolowski: +1 with a comment still, also would be good if you got reviews from mborzecki and mvo for it [11:47] hehe :) [11:47] pedronis: k [12:20] re [12:20] some kitchen emergency, all good now [12:24] * pstolowski lunch [12:31] I'm seeing one test fail often today; [12:32] tests/main/xdg-open-compat fails with ERROR 503 while talking to launchpad.nett https://www.irccloud.com/pastebin/74kd9yef/ [12:32] zyga: .nett? [12:33] no, .net, just a typo [12:35] zyga: launchpad might be sad today [13:01] PR snapd#6357 opened: cmd/snap-update-ns: make freezer mockable [13:05] PR snapd#6358 opened: cmd/snap-update-ns: close internal lock on error [13:05] mborzecki, pstolowski: I would love a review for the two above, this would make the refactor purely a refactor with 0 new features or fixes [13:06] I broke the two patches out to make that true [13:06] they are both really tiny [13:07] PR snapd#6349 closed: cmd/snap-update-ns: move XDG code to dedicated file === ricab is now known as ricab|lunch [13:34] is the store api down (snap find foo isn't working) or just my system having issues? [13:34] aha. it's gone through now [13:34] transient [13:34] ignore me [13:34] working for me [13:34] :-) [13:36] re [13:36] the knights who say "re"? [13:36] PR snapd#6359 opened: tests: use double quotes for regex on listing test to match \\* [13:36] :-p [13:36] store down and wonky errors https://www.irccloud.com/pastebin/pj7DG1v2/ [13:37] Chipaca: ^ [14:02] Chipaca: standup? [14:02] agh, yes [14:02] was distracted by CVEs [14:02] * Chipaca goes [14:21] how do i tell my snapcraft.yaml that i want to stage-packages from 16.04? [14:22] if you don't tell it you want `base: core18` it will use 16.04 by default (you are using multipass, right?) [14:22] i don't know [14:25] diddledan: I don't think that's true [14:25] diddledan: if you use base: core18 you will use the new base and the new multipass builder [14:25] diddledan: but in absence of that I think you will build the old way [14:25] diddledan: I may be wrong, but that's what I think was the approach [14:25] "Issues while validating snapcraft.yaml: The 'version' property does not match the required schema: 0 is not a valid snap version string." [14:26] zyga: yes, which is why I caveated my comment with the multipass [14:26] right but multipass is not on uless you use base: * [14:26] but there's no published core16 base [14:26] what is a valid version string then? [14:26] ali1234: perhaps "1" [14:26] not sure why 0 is rejected [14:26] nope, 1 also does not work [14:26] if you aren't knowingly using multipass then you'll use the old build which builds against your host. if you specify `base: core18` then you will use multipass [14:27] i want to use 16.04 as base when building on 18.04 [14:27] the solution to use multipass correctly is `env SNAPCRAFT_BUILD_ENVIRONMENT=multipass snapcraft` [14:30] yeah what happens is if you don't have "base:" in snapcraft.yaml it builds against the host [14:30] not if you tell it to use multipass [14:30] if you have "base" it installs multipass for you, then fails to work because it won't accept any version string [14:31] the only `base` value that is accepted is `core18`. don't set it but tell snapcraft to use multipass [14:32] if i set base: core18 then it still fails to accept the version string. but doing it your way works [14:32] it is now launching a VM === ricab|lunch is now known as ricab [14:36] it seems to be stuck... [14:36] PR snapd#6358 closed: cmd/snap-update-ns: close internal lock on error [14:36] ali1234: quick question, is there a reason you don't want to just say "base: core18" [14:37] yes, the package isn't available in ubuntu 18.04, if it was i'd just install it normally [14:38] "launch failed: timed out waiting for instance to respond" [14:40] instance failed instantly :) [14:41] ali1234: I'm not sure I understand [14:41] which part? [14:41] ali1234: using base: core18 will just build your project against ubuntu 18.04 build system [14:41] ali1234: is that breaking your software? [14:42] i dont have any software [14:42] o_O [14:42] ali1234: which package is not available in 18.04? [14:42] eagle [14:43] eagle? [14:43] yes, eagle [14:43] and is it advailable in 16.04? [14:43] https://packages.ubuntu.com/search?keywords=eagle&searchon=names&suite=all§ion=all [14:43] yes [14:43] the CAD tool ? [14:43] yes, the CAD tool [14:43] aaah [14:43] which is non-free [14:43] well [14:43] that's not from the ubuntu archive :) [14:43] what are you trying to build? [14:44] eagle [14:44] an eagle snap? [14:44] yes [14:44] specifically an eagle 6.6 snap [14:44] I think you can use base: core18 just fine, you need to teach your snapcraft.yaml about where to get eagle from [14:44] the version that is available for ubuntu 16.04 [14:44] unless eagle just plainly doesn't work on any other version of ubuntu [14:44] it isn't available any more [14:44] the only place it is available is the ubuntu package [14:45] eagle isn't available for ubuntu 16.04 specifically - you download it from autodesk as a tarball [14:45] I think the error you are seeing is unrelated to core18 or eagle and it would be the best to migrate to core18 for your software, integrate fetching the eagle .deb (however legal is that) [14:46] I'm not just saying this because core18 is better [14:46] diddledan: no, it is available as an ubuntu package for 16.04 [14:46] nope [14:46] but because the old build model (building natively) is going away [14:46] snapcraft switched to build with multipass-managed virtual machines [14:46] https://launchpad.net/ubuntu/+source/eagle/6.6.0-2 [14:46] or migrate to kicad :) [14:47] that's not available in xenial [14:47] i386? [14:47] yes it is: https://launchpad.net/ubuntu/+source/eagle/ [14:47] Eagle is a powerful IM client designed to fit in perfectly in an enterprise environment. [14:47] yes, it's i386 only [14:47] weird [14:48] anyway, I'm back to coding [14:48] PR snapd#6357 closed: cmd/snap-update-ns: make freezer mockable [14:49] pstolowski: could you do a 2nd review for https://github.com/snapcore/snapd/pull/6345 [14:49] PR #6345: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user [14:52] ali1234, regarding your version issue, i can build just fine here using "version: 0" in a snap [14:52] yes, here it won't accept any version string at all [14:52] did you put any quotes areound the version string or some such ? [14:52] no [14:52] *around [14:52] very weird [14:53] what is the most simple possible snapcraft.yaml that should always be guaranteed to build? [14:53] what snapcraft version isthat ? [14:53] $ snap info snapcraft|grep installed [14:53] installed: 3.0.1 (2374) 28MB classic [14:53] whatever you get with 18.04 [14:53] you dont use the snap ? [14:53] PR snapd#6345 closed: cmd/libsnap: pass --from-snap-confine when calling snap-update-ns as user [14:53] \o/ [14:53] thanks! [14:54] * ogra has long stopped using snapcraft from the archive ... never had issues [14:54] snapcraft, version 3.0.1 [14:54] I try to use a snap if one is available unless I hit issues with it that I can't fudge [14:54] well, then i dont get why it doesnt work the same way as mine [14:55] actually i do have it installed through snap: installed: 3.0.1 (2374) 28MB classic [14:55] probably some other typo in the snapcraft.yaml ? (and the version thingie just being fallout) [14:58] this is my entire snapcraft.yaml: http://paste.ubuntu.com/p/cQZFmSnm49/ [14:58] i doubt thats valid [14:59] better use snapcraft init and modify the created file then [14:59] PR snapd#6360 opened: cmd/snap-update-ns: refactor of profile application [14:59] you are surely missing a lot of required fields [15:00] (description, confinement ... not sure but probably also grade) [15:00] `version: 0` is actually invalid because snapcraft (or rather the python yaml parser) reads it as a number when it's expecting a string [15:00] diddledan, it doesnt for me [15:00] replacing it with `version: '0'` works [15:01] i just took one of my snaps changed version to 0 and called snapcraft ... no errors for me [15:02] okay i did "snapcraft init" and then "snapcraft" - it's hanging at launching the VM again [15:04] ogra: with ali1234's yaml: https://www.irccloud.com/pastebin/OeZVLYOb/ [15:05] "snapcraft init" also generates a quoted version field [15:05] niemeyer: the wikipedia reference on that bug is fantastic [15:05] "That looks great. Just one thing: get rid of the duck." [15:05] :"D [15:05] diddledan, well, but that snapcraft.yaml is generalyl broken [15:06] the rest of the brokenness is besides the point though. snapcraft _expects_ a string. [15:06] if you managed to get a working build with a number then you've hit a bug [15:06] i just tried removing the quotes from the generated snapcraft.yaml and it produces the same error [15:07] the error message could be more helpful. [15:09] is multipass using docker? [15:09] no, kvm [15:11] "multipass launch" works, it is actually doing something [15:13] i can see qemu using CPU, it's still spinning though [15:17] nope, failed [15:20] how ? [15:20] (surely different than before ?) [15:20] nope, identical. it spins for about 8 minutes then says "launch failed: timed out waiting for instance to respond" [15:22] now running it with verbose [15:22] have you tried a reboot ... or logout/login cycle, after installing multipass ? [15:22] no [15:22] (did you wiggle the cable ?) :P [15:23] https://paste.ubuntu.com/p/26DQgRrWKQ/ [15:24] wow [15:25] classic snaps ... the pain ... [15:25]