One worrying thing we discussed today with YuanChen Cheng about the fwupd situation is the fact of an unversioned dependency on libjcat1 right now. I am a bit concerned that there is no versioned dep in neither of the packages, meaning that some users might only upgrade fwupd but not libjcat1 and therefore not be able to get the latest firmware upgrades. So they'd have to upgrade fully to get this experience.
This, however, is seemingly also the case in jammy and even in Debian with 1.7.6-1. I think with the nearest follow up upload we need to make sure that users upgrading to latest fwupd also get the latest dependencies. From what YuanChen told me, it seems to not cause any breakages, simply inability to get the latest firmware (older ones are fine). Even though this is not a perfect situation, I guess we can live with it for a short moment.
One worrying thing we discussed today with YuanChen Cheng about the fwupd situation is the fact of an unversioned dependency on libjcat1 right now. I am a bit concerned that there is no versioned dep in neither of the packages, meaning that some users might only upgrade fwupd but not libjcat1 and therefore not be able to get the latest firmware upgrades. So they'd have to upgrade fully to get this experience.
This, however, is seemingly also the case in jammy and even in Debian with 1.7.6-1. I think with the nearest follow up upload we need to make sure that users upgrading to latest fwupd also get the latest dependencies. From what YuanChen told me, it seems to not cause any breakages, simply inability to get the latest firmware (older ones are fine). Even though this is not a perfect situation, I guess we can live with it for a short moment.