Package rpminstall-tests: Information

  • Default inline alert: Version in the repository: 1.1.3-alt8

Source package: rpminstall-tests
Version: 1.1.3-alt6
Latest version according to Repology
Build time:  Jul 4, 2020, 04:02 AM in the task #254442
Report package bug
License: GPLv2+
Summary: Tests for rpm: how it interprets packages when installing
Description: 
Tests for rpm: how it interprets packages when installing.

Now, it tests how various forms of constraints (Requires, Conflicts, Obsoletes)
are interpreted when they are installed together with packages with
various forms of matching Provides.

More tests can appear.

List of rpms provided by this srpm:
rpminstall-tests (noarch)
rpminstall-tests-archcompat-checkinstall (noarch)
rpminstall-tests-archcompat-with-proc-checkinstall (noarch)
rpminstall-tests-checkinstall (noarch)

Maintainer: Ivan Zakharyaschev

List of contributors:
Ivan Zakharyaschev

ACL:
Ivan Zakharyaschev
@everybody

    1. make
    2. rpm
    3. rpm-build
    4. rpm-build-licenses
    5. tmpdir.sh

Last changed


July 3, 2020 Ivan Zakharyaschev 1.1.3-alt6
- Run additionally a test with a package built for system rpm's ARCH
  (i.e., with rpmbuild --target set to it).
- Ignore an arch_compat test on ARM (the one introduced in 1.1.3-alt5:
  with the default arch on this machine) until better times, because
  the ARM arch detection in rpm-build (<= 4.0.4-alt141) is not ideal yet.
June 30, 2020 Ivan Zakharyaschev 1.1.3-alt5
- Also test the compatibility between `uname -m`, rpmbuild, and rpm -i.
  (A separate archcompat-checkinstall subpkg does this.)
- First, run a simple test (to fail fast).
June 4, 2019 Ivan Zakharyaschev 1.1.3-alt4
- To catch more errors:
  + in upgradable.mk strictly_newer_* helpers, separated the xfail reasons:
    a special reason for xfailing just the asymmetry test
    (i.e., a pair of pkgs non-upgradable in bad direction),
    and another one for xfailing just the upgrade test
    (i.e., the same pair of pkgs upgradable in good direction).
  (Now, the tests failing for one of the two reasons which is not marked as xfail
  will just fail rather than xfail. Previously, we couldn't distinguish them
  and could overlook a real unexpected failure.)