[Lvfs-announce] Migrating legacy groups to vendor-id restricted (2)
Richard Hughes <[email protected]> Fri, 26 Feb 2021 08:40:46 +0000
| Newsgroups | dev.linux.lists.lvfs-announce |
|---|---|
| Message-ID | <CAD2FfiHmFXeqbXLZBiTF0xZmfV+Lo4zuKevqeA_0FOHczSdmmQ@mail.gmail.com> |
Hi all, In September I announced I was making all the embargo remotes require a vendor ID. This happened as planned, and now I'm doing the same for the public remotes. See https://lists.linuxfoundation.org/pipermail/lvfs-announce/2020-September/000049.html for more information about what was required and why we're making the LVFS more secure. If you've accidentally forgotten to tell me your vendor IDs, or if you need additional vendor IDs added to your account please email me. I can make vendor-id changes immediately with no firmware or code changes required. If you get any errors while testing firmware like: Not compatible with vendor: failed predicate: [XXX:NEVER_GOING_TO_MATCH eq ATA:0x14A4] (for old versions of fwupd) Metadata has no vendor ID Not compatible with vendor ATA:0x14A4: got ATA:0x1523 (for newer versions) ...then please send me an email with the error message and the output of "fwupdmgr get-devices --verbose". Many thanks, Richard.