question
stringlengths 235
464k
| answer
stringlengths 11
2.11k
|
|---|---|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
No match for argument: checkpolicy >= 3.8
|
Missing checkpolicy dependency of the required 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:
No match for argument: policycoreutils-devel >= 3.8
|
Missing policycoreutils-devel of required version
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Test failure message:]: [Test suite error message]
=============
[ throw err;]: [Test suite error message]
|
Issue: Test from package test suite failed.
Resolution: Fix code that was test testing, unfortunately no detailed test logs were provided.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Test failure message:
|
Test suite error message
|
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:
throw err;
|
Test suite error message
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Failed to resolve the transaction:
Problem: cannot install both fuse3-libs-3.17.1-1.fc43.x86_64 from copr_base and fuse3-libs-3.16.2-5.fc42.x86_64 from fedora
- package freerdp-libs-2:3.12.0-2.fc43.x86_64 from fedora requires libfuse3.so.3()(64bit), but none of the providers can be installed
- package freerdp-libs-2:3.12.0-2.fc43.x86_64 from fedora requires libfuse3.so.3(FUSE_3.0)(64bit), but none of the providers can be installed
- package fuse3-devel-3.17.1-1.fc43.x86_64 from copr_base requires libfuse3.so.4()(64bit), but none of the providers can be installed
- package fuse3-devel-3.17.1-1.fc43.x86_64 from copr_base requires fuse3-libs = 3.17.1-1.fc43, but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-client3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-server3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-server-proxy3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-shadow-subsystem3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-shadow3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires librdtk0.so.0()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires freerdp-libs(x86-64) = 2:3.12.0-2.fc43, but none of the providers can be installed
- cannot install the best candidate for the job
You can try to add to command line:
--no-best to not limit the transaction to the best candidates
Copr build error: Build failed]: [This is where the build failed. ]
|
Issue: There are BuildRequires on fuse3-devel and freerdp-devel. While fuse3-devel requires libfuse3.so.4 provided by fuse3-libs-3.17.1-1.fc43 in the copr_base repo, freerdp-devel from the fedora repo requires libfuse3.so.3 provided by fuse3-libs-3.16.2-5.fc42. Those two packages can not be installed both at the same time, causing the build to fail due to unability to install all BuildRequires.
Resolution: Build freerdp in the same copr project, so there is the freerdp-devel package that is linked against and thus require libfuse3.so.4, removing the conflict and allowing the BuildRequires to be installed properly
|
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:
Problem: cannot install both fuse3-libs-3.17.1-1.fc43.x86_64 from copr_base and fuse3-libs-3.16.2-5.fc42.x86_64 from fedora
- package freerdp-libs-2:3.12.0-2.fc43.x86_64 from fedora requires libfuse3.so.3()(64bit), but none of the providers can be installed
- package freerdp-libs-2:3.12.0-2.fc43.x86_64 from fedora requires libfuse3.so.3(FUSE_3.0)(64bit), but none of the providers can be installed
- package fuse3-devel-3.17.1-1.fc43.x86_64 from copr_base requires libfuse3.so.4()(64bit), but none of the providers can be installed
- package fuse3-devel-3.17.1-1.fc43.x86_64 from copr_base requires fuse3-libs = 3.17.1-1.fc43, but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-client3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-server3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-server-proxy3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-shadow-subsystem3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires libfreerdp-shadow3.so.3()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires librdtk0.so.0()(64bit), but none of the providers can be installed
- package freerdp-devel-2:3.12.0-2.fc43.x86_64 from fedora requires freerdp-libs(x86-64) = 2:3.12.0-2.fc43, but none of the providers can be installed
- cannot install the best candidate for the job
You can try to add to command line:
--no-best to not limit the transaction to the best candidates
Copr build error: Build failed
|
This is where the build failed.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[/builddir/build/BUILD/neovim-0.11.0_dev.1664.e71d2c817-build/neovim/src/nvim/lua/treesitter.c:221:27: error: implicit declaration of function âts_language_abi_versionâ; did you mean âts_language_versionâ? [-Wimplicit-function-declaration]
221 | uint32_t lang_version = ts_language_abi_version(lang);
| ^~~~~~~~~~~~~~~~~~~~~~~
| ts_language_version]: [Function `ts_language_abi_version` was used without previous declaration. It is possible that a typo is cause of the problem, since function `ts_language_version` does exist.]
=============
[gmake: *** [Makefile:159: all] Error 2]: [General gmake message, indicating failure of execution on Makefile file line 159, of target `all`.]
|
Issue: Build failed during compilation of source code, due to use of previously undeclared function `ts_language_abi_version`.
Resolution: In C and many other compiled languages, one can not reference a function without previously declaring its signature. Check your source code, and insert function declaration at an appropriate location.
|
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/neovim-0.11.0_dev.1664.e71d2c817-build/neovim/src/nvim/lua/treesitter.c:221:27: error: implicit declaration of function âts_language_abi_versionâ; did you mean âts_language_versionâ? [-Wimplicit-function-declaration]
221 | uint32_t lang_version = ts_language_abi_version(lang);
| ^~~~~~~~~~~~~~~~~~~~~~~
| ts_language_version
|
Function `ts_language_abi_version` was used without previous declaration. It is possible that a typo is cause of the problem, since function `ts_language_version` does exist.
|
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: *** [Makefile:159: all] Error 2
|
General gmake message, indicating failure of execution on Makefile file line 159, of target `all`.
|
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: cannot install the best candidate for the job]: [This is a general error message stating that the build system was unable to find and install the optimal package to fulfill a specific dependency.]
=============
[ - nothing provides nim-srpm-macros needed by redhat-rpm-config-178-1.fc34.noarch from copr_xxmitsu_llvm_priority_10
]: [This part specifies the exact dependency problem.
nim-srpm-macros: This is the package name that's missing.
redhat-rpm-config-178-1.fc34.noarch: This is the package that requires nim-srpm-macros.
copr_xxmitsu_llvm_priority_10: This is the repository from which the redhat-rpm-config package is being pulled.]
|
Issue: The RPM build failed because it couldn't find the required package nim-srpm-macros. This package is a dependency of redhat-rpm-config-178-1.fc34.noarch, which is being pulled from the copr_xxmitsu_llvm_priority_10 repository.
Resolution: Track down package nim-srpm-macros. Contact owner of the package and work with them on a resolution.
|
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: cannot install the best candidate for the job
|
This is a general error message stating that the build system was unable to find and install the optimal package to fulfill a specific dependency.
|
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:
- nothing provides nim-srpm-macros needed by redhat-rpm-config-178-1.fc34.noarch from copr_xxmitsu_llvm_priority_10
|
This part specifies the exact dependency problem.
nim-srpm-macros: This is the package name that's missing.
redhat-rpm-config-178-1.fc34.noarch: This is the package that requires nim-srpm-macros.
copr_xxmitsu_llvm_priority_10: This is the repository from which the redhat-rpm-config package is being pulled.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[error:]: [Error header]
=============
[Installed (but unpackaged) file(s) found:
/usr/lib/tmpfiles.d/mariadb.conf]: [Error description]
|
Issue: RPM build - Installed but unpackaged file found
Resolution: Add the file to the %files section of the SPECfile or remove the file in %install 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:
error:
|
Error header
|
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:
Installed (but unpackaged) file(s) found:
/usr/lib/tmpfiles.d/mariadb.conf
|
Error description
|
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: Command failed:
# /usr/bin/systemd-nspawn -q -M 7f9bc3da00eb41398ea091ef5cd607f2 -D /var/lib/mock/centos-stream-9-x86_64-1749005413.609961/root -a -u mockbuild --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.kf454ns0:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --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 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/originals/dnf.spec']: [It shows the rpmbuild command that failed.]
=============
[error: /builddir/build/originals/dnf.spec: line 285: Unknown option V in ctest(:-:)]: [It shows why the rpmbuild command failed.]
|
Issue: The spec file used for the build (dnf.spec) contains an unknown option V in ctest.
Resolution: The dnf.spec file has to be updated. The unknown option could be removed or replaced by some supported option.
In addition we could figure out why this option isn't supported while it works on other platforms.
|
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 7f9bc3da00eb41398ea091ef5cd607f2 -D /var/lib/mock/centos-stream-9-x86_64-1749005413.609961/root -a -u mockbuild --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.kf454ns0:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --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 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/originals/dnf.spec'
|
It shows the rpmbuild command that 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: /builddir/build/originals/dnf.spec: line 285: Unknown option V in ctest(:-:)
|
It shows why the rpmbuild command 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:
[o/main.c:1475:14: error: ‘bfd_mach_common64’ undeclared (first use in this function); did you mean ‘bfd_mach_msp26’?
1475 | i.mach=OUTPUT_MACH;
| ^~~~~~~~~~~]: [Fatal GCC error which caused the build failure.]
=============
[gcc -DHAVE_CONFIG_H -I. -I./h -I h -I /usr/include/tirpc -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-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -fsigned-char -pipe -fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -std=gnu17 -Wall -Wno-empty-body -Wno-unused-but-set-variable -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -mlongcall -I/usr/include/tirpc -O2 -I o -c -o o/main.o o/main.c]: [GCC invocation which lead to the failure.]
|
Issue: The bfd_mach_common64 function is not declared in the respective compilation unit.
Resolution: Declare in the bfd_mach_common64 function, either manually or by including the respective header. Alternatively, check that the compiler invocation is correct.
|
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:
o/main.c:1475:14: error: ‘bfd_mach_common64’ undeclared (first use in this function); did you mean ‘bfd_mach_msp26’?
1475 | i.mach=OUTPUT_MACH;
| ^~~~~~~~~~~
|
Fatal GCC error which caused the 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:
gcc -DHAVE_CONFIG_H -I. -I./h -I h -I /usr/include/tirpc -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-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -fsigned-char -pipe -fcommon -fno-builtin-malloc -fno-builtin-free -fno-PIE -fno-pie -fno-PIC -fno-pic -std=gnu17 -Wall -Wno-empty-body -Wno-unused-but-set-variable -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -mlongcall -I/usr/include/tirpc -O2 -I o -c -o o/main.o o/main.c
|
GCC invocation which lead to the 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:
[DEBUG util.py:459: No matching package to install: 'iniparser-devel'
DEBUG util.py:461: Package rpm-4.19.1.1-12.el10.ppc64le is already installed.
DEBUG util.py:461: Package sed-4.9-3.el10.ppc64le is already installed.
DEBUG util.py:459: Not all dependencies satisfied
DEBUG util.py:459: Error: Some packages could not be found.]: [dnf complains about a missing package during buildroot setup (iniparser-devel).]
|
Issue: Buildroot setup failed because dnf failed to install required build dependencies (iniparser-devel). In this particular case it's because the iniparser package is not built in EPEL10.
Resolution: Make sure all package (build) dependencies are spelled correctly and are available in respective repositories.
|
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: No matching package to install: 'iniparser-devel'
DEBUG util.py:461: Package rpm-4.19.1.1-12.el10.ppc64le is already installed.
DEBUG util.py:461: Package sed-4.9-3.el10.ppc64le is already installed.
DEBUG util.py:459: Not all dependencies satisfied
DEBUG util.py:459: Error: Some packages could not be found.
|
dnf complains about a missing package during buildroot setup (iniparser-devel).
|
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/python3.14/site-packages/setuptools/_distutils/cmd.py:135: SetuptoolsDeprecationWarning: bdist_wheel.universal is deprecated
!!
********************************************************************************
With Python 2.7 end-of-life, support for building universal wheels
(i.e., wheels that support both Python 2 and Python 3)
is being obviated.
Please discontinue using this option, or if you still need it,
file an issue with pypa/setuptools describing your use case.
By 2025-Aug-30, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
********************************************************************************
!!]: [Warning not relevant for this build, but makes sense to consider while debugging python2.7 applications in the future.]
=============
[INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
fedora 100% | 78.7 KiB/s | 28.4 KiB | 00m00s
Copr repository 100% | 57.0 KiB/s | 1.5 KiB | 00m00s
Repositories loaded.
Failed to resolve the transaction:
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-devel-3.14.0~b2-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-3.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-setuptools-78.1.1-7.fc43.noarch" is already installed.
Problem: cannot install the best candidate for the job
- nothing provides python(abi) = 3.13 needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides python3.13dist(certifi) >= 2017.4.17 needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides (python3.13dist(charset-normalizer) < 4~~ with python3.13dist(charset-normalizer) >= 2) needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides (python3.13dist(idna) < 4~~ with python3.13dist(idna) >= 2.5) needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
You can try to add to command line:]: [Missing dynamic buildrequires packages seem to be the culprit for this build failure]
=============
[Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '78ee3ad797934bc8810467f68a13483c', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1750072132.132465/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.rwsw4_o9:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--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', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-idds-common.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
]: [Due to the missing packages systemd-nspawn is unable to spin up the virtual container, hence deployment fails.]
|
Issue: Problem: cannot install the best candidate for the job
Failed to resolve the transaction:
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-devel-3.14.0~b2-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-3.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-setuptools-78.1.1-7.fc43.noarch" is already installed.
Resolution: To resolve this failure, following can be attempted but since its Copr ttl access may not be possible.
An available official source of the packages should be possible to add in the build 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/python3.14/site-packages/setuptools/_distutils/cmd.py:135: SetuptoolsDeprecationWarning: bdist_wheel.universal is deprecated
!!
********************************************************************************
With Python 2.7 end-of-life, support for building universal wheels
(i.e., wheels that support both Python 2 and Python 3)
is being obviated.
Please discontinue using this option, or if you still need it,
file an issue with pypa/setuptools describing your use case.
By 2025-Aug-30, you need to update your project and remove deprecated calls
or your builds will no longer be supported.
********************************************************************************
!!
|
Warning not relevant for this build, but makes sense to consider while debugging python2.7 applications in the future.
|
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:
INFO: Going to install missing dynamic buildrequires
Updating and loading repositories:
fedora 100% | 78.7 KiB/s | 28.4 KiB | 00m00s
Copr repository 100% | 57.0 KiB/s | 1.5 KiB | 00m00s
Repositories loaded.
Failed to resolve the transaction:
Package "pyproject-rpm-macros-1.18.1-1.fc43.noarch" is already installed.
Package "python3-devel-3.14.0~b2-3.fc43.x86_64" is already installed.
Package "python3-packaging-25.0-3.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-pip-25.1.1-4.fc43.noarch" is already installed.
Package "python3-setuptools-78.1.1-7.fc43.noarch" is already installed.
Problem: cannot install the best candidate for the job
- nothing provides python(abi) = 3.13 needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides python3.13dist(certifi) >= 2017.4.17 needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides (python3.13dist(charset-normalizer) < 4~~ with python3.13dist(charset-normalizer) >= 2) needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
- nothing provides (python3.13dist(idna) < 4~~ with python3.13dist(idna) >= 2.5) needed by python3-requests-2.32.4-1.fc43.noarch from copr_base
You can try to add to command line:
|
Missing dynamic buildrequires packages seem to be the culprit for this 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:
Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '78ee3ad797934bc8810467f68a13483c', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1750072132.132465/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.rwsw4_o9:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--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', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-idds-common.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False
|
Due to the missing packages systemd-nspawn is unable to spin up the virtual container, hence deployment fails.
|
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:
[npm error code ENOTFOUND
npm error syscall getaddrinfo
npm error errno ENOTFOUND
npm error network request to https://registry.npmjs.org/@babel%2fcore failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly. See: 'npm help config']: [Request to npm repository has failed.]
|
Issue: The request to npm package repository has failed, causing build failure, as necessary dependencies couldn't be installed.
Resolution: Ensure that your network connection is fully functional and that the npm repository is online and reachable from you region. It is possible that you have problems with network settings.
Misconfigured proxy, VPN or firewall could be the issue.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
npm error code ENOTFOUND
npm error syscall getaddrinfo
npm error errno ENOTFOUND
npm error network request to https://registry.npmjs.org/@babel%2fcore failed, reason: getaddrinfo ENOTFOUND registry.npmjs.org
npm error network This is a problem related to network connectivity.
npm error network In most cases you are behind a proxy or have bad network settings.
npm error network
npm error network If you are behind a proxy, please make sure that the
npm error network 'proxy' config is set properly. See: 'npm help config'
|
Request to npm repository has 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:
[gmake[2]: *** [vendor/CMakeFiles/libadb.dir/build.make:78: vendor/app_processes.pb.h] Error 1]: [Build has failed on line 78 of the `vendor/CMakeFiles/libadb.dir/build.make` while working with `vendor/app_processes.pb.h` source file, with code 1.]
=============
[gmake[1]: *** Waiting for unfinished jobs.]: [Unfinished jobs of the build are still continuing. ]
=============
[gmake: *** [Makefile:159: all] Error 2]: [Program `gmake` exited with code 2, indicating error. This happened while working on target `all` in the file `Makefile` on line 159.]
=============
[ # /usr/bin/systemd-nspawn -q -M 971615ef9ea540b5aab33085b8645de6 -D /var/lib/mock/rhel+epel-9-x86_64-1741087988.628519/root -a -u mockbuild --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.1jxg69c3:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --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 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/originals/android-tools.spec']: [General error indicating build failure.]
=============
[app_processes.proto: This file contains proto3 optional fields, but --experimental_allow_proto3_optional was not set.]: [File `app_process.proto` contains proto3 optional fields, but flag allowing these fields `--experimental_allow_proto3_optional` was not set.]
|
Issue: File `app_process.proto` contained fields not supported by default flags used for build.
Resolution: Rerun the build with appropriate flags set, or make sure that all source files contain only supported features. In this case `app_process.proto` contained fields that are only supported by `--experimental_allow_proto3_optional` flag. Without it, the fields are not allowed.
Alternatively you can modify the file `app_process.proto` so it doesn't contain prohibited fields.
|
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]: *** [vendor/CMakeFiles/libadb.dir/build.make:78: vendor/app_processes.pb.h] Error 1
|
Build has failed on line 78 of the `vendor/CMakeFiles/libadb.dir/build.make` while working with `vendor/app_processes.pb.h` source file, with code 1.
|
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[1]: *** Waiting for unfinished jobs.
|
Unfinished jobs of the build are still continuing.
|
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: *** [Makefile:159: all] Error 2
|
Program `gmake` exited with code 2, indicating error. This happened while working on target `all` in the file `Makefile` on line 159.
|
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/systemd-nspawn -q -M 971615ef9ea540b5aab33085b8645de6 -D /var/lib/mock/rhel+epel-9-x86_64-1741087988.628519/root -a -u mockbuild --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.1jxg69c3:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --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 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/originals/android-tools.spec'
|
General error indicating 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:
app_processes.proto: This file contains proto3 optional fields, but --experimental_allow_proto3_optional was not set.
|
File `app_process.proto` contains proto3 optional fields, but flag allowing these fields `--experimental_allow_proto3_optional` was not set.
|
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/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 1: ‘operator==(int, int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 2: ‘operator==(int, long long unsigned int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘long long unsigned int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 3: ‘operator==(long long unsigned int, int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 4: ‘operator==(long long unsigned int, long long unsigned int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘long long unsigned int’
/usr/include/vulkan/vulkan.hpp:203:8: note: candidate 5: ‘template<unsigned int N, unsigned int M> bool vk::operator==(const ArrayWrapper1D<char, N>&, const ArrayWrapper1D<char, M>&)’
]: [This is reference to 64bits structure that cannot be satisfied on 32bit system.]
|
Issue: The sources uses 64bit code that cannot be build for 32 bit system.
Resolution: Stop building for i386 by adding this to SPEC file:
ExcludeArch: %{ix86}
|
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/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 1: ‘operator==(int, int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 2: ‘operator==(int, long long unsigned int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘long long unsigned int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 3: ‘operator==(long long unsigned int, int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘int’
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: candidate 4: ‘operator==(long long unsigned int, long long unsigned int)’ (built-in)
/usr/include/vulkan/vulkan_structs.hpp:20196:75: note: no known conversion for argument 2 from ‘const vk::CuModuleNVX’ to ‘long long unsigned int’
/usr/include/vulkan/vulkan.hpp:203:8: note: candidate 5: ‘template<unsigned int N, unsigned int M> bool vk::operator==(const ArrayWrapper1D<char, N>&, const ArrayWrapper1D<char, M>&)’
|
This is reference to 64bits structure that cannot be satisfied on 32bit system.
|
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:
[Jul 18 20:38:41.497677 np0038011187 manila-share[112678]: INFO manila.message.api [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Creating message record for request_id = req-f0277365-7975-401d-95be-7d4bde732876
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Shrink share failed due to possible data loss.: manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 210, in rados_command
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager raise rados.Error(outs, ret)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager rados.Error: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager During handling of the above exception, another exception occurred:
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 624, in shrink_share
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager rados_command(self.rados_client, "fs subvolume resize", argdict)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 222, in rados_command
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager raise exception.ShareBackendException(msg)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager manila.exception.ShareBackendException: json_command failed - prefix=fs subvolume resize, argdict={'vol_name': 'cephfs', 'sub_name': '98643f14-a311-4289-9cc4-9db9ead6526d', 'new_size': 1073741824, 'no_shrink': True, 'format': 'json'} - exception message: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'.
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager During handling of the above exception, another exception occurred:
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/manager.py", line 4776, in shrink_share
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager self.driver.shrink_share(
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 627, in shrink_share
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager raise exception.ShareShrinkingPossibleDataLoss(
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.581407 np0038011187 manila-share[112678]: DEBUG manila.quota [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Rolled back reservations ['edd4a37e-622a-4e0b-8a84-3f8aac2bdefa', '416275ad-9530-45cb-8639-bc3e86b6e048'] {{(pid=112678) rollback /opt/stack/manila/manila/quota.py:1089}}
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Exception during message handling: manila.exception.ShareShrinkingError: Share 107f4edb-27c2-42f9-9b3d-a67287b6f7f8 could not be shrunk due to error in the driver: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 210, in rados_command
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise rados.Error(outs, ret)
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server rados.Error: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 624, in shrink_share
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server rados_command(self.rados_client, "fs subvolume resize", argdict)
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 222, in rados_command
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareBackendException(msg)
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareBackendException: json_command failed - prefix=fs subvolume resize, argdict={'vol_name': 'cephfs', 'sub_name': '98643f14-a311-4289-9cc4-9db9ead6526d', 'new_size': 1073741824, 'no_shrink': True, 'format': 'json'} - exception message: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'.
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4776, in shrink_share
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server self.driver.shrink_share(
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 627, in shrink_share
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareShrinkingPossibleDataLoss(
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 241, in wrapped
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/utils.py", line 484, in wrapper
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4797, in shrink_share
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server error_occurred(e, **error_params)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4747, in error_occurred
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareShrinkingError(
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareShrinkingError: Share 107f4edb-27c2-42f9-9b3d-a67287b6f7f8 could not be shrunk due to error in the driver: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server ]: [It contains the traceback from the python process in OpenStack Manila that identifies a failure while resizing a shared file system]
|
Issue: The share driver detected that the size requested is lesser than the size occupied by data in the shared file system
Resolution: the user must request a bigger size
|
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:
Jul 18 20:38:41.497677 np0038011187 manila-share[112678]: INFO manila.message.api [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Creating message record for request_id = req-f0277365-7975-401d-95be-7d4bde732876
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Shrink share failed due to possible data loss.: manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 210, in rados_command
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager raise rados.Error(outs, ret)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager rados.Error: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager During handling of the above exception, another exception occurred:
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 624, in shrink_share
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager rados_command(self.rados_client, "fs subvolume resize", argdict)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 222, in rados_command
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager raise exception.ShareBackendException(msg)
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager manila.exception.ShareBackendException: json_command failed - prefix=fs subvolume resize, argdict={'vol_name': 'cephfs', 'sub_name': '98643f14-a311-4289-9cc4-9db9ead6526d', 'new_size': 1073741824, 'no_shrink': True, 'format': 'json'} - exception message: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'.
Jul 18 20:38:41.528467 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager During handling of the above exception, another exception occurred:
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager Traceback (most recent call last):
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/manager.py", line 4776, in shrink_share
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager self.driver.shrink_share(
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 627, in shrink_share
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager raise exception.ShareShrinkingPossibleDataLoss(
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.533065 np0038011187 manila-share[112678]: ERROR manila.share.manager
Jul 18 20:38:41.581407 np0038011187 manila-share[112678]: DEBUG manila.quota [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Rolled back reservations ['edd4a37e-622a-4e0b-8a84-3f8aac2bdefa', '416275ad-9530-45cb-8639-bc3e86b6e048'] {{(pid=112678) rollback /opt/stack/manila/manila/quota.py:1089}}
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server [None req-f0277365-7975-401d-95be-7d4bde732876 tempest-TestShareShrinkNFS-825981263 None] Exception during message handling: manila.exception.ShareShrinkingError: Share 107f4edb-27c2-42f9-9b3d-a67287b6f7f8 could not be shrunk due to error in the driver: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 210, in rados_command
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise rados.Error(outs, ret)
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server rados.Error: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 624, in shrink_share
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server rados_command(self.rados_client, "fs subvolume resize", argdict)
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 222, in rados_command
Jul 18 20:38:41.585408 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareBackendException(msg)
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareBackendException: json_command failed - prefix=fs subvolume resize, argdict={'vol_name': 'cephfs', 'sub_name': '98643f14-a311-4289-9cc4-9db9ead6526d', 'new_size': 1073741824, 'no_shrink': True, 'format': 'json'} - exception message: [errno -22] Can't resize the subvolume. The new size '1073741824' would be lesser than the current used size '1342177280'.
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4776, in shrink_share
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server self.driver.shrink_share(
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/drivers/cephfs/driver.py", line 627, in shrink_share
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareShrinkingPossibleDataLoss(
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareShrinkingPossibleDataLoss: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server During handling of the above exception, another exception occurred:
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server Traceback (most recent call last):
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message)
Jul 18 20:38:41.589182 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/dispatcher.py", line 309, in dispatch
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/data/venv/lib/python3.10/site-packages/oslo_messaging/rpc/dispatcher.py", line 229, in _do_dispatch
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 241, in wrapped
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return f(self, *args, **kwargs)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/utils.py", line 484, in wrapper
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server return func(self, *args, **kwargs)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4797, in shrink_share
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server error_occurred(e, **error_params)
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server File "/opt/stack/manila/manila/share/manager.py", line 4747, in error_occurred
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server raise exception.ShareShrinkingError(
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server manila.exception.ShareShrinkingError: Share 107f4edb-27c2-42f9-9b3d-a67287b6f7f8 could not be shrunk due to error in the driver: Share 98643f14-a311-4289-9cc4-9db9ead6526d could not be shrunk due to possible data loss
Jul 18 20:38:41.592017 np0038011187 manila-share[112678]: ERROR oslo_messaging.rpc.server
|
It contains the traceback from the python process in OpenStack Manila that identifies a failure while resizing a shared file system
|
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:
[============================================================================
Testsuite summary for genimage 18
============================================================================
# TOTAL: 57
# PASS: 44
# SKIP: 11
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 1]: [testsuite result summary]
=============
[ERROR: test/filesystem.test - exited with status 1]: [test with error state]
=============
[FAIL: test/filesystem.test 2 - cramfs]: [test with failed state]
|
Issue: Testsuite ended with one failed and one test in error state
Resolution: Check test results and fix either code or test
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
============================================================================
Testsuite summary for genimage 18
============================================================================
# TOTAL: 57
# PASS: 44
# SKIP: 11
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 1
|
testsuite result summary
|
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: test/filesystem.test - exited with status 1
|
test with error state
|
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/filesystem.test 2 - cramfs
|
test with failed state
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Patch #503 (expat-CVE-2022-25315.patch):
+ echo 'Patch #503 (expat-CVE-2022-25315.patch):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p1 -b --suffix .expat-CVE-2022-25315 --fuzz=2
patching file parser/expat/lib/xmlparse.c
Hunk #1 succeeded at 2491 (offset 12 lines).
Hunk #2 FAILED at 2491.
1 out of 2 hunks FAILED -- saving rejects to file parser/expat/lib/xmlparse.c.rej
error: Bad exit status from /var/tmp/rpm-tmp.ygjz40 (%prep)]: [This snippet contains the relevant lines where the build failed. Applying patch #503 (expat-CVE-2022-25315.patch) to the sources failed.]
|
Issue: The patch expat-CVE-2022-25315.patch could not be applied because the source portion where it is to be applied to changed at line 2491 or following.
Resolution: Inspect the new source code and determine differences to the source code context in the patch. It could be a source code line changed that is to be removed with the patch, or the surrounding context lines were altered.
The patch needs to be adapted to the changes and regenerated and the resulting file be added to dist-git.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Patch #503 (expat-CVE-2022-25315.patch):
+ echo 'Patch #503 (expat-CVE-2022-25315.patch):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p1 -b --suffix .expat-CVE-2022-25315 --fuzz=2
patching file parser/expat/lib/xmlparse.c
Hunk #1 succeeded at 2491 (offset 12 lines).
Hunk #2 FAILED at 2491.
1 out of 2 hunks FAILED -- saving rejects to file parser/expat/lib/xmlparse.c.rej
error: Bad exit status from /var/tmp/rpm-tmp.ygjz40 (%prep)
|
This snippet contains the relevant lines where the build failed. Applying patch #503 (expat-CVE-2022-25315.patch) to the sources 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:
[clang++ -MD -MF obj/skia/rust_png_ffi_cxx_generated/FFI.rs.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_EXTENSIVE -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCPP_INSTRUMENTED_WITH_ASAN=0 -DCR_LIBCXX_REVISION=7f8b68f91ca8b192375f5e71cd81fb3ed9650ef3 -DTMP_REBUILD_HACK -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DSK_ENABLE_SKSL -DSK_UNTIL_CRBUG_1187654_IS_FIXED -DSK_USER_CONFIG_HEADER=\"../../skia/config/SkUserConfig.h\" -DSK_WIN_FONTMGR_NO_SIMULATIONS -DSK_DISABLE_LEGACY_INIT_DECODERS -DSK_CODEC_DECODES_JPEG -DSK_CODEC_ENCODES_JPEG -DSK_GAMMA_EXPONENT=1.2 -DSK_GAMMA_CONTRAST=0.2 -DSK_GANESH -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DSK_GL -DSK_VULKAN=1 -DSK_GRAPHITE -DSK_DAWN -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_WAYLAND_KHR -DCR_CXX_INCLUDE=\"third_party/rust/chromium_crates_io/vendor/cxx-1.0.141/include/cxx.h\" -I../.. -Igen -I../../buildtools/third_party/libc++ -I../../third_party/skia -Igen/third_party/skia -I../../third_party/wuffs/src/release/c -I../../third_party/vulkan/include -I../../third_party/vulkan-headers/src/include -I../../third_party/wayland/src/src -I../../third_party/wayland/include/src -Igen/third_party/dawn/include -I../../third_party/dawn/include -fno-delete-null-pointer-checks -fno-strict-overflow -fno-ident -fno-strict-aliasing -fstack-protector-strong -ftrivial-auto-var-init=zero -fwrapv -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fno-sized-deallocation -fcrash-diagnostics-dir=../../tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -mllvm -split-threshold-for-reg-with-hint=0 -ffp-contract=off -Wa,--crel,--allow-experimental-crel -fcomplete-member-pointers -m64 -ffile-compilation-dir=. -no-canonical-prefixes -ftrivial-auto-var-init=pattern -O2 -fdata-sections -ffunction-sections -fno-unique-section-names -fno-math-errno -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wno-redundant-parens -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-misleading-indentation -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wloop-analysis -Wno-unneeded-internal-declaration -Wno-cast-function-type -Wno-thread-safety-reference-return -Wno-nontrivial-memcall -std=c++20 -Wno-trigraphs -gsimple-template-names -fno-exceptions -fno-rtti -nostdinc++ -isystem../../third_party/libc++/src/include -isystem../../third_party/libc++abi/src/include -fvisibility-inlines-hidden -Wno-invalid-offsetof -Wenum-compare-conditional -Wno-c++11-narrowing-const-reference -Wno-missing-template-arg-list-after-template-kw -Wno-deprecated-declarations -Wno-unknown-warning-option -Wno-unused-command-line-argument -Wno-unused-but-set-variable -Wno-unused-result -Wno-unused-function -Wno-unused-variable -Wno-unused-const-variable -Wno-unneeded-internal-declaration -Wno-unknown-attributes -Wno-unknown-pragmas -faltivec-src-compat=mixed -Wno-deprecated-altivec-src-compat -c gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc -o obj/skia/rust_png_ffi_cxx_generated/FFI.rs.o
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:59: error: no member named 'unique_ptr' in namespace 'std'
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:91: error: expected '(' for function-style cast or type construction
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:93: error: use of undeclared identifier 'input'
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:99: error: expected ';' after top level declarator
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ^
| ;
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:59: error: no member named 'unique_ptr' in namespace 'std'
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:92: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:94: error: use of undeclared identifier 'output'
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:118: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:141: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:171: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:193: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:237: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:286: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:298: error: expected ';' after top level declarator
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ^
| ;
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:29: error: no member named 'unique_ptr' in namespace 'std'
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:61: error: expected '(' for function-style cast or type construction
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:62: error: expected expression
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1123:30: error: no member named 'unique_ptr' in namespace 'std'
1123 | static_assert(alignof(::std::unique_ptr<::rust_png::ReadTrait>) == alignof(void *), "");
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1123:62: error: expected '(' for function-style cast or type construction
1123 | static_assert(alignof(::std::unique_ptr<::rust_png::ReadTrait>) == alignof(void *), "");
| ~~~~~~~~~~~~~~~~~~~~~^]: [The error messages indicate that the compiler cannot find std::unique_ptr. This typically means that the C++ standard library headers were not included correctly]
|
Issue: The build failed because does not find the correct headers where std::unique_ptr is defined.
Resolution: Edit third_party/skia/experimental/rust_png/ffi/FFI.h and add #include <memory> at the very top of the 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:
clang++ -MD -MF obj/skia/rust_png_ffi_cxx_generated/FFI.rs.o.d -DUSE_UDEV -DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_OZONE=1 -DOFFICIAL_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DNO_UNWIND_TABLES -D_GNU_SOURCE -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_EXTENSIVE -D_LIBCPP_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCXXABI_DISABLE_VISIBILITY_ANNOTATIONS -D_LIBCPP_INSTRUMENTED_WITH_ASAN=0 -DCR_LIBCXX_REVISION=7f8b68f91ca8b192375f5e71cd81fb3ed9650ef3 -DTMP_REBUILD_HACK -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DSK_ENABLE_SKSL -DSK_UNTIL_CRBUG_1187654_IS_FIXED -DSK_USER_CONFIG_HEADER=\"../../skia/config/SkUserConfig.h\" -DSK_WIN_FONTMGR_NO_SIMULATIONS -DSK_DISABLE_LEGACY_INIT_DECODERS -DSK_CODEC_DECODES_JPEG -DSK_CODEC_ENCODES_JPEG -DSK_GAMMA_EXPONENT=1.2 -DSK_GAMMA_CONTRAST=0.2 -DSK_GANESH -DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\" -DSK_GL -DSK_VULKAN=1 -DSK_GRAPHITE -DSK_DAWN -DVK_USE_PLATFORM_XCB_KHR -DVK_USE_PLATFORM_WAYLAND_KHR -DCR_CXX_INCLUDE=\"third_party/rust/chromium_crates_io/vendor/cxx-1.0.141/include/cxx.h\" -I../.. -Igen -I../../buildtools/third_party/libc++ -I../../third_party/skia -Igen/third_party/skia -I../../third_party/wuffs/src/release/c -I../../third_party/vulkan/include -I../../third_party/vulkan-headers/src/include -I../../third_party/wayland/src/src -I../../third_party/wayland/include/src -Igen/third_party/dawn/include -I../../third_party/dawn/include -fno-delete-null-pointer-checks -fno-strict-overflow -fno-ident -fno-strict-aliasing -fstack-protector-strong -ftrivial-auto-var-init=zero -fwrapv -fno-unwind-tables -fno-asynchronous-unwind-tables -fPIC -pthread -fcolor-diagnostics -fmerge-all-constants -fno-sized-deallocation -fcrash-diagnostics-dir=../../tools/clang/crashreports -mllvm -instcombine-lower-dbg-declare=0 -mllvm -split-threshold-for-reg-with-hint=0 -ffp-contract=off -Wa,--crel,--allow-experimental-crel -fcomplete-member-pointers -m64 -ffile-compilation-dir=. -no-canonical-prefixes -ftrivial-auto-var-init=pattern -O2 -fdata-sections -ffunction-sections -fno-unique-section-names -fno-math-errno -fno-omit-frame-pointer -g0 -fvisibility=hidden -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare -Wno-redundant-parens -Wall -Wno-unused-variable -Wno-c++11-narrowing -Wno-unused-but-set-variable -Wno-misleading-indentation -Wno-missing-field-initializers -Wno-unused-parameter -Wno-psabi -Wloop-analysis -Wno-unneeded-internal-declaration -Wno-cast-function-type -Wno-thread-safety-reference-return -Wno-nontrivial-memcall -std=c++20 -Wno-trigraphs -gsimple-template-names -fno-exceptions -fno-rtti -nostdinc++ -isystem../../third_party/libc++/src/include -isystem../../third_party/libc++abi/src/include -fvisibility-inlines-hidden -Wno-invalid-offsetof -Wenum-compare-conditional -Wno-c++11-narrowing-const-reference -Wno-missing-template-arg-list-after-template-kw -Wno-deprecated-declarations -Wno-unknown-warning-option -Wno-unused-command-line-argument -Wno-unused-but-set-variable -Wno-unused-result -Wno-unused-function -Wno-unused-variable -Wno-unused-const-variable -Wno-unneeded-internal-declaration -Wno-unknown-attributes -Wno-unknown-pragmas -faltivec-src-compat=mixed -Wno-deprecated-altivec-src-compat -c gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc -o obj/skia/rust_png_ffi_cxx_generated/FFI.rs.o
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:59: error: no member named 'unique_ptr' in namespace 'std'
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:91: error: expected '(' for function-style cast or type construction
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:93: error: use of undeclared identifier 'input'
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:919:99: error: expected ';' after top level declarator
919 | ::rust::Box<::rust_png::ResultOfReader> new_reader(::std::unique_ptr<::rust_png::ReadTrait> input) noexcept {
| ^
| ;
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:59: error: no member named 'unique_ptr' in namespace 'std'
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:92: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:94: error: use of undeclared identifier 'output'
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:118: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:141: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:171: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:193: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:237: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:286: error: expected '(' for function-style cast or type construction
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1051:298: error: expected ';' after top level declarator
1051 | ::rust::Box<::rust_png::ResultOfWriter> new_writer(::std::unique_ptr<::rust_png::WriteTrait> output, ::std::uint32_t width, ::std::uint32_t height, ::rust_png::ColorType color, ::std::uint8_t bits_per_component, ::rust_png::Compression compression, ::rust::Slice<::std::uint8_t const> icc_profile) noexcept {
| ^
| ;
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:29: error: no member named 'unique_ptr' in namespace 'std'
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:61: error: expected '(' for function-style cast or type construction
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ~~~~~~~~~~~~~~~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1122:62: error: expected expression
1122 | static_assert(sizeof(::std::unique_ptr<::rust_png::ReadTrait>) == sizeof(void *), "");
| ^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1123:30: error: no member named 'unique_ptr' in namespace 'std'
1123 | static_assert(alignof(::std::unique_ptr<::rust_png::ReadTrait>) == alignof(void *), "");
| ~~~~~~~^
gen/third_party/skia/experimental/rust_png/ffi/FFI.rs.cc:1123:62: error: expected '(' for function-style cast or type construction
1123 | static_assert(alignof(::std::unique_ptr<::rust_png::ReadTrait>) == alignof(void *), "");
| ~~~~~~~~~~~~~~~~~~~~~^
|
The error messages indicate that the compiler cannot find std::unique_ptr. This typically means that the C++ standard library headers were not included correctly
|
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: Bad exit status from /var/tmp/rpm-tmp.WWpyzw (%build)
Bad exit status from /var/tmp/rpm-tmp.WWpyzw (%build)
Child return code was: 1
]: [The build failed in %build section.]
=============
[ 98 | explodeGIF (raw, nraw, wp, hp, pixap, ra, ga, ba, errmsg)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:111:13: error: too many arguments to function ‘LoadGIF’; expected 0, have 1
111 | if (LoadGIF (&pi) != 1)
| ^~~~~~~ ~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:95:12: note: declared here
95 | static int LoadGIF();
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘LoadGIF’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:124:12: warning: old-style function definition [-Wold-style-definition]
124 | static int LoadGIF(pinfo)
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:144:13: error: too many arguments to function ‘gifError’; expected 0, have 2
144 | return( gifError(pinfo, "not enough memory to read gif file") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:150:19: error: too many arguments to function ‘gifError’; expected 0, have 2
150 | else return( gifError(pinfo, "not a GIF file"));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:172:24: error: too many arguments to function ‘gifError’; expected 0, have 2
172 | if (!gif89) return(gifError(pinfo,"corrupt GIF file (screen descriptor)"));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:244:15: warning: variable ‘ch’ set but not used [-Wunused-but-set-variable]
244 | int ch, j, sbsize, cmtlen;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:68: warning: variable ‘bg’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:64: warning: variable ‘fg’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:55: warning: variable ‘cHeight’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:47: warning: variable ‘cWidth’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:268:22: warning: variable ‘ch’ set but not used [-Wunused-but-set-variable]
268 | int j,sbsize,ch;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:355:16: error: too many arguments to function ‘readImage’; expected 0, have 1
355 | else if (readImage(pinfo)) gotimage = 1;
| ^~~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:81:14: note: declared here
81 | static int readImage();
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:371:31: error: too many arguments to function ‘gifError’; expected 0, have 2
371 | if (!gotimage) return gifError(pinfo, str);
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:372:22: error: too many arguments to function ‘gifError’; expected 0, have 2
372 | else return( gifError(pinfo, str));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:382:14: error: too many arguments to function ‘gifError’; expected 0, have 2
382 | return( gifError(pinfo, "no image data found in GIF file") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘readImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:389:12: warning: old-style function definition [-Wold-style-definition]
389 | static int readImage(pinfo)
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘lstsqr’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:422:13: error: too many arguments to function ‘gifError’; expected 0, have 2
422 | return (gifError (pinfo, "No colormap in this GIF file."));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:63:39: error: passing argument 5 of ‘amoeba’ from incompatible pointer type [-Wincompatible-pointer-types]
63 | ret = amoeba (p, y, np, ftol, chisqr_1based, &iter);
| ^~~~~~~~~~~~~
| |
| double (*)(double *)
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:15:14: note: expected ‘double (*)(void)’ but argument is of type ‘double (*)(double *)’
15 | double (*funk)(), int *nfunk);
| ~~~~~~~~~^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:20:1: note: ‘chisqr_1based’ declared here
20 | chisqr_1based (double p[])
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:469:22: error: too many arguments to function ‘gifError’; expected 0, have 2
469 | if (!pic8) return( gifError(pinfo, "couldn't malloc 'pic8'") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘amoeba’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:111:1: warning: old-style function definition [-Wold-style-definition]
111 | amoeba(p,y,ndim,ftol,funk,nfunk)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:491:15: error: too many arguments to function ‘DoInterlace’; expected 0, have 1
491 | else DoInterlace(FinChar);
| ^~~~~~~~~~~ ~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:83:14: note: declared here
83 | static void DoInterlace();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: error: conflicting types for ‘amotry’; have ‘double(void)’
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:94:15: note: previous declaration of ‘amotry’ with type ‘double(double **, double *, double *, int, double (*)(void), int, int *, double)’
94 | static double amotry(double **p, double *y, double *psum, int ndim,
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:52: error: conflicting types for ‘vector’; have ‘double *(void)’
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:97:16: note: previous declaration of ‘vector’ with type ‘double *(int, int)’
97 | static double *vector(int nl, int nh);
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:14: error: conflicting types for ‘nrerror’; have ‘void(void)’
117 | void nrerror(),free_vector();
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:96:13: note: previous declaration of ‘nrerror’ with type ‘void(char *)’
96 | static void nrerror( char error_text[]);
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: error: conflicting types for ‘free_vector’; have ‘void(void)’
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:98:13: note: previous declaration of ‘free_vector’ with type ‘void(double *, int, int)’
98 | static void free_vector(double *v, int nl, int nh);
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:120:14: error: too many arguments to function ‘vector’; expected 0, have 2
120 | psum=vector(1,ndim);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:52: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:540:53: error: too many arguments to function ‘DoInterlace’; expected 0, have 1
540 | else for (i=OutCount-1; i>=0; i--) DoInterlace(OutCode[i]);
| ^~~~~~~~~~~ ~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:83:14: note: declared here
83 | static void DoInterlace();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:107:42: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
107 | #define GET_PSUM for (j=1;j<=ndim;j++) { for (i=1,sum=0.0;i<=mpts;i++)\
| ^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:122:9: note: in expansion of macro ‘GET_PSUM’
122 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:108:65: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘for’
108 | sum += p[i][j]; psum[j]=sum;}
| ^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:122:9: note: in expansion of macro ‘GET_PSUM’
122 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:140:21: error: too many arguments to function ‘free_vector’; expected 0, have 3
140 | free_vector(psum,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: note: declared here
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘DoInterlace’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:143:22: error: too many arguments to function ‘amotry’; expected 0, have 8
143 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,-ALPHA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:607:13: warning: old-style function definition [-Wold-style-definition]
607 | static void DoInterlace(Index)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:145:30: error: too many arguments to function ‘amotry’; expected 0, have 8
145 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,GAMMA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:148:30: error: too many arguments to function ‘amotry’; expected 0, have 8
148 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,BETA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘gifError’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:156:55: error: too many arguments to function ‘funk’; expected 0, have 1
156 | y[i]=(*funk)(psum);
| ~^~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:657:12: warning: old-style function definition [-Wold-style-definition]
657 | static int gifError(pinfo, st)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:107:42: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
107 | #define GET_PSUM for (j=1;j<=ndim;j++) { for (i=1,sum=0.0;i<=mpts;i++)\
| ^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:160:33: note: in expansion of macro ‘GET_PSUM’
160 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:108:65: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘for’
108 | sum += p[i][j]; psum[j]=sum;}
| ^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:160:33: note: in expansion of macro ‘GET_PSUM’
160 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:165:9: error: too many arguments to function ‘free_vector’; expected 0, have 3
165 | free_vector(psum,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: note: declared here
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘amotry’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:171:1: warning: old-style function definition [-Wold-style-definition]
171 | amotry(p,y,psum,ndim,funk,ihi,nfunk,fac)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:179:14: error: too many arguments to function ‘vector’; expected 0, have 2
179 | ptry=vector(1,ndim);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:176:38: note: declared here
176 | double fac1,fac2,ytry,*ptry,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:183:15: error: too many arguments to function ‘funk’; expected 0, have 1
183 | ytry=(*funk)(ptry);
| ~^~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:192:9: error: too many arguments to function ‘free_vector’; expected 0, have 3
192 | free_vector(ptry,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:177:24: note: declared here
177 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘nrerror’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:205:1: warning: old-style function definition [-Wold-style-definition]
205 | nrerror(error_text)
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘vector’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:217:1: warning: old-style function definition [-Wold-style-definition]
217 | vector(nl,nh)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘free_vector’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:229:1: warning: old-style function definition [-Wold-style-definition]
229 | free_vector(v,nl,nh)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: At top level:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:229:1: warning: ‘free_vector’ defined but not used [-Wunused-function]
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:217:1: warning: ‘vector’ defined but not used [-Wunused-function]
217 | vector(nl,nh)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:171:1: warning: ‘amotry’ defined but not used [-Wunused-function]
171 | amotry(p,y,psum,ndim,funk,ihi,nfunk,fac)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘xy2RADec’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:32:1: warning: old-style function definition [-Wold-style-definition]
32 | xy2RADec (fip, x, y, rap, decp)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘RADec2xy’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:60:1: warning: old-style function definition [-Wold-style-definition]
60 | RADec2xy (fip, ra, dec, xp, yp)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘dsswcs’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:89:1: warning: old-style function definition [-Wold-style-definition]
89 | dsswcs (fip)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘dssxy2RADec’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:147:1: warning: old-style function definition [-Wold-style-definition]
147 | dssxy2RADec (fip, X, Y, rap, decp)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘setWCScache’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:233:1: warning: old-style function definition [-Wold-style-definition]
233 | setWCScache (fip)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘worldpos’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:342:12: warning: old-style function definition [-Wold-style-definition]
342 | static int worldpos(xpix, ypix, xref, yref, xrefpix, yrefpix, xinc, yinc, rot,
| ^~~~~~~~
gmake[2]: *** [libip/CMakeFiles/ip.dir/build.make:138: libip/CMakeFiles/ip.dir/lstsqr.c.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[2]: *** [libip/CMakeFiles/ip.dir/build.make:82: libip/CMakeFiles/ip.dir/explodegif.c.o] Error 1
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘xypix’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:551:12: warning: old-style function definition [-Wold-style-definition]
551 | static int xypix(xpos, ypos, xref, yref, xrefpix, yrefpix, xinc, yinc, rot,
| ^~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:49:1: warning: old-style function definition [-Wold-style-definition]
49 | writeFITS (fd, fip, errmsg, restore)
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:147:1: warning: old-style function definition [-Wold-style-definition]
147 | readFITS (fd, fip, errmsg)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readIncFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:289:1: warning: old-style function definition [-Wold-style-definition]
289 | readIncFITS (fd, fip, errmsg)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:345:1: warning: old-style function definition [-Wold-style-definition]
345 | readFITSHeader (fd, fip, errmsg)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeSimpleFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:425:1: warning: old-style function definition [-Wold-style-definition]
425 | writeSimpleFITS (fd, pix, w, h, restore)
| ^~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getNAXIS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:451:1: warning: old-style function definition [-Wold-style-definition]
451 | getNAXIS (fip, n1p, n2p, errmsg)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:560:1: warning: old-style function definition [-Wold-style-definition]
560 | writeFITSHeader (fip, fd, errmsg)
| ^~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘initFImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:595:1: warning: old-style function definition [-Wold-style-definition]
595 | initFImage (fip)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘resetFImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:607:1: warning: old-style function definition [-Wold-style-definition]
607 | resetFImage (fip)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setSimpleFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:622:1: warning: old-style function definition [-Wold-style-definition]
622 | setSimpleFITSHeader (fip)
| ^~~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:636:1: warning: old-style function definition [-Wold-style-definition]
636 | setLogicalFITS (fip, name, v, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:655:1: warning: old-style function definition [-Wold-style-definition]
655 | setIntFITS (fip, name, v, comment)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:674:1: warning: old-style function definition [-Wold-style-definition]
674 | setRealFITS (fip, name, v, sigdig, comment)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:697:1: warning: old-style function definition [-Wold-style-definition]
697 | setStringFITS (fip, name, string, comment)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setCommentFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:719:1: warning: old-style function definition [-Wold-style-definition]
719 | setCommentFITS (fip, name, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:744:1: warning: old-style function definition [-Wold-style-definition]
744 | getLogicalFITS (fip, name, vp)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:765:1: warning: old-style function definition [-Wold-style-definition]
765 | getIntFITS (fip, name, vp)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:782:1: warning: old-style function definition [-Wold-style-definition]
782 | getRealFITS (fip, name, vp)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getCommentFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:806:1: warning: old-style function definition [-Wold-style-definition]
806 | getCommentFITS (fip, name, buf)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:826:1: warning: old-style function definition [-Wold-style-definition]
826 | getStringFITS (fip, name, string)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘findFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:858:1: warning: old-style function definition [-Wold-style-definition]
858 | findFImageVar (fip, name, rpp)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘addFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:879:1: warning: old-style function definition [-Wold-style-definition]
879 | addFImageVar (fip, row)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘delFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:909:1: warning: old-style function definition [-Wold-style-definition]
909 | delFImageVar (fip, name)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘cpyFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:950:1: warning: old-style function definition [-Wold-style-definition]
950 | cpyFImageVar (fip1, fip2, name)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:969:1: warning: old-style function definition [-Wold-style-definition]
969 | fmtLogicalFITS (line, name, value, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:983:1: warning: old-style function definition [-Wold-style-definition]
983 | fmtIntFITS (line, name, value, comment)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1003:1: warning: old-style function definition [-Wold-style-definition]
1003 | fmtRealFITS (line, name, value, sigdig, comment)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1019:1: warning: old-style function definition [-Wold-style-definition]
1019 | fmtStringFITS (line, name, value, comment)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtENDFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1047:1: warning: old-style function definition [-Wold-style-definition]
1047 | fmtENDFITS (line)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtInlineComment’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1056:1: warning: old-style function definition [-Wold-style-definition]
1056 | fmtInlineComment (line, comment)
| ^~~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘enFITSPixels’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1072:1: warning: old-style function definition [-Wold-style-definition]
1072 | enFITSPixels (fip)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘unFITSPixels’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1101:1: warning: old-style function definition [-Wold-style-definition]
1101 | unFITSPixels (fip)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fsmatch.c:528:16: warning: argument 1 of type ‘double[4]’ with mismatched bound [-Warray-parameter=]
528 | chisqr (double p[4])
| ~~~~~~~^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fsmatch.c:66:29: note: previously declared as ‘double[]’
66 | static double chisqr(double p[]);
| ~~~~~~~^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘setWCScache’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:259:9: warning: ‘strncpy’ output may be truncated copying 4 bytes from a string of length 75 [-Wstringop-truncation]
259 | strncpy (fip->type, typestr+4, sizeof(fip->type)-1);
| ^]: [Various C errors due old style coding.]
|
Issue: You are using old C standard while the default likely moved to new standard.
Resolution: You should be explicit in your CMakeLists.txt and set there:
set(CMAKE_C_STANDARD 17)
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
RPM build errors:
error: Bad exit status from /var/tmp/rpm-tmp.WWpyzw (%build)
Bad exit status from /var/tmp/rpm-tmp.WWpyzw (%build)
Child return code was: 1
|
The build failed in %build 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:
98 | explodeGIF (raw, nraw, wp, hp, pixap, ra, ga, ba, errmsg)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:111:13: error: too many arguments to function ‘LoadGIF’; expected 0, have 1
111 | if (LoadGIF (&pi) != 1)
| ^~~~~~~ ~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:95:12: note: declared here
95 | static int LoadGIF();
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘LoadGIF’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:124:12: warning: old-style function definition [-Wold-style-definition]
124 | static int LoadGIF(pinfo)
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:144:13: error: too many arguments to function ‘gifError’; expected 0, have 2
144 | return( gifError(pinfo, "not enough memory to read gif file") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:150:19: error: too many arguments to function ‘gifError’; expected 0, have 2
150 | else return( gifError(pinfo, "not a GIF file"));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:172:24: error: too many arguments to function ‘gifError’; expected 0, have 2
172 | if (!gif89) return(gifError(pinfo,"corrupt GIF file (screen descriptor)"));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:244:15: warning: variable ‘ch’ set but not used [-Wunused-but-set-variable]
244 | int ch, j, sbsize, cmtlen;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:68: warning: variable ‘bg’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:64: warning: variable ‘fg’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:55: warning: variable ‘cHeight’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:269:47: warning: variable ‘cWidth’ set but not used [-Wunused-but-set-variable]
269 | int tgLeft, tgTop, tgWidth, tgHeight, cWidth, cHeight, fg, bg;
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:268:22: warning: variable ‘ch’ set but not used [-Wunused-but-set-variable]
268 | int j,sbsize,ch;
| ^~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:355:16: error: too many arguments to function ‘readImage’; expected 0, have 1
355 | else if (readImage(pinfo)) gotimage = 1;
| ^~~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:81:14: note: declared here
81 | static int readImage();
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:371:31: error: too many arguments to function ‘gifError’; expected 0, have 2
371 | if (!gotimage) return gifError(pinfo, str);
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:372:22: error: too many arguments to function ‘gifError’; expected 0, have 2
372 | else return( gifError(pinfo, str));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:382:14: error: too many arguments to function ‘gifError’; expected 0, have 2
382 | return( gifError(pinfo, "no image data found in GIF file") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘readImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:389:12: warning: old-style function definition [-Wold-style-definition]
389 | static int readImage(pinfo)
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘lstsqr’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:422:13: error: too many arguments to function ‘gifError’; expected 0, have 2
422 | return (gifError (pinfo, "No colormap in this GIF file."));
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:63:39: error: passing argument 5 of ‘amoeba’ from incompatible pointer type [-Wincompatible-pointer-types]
63 | ret = amoeba (p, y, np, ftol, chisqr_1based, &iter);
| ^~~~~~~~~~~~~
| |
| double (*)(double *)
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:15:14: note: expected ‘double (*)(void)’ but argument is of type ‘double (*)(double *)’
15 | double (*funk)(), int *nfunk);
| ~~~~~~~~~^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:20:1: note: ‘chisqr_1based’ declared here
20 | chisqr_1based (double p[])
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:469:22: error: too many arguments to function ‘gifError’; expected 0, have 2
469 | if (!pic8) return( gifError(pinfo, "couldn't malloc 'pic8'") );
| ^~~~~~~~ ~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:84:14: note: declared here
84 | static int gifError();
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘amoeba’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:111:1: warning: old-style function definition [-Wold-style-definition]
111 | amoeba(p,y,ndim,ftol,funk,nfunk)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:491:15: error: too many arguments to function ‘DoInterlace’; expected 0, have 1
491 | else DoInterlace(FinChar);
| ^~~~~~~~~~~ ~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:83:14: note: declared here
83 | static void DoInterlace();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: error: conflicting types for ‘amotry’; have ‘double(void)’
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:94:15: note: previous declaration of ‘amotry’ with type ‘double(double **, double *, double *, int, double (*)(void), int, int *, double)’
94 | static double amotry(double **p, double *y, double *psum, int ndim,
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:52: error: conflicting types for ‘vector’; have ‘double *(void)’
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:97:16: note: previous declaration of ‘vector’ with type ‘double *(int, int)’
97 | static double *vector(int nl, int nh);
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:14: error: conflicting types for ‘nrerror’; have ‘void(void)’
117 | void nrerror(),free_vector();
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:96:13: note: previous declaration of ‘nrerror’ with type ‘void(char *)’
96 | static void nrerror( char error_text[]);
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: error: conflicting types for ‘free_vector’; have ‘void(void)’
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:98:13: note: previous declaration of ‘free_vector’ with type ‘void(double *, int, int)’
98 | static void free_vector(double *v, int nl, int nh);
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:120:14: error: too many arguments to function ‘vector’; expected 0, have 2
120 | psum=vector(1,ndim);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:52: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:540:53: error: too many arguments to function ‘DoInterlace’; expected 0, have 1
540 | else for (i=OutCount-1; i>=0; i--) DoInterlace(OutCode[i]);
| ^~~~~~~~~~~ ~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:83:14: note: declared here
83 | static void DoInterlace();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:107:42: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
107 | #define GET_PSUM for (j=1;j<=ndim;j++) { for (i=1,sum=0.0;i<=mpts;i++)\
| ^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:122:9: note: in expansion of macro ‘GET_PSUM’
122 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:108:65: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘for’
108 | sum += p[i][j]; psum[j]=sum;}
| ^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:122:9: note: in expansion of macro ‘GET_PSUM’
122 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:140:21: error: too many arguments to function ‘free_vector’; expected 0, have 3
140 | free_vector(psum,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: note: declared here
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘DoInterlace’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:143:22: error: too many arguments to function ‘amotry’; expected 0, have 8
143 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,-ALPHA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:607:13: warning: old-style function definition [-Wold-style-definition]
607 | static void DoInterlace(Index)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:145:30: error: too many arguments to function ‘amotry’; expected 0, have 8
145 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,GAMMA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:148:30: error: too many arguments to function ‘amotry’; expected 0, have 8
148 | ytry=amotry(p,y,psum,ndim,funk,ihi,nfunk,BETA);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:116:36: note: declared here
116 | double ytry,ysave,sum,rtol,amotry(),*psum,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c: In function ‘gifError’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:156:55: error: too many arguments to function ‘funk’; expected 0, have 1
156 | y[i]=(*funk)(psum);
| ~^~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/explodegif.c:657:12: warning: old-style function definition [-Wold-style-definition]
657 | static int gifError(pinfo, st)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:107:42: warning: this ‘for’ clause does not guard... [-Wmisleading-indentation]
107 | #define GET_PSUM for (j=1;j<=ndim;j++) { for (i=1,sum=0.0;i<=mpts;i++)\
| ^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:160:33: note: in expansion of macro ‘GET_PSUM’
160 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:108:65: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘for’
108 | sum += p[i][j]; psum[j]=sum;}
| ^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:160:33: note: in expansion of macro ‘GET_PSUM’
160 | GET_PSUM
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:165:9: error: too many arguments to function ‘free_vector’; expected 0, have 3
165 | free_vector(psum,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:117:24: note: declared here
117 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘amotry’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:171:1: warning: old-style function definition [-Wold-style-definition]
171 | amotry(p,y,psum,ndim,funk,ihi,nfunk,fac)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:179:14: error: too many arguments to function ‘vector’; expected 0, have 2
179 | ptry=vector(1,ndim);
| ^~~~~~ ~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:176:38: note: declared here
176 | double fac1,fac2,ytry,*ptry,*vector();
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:183:15: error: too many arguments to function ‘funk’; expected 0, have 1
183 | ytry=(*funk)(ptry);
| ~^~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:192:9: error: too many arguments to function ‘free_vector’; expected 0, have 3
192 | free_vector(ptry,1,ndim);
| ^~~~~~~~~~~ ~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:177:24: note: declared here
177 | void nrerror(),free_vector();
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘nrerror’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:205:1: warning: old-style function definition [-Wold-style-definition]
205 | nrerror(error_text)
| ^~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘vector’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:217:1: warning: old-style function definition [-Wold-style-definition]
217 | vector(nl,nh)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: In function ‘free_vector’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:229:1: warning: old-style function definition [-Wold-style-definition]
229 | free_vector(v,nl,nh)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c: At top level:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:229:1: warning: ‘free_vector’ defined but not used [-Wunused-function]
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:217:1: warning: ‘vector’ defined but not used [-Wunused-function]
217 | vector(nl,nh)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/lstsqr.c:171:1: warning: ‘amotry’ defined but not used [-Wunused-function]
171 | amotry(p,y,psum,ndim,funk,ihi,nfunk,fac)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘xy2RADec’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:32:1: warning: old-style function definition [-Wold-style-definition]
32 | xy2RADec (fip, x, y, rap, decp)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘RADec2xy’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:60:1: warning: old-style function definition [-Wold-style-definition]
60 | RADec2xy (fip, ra, dec, xp, yp)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘dsswcs’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:89:1: warning: old-style function definition [-Wold-style-definition]
89 | dsswcs (fip)
| ^~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘dssxy2RADec’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:147:1: warning: old-style function definition [-Wold-style-definition]
147 | dssxy2RADec (fip, X, Y, rap, decp)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘setWCScache’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:233:1: warning: old-style function definition [-Wold-style-definition]
233 | setWCScache (fip)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘worldpos’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:342:12: warning: old-style function definition [-Wold-style-definition]
342 | static int worldpos(xpix, ypix, xref, yref, xrefpix, yrefpix, xinc, yinc, rot,
| ^~~~~~~~
gmake[2]: *** [libip/CMakeFiles/ip.dir/build.make:138: libip/CMakeFiles/ip.dir/lstsqr.c.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
gmake[2]: *** [libip/CMakeFiles/ip.dir/build.make:82: libip/CMakeFiles/ip.dir/explodegif.c.o] Error 1
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘xypix’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:551:12: warning: old-style function definition [-Wold-style-definition]
551 | static int xypix(xpos, ypos, xref, yref, xrefpix, yrefpix, xinc, yinc, rot,
| ^~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:49:1: warning: old-style function definition [-Wold-style-definition]
49 | writeFITS (fd, fip, errmsg, restore)
| ^~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:147:1: warning: old-style function definition [-Wold-style-definition]
147 | readFITS (fd, fip, errmsg)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readIncFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:289:1: warning: old-style function definition [-Wold-style-definition]
289 | readIncFITS (fd, fip, errmsg)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘readFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:345:1: warning: old-style function definition [-Wold-style-definition]
345 | readFITSHeader (fd, fip, errmsg)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeSimpleFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:425:1: warning: old-style function definition [-Wold-style-definition]
425 | writeSimpleFITS (fd, pix, w, h, restore)
| ^~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getNAXIS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:451:1: warning: old-style function definition [-Wold-style-definition]
451 | getNAXIS (fip, n1p, n2p, errmsg)
| ^~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘writeFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:560:1: warning: old-style function definition [-Wold-style-definition]
560 | writeFITSHeader (fip, fd, errmsg)
| ^~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘initFImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:595:1: warning: old-style function definition [-Wold-style-definition]
595 | initFImage (fip)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘resetFImage’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:607:1: warning: old-style function definition [-Wold-style-definition]
607 | resetFImage (fip)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setSimpleFITSHeader’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:622:1: warning: old-style function definition [-Wold-style-definition]
622 | setSimpleFITSHeader (fip)
| ^~~~~~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:636:1: warning: old-style function definition [-Wold-style-definition]
636 | setLogicalFITS (fip, name, v, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:655:1: warning: old-style function definition [-Wold-style-definition]
655 | setIntFITS (fip, name, v, comment)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:674:1: warning: old-style function definition [-Wold-style-definition]
674 | setRealFITS (fip, name, v, sigdig, comment)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:697:1: warning: old-style function definition [-Wold-style-definition]
697 | setStringFITS (fip, name, string, comment)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘setCommentFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:719:1: warning: old-style function definition [-Wold-style-definition]
719 | setCommentFITS (fip, name, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:744:1: warning: old-style function definition [-Wold-style-definition]
744 | getLogicalFITS (fip, name, vp)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:765:1: warning: old-style function definition [-Wold-style-definition]
765 | getIntFITS (fip, name, vp)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:782:1: warning: old-style function definition [-Wold-style-definition]
782 | getRealFITS (fip, name, vp)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getCommentFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:806:1: warning: old-style function definition [-Wold-style-definition]
806 | getCommentFITS (fip, name, buf)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘getStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:826:1: warning: old-style function definition [-Wold-style-definition]
826 | getStringFITS (fip, name, string)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘findFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:858:1: warning: old-style function definition [-Wold-style-definition]
858 | findFImageVar (fip, name, rpp)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘addFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:879:1: warning: old-style function definition [-Wold-style-definition]
879 | addFImageVar (fip, row)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘delFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:909:1: warning: old-style function definition [-Wold-style-definition]
909 | delFImageVar (fip, name)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘cpyFImageVar’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:950:1: warning: old-style function definition [-Wold-style-definition]
950 | cpyFImageVar (fip1, fip2, name)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtLogicalFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:969:1: warning: old-style function definition [-Wold-style-definition]
969 | fmtLogicalFITS (line, name, value, comment)
| ^~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtIntFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:983:1: warning: old-style function definition [-Wold-style-definition]
983 | fmtIntFITS (line, name, value, comment)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtRealFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1003:1: warning: old-style function definition [-Wold-style-definition]
1003 | fmtRealFITS (line, name, value, sigdig, comment)
| ^~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtStringFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1019:1: warning: old-style function definition [-Wold-style-definition]
1019 | fmtStringFITS (line, name, value, comment)
| ^~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtENDFITS’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1047:1: warning: old-style function definition [-Wold-style-definition]
1047 | fmtENDFITS (line)
| ^~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘fmtInlineComment’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1056:1: warning: old-style function definition [-Wold-style-definition]
1056 | fmtInlineComment (line, comment)
| ^~~~~~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘enFITSPixels’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1072:1: warning: old-style function definition [-Wold-style-definition]
1072 | enFITSPixels (fip)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c: In function ‘unFITSPixels’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fits.c:1101:1: warning: old-style function definition [-Wold-style-definition]
1101 | unFITSPixels (fip)
| ^~~~~~~~~~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fsmatch.c:528:16: warning: argument 1 of type ‘double[4]’ with mismatched bound [-Warray-parameter=]
528 | chisqr (double p[4])
| ~~~~~~~^~~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/fsmatch.c:66:29: note: previously declared as ‘double[]’
66 | static double chisqr(double p[]);
| ~~~~~~~^~~
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c: In function ‘setWCScache’:
/builddir/build/BUILD/xephem-4.2.0-build/XEphem-4.2.0/libip/wcs.c:259:9: warning: ‘strncpy’ output may be truncated copying 4 bytes from a string of length 75 [-Wstringop-truncation]
259 | strncpy (fip->type, typestr+4, sizeof(fip->type)-1);
| ^
|
Various C errors due old style coding.
|
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.kWIUH3 (%check)]: [This indicates that the package build failed in the %check section. It means that package has got likely upstream tests running, and some of that tests failed.]
=============
[Fatal Python error: Segmentation fault]: [Segmentation fault is a fatal error that made the package build unsuccessful.]
=============
[tests/test_command.py F.FFF.FF.F.F.....FF.... [ 3%]]: [A bunch of capital letter Fs show that some tests have run and failed. This would invalidate the build.]
=============
[Extension modules: numpy._core._multiarray_umath, numpy.linalg._umath_linalg, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, pandas._libs.tslibs.ccalendar, pandas._libs.tslibs.np_datetime, pandas._libs.tslibs.dtypes, pandas._libs.tslibs.base, pandas._libs.tslibs.nattype, pandas._libs.tslibs.timezones, pandas._libs.tslibs.fields, pandas._libs.tslibs.timedeltas, pandas._libs.tslibs.tzconversion, pandas._libs.tslibs.timestamps, pandas._libs.properties, pandas._libs.tslibs.offsets, pandas._libs.tslibs.strptime, pandas._libs.tslibs.parsing, pandas._libs.tslibs.conversion, pandas._libs.tslibs.period, pandas._libs.tslibs.vectorized, pandas._libs.ops_dispatch, pandas._libs.missing, pandas._libs.hashtable, pandas._libs.algos, pandas._libs.interval, pandas._libs.lib, pandas._libs.ops, pandas._libs.hashing, pandas._libs.arrays, pandas._libs.tslib, pandas._libs.sparse, pandas._libs.internals, pandas._libs.indexing, pandas._libs.index, pandas._libs.writers, pandas._libs.join, pandas._libs.window.aggregations, pandas._libs.window.indexers, pandas._libs.reshape, pandas._libs.groupby, pandas._libs.json, pandas._libs.parsers, pandas._libs.testing, yaml._yaml (total: 52)]: [There is a list of extension modules that were loaded during the interpreter crash. It can help when looking for a root cause of the failure.]
|
Issue: The build failed because of a segmentation error. This most likely comes from incompatible libraries or a bug in this package.
Resolution: To fix the build, it is first necessary to review the extension modules used by the package. Most probably one or more of them are not compatible with the recent Python version and need to be fixed or rebuilt with it. When all of the libraries are rebuilt with the most recent Python version, this build should be retriggered. Then, the traceback of the failed tests will appear which will have to be fixed too.
|
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.kWIUH3 (%check)
|
This indicates that the package build failed in the %check section. It means that package has got likely upstream tests running, and some of that tests 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:
Fatal Python error: Segmentation fault
|
Segmentation fault is a fatal error that made the package build unsuccessful.
|
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:
tests/test_command.py F.FFF.FF.F.F.....FF.... [ 3%]
|
A bunch of capital letter Fs show that some tests have run and failed. This would invalidate 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:
Extension modules: numpy._core._multiarray_umath, numpy.linalg._umath_linalg, numpy.random._common, numpy.random.bit_generator, numpy.random._bounded_integers, numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, pandas._libs.tslibs.ccalendar, pandas._libs.tslibs.np_datetime, pandas._libs.tslibs.dtypes, pandas._libs.tslibs.base, pandas._libs.tslibs.nattype, pandas._libs.tslibs.timezones, pandas._libs.tslibs.fields, pandas._libs.tslibs.timedeltas, pandas._libs.tslibs.tzconversion, pandas._libs.tslibs.timestamps, pandas._libs.properties, pandas._libs.tslibs.offsets, pandas._libs.tslibs.strptime, pandas._libs.tslibs.parsing, pandas._libs.tslibs.conversion, pandas._libs.tslibs.period, pandas._libs.tslibs.vectorized, pandas._libs.ops_dispatch, pandas._libs.missing, pandas._libs.hashtable, pandas._libs.algos, pandas._libs.interval, pandas._libs.lib, pandas._libs.ops, pandas._libs.hashing, pandas._libs.arrays, pandas._libs.tslib, pandas._libs.sparse, pandas._libs.internals, pandas._libs.indexing, pandas._libs.index, pandas._libs.writers, pandas._libs.join, pandas._libs.window.aggregations, pandas._libs.window.indexers, pandas._libs.reshape, pandas._libs.groupby, pandas._libs.json, pandas._libs.parsers, pandas._libs.testing, yaml._yaml (total: 52)
|
There is a list of extension modules that were loaded during the interpreter crash. It can help when looking for a root cause of the 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: attempt to use unversioned python, define %__python to /usr/bin/python2 or /usr/bin/python3 explicitly
]: [rpmbuild complains about python and exits]
|
Issue: rpmbuild requires usage of versioned python shebangs
Resolution: check python files and use versioned python shebangs
|
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: attempt to use unversioned python, define %__python to /usr/bin/python2 or /usr/bin/python3 explicitly
|
rpmbuild complains about python and exits
|
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.12 setup.py build '--executable=/usr/bin/python3.12 -sP'
/usr/bin/python3.12: can't open file '/builddir/build/BUILD/sniffio-1.3.1/setup.py': [Errno 2] No such file or directory
]: [execution of setup.py build failing to find the setup.py file in the sources directory]
|
Issue: setup.py is no longer present in the project as the developers migrated setup.py to pyproject.toml
Resolution: Migrate the RPM spec to use pyproject-rpm-macros to build the project using pyproject.toml.
https://github.com/hroncok/pyprojectize could also be used to automatically do the needed changes 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:
+ /usr/bin/python3.12 setup.py build '--executable=/usr/bin/python3.12 -sP'
/usr/bin/python3.12: can't open file '/builddir/build/BUILD/sniffio-1.3.1/setup.py': [Errno 2] No such file or directory
|
execution of setup.py build failing to find the setup.py file in the sources directory
|
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:
[gcc -I. -I../../include -fPIC -fcommon -DNO_DB -DHAS_LDAP -DLDAP_DEPRECATED=1 -DUSE_LDAP_SASL -DHAS_LMDB -DHAS_PCRE=2 -DHAS_MYSQL -I/usr/include/mysql -DHAS_PGSQL -I/usr/include/pgsql -DHAS_SQLITE -DHAS_CDB -DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/usr/include/sasl -DUSE_TLS -DDEF_CONFIG_DIR=\"/etc/postfix\" -DNO_NIS -DHAS_DEV_URANDOM -DUSE_DYNAMIC_LIBS -DUSE_DYNAMIC_MAPS -Wmissing-prototypes -Wformat -Wno-comment -fno-common -fPIC -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-v3 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fno-strict-aliasing -Wno-comment -I. -I../../include -DLINUX6 -c bounce.c
In file included from bounce.c:210:
./mail_params.h:17:13: error: ‘bool’ cannot be defined via ‘typedef’
17 | typedef int bool;
| ^~~~
./mail_params.h:17:13: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
]: [It's a compilation error.]
|
Issue: GCC 15 moved a default C language version to to C23. That version has a built-in "bool" keyword, therefore a C code is allowed to defined a custom type of the same name.
Resolution: Change to code not to define bool type in case of C23 or higher language standard 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:
gcc -I. -I../../include -fPIC -fcommon -DNO_DB -DHAS_LDAP -DLDAP_DEPRECATED=1 -DUSE_LDAP_SASL -DHAS_LMDB -DHAS_PCRE=2 -DHAS_MYSQL -I/usr/include/mysql -DHAS_PGSQL -I/usr/include/pgsql -DHAS_SQLITE -DHAS_CDB -DUSE_SASL_AUTH -DUSE_CYRUS_SASL -I/usr/include/sasl -DUSE_TLS -DDEF_CONFIG_DIR=\"/etc/postfix\" -DNO_NIS -DHAS_DEV_URANDOM -DUSE_DYNAMIC_LIBS -DUSE_DYNAMIC_MAPS -Wmissing-prototypes -Wformat -Wno-comment -fno-common -fPIC -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-v3 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -mtls-dialect=gnu2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fno-strict-aliasing -Wno-comment -I. -I../../include -DLINUX6 -c bounce.c
In file included from bounce.c:210:
./mail_params.h:17:13: error: ‘bool’ cannot be defined via ‘typedef’
17 | typedef int bool;
| ^~~~
./mail_params.h:17:13: note: ‘bool’ is a keyword with ‘-std=c23’ onwards
|
It's a compilation error.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[
# Failed test 'did not search PATH for C++ compiler when given absolute path to C compiler'
# at t/03-cplusplus.t line 73.
# got: 'g++'
# expected: '/builddir/build/BUILD/perl-5.41.13-build/perl-5.41.12/dist/ExtUtils-CBuilder/some/directory/what/doesnt/exist/cc'
# Looks like you failed 1 test of 7.
../dist/ExtUtils-CBuilder/t/03-cplusplus.t ...........................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/7 subtests ]: [Here build failed, because test got different result as expected]
|
Issue: The test failed because it did not expect $ENV{CXX}, and consequently $cb->{config}{cxx}, to be defined at runtime.
https://github.com/Perl/perl5/issues/23277
Resolution: There are two way how to solve it.
The test should be skipped entirely if $CXX is set, or $CXX needs to be (temporarily) unset.
|
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 'did not search PATH for C++ compiler when given absolute path to C compiler'
# at t/03-cplusplus.t line 73.
# got: 'g++'
# expected: '/builddir/build/BUILD/perl-5.41.13-build/perl-5.41.12/dist/ExtUtils-CBuilder/some/directory/what/doesnt/exist/cc'
# Looks like you failed 1 test of 7.
../dist/ExtUtils-CBuilder/t/03-cplusplus.t ...........................
Dubious, test returned 1 (wstat 256, 0x100)
Failed 1/7 subtests
|
Here build failed, because test got different result as expected
|
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: No match for argument: python3-pytest-asyncio >= 0.24
DEBUG util.py:459: You can try to add to command line:
DEBUG util.py:459: --skip-unavailable to skip unavailable packages
]: [The required package python3-pytest-asyncio is either not available or is not available in required version.]
|
Issue: The build dependency cannot be satisfied.
Resolution: You have to work with the maintainer of python3-pytest-asyncio to build it in the required version.
As a temporary solution, you can disable the test suite.
|
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: No match for argument: python3-pytest-asyncio >= 0.24
DEBUG util.py:459: You can try to add to command line:
DEBUG util.py:459: --skip-unavailable to skip unavailable packages
|
The required package python3-pytest-asyncio is either not available or is not available in required version.
|
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:
[ModuleNotFoundError: No module named 'mailcap']: [The module mailcap which is trying to be imported was not found.]
=============
[error: Bad exit status from /var/tmp/rpm-tmp.6Zl7m0 (%check)]: [The build failed in the %check part of the build process.]
|
Issue: The build failed because the mailcap module that is trying to be imported is not found, this is because the mailcap module was deprecated in python 3.11 and removed in python 3.13 adn this build is being built using python 3.13.
Resolution: Switch to the alternative of the mailcap module which is the mimetypes module or use an older version of python to build the 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:
ModuleNotFoundError: No module named 'mailcap'
|
The module mailcap which is trying to be imported was not found.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
error: Bad exit status from /var/tmp/rpm-tmp.6Zl7m0 (%check)
|
The build failed in the %check part of the build process.
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[RPM build errors:
%changelog not in descending chronological order
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/adelsystem_cbi.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/apc_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/asem.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/generic_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/huawei-ups2000.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/phoenixcontact_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/pijuice.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/socomec_jbus.8.gz
Child return code was: 1
]: [rmbuild complains about files not found]
|
Issue: build failed as spec file says that build should have created these files, but they weren't.
Resolution: This may be caused by rebase to new upstream version that removed or renamed some files or some change in build environment, where some build dependency may be missing. Consult with changelog and configure script where it does not find some 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:
RPM build errors:
%changelog not in descending chronological order
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/adelsystem_cbi.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/apc_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/asem.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/generic_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/huawei-ups2000.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/phoenixcontact_modbus.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/pijuice.8.gz
File not found: /builddir/build/BUILDROOT/nut-2.8.1-2.el9.x86_64/usr/share/man/man8/socomec_jbus.8.gz
Child return code was: 1
|
rmbuild complains about files 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:
[y 45 kB/s | 1.5 kB 00:00
Additional repo https_kojipkgs_fedoraproject_or 104 kB/s | 3.8 kB 00:00
Additional repo https_download_copr_fedorainfra 100 kB/s | 3.3 kB 00:00
Fedora - ELN BaseOS - Developmental packages fo 68 kB/s | 2.3 kB 00:00
Fedora - ELN AppStream - Developmental packages 66 kB/s | 2.3 kB 00:00
Fedora - ELN CodeReady Linux Builders - Build p 66 kB/s | 2.3 kB 00:00
Error:
Problem: cannot install the best candidate for the job
- nothing provides clang = 13.0.0 needed by clang-rpm-macros-1-136.el115.noarch from https_download_copr_fedorainfracloud_org_results_fedora_llvm_team_clang_rpm_macros_fedora_releasever_basearch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.rpm.log
/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.librepo.log
/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.log
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-mmgu1jug/perl-FileHandle-Fmode/perl-FileHandle-Fmode.spec) Config(fedora-eln-x86_64) 1 minutes 34 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M 77fb7256ea894b5a9d9b7112ce42a363 -D /var/lib/mock/fedora-eln-x86_64-bootstrap-1706200861.636798/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.q00l_rzh:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>]: [This is one of the three attempts Mock does to install the BuildRequires specified in spec file. All of the three attempts failed to install `clang-rpm-macros` which runtime-depends on `clang = 13.0.0`. But no package providing this exists.]
|
Issue: Because the BuildRequires aren't installable.
Resolution: Fix the `clang` or `clang-rpm-macros` package. If you don't have permissions to do this, ask the corresponding maintainer. This failure is not your fault.
|
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:
y 45 kB/s | 1.5 kB 00:00
Additional repo https_kojipkgs_fedoraproject_or 104 kB/s | 3.8 kB 00:00
Additional repo https_download_copr_fedorainfra 100 kB/s | 3.3 kB 00:00
Fedora - ELN BaseOS - Developmental packages fo 68 kB/s | 2.3 kB 00:00
Fedora - ELN AppStream - Developmental packages 66 kB/s | 2.3 kB 00:00
Fedora - ELN CodeReady Linux Builders - Build p 66 kB/s | 2.3 kB 00:00
Error:
Problem: cannot install the best candidate for the job
- nothing provides clang = 13.0.0 needed by clang-rpm-macros-1-136.el115.noarch from https_download_copr_fedorainfracloud_org_results_fedora_llvm_team_clang_rpm_macros_fedora_releasever_basearch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
INFO: chroot_scan: 3 files copied to /var/lib/copr-rpmbuild/results/chroot_scan
INFO: /var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.rpm.log
/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.librepo.log
/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/var/log/dnf.log
ERROR: Exception(/var/lib/copr-rpmbuild/workspace/workdir-mmgu1jug/perl-FileHandle-Fmode/perl-FileHandle-Fmode.spec) Config(fedora-eln-x86_64) 1 minutes 34 seconds
INFO: Results and/or logs in: /var/lib/copr-rpmbuild/results
INFO: Cleaning up build root ('cleanup_on_failure=True')
Start: clean chroot
INFO: unmounting tmpfs.
Finish: clean chroot
ERROR: Command failed:
# /usr/bin/systemd-nspawn -q -M 77fb7256ea894b5a9d9b7112ce42a363 -D /var/lib/mock/fedora-eln-x86_64-bootstrap-1706200861.636798/root -a --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240 --capability=cap_ipc_lock --bind=/tmp/mock-resolv.q00l_rzh:/etc/resolv.conf --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/var/lib/mock/fedora-eln-x86_64-1706200861.636798/root/installation-homedir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;<mock-chroot>
|
This is one of the three attempts Mock does to install the BuildRequires specified in spec file. All of the three attempts failed to install `clang-rpm-macros` which runtime-depends on `clang = 13.0.0`. But no package providing this 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:
[ 'chroot': 'centos-stream-9-x86_64',]: [This build is using a CentOS Stream chroot.]
=============
[No matching package to install: 'system-bookmarks']: [There is a missing dependency.]
|
Issue: The build failed due to a missing dependency. Some dependencies in CentOS Stream are buildroot only, so they are not present in the default repositories that COPR uses for CentOS Stream.
Resolution: You need to manually add the CentOS Stream buildroot repositories from CentOS Stream koji to the additional repos for your CentOS stream chroots. Here is a template for the repo url: https://kojihub.stream.centos.org/kojifiles/repos/c{centos_version}s-build/latest/{arch}/"
|
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:
'chroot': 'centos-stream-9-x86_64',
|
This build is using a CentOS Stream chroot.
|
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: 'system-bookmarks'
|
There is a missing dependency.
|
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:
[[javac] error: Source option 1.3 is no longer supported. Use 8 or later./builddir/build/BUILD/bsf-2.4.0-build/bsf-2.4.0/build.xml:219: Compile failed; see the compiler error output for details.]: [Ant build failure related to javac tool.]
|
Issue: The version of javac used during the build does not support the source flag 1.3.
Resolution: Inspect the build.xml file and set the appropriate key referring to the java source flag to a version supported by the compiler.
|
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:
[javac] error: Source option 1.3 is no longer supported. Use 8 or later./builddir/build/BUILD/bsf-2.4.0-build/bsf-2.4.0/build.xml:219: Compile failed; see the compiler error output for details.
|
Ant build failure related to javac tool.
|
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:
[-f /builddir/build/BUILD/linux-libre-6.15_rc7-build/linux-6.15-rc7/Makefile
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***]: [Description of the make error]
|
Issue: Make coudn't find the configuration file
Resolution: Provide the config 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:
-f /builddir/build/BUILD/linux-libre-6.15_rc7-build/linux-6.15-rc7/Makefile
***
*** Configuration file ".config" not found!
***
*** Please run some configurator (e.g. "make oldconfig" or
*** "make menuconfig" or "make xconfig").
***
|
Description of the make error
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.c:1785:25: error: too many arguments to function ‘SYSTEM_BG’; expected 0, have 1
1785 | SYSTEM_BG("splash.bmp");
| ^~~~~~~~~ ~~~~~~~~~~~~
In file included from /builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.c:19:
/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.h:30:6: note: declared here
30 | void SYSTEM_BG();
| ^~~~~~~~~]: [Build failure - incorrect function call in C code]
=============
[/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shipsdl2.c:409:6: error: conflicting types for ‘SYSTEM_DRAW_BG’; have ‘void(char *)’
409 | void SYSTEM_DRAW_BG(char *bmp)
| ^~~~~~~~~~~~~~
In file included from /builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shipsdl2.c:7:
/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.h:31:6: note: previous declaration of ‘SYSTEM_DRAW_BG’ with type ‘void(void)’
31 | void SYSTEM_DRAW_BG();
| ^~~~~~~~~~~~~~]: [Build failiure - double declaration of a function with conflicting arguments]
|
Issue: The SYSTEM_BG() function was called with an argument, but it's defined without any, causing the compilation to fail.
The SYSTEM_DRAW_BG is being declared twice, once as void(char *), second time as void(void). That is not allowed in C.
Resolution: Remove the argument from the SYSTEM_BG function call
Unify the SYSTEM_DRAW_BG function delaration or remove one of the declarations to fix the conflict.
|
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/shippy-1.5.4-build/shippy-1.5.4/shippy.c:1785:25: error: too many arguments to function ‘SYSTEM_BG’; expected 0, have 1
1785 | SYSTEM_BG("splash.bmp");
| ^~~~~~~~~ ~~~~~~~~~~~~
In file included from /builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.c:19:
/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.h:30:6: note: declared here
30 | void SYSTEM_BG();
| ^~~~~~~~~
|
Build failure - incorrect function call in C code
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shipsdl2.c:409:6: error: conflicting types for ‘SYSTEM_DRAW_BG’; have ‘void(char *)’
409 | void SYSTEM_DRAW_BG(char *bmp)
| ^~~~~~~~~~~~~~
In file included from /builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shipsdl2.c:7:
/builddir/build/BUILD/shippy-1.5.4-build/shippy-1.5.4/shippy.h:31:6: note: previous declaration of ‘SYSTEM_DRAW_BG’ with type ‘void(void)’
31 | void SYSTEM_DRAW_BG();
| ^~~~~~~~~~~~~~
|
Build failiure - double declaration of a function with conflicting arguments
|
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:
[tcl/tclWrapper.cpp:444:37: error: ‘TCL_CHANNEL_VERSION_2’ was not declared in this scope; did you mean ‘TCL_CHANNEL_VERSION_5’?]: [Error in the syntax finding a constant/macro.]
|
Issue: The constant/macro TCL_CHANNEL_VERSION_2 not declared.
Resolution: Properly declare constant/macro.
|
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:
tcl/tclWrapper.cpp:444:37: error: ‘TCL_CHANNEL_VERSION_2’ was not declared in this scope; did you mean ‘TCL_CHANNEL_VERSION_5’?
|
Error in the syntax finding a constant/macro.
|
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:
[go: go.mod requires go >= 1.23.3 (running go 1.22.12; GOTOOLCHAIN=local)]: [Build failure reason.]
|
Issue: The build process requires go package in version 1.23.3 or higher. Current version is 1.22.12.
Resolution: Set requirements for go package to be at least in version 1.23.3 in your .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:
go: go.mod requires go >= 1.23.3 (running go 1.22.12; GOTOOLCHAIN=local)
|
Build failure reason.
|
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:
[[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXdKU0Vh/agent.42927
SSH_AGENT_PID=42929
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/workspace/RHEL-10.0/subscription-manager-cockpit@tmp/private_key_14696866137573535711.key ([email protected])
[ssh-agent] Using credentials jenkins (rhsm-qe)]: [jenkins provides ssh-agent]
=============
[> git rev-parse --resolve-git-dir /home/jenkins/workspace/RHEL-10.0/subscription-manager-cockpit/.git # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe # timeout=10
Fetching upstream changes from https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe
> git --version # timeout=10
> git --version # 'git version 2.48.1'
> git fetch --tags --force --progress -- https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse origin/main^{commit} # timeout=10
Checking out Revision fdf2ce595dd50a1610819052fcf4904a75f960ba (origin/main)
> git config core.sparsecheckout # timeout=10
> git checkout -f fdf2ce595dd50a1610819052fcf4904a75f960ba # timeout=10
Commit message: "Merge branch 'rhc-highavailability' into 'main'"
> git rev-list --no-walk fdf2ce595dd50a1610819052fcf4904a75f960ba # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10]: [git command to fetch tested repo]
=============
[Requirement already satisfied: pip in ./env/lib64/python3.12/site-packages (23.3.2)
Collecting pip
Using cached pip-25.0.1-py3-none-any.whl.metadata (3.7 kB)
Using cached pip-25.0.1-py3-none-any.whl (1.8 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 23.3.2
Uninstalling pip-23.3.2:
Successfully uninstalled pip-23.3.2
Successfully installed pip-25.0.1
Collecting wheel
Downloading wheel-0.45.1-py3-none-any.whl.metadata (2.3 kB)
Collecting setuptools_rust
Downloading setuptools_rust-1.10.2-py3-none-any.whl.metadata (9.2 kB)
Collecting setuptools>=62.4 (from setuptools_rust)
Downloading setuptools-76.0.0-py3-none-any.whl.metadata (6.7 kB)
Collecting semantic-version<3,>=2.8.2 (from setuptools_rust)
Downloading semantic_version-2.10.0-py2.py3-none-any.whl.metadata (9.7 kB)
Downloading wheel-0.45.1-py3-none-any.whl (72 kB)
Downloading setuptools_rust-1.10.2-py3-none-any.whl (26 kB)
Downloading semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
Downloading setuptools-76.0.0-py3-none-any.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 60.7 MB/s eta 0:00:00
Installing collected packages: wheel, setuptools, semantic-version, setuptools_rust
Successfully installed semantic-version-2.10.0 setuptools-76.0.0 setuptools_rust-1.10.2 wheel-0.45.1
Collecting ansible (from -r requirements.txt (line 1))
Downloading ansible-11.3.0-py3-none-any.whl.metadata (8.0 kB)
Collecting ansible-lint (from -r requirements.txt (line 2))
Downloading ansible_lint-25.1.3-py3-none-any.whl.metadata (6.8 kB)
Collecting ara (from -r requirements.txt (line 3))]: [activate python environment]
=============
[ansible-playbook -i localhost.ini -e chromedriver_version=133.0.6943.98 playbooks/install-chromedriver.yml
[DEPRECATION WARNING]: community.general.yaml has been deprecated. The plugin
has been superseded by the the option `result_format=yaml` in callback plugin
ansible.builtin.default from ansible-core 2.13 onwards. This feature will be
removed from community.general in version 13.0.0. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.
Operations to perform:
Apply all migrations: admin, api, auth, contenttypes, db, ses]: [chrome-driver version installed in machine]
|
Issue: xpath element did not apperd
Resolution: review 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:
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-XXXXXXdKU0Vh/agent.42927
SSH_AGENT_PID=42929
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/workspace/RHEL-10.0/subscription-manager-cockpit@tmp/private_key_14696866137573535711.key ([email protected])
[ssh-agent] Using credentials jenkins (rhsm-qe)
|
jenkins provides ssh-agent
|
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:
> git rev-parse --resolve-git-dir /home/jenkins/workspace/RHEL-10.0/subscription-manager-cockpit/.git # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe # timeout=10
Fetching upstream changes from https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe
> git --version # timeout=10
> git --version # 'git version 2.48.1'
> git fetch --tags --force --progress -- https://gitlab.cee.redhat.com/RHSM-QE/rhsm-ansible-qe +refs/heads/*:refs/remotes/origin/* # timeout=10
> git rev-parse origin/main^{commit} # timeout=10
Checking out Revision fdf2ce595dd50a1610819052fcf4904a75f960ba (origin/main)
> git config core.sparsecheckout # timeout=10
> git checkout -f fdf2ce595dd50a1610819052fcf4904a75f960ba # timeout=10
Commit message: "Merge branch 'rhc-highavailability' into 'main'"
> git rev-list --no-walk fdf2ce595dd50a1610819052fcf4904a75f960ba # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
|
git command to fetch tested repo
|
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 already satisfied: pip in ./env/lib64/python3.12/site-packages (23.3.2)
Collecting pip
Using cached pip-25.0.1-py3-none-any.whl.metadata (3.7 kB)
Using cached pip-25.0.1-py3-none-any.whl (1.8 MB)
Installing collected packages: pip
Attempting uninstall: pip
Found existing installation: pip 23.3.2
Uninstalling pip-23.3.2:
Successfully uninstalled pip-23.3.2
Successfully installed pip-25.0.1
Collecting wheel
Downloading wheel-0.45.1-py3-none-any.whl.metadata (2.3 kB)
Collecting setuptools_rust
Downloading setuptools_rust-1.10.2-py3-none-any.whl.metadata (9.2 kB)
Collecting setuptools>=62.4 (from setuptools_rust)
Downloading setuptools-76.0.0-py3-none-any.whl.metadata (6.7 kB)
Collecting semantic-version<3,>=2.8.2 (from setuptools_rust)
Downloading semantic_version-2.10.0-py2.py3-none-any.whl.metadata (9.7 kB)
Downloading wheel-0.45.1-py3-none-any.whl (72 kB)
Downloading setuptools_rust-1.10.2-py3-none-any.whl (26 kB)
Downloading semantic_version-2.10.0-py2.py3-none-any.whl (15 kB)
Downloading setuptools-76.0.0-py3-none-any.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 60.7 MB/s eta 0:00:00
Installing collected packages: wheel, setuptools, semantic-version, setuptools_rust
Successfully installed semantic-version-2.10.0 setuptools-76.0.0 setuptools_rust-1.10.2 wheel-0.45.1
Collecting ansible (from -r requirements.txt (line 1))
Downloading ansible-11.3.0-py3-none-any.whl.metadata (8.0 kB)
Collecting ansible-lint (from -r requirements.txt (line 2))
Downloading ansible_lint-25.1.3-py3-none-any.whl.metadata (6.8 kB)
Collecting ara (from -r requirements.txt (line 3))
|
activate python environment
|
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:
ansible-playbook -i localhost.ini -e chromedriver_version=133.0.6943.98 playbooks/install-chromedriver.yml
[DEPRECATION WARNING]: community.general.yaml has been deprecated. The plugin
has been superseded by the the option `result_format=yaml` in callback plugin
ansible.builtin.default from ansible-core 2.13 onwards. This feature will be
removed from community.general in version 13.0.0. Deprecation warnings can be
disabled by setting deprecation_warnings=False in ansible.cfg.
Operations to perform:
Apply all migrations: admin, api, auth, contenttypes, db, ses
|
chrome-driver version installed in machine
|
Given following log snippets, their explanation, and nothing else, explain what failure, if any, occurred during build of this package.
Snippets are in a format of [X] : [Y], where [X] is a log snippet, and [Y] is the explanation.
Snippets are delimited with '================'.
Drawing on information from all snippets, provide a concise explanation of the issue and recommend a solution.
Explanation of the issue, and recommended solution, should take a handful of sentences.
Snippets:
[Patch #0 (version-fixes.diff):
+ cd pcsx2
+ echo 'Patch #0 (version-fixes.diff):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p0 --fuzz=0
patching file cmake/SearchForStuff.cmake
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file cmake/SearchForStuff.cmake.rej
error: Bad exit status from /var/tmp/rpm-tmp.BdmXPD (%prep)]: [The Patch version-fixes.diff application failed.]
=============
[Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.BdmXPD
+ umask 022
+ cd /builddir/build/BUILD
+ git clone https://github.com/PCSX2/pcsx2 --recursive]: [The %prep section contains `git clone`. This is non-standard; typical RPM build is offline. Anyway, this makes the build "sensitive" for external changes and the patch application may get broken (as it happened) very easily.]
|
Issue: The spec file uses patch `version-fixes.diff` which is not applicable against the current sources.
Resolution: Fix the patch, or drop it - depending whether it is needed or not.
|
Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet:
Patch #0 (version-fixes.diff):
+ cd pcsx2
+ echo 'Patch #0 (version-fixes.diff):'
+ /usr/bin/patch --no-backup-if-mismatch -f -p0 --fuzz=0
patching file cmake/SearchForStuff.cmake
Hunk #1 FAILED at 95.
1 out of 1 hunk FAILED -- saving rejects to file cmake/SearchForStuff.cmake.rej
error: Bad exit status from /var/tmp/rpm-tmp.BdmXPD (%prep)
|
The Patch version-fixes.diff application 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:
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.BdmXPD
+ umask 022
+ cd /builddir/build/BUILD
+ git clone https://github.com/PCSX2/pcsx2 --recursive
|
The %prep section contains `git clone`. This is non-standard; typical RPM build is offline. Anyway, this makes the build "sensitive" for external changes and the patch application may get broken (as it happened) very easily.
|
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:
[Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.LlGRXf
+ umask 022
+ cd /builddir/build/BUILD/supernovas-1.1.1-build
+ cd /builddir/build/BUILD/supernovas-1.1.1-build
+ rm -rf SuperNOVAS-1.1.1
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/v1.1.1-2.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd SuperNOVAS-1.1.1
/var/tmp/rpm-tmp.LlGRXf: line 41: cd: SuperNOVAS-1.1.1: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.LlGRXf (%prep)
Bad exit status from /var/tmp/rpm-tmp.LlGRXf (%prep)
]: [This part indicated that during %prep phase the upstream archive was extracted, but it does not contained `SuperNOVAS-1.1.1` directory.]
|
Issue: During %prep phase you usually use %setup macro to extract upstream archive and cd into top-level directory. By default the directory is assumed to be %name-%version. But some upstream archive has different structure. In such case the build fails unless you tell %setup macro what to do.
Resolution: Check what is inside of the tarball and check what arguments to %setup macro is suitable for you. The relevant documentation is http://ftp.rpm.org/max-rpm/s1-rpm-inside-macros.html
|
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:
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.LlGRXf
+ umask 022
+ cd /builddir/build/BUILD/supernovas-1.1.1-build
+ cd /builddir/build/BUILD/supernovas-1.1.1-build
+ rm -rf SuperNOVAS-1.1.1
+ /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/v1.1.1-2.tar.gz
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd SuperNOVAS-1.1.1
/var/tmp/rpm-tmp.LlGRXf: line 41: cd: SuperNOVAS-1.1.1: No such file or directory
error: Bad exit status from /var/tmp/rpm-tmp.LlGRXf (%prep)
Bad exit status from /var/tmp/rpm-tmp.LlGRXf (%prep)
|
This part indicated that during %prep phase the upstream archive was extracted, but it does not contained `SuperNOVAS-1.1.1` directory.
|
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: No spec file found at /var/lib/copr-rpmbuild/workspace/workdir-ddehpqm9/Rokon.
]: [No spec file found for the build job.]
|
Issue: Because there is no spec file for the build.
Resolution: Source git tree should be checked and use proper parameters for making build.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.