question
stringlengths 236
348k
| answer
stringlengths 10
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:
[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:
[+ /usr/bin/git init -q
/var/tmp/rpm-tmp.fQS1pZ: line 47: /usr/bin/git: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.fQS1pZ (%prep)]: [Error report during %prep phase.]
| Issue: git was missing from BuildRequires. It is used for `%autosetup -S git` macro.
Resolution: Add git to the list of BuildRequires dependencies. |
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/git init -q
/var/tmp/rpm-tmp.fQS1pZ: line 47: /usr/bin/git: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.fQS1pZ (%prep) | Error report during %prep 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:
[Errors during downloading metadata for repository 'opensuse-tumbleweed-oss':
- Status code: 404 for https://slc-mirror.opensuse.org/tumbleweed/repo/oss/repodata/0f99b390d4bfec93be22bd85e64559c810d3295517334259183a66f6afe6d4c5abddb1cb28b677118ace05b2cc1f45373e9f56aa8b46f91cf525e5a2959e2b8e-primary.xml.zst (IP: 2a07:de40:617e:1904::10)
Error: Failed to download metadata for repo 'opensuse-tumbleweed-oss': Yum repo downloading error: Downloading error(s): repodata/0f99b390d4bfec93be22bd85e64559c810d3295517334259183a66f6afe6d4c5abddb1cb28b677118ace05b2cc1f45373e9f56aa8b46f91cf525e5a2959e2b8e-primary.xml.zst - Cannot download, all mirrors were already tried without success
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-atx7kz5m/wezterm-nightly/wezterm.spec) Config(opensuse-tumbleweed-x86_64) 4 minutes 39 seconds
]: [Download of repository metadata timed out]
| Issue: It wasn't possible to fetch metadata of repository due to infrastructure failure
Resolution: Report infrastructure 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:
Errors during downloading metadata for repository 'opensuse-tumbleweed-oss':
- Status code: 404 for https://slc-mirror.opensuse.org/tumbleweed/repo/oss/repodata/0f99b390d4bfec93be22bd85e64559c810d3295517334259183a66f6afe6d4c5abddb1cb28b677118ace05b2cc1f45373e9f56aa8b46f91cf525e5a2959e2b8e-primary.xml.zst (IP: 2a07:de40:617e:1904::10)
Error: Failed to download metadata for repo 'opensuse-tumbleweed-oss': Yum repo downloading error: Downloading error(s): repodata/0f99b390d4bfec93be22bd85e64559c810d3295517334259183a66f6afe6d4c5abddb1cb28b677118ace05b2cc1f45373e9f56aa8b46f91cf525e5a2959e2b8e-primary.xml.zst - Cannot download, all mirrors were already tried without success
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-atx7kz5m/wezterm-nightly/wezterm.spec) Config(opensuse-tumbleweed-x86_64) 4 minutes 39 seconds
| Download of repository metadata timed out |
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:
[type=AVC msg=audit(1747430234.032:32866): avc: denied { read } for pid=718312 comm="rc" name="pmproxy" dev="xvda3" ino=503324563 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:pcp_log_t:s0 tclass=lnk_file permissive=1]: [Selinux issue]
| Issue: pmproxy tried to open a device which was not allowed in pcp-selinux policy
Resolution: pcp-selinux needs to update its selinux rules to be able to access xvda3 device |
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:
type=AVC msg=audit(1747430234.032:32866): avc: denied { read } for pid=718312 comm="rc" name="pmproxy" dev="xvda3" ino=503324563 scontext=system_u:system_r:init_t:s0 tcontext=unconfined_u:object_r:pcp_log_t:s0 tclass=lnk_file permissive=1 | Selinux issue |
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:
[=================================== FAILURES ===================================
_______________________________ test_style_defs ________________________________
]: [test_style_defs failed during the test run]
=============
[> assert expect_line in style_str
E AssertionError: assert '.o { color: #666666 } /* Operator */' in 'pre { line-height: 125%; }\ntd.linenos .normal { color: inherit; background-color: transparent; padding-left: 5px; pa...e.Instance */\n.vm { color: #19177C } /* Name.Variable.Magic */\n.il { color: #666 } /* Literal.Number.Integer.Long */'
]: [Assertion error in the test failed. The test checks if expect_line, whose value is '.o { color: #666666 } /* Operator */' is in the style_str. It isn't, hence the assertion fails.]
=============
[ # Check that a sample of the styles are present
# (use only a sample to make the test more robust
# against Pygments changes).]: [The test tests features related to Pygments library.]
| Issue: A new version of pygments has probably changed generated output of the css files. The test looks for a specific string in the file content and doesn't find it. This causes test to fail.
Resolution: The source code of the package should be updated to incorporate changes happening in the new pygments 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:
=================================== FAILURES ===================================
_______________________________ test_style_defs ________________________________
| test_style_defs failed during the test run |
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:
> assert expect_line in style_str
E AssertionError: assert '.o { color: #666666 } /* Operator */' in 'pre { line-height: 125%; }\ntd.linenos .normal { color: inherit; background-color: transparent; padding-left: 5px; pa...e.Instance */\n.vm { color: #19177C } /* Name.Variable.Magic */\n.il { color: #666 } /* Literal.Number.Integer.Long */'
| Assertion error in the test failed. The test checks if expect_line, whose value is '.o { color: #666666 } /* Operator */' is in the style_str. It isn't, hence the assertion fails. |
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:
# Check that a sample of the styles are present
# (use only a sample to make the test more robust
# against Pygments changes). | The test tests features related to Pygments library. |
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:
[Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/rubygem-rails-7.0.8.6-1.el9.x86_64
RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/rails-7.0.8.6/MIT-LICENSE
Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/rails-7.0.8.6/MIT-LICENSE
]: [This is check at the end of rpmbuild that failed and as a consequence failed the whole build.]
| Issue: During %install phase you or some script installed MIT-LICENSE file to %{buildroot} directory. But this file is neither listed in %files section nor excluded in %files section.
Resolution: This file seems to be important and you should include it in final %files section. Put there:
%files
%license %{gem_instdir}/MIT-LICENSE
Alternatively it may be good idea to move the license file to %{gem_docdir} and use this path in %files section. |
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:
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/rubygem-rails-7.0.8.6-1.el9.x86_64
RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/rails-7.0.8.6/MIT-LICENSE
Installed (but unpackaged) file(s) found:
/usr/share/gems/gems/rails-7.0.8.6/MIT-LICENSE
| This is check at the end of rpmbuild that failed and as a consequence failed the whole 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:
[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.]: [A lookup error while searching for a tox configuration in the current directory]
=============
[ File "/usr/lib/python3.13/site-packages/tox_current_env/hooks4.py", line 82, in tox_add_core_config]: [tox_add_core_config has raised an error becasue the tox config file was not found.]
| Issue: The build failed because the tox config was not found in the current directory which resulted in a an error in the tox_add_core_config function.
Resolution: Ensure that the config file is in the correct directory and is named correctly (tox.ini, setup.cfg, pyproject.toml, or tox.toml).
See https://tox.wiki/en/latest/config.html for details.
|
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. | A lookup error while searching for a tox configuration in the current directory |
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 "/usr/lib/python3.13/site-packages/tox_current_env/hooks4.py", line 82, in tox_add_core_config | tox_add_core_config has raised an error becasue the tox config file was not found. |
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: Installed (but unpackaged) file(s) found:
/usr/share/bash-completion/completions/gdal2tiles.py
/usr/share/bash-completion/completions/gdal2xyz.py
/usr/share/bash-completion/completions/gdal_calc.py
/usr/share/bash-completion/completions/gdal_edit.py
/usr/share/bash-completion/completions/gdal_fillnodata.py
/usr/share/bash-completion/completions/gdal_merge.py
/usr/share/bash-completion/completions/gdal_polygonize.py
/usr/share/bash-completion/completions/gdal_proximity.py
/usr/share/bash-completion/completions/gdal_retile.py
/usr/share/bash-completion/completions/gdal_sieve.py
/usr/share/bash-completion/completions/gdalchksum.py
/usr/share/bash-completion/completions/gdalcompare.py
/usr/share/bash-completion/completions/gdalident.py
/usr/share/bash-completion/completions/gdalimport.py
/usr/share/bash-completion/completions/gdalmove.py
/usr/share/bash-completion/completions/ogrmerge.py
/usr/share/man/man1/gdal2tiles.1.gz
/usr/share/man/man1/gdal_calc.1.gz
/usr/share/man/man1/gdal_edit.1.gz
/usr/share/man/man1/gdal_fillnodata.1.gz
/usr/share/man/man1/gdal_merge.1.gz
/usr/share/man/man1/gdal_pansharpen.1.gz
/usr/share/man/man1/gdal_polygonize.1.gz
/usr/share/man/man1/gdal_proximity.1.gz
/usr/share/man/man1/gdal_retile.1.gz
/usr/share/man/man1/gdal_sieve.1.gz
/usr/share/man/man1/gdalcompare.1.gz
/usr/share/man/man1/gdalmove.1.gz
/usr/share/man/man1/ogr_layer_algebra.1.gz
/usr/share/man/man1/pct2rgb.1.gz
/usr/share/man/man1/rgb2pct.1.gz
Installed (but unpackaged) file(s) found:
/usr/share/bash-completion/completions/gdal2tiles.py
/usr/share/bash-completion/completions/gdal2xyz.py
/usr/share/bash-completion/completions/gdal_calc.py
/usr/share/bash-completion/completions/gdal_edit.py
/usr/share/bash-completion/completions/gdal_fillnodata.py
/usr/share/bash-completion/completions/gdal_merge.py
/usr/share/bash-completion/completions/gdal_polygonize.py
/usr/share/bash-completion/completions/gdal_proximity.py
/usr/share/bash-completion/completions/gdal_retile.py
/usr/share/bash-completion/completions/gdal_sieve.py
/usr/share/bash-completion/completions/gdalchksum.py
/usr/share/bash-completion/completions/gdalcompare.py
/usr/share/bash-completion/completions/gdalident.py
/usr/share/bash-completion/completions/gdalimport.py
/usr/share/bash-completion/completions/gdalmove.py
/usr/share/bash-completion/completions/ogrmerge.py
/usr/share/man/man1/gdal2tiles.1.gz
/usr/share/man/man1/gdal_calc.1.gz
/usr/share/man/man1/gdal_edit.1.gz
/usr/share/man/man1/gdal_fillnodata.1.gz
/usr/share/man/man1/gdal_merge.1.gz
/usr/share/man/man1/gdal_pansharpen.1.gz
/usr/share/man/man1/gdal_polygonize.1.gz
/usr/share/man/man1/gdal_proximity.1.gz
/usr/share/man/man1/gdal_retile.1.gz
/usr/share/man/man1/gdal_sieve.1.gz
/usr/share/man/man1/gdalcompare.1.gz
/usr/share/man/man1/gdalmove.1.gz
/usr/share/man/man1/ogr_layer_algebra.1.gz
/usr/share/man/man1/pct2rgb.1.gz
/usr/share/man/man1/rgb2pct.1.gz]: [It contains the list of unpackaged files.]
| Issue: The package installs multiple files which are not listed under %files in the spec file.
Resolution: The files should either be included in the spec file under %files or not installed. |
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: Installed (but unpackaged) file(s) found:
/usr/share/bash-completion/completions/gdal2tiles.py
/usr/share/bash-completion/completions/gdal2xyz.py
/usr/share/bash-completion/completions/gdal_calc.py
/usr/share/bash-completion/completions/gdal_edit.py
/usr/share/bash-completion/completions/gdal_fillnodata.py
/usr/share/bash-completion/completions/gdal_merge.py
/usr/share/bash-completion/completions/gdal_polygonize.py
/usr/share/bash-completion/completions/gdal_proximity.py
/usr/share/bash-completion/completions/gdal_retile.py
/usr/share/bash-completion/completions/gdal_sieve.py
/usr/share/bash-completion/completions/gdalchksum.py
/usr/share/bash-completion/completions/gdalcompare.py
/usr/share/bash-completion/completions/gdalident.py
/usr/share/bash-completion/completions/gdalimport.py
/usr/share/bash-completion/completions/gdalmove.py
/usr/share/bash-completion/completions/ogrmerge.py
/usr/share/man/man1/gdal2tiles.1.gz
/usr/share/man/man1/gdal_calc.1.gz
/usr/share/man/man1/gdal_edit.1.gz
/usr/share/man/man1/gdal_fillnodata.1.gz
/usr/share/man/man1/gdal_merge.1.gz
/usr/share/man/man1/gdal_pansharpen.1.gz
/usr/share/man/man1/gdal_polygonize.1.gz
/usr/share/man/man1/gdal_proximity.1.gz
/usr/share/man/man1/gdal_retile.1.gz
/usr/share/man/man1/gdal_sieve.1.gz
/usr/share/man/man1/gdalcompare.1.gz
/usr/share/man/man1/gdalmove.1.gz
/usr/share/man/man1/ogr_layer_algebra.1.gz
/usr/share/man/man1/pct2rgb.1.gz
/usr/share/man/man1/rgb2pct.1.gz
Installed (but unpackaged) file(s) found:
/usr/share/bash-completion/completions/gdal2tiles.py
/usr/share/bash-completion/completions/gdal2xyz.py
/usr/share/bash-completion/completions/gdal_calc.py
/usr/share/bash-completion/completions/gdal_edit.py
/usr/share/bash-completion/completions/gdal_fillnodata.py
/usr/share/bash-completion/completions/gdal_merge.py
/usr/share/bash-completion/completions/gdal_polygonize.py
/usr/share/bash-completion/completions/gdal_proximity.py
/usr/share/bash-completion/completions/gdal_retile.py
/usr/share/bash-completion/completions/gdal_sieve.py
/usr/share/bash-completion/completions/gdalchksum.py
/usr/share/bash-completion/completions/gdalcompare.py
/usr/share/bash-completion/completions/gdalident.py
/usr/share/bash-completion/completions/gdalimport.py
/usr/share/bash-completion/completions/gdalmove.py
/usr/share/bash-completion/completions/ogrmerge.py
/usr/share/man/man1/gdal2tiles.1.gz
/usr/share/man/man1/gdal_calc.1.gz
/usr/share/man/man1/gdal_edit.1.gz
/usr/share/man/man1/gdal_fillnodata.1.gz
/usr/share/man/man1/gdal_merge.1.gz
/usr/share/man/man1/gdal_pansharpen.1.gz
/usr/share/man/man1/gdal_polygonize.1.gz
/usr/share/man/man1/gdal_proximity.1.gz
/usr/share/man/man1/gdal_retile.1.gz
/usr/share/man/man1/gdal_sieve.1.gz
/usr/share/man/man1/gdalcompare.1.gz
/usr/share/man/man1/gdalmove.1.gz
/usr/share/man/man1/ogr_layer_algebra.1.gz
/usr/share/man/man1/pct2rgb.1.gz
/usr/share/man/man1/rgb2pct.1.gz | It contains the list of unpackaged files. |
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:
[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:
[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:
[Some test(s) failed.]: [Error message, some test(s) failed.]
=============
[FAIL: Test-proxied-https-auth.px
FAIL: Test-proxied-https-auth-keepalive.px]: [Failed tests]
=============
[============================================================================
Testsuite summary for wget 1.25.0 (Red Hat modified)
============================================================================
# TOTAL: 88
# PASS: 78
# SKIP: 8
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0]: [Testsuite summary]
| Issue: Ttest failed when running the %check phase of the build.
Resolution: Either issue in the code or in the test itself needs to be resolved. It might be a good idea to contact upstream developers. |
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:
Some test(s) failed. | Error message, some test(s) 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:
FAIL: Test-proxied-https-auth.px
FAIL: Test-proxied-https-auth-keepalive.px | 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:
============================================================================
Testsuite summary for wget 1.25.0 (Red Hat modified)
============================================================================
# TOTAL: 88
# PASS: 78
# SKIP: 8
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0 | Testsuite 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:
[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:
[# Failed test 38 in test.pl at line 133
# test.pl line 133 is: ok(RPM2->rpm_api_version =~ /4.\d+/);]: [Test #38 failed on line 133 of test.pl file.]
| Issue: The test failed because the test expected that RPM2->rpm_api_version call will return an RPM library version starting with "4." prefix, while the new 5.99.90 version of the library returns "5.99".
Resolution: The test need to be adapted to accept the new "5.99" version. E.g. the regular expression /4.\d+/ can be changed to /(?:4\.\d+|5\.99\d*|6\.\d+)/. |
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 test 38 in test.pl at line 133
# test.pl line 133 is: ok(RPM2->rpm_api_version =~ /4.\d+/); | Test #38 failed on line 133 of test.pl file. |
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:
[ValueError: invalid pyproject.toml config: `project.license`.
configuration error: `project.license` must be valid exactly by one definition (2 matches found):
- keys:
'file': {type: string}
required: ['file']
- keys:
'text': {type: string}
required: ['text']]: [The key "license" under section "project" in the file "pyproject.toml" contains string. But expected content is either "text" or "file" section.]
| Issue: Because a file pyptoject.toml has wrong format.
Resolution: The key "license" under section "project" in the file "pyproject.toml" should be fixed to correct format. Either file or text. The easisest way would be to change string "MIT" to a section { text = "MIT" } |
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:
ValueError: invalid pyproject.toml config: `project.license`.
configuration error: `project.license` must be valid exactly by one definition (2 matches found):
- keys:
'file': {type: string}
required: ['file']
- keys:
'text': {type: string}
required: ['text'] | The key "license" under section "project" in the file "pyproject.toml" contains string. But expected content is either "text" or "file" section. |
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:
[ Problem: conflicting requests
- nothing provides libllhttp.so.9.0()(64bit) needed by python3-aiohttp-3.8.5-1.eln130.aarch64 from buil]: [The `libllhttp.so.9.0` is needed by `python3-aiohttp` package but cannot be installed ]
| Issue: The `libllhttp.so.9.0` library is needed by `python3-aiohttp` package but cannot be installed because it is not available on Fedora ELN
Resolution: The `libllhttp` library should be provided by the `llhttp-devel` package. You will need to build it for Fedora ELN. |
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: conflicting requests
- nothing provides libllhttp.so.9.0()(64bit) needed by python3-aiohttp-3.8.5-1.eln130.aarch64 from buil | The `libllhttp.so.9.0` is needed by `python3-aiohttp` package but cannot be 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:
[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:
[error: Dependency tokens must begin with alpha-numeric, '_' or '/': ("Opening input file" "No such file or directory" "/builddir/build/BUILD/erlang-26.2.5.11-build/BUILDROOT/usr/share/emacs/site-lisp/erlang/erlang-flymake.el")]: [The error message with dependency token.]
| Issue: Dependency token should be alpha-numeric.
Resolution: Rename dependency token. |
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: Dependency tokens must begin with alpha-numeric, '_' or '/': ("Opening input file" "No such file or directory" "/builddir/build/BUILD/erlang-26.2.5.11-build/BUILDROOT/usr/share/emacs/site-lisp/erlang/erlang-flymake.el") | The error message with dependency token. |
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:
[
DEBUG util.py:459: Failed to resolve the transaction:
DEBUG util.py:459: Package "pyproject-rpm-macros-1.16.3-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-devel-3.13.0-1.fc42.ppc64le" is already installed.
DEBUG util.py:459: Package "python3-hatch-vcs-0.4.0-6.fc41.noarch" is already installed.
DEBUG util.py:459: Package "python3-hatchling-1.25.0-1.fc42.noarch" is already installed.
DEBUG util.py:459: No match for argument: python3dist(mne) >= 1.7
DEBUG util.py:459: Package "python3-packaging-24.2-2.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-pip-24.3.1-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-pytest-8.3.4-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "tomcli-0.8.0-1.fc42.noarch" is already installed.
DEBUG util.py:459: You can try to add to command line:
DEBUG util.py:459: --skip-unavailable to skip unavailable packages
DEBUG util.py:608: Child return code was: 1]: [The builddependecies failed to resolve and buildroot cannot be initiated.]
| Issue: The dependency `python3dist(mne) >= 1.7` could not be satisfied.
Resolution: You have to build the dependency of the required version first.
In this case the dependency was required because of
BuildRequires: %{py3_dist pytest} >= 8
when you relax it to
BuildRequires: %{py3_dist pytest}
it will use the lower version of pytest that is present in Fedora and that will work. |
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:459: Failed to resolve the transaction:
DEBUG util.py:459: Package "pyproject-rpm-macros-1.16.3-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-devel-3.13.0-1.fc42.ppc64le" is already installed.
DEBUG util.py:459: Package "python3-hatch-vcs-0.4.0-6.fc41.noarch" is already installed.
DEBUG util.py:459: Package "python3-hatchling-1.25.0-1.fc42.noarch" is already installed.
DEBUG util.py:459: No match for argument: python3dist(mne) >= 1.7
DEBUG util.py:459: Package "python3-packaging-24.2-2.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-pip-24.3.1-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "python3-pytest-8.3.4-1.fc42.noarch" is already installed.
DEBUG util.py:459: Package "tomcli-0.8.0-1.fc42.noarch" is already installed.
DEBUG util.py:459: You can try to add to command line:
DEBUG util.py:459: --skip-unavailable to skip unavailable packages
DEBUG util.py:608: Child return code was: 1 | The builddependecies failed to resolve and buildroot cannot be initiated. |
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:
[
../../designer/pluginloader.cpp:146:17: error: âPy_SetProgramNameâ was not declared in this scope; did you mean âPy_GetProgramNameâ]: [Py_SetProgramName is not declared in pluginloader.cpp]
| Issue: Py_SetProgramName is not declared.
Resolution: Import/Declare Py_SetProgramName or change the line. |
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:
../../designer/pluginloader.cpp:146:17: error: âPy_SetProgramNameâ was not declared in this scope; did you mean âPy_GetProgramNameâ | Py_SetProgramName is not declared in pluginloader.cpp |
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:
[RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
]: [RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
]
| Issue: This build had unpackaged files, that needed to be addressed.
Resolution: After the files section, it was necessary to add the following lines
%{python3_sitelib}/pulp_glue/deb
%{python3_sitelib}/%{srcname}-%{version}.dist-info/
the %{srcname} macro was defined with pulp_glue_deb, as it was the one highlighted in the error |
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/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
| RPM build errors:
error: Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
Installed (but unpackaged) file(s) found:
/usr/lib/python3.11/site-packages/pulp_glue/deb/__init__.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/__init__.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/__pycache__/context.cpython-311.pyc
/usr/lib/python3.11/site-packages/pulp_glue/deb/context.py
/usr/lib/python3.11/site-packages/pulp_glue/deb/py.typed
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/INSTALLER
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/METADATA
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/WHEEL
/usr/lib/python3.11/site-packages/pulp_glue_deb-0.0.7.dist-info/top_level.txt
|
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:
[gmake[2]: *** [intern/cycles/kernel/CMakeFiles/cycles_kernel_hip.dir/build.make:402: intern/cycles/kernel/kernel_gfx1010.fatbin] Error 1
gmake[2]: Leaving directory '/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build']: [The issue seems impacting HIP for Cycles Rendering Engine using AMD hardware]
=============
[ Building CXX object extern/ceres/CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o
cd /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build/extern/ceres && /usr/bin/ccache /usr/lib64/ccache/g++ -DGFLAGS_DLL_DECL="" -DGFLAGS_DLL_DECLARE_FLAG="" -DGFLAGS_DLL_DEFINE_FLAG="" -DGOOGLE_GLOG_DLL_DECL="" -DHAVE_EXECINFO_H -DNDEBUG -DWITH_ASSERT_ABORT -DWITH_GHOST_WAYLAND_LIBDECOR -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -D__LITTLE_ENDIAN__ -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/include -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/internal -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/config -isystem /usr/include/eigen3 -isystem /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/gflags/src -isystem /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/glog/include -Wuninitialized -Wall -Wno-invalid-offsetof -Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wcomma-subscript -Wformat-signedness -Wrestrict -Wno-suggest-override -Wuninitialized -Wno-stringop-overread -Wno-stringop-overflow -Wimplicit-fallthrough=5 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -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 -Wl,--as-needed -march=x86-64-v2 -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -ffp-contract=off -fmacro-prefix-map="/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/"="" -fmacro-prefix-map="/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build/"="" -Wno-deprecated-declarations -Wno-unused-parameter -Wno-unused-function -Wno-type-limits -Wno-int-in-bool-context -Wno-switch -Wno-unused-variable -Wno-uninitialized -Wno-implicit-fallthrough -Wno-error=unused-but-set-variable -Wno-class-memaccess -Wno-comment -Wno-unused-local-typedefs -Wno-unused-variable -Wno-uninitialized -Wno-maybe-uninitialized -DNDEBUG -std=c++17 -MD -MT extern/ceres/CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o -MF CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o.d -o CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o -c /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/internal/ceres/linear_solver.cc
clang++: error: unknown argument: '--genco']: [--genco parameter unrecognized for clang++]
| Issue: Failure occurred on HIP for Cycles Rendering Engine
Resolution: Fix HIP for Rendering Cycle engine and address the incompatible parameter for clang++ |
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:
gmake[2]: *** [intern/cycles/kernel/CMakeFiles/cycles_kernel_hip.dir/build.make:402: intern/cycles/kernel/kernel_gfx1010.fatbin] Error 1
gmake[2]: Leaving directory '/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build' | The issue seems impacting HIP for Cycles Rendering Engine using AMD hardware |
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:
Building CXX object extern/ceres/CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o
cd /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build/extern/ceres && /usr/bin/ccache /usr/lib64/ccache/g++ -DGFLAGS_DLL_DECL="" -DGFLAGS_DLL_DECLARE_FLAG="" -DGFLAGS_DLL_DEFINE_FLAG="" -DGOOGLE_GLOG_DLL_DECL="" -DHAVE_EXECINFO_H -DNDEBUG -DWITH_ASSERT_ABORT -DWITH_GHOST_WAYLAND_LIBDECOR -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -D__LITTLE_ENDIAN__ -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/include -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/internal -I/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/config -isystem /usr/include/eigen3 -isystem /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/gflags/src -isystem /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/glog/include -Wuninitialized -Wall -Wno-invalid-offsetof -Wno-sign-compare -Wlogical-op -Winit-self -Wmissing-include-dirs -Wno-div-by-zero -Wtype-limits -Wno-char-subscripts -Wno-unknown-pragmas -Wpointer-arith -Wcomma-subscript -Wformat-signedness -Wrestrict -Wno-suggest-override -Wuninitialized -Wno-stringop-overread -Wno-stringop-overflow -Wimplicit-fallthrough=5 -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -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 -Wl,--as-needed -march=x86-64-v2 -fopenmp -pipe -fPIC -funsigned-char -fno-strict-aliasing -ffp-contract=off -fmacro-prefix-map="/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/"="" -fmacro-prefix-map="/builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/redhat-linux-build/"="" -Wno-deprecated-declarations -Wno-unused-parameter -Wno-unused-function -Wno-type-limits -Wno-int-in-bool-context -Wno-switch -Wno-unused-variable -Wno-uninitialized -Wno-implicit-fallthrough -Wno-error=unused-but-set-variable -Wno-class-memaccess -Wno-comment -Wno-unused-local-typedefs -Wno-unused-variable -Wno-uninitialized -Wno-maybe-uninitialized -DNDEBUG -std=c++17 -MD -MT extern/ceres/CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o -MF CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o.d -o CMakeFiles/extern_ceres.dir/internal/ceres/linear_solver.cc.o -c /builddir/build/BUILD/blender-4.4.0-build/blender-4.4.0/extern/ceres/internal/ceres/linear_solver.cc
clang++: error: unknown argument: '--genco' | --genco parameter unrecognized for clang++ |
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/rpm/rpmuncompress -x /builddir/build/SOURCES/78af4ff.zip
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd libbacktrace-1.0
/var/tmp/rpm-tmp.ZcVUQS: line 42: cd: libbacktrace-1.0: No such file or directory]: [Might indicate that source was wrong, since cd to it does not work]
=============
[error: Bad exit status from /var/tmp/rpm-tmp.ZcVUQS (%prep)]: [Failed in %prep]
| Issue: Failed to download proper sources
Resolution: Check how your tarball sourced, maybe check Source: in 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:
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/78af4ff.zip
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd libbacktrace-1.0
/var/tmp/rpm-tmp.ZcVUQS: line 42: cd: libbacktrace-1.0: No such file or directory | Might indicate that source was wrong, since cd to it does not work |
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.ZcVUQS (%prep) | Failed in %prep |
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:
[error: Bad exit status from /var/tmp/rpm-tmp.KjvJPM (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.KjvJPM (%build)
Child return code was: 1]: [The build failed in `%build` phase.]
=============
[/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:91:1: warning: "/*" within comment [-Wcomment]
91 | /*!
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp: In member function ‘virtual bool Dtk::Core::{anonymous}::FileBackend::load(const QString&)’:
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:180:50: warning: ‘T* QScopedPointer<T, Cleanup>::take() [with T = Dtk::Core::DConfigFile; Cleanup = QScopedPointerDeleter<Dtk::Core::DConfigFile>]’ is deprecated: Use std::unique_ptr instead, and call release(). [-Wdeprecated-declarations]
180 | genericConfigFile.reset(file.take());
| ~~~~~~~~~^~
In file included from /usr/include/qt6/QtCore/QScopedPointer:1,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base/dobject.h:8,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/DtkCore/DObject:1,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dconfig.h:9,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:5:
/usr/include/qt6/QtCore/qscopedpointer.h:130:8: note: declared here
130 | T *take() noexcept
| ^~~~
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:181:52: warning: ‘T* QScopedPointer<T, Cleanup>::take() [with T = Dtk::Core::DConfigCache; Cleanup = QScopedPointerDeleter<Dtk::Core::DConfigCache>]’ is deprecated: Use std::unique_ptr instead, and call release(). [-Wdeprecated-declarations]
181 | genericConfigCache.reset(cache.take());
| ~~~~~~~~~~^~
/usr/include/qt6/QtCore/qscopedpointer.h:130:8: note: declared here
130 | T *take() noexcept
| ^~~~
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp: In static member function ‘static QVariant Dtk::Core::{anonymous}::DBusBackend::decodeQDBusArgument(const QVariant&)’:
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:372:49: warning: ‘constexpr typename std::add_const<_Tp>::type& qAsConst(T&) [with T = QList<QVariant>; typename std::add_const<_Tp>::type = const QList<QVariant>]’ is deprecated: Use std::as_const() instead. [-Wdeprecated-declarations]
372 | for (const auto &item : qAsConst(list)) {
| ~~~~~~~~^~~~~~
In file included from /usr/include/qt6/QtCore/qforeach.h:11,
from /usr/include/qt6/QtCore/qglobal.h:57,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dtkcore_global.h:7,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dconfig.h:8:
/usr/include/qt6/QtCore/qttypetraits.h:36:45: note: declared here
36 | constexpr typename std::add_const<T>::type &qAsConst(T &t) noexcept { return t; }
| ^~~~~~~~
[60/80] /usr/bin/g++ -DDSYSINFO_PREFIX=\"\" -DLIBDTKCORE_LIBRARY -DPREFIX=\"/usr\" -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_NO_DEBUG -DQT_XML_LIB -Ddtk6core_EXPORTS -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/redhat-linux-build/src -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/redhat-linux-build/src/dtk6core_autogen/include -I/usr/include/uchardet -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/util -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/dci -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/log -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base/private -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/DtkCore -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/settings -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/filesystem -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include -isystem /usr/include/qt6/QtCore -isystem /usr/include/qt6 -isystem /usr/lib64/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtDBus -isystem /usr/include/qt6/QtXml -isystem /usr/include/dtk6/DLog -isystem /usr/include/qt6/QtCore/6.8.1 -isystem /usr/include/qt6/QtCore/6.8.1/QtCore -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 -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 -fPIC -Wall -Wextra -DNDEBUG -std=gnu++17 -fPIC -MD -MT src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o -MF src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o.d -o src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o -c /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dsysinfo.cpp
ninja: build stopped: subcommand failed.]: [Warning about the usage of deprecated calls.]
| Issue: The build failed in `%build` phase because the code use deprecated calls. Compiler flags like `-Wcomments` and `-Wdeprecated-declarations` makes this fatal error.
Resolution: While you can suppress these flags temporarily, it's better to fix the issues they highlight.
You should contact upstream and replace the deprecated call with code that aligns with current practices. |
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.KjvJPM (%build)
RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.KjvJPM (%build)
Child return code was: 1 | 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:
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:91:1: warning: "/*" within comment [-Wcomment]
91 | /*!
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp: In member function ‘virtual bool Dtk::Core::{anonymous}::FileBackend::load(const QString&)’:
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:180:50: warning: ‘T* QScopedPointer<T, Cleanup>::take() [with T = Dtk::Core::DConfigFile; Cleanup = QScopedPointerDeleter<Dtk::Core::DConfigFile>]’ is deprecated: Use std::unique_ptr instead, and call release(). [-Wdeprecated-declarations]
180 | genericConfigFile.reset(file.take());
| ~~~~~~~~~^~
In file included from /usr/include/qt6/QtCore/QScopedPointer:1,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base/dobject.h:8,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/DtkCore/DObject:1,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dconfig.h:9,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:5:
/usr/include/qt6/QtCore/qscopedpointer.h:130:8: note: declared here
130 | T *take() noexcept
| ^~~~
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:181:52: warning: ‘T* QScopedPointer<T, Cleanup>::take() [with T = Dtk::Core::DConfigCache; Cleanup = QScopedPointerDeleter<Dtk::Core::DConfigCache>]’ is deprecated: Use std::unique_ptr instead, and call release(). [-Wdeprecated-declarations]
181 | genericConfigCache.reset(cache.take());
| ~~~~~~~~~~^~
/usr/include/qt6/QtCore/qscopedpointer.h:130:8: note: declared here
130 | T *take() noexcept
| ^~~~
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp: In static member function ‘static QVariant Dtk::Core::{anonymous}::DBusBackend::decodeQDBusArgument(const QVariant&)’:
/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dconfig.cpp:372:49: warning: ‘constexpr typename std::add_const<_Tp>::type& qAsConst(T&) [with T = QList<QVariant>; typename std::add_const<_Tp>::type = const QList<QVariant>]’ is deprecated: Use std::as_const() instead. [-Wdeprecated-declarations]
372 | for (const auto &item : qAsConst(list)) {
| ~~~~~~~~^~~~~~
In file included from /usr/include/qt6/QtCore/qforeach.h:11,
from /usr/include/qt6/QtCore/qglobal.h:57,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dtkcore_global.h:7,
from /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global/dconfig.h:8:
/usr/include/qt6/QtCore/qttypetraits.h:36:45: note: declared here
36 | constexpr typename std::add_const<T>::type &qAsConst(T &t) noexcept { return t; }
| ^~~~~~~~
[60/80] /usr/bin/g++ -DDSYSINFO_PREFIX=\"\" -DLIBDTKCORE_LIBRARY -DPREFIX=\"/usr\" -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_NO_DEBUG -DQT_XML_LIB -Ddtk6core_EXPORTS -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/redhat-linux-build/src -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/redhat-linux-build/src/dtk6core_autogen/include -I/usr/include/uchardet -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/util -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/dci -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/log -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/base/private -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/global -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/DtkCore -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/settings -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include/filesystem -I/builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/include -isystem /usr/include/qt6/QtCore -isystem /usr/include/qt6 -isystem /usr/lib64/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtDBus -isystem /usr/include/qt6/QtXml -isystem /usr/include/dtk6/DLog -isystem /usr/include/qt6/QtCore/6.8.1 -isystem /usr/include/qt6/QtCore/6.8.1/QtCore -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 -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 -fPIC -Wall -Wextra -DNDEBUG -std=gnu++17 -fPIC -MD -MT src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o -MF src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o.d -o src/CMakeFiles/dtk6core.dir/dsysinfo.cpp.o -c /builddir/build/BUILD/dtk6core-6.0.21-build/dtk6core-6.0.21/src/dsysinfo.cpp
ninja: build stopped: subcommand failed. | Warning about the usage of deprecated calls. |
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:
[stdout: Wrote: /var/lib/copr-rpmbuild/results/pycharm-community-plugins.spec
stderr: warning: Downloading https://plugins.jetbrains.com/files/8183/599893/GitLink-4.5.2.zip#/GitLink-4.5.2.zip to /var/lib/copr-rpmbuild/results/GitLink-4.5.2.zip
warning: Downloading https://plugins.jetbrains.com/files/7792/100135/intellij-ansible-0.11.2.zip#/intellij-ansible-0.11.2.zip to /var/lib/copr-rpmbuild/results/intellij-ansible-0.11.2.zip
warning: Downloading https://plugins.jetbrains.com/files/12552/373650/intellij-rpmspec-2.2.0.zip#/intellij-rpmspec-2.2.0.zip to /var/lib/copr-rpmbuild/results/intellij-rpmspec-2.2.0.zip
warning: Downloading https://plugins.jetbrains.com/files/7724/715275/clouds-docker-impl-251.23774.426.zip#/clouds-docker-impl-251.23774.426.zip to /var/lib/copr-rpmbuild/results/clouds-docker-impl-251.23774.426.zip
warning: Downloading https://plugins.jetbrains.com/files/164/718030/IdeaVIM-2.22.0.zip#/IdeaVIM-2.22.0.zip to /var/lib/copr-rpmbuild/results/IdeaVIM-2.22.0.zip
warning: Downloading https://plugins.jetbrains.com/files/6981/711004/ini-251.23774.318.zip#/ini-251.23774.318.zip to /var/lib/copr-rpmbuild/results/ini-251.23774.318.zip
warning: Downloading https://plugins.jetbrains.com/files/7566/711171/settingsRepository-251.23774.318.zip#/settingsRepository-251.23774.318.zip to /var/lib/copr-rpmbuild/results/settingsRepository-251.23774.318.zip
warning: Downloading https://plugins.jetbrains.com/files/7495/678216/ignore-4.5.6.zip#/ignore-4.5.6.zip to /var/lib/copr-rpmbuild/results/ignore-4.5.6.zip
warning: Downloading https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip to /var/lib/copr-rpmbuild/results/env-files-251.23774.318.zip
curl: (22) The requested URL returned error: 403
error: Executing url helper "/usr/bin/curl --proto -all,+https,+ftps --silent --show-error --fail --globoff --location -o /var/lib/copr-rpmbuild/results/env-files-251.23774.318.zip https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip" failed with status 22
error: Couldn't download https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip
]: [Building SRPM failed because URL does not exists]
| Issue: The build of SRPM package failed because URL specified in SPEC file is wrong
Resolution: Please take a look at the corresponding SPEC file and define proper URL |
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:
stdout: Wrote: /var/lib/copr-rpmbuild/results/pycharm-community-plugins.spec
stderr: warning: Downloading https://plugins.jetbrains.com/files/8183/599893/GitLink-4.5.2.zip#/GitLink-4.5.2.zip to /var/lib/copr-rpmbuild/results/GitLink-4.5.2.zip
warning: Downloading https://plugins.jetbrains.com/files/7792/100135/intellij-ansible-0.11.2.zip#/intellij-ansible-0.11.2.zip to /var/lib/copr-rpmbuild/results/intellij-ansible-0.11.2.zip
warning: Downloading https://plugins.jetbrains.com/files/12552/373650/intellij-rpmspec-2.2.0.zip#/intellij-rpmspec-2.2.0.zip to /var/lib/copr-rpmbuild/results/intellij-rpmspec-2.2.0.zip
warning: Downloading https://plugins.jetbrains.com/files/7724/715275/clouds-docker-impl-251.23774.426.zip#/clouds-docker-impl-251.23774.426.zip to /var/lib/copr-rpmbuild/results/clouds-docker-impl-251.23774.426.zip
warning: Downloading https://plugins.jetbrains.com/files/164/718030/IdeaVIM-2.22.0.zip#/IdeaVIM-2.22.0.zip to /var/lib/copr-rpmbuild/results/IdeaVIM-2.22.0.zip
warning: Downloading https://plugins.jetbrains.com/files/6981/711004/ini-251.23774.318.zip#/ini-251.23774.318.zip to /var/lib/copr-rpmbuild/results/ini-251.23774.318.zip
warning: Downloading https://plugins.jetbrains.com/files/7566/711171/settingsRepository-251.23774.318.zip#/settingsRepository-251.23774.318.zip to /var/lib/copr-rpmbuild/results/settingsRepository-251.23774.318.zip
warning: Downloading https://plugins.jetbrains.com/files/7495/678216/ignore-4.5.6.zip#/ignore-4.5.6.zip to /var/lib/copr-rpmbuild/results/ignore-4.5.6.zip
warning: Downloading https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip to /var/lib/copr-rpmbuild/results/env-files-251.23774.318.zip
curl: (22) The requested URL returned error: 403
error: Executing url helper "/usr/bin/curl --proto -all,+https,+ftps --silent --show-error --fail --globoff --location -o /var/lib/copr-rpmbuild/results/env-files-251.23774.318.zip https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip" failed with status 22
error: Couldn't download https://plugins.jetbrains.com/files/9525/711041/env_files-251.23774.318.zip#/env-files-251.23774.318.zip
| Building SRPM failed because URL does not exists |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.