Jan Lübbe

We've split off the simple fix as #977. When that is merged, only the seed slot handling remains. At that point, we should probably change it to use `slot->ext_mount_point` as...

As the user should not need to know which image (A/B) is active or being installed to, specifying the location of the previously installed `.caibx` on the command line is...

Since https://github.com/rauc/rauc/pull/925, we now have a shared data directory where the `.caibx` for each slot could be stored (see https://github.com/rauc/rauc/pull/817#issuecomment-1158692257).

As far as I can see, the logged warning is the only effect of this issue. Note that RAUC only sends one `NBD_CMD_DISCONNECT`, the other is generated by the kernel...

> It looks like `clear_slot` always clears the entire "device" before writing the new slot. This can be problematic for devices which "abuse" the boot0 partition by storing additional data...

> > RAUC has some tradition of trying to make it harder to make design errors, so I'm skeptical. One approach might be to reuse the `region-start/-size` options from https://rauc.readthedocs.io/en/latest/advanced.html#update-boot-partition-in-gpt....

Sorry, but there are currently no external error codes. My preferred approach would be to define error codes on the DBus level. @ejoerns took a quick look at that some...

As this feature is not on our roadmap so far, I can only offer to review any PRs which work towards this.

Yes, this feature was one of the reasons why we choose CMS. So far, adding signatures or n-of-m checking during verification is not implemented. We'd be happy to review and...

Could you attach gdb to the running rauc process in that situation and get a backtrace? It should be blocked in g_subprocess_wait_check() and not use any CPU time while the...