question
stringlengths 235
464k
| answer
stringlengths 11
2.11k
|
|---|---|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
make: pg_config: Command not found
make: *** No rule to make target 'install'. Stop.
|
The pg_config file was not found and the makefile being called during the make process does not contain the install rule itself
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[ File not found: /builddir/build/BUILD/libqalculate-5.5.2-build/BUILDROOT/usr/lib64/libqalculate.so.23.3.2]: [This indicates that the libqalculate.so.23.3.2 file was not found while trying to package it in the %files part of the build process.]
|
Issue: The file libqalculate.so.23.3.2 file was not found while trying to package it in the %files part of the build process, it does not exist, it's not named correctly or it is not located in the correct directory.
Resolution: Ensure the libqalculate.so.23.3.2 file is located in the correct directory, it is created during the build process and it is named correctly or that the %files section of the spec file contains the correct path and filename.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
File not found: /builddir/build/BUILD/libqalculate-5.5.2-build/BUILDROOT/usr/lib64/libqalculate.so.23.3.2
|
This indicates that the libqalculate.so.23.3.2 file was not found while trying to package it in the %files part of the build process.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[version conflict for package "Tcl": have 9.0.0, need 8.6
while executing
"package require Tcl 8.6"
(file "test/tester.tcl" line 33)]: [Error message]
|
Issue: Mismatched version of dependency, requested version is different from what is provided.
Resolution: Package depends on Tcl version that is not present in Fedora, either fix in upstream or create a patch that fixes the issue.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
version conflict for package "Tcl": have 9.0.0, need 8.6
while executing
"package require Tcl 8.6"
(file "test/tester.tcl" line 33)
|
Error message
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Problem: nothing provides requested (crate(condtype/default) >= 1.3.0 with crate(condtype/default) < 2.0.0~)
You can try to add to command line:]: [cargo crate may not have been added to fedora/copr yet]
|
Issue: unsatisfied dependencies
Resolution: run rust2rpm condtype and upload to spec to same copr project
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Problem: nothing provides requested (crate(condtype/default) >= 1.3.0 with crate(condtype/default) < 2.0.0~)
You can try to add to command line:
|
cargo crate may not have been added to fedora/copr yet
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Finish(bootstrap): chroot init]: [The 'Finish(bootstrap): chroot init' means that Mock finalized bootstrap installation, so there's no problem.]
=============
[Finish: installing minimal buildroot with dnf]: [The "Finish: installing minimal buildroot with dnf" means that even the minimal buildroot was successfully initialized.]
=============
[Start: build phase for rebase-helper-0.28.1-3.fc38.src.rpm]: [The "Start: build phase..." part means that Mock started building the source RPM. ]
=============
[Finish: build phase for rebase-helper-0.28.1-3.fc38.src.rpm]: [Source RPM has been successfully built.]
=============
[Error:
Problem: package python3-sphinx_rtd_theme-1.1.1-2.fc38.noarch from copr_base requires (python3.11dist(sphinx) < 6~~ with python3.11dist(sphinx) >= 1.6), but none of the providers can be installed
- cannot install both python3-sphinx-1:5.3.0-3.fc38.noarch from fedora and python3-sphinx-1:7.2.6-5.fc38.noarch from copr_base
- cannot install the best candidate for the job]: [But `python3-sphinx_rtd_theme` from `copr_base` seems to require non-installable dependencies in buildroot.]
|
Issue: Because the BuildRequires specify a non-installable package.
Resolution: Fix the dependency tree, either python3-sphinx_rtd_theme or python3-sphinx or both.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Finish(bootstrap): chroot init
|
The 'Finish(bootstrap): chroot init' means that Mock finalized bootstrap installation, so there's no problem.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Finish: installing minimal buildroot with dnf
|
The "Finish: installing minimal buildroot with dnf" means that even the minimal buildroot was successfully initialized.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Start: build phase for rebase-helper-0.28.1-3.fc38.src.rpm
|
The "Start: build phase..." part means that Mock started building the source RPM.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Finish: build phase for rebase-helper-0.28.1-3.fc38.src.rpm
|
Source RPM has been successfully built.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Error:
Problem: package python3-sphinx_rtd_theme-1.1.1-2.fc38.noarch from copr_base requires (python3.11dist(sphinx) < 6~~ with python3.11dist(sphinx) >= 1.6), but none of the providers can be installed
- cannot install both python3-sphinx-1:5.3.0-3.fc38.noarch from fedora and python3-sphinx-1:7.2.6-5.fc38.noarch from copr_base
- cannot install the best candidate for the job
|
But `python3-sphinx_rtd_theme` from `copr_base` seems to require non-installable dependencies in buildroot.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[============================= test session starts ==============================
platform linux -- Python 3.13.0, pytest-8.3.4, pluggy-1.5.0
rootdir: /builddir/build/BUILD/mock-5.9-build/mock-git-3857.8f7301c
collected 37 items
tests/plugins/test_rpmautospec.py ............ [ 32%]
tests/test_buildroot.py . [ 35%]
tests/test_buildroot_lock.py .F. [ 43%]
tests/test_config_loader.py . [ 45%]
tests/test_config_templates.py ......x... [ 72%]
tests/test_installed_packages.py . [ 75%]
tests/test_package_manager.py ......... [100%]]: [Test are included into the build process.]
=============
[FAILED tests/test_buildroot_lock.py::test_buildroot_lock_output - TypeError: ...
]: [Test named `test_buildroot_lock_output` has failed during the package build.]
=============
[ def test_buildroot_lock_output():
""" test the buildroot_lock.json file format """
tc, buildroot, plugins = _mock_vars(RPM_OUTPUT, REPOQUERY_OUTPUT)
> _call_method(plugins, buildroot)
tests/test_buildroot_lock.py:137:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/test_buildroot_lock.py:105: in _call_method
method()
py/mockbuild/plugins/buildroot_lock.py:115: in produce_lockfile
fdlist.write(json.dumps(data, indent=4, sort_keys=True) + "\n")
/usr/lib64/python3.13/json/__init__.py:238: in dumps
**kw).encode(obj)
/usr/lib64/python3.13/json/encoder.py:200: in encode
chunks = self.iterencode(o, _one_shot=True)
/usr/lib64/python3.13/json/encoder.py:261: in iterencode
return _iterencode(o, 0)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <json.encoder.JSONEncoder object at 0x7f2a44694a50>
o = <MagicMock name='mock.get_image_digest()' id='139819511716160'>
def default(self, o):
"""Implement this method in a subclass such that it returns
a serializable object for ``o``, or calls the base implementation
(to raise a ``TypeError``).
For example, to support arbitrary iterators, you could
implement default like this::
def default(self, o):
try:
iterable = iter(o)
except TypeError:
pass
else:
return list(iterable)
# Let the base class default method raise the TypeError
return super().default(o)
"""
> raise TypeError(f'Object of type {o.__class__.__name__} '
f'is not JSON serializable')
E TypeError: Object of type MagicMock is not JSON serializable]: [The `test_buildroot_lock_output` test has failed with traceback `TypeError: Object of type MagicMock is not JSON serializable`
The `MagicMock` object is used for mocking the python object so this might be an issue in how the code is tested.]
|
Issue: One of the tests executed as part of the build has failed.
Resolution: Please fix the test or code tested by the test.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
============================= test session starts ==============================
platform linux -- Python 3.13.0, pytest-8.3.4, pluggy-1.5.0
rootdir: /builddir/build/BUILD/mock-5.9-build/mock-git-3857.8f7301c
collected 37 items
tests/plugins/test_rpmautospec.py ............ [ 32%]
tests/test_buildroot.py . [ 35%]
tests/test_buildroot_lock.py .F. [ 43%]
tests/test_config_loader.py . [ 45%]
tests/test_config_templates.py ......x... [ 72%]
tests/test_installed_packages.py . [ 75%]
tests/test_package_manager.py ......... [100%]
|
Test are included into the build process.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
FAILED tests/test_buildroot_lock.py::test_buildroot_lock_output - TypeError: ...
|
Test named `test_buildroot_lock_output` has failed during the package build.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
def test_buildroot_lock_output():
""" test the buildroot_lock.json file format """
tc, buildroot, plugins = _mock_vars(RPM_OUTPUT, REPOQUERY_OUTPUT)
> _call_method(plugins, buildroot)
tests/test_buildroot_lock.py:137:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/test_buildroot_lock.py:105: in _call_method
method()
py/mockbuild/plugins/buildroot_lock.py:115: in produce_lockfile
fdlist.write(json.dumps(data, indent=4, sort_keys=True) + "\n")
/usr/lib64/python3.13/json/__init__.py:238: in dumps
**kw).encode(obj)
/usr/lib64/python3.13/json/encoder.py:200: in encode
chunks = self.iterencode(o, _one_shot=True)
/usr/lib64/python3.13/json/encoder.py:261: in iterencode
return _iterencode(o, 0)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self = <json.encoder.JSONEncoder object at 0x7f2a44694a50>
o = <MagicMock name='mock.get_image_digest()' id='139819511716160'>
def default(self, o):
"""Implement this method in a subclass such that it returns
a serializable object for ``o``, or calls the base implementation
(to raise a ``TypeError``).
For example, to support arbitrary iterators, you could
implement default like this::
def default(self, o):
try:
iterable = iter(o)
except TypeError:
pass
else:
return list(iterable)
# Let the base class default method raise the TypeError
return super().default(o)
"""
> raise TypeError(f'Object of type {o.__class__.__name__} '
f'is not JSON serializable')
E TypeError: Object of type MagicMock is not JSON serializable
|
The `test_buildroot_lock_output` test has failed with traceback `TypeError: Object of type MagicMock is not JSON serializable`
The `MagicMock` object is used for mocking the python object so this might be an issue in how the code is tested.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[/usr/lib/gcc/x86_64-redhat-linux/15/include/omp.h:557:1: error: template with C linkage
557 | template<typename __T>
| ^~~~~~~~
/builddir/build/BUILD/darktable-5.0.1-build/darktable-5.0.1/src/imageio/format/imageio_format_api.h:24:1: note: ‘extern "C"’ linkage started here
24 | extern "C" {
| ^~~~~~~~~~
[ 97%] Linking C shar]: [Use of C++ in scope defined as C code]
|
Issue: Source code has an error which prevents the build
Resolution: Remove C++ code from parts that should only contain C code
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
/usr/lib/gcc/x86_64-redhat-linux/15/include/omp.h:557:1: error: template with C linkage
557 | template<typename __T>
| ^~~~~~~~
/builddir/build/BUILD/darktable-5.0.1-build/darktable-5.0.1/src/imageio/format/imageio_format_api.h:24:1: note: ‘extern "C"’ linkage started here
24 | extern "C" {
| ^~~~~~~~~~
[ 97%] Linking C shar
|
Use of C++ in scope defined as C code
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[E TypeError: unsupported operand type(s) for |: 'type' and 'type']: [cause of the failed tests]
=============
[RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.SpPQzz (%check)
Bad exit status from /var/tmp/rpm-tmp.SpPQzz (%check)]: [reason why the build failed]
|
Issue: Using typing hints for union in Python 3.9 that are supported since Python 3.10
Resolution: Use the backward-compatible `Union[X, Y]`
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
E TypeError: unsupported operand type(s) for |: 'type' and 'type'
|
cause of the failed tests
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.SpPQzz (%check)
Bad exit status from /var/tmp/rpm-tmp.SpPQzz (%check)
|
reason why the build failed
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[
+ scl enable '%{scl}' -
/var/tmp/rpm-tmp.Sgo1r8: line 33: scl: command not fou]: [Missing command 'scl']
|
Issue: Missing utility or script 'scl'
Resolution: Provide 'scl' to the enviroment
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
+ scl enable '%{scl}' -
/var/tmp/rpm-tmp.Sgo1r8: line 33: scl: command not fou
|
Missing command 'scl'
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[FAIL: test_ipa_subdom_server
============================
[==========] tests: Running 13 test(s).
[ RUN ] test_ipa_trust_dir2str
[ OK ] test_ipa_trust_dir2str
[ RUN ] test_ipa_server_create_oneway
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway
[ RUN ] test_ipa_server_create_oneway_kt_exists
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway_kt_exists
[ RUN ] test_ipa_server_create_oneway_kt_refresh_fallback
[sssd] [child_sig_handler] (0x0020): child [75993] failed with status [1].
[sssd] [child_sig_handler] (0x0020): child [75994] failed with status [1].
[sssd] [child_sig_handler] (0x0020): child [75995] failed with status [1].
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [child_sig_handler] (0x0020): child [75996] failed with status [1].
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway_kt_refresh_fallback
[ RUN ] test_ipa_server_create_oneway_kt_refresh_fail
[sssd] [child_sig_handler] (0x0020): child [76001] failed with status [1].
[ OK ] test_ipa_server_create_oneway_kt_refresh_fail
[ RUN ] test_ipa_server_trust_oneway_init
[ ERROR ] --- test_ctx->ipa_ctx->server_mode->trusts
[ LINE ] --- src/tests/cmocka/test_ipa_subdomains_server.c:1002: error: Failure!
[ FAILED ] test_ipa_server_trust_oneway_init
[ RUN ] test_ipa_server_trust_init
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_trust_init
[ RUN ] test_ipa_server_create_trusts
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_trusts
[ RUN ] test_get_trust_direction_inbound
[ OK ] test_get_trust_direction_inbound
[ RUN ] test_get_trust_direction_outbound
[ OK ] test_get_trust_direction_outbound
[ RUN ] test_get_trust_direction_twoway
[ OK ] test_get_trust_direction_twoway
[ RUN ] test_get_trust_direction_notset_root
[ OK ] test_get_trust_direction_notset_root
[ RUN ] test_get_trust_direction_notset_member
[ OK ] test_get_trust_direction_notset_member
[==========] tests: 13 test(s) run.
[ PASSED ] 12 test(s).
[ FAILED ] tests: 1 test(s), listed below:
[ FAILED ] test_ipa_server_trust_oneway_init
1 FAILED TEST(S)
FAIL test_ipa_subdom_server (exit status: 1)]: [Log of the failed test.]
=============
[FAIL: test_ipa_subdom_server]: [Name of the failed test.]
|
Issue: The testsuite failed.
Resolution: Analyse the test failure. If unsure, try contacting upstream for additional assistance.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
FAIL: test_ipa_subdom_server
============================
[==========] tests: Running 13 test(s).
[ RUN ] test_ipa_trust_dir2str
[ OK ] test_ipa_trust_dir2str
[ RUN ] test_ipa_server_create_oneway
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway
[ RUN ] test_ipa_server_create_oneway_kt_exists
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway_kt_exists
[ RUN ] test_ipa_server_create_oneway_kt_refresh_fallback
[sssd] [child_sig_handler] (0x0020): child [75993] failed with status [1].
[sssd] [child_sig_handler] (0x0020): child [75994] failed with status [1].
[sssd] [child_sig_handler] (0x0020): child [75995] failed with status [1].
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [child_sig_handler] (0x0020): child [75996] failed with status [1].
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_oneway_kt_refresh_fallback
[ RUN ] test_ipa_server_create_oneway_kt_refresh_fail
[sssd] [child_sig_handler] (0x0020): child [76001] failed with status [1].
[ OK ] test_ipa_server_create_oneway_kt_refresh_fail
[ RUN ] test_ipa_server_trust_oneway_init
[ ERROR ] --- test_ctx->ipa_ctx->server_mode->trusts
[ LINE ] --- src/tests/cmocka/test_ipa_subdomains_server.c:1002: error: Failure!
[ FAILED ] test_ipa_server_trust_oneway_init
[ RUN ] test_ipa_server_trust_init
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_trust_init
[ RUN ] test_ipa_server_create_trusts
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[sssd] [ipa_get_options] (0x0020): No ipa server set, will use service discovery!
[ OK ] test_ipa_server_create_trusts
[ RUN ] test_get_trust_direction_inbound
[ OK ] test_get_trust_direction_inbound
[ RUN ] test_get_trust_direction_outbound
[ OK ] test_get_trust_direction_outbound
[ RUN ] test_get_trust_direction_twoway
[ OK ] test_get_trust_direction_twoway
[ RUN ] test_get_trust_direction_notset_root
[ OK ] test_get_trust_direction_notset_root
[ RUN ] test_get_trust_direction_notset_member
[ OK ] test_get_trust_direction_notset_member
[==========] tests: 13 test(s) run.
[ PASSED ] 12 test(s).
[ FAILED ] tests: 1 test(s), listed below:
[ FAILED ] test_ipa_server_trust_oneway_init
1 FAILED TEST(S)
FAIL test_ipa_subdom_server (exit status: 1)
|
Log of the failed test.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
FAIL: test_ipa_subdom_server
|
Name of the failed test.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[
Patch #0 (version-fixes.diff):
+ echo 'Patch #0 (version-fixes.diff):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p0 --fuzz=0
patching file cmake/SearchForStuff.cmake
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file cmake/SearchForStuff.cmake.rej
error: Bad exit status from /var/tmp/rpm-tmp.NRkwWV (%prep)]: [Applying a patch in the %prep section failed.]
|
Issue: The build failed because the patch could not be applied. It may happen that when you try it manually, that patch works for you. But rpm uses fuzziness level 0 (patch --fuzz 0). And your patch may be off by a few lines.
Resolution: You need to rebase your Patch0. Apply the patch manually. Resolve conflicts if there are some. And generate a new patch.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Patch #0 (version-fixes.diff):
+ echo 'Patch #0 (version-fixes.diff):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p0 --fuzz=0
patching file cmake/SearchForStuff.cmake
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file cmake/SearchForStuff.cmake.rej
error: Bad exit status from /var/tmp/rpm-tmp.NRkwWV (%prep)
|
Applying a patch in the %prep section failed.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[[ERROR] error: Source option 5 is no longer supported. Use 8 or later.]: [Maven build failure related to the Java compiler not supporting a particular source option.]
=============
[[ERROR] error: Target option 5 is no longer supported. Use 8 or later.]: [Maven build failure related to the Java compiler not supporting a particular target option.]
|
Issue: The Java compiler used during the build is newer than what the upstream build uses and does not support source and target option 5 but at least 8.
Resolution: Inspect the pom.xml file and find a build property affecting the Java source and target options. Set it to the a version supported by the packaged Java compiler.
You may need to patch the sources.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
[ERROR] error: Source option 5 is no longer supported. Use 8 or later.
|
Maven build failure related to the Java compiler not supporting a particular source option.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
[ERROR] error: Target option 5 is no longer supported. Use 8 or later.
|
Maven build failure related to the Java compiler not supporting a particular target option.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[:: [ 09:23:43 ] :: [ BEGIN ] :: start a mock HTTP server :: actually running 'python2 -m SimpleHTTPServer & 1>srv_out 2>srv_err'
/usr/share/beakerlib/testing.sh: line 896: python2: command not found]: [Missing python2 package.]
=============
[:: [ 09:23:47 ] :: [ BEGIN ] :: telnet_err is empty :: actually running '! test -s telnet_err'
:: [ 09:23:47 ] :: [ FAIL ] :: telnet_err is empty (Expected 0, got 1)]: [Failure caused by missing python2.]
=============
[:: [ 09:23:47 ] :: [ BEGIN ] :: telnet_out is not empty :: actually running ' test -s telnet_out'
:: [ 09:23:47 ] :: [ FAIL ] :: telnet_out is not empty (Expected 0, got 1)]: [Failure caused by missing python2.]
=============
[:: [ 09:23:47 ] :: [ BEGIN ] :: compare what telnet received with what was sent :: actually running 'diffdump telnet_out data'
--- /dev/fd/63 2025-02-18 09:23:47.151243575 +0000
+++ /dev/fd/62 2025-02-18 09:23:47.154243644 +0000
@@ -0,0 +1,3 @@
+00000000 68 65 6c 6c 6f 0a 6f 6e 65 0a 74 77 6f 0a 74 68 |hello.one.two.th|
+00000010 72 65 65 0a 62 79 65 0a |ree.bye.|
+00000018
:: [ 09:23:47 ] :: [ FAIL ] :: compare what telnet received with what was sent (Expected 0, got 1)
8888888888888888888888
send: spawn id exp4 not open
while executing
"send "GET /data\r\r""
(file "telnet.expect" line 6)
8888888888888888888888]: [Failure caused by missing python2.]
|
Issue: python2 is not present on the system where the test was run.
Resolution: For RHELLike '>8' or for fedoras, do not use python2 but use python3 instead.
if rlIsRHELLike '>8' || rlIsFedora; then
rlRun "python3 -m http.server & 1>srv_out 2>srv_err" 0 "start a mock HTTP server"
else
rlRun "python2 -m SimpleHTTPServer & 1>srv_out 2>srv_err" 0 "start a mock HTTP server"
fi
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
:: [ 09:23:43 ] :: [ BEGIN ] :: start a mock HTTP server :: actually running 'python2 -m SimpleHTTPServer & 1>srv_out 2>srv_err'
/usr/share/beakerlib/testing.sh: line 896: python2: command not found
|
Missing python2 package.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
:: [ 09:23:47 ] :: [ BEGIN ] :: telnet_err is empty :: actually running '! test -s telnet_err'
:: [ 09:23:47 ] :: [ FAIL ] :: telnet_err is empty (Expected 0, got 1)
|
Failure caused by missing python2.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
:: [ 09:23:47 ] :: [ BEGIN ] :: telnet_out is not empty :: actually running ' test -s telnet_out'
:: [ 09:23:47 ] :: [ FAIL ] :: telnet_out is not empty (Expected 0, got 1)
|
Failure caused by missing python2.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
:: [ 09:23:47 ] :: [ BEGIN ] :: compare what telnet received with what was sent :: actually running 'diffdump telnet_out data'
--- /dev/fd/63 2025-02-18 09:23:47.151243575 +0000
+++ /dev/fd/62 2025-02-18 09:23:47.154243644 +0000
@@ -0,0 +1,3 @@
+00000000 68 65 6c 6c 6f 0a 6f 6e 65 0a 74 77 6f 0a 74 68 |hello.one.two.th|
+00000010 72 65 65 0a 62 79 65 0a |ree.bye.|
+00000018
:: [ 09:23:47 ] :: [ FAIL ] :: compare what telnet received with what was sent (Expected 0, got 1)
8888888888888888888888
send: spawn id exp4 not open
while executing
"send "GET /data\r\r""
(file "telnet.expect" line 6)
8888888888888888888888
|
Failure caused by missing python2.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[disc.c: In function ‘disc_stop’:
disc.c:286:17: error: too many arguments to function ‘drives[drive].stop’; expected 0, have 1
286 | drives[drive].stop(drive);
| ^~~~~~ ~~~~~]: [gcc error stating that incorrect number of arguments were used.]
|
Issue: Program cannot be compiled
Resolution: check that library header file is used properly, so compilation uses correct definition
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
disc.c: In function ‘disc_stop’:
disc.c:286:17: error: too many arguments to function ‘drives[drive].stop’; expected 0, have 1
286 | drives[drive].stop(drive);
| ^~~~~~ ~~~~~
|
gcc error stating that incorrect number of arguments were used.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[=========================== short test summary info ============================
FAILED tests/test_ggsave.py::TestArguments::test_save_method - AssertionError...
FAILED tests/test_guide_internals.py::test_no_after_scale_warning - pandas.er...
FAILED tests/test_save_as_pdf_pages.py::TestArguments::test_save_method - Ass...
=== 3 failed, 293 passed, 1 skipped, 95 deselected, 8539 warnings in 35.58s ====]: [testsuite fail summary]
|
Issue: Failed because of fails in testsuite
Resolution: Check the test results and update the code or the test
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
=========================== short test summary info ============================
FAILED tests/test_ggsave.py::TestArguments::test_save_method - AssertionError...
FAILED tests/test_guide_internals.py::test_no_after_scale_warning - pandas.er...
FAILED tests/test_save_as_pdf_pages.py::TestArguments::test_save_method - Ass...
=== 3 failed, 293 passed, 1 skipped, 95 deselected, 8539 warnings in 35.58s ====
|
testsuite fail summary
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[ERROR: Meson version is 1.3.2 but project requires >= 1.4.0]: [An error during build is reported.]
|
Issue: According to error report, the meson build system present in buildroot was older than required.
Resolution: Update the meson build system either via package repository or directly via pip.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
ERROR: Meson version is 1.3.2 but project requires >= 1.4.0
|
An error during build is reported.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[2 out of 2 hunks FAILED -- saving rejects to file src/xdg-desktop-portal.c.rej]: [It indicates that a patch has failed to apply.]
|
Issue: Because a downstream patch failed to apply.
Resolution: Rebase the patch so that I applies clearly.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
2 out of 2 hunks FAILED -- saving rejects to file src/xdg-desktop-portal.c.rej
|
It indicates that a patch has failed to apply.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[DEBUG util.py:461: No match for argument: python3dist(terminaltables) >= 3.1.10]: [Required package for the build is not available in the requested version.]
=============
[DEBUG util.py:461: Problem 1: conflicting requests
DEBUG util.py:461: - nothing provides ((python3.12dist(cryptography) < 40 or python3.12dist(cryptography) > 40) with (python3.12dist(cryptography) < 40.0.1 or python3.12dist(cryptography) > 40.0.1) with python3.12dist(cryptography) < 42~~ with python3.12dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-3.fc40.noarch
DEBUG util.py:461: Problem 2: package python3-oci-2.124.2-1.fc41.noarch requires (python3.12dist(pyopenssl) < 25~~ with python3.12dist(pyopenssl) >= 17.5), but none of the providers can be installed
DEBUG util.py:461: - conflicting requests
DEBUG util.py:461: - nothing provides ((python3.12dist(cryptography) < 40 or python3.12dist(cryptography) > 40) with (python3.12dist(cryptography) < 40.0.1 or python3.12dist(cryptography) > 40.0.1) with python3.12dist(cryptography) < 42~~ with python3.12dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-3.fc40.noarch]: [Error from the requirements for the package. The requested package provides can't be satisfied.]
=============
[DEBUG util.py:461: Failed to resolve the transaction:]: [RPM package transaction has failed. Build can't continue because some dependencies can't be satisfied. ]
|
Issue: Package dependency can't be satisfied because there is a package which can't be found.
Resolution: Fix the missing package dependency. Verify that the package is correct and if it is missing you can add it as a new package.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
DEBUG util.py:461: No match for argument: python3dist(terminaltables) >= 3.1.10
|
Required package for the build is not available in the requested version.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
DEBUG util.py:461: Problem 1: conflicting requests
DEBUG util.py:461: - nothing provides ((python3.12dist(cryptography) < 40 or python3.12dist(cryptography) > 40) with (python3.12dist(cryptography) < 40.0.1 or python3.12dist(cryptography) > 40.0.1) with python3.12dist(cryptography) < 42~~ with python3.12dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-3.fc40.noarch
DEBUG util.py:461: Problem 2: package python3-oci-2.124.2-1.fc41.noarch requires (python3.12dist(pyopenssl) < 25~~ with python3.12dist(pyopenssl) >= 17.5), but none of the providers can be installed
DEBUG util.py:461: - conflicting requests
DEBUG util.py:461: - nothing provides ((python3.12dist(cryptography) < 40 or python3.12dist(cryptography) > 40) with (python3.12dist(cryptography) < 40.0.1 or python3.12dist(cryptography) > 40.0.1) with python3.12dist(cryptography) < 42~~ with python3.12dist(cryptography) >= 38) needed by python3-pyOpenSSL-23.2.0-3.fc40.noarch
|
Error from the requirements for the package. The requested package provides can't be satisfied.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
DEBUG util.py:461: Failed to resolve the transaction:
|
RPM package transaction has failed. Build can't continue because some dependencies can't be satisfied.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Run-time dependency libadwaita-1 found: NO
src/meson.build:33:2: ERROR: Dependency lookup for libadwaita-1 with method 'pkgconfig' failed: Invalid version, need 'libadwaita-1' ['>= 1.7'] found '1.6.6'.]: [This part exactly describes what happened.]
|
Issue: The build is failing because it requires a newer version of libadwaita than what's available on the system.
Resolution: If you have access to the system, update the libadwaita. If there's no newer libadwaita in the repositories, ask the maintainer to rebase it to a newer version. If it can't be rebased, consider building an older version of your package.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Run-time dependency libadwaita-1 found: NO
src/meson.build:33:2: ERROR: Dependency lookup for libadwaita-1 with method 'pkgconfig' failed: Invalid version, need 'libadwaita-1' ['>= 1.7'] found '1.6.6'.
|
This part exactly describes what happened.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[1071/1750 systemd:libsystemd / test-libsystemd-sym FAIL 0.01s exit status 1
>>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 LD_LIBRARY_PATH='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build/' PATH='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin' MESON_TEST_ITERATION=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 SYSTEMD_SLOW_TESTS=1 PROJECT_BUILD_ROOT='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build' SYSTEMD_LANGUAGE_FALLBACK_MAP='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/src/locale/language-fallback-map' MALLOC_PERTURB_=212 PYTHONDONTWRITEBYTECODE=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 '/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build/test-libsystemd-sym'
âââââââââââââââââââââââââââââââââââââ â âââââââââââââââââââââââââââââââââââââ
Listing only the last 100 lines from a long log.
0x3ffb7ca32f0: sd_varlink_connect_fd
0x3ffb7ca3160: sd_varlink_connect_fd_pair
0x3ffb7ca7780: sd_varlink_connect_url
0x3ffb7cafd50: sd_varlink_detach_event
0x3ffb7cb2870: sd_varlink_dispatch
0x3ffb7ca8880: sd_varlink_dispatch_again
0x3ffb7cb2480: sd_varlink_error
0x3ffb7cb2940: sd_varlink_error_errno
0x3ffb7cb29f0: sd_varlink_error_invalid_parameter
0x3ffb7cb2830: sd_varlink_error_invalid_parameter_name
0x3ffb7caf420: sd_varlink_error_is_invalid_parameter
0x3ffb7cb1640: sd_varlink_error_to_errno
0x3ffb7cb26d0: sd_varlink_errorb
0x3ffb7caa6c0: sd_varlink_flush
0x3ffb7caa820: sd_varlink_flush_close_unref
0x3ffb7ca8930: sd_varlink_get_current_method
0x3ffb7ca89d0: sd_varlink_get_current_parameters
0x3ffb7cac040: sd_varlink_get_description
0x3ffb7cac090: sd_varlink_get_event
0x3ffb7ca3590: sd_varlink_get_events
0x3ffb7ca3430: sd_varlink_get_fd
0x3ffb7ca34b0: sd_varlink_get_input_fd
0x3ffb7cac470: sd_varlink_get_n_fds
0x3ffb7ca3520: sd_varlink_get_output_fd
0x3ffb7cabbc0: sd_varlink_get_peer_gid
0x3ffb7cabcd0: sd_varlink_get_peer_pid
0x3ffb7cabdd0: sd_varlink_get_peer_pidfd
0x3ffb7cabab0: sd_varlink_get_peer_uid
0x3ffb7cabf10: sd_varlink_get_server
0x3ffb7ca3680: sd_varlink_get_timeout
0x3ffb7caba60: sd_varlink_get_userdata
0x3ffb7caea70: sd_varlink_idl_dump
0x3ffb7caed70: sd_varlink_idl_format
0x3ffb7caec50: sd_varlink_idl_format_full
0x3ffb7cb0bf0: sd_varlink_invocation
0x3ffb7caad20: sd_varlink_invoke
0x3ffb7caaee0: sd_varlink_invokeb
0x3ffb7ca33c0: sd_varlink_is_idle
0x3ffb7cb2bb0: sd_varlink_notify
0x3ffb7cb2da0: sd_varlink_notifyb
0x3ffb7cab010: sd_varlink_observe
0x3ffb7cab1f0: sd_varlink_observeb
0x3ffb7cac370: sd_varlink_peek_dup_fd
0x3ffb7cac2f0: sd_varlink_peek_fd
0x3ffb7ca94a0: sd_varlink_process
0x3ffb7cac1d0: sd_varlink_push_dup_fd
0x3ffb7cac0e0: sd_varlink_push_fd
0x3ffb7ca3300: sd_varlink_ref
0x3ffb7cb21b0: sd_varlink_reply
0x3ffb7cb2370: sd_varlink_replyb
0x3ffb7cab920: sd_varlink_reset_fds
0x3ffb7caaa20: sd_varlink_send
0x3ffb7caabf0: sd_varlink_sendb
0x3ffb7cb0480: sd_varlink_server_add_connection
0x3ffb7cb0040: sd_varlink_server_add_connection_pair
0x3ffb7cb06b0: sd_varlink_server_add_connection_stdio
0x3ffb7cae450: sd_varlink_server_add_interface
0x3ffb7cae670: sd_varlink_server_add_interface_many_internal
0x3ffb7cb12f0: sd_varlink_server_attach_event
0x3ffb7cae350: sd_varlink_server_bind_connect
0x3ffb7cae3d0: sd_varlink_server_bind_disconnect
0x3ffb7cadfc0: sd_varlink_server_bind_method
0x3ffb7cae210: sd_varlink_server_bind_method_many_internal
0x3ffb7cae780: sd_varlink_server_connections_max
0x3ffb7cae800: sd_varlink_server_connections_per_uid_max
0x3ffb7cae970: sd_varlink_server_current_connections
0x3ffb7cb11c0: sd_varlink_server_detach_event
0x3ffb7cadf70: sd_varlink_server_get_event
0x3ffb7cadf20: sd_varlink_server_get_userdata
0x3ffb7caf9e0: sd_varlink_server_listen_address
0x3ffb7cb0b20: sd_varlink_server_listen_auto
0x3ffb7caf850: sd_varlink_server_listen_fd
0x3ffb7cb08f0: sd_varlink_server_listen_name
0x3ffb7cb1500: sd_varlink_server_loop_auto
0x3ffb7cb1070: sd_varlink_server_new
0x3ffb7cac660: sd_varlink_server_ref
0x3ffb7cae8e0: sd_varlink_server_set_connections_max
0x3ffb7cae850: sd_varlink_server_set_connections_per_uid_max
0x3ffb7cae990: sd_varlink_server_set_description
0x3ffb7cb1260: sd_varlink_server_set_exit_on_idle
0x3ffb7cac6d0: sd_varlink_server_set_info
0x3ffb7caded0: sd_varlink_server_set_userdata
0x3ffb7cb0e00: sd_varlink_server_shutdown
0x3ffb7cb0f20: sd_varlink_server_unref
0x3ffb7cac4d0: sd_varlink_set_allow_fd_passing_input
0x3ffb7cac570: sd_varlink_set_allow_fd_passing_output
0x3ffb7cabf60: sd_varlink_set_description
0x3ffb7cac610: sd_varlink_set_input_sensitive
0x3ffb7cabe80: sd_varlink_set_relative_timeout
0x3ffb7caba10: sd_varlink_set_userdata
0x3ffb7cac3f0: sd_varlink_take_fd
0x3ffb7ca74a0: sd_varlink_unref
0x3ffb7ca3740: sd_varlink_wait
0x3ffb7c3b3e0: sd_watchdog_enabled
Found 865 symbols from symbol file.
Found 887 symbols from header files.
Found 864 symbols from source files.
Found in symbol file, but not in sources: sd_bus_message_dump_json
Found in header file, but not in sources: sd_bus_message_dump_json
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
]: [test test-libsystemd-sym failed]
=============
[error: Bad exit status from /var/tmp/rpm-tmp.jjJXFj (%check)]: [Build failed during %check phase]
|
Issue: Test test-libsystemd-sym failed during %check phase
Resolution: Check if the test test-libsystemd-sym was failing before changes were introduced in the current build. If not, check the new code and test to find the bug.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
1071/1750 systemd:libsystemd / test-libsystemd-sym FAIL 0.01s exit status 1
>>> MSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 LD_LIBRARY_PATH='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build/' PATH='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/sbin' MESON_TEST_ITERATION=1 ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 SYSTEMD_SLOW_TESTS=1 PROJECT_BUILD_ROOT='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build' SYSTEMD_LANGUAGE_FALLBACK_MAP='/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/src/locale/language-fallback-map' MALLOC_PERTURB_=212 PYTHONDONTWRITEBYTECODE=1 UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 '/builddir/build/BUILD/systemd-258_devel-build/systemd-258~devel/redhat-linux-build/test-libsystemd-sym'
âââââââââââââââââââââââââââââââââââââ â âââââââââââââââââââââââââââââââââââââ
Listing only the last 100 lines from a long log.
0x3ffb7ca32f0: sd_varlink_connect_fd
0x3ffb7ca3160: sd_varlink_connect_fd_pair
0x3ffb7ca7780: sd_varlink_connect_url
0x3ffb7cafd50: sd_varlink_detach_event
0x3ffb7cb2870: sd_varlink_dispatch
0x3ffb7ca8880: sd_varlink_dispatch_again
0x3ffb7cb2480: sd_varlink_error
0x3ffb7cb2940: sd_varlink_error_errno
0x3ffb7cb29f0: sd_varlink_error_invalid_parameter
0x3ffb7cb2830: sd_varlink_error_invalid_parameter_name
0x3ffb7caf420: sd_varlink_error_is_invalid_parameter
0x3ffb7cb1640: sd_varlink_error_to_errno
0x3ffb7cb26d0: sd_varlink_errorb
0x3ffb7caa6c0: sd_varlink_flush
0x3ffb7caa820: sd_varlink_flush_close_unref
0x3ffb7ca8930: sd_varlink_get_current_method
0x3ffb7ca89d0: sd_varlink_get_current_parameters
0x3ffb7cac040: sd_varlink_get_description
0x3ffb7cac090: sd_varlink_get_event
0x3ffb7ca3590: sd_varlink_get_events
0x3ffb7ca3430: sd_varlink_get_fd
0x3ffb7ca34b0: sd_varlink_get_input_fd
0x3ffb7cac470: sd_varlink_get_n_fds
0x3ffb7ca3520: sd_varlink_get_output_fd
0x3ffb7cabbc0: sd_varlink_get_peer_gid
0x3ffb7cabcd0: sd_varlink_get_peer_pid
0x3ffb7cabdd0: sd_varlink_get_peer_pidfd
0x3ffb7cabab0: sd_varlink_get_peer_uid
0x3ffb7cabf10: sd_varlink_get_server
0x3ffb7ca3680: sd_varlink_get_timeout
0x3ffb7caba60: sd_varlink_get_userdata
0x3ffb7caea70: sd_varlink_idl_dump
0x3ffb7caed70: sd_varlink_idl_format
0x3ffb7caec50: sd_varlink_idl_format_full
0x3ffb7cb0bf0: sd_varlink_invocation
0x3ffb7caad20: sd_varlink_invoke
0x3ffb7caaee0: sd_varlink_invokeb
0x3ffb7ca33c0: sd_varlink_is_idle
0x3ffb7cb2bb0: sd_varlink_notify
0x3ffb7cb2da0: sd_varlink_notifyb
0x3ffb7cab010: sd_varlink_observe
0x3ffb7cab1f0: sd_varlink_observeb
0x3ffb7cac370: sd_varlink_peek_dup_fd
0x3ffb7cac2f0: sd_varlink_peek_fd
0x3ffb7ca94a0: sd_varlink_process
0x3ffb7cac1d0: sd_varlink_push_dup_fd
0x3ffb7cac0e0: sd_varlink_push_fd
0x3ffb7ca3300: sd_varlink_ref
0x3ffb7cb21b0: sd_varlink_reply
0x3ffb7cb2370: sd_varlink_replyb
0x3ffb7cab920: sd_varlink_reset_fds
0x3ffb7caaa20: sd_varlink_send
0x3ffb7caabf0: sd_varlink_sendb
0x3ffb7cb0480: sd_varlink_server_add_connection
0x3ffb7cb0040: sd_varlink_server_add_connection_pair
0x3ffb7cb06b0: sd_varlink_server_add_connection_stdio
0x3ffb7cae450: sd_varlink_server_add_interface
0x3ffb7cae670: sd_varlink_server_add_interface_many_internal
0x3ffb7cb12f0: sd_varlink_server_attach_event
0x3ffb7cae350: sd_varlink_server_bind_connect
0x3ffb7cae3d0: sd_varlink_server_bind_disconnect
0x3ffb7cadfc0: sd_varlink_server_bind_method
0x3ffb7cae210: sd_varlink_server_bind_method_many_internal
0x3ffb7cae780: sd_varlink_server_connections_max
0x3ffb7cae800: sd_varlink_server_connections_per_uid_max
0x3ffb7cae970: sd_varlink_server_current_connections
0x3ffb7cb11c0: sd_varlink_server_detach_event
0x3ffb7cadf70: sd_varlink_server_get_event
0x3ffb7cadf20: sd_varlink_server_get_userdata
0x3ffb7caf9e0: sd_varlink_server_listen_address
0x3ffb7cb0b20: sd_varlink_server_listen_auto
0x3ffb7caf850: sd_varlink_server_listen_fd
0x3ffb7cb08f0: sd_varlink_server_listen_name
0x3ffb7cb1500: sd_varlink_server_loop_auto
0x3ffb7cb1070: sd_varlink_server_new
0x3ffb7cac660: sd_varlink_server_ref
0x3ffb7cae8e0: sd_varlink_server_set_connections_max
0x3ffb7cae850: sd_varlink_server_set_connections_per_uid_max
0x3ffb7cae990: sd_varlink_server_set_description
0x3ffb7cb1260: sd_varlink_server_set_exit_on_idle
0x3ffb7cac6d0: sd_varlink_server_set_info
0x3ffb7caded0: sd_varlink_server_set_userdata
0x3ffb7cb0e00: sd_varlink_server_shutdown
0x3ffb7cb0f20: sd_varlink_server_unref
0x3ffb7cac4d0: sd_varlink_set_allow_fd_passing_input
0x3ffb7cac570: sd_varlink_set_allow_fd_passing_output
0x3ffb7cabf60: sd_varlink_set_description
0x3ffb7cac610: sd_varlink_set_input_sensitive
0x3ffb7cabe80: sd_varlink_set_relative_timeout
0x3ffb7caba10: sd_varlink_set_userdata
0x3ffb7cac3f0: sd_varlink_take_fd
0x3ffb7ca74a0: sd_varlink_unref
0x3ffb7ca3740: sd_varlink_wait
0x3ffb7c3b3e0: sd_watchdog_enabled
Found 865 symbols from symbol file.
Found 887 symbols from header files.
Found 864 symbols from source files.
Found in symbol file, but not in sources: sd_bus_message_dump_json
Found in header file, but not in sources: sd_bus_message_dump_json
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
|
test test-libsystemd-sym failed
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
error: Bad exit status from /var/tmp/rpm-tmp.jjJXFj (%check)
|
Build failed during %check phase
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-music21-9.5.0-build/music21-9.5.0/pyproject-wheeldir --output /builddir/build/BUILD/python-music21-9.5.0-build/python-music21-9.5.0-1.fc43.x86_64-pyproject-buildrequires -t]: [This snipped describes an invocation to generate build requirements for the package from the built wheel metadata. It contains a flag "-t" which adds the tox configuration to the build.]
=============
[LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details.]: [The tox configuration file couldn't be located, hence the LookupError is raised.]
|
Issue: The package configures fetching additional test build requirements from tox configuration, but it doesn't provide a configuration file from which it's possible to read the requirements.
Resolution: It should be ensured that tox configuration file is present in the sdist. If the package doesn't use tox, the "-t" flag from the generate_buildrequires.py invocation should be removed.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
+ /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /builddir/build/BUILD/python-music21-9.5.0-build/music21-9.5.0/pyproject-wheeldir --output /builddir/build/BUILD/python-music21-9.5.0-build/python-music21-9.5.0-1.fc43.x86_64-pyproject-buildrequires -t
|
This snipped describes an invocation to generate build requirements for the package from the built wheel metadata. It contains a flag "-t" which adds the tox configuration to the build.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
LookupError: tox configuration not found. To use tox, please ensure tox configuration is located in current directory (in tox.ini, setup.cfg, pyproject.toml, or tox.toml). See https://tox.wiki/en/latest/config.html for details.
|
The tox configuration file couldn't be located, hence the LookupError is raised.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[exportfs.c: In function ‘release_lockfile’:
exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
83 | lockf(_lockfd, F_ULOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
exportfs.c: In function ‘grab_lockfile’:
exportfs.c:77:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
77 | lockf(_lockfd, F_LOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
]: [Error message from the compiler]
|
Issue: Compiler checks unused return value from a function. [-Werror=unused-result]
Resolution: Don't ignore the return value from a function. Or define function as returning no value.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
exportfs.c: In function ‘release_lockfile’:
exportfs.c:83:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
83 | lockf(_lockfd, F_ULOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
exportfs.c: In function ‘grab_lockfile’:
exportfs.c:77:17: error: ignoring return value of ‘lockf’ declared with attribute ‘warn_unused_result’ [-Werror=unused-result]
77 | lockf(_lockfd, F_LOCK, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
|
Error message from the compiler
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[meson.build:443:0: ERROR: Program 'gi-docgen' not found or not executable]: [Description of build failure.]
|
Issue: Missing gi-docgen dependency.
Resolution: Add gi-docgen package as BuildRequire to your SPEC file or try to build package without this requirement.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
meson.build:443:0: ERROR: Program 'gi-docgen' not found or not executable
|
Description of build failure.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[No matching package to install: 'rust >= 1.86'
Not all dependencies satisfied
Error: Some packages could not be found.]: [It shows the error message which caused the build failure.]
|
Issue: Because some package dependencies were not installed, as they were not found.
Resolution: Ensure that all dependencies needed by the package are installable.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
No matching package to install: 'rust >= 1.86'
Not all dependencies satisfied
Error: Some packages could not be found.
|
It shows the error message which caused the build failure.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Can't locate Sub/Name.pm in @INC (you may need to install the Sub::Name module) (@INC entries checked: /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/arch /usr/local/lib64/perl5/5.40 /usr/local/share/perl5/5.40 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/Moose/Meta/Method/VariantTable.pm line 11.
BEGIN failed--compilation aborted at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/Moose/Meta/Method/VariantTable.pm line 11.
Compilation failed in require at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/MooseX/Types/VariantTable/Declare.pm line 17.
BEGIN failed--compilation aborted at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/MooseX/Types/VariantTable/Declare.pm line 17.
Compilation failed in require at t/sugar.t line 24.
BEGIN failed--compilation aborted at t/sugar.t line 24.
t/sugar.t ....... skipped: (no reason given)]: [t/sugar.t test failed.]
|
Issue: Moose::Meta::Method::VariantTable module attempted to load Sub::Name module. That failed because the module is not installed.
Resolution: Declare a build-time dependency on "perl(Sub::Name)" in the spec file.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Can't locate Sub/Name.pm in @INC (you may need to install the Sub::Name module) (@INC entries checked: /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/arch /usr/local/lib64/perl5/5.40 /usr/local/share/perl5/5.40 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/Moose/Meta/Method/VariantTable.pm line 11.
BEGIN failed--compilation aborted at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/Moose/Meta/Method/VariantTable.pm line 11.
Compilation failed in require at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/MooseX/Types/VariantTable/Declare.pm line 17.
BEGIN failed--compilation aborted at /builddir/build/BUILD/perl-MooseX-Types-VariantTable-0.04-build/MooseX-Types-VariantTable-0.04/blib/lib/MooseX/Types/VariantTable/Declare.pm line 17.
Compilation failed in require at t/sugar.t line 24.
BEGIN failed--compilation aborted at t/sugar.t line 24.
t/sugar.t ....... skipped: (no reason given)
|
t/sugar.t test failed.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Failed to resolve the transaction:
Package "pyproject-rpm-macros-1.16.0-1.fc41.noarch" is already installed.
Package "python3-devel-3.13.0-1.fc41.x86_64" is already installed.
Package "python3-packaging-24.1-2.fc41.noarch" is already installed.
Package "python3-pip-24.2-1.fc41.noarch" is already installed.
Package "python3-poetry-core-1.9.1-1.fc41.noarch" is already installed.
Problem 1: nothing provides requested (python3dist(cryptography) < 37~~ with python3dist(cryptography) >= 36)
Problem 2: nothing provides requested (python3dist(delta-spark) < 3.3~~ with python3dist(delta-spark) >= 3.2.1)
Problem 3: nothing provides requested (python3dist(hadoop-fs-wrapper) < 0.8~~ with python3dist(hadoop-fs-wrapper) >= 0.7)]: [DNF failed to resolve all dependencies.
Specifically, following constraints were impossible to satisfy:
(python3dist(cryptography) < 37~~ with python3dist(cryptography) >= 36)
(python3dist(delta-spark) < 3.3~~ with python3dist(delta-spark) >= 3.2.1)
(python3dist(hadoop-fs-wrapper) < 0.8~~ with python3dist(hadoop-fs-wrapper) >= 0.7)
]
|
Issue: Multiple dependency constraints were impossible to satisfy. Leading to build failure.
Resolution: Ensure that all dependency constraints can be satisfied before initializing build process.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Failed to resolve the transaction:
Package "pyproject-rpm-macros-1.16.0-1.fc41.noarch" is already installed.
Package "python3-devel-3.13.0-1.fc41.x86_64" is already installed.
Package "python3-packaging-24.1-2.fc41.noarch" is already installed.
Package "python3-pip-24.2-1.fc41.noarch" is already installed.
Package "python3-poetry-core-1.9.1-1.fc41.noarch" is already installed.
Problem 1: nothing provides requested (python3dist(cryptography) < 37~~ with python3dist(cryptography) >= 36)
Problem 2: nothing provides requested (python3dist(delta-spark) < 3.3~~ with python3dist(delta-spark) >= 3.2.1)
Problem 3: nothing provides requested (python3dist(hadoop-fs-wrapper) < 0.8~~ with python3dist(hadoop-fs-wrapper) >= 0.7)
|
DNF failed to resolve all dependencies.
Specifically, following constraints were impossible to satisfy:
(python3dist(cryptography) < 37~~ with python3dist(cryptography) >= 36)
(python3dist(delta-spark) < 3.3~~ with python3dist(delta-spark) >= 3.2.1)
(python3dist(hadoop-fs-wrapper) < 0.8~~ with python3dist(hadoop-fs-wrapper) >= 0.7)
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[ openssl-libs x86_64 1:3.1.4-1.fc40 fedora 7.8 Mi]: [This line indicate that openssl 3.1.4 is used.]
=============
[
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -I.. -I./src/sss_client -I./src -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libnl3 -DLIBDIR=\"/usr/lib64\" -DVARDIR=\"/var\" -DRUNDIR=\"/run\" -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" -DLOCALEDIR=\"/usr/share/locale\" -DBASE_FILE_STEM=\"libsss_certmap_la-cert\" -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wundef -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs -fno-strict-aliasing -std=gnu99 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c src/util/cert/libcrypto/cert.c -fPIC -DPIC -o src/util/cert/libcrypto/.libs/libsss_certmap_la-cert.o
src/util/cert/libcrypto/cert.c: In function 'ec_pub_key_to_ssh':
src/util/cert/libcrypto/cert.c:196:5: warning: 'EVP_PKEY_get1_EC_KEY' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
196 | ec_key = EVP_PKEY_get1_EC_KEY(cert_pub_key);
| ^~~~~~
In file included from /usr/include/openssl/x509.h:29,
from src/util/cert/libcrypto/cert.c:20:
/usr/include/openssl/evp.h:1390:19: note: declared here
1390 | struct ec_key_st *EVP_PKEY_get1_EC_KEY(EVP_PKEY *pkey);
| ^~~~~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:202:5: warning: 'EC_KEY_get0_group' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
202 | ec_group = EC_KEY_get0_group(ec_key);
| ^~~~~~~~
In file included from /usr/include/openssl/x509.h:33:
/usr/include/openssl/ec.h:1037:39: note: declared here
1037 | OSSL_DEPRECATEDIN_3_0 const EC_GROUP *EC_KEY_get0_group(const EC_KEY *key);
| ^~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:227:5: warning: 'EC_KEY_get0_public_key' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
227 | ec_public_key = EC_KEY_get0_public_key(ec_key);
| ^~~~~~~~~~~~~
/usr/include/openssl/ec.h:1065:39: note: declared here
1065 | OSSL_DEPRECATEDIN_3_0 const EC_POINT *EC_KEY_get0_public_key(const EC_KEY *key);
| ^~~~~~~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:282:5: warning: 'EC_KEY_free' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
282 | EC_KEY_free(ec_key);
| ^~~~~~~~~~~
/usr/include/openssl/ec.h:1006:28: note: declared here
1006 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
| ^~~~~~~~~~~
src/util/cert/libcrypto/cert.c: In function 'rsa_pub_key_to_ssh':
src/util/cert/libcrypto/cert.c:307:5: warning: 'EVP_PKEY_get0_RSA' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
307 | rsa_pub_key = EVP_PKEY_get0_RSA(cert_pub_key);
| ^~~~~~~~~~~
/usr/include/openssl/evp.h:1362:22: note: declared here
1362 | const struct rsa_st *EVP_PKEY_get0_RSA(const EVP_PKEY *pkey);
| ^~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:313:5: warning: 'RSA_get0_key' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
313 | RSA_get0_key(rsa_pub_key, &n, &e, NULL);
| ^~~~~~~~~~~~
In file included from /usr/include/openssl/x509.h:36:
/usr/include/openssl/rsa.h:228:28: note: declared here
228 | OSSL_DEPRECATEDIN_3_0 void RSA_get0_key(const RSA *r,
| ^~~~~~~~~~~]: [The build process for the SSSD package is failing due to the use of deprecated functions from the OpenSSL library. The warnings indicate that several functions (EVP_PKEY_get1_EC_KEY, EC_KEY_get0_group, EC_KEY_get0_public_key, EC_KEY_free, EVP_PKEY_get0_RSA, RSA_get0_key) are deprecated as of OpenSSL 3.0.
To resolve this issue, you should update the source code of SSSD to use the new functions provided by OpenSSL 3.0 or later. The deprecated functions are related to handling EC (Elliptic Curve) and RSA keys. You should replace them with the appropriate non-deprecated functions. But this is merely warning and it is not a reason for build failure.]
=============
[
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -I.. -I./src/sss_client -I./src -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libnl3 -DLIBDIR=\"/usr/lib64\" -DVARDIR=\"/var\" -DRUNDIR=\"/run\" -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" -DLOCALEDIR=\"/usr/share/locale\" -DBASE_FILE_STEM=\"pam_sss\" -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wundef -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs -fno-strict-aliasing -std=gnu99 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c src/sss_client/pam_sss.c -fPIC -DPIC -o src/sss_client/.libs/pam_sss.o
In file included from src/sss_client/pam_sss.c:41:
/usr/include/gdm/gdm-pam-extensions.h:24:10: fatal error: gdm-choice-list-pam-extension.h: No such file or directory
24 | #include "gdm-choice-list-pam-extension.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated]: [This is the reason for failure. It is due to a missing header file: `gdm-choice-list-pam-extension.h`. This file is expected to be part of the GDM (GNOME Display Manager) development package but is not found in the standard include directories.]
|
Issue: You are missing the required header file `gdm-choice-list-pam-extension.h`. The file is likely provided by package `gdm-devel`.
Resolution: You need to add:
BuildRequires: gdm-devel
to your SPEC file.
To be sure you can run command: `dnf provides '*/gdm-choice-list-pam-extension.h'` to find which package contains the required file.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
openssl-libs x86_64 1:3.1.4-1.fc40 fedora 7.8 Mi
|
This line indicate that openssl 3.1.4 is used.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -I.. -I./src/sss_client -I./src -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libnl3 -DLIBDIR=\"/usr/lib64\" -DVARDIR=\"/var\" -DRUNDIR=\"/run\" -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" -DLOCALEDIR=\"/usr/share/locale\" -DBASE_FILE_STEM=\"libsss_certmap_la-cert\" -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wundef -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs -fno-strict-aliasing -std=gnu99 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c src/util/cert/libcrypto/cert.c -fPIC -DPIC -o src/util/cert/libcrypto/.libs/libsss_certmap_la-cert.o
src/util/cert/libcrypto/cert.c: In function 'ec_pub_key_to_ssh':
src/util/cert/libcrypto/cert.c:196:5: warning: 'EVP_PKEY_get1_EC_KEY' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
196 | ec_key = EVP_PKEY_get1_EC_KEY(cert_pub_key);
| ^~~~~~
In file included from /usr/include/openssl/x509.h:29,
from src/util/cert/libcrypto/cert.c:20:
/usr/include/openssl/evp.h:1390:19: note: declared here
1390 | struct ec_key_st *EVP_PKEY_get1_EC_KEY(EVP_PKEY *pkey);
| ^~~~~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:202:5: warning: 'EC_KEY_get0_group' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
202 | ec_group = EC_KEY_get0_group(ec_key);
| ^~~~~~~~
In file included from /usr/include/openssl/x509.h:33:
/usr/include/openssl/ec.h:1037:39: note: declared here
1037 | OSSL_DEPRECATEDIN_3_0 const EC_GROUP *EC_KEY_get0_group(const EC_KEY *key);
| ^~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:227:5: warning: 'EC_KEY_get0_public_key' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
227 | ec_public_key = EC_KEY_get0_public_key(ec_key);
| ^~~~~~~~~~~~~
/usr/include/openssl/ec.h:1065:39: note: declared here
1065 | OSSL_DEPRECATEDIN_3_0 const EC_POINT *EC_KEY_get0_public_key(const EC_KEY *key);
| ^~~~~~~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:282:5: warning: 'EC_KEY_free' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
282 | EC_KEY_free(ec_key);
| ^~~~~~~~~~~
/usr/include/openssl/ec.h:1006:28: note: declared here
1006 | OSSL_DEPRECATEDIN_3_0 void EC_KEY_free(EC_KEY *key);
| ^~~~~~~~~~~
src/util/cert/libcrypto/cert.c: In function 'rsa_pub_key_to_ssh':
src/util/cert/libcrypto/cert.c:307:5: warning: 'EVP_PKEY_get0_RSA' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
307 | rsa_pub_key = EVP_PKEY_get0_RSA(cert_pub_key);
| ^~~~~~~~~~~
/usr/include/openssl/evp.h:1362:22: note: declared here
1362 | const struct rsa_st *EVP_PKEY_get0_RSA(const EVP_PKEY *pkey);
| ^~~~~~~~~~~~~~~~~
src/util/cert/libcrypto/cert.c:313:5: warning: 'RSA_get0_key' is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations]
313 | RSA_get0_key(rsa_pub_key, &n, &e, NULL);
| ^~~~~~~~~~~~
In file included from /usr/include/openssl/x509.h:36:
/usr/include/openssl/rsa.h:228:28: note: declared here
228 | OSSL_DEPRECATEDIN_3_0 void RSA_get0_key(const RSA *r,
| ^~~~~~~~~~~
|
The build process for the SSSD package is failing due to the use of deprecated functions from the OpenSSL library. The warnings indicate that several functions (EVP_PKEY_get1_EC_KEY, EC_KEY_get0_group, EC_KEY_get0_public_key, EC_KEY_free, EVP_PKEY_get0_RSA, RSA_get0_key) are deprecated as of OpenSSL 3.0.
To resolve this issue, you should update the source code of SSSD to use the new functions provided by OpenSSL 3.0 or later. The deprecated functions are related to handling EC (Elliptic Curve) and RSA keys. You should replace them with the appropriate non-deprecated functions. But this is merely warning and it is not a reason for build failure.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wall -I.. -I./src/sss_client -I./src -I. -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/libnl3 -DLIBDIR=\"/usr/lib64\" -DVARDIR=\"/var\" -DRUNDIR=\"/run\" -DSSS_STATEDIR=\"/var/lib/sss\" -DSYSCONFDIR=\"/etc\" -DSHLIBEXT=\"\" -DSSSDDATADIR=\"/usr/share/sssd\" -DSSSD_LIBEXEC_PATH=\"/usr/libexec/sssd\" -DSSSD_CONF_DIR=\"/etc/sssd\" -DSSS_NSS_MCACHE_DIR=\"/var/lib/sss/mc\" -DSSS_NSS_SOCKET_NAME=\"/var/lib/sss/pipes/nss\" -DSSS_PAM_SOCKET_NAME=\"/var/lib/sss/pipes/pam\" -DSSS_PAC_SOCKET_NAME=\"/var/lib/sss/pipes/pac\" -DSSS_PAM_PRIV_SOCKET_NAME=\"/var/lib/sss/pipes/private/pam\" -DSSS_SUDO_SOCKET_NAME=\"/var/lib/sss/pipes/sudo\" -DSSS_AUTOFS_SOCKET_NAME=\"/var/lib/sss/pipes/autofs\" -DSSS_SSH_SOCKET_NAME=\"/var/lib/sss/pipes/ssh\" -DLOCALEDIR=\"/usr/share/locale\" -DBASE_FILE_STEM=\"pam_sss\" -Wall -Wshadow -Wstrict-prototypes -Wpointer-arith -Wcast-qual -Wcast-align -Wwrite-strings -Wundef -Werror-implicit-function-declaration -Winit-self -Wmissing-include-dirs -fno-strict-aliasing -std=gnu99 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c src/sss_client/pam_sss.c -fPIC -DPIC -o src/sss_client/.libs/pam_sss.o
In file included from src/sss_client/pam_sss.c:41:
/usr/include/gdm/gdm-pam-extensions.h:24:10: fatal error: gdm-choice-list-pam-extension.h: No such file or directory
24 | #include "gdm-choice-list-pam-extension.h"
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated
|
This is the reason for failure. It is due to a missing header file: `gdm-choice-list-pam-extension.h`. This file is expected to be part of the GDM (GNOME Display Manager) development package but is not found in the standard include directories.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[+ /usr/bin/pytest
============================= test session starts ==============================
platform linux -- Python 3.13.3, pytest-8.3.5, pluggy-1.5.0
rootdir: /builddir/build/BUILD/python-partd-1.4.2-build/partd-1.4.2
configfile: pyproject.toml
collected 56 items
partd/tests/test_buffer.py ... [ 5%]
partd/tests/test_compressed.py .. [ 8%]
partd/tests/test_dict.py .... [ 16%]
partd/tests/test_encode.py .. [ 19%]
partd/tests/test_file.py ....... [ 32%]
partd/tests/test_numpy.py ....... [ 44%]
partd/tests/test_pandas.py ..............s [ 71%]
partd/tests/test_partd.py .... [ 78%]
partd/tests/test_pickle.py .. [ 82%]
partd/tests/test_python.py . [ 83%]
partd/tests/test_utils.py .. [ 87%]
partd/tests/test_zmq.py . !! Copr timeout => sending INT
Copr build error: Build failed]: [It shows the progress of tests run.]
|
Issue: There seems to be a problem causing the tests to get stuck, and then the build reached the limit of 5 hours and got killed by COPR.
Resolution: Find the test that hangs and figure out what is wrong with it, or skip it.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
+ /usr/bin/pytest
============================= test session starts ==============================
platform linux -- Python 3.13.3, pytest-8.3.5, pluggy-1.5.0
rootdir: /builddir/build/BUILD/python-partd-1.4.2-build/partd-1.4.2
configfile: pyproject.toml
collected 56 items
partd/tests/test_buffer.py ... [ 5%]
partd/tests/test_compressed.py .. [ 8%]
partd/tests/test_dict.py .... [ 16%]
partd/tests/test_encode.py .. [ 19%]
partd/tests/test_file.py ....... [ 32%]
partd/tests/test_numpy.py ....... [ 44%]
partd/tests/test_pandas.py ..............s [ 71%]
partd/tests/test_partd.py .... [ 78%]
partd/tests/test_pickle.py .. [ 82%]
partd/tests/test_python.py . [ 83%]
partd/tests/test_utils.py .. [ 87%]
partd/tests/test_zmq.py . !! Copr timeout => sending INT
Copr build error: Build failed
|
It shows the progress of tests run.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[
RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/include/offload/OffloadAPI.h
/usr/include/offload/OffloadPrint.hpp
/usr/lib/debug/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254-20.0.0~pre20241206.g1a896049018254-1.el8.s390x.debug
/usr/lib64/libLLVMOffload.so
/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254
Installed (but unpackaged) file(s) found:
/usr/include/offload/OffloadAPI.h
/usr/include/offload/OffloadPrint.hpp
/usr/lib/debug/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254-20.0.0~pre20241206.g1a896049018254-1.el8.s390x.debug
/usr/lib64/libLLVMOffload.so
/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254]: [Multiple files were installed by the package but not tracked by the package manager.]
=============
[sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory]: [Attempts to use `/usr/bin/python3.12` binary were not successful, as it was not installed.]
|
Issue: Some of the files installed by the package were not properly tracked. This can cause conflicts when installing other packages, issues during upgrades, and make safe removal of the files impossible.
Resolution: Ensure that all files installed by the package, no matter their source and destination, are tracked.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/include/offload/OffloadAPI.h
/usr/include/offload/OffloadPrint.hpp
/usr/lib/debug/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254-20.0.0~pre20241206.g1a896049018254-1.el8.s390x.debug
/usr/lib64/libLLVMOffload.so
/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254
Installed (but unpackaged) file(s) found:
/usr/include/offload/OffloadAPI.h
/usr/include/offload/OffloadPrint.hpp
/usr/lib/debug/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254-20.0.0~pre20241206.g1a896049018254-1.el8.s390x.debug
/usr/lib64/libLLVMOffload.so
/usr/lib64/libLLVMOffload.so.20.0pre20241206.g1a896049018254
|
Multiple files were installed by the package but not tracked by the package manager.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
sh: /usr/bin/python3.12: No such file or directory
|
Attempts to use `/usr/bin/python3.12` binary were not successful, as it was not installed.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[flist.c:2787:55: error: passing argument 4 of ‘qsort’ from incompatible pointer type [-Wincompatible-pointer-types]
2787 | sizeof the_fattr_list.files[0], (int (*)())fattr_compare);
| ^~~~~~~~~~~~~~~~~~~~~~~~
| |
| int (*)(void)
In file included from rsync.h:330:]: [Description of a compilation error.]
|
Issue: Incompatible pointer type insertion, likely due to the updated gcc standard
Resolution: Correct the used types in the source code according to the compilers suggestion
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
flist.c:2787:55: error: passing argument 4 of ‘qsort’ from incompatible pointer type [-Wincompatible-pointer-types]
2787 | sizeof the_fattr_list.files[0], (int (*)())fattr_compare);
| ^~~~~~~~~~~~~~~~~~~~~~~~
| |
| int (*)(void)
In file included from rsync.h:330:
|
Description of a compilation error.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[error: Bad exit status from /var/tmp/rpm-tmp.wNPS2P (%build)
]: [The failure happened in %build phase.]
=============
[Match_inv.c: In function ‘f_match_inv_add’:
Match_inv.c:40:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 6
40 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]));
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:44:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 7
44 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]),arg1);
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:52:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 8
52 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]),arg1,arg2);
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:69:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 6
69 | match_extra_fn[j](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[j]));
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:71:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 7
71 | match_extra_fn[j](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[j]), match_extra_fn_arg1[j] );
| ^~~~~~~~~~~~~~ ~~
Match_inv.c: In function ‘match_inv’:
Match_inv.c:213:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 6
213 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]));
| ^~~~~~~~~~~~~~ ~~~~
Match_inv.c:215:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 7
215 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]),match_extra_fn_arg1[j]);
| ^~~~~~~~~~~~~~ ~~~~
Match_inv.c:217:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 8
217 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]),
| ^~~~~~~~~~~~~~ ~~~~
make: *** [makefile:60: Match_inv.o] Error 1
make: *** Waiting for unfinished jobs....
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Lola.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Match_fs.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Macro.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Match.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Mem_buffer.c]: [You are using incompatible gcc syntax.]
|
Issue: Your code is using C15 standard, while defaults move to C23.
Resolution: The best move is to report this to upstream and as a temporary fix pass -std=gnu17 to gcc.
export CFLAGS="-std=gnu17"
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
error: Bad exit status from /var/tmp/rpm-tmp.wNPS2P (%build)
|
The failure happened in %build phase.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Match_inv.c: In function ‘f_match_inv_add’:
Match_inv.c:40:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 6
40 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]));
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:44:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 7
44 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]),arg1);
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:52:13: error: too many arguments to function ‘match_extra_fn[match_extra_fn_n]’; expected 0, have 8
52 | match_extra_fn[match_extra_fn_n](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[match_extra_fn_n]),arg1,arg2);
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:69:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 6
69 | match_extra_fn[j](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[j]));
| ^~~~~~~~~~~~~~ ~~
Match_inv.c:71:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 7
71 | match_extra_fn[j](-1, NULL, NULL, 0, inv_out, &(match_extra_fn_local[j]), match_extra_fn_arg1[j] );
| ^~~~~~~~~~~~~~ ~~
Match_inv.c: In function ‘match_inv’:
Match_inv.c:213:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 6
213 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]));
| ^~~~~~~~~~~~~~ ~~~~
Match_inv.c:215:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 7
215 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]),match_extra_fn_arg1[j]);
| ^~~~~~~~~~~~~~ ~~~~
Match_inv.c:217:17: error: too many arguments to function ‘match_extra_fn[j]’; expected 0, have 8
217 | match_extra_fn[j](mode, sec, data, ndata, inv_out, &(match_extra_fn_local[j]),
| ^~~~~~~~~~~~~~ ~~~~
make: *** [makefile:60: Match_inv.o] Error 1
make: *** Waiting for unfinished jobs....
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Lola.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Match_fs.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Macro.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Match.c
gcc -c -I.. -I/usr/include/netcdf -I/usr/include/mysql -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fopenmp Mem_buffer.c
|
You are using incompatible gcc syntax.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType']: [this is the summary line of the exception that got thrown during unit testing which broke the build]
|
Issue: Python 3.9 does not support the used typing syntax
Resolution: move to a typing syntax supported by Python 3.9
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
TypeError: unsupported operand type(s) for |: 'types.GenericAlias' and 'NoneType'
|
this is the summary line of the exception that got thrown during unit testing which broke the build
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[error: Bad exit status from /var/tmp/rpm-tmp.taDLCp (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.taDLCp (%build)
]: [The build failed in %build phase.]
=============
[*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.20 but the autoconf macros are from gettext version 0.22
make[2]: *** [Makefile:248: stamp-po] Error 1
make[1]: *** [Makefile:419: all-recursive] Error 1
make: *** [Makefile:360: all] Error 2]: [You are using macros from autotools 0.22 but gettext is in version 0.20.]
|
Issue: There is mismatch in generated Makefile.in.in and available gettext version.
Resolution: You can fix it by forcing updating gettext data at the beginning of the %build section. Put at the top of the %build section following line:
gettextize -f
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
error: Bad exit status from /var/tmp/rpm-tmp.taDLCp (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.taDLCp (%build)
|
The build failed in %build phase.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
*** error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.20 but the autoconf macros are from gettext version 0.22
make[2]: *** [Makefile:248: stamp-po] Error 1
make[1]: *** [Makefile:419: all-recursive] Error 1
make: *** [Makefile:360: all] Error 2
|
You are using macros from autotools 0.22 but gettext is in version 0.20.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Problem: nothing provides requested (python3dist(flit-core) < 4~~ with python3dist(flit-core) >= 3.12)
WARNING: DNF5 command failed, retrying, attempt #3, sleeping 10s]: [The DNF5 command fails since there is a dependency which is not available from any source]
=============
[ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M cbe9e2faae7f43b6ad0663fdc55b13bc -D /var/lib/mock/fedora-42-x86_64-bootstrap-1746776964.163860/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.msb6yihu:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-42-x86_64-1746776964.163860/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --setenv=SYSTEMD_SECCOMP=0 --resolv-conf=off /usr/bin/dnf5 builddep --installroot /var/lib/mock/fedora-42-x86_64-1746776964.163860/root/ --releasever 42 '/var/lib/mock/fedora-42-x86_64-1746776964.163860/root/builddir/build/SRPMS/python-stestr-4.2.0-1.fc42~bootstrap.buildreqs.nosrc.rpm' --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts]: [The container is unable to spawn, because a required package is missing python3dist(flit-core).]
|
Issue: Missing package as dependency, (python3dist(flit-core) < 4~~ with python3dist(flit-core) >= 3.12)
Resolution: Package dependency needs to be met, so if required the package needs to be built from source before the build step.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Problem: nothing provides requested (python3dist(flit-core) < 4~~ with python3dist(flit-core) >= 3.12)
WARNING: DNF5 command failed, retrying, attempt #3, sleeping 10s
|
The DNF5 command fails since there is a dependency which is not available from any source
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M cbe9e2faae7f43b6ad0663fdc55b13bc -D /var/lib/mock/fedora-42-x86_64-bootstrap-1746776964.163860/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.msb6yihu:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-42-x86_64-1746776964.163860/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>\007"' '--setenv=PS1=<mock-chroot> \s-\v\$ ' --setenv=LANG=C.UTF-8 --setenv=LC_MESSAGES=C.UTF-8 --setenv=SYSTEMD_NSPAWN_TMPFS_TMP=0 --setenv=SYSTEMD_SECCOMP=0 --resolv-conf=off /usr/bin/dnf5 builddep --installroot /var/lib/mock/fedora-42-x86_64-1746776964.163860/root/ --releasever 42 '/var/lib/mock/fedora-42-x86_64-1746776964.163860/root/builddir/build/SRPMS/python-stestr-4.2.0-1.fc42~bootstrap.buildreqs.nosrc.rpm' --setopt=deltarpm=False --setopt=allow_vendor_change=yes --allowerasing --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts --setopt=tsflags=nocontexts
|
The container is unable to spawn, because a required package is missing python3dist(flit-core).
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Requirement not satisfied: virtualenv; extra == 'test']: [The requirements from metadata were not satisfied.]
=============
[Requirement not satisfied: graphviz; extra == 'graphviz']: [The requirements from metadata were not satisfied.]
=============
[Requirement not satisfied: pytest-mock>=3.12; extra == 'test']: [The requirements from metadata were not satisfied.]
=============
[Requirement not satisfied: pytest>=7.4.3; extra == 'test']: [The requirements from metadata were not satisfied.]
=============
[No matching package to install: 'python3dist(pip) >= 23.3.1']: [The missing dependent/required package was not matched for installation.]
=============
[Not all dependencies satisfied]: [The dependencies were not satisfied in completion.]
=============
[Error: Some packages could not be found.]: [The required package was not found]
=============
[WARNING: DNF command failed, retrying, attempt #2, sleeping 10s]: [The DNF command failed, it's trying again.]
|
Issue: There were some missing dependencies/required packages. When the DNF command tried to install the packages it failed, because the packages were not matched.
Resolution: Check that correct/available versions of packages are in the metadata. Check that the repos are available.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Requirement not satisfied: virtualenv; extra == 'test'
|
The requirements from metadata were not satisfied.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Requirement not satisfied: graphviz; extra == 'graphviz'
|
The requirements from metadata were not satisfied.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Requirement not satisfied: pytest-mock>=3.12; extra == 'test'
|
The requirements from metadata were not satisfied.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Requirement not satisfied: pytest>=7.4.3; extra == 'test'
|
The requirements from metadata were not satisfied.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
No matching package to install: 'python3dist(pip) >= 23.3.1'
|
The missing dependent/required package was not matched for installation.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Not all dependencies satisfied
|
The dependencies were not satisfied in completion.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Error: Some packages could not be found.
|
The required package was not found
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
WARNING: DNF command failed, retrying, attempt #2, sleeping 10s
|
The DNF command failed, it's trying again.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[+ rspec spec
/usr/bin/rspec:25: warning: syslog is not part of the default gems starting from Ruby 3.4.0. Install syslog from RubyGems.
An error occurred while loading ./spec/abrt_handler_spec.rb. - Did you mean?
rspec ./spec/abrt_spec.rb
Failure/Error: require 'syslog'
LoadError:
cannot load such file -- syslog
# ./lib/abrt/handler.rb:2:in '<top (required)>'
# ./spec/abrt_handler_spec.rb:2:in '<top (required)>']: [When trying to execute tests with rspec, one of the test files failed to load its dependency of 'syslog'.]
|
Issue: Syslog moved from the standard library in Ruby to bundled gems. It is now available in "ruby-bundled-gems"
Resolution: Add "BuildRequires: rubygem(syslog)" to the specfile to install the syslog dependency for tests.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
+ rspec spec
/usr/bin/rspec:25: warning: syslog is not part of the default gems starting from Ruby 3.4.0. Install syslog from RubyGems.
An error occurred while loading ./spec/abrt_handler_spec.rb. - Did you mean?
rspec ./spec/abrt_spec.rb
Failure/Error: require 'syslog'
LoadError:
cannot load such file -- syslog
# ./lib/abrt/handler.rb:2:in '<top (required)>'
# ./spec/abrt_handler_spec.rb:2:in '<top (required)>'
|
When trying to execute tests with rspec, one of the test files failed to load its dependency of 'syslog'.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.