Mario Limonciello
Mario Limonciello
I suspect that this is just a bug in older fwupd 1.9.x releases, there shouldn't be anything we can or will do about it.
> It looks like fwupd is broken now on Fedora 39: > > ``` > $ fwupdmgr refresh > Updating lvfs > Downloading… [************************************** ] > Successfully downloaded new metadata:...
Something I think worth asking; _why_ generate the tar.xz and the detached signature in the first place? Github will generate a .zip and .tar.gz for you **when you tag**. It's...
> The tag is signed with the same key, so the issue still stands. Ah true. > But also those are not signed, so you can't verify their integrity after...
> I'm also wondering if we can just use https://github.com/fwupd/fwupd/archive/refs/tags/1.9.16.tar.gz -- and then maybe upload a sha256 hash of that, and a detached signature perhaps -- but maybe we don't...
There is another device on the market that works similar to this; the Dell WD19TB4. The thunderbolt NVM can be flashed both from the thunderbolt plugin or the intel-usb4 plugin....
Sure; I think if they can be reported we could tear out that plugin rule while breaking ABI too.
> btw, what if instead of shadowing devices with equivalent id, I'll try another approach, set virtual parent and update it via any available child (by priority): > ``` >...
In this context it means that firmware updates "have been" made available for devices on a supported fwupd remote like lvfs (or which could happen to be a local remote)....