/
githubmirror
/
rpm
ОбзорДокументацияВойти
/
githubmirror
/
rpm
Код
Запросы
0
Пакеты
0
Релизы
0
Аналитика
Безопасность
ДокументацияПоддержка
Политика конфиденциальностиПользовательское соглашениеПолитика использования «cookies»Согласие субъекта персональных данных
2026 ©
rpm/
tests/pinned/
..
common

Add a SHA3 header digest to v6 packages

год назад
README

Add a small blurb about sanity checks to the pinned tests

3 года назад
rpmlibver.sh

Add support for "pinned" tests

3 года назад
rpmlibver.txt

Bump our soname minor version to match that of 6.1

3 месяца назад
rpmsigdig.sh

Split our reproducability tests to further helpers to allow reuse

2 года назад
rpmsigdig.txt

Bump version to 6.1.90 to begin the 6.2 devel cycle

3 месяца назад
rpmsigdig6.sh

Add tests for v6 package structure and digests, equal to v4 just now

2 года назад
rpmsigdig6.txt

Bump version to 6.1.90 to begin the 6.2 devel cycle

3 месяца назад
update

Add support for "pinned" tests

3 года назад
README
PINNED TESTS
============
 
This directory contains tests whose expected output needs to be "pinned" to a
specific commit, typically one that bumps the RPM version number. This output
usually can't be generated by other means during test runtime so it has to be
tracked in git alongside the sources and updated whenever a change in those
triggers a change in the output.
 
A typical example of such a test is one that covers reproducible package builds
by clamping file mtimes to SOURCE_DATE_EPOCH and making sure the package digest
is always the same. However, since packages carry the version of RPM used to
build them in a tag, the digests have to be updated whenever the version is.
 
USAGE
-----
 
The tests are used via the m4 macro RPMTEST_CHECK_PINNED([<name>]) where <name>
is the respective filename (without an extension) found in this directory. The
macro then sources the script <name>.sh and compares its standard output with
the contents of <name>.txt.
 
To pin the *.txt files to the current commit, run "make pinned" from the build
directory. This will run all the *.sh tests, capture their output and store it
in the corresponding *.txt files in your source directory, then automatically
git-stage the changes and print the diff (if any).
 
MANUALLY SANITY-CHECK ALL CHANGES TO THESE VALUES! Ie. when the values
change, always ensure you understand WHY before proceeding. And vice
versa: when you expect a change (such as rpm version change), ensure it
actually happens.