[07:04] morning [07:22] mborzecki: hi! Is this file an ordinary shell script? https://github.com/snapcore/snapd/blob/b47c262d795ea262016f0eaa9c2804f05a82e2b6/tests/lib/snaps/test-snapd-remodel-pc-18/grub.cfg [07:22] mardy: almost, but not quite [07:23] grub implements a subset of shell operations, or something that is deceptively similar, but not quite 😕 [07:23] ahh, I was in fact wondering why the variables where being assigned with "set var=value", because that doesn't seem to work in bash [07:24] heh, it's like csh iirc [07:24] but again, not quite 🙂 [07:43] PR snapd#11207 closed: gadget: allow gadget struct with unspecified filesystem to match part with fs [08:09] morning [08:56] pstolowski: hi! [08:57] good morning pstolowski and mardy ! [08:57] heya [08:57] https://github.com/snapcore/snapd/pull/10864 would be great to land :) [08:57] PR #10864: mount-control: step 3 [08:58] PR snapd#11227 closed: spread.yaml: add debian-{10,11}, drop debian-9 [08:58] PR snapd#11237 closed: HACKING.md: add dbus-x11 to packages needed to run unit tests [08:58] PR snapd#11238 closed: cmd/snap/quota: fix typo in the help message [08:59] unrelated failures in 10864 afaict (quota, udev-subsystem, bluez) [09:33] mvo: hi, can you land this PR? https://github.com/snapcore/snapd/pull/11226 [09:33] PR #11226: tests: workaround missing bluez snap <⚠ Critical> [09:57] good morning :) [10:19] zyga: hi! [10:35] heh [10:35] go get vs go install in 1.16+ is so much full [10:35] our run-checks code is doing silly things now [10:44] PR snapd#11239 opened: tests/lib/prepare-restore: use go install rather than go get [11:34] PR snapd#11236 closed: tests: ensure /snap/bin is in PATH in "tests.session exec" [11:44] PR snapd#11240 opened: tests: fix parallel-install-basic on external UC16 devices [12:14] PR snapd#11241 opened: systemd: add NeedDaemonReload to the unit state [12:19] PR snapd#11242 opened: systemd: enable batched calls for systemd calls operation on units [12:24] I want to reuse this function (with minimal changes) in another interface: https://github.com/snapcore/snapd/blob/master/interfaces/builtin/shared_memory.go#L83-L106 Would interfaces/helpers.go the right place for it? [12:39] PR snapd#11243 opened: tests/main/snap-info: use yaml.safe_load rather than yaml.load [12:59] PR snapd#11244 opened: tests: Test initrd systemd configuration refactoring (alternative patch set) [13:09] PR snapd#11245 opened: vscode: Added integrated support for MS VSCODE [13:57] PR core20#126 closed: make update-motd writable for branding purposes [13:57] PR core18#185 closed: make update-motd writable for branding purposes [14:02] PR core20#125 closed: static: disable systemd ctrl-alt-del burst action [14:02] PR core18#184 closed: static: disable systemd ctrl-alt-del burst action [14:15] PR snapcraft#3620 opened: Revert "lifecycle: do not stage deps for pull on core20" [14:15] PR snapd#11241 closed: systemd: add NeedDaemonReload to the unit state [14:20] PR snapd#11226 closed: tests: workaround missing bluez snap <⚠ Critical> [14:20] PR snapd#11241 opened: systemd: add NeedDaemonReload to the unit state [14:47] PR core20#127 opened: Add a PR template that informs of core-base repository [14:52] PR core20#127 closed: Add a PR template that informs of core-base repository [14:55] PR snapcraft#3604 closed: Newsnapcraftspike snapyaml [15:10] PR snapcraft#3612 closed: Flutter extension: Force GDK to use GLES [15:30] Hello! I have a question about using cloud-init with Ubuntu Core 20. The docs say that you can put a cloud.conf file in the root of the gadget, but does it not need to be referenced from gadget.yaml or snapcraft.yaml somehow? My cloud.conf doesn't seem to work if I just put the file in the gadget directory before building it. [15:34] I found this post saying that there's a document in progress for using cloud-init with UC20, but it's from March 2021 and as far as I can see there isn't any documentation published for it yet: https://forum.snapcraft.io/t/ubuntu-core-20-ama/23406/5 [15:40] PR snapcraft#3620 closed: Revert "lifecycle: do not stage deps for pull on core20" [16:06] webchat51: the cloud.conf needs to be staged into the final snap, it's not enough to just put it in the same dir as the snapcraft.yaml, you have to either edit your snapcraft.yaml to put the file into the snap, or after building (or modifying an existing gadget snap), unpack the .snap file copy in the cloud.conf then repack it [16:12] ijohnson[m]: Thanks for the reply! I'm new to creating snaps so I'm not sure what the syntax is for snapcraft.yaml to include a file, but I'm sure I can look that up. Did I read correctly that cloud.conf just needs to be in the root of the built/packed snap and then UC20 will use it for cloud-init? [16:14] yes it just needs to be in the root of the built/packed snap [16:14] you can look at the dump plugin in snapcraft as an easy way to include files into the built snap [16:16] Awesome, thank you for your help! [18:20] PR snapcraft#3621 opened: [DRAFT] setup: unpin linters and add additional linting tools === diddledani_ is now known as diddledani === cjp256_ is now known as cjp256 === jamespage_ is now known as jamespage === madhens_ is now known as madhens === ogra` is now known as ogra [19:26] Quick question about setting snaps in the model assertion. Can classic confinement snaps be installed via the model assertion in a custom image, or only strict mode snaps? [19:37] webchat51: only strict/devmode snaps on Ubuntu Core [19:37] Ok, thanks! [19:39] np [20:56] PR snapd#11246 opened: tests: fix `tests/core/create-user` on testflinger pi3 === stgraber_ is now known as stgraber [22:30] PR snapcraft#3616 closed: cli: create new snapcraft entry point (CRAFT-729) [23:17] PR snapd#11234 closed: gadget: resolve index ambiguity between OnDiskStructure and LaidOutStructure [23:57] PR snapd#11229 closed: cmd/snap, daemon: add debug command for getting OnDiskVolume dump