The RPM package management system
40c682ecfc
Running a build through the RHEL OSCI reveals some possible shortcomings of the original design: - Custom macros using %__gpg may now easily break if the Sequoia backend is installed, such as those overriding %__gpg_sign_cmd where %__gpg is typically the first argument, followed by CLI options only known to GnuPG. This is exactly the case with some of our Beaker tests. - Some tests attempt to install both subpackages directly with dnf which obviously fails as they conflict with each other. This is just a test issue, though. Therefore, the boolean dependency in rpm-sign-libs declaring that both implementations are equally compatible is just wrong, until we can prove otherwise, by making the CI tests pass, for starters. Drop the Sequoia subpackage for now. This is less drastic than a full revert since the actual GnuPG split-off is still reasonable on its own. We can always add Sequoia support back later, once we figure out the above issues. Related: RHEL-56363 |
||
|---|---|---|
| .fmf | ||
| plans/internal | ||
| tests | ||
| .gitignore | ||
| 0001-Fix-memory-leak-in-rpmsign.patch | ||
| 0001-Fix-potential-use-of-uninitialized-pgp-struct.patch | ||
| 0001-Fix-potential-use-of-uninitialized-pipe-array.patch | ||
| 0001-Fix-regression-in-Lua-scriptlet-runaway-child-detect.patch | ||
| 0001-Refactor-sign-command-expand-and-parse-out-of-runGPG.patch | ||
| 0002-Eliminate-hardcoded-GPG-references-from-user-visible.patch | ||
| 0003-Declare-signCmd-static.patch | ||
| ci.fmf | ||
| gating.yaml | ||
| macros.rpmsign-gnupg | ||
| rpm-4.7.1-geode-i686.patch | ||
| rpm-4.9.90-no-man-dirs.patch | ||
| rpm-4.17.x-rpm_dbpath.patch | ||
| rpm-4.18.90-weak-user-group.patch | ||
| rpm-4.18.92-disable-sysusers.patch | ||
| rpm-4.18.x-siteconfig.patch | ||
| rpm-4.19.1.1-nogpg.patch | ||
| rpm.spec | ||
| rpmdb_migrate | ||
| rpmdb-migrate.service | ||
| rpmdb-rebuild.service | ||
| sources | ||
| STAGE2-rpm | ||