cups-filters

Overview

cups-filters is the OpenPrinting filter and backend package used with CUPS 2.x on non-Mac systems. It provides the print-job processing pieces that CUPS uses when a job needs filtering, conversion, or backend handling before it reaches a printer. The upstream project describes it as the set of filters, backends, and related utilities needed for that printing stack. (github.com)

In a Linux distribution, this package exists so CUPS can process a wider range of print jobs and printer workflows without depending on the upstream source tree at build time. The exact set of files shipped by the RPM is defined by the spec file and the sources stored in this dist-git repository.

Purpose and typical use cases

Typical use cases include:

• processing print jobs for CUPS-managed printers,
• converting document formats into printer-ready output,
• supporting legacy and driver-based printing workflows where the distribution still needs them,
• providing helper utilities used by the printing stack.

Typical users include:

• desktop users who print through CUPS-backed applications,
• system administrators maintaining local print services,
• developers working on the printing stack,
• CI/CD and release engineers validating package rebuilds,
• security engineers reviewing update impact on the printing path.

Upstream project

Upstream is maintained by OpenPrinting. The canonical project repository is the OpenPrinting cups-filters GitHub project. The upstream project documentation and release pages are the best starting points for understanding current behavior and build expectations. (github.com)

NiceOS maintainers should verify upstream release notes and build changes before each update, especially when upstream changes filter behavior, install paths, or the way helper tools are discovered by CUPS.

Dist-git repository contents

This RPM dist-git repository is organized as follows:

• SPECS/ — RPM spec files and packaging logic.
• SOURCES/ — source-manifest metadata and any packaging-side source references.
• METADATA/ — repository metadata used by the packaging workflow.
• SBOM/ — software bill of materials artifacts, when present.

The repository does not store large upstream source archives directly in Git. That keeps the repository small and makes review easier. Instead, source integrity is tracked through manifest files in SOURCES/.

Source storage and integrity policy

For this package, the source policy is to keep large upstream archives out of the Git history and record source integrity through SOURCES manifests instead. That means maintainers should check the manifest entries, the spec file source references, and any accompanying metadata when reviewing an update.

Do not rely on the presence of a local archive in the repository. If a source file, manifest entry, or packaging reference changes unexpectedly, NiceOS maintainers should verify whether the change is intentional and whether the corresponding upstream artifact is the one that should be packaged.

NiceOS maintenance notes

Before updating this package, check the following:

• confirm the upstream release notes for packaging-impacting changes,
• verify that the spec file still matches upstream install paths and build options,
• review whether any SOURCES manifest entries need regeneration,
• check whether SBOM/ artifacts need to be refreshed,
• confirm that file lists, licenses, and installed helper paths still match the build output,
• look for behavior changes in filters, backends, or helper utilities that might affect printing workflows.

Pay special attention to these risks:

• changes in upstream build systems that alter generated files or install locations,
• renamed or removed helper tools,
• changes that could affect CUPS integration or printer discovery,
• packaging drift between spec logic and upstream defaults.

If a detail is uncertain, NiceOS maintainers should verify it before relying on it.

Build and verification checklist

For RPM maintenance, a practical checklist is:

• inspect the spec diff before merging,
• confirm the source manifest in SOURCES/ matches the intended upstream artifact,
• rebuild the SRPM and binary RPMs in a clean environment,
• review build logs for missing dependencies, path changes, or file-install warnings,
• run packaging sanity checks such as file ownership, permissions, and scriptlet behavior,
• verify that installed binaries, libraries, filters, or helpers land in the expected paths,
• compare the package contents against prior builds to spot unexpected removals or additions,
• if available, run basic print-path smoke tests or integration tests relevant to the package,
• check that SBOM data, if maintained here, still matches the rebuilt artifacts.

References

• OpenPrinting/cups-filters
• cupsfilter(8) manual page
• OpenPrinting CUPS project

Russian documentation

See README_RU.md.

Dist-git repository notes

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