User/jocelynb/add fwupd spec

[JocelynBerrendonner]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

What does the PR accomplish, why was it needed?
The PR introduce the fwupd package and its dependencies to the SPECS-EXTENDED folder (all the code is contained within SPECS-EXTENDED). Package definitions were pulled from the Fedora repository and subsequently modified to match the Azure Linux requirements. The source code was pulled from the Fedora servers.

Change Log

New Packages:

• Flashrom - https://flashrom.org
• fwupd-efi - https://github.com/fwupd/fwupd-efi
  - patched for azl compat
• fwupd - https://github.com/fwupd/fwupd
  - redfish improvements
• gi-docgen - https://gitlab.gnome.org/GNOME/gi-docgen
• libcbor - http://libcbor.org
• libjaylink - https://gitlab.zapb.de/libjaylink/libjaylink
• libusb1 - https://libusb.info
• passim - https://github.com/hughsie/passim
• python-breathe - https://github.com/michaeljones/breathe
  - 2 patches
• python-cbor2 - https://github.com/agronholm/cbor2
• python-flit-core - https://flit.pypa.io/
• python-smartypants - https://github.com/leohemsted/smartypants.py
• python-typogrify - https://github.com/mintchaos/typogrify
• python-uswid - https://github.com/hughsie/python-uswid
• python-sphinxcontrib-jquery - https://github.com/sphinx-contrib/jquery/
• umockdev - https://github.com/martinpitt/umockdev

Package Upgrades:

• SPECS-EXTENDED/libblockdev/libblockdev.spec
  - spec config change
• SPECS-EXTENDED/libjcat/libjcat.spec
  - 0.1.6 to 0.2.2
• SPECS-EXTENDED/libxmlb/libxmlb.spec
  - 0.3.11 to 0.3.21

Does this affect the toolchain?

NO

Associated issues

n/a (this PR only introduces new code)

Links to CVEs

n/a (this PR only introduces new code)

Test Methodology

• Locally built and manually tested the resulting binary on a test box.
• Successfully ran a buddy build on the code: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=728998&view=results

[bfjelds]

• i think the version-iteration of new packages should match the upstream version being imported, seems inconsistent in the PR. there are some that use the same version (i think this is correct), some that increment the version.

• ensure that the changelog version matches what is declared in the spec.

• i think that only downloaded files need to be in the signature file, so patch files that are in the PR don't need to be included.

[JocelynBerrendonner]

• i think the version-iteration of new packages should match the upstream version being imported, seems inconsistent in the PR. there are some that use the same version (i think this is correct), some that increment the version.
• ensure that the changelog version matches what is declared in the spec.
• i think that only downloaded files need to be in the signature file, so patch files that are in the PR don't need to be included.

Thanks for the great feedback. What I understand from the build team is:

• As per Andrew's guidance, the version and release numbers in the Azure Linux spec file need to be increased by one when pulling/adapting a spec from Fedora (so, there is some revv'ing up of these numbers)
• You are correct about not having patch files as part of the signature file. To clarify, as per the build team, all the files mentioned as "Sources" in the spec file must have their signature in the signature json file. Other files don't.

[JocelynBerrendonner]

Successfully ran a buddy build on the code: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=728998&view=results