This article provides answers to some of the most common questions about Azure Linux packages, including how to add packages, upgrade models, and debug symbol packages.
A package I need isn't available in Azure Linux. How do I add it?
Use mock or azldev to build custom RPMs for Azure Linux. You can then include your custom RPMs in a custom image using Image Customizer. For more information, see Build RPMs for Azure Linux and Customize images with Image Customizer.
Are packages ever bumped to take non-CVE bug fixes?
The preferred approach remains backporting. However, bug fixes and other business-driven justifications are valid reasons to upgrade a package outside of CVE remediation.
What is the requirement for a patch to land on Azure Linux?
Like other Linux distributions, Azure Linux prefers that changes to open-source projects are merged upstream first. We take upgrades or patches only if they're accepted by the upstream maintainers. Under critical situations with reasonable business justification, a hotfix patch can be discussed.
What is the Azure Linux package repository structure?
For more information, see Azure Linux package repositories overview.
Where can I find debug symbol packages for Azure Linux?
Debuginfo packages for Azure Linux are published in a separate repository under packages.microsoft.com. For more information, see Install debug symbol packages on Azure Linux.
How do I find packages, and how can I identify which package provides a specific file or binary?
Use DNF commands such as:
dnf search: Finds packages related to a keyword.dnf provides: Identifies which package supplies a specific file or binary.
For more information, see Manage Azure Linux packages with DNF5.