[07:40] good mornign [07:50] morning [07:55] good morning mborzecki [07:55] mvo: hey [08:03] mvo: can you land https://github.com/snapcore/snapd/pull/9927 ? it's the reference rpm spec for fedora, but a spread job on uc20 failed [08:03] PR #9927: packaging/fedora: sync with downstream packaging in Fedora [08:04] (oh and it needs a 2nd review) [08:05] mborzecki: sure [08:08] mvo: thanks! [08:10] PR snapd#9927 closed: packaging/fedora: sync with downstream packaging in Fedora [08:15] morning [08:15] pstolowski: hey [08:30] hey guys [08:31] hey zyga [08:31] and good morning pstolowski [08:34] o/ === alan_g_ is now known as alan_g [10:34] pedronis: replied under https://github.com/snapcore/snapd/pull/9921/files/940b71fefdeadd4d2d1823139a8529b907117876#r575128036 [10:34] PR #9921: boot: helper for setting up a try recover system [10:35] mborzecki: do be clear both our comments are about unexpected reboots, not expected reboots [10:35] *to be clear [10:36] pedronis: right, unless snapd_recovery_mode/snapd_recovery_system is modified we should not boot into the tried recovery system [10:37] pedronis: and the first case would be when we unexpectedly reboot in SetTryRecoverySystem() cleanup, but we still haven't modified snapd_* variables, as this is done by devicemgr.Reboot(mode,system) [10:38] pedronis: and the other case is unexpected reboot when we're back in run mode after having tried the system or just cleaning up, the snapd_* boot vars should be set to boot into run mode only at this point [10:38] does that make sense? :) [10:39] mborzecki: tbh, I think maybe you should quickly write down how you expect this to work, I mean the flow and the way the vars change at different point. It might make reviewing things piece by piece easier [10:40] pedronis: sure, let me update the doc [10:40] and maybe we can have a quick chat before the standup then [10:40] ok [10:40] maybe invite Ian as well (not sure he can make it though) [10:42] hm if he can't make it, i suspect the interview won't take the whole hour, co we can do it afterwards too [11:05] pedronis: updated the doc now [11:08] mvo: have you looked more into the boot-state tool? [11:12] mborzecki: I have other meetings after the interview [11:14] mborzecki: was in calls until just now, I have the spread debug shell still open [11:14] mborzecki: I check it now [11:25] mborzecki: mystery solved I think, one sec [11:26] mborzecki: https://github.com/snapcore/snapd/blob/master/tests/lib/tools/boot-state#L107 if run_grub_editenv fails it will then fallback to manipulate it with sed [11:26] * pstolowski lunch [11:27] mborzecki: so yeah, fine to use but probably best to have snap debug set-bootenv or something [11:27] mborzecki: anyway, your call :) [11:27] mvo: uhh, still kind of sucks there isn't even a crc32 of the grub bootenv [11:28] mborzecki: +1 [11:51] PR snapd#9915 closed: snap-confine.apparmor.in: support tmp and log dirs on Yocto/Poky [11:53] mvo: can you cherry pick those patches ^^ to 2.49? [12:12] mborzecki: sure, done [12:12] mvo: thanks! [12:12] mborzecki: they will only make it into a possible 2.49.1 of course [12:13] sure [13:31] hey mborzecki just saw the meeting invite, I'll try to be there in a couple minutes but you can start without me [13:31] ijohnson: sure [13:51] PR snapd#9893 closed: store: support validation sets with fetch-assertions action [14:00] just out of curiosity: Is there a way to refresh a snap if the installed revision's pre-refresh hook has an error that will always cause the hook to abort? Like [14:01] (nmv the “Like”) [14:32] PR snapd#9929 opened: wrappers: use proper paths for mocked mount units in tests [15:00] dot-tobias: not unless you have the user revert the snap to a different revision with `snap revert` and then refresh past the broken one to a new one, or remove it and reinstall it [15:02] PR snapd#9908 closed: snap: rename gdbserver option to `snap run --gdbserver` [15:02] PR snapd#9930 opened: asserts: pool changes and RefreshValidationSetAssertions method for validation-sets [15:03] pedronis: so the main issue with my repair branch is just that this new test account-key should have authority-id and account-id set to "testrootrepair" ? [15:03] if so I can fix that easily [16:02] ijohnson: Thanks for clarifying! Only affects the edge channel, so shouldn't be a huge problem as it's only for internal testing and a handful of “I know things might break” users. [16:21] Hi all, going back to updating my gadget from 18 to 20, as suggested I copied the logic from rpi boot.scr (https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1871831) however I have 2 issues: [16:21] Bug #1871831: Consolidate Core and Classic bootscripts [16:21] 1- the CRC of boot.sel seems to be wrong or missing as my uboot can't import boot.sel [16:22] 2- even when removing the CRC check, it seems like I'm missing things as the recovery install doesn't do anything [16:23] see this log when it fails: https://gist.github.com/gibsson/c09efaa2da7cd8b7c330cef8f4eb3cbb [16:23] for 1) who generates the recovery boot.sel? where can I check that the CRC is generated? [16:25] for 2) can I enable some debug outputs to know more? seems to be looking for a writable LABEL but I don't understand how this could work on pi: https://github.com/snapcore/pi-gadget/blob/20-arm64/gadget.yaml [16:27] ijohnson: no, they both need to be testrootorg [16:52] pedronis: why do they both need to be testrootorg? it seems misleading since we are creating an additional account-key with account-id of testrootorg and even signed by the other testrootorg account-key [16:52] ijohnson: sounds we need a chat [16:52] hmm ok, I have 5 minutes right now ? [16:53] ijohnson: going to the SU [17:37] PR snapd#9931 opened: asserts: repeat the authority cross-check in CheckSignature as well [17:46] ijohnson: ^ [17:47] thanks, just got done with the interview, so I'll loop back on that now [17:56] ijohnson: np, no super hurry, but it's definitely the kind of things that was easier to do immediately than queue it for me [17:57] PR snapd#9929 closed: wrappers: use proper paths for mocked mount units in tests === ijohnson is now known as ijohnson|lunch [18:48] PR snapd#9916 closed: daemon: move postSnap and inst.dispatch tests to api_snaps_test.go === ijohnson|lunch is now known as ijohnson [21:08] PR snapd#9923 closed: o/snapstate/check_snap.go: add support for many subversions in assumes snapdX [21:32] I changed my login.ubuntu.com username but it did not change my Snap Store ID, why ? [21:33] Also where can I find roadmr, I don't see him here these days ? [21:39] ijohnson: I commented on your questions in the standup doc [21:39] ah thanks pedronis [22:23] PR snapd#9932 opened: [RFC] o/configstate/configcore: support snap set system swap.size=