Skip to content

playbooks, test/system: Drop the PODMAN and SKOPEO environment variables#1592

Merged
debarshiray merged 3 commits intocontainers:mainfrom
debarshiray:wip/rishi/playbooks-test-system-drop-PODMAN-environment-variable
Nov 14, 2024
Merged

playbooks, test/system: Drop the PODMAN and SKOPEO environment variables#1592
debarshiray merged 3 commits intocontainers:mainfrom
debarshiray:wip/rishi/playbooks-test-system-drop-PODMAN-environment-variable

Conversation

@debarshiray
Copy link
Copy Markdown
Member

No description provided.

@softwarefactory-project-zuul
Copy link
Copy Markdown

@debarshiray debarshiray force-pushed the wip/rishi/playbooks-test-system-drop-PODMAN-environment-variable branch from 1e9c1b6 to 95be6f7 Compare November 12, 2024 21:46
The package providing /usr/share/pkgconfig/bash-completion.pc changed
from bash-completion to bash-completion-devel in Fedora 41 onwards [1].
This meant that the Bash completions were no longer being generated and
installed by the CI.

[1] Fedora bash-completion commit d1f5dc48c0440cc6
    https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc6
    https://bugzilla.redhat.com/show_bug.cgi?id=1457164

containers#1593
@softwarefactory-project-zuul
Copy link
Copy Markdown

Unlike Fedora, where the package providing bash-completion.pc changed in
Fedora 41 onwards [1,2], it hasn't changed in CentOS Stream 9.  So, this
doesn't change the behaviour of the CI.

However, the Fedora Packaging Guidelines recommend using pkgconfig(...)
to depend on a *.pc file [3], instead of the name of the package, and
there has been a problem on Fedora caused by not doing that.  Therefore,
it's better to follow the guidelines for consistency and safety.

[1] Fedora bash-completion commit d1f5dc48c0440cc6
    https://src.fedoraproject.org/rpms/bash-completion/c/d1f5dc48c0440cc6
    https://bugzilla.redhat.com/show_bug.cgi?id=1457164

[2] Commit 2049199
    containers@204919917e4af528

[3] https://docs.fedoraproject.org/en-US/packaging-guidelines/PkgConfigBuildRequires/

containers#1593
The toolbox(1) binary always relies on the PATH environment variable to
find the podman(1) and skopeo(1) binaries.  There's no way to override
those with the PODMAN and SKOPEO environment variables, and they only
affect any direct use of podman(1) and skopeo(1) within the test suite.

Therefore, offering the PODMAN and SKOPEO environment variables in their
current form is needlessly confusing and misleading, and can lead to
surprises arising from different podman(1) and skopeo(1) binaries being
used in different places.  Either toolbox(1) should also honour them or
the test suite shouldn't offer them.  The former is more complicated
without any obvious need for it, so the latter was chosen.

containers#1592
@debarshiray debarshiray force-pushed the wip/rishi/playbooks-test-system-drop-PODMAN-environment-variable branch from 95be6f7 to fbffd45 Compare November 14, 2024 01:07
@softwarefactory-project-zuul
Copy link
Copy Markdown

@debarshiray
Copy link
Copy Markdown
Member Author

recheck

@softwarefactory-project-zuul
Copy link
Copy Markdown

@debarshiray
Copy link
Copy Markdown
Member Author

recheck

@softwarefactory-project-zuul
Copy link
Copy Markdown

@debarshiray debarshiray merged commit fbffd45 into containers:main Nov 14, 2024
@debarshiray debarshiray deleted the wip/rishi/playbooks-test-system-drop-PODMAN-environment-variable branch November 14, 2024 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant