a52dec

Overview

a52dec is the RPM package for the small test program shipped with liba52. In practical terms, it is part of the tooling around ATSC A/52, also known as AC-3, audio streams. The upstream project is liba52, which provides decoding support for those streams. a52dec is useful when a distribution needs to package the upstream test utility alongside the library and related documentation, rather than treating it as an ad hoc extra. (sourceforge.net)

Purpose and typical use cases

Typical uses include:

• checking that the package builds cleanly with the expected toolchain,
• exercising the upstream decoder test program during packaging or QA,
• providing a command-line utility that can be used when diagnosing A/52 or AC-3 handling on a system,
• keeping the upstream package split in a form that is convenient for distribution maintenance.

The most common users are RPM maintainers, distribution integrators, QA engineers, and developers who need a small reference utility while working on liba52-related packages. Desktop users are not usually the primary audience for this package.

Upstream project

The upstream project is liba52, an open-source project described as a free ATSC A/52 audio stream decoder. Public package documentation also identifies a52dec as a small test program for liba52. If you need to rely on upstream history, release cadence, or current maintenance status, NiceOS maintainers should verify those details directly in upstream sources before making packaging decisions. (sourceforge.net)

Dist-git repository contents

This dist-git repository is the packaging source for NiceOS. It normally contains:

• SPECS/ — RPM spec files and any packaging logic,
• SOURCES/ — source manifests and related metadata used to track imported sources,
• METADATA/ — repository metadata used by the packaging workflow,
• SBOM/ — software bill of materials material, if maintained for this package.

The repository is meant to hold packaging inputs and metadata, not the full upstream source tree.

Source storage and integrity policy

Large upstream source archives are intentionally not stored in this Git repository. Instead, source integrity is tracked through manifest files in SOURCES/.

For maintainers, this means:

• verify that the SOURCES/ manifest still matches the imported upstream source,
• confirm that any source re-import was done from the intended upstream release or tag,
• check whether ancillary files need to be refreshed together with the source import,
• avoid relying on files that are not represented in the manifests.

Do not treat the Git tree as the authoritative storage for large upstream tarballs or release payloads.

NiceOS maintenance notes

Before updating this package, NiceOS maintainers should check:

• whether upstream still provides the same test program and related files,
• whether the spec file needs refresh for changed build systems, install paths, or compiler flags,
• whether any generated packaging files, manifests, or SBOM data need regeneration,
• whether the upstream tarball layout changed in a way that affects %prep or %install,
• whether bundled examples or tests still behave as expected on current toolchains,
• whether a package split or file list adjustment is needed if upstream adds or removes files.

Risks to consider:

• the upstream project is small and may change infrequently, so stale packaging assumptions can linger,
• generated files may drift if they are not rebuilt after a source update,
• build failures may appear when modern compilers or RPM macros interpret old build scripts more strictly.

If a detail is uncertain, NiceOS maintainers should verify it in the spec, the imported source, or upstream documentation before relying on it.

Build and verification checklist

For a routine RPM update, check the following:

• confirm the upstream source reference is correct and complete,
• verify the SOURCES/ manifest matches the imported source payload,
• inspect the spec for obsolete patches, paths, or build flags,
• build the SRPM and binary RPMs in a clean environment,
• run any available package tests or smoke checks,
• confirm the files installed by the package match the expected payload,
• review the changelog and packaging metadata for consistency,
• if SBOM data is maintained, regenerate or validate it after the source update,
• compare the resulting package contents against the previous build to spot unintended removals or additions.

References

• liba52 project on SourceForge
• a52dec package information in Debian manpages
• a52dec package page in Fedora

Russian documentation

See README_RU.md for the Russian version of this document.

Dist-git repository notes

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