[05:24] morning [05:47] mvo: is it equally hot at your location? it's ~8am and 26 degrees in the shade [05:49] mborzecki: its overcast here today so not hot yet [05:49] mborzecki: we had this last week :/ === pstolowski|afk is now known as pstolowski [07:02] mornings [07:05] hey pstolowski [07:18] pstolowski: hi. I ran into a transient unit test failure in the "snap snapshot" tests, and it looks like you've had most involvement in them. I filed https://bugs.launchpad.net/snapd/+bug/1832161 with the details [07:18] seems like the regexp should be adjusted to account for different amounts of white space [07:20] jamesh: hi! thanks for the report, will investigate === harrisj_ is now known as harrisj [07:57] pstolowski: hey [08:00] jamesh: https://github.com/snapcore/snapd/pull/6982 should fix i [08:00] *it [08:18] is there now a way to disable automatic snap update checks? I'd like to not auto update my snaps as I want to have control over my system and don't need automated updates [08:18] Chipaca ^updates could introduce security issues or there might be malicious updates which I don't want to automatically apply to my stable system [08:21] lss8: it seems like a rather poor strawman to me, if you trust the thing enough to install it, you trust it to refresh -- for any case where an update has introduced new vulnerabilities, there have been many that removed them [08:22] lss8: unless as I say you're vetting for a large fleet of devices in which case fair enough and there are tools for that [08:22] mborzecki: one question to #6980 [08:23] lss8: for a single device, even for a small handful, you won't have a person full-time vetting things [08:23] Chipaca those are my personal servers and I do have time to run `snap refresh lxd` every once in a while [08:23] lss8: at which point you're arguing that existing, known security vulnerabilities are safer than unknown new ones [08:24] I just don't want LXD to update itself when the current release is perfectly stable for me [08:24] lss8: you can control when the refresh happens, and how often [08:24] lss8: you cannot turn it off [08:24] but.. there's no way to completely turn it off? [08:24] lss8: there is no way to opt in to being part of a botnet, no [08:36] I wish the forum would close topics after a couple of months of inactivity [08:37] six months later "I'm getting the same error: " [08:41] Chipaca: I think https://github.com/snapcore/snapd/pull/6954 is mostly ready. It ballooned in size a bit adding the Ubuntu Core support though. I could split that out into a separate PR pretty easily though by cutting off the final four commits [08:41] jamesh: I need to circle back to some reviews, yes, sorry for my delay [08:41] jamesh: I'll take a look and let you know, re splitting [08:43] the Ubuntu Core support mainly involved installing the new unit files on core18 systems [08:50] Chipaca: hey, do you have a moment for https://github.com/snapcore/snapd/pull/6982 ? [08:52] pstolowski: sure [08:58] Chipaca: ty! [09:17] Chipaca: by the looks of it manjaro forums does close the topics after 90 days of inactivity, so maybe it's a configuration option or a feature of some newer version of discourse? [09:26] mborzecki: sadly I am only a moderator, not an admin [09:27] Chipaca: mhm, i know [09:28] Chipaca: looks like discourse https://forum.manjaro.org/t/snapd-is-not-working-since-downgrade-to-systemd-239-6-2-2-advised-in-the-security-update-on-2019-01-19/73774/37 doesn't it? [09:30] ha found the exact version even among tags: Discourse 2.3.0.beta11 - https://github.com/discourse/discourse version ace6ce046273799c866e85942182db7d77bed4d2 [09:30] we use: Discourse 2.0.0.beta10 - https://github.com/discourse/discourse version 30fbf6fe8181426ff8cab81d10a26c61f635f4d6 [09:33] the downside of closing old topics is that people end up needing to start new topics about the same thing that lose all context from the old discussion [09:34] it's not always a new user incorrectly diagnosing their bug [09:34] jamesh: true, and I may just be noticing the bad ones [09:52] * Chipaca brb [11:20] Good morning [12:21] hey zyga === ricab is now known as ricab|lunch [12:35] #6958 could use another review [12:52] hey pawel :) [12:52] how are you guys doing? [12:56] zyga: the weather is unbearable here, i envy you ;) [13:29] pstolowski: 16C [13:31] mvo: I just realied I should've reopened #6582 and targeted it to 2.40; done that now (pending rob's confirmation) [13:33] Chipaca: ok === ricab|lunch is now known as ricab [13:41] pstolowski: and it rains [13:41] zyga: hey, how are you? how is the summit [13:42] pstolowski: I kind of wish it would be not raining so much because the hotel keeps us hostage [13:42] mvo: hey, good morning! [14:00] pstolowski: it's getting worse https://i.imgur.com/6MJHkqC.jpg [14:01] omg [14:06] pedronis, mvo: https://paste.ubuntu.com/p/BCXRzjcX5V/ [14:07] magic [14:13] mborzecki, pstolowski you feel like me now [14:13] cachio: :) [14:33] * cachio afk [14:36] update on centos : "Job for var-lib-snapd-snap-core-6964.mount failed." See $insert-log-message-checking-message-here - updating 2.38.1 to 2.39.1 [14:42] Chipaca: heh [14:47] diddledan: that's when the rpm snippets ran right? [14:48] diddledan: keep in mind you need to reboot after the update [15:04] mborzecki: o m g [15:04] 41C [15:07] zyga: where? [15:07] mvo: in pl [15:11] thanks mborzecki [15:14] * Chipaca takes a break [15:14] * Chipaca does not miss 41°C weather === pstolowski is now known as pstolowski|afk [18:15] is this a bug? devmode classic confinement snaps seemingly don't inherit environment variables from the calling shell while in stable they do [18:36] * cachio afk