osbuild-ci: explicitly install python3-dnf package #81
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is due to upstream bug: rpm-software-management/dnf5#1848 Signed-off-by: Tomáš Hozza <[email protected]>
This package is needed for the DNF4 Python API bindings, which we need for testing e.g. the SBOM functionality. With F41 not installing it by default, the tests are now skipped, which is not good. Example: https://github.com/osbuild/osbuild/actions/runs/11729332192/job/32674732154#step:3:266 Signed-off-by: Tomáš Hozza <[email protected]>
Resolves the following error: ``` No match for argument: development tools ``` Keep the old group name for CentOS Stream image builds. Signed-off-by: Tomáš Hozza <[email protected]>
Something must have happened to the GCP repository, because we have been building the 'cloud-tools' container for both aarch64 and x86_64 for the past 2 years, but using a GCP repository that hard-coded the x86_64 arch in its URL. And so far everything worked just fine. However, the aarch64 builds now started to fail on installation of x86_64 packages. Use the el0 version of the repository and don't specify the architecture explicitly in the URL, but let DNF substitute it based on the host arch. Signed-off-by: Tomáš Hozza <[email protected]>
thozza
force-pushed
the
osbuild-ci-dnf4-module
branch
2 times, most recently
from
4dc62f0
to
bcc44f6
Compare
The c10s container contains newer packages than the ones that are available in the repositories. Therefore we are running into a situation when DNF would need to downgrade some packages, in order to install the requested package set. This fails, unless the --nobest options is passed to DNF. Extend the dnf.py script and osbuild-ci.Dockerfile, to allow using the --nobest option if needed. Use the option for the c10s osbuild-ci container. Signed-off-by: Tomáš Hozza <[email protected]>
thozza
force-pushed
the
osbuild-ci-dnf4-module
branch
from
bcc44f6
to
157dea1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explicitly install
python3-dnf, which provides the DNF4 Python API bindings. We need them for testing e.g. the SBOM functionality. With F41 not installing it by default, the tests are now skipped, which is not good.Example:
https://github.com/osbuild/osbuild/actions/runs/11729332192/job/32674732154#step:3:266
Additional fixes:
--to signify the end of command line options not accepted bydnfCLI any more rpm-software-management/dnf5#1848.