dejavu-fonts

Overview

DejaVu Fonts is a font family distributed in several styles, including sans, serif, and monospace variants. The upstream project publishes downloadable font sources and related documentation on its official site. For NiceOS, this package exists so the distribution can provide a maintained font set with broad Unicode coverage for text rendering, documents, terminals, and other applications that rely on system fonts. (dejavu-fonts.github.io)

In a Linux distribution, a font package like this is usually consumed by desktop environments, applications, document toolchains, and any software that needs predictable fallback fonts. NiceOS maintainers should verify the exact usage in the distribution before relying on any narrower assumption. (github.com)

Purpose and typical use cases

Typical use cases include:

• system font fallback for desktop applications;
• rendering text in documents and office files;
• use in terminals and developer tools where a monospace font is needed;
• general-purpose UI text where broad script coverage matters.

Typical users include desktop users, administrators, developers, and build or CI/CD maintainers who need a consistent font package available in the system or build environment. Security engineers may also care about the package as part of a controlled software inventory, but this README does not claim any special security properties beyond normal package maintenance. (github.com)

Upstream project

The upstream project is the DejaVu fonts family. The official project site provides downloads and project information, and the GitHub repository contains the upstream source tree and release pages. (dejavu-fonts.github.io)

Canonical upstream references:

• Project site: DejaVu Fonts — Download
• Upstream repository: dejavu-fonts/dejavu-fonts
• Upstream releases: Releases · dejavu-fonts/dejavu-fonts

Dist-git repository contents

This NiceOS dist-git repository is organized as follows:

• SPECS/ — RPM spec files and package metadata used for builds;
• SOURCES/ — source manifests and related integrity metadata;
• METADATA/ — repository metadata used by the packaging workflow;
• SBOM/ — software bill of materials material maintained for the package.

The large upstream source archives are intentionally not stored in this Git repository. Instead, source integrity is tracked through manifest files in SOURCES/. NiceOS maintainers should treat the manifests as the reference for what should be fetched and verified during build preparation. (dejavu-fonts.github.io)

Source storage and integrity policy

This repository follows a manifest-based source policy:

• the Git repository stores small metadata files and source manifests, not the full upstream archives;
• the SOURCES/ manifests describe the expected upstream input;
• integrity checks are performed by comparing the fetched source against the manifest-driven expected state;
• concrete hash values are intentionally not repeated in this README so that it remains stable across updates.

If the upstream project changes its release layout, tag naming, or packaging format, NiceOS maintainers should verify that the manifest workflow still matches the actual upstream source set before updating the package. (dejavu-fonts.github.io)

NiceOS maintenance notes

Before updating this package, NiceOS maintainers should check:

• whether the upstream release or source layout changed;
• whether the SOURCES/ manifest still matches the upstream files that will be fetched;
• whether any RPM spec logic needs adjustment for new or renamed files;
• whether SBOM/ material should be regenerated or reviewed after the source update;
• whether METADATA/ needs a refresh for repository bookkeeping;
• whether the package still installs the font files expected by dependent packages or desktop stacks.

Risks to consider:

• font package changes can affect rendering, fallback selection, and document appearance;
• upstream source layout changes can break manifest-driven fetch or verification steps;
• any file list change may require a spec update to keep the install set accurate.

If any of these points is unclear from the upstream release artifacts, NiceOS maintainers should verify it before relying on the update. (dejavu-fonts.github.io)

Build and verification checklist

For RPM maintenance work, a practical checklist is:

1. Review the upstream release notes or repository state for file layout changes.
2. Confirm that the SOURCES/ manifest matches the intended upstream source input.
3. Regenerate any packaging metadata that depends on the source set, if required.
4. Review the spec for file paths, installed artifacts, and packaging rules.
5. Build the SRPM and RPMs in a clean environment.
6. Inspect the build logs for fetch, unpack, install, and file list warnings.
7. Verify that the expected font files are installed in the package payload.
8. Check that SBOM/ and other repository metadata remain consistent with the new source state, if your workflow uses them.
9. Install the package in a test system or container and confirm that applications can discover the fonts.
10. If dependent packages rely on specific filenames or family names, confirm those expectations before publishing.

References

• DejaVu Fonts — Download
• dejavu-fonts/dejavu-fonts
• Releases · dejavu-fonts/dejavu-fonts

Russian documentation

• See README_RU.md

Dist-git repository notes

• Package repository: rpms/dejavu-fonts
• NiceOS branch: niceos-5.2
• This README is intentionally stable and does not include EVR, source archive checksums or lock hashes.