[04:17] Bug # changed: 1663615, 1667359, 1681328, 1682550 [04:20] Bug #1667408 changed: docker container command XXXX could not be invoked === Lin-Buo-Ren-alt1 is now known as Lin-Buo-Ren [04:25] https://forum.snapcraft.io/t/how-to-create-a-lxd-container-for-snap-development/4658 [04:25] RFC [05:13] morning [06:25] hey [06:25] * zyga will be a little late due to DST change [06:25] zyga: hey [06:29] hey ho [06:29] so this week will be, hopefully, more at ease than the last one [06:30] * zyga -> breakfast [07:13] good morning === pstolowski|afk is now known as pstolowski [07:14] morning guys! [07:16] o/ pstolowski [07:23] Hey hey [07:40] PR snapd#4929 opened: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [07:40] Looking [07:42] there's probably a nicer way to write this rule, would appreciate suggestions [07:46] Not in a major way [07:46] It is fine [07:47] oh, ok ;) [07:47] zyga: can you take a look at https://github.com/snapcore/snapd/pull/4908 too? [07:47] PR #4908: [RFC] cmd/snap-confine: attempt to detect if multiarch host uses arch triplets [07:49] zyga: a thought i had during the weekend, maybe we should dump all the figuring out of nvidia dirs from snap-confine and do it in snap command instead, only pass the paths we detected in some predefined environment variables [07:49] Yes, that is the goal [07:50] I think we have all the means now [07:50] something SC_NVIDIA_LIB=/usr/lib/..., SC_NVIDIA_METHOD=symlink, or SC_NVIDA_LIB=/usr/lib/nvidia-340xx, SC_NVIDIA_METHOD=bind, simiarly for 32bit variants [07:50] No no [07:50] Just use the mount profile [07:51] No need for more variables [07:51] .fstab files? [07:52] Yes they have all the bits needed now [07:52] I wanted to do this for quite some time now [07:56] Move the existing system over [07:56] Let snapd handle this [07:56] Rip the c code out [07:58] Nvidia mode gets added to system key [07:58] Later on it just becomes nvidia snap [07:59] zyga: yes, this will work [08:00] meanwhile, 4908 fixes nvidia not working at all with 18.04 :/ [08:03] running new gnome, they seem to half-respect LC_DATE, it currently shows 'poniedziałek, 26 March 2018' [08:04] mborzecki-ubuntu: oh? maybe it's IPC'd over from gnome-something-something [08:04] mborzecki-ubuntu: looking at 4908 now [08:04] * zyga got back from a walk [08:07] how did the failure look like? [08:08] zyga: which failure? [08:09] the 4908 fix for nvidia on ubuntu [08:10] zyga: well, no 3d with nvidia on 18.04 [08:10] zyga: some details https://forum.snapcraft.io/t/nvidia-gl-libs-access-broken-on-ubuntu-18-04/4440 [08:10] let me read that [08:11] so I'm puzzled, you said that your triplet branch made it work on 18.04 [08:11] or was that still on arch? [08:12] zyga: arch fixes are already merged [08:12] and what happens on ubuntu with that multi-arch branch? [08:12] zyga: triplet is for ubuntu, but uses the same thing as is used on arch [08:13] does it crash, does it just not do anything? [08:13] zyga: without the branch there's no 3d, eg. ohmygiraffe hangs, glxinfo shows swrast [08:13] right [08:14] that's expected now that 18.04 uses libglvnd [08:14] zyga: with the branch, if nvidia libs are in /usr/lib/, they'll get symlinked, otherwise /usr/lib/nvidia-xxx is bind mounted (if it exists) [08:14] right [08:14] and what happens on 18.04? we get the symlinks, right? [08:14] zyga: yes [08:15] and? [08:15] zyga: and it works [08:18] oh [08:19] I must be sleepy then, I misunderstood you [08:19] zyga: heh, no worries, I might be sleepy too and talking garbage :P [08:22] hi, a 2nd review of #4928 would be appreciated (should solve at least of most tests/main/layout failures) [08:22] PR #4928: tests: disentangle etc vs extrausers in core tests [08:23] good morning [08:23] hey mwhudson [08:24] pedronis: yes, thank you for pointing that out, pstolowski, mborzecki-ubuntu can you please look at 4928 [08:25] mborzecki-ubuntu: did you see this https://forum.snapcraft.io/t/refresh-scheduling-on-specific-days-of-the-month/1239/22 [08:25] looking [08:26] pedronis: yes, that's the 5minute ensure interval playing tricks, i recall asking about that back when i was double checking that it works, but the behavior (and the code) looked so specific that i did not view it as a bug [08:27] well, it's an easy fix [08:28] zyga: hm pretty much any pr to master touchich apparmor profiles has a problem with temp profile files left behind [08:29] mborzecki-ubuntu: I can prepare a PR if you are busy with nvidia debugging [08:29] pedronis: that'd be great if that's not a big problem for you :) [08:29] mborzecki-ubuntu: can you reproduce that with -debug? [08:30] something must have changed to cause this [08:32] zyga: i have 3 prs for master, 4875, 4908, 4929, each touching apparmor profile and all fail tests/main/snap-confine, i was able to get a debug shell in 4875 using the same -seed, but i was only able to confirm there were temp files in /etc/apparmor.d and those files were not in snapd state snapshot [08:32] interesting [08:32] perhaps the key to trigger it is to change the apparmor profile [08:32] that would trigger the code that updates it [08:34] pedronis: btw. that's just calling EnsureBefore() at the right place? [08:34] yes [08:34] the most annoying bit is writing the unit test [08:34] anyway I started already [08:35] pedronis: great, thank you! [08:45] Bug #1758849 opened: Snap not able to enable ssh after core upgrade [08:50] * zyga tests the community update to the opensuse package [09:05] `VK_ICD_FILENAMES=/var/lib/snapd/lib/vulkan/icd.d/nvidia_icd.json` snap run graphics-debug-tools-bboozzoo.vulkaninfo makes it find nvidia icd now [09:09] PR snapd#4930 opened: skip test that requires internet when not present [09:16] PR snapd#4931 opened: configcore: give a chance to immediately recompute the next refresh time when schedules are set [09:17] mborzecki: ^ [09:18] we probably need to revisit validateRefreshSchedule , it has grown convoluted [09:18] pstolowski: still looking at 4928, any questions? [09:29] pedronis: yes, i've a qustion [09:29] pedronis: just got sidetracked.. give me a sec [09:33] pedronis: commented [09:34] zyga: hi. Now that jdstrand seems mostly happy with the "secure bind mount" implementation, what's next as far as integrating it? [09:35] pstolowski: yes, the tail/head usage is preexisting, we could use grep (at least for root and test), the issue is that afaict the user called ubuntu, is not called like that, it depens on the cloud [09:36] so it's a win some/lose some kind of situation [09:37] pstolowski: I suppose we can use a mixed approach, grep for root, and sanity check for test (but copy the two users, the "cloud" one as well) [09:38] pstolowski: seems like a follow material though [09:38] *follow up [09:38] pedronis: yes, 'test' user would be worth checking for [09:38] pedronis: ok [09:39] I'll do a 2nd PR this afternoon [09:41] I'm squash merging it, because we probably want it in 2.32 if we have more development to do there, or if we get in trouble for this problem with the validations [09:42] pstolowski: thank you for the review [09:42] PR snapd#4928 closed: tests: disentangle etc vs extrausers in core tests [09:43] pedronis: just to be sure, each EnsureBefore(0) causes one iteration of this loop https://github.com/snapcore/snapd/blob/master/overlord/overlord.go#L257 right? [09:44] mborzecki: not each, if you call EnsureBefore(0) many times before the loop has a chance to run, they coalesce to one request [09:44] that's why it's time based [10:00] zyga mvo Morning [10:00] hey flexiondotorg [10:00] mvo is off this week [10:00] Last week before I left for the US I mentioned that snapd 2.32 caused some serious regressions on 18.04. [10:01] Is there a new release to resolve that? [10:01] I'm still experiencing problems. [10:02] niemeyer: ^ [10:02] pedronis: i'm a bit slow today, where are the calls coalesced into one? iirc calling time.Timer.Reset(0) makes it expire immediately, so if the call is made from a handled in one of the .Ensure() calls in overlord/.. the loop will wait (from what i saw those are run in the same goroutine), but if a call like this was made from daemon api, then the loop could turn (different gouroutines), or am i missing [10:02] something? [10:03] zyga: hm got these 2 files: etc/apparmor.d/snap.core.4321.usr.lib.snapd.snap-confine /etc/apparmor.d/snap.core.4321.usr.lib.snapd.snap-confine.pXJnJ6rsK7wX [10:07] mborzecki: do you have a debug session? [10:07] zyga: jest [10:07] zyga: notice this: [10:07] can you stat both of the files [10:07] -rw-r--r-- 1 root root 21297 Mar 26 09:33 /etc/apparmor.d/snap.core.4321.usr.lib.snapd.snap-confine [10:07] and diff them [10:07] -rw-r--r-- 1 root root 21297 Mar 26 09:26 /etc/apparmor.d/snap.core.4321.usr.lib.snapd.snap-confine.pXJnJ6rsK7wX [10:08] so the garbage one is slightly older [10:08] this host executed tests/main/snap-seccomp around 9:26 [10:08] I wonder if we don't do some error checking [10:09] aha [10:09] (have this special patch to spread that logs machine names running each test) [10:10] there is nothing in that test that looks like it would touch snap-confine [10:10] and we only make that file when snapd starts up [10:11] actually, and when it installs new core snap [10:11] zyga: hmm 2018-03-26 11:26:12 Executing google:ubuntu-16.04-64:tests/main/snap-seccomp (1/230) (google:ubuntu-16.04-64 (mar261114-742037))... [10:18] mborzecki: we move reset only if the next is before the current next, but yes usually calls from api.go will provoke many ensures [10:19] pedronis: thanks for confirming :) [10:22] zyga: sorry, for some reason I only got your email now [10:22] zyga: about opensuse package [10:22] hey! [10:22] haha, I'm running "osc build" now :) [10:22] welcome Caelum :) [10:23] I fixed the spaces in the PR, I'll update the patch [10:23] thanks, I'll test it and see what is going on there [10:24] we have some packaging in the git tree [10:24] but it's aimed at our CI loop [10:24] it would be great if you could see how to unify the. two [10:24] Caelum: and again, thank you so much for doing this! [10:24] what was that about the udev rules, just remove those files? [10:24] mmm, which one was that? let me look [10:24] hey, I was only doing this so I could run spotify :D [10:26] I think we don't need to ship the repair service at all [10:26] it's a feature that is only for core devices (distribution that is using just snaps for everything) [10:26] here we can always update snapd with the regular rpm [10:26] ah, I see -%{_udevrulesdir}/80-snappy-assign.rules [10:26] * zyga looks at that file [10:27] so that file we do need [10:28] it's there so that devices that are udev-tagged to a specific snap are actually added to the device cgroup of that snapo [10:28] what made you remove that? [10:29] I didn't touch that [10:29] looking at https://build.opensuse.org/request/show/590994 [10:29] I see -%{_udevrulesdir}/80-snappy-assign.rules [10:31] oh I must have removed it because the dist didn't install it [10:31] oh, I see [10:32] but we still need it, it's also a little bit more complex as it was renamed recently [10:32] let me see what I get in the built rpm now [10:34] do you want me to update to 2.32 ? I didn't do that yet because it wasn't listed as a release [10:34] yes, I think we want that as it brings in a lot of fixes and new features [10:35] but [10:35] let's see if we can get 2.31.x out first [10:35] note that we want to do 2.31.2 probably [10:35] as it's a minor bug fix release and should be the same for packaging [10:35] ah ok, I will update this [10:39] zyga: Regarding snapd in 18.04. [10:40] I've just tested core snap from edge and *all* strictly confined desktop snaps fail to execute. [10:40] `failed to create prefix path: /tmp/snap.rootfs_wo6vzw/var/lib/snapd/lib/vulkan/icd.d: Permission denied` [10:41] mborzecki: ^ is that covered by your recent work? [10:41] or do we need a new PR to update the profiles to match? [10:41] zyga: flexiondotorg: #4929 fixes that [10:41] PR #4929: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [10:42] mborzecki: Thanks. When is that due to land? [10:42] zyga: well ran into a snag already, the vendor releases have the go libs bundled, but the github tarball does not [10:43] Caelum: oh, I see, we didn't make a .vendor tarball? [10:43] OpenGL apps on 18.04 using core from stable either fail to execute or attempt to regression to swrast. [10:43] I think I had a similar problem and I solved it by creating the /var/lib/snapd/lib directory [10:43] flexiondotorg: opengl is well known and not fixed yet [10:43] flexiondotorg: hopefully as sonn as jdstrand gives it a green light (and the build is green) [10:43] Caelum: no, the issue here is much more complex [10:44] flexiondotorg: proposal for fixing opengl is in #4908 [10:44] PR #4908: [RFC] cmd/snap-confine: attempt to detect if multiarch host uses arch triplets [10:44] Caelum: I'll try to get that corrected [10:44] zyga: awesome, because I have no idea how I'd get the go libs otherwise :) [10:45] Caelum: ./get-deps.sh does that [10:45] but I think we can get the vendor tarball done [10:47] is it standard for go to use real tabs? I don't know much about go yet [10:51] Caelum: I think this is what the default "go fmt" formatting does [10:52] ah [11:03] zyga: also you said in the original email, which I only got now for some reason, to remove snap.mount and snap-repair units, should I do that? [11:07] yes [11:15] PR snapd#4932 opened: RFC: Content-interface: add rule so slot can access shared directory using plug's namespace [11:15] zyga: jdstrand: when you have a moment, I'd appreciate your opinions on this: https://github.com/snapcore/snapd/pull/4932 [11:15] PR #4932: RFC: Content-interface: add rule so slot can access shared directory using plug's namespace [11:16] greyback: ack, I'll read this and get back to you [11:16] thank you [11:18] Caelum: so, I know how to make the vendor tarball now, I will make one for 2.31.2 now [11:18] Caelum: and then we can look at 2.32.1 later today [11:18] 2.32 has a small known issue that we must address first [11:20] Caelum: I will let you know when it is available and I will test your package and approve it in the end [11:20] Caelum: perhaps with small tweaks if needed [11:27] zyga: awesome thank you! [11:39] PR snapd#4933 opened: tests: copy or sanity check core users using usernames [11:40] pstolowski: ^ [11:43] * cachio afk [11:55] pedronis: thanks [11:57] +1 === pstolowski is now known as pstolowski|afk [12:04] * zyga curses at backspace-goes-back-in-history in firefox [12:04] and erases *all* form input [12:10] PR snapd#4933 closed: tests: copy or sanity check core users using usernames === pstolowski|afk is now known as pstolowski|lunch === zarcade_droid is now known as Guest76762 === nessita_ is now known as nessita [12:18] pedronis: hey [12:18] pedronis: mborzecki figured out why we have the garbage filenames in snap-confine profile === matteo| is now known as matteo [12:19] pedronis: I think you will need to review that change, it's not big by any standards but it's curious [12:20] so far it's looking good, i'll start another spread run and open a PR [12:22] mborzecki: then we need to rebase/merge the vulcan PR so that it passes [12:24] ok, given that the standup has moved, I will have walk now but can review after the standup [12:24] pedronis: sounds good, thank you [12:26] PR snapd#4934 opened: cmd/snapd: make sure signal handlers are established during early daemon startup [12:26] pedronis: ^^ [12:28] zyga: go to "about:config", search for backspace, and change to 2. Disable backspace=back in FF [12:29] greyback: +1 on your PR [12:29] I added it to 2.32 [12:29] we will do a 2.32.x release soon [12:30] zyga: cool thanks [12:30] * greyback waves https://github.com/snapcore/snapd/pull/4545 seductively [12:30] PR #4545: interfaces/x11: allow X11 slot implementations [12:32] greyback: for 2.33 I'm afraid [12:32] zyga: fair enough [12:34] greyback: can you check if I answered all the open questions that are addressed at me [12:36] zyga: you did, thanks [12:44] thank you jdstrand [12:44] jdstrand: thanks [12:45] np [12:45] zyga: #4939 first, once merged rebase #4929 on top and we should be good, right? [12:45] PR #4929: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [12:45] and hi [12:45] yes [12:45] i meant #4934 [12:45] PR #4934: cmd/snapd: make sure signal handlers are established during early daemon startup [12:46] * kalikiana lunch [12:46] mborzecki: I noticed that there was a 'conflicting profile for snap-confine.XXXXXX. I restarted the test, but it seems like there are temporary files still on disk when the test runs... [12:46] jdstrand: the PR mborzecki just mentioned (4934) fixes that [12:47] ok cool [12:47] hence the rebase dance [12:47] nice [12:51] PR snapcraft#2010 closed: Release/2.40+18.04 [12:53] pedronis: do you think we should include the fix for //deleted mounts for 2.32.1 [12:53] pedronis: it was just test code but could save us some issues in autopkgtest === Son_Goku is now known as Conan_Kudo === Conan_Kudo is now known as Son_Goku [13:00] zyga: yes [13:01] I squashed thinking it might need backporting [13:01] pedronis: thank you [13:21] Issue snapcraft#2025 opened: Proper error on held packages [13:30] Issue snapcraft#2026 opened: Implement a passthrough feature [13:33] Issue snapcraft#2027 opened: Properly crawl tree of remote parts [13:33] Issue snapcraft#2028 opened: When asking to release to a branch that's too long, a traceback is printed that gives no hints as to the source of the error [13:36] Issue snapcraft#2029 opened: Proper error for apt hash sum mismatches [13:36] Issue snapcraft#2030 opened: Properly invalidate the cache if sources change [13:39] Issue snapcraft#2031 opened: Inconsistent results when building, cleaning stage and rebuilding [13:42] Issue snapcraft#2032 opened: Can not use NodeJS 8 [13:42] Issue snapcraft#2033 opened: LP: #1752344 [13:48] mborzecki: I have a fix for the atomic file thing [13:48] zyga: pr? [13:48] Issue snapcraft#1682 closed: Refactor grammar to be compatible with Python 2 [13:48] Issue snapcraft#1683 closed: Make grammar processing available in pypi [13:48] Issue snapcraft#1684 closed: Vendor grammar logic into snapcraft [13:50] PR snapd#4935 opened: tests: disentangle etc vs extrausers in core tests (2.32) [13:51] Issue snapcraft#1708 closed: Implement new design for travis CI UX [13:51] mborzecki: i saw you mention you'd update snapd in arch recently. On my manjaro system I'm only seeing 2.30. Do I need to do some voodoo to get updated? [13:52] popey: build snapd from aur https://aur.archlinux.org/packages/snapd [13:53] mborzecki: is that the 'recommend' way going forward to get the latest version? [13:54] Issue snapcraft#1670 closed: Change file migrations such that files move from stage to prime rather than coming from the part each time [13:57] Issue snapcraft#1690 closed: Design quilt support [13:57] Issue snapcraft#1691 closed: Implement quilt design [13:57] Issue snapcraft#1692 closed: snapcraft quilt tutorial [14:00] popey: yes, at least on arch [14:00] popey: manjaro maintains a set of prebuilt packages from aur, but i have no clue when they get updated [14:01] mborzecki: ok, what's the command to install it? Because that's not the way we have documented how to install snapd on arch.. https://docs.snapcraft.io/core/install-arch-linux [14:01] ah okay [14:01] maybe we need a guide for vanilla arch and one for manjaro? [14:01] oh duh, we have one for manjaro [14:01] https://docs.snapcraft.io/core/install-manjaro [14:01] thanks mborzecki [14:03] zyga: so #4934 is timing out... [14:03] PR #4934: cmd/snapd: make sure signal handlers are established during early daemon startup === pstolowski|lunch is now known as pstolowski [14:07] mborzecki: fun [14:07] mborzecki: I need to break for a moment now but I will propose a fix for the atomic issue when I'm back [14:07] zyga: yeah, fun fact, passing when i run it from spread directly (using google backend obviously) [14:25] zyga: i'll update tests/main/snap-confine to check rules vulkan [14:25] vulkan glob rules [14:26] mborzecki: see if we can mock enough of the logic to break [14:26] as in [14:26] mock the environment [14:26] not the logic [14:26] zyga: yeah, i'm dumping a canary into /usr/share/vulkan/icd.d/ [14:26] it would be cool to install real package with driver deps [14:26] and mock something in sysfs to have snap-confine go the nvidia path [14:28] zyga: afaik nvidia libs are the only driver that ships icd files, but our rules pick up any file for that matter [14:28] mborzecki: can we install nvidia libs in a test? [14:29] in case some pattern is off and only real files cause the issue [14:31] Caelum: you can now get the 2.31.2 tarball [14:40] zyga: then the code path would be executed only on artful (nvidia-384) and bionic (libnvidia-gl-390) [14:42] mborzecki: it's better than nothing [14:42] niemeyer: can you please look at https://github.com/snapcore/snapd/compare/master...zyga:fix/apparmor-tilde?expand=1 [14:42] this is for the ~ in apparmor profiles [14:42] I will write some unit tests but I wanted to get your quick feedback on how this is done [14:43] zyga: there's a typo in the fedora spec on 2.32 [14:43] mmh, also the changelog [14:43] ah, in the changelog [14:43] pedronis: what typo? 'relevant'? [14:43] I saw that [14:43] yes [14:43] I thought it was fixed with the 2.32 merge back to master [14:44] but we should fix it in the release branch too [14:44] zyga: I did thebackport but is failing [14:44] it will annoy tests [14:44] on that [14:44] zyga: https://github.com/snapcore/snapd/pull/4935 is my backport [14:44] PR #4935: tests: disentangle etc vs extrausers in core tests (2.32) [14:45] pedronis: just rename it in your PR [14:45] (fix the typo) [14:45] I think it's fine to do [14:45] zyga: What's the current suffix? [14:46] random alphanumeric AFAIR [14:46] zyga: was there a corresponding PR on master? [14:46] strutil.MakeRandomString(12) [14:46] pedronis: I suspect mvo fixed that in the 2.32 merge but I didn't see a dedicated PR ; it had to be done within the release ->master merge [14:47] zyga: Why not just appending the ~ at the end? [14:47] niemeyer: I'm doing that now [14:47] zyga: that's not even merged yet [14:47] are you saying unconditionally? [14:47] pedronis: ahh, I must have seen wrong [14:47] zyga: Yes, the "just" part :) [14:47] #4927 [14:47] PR #4927: release 2.32 [14:47] niemeyer: sure, that works too [14:47] it's a nice thing to do in general [14:47] maybe more tools skip ~ [14:48] pedronis: so there's no fixing PR yet, sorry [14:48] zyga: Yeah.. [14:49] zyga: I need to have some tea, I will think what to do [14:49] pedronis: thank you [14:49] we probably want to take care of 4927 as well [14:49] niemeyer: I'll do that, thanks! [14:50] * zyga needs to lunch too [14:51] np, and lunch is a pretty good idea [14:57] zyga: hm vulkan code is gated by nvidia driver check too [14:58] let me try the simplest tring, i.e. to load the driver without the card, if that doesn't work well, we could somehow try to mock the path to sys, or try to override it at runtime [15:01] modprobe: ERROR: could not insert 'nvidia_384': No such device [15:03] PR snapd#4936 opened: packaging: fix changelogs' typo (2.32) [15:10] mborzecki you can perhaps mount tmpfs in a place in sysfs and make it appear to be loaded? [15:46] re [15:46] * zyga returns to updating the PRs [15:53] zyga: was passed out on the couch, will update things now, did you want me to pull the udev file from the old dist and add it back in? [15:53] Caelum: yes, please [15:54] Caelum: I will review your update shortly but I have some things to finish [15:54] ok will do :) [15:54] Caelum: just try 2.31.2 [15:54] look at the release page for info [15:54] wait until I update everything [15:54] we added snapd-generator binary [15:54] thats a new thing [15:54] and it replaces the snap.mount unit [15:54] please package that one, it fixes snapd running inside containers [15:55] other than that it should be fairly similar [15:55] got it [16:01] mborzecki, hey, could you please tellme what of all this is not needed for the arch images? [16:01] https://github.com/sergiocazzolato/compute-archlinux-image-builder/blob/master/arch-image.py [16:01] mborzecki, they are doing many thinks but I am not sure what's really needed [16:02] mborzecki, I am starting from this image http://mirror.rackspace.com/archlinux/iso/2018.03.01/archlinux-bootstrap-2018.03.01-x86_64.tar.gz [16:18] PR snapd#4937 opened: osutil: use tilde suffix for temporary files used for atomic replacement [16:18] niemeyer: ^ that's the simplified version [16:27] zyga: Reviewed [16:32] niemeyer: thanks, updated now [16:34] * kalikiana heading out for the day [16:35] mborzecki: ^ [16:38] stgraber nacc: hey, I think I got you covered already, but just in case, want to try out https://forum.snapcraft.io/t/call-for-testing-snapcraft-2-40/4643 ? [16:39] diddledan: thanks for the updates to the ref :-) [16:40] mborzecki: I wonder why the signal handler change is causing things to hang though [16:40] mborzecki: did you try it in qemu? [16:42] zyga: no, it'd be useful to compare how long each test takes now [16:44] mborzecki: you can run qemu with the qemu gui on [16:44] and then log in and watch/interact [16:44] bionic looks different... [16:45] zyga: 'fake' nvidia test https://github.com/bboozzoo/snapd/commit/2c8aa956b3ffe68d98fd446988472db81dbd4c51 [16:46] mmm === Guest78101 is now known as devil__ [16:49] need to wrap it up for today, my wife is really unamused with me now [16:49] mborzecki: thank you! [16:50] mborzecki: I gave you a quick review [16:50] mborzecki: can you propose that? [16:50] pedronis: pushed a patch with buffered channel as you suggested [16:51] hi there! is there a way of changing the display name for the developer of a snap, other than transferring ownership? I tried adding a 'company' name to my profile, but to no avail [16:51] zyga: i'll drop the daemon patch from 4929 and push the test there instead [16:52] thanks [16:53] sergiusens: is it in xenial-updates already? [16:53] nacc: xenial-proposed [16:53] sergiusens: ah ok [16:53] i'll check it out [16:57] the tests take a really long time, would be nice if you could run a smaller subset of important tests [17:05] PR snapd#4936 closed: packaging: fix changelogs' typo (2.32) [17:05] PR snapd#4937 closed: osutil: use tilde suffix for temporary files used for atomic replacement [17:05] hello. I'm having different sets of staged packages (almost) every time I run snapcraft prime; what do I use to debug that? [17:07] the snap does not change, the iamge I build in the snap is the same, too. [17:07] s/the snap/snapcraft.yaml/ [17:09] Caelum: unit tests? They should run pretty quickly. What are you getting? [17:14] zyga: I updated #4927 to include the typo fix, #4935 is green [17:14] PR #4927: release 2.32 [17:14] PR #4935: tests: disentangle etc vs extrausers in core tests (2.32) [17:14] Thank you, looking [17:16] We are only missing one thing now. The fix for apparmor profiles [17:16] PR snapd#4935 closed: tests: disentangle etc vs extrausers in core tests (2.32) [17:16] It should be mergable soon [17:17] maybe there is a ML where I can post so it wont get scrolledback into oblivion? [17:17] thresh: use forum.snapcraft.io please [17:18] fancy :-) [17:39] nacc: thanks [17:39] zyga: the tests take longer for me than the whole build, although I have an old laptop [17:40] I see, I think you will be happy to know our integration tests run for a few hours [17:41] heh [18:06] PR snapd#4938 opened: release-tools: add repack-debian-tarball.sh [18:16] Caelum: I think unit tests are worth keeping [18:17] it's the minimalistic line of defence [18:21] oh sure, they are definitely worth having, I just meant that you have like a "quick sanity check mode" and "all unit tests" mode [18:22] zyga: so I'm done with the changes, updated to 2.31.2, re-added udev rule, removed snap-repair units [18:22] excellent [18:23] I will build, review and test it today and tomorrow [18:23] we can release it tomorrow [18:23] try as many snaps as you can [18:23] sweet [18:23] and see if something breaks [18:23] yeah I already have mailspring and spotify working nicely [18:23] :-) [18:23] would you like to help me get snapd into opensuse proper? [18:24] into factory and tumbleweed and leap? [18:25] yes [18:25] woot, fantastic [18:25] are you familiar with the process? [18:41] hey mvo [18:41] hey zyga [18:41] 700/2000 tests [18:41] I reverted a spread test for nvidia that isn't ready [18:41] zyga: neat [18:41] sorry :/ [18:41] zyga: what pr is it? [18:41] https://github.com/snapcore/snapd/pull/4929 [18:41] PR #4929: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [18:42] mvo: I updated 2.31.2 release page https://github.com/snapcore/snapd/releases/tag/2.31.2 [18:42] zyga: great, thank you! [18:44] zyga: I'm not, this is the first package for oS I've worked on, but from what I can tell from the wiki you just submit the package and it gets reviewed and added, and I know some people in oS who can help me [18:45] Caelum: that's good, I think we can help too [18:45] Caelum: I think we can try to propose 2.32.x once that's ready this week [18:45] PR snapd#4927 closed: release 2.32 [18:45] mvo: did you see my question here: https://github.com/snapcore/snapd/pull/4927#discussion_r176911637 [18:45] PR #4927: release 2.32 [18:47] zyga: I did not, sorry - too trigger happy :( [18:48] zyga: but that is ok, the exact verison in the postinst needs to be adjusted for each upload anyway. but only once [18:48] no worries, what's the answer? [18:48] oh? [18:48] why only once? [18:50] zyga: we need it to match the exact version of the upload (so e.g. 2.32.1+17.10) [18:50] zyga: after that (when we release 2.32.2) it will be enough to test for "less-than" 2.32.2 I think [18:50] zyga: any news on the nvivia 18.04 work? [18:52] not more than earlier today, maciej needs to add the scoping and the tests for this [18:52] I think it can all happen tomorrow [18:52] I think the last PR looks happy now [18:52] discarding machines [18:53] zyga: yay, no errors? [18:53] zyga: cool, once its merged I will cherry-pick [18:53] yes [18:53] it's green now [18:53] merging [18:54] drat, I didn't squash [18:54] mvo: please take just https://github.com/snapcore/snapd/pull/4929/commits/5f1762b0b8ab52b7e60fcce377e24c5ce025b219 [18:54] PR #4929: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [18:54] PR snapd#4929 closed: cmd/snap-confine: apparmor: allow creating prefix path for gl/vulkan [18:54] mvo: and f3f77d9ac192e78523c82a15d368dea943ed8841 [18:55] and that's the release [18:55] zyga: ok, thanks [18:55] zyga: nothing from beta validation that needs fixing? all green there? [18:55] no, all green there [18:56] zyga: cool [18:56] mvo: you can consider https://github.com/snapcore/snapd/pull/4934 if you want but I'm not pushing for that [18:56] PR #4934: cmd/snapd: make sure signal handlers are established during early daemon startup [18:56] zyga: the "~" pr is a bit of a workaround ;) [18:56] it's 2.32.2 material [18:56] haha, yes [18:56] I read apparmor source code [18:56] anything else is worse [18:56] like .rej [18:56] or .dpkg-new [18:56] zyga: ;) [18:56] or .rpm-something [18:57] zyga: ideally we would figure out why we have the leftovers but I think we are in agreement here :) [18:57] zyga: I looked at the singal PR, it looks harmless, does it fix a real issue? [18:57] zyga: I mean, anything that was reported by users etc? [18:57] oh [18:57] we did [18:58] it is the real issue [18:58] we have logs where we start initializing stuff [18:58] and then get killed with SIGINT [18:58] this and the ~ PRs fix the same issue from two ways [18:58] or sides [18:58] we will only process signal and shutdown after snapd is constructed [18:58] and we will write files that are ignored by apparmor anyway [18:59] this is a test issue but it can affect real systems too [18:59] in tests it's just shutting down snapd being unreliable [19:00] squash it please [19:00] PR snapd#4934 closed: cmd/snapd: make sure signal handlers are established during early daemon startup [19:00] mvo: if you prepare the debian part I can make the release page look nice again :) [19:00] mvo: I need to take Bit out for a walk [19:01] (Bit is how our dog is called :) [19:05] zyga: sure, I prepare things and we sync up when you are back. cu [19:11] PR snapd#4939 opened: release: 2.32.1 [19:13] zyga: its building in ppa:snappy-dev/image now, once that is done I will trigger beta build etc [19:15] Super [19:36] mvo: back [19:39] zyga: waiting for publication [19:41] mvo: I'm seeing the same thing [19:44] mvo: we need to be careful in typos in changelog [19:44] they cause test failures [19:45] I think it's fine now, just saying [19:46] mvo: published [19:48] zyga: yeah, triggered the build [19:48] mvo: so that's it now, just -> beta publishing once it's out [19:52] zyga: yeah [19:53] zyga: and ideally merge the changelog pr so that we have a edge build again :) [19:53] yeah [19:53] you can merge https://github.com/snapcore/snapd/pull/4938 [19:53] PR #4938: release-tools: add repack-debian-tarball.sh [19:57] PR snapcraft#2023 closed: repo: catch error due to broken build packages [20:00] Issue snapcraft#2025 closed: Proper error on held packages [20:08] PR snapd#4939 closed: release: 2.32.1 [20:09] zyga: pushed to beta [20:10] great, then that's today [20:11] have a peaceful night :-) [20:11] zyga: thank you, you too! keep me posted if things work or if we need a .2 :) [20:11] * mvo waves [20:12] PR snapcraft#2034 opened: pluginhandler: organize correcly for targets with leading / [20:15] zyga: fwiw, this is the page I was following the past few days, and it also describes how to add stuff to Factory (TW) I think we can start with the process of requesting a new devel project or finding an appropriate top-level space right now https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory [20:33] PR snapcraft#2035 opened: ci: cache core and lxd to avoid redownloading [20:37] Caelum: I think we have a nice devel project already [20:37] Caelum: system:snappy is a good place [21:37] zyga: yeah then it's just one osc command to submit to Factory [21:38] That's the beauty of OpenSUSE [22:00] zyga, thought you'd like to know, I'm now a sublime text user [23:25] Issue snapcraft#1974 closed: organize with forward slashes should be stripped [23:25] PR snapcraft#2034 closed: pluginhandler: organize correcly for targets with leading / [23:34] nacc: hey, did you have an opportunity to look into 2.40? Personally I setup my own buildd for git-ubuntu and ran the self-tests succesfully, not sure what more could be done [23:35] sergiusens: i haven't had a chance yet; if you've run the above, though, that's what i'd do [23:35] so i'm +1 if that passed [23:35] (which is what didn't before :) [23:35] nacc: yes, fwiw https://forum.snapcraft.io/t/snapcraft-snap-building-sanity-checks-for-build-snapcraft-io/4632/1 [23:36] I still need to hook more of it up in some orchestration system, but this will be part of our release testing