[Lvfs-announce] New features on the LVFS
Richard Hughes <[email protected]> Sun, 27 Jan 2019 09:06:30 +0000
| Newsgroups | dev.linux.lists.lvfs-announce |
|---|---|
| Message-ID | <CAD2FfiHPrSc0OFbmufoHW_GU22D6j-ErODOZDtvae8Jm14rTUA@mail.gmail.com> |
Hi all, This weekend we deployed two new, smaller, features on the LVFS. * The first feature is only important if you are distributing GPL licensed firmware on the LVFS. If you are, there is a new source type URL to include the <releases> section in your metainfo file. This should point to the release-specific source code that can be used to rebuild the binary from the code. GPL firmware without source information can no longer be moved to testing or stable. You can also edit or add the source URL in the existing "Update Details" section in the component view. * The second feature may be useful to larger OEMs and is available for both free and proprietary firmware. There are currently quite strict limits on the format of the release ChangeLog included in the <description> part of the metainfo, or edited on the LVFS. For instance, OEMs are not allowed to include links within the text and have to adhere to a style guide. All firmware can now specify a URL like <url type="details"> within the <release> section. This could point to a website page or PDF description of the specific release. This would allow vendors to provide more information about specific CVEs or detailed technical information. Whist the update details should still be considered the "primary" method to convey information about the firmware release, the URL may be useful too in some cases. In time, fwupdmgr and gnome-software will show both new URLs if set. Both new tags are documented in more detail here: https://fwupd.org/lvfs/docs/metainfo/urls A reminder for those that joined the mailing list recently, last week we added the 2 factor authentication feature which I encourage you to enable if not using OAuth: https://lists.linuxfoundation.org/pipermail/lvfs-announce/2019-January/000010.html Richard