Hi,
I've ran into this problem twice today... The automated scratch-build in PR
fails with 'error'.
When looking into the error message, it gives me no clear reason why it
failed.
These are the PRs with failed scratch-builds (Note: when using "fedpkg
scratch-build --srpm" the same builds are built successfully):
https://src.fedoraproject.org/rpms/libarchive/pull-request/10https://src.fedoraproject.org/rpms/proxysql/pull-request/9
Could anyone help me understand what is causing this?
Thank you so much :)
--
S pozdravom/ Best regards
Lukáš Javorský
Associate Software Engineer, Core service - Databases
Red Hat <https://www.redhat.com>
Purkyňova 115 (TPB-C)
612 00 Brno - Královo Pole
ljavorsk(a)redhat.com
<https://www.redhat.com>
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-34-20220213.0):
ID: 1128181 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1128181
ID: 1128194 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1128194
Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
No missing expected images.
Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64)
(Tests completed, but using a workaround for a known bug)
Old soft failures (same test soft failed in Fedora-Cloud-35-20220213.0):
ID: 1128165 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1128165
ID: 1128178 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL: https://openqa.fedoraproject.org/tests/1128178
Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
Hello,
this is about the following Fedora change:
https://fedoraproject.org/wiki/Changes/ExcludeFromWeakAutodetect
In the tracking bugzilla, the relevant comment is:
https://bugzilla.redhat.com/show_bug.cgi?id=2013327#c4
If I understand this correctly, the current implementation is not doing what
the change described and the change owner says the feature cannot be
implemented as described.
There are several options and we should probably decide what to do before beta
freeze. Hence opening this discussion.
The change summarizes as "We would like to change a default behavior
dnf/PackageKit/microdnf to install only newly recommended packages on
upgrades." however the current impementation disbales weak depndencies in
various other scenarios, as reported by various of our packagers e.g. in
Bug 2048394 - dnf should pull weak dependencies in install transaction
Bug 2033130 - exclude_from_weak_autodetect=true effectively renders rich weak
dependencies useless
Bug 2042808 - weakdeps not working on rawhide system
The change owner proposed 4 options to move forward. I understand them as follows:
1. do nothing, keep it broken
2. disable this behavior by default, keep it optional, but keep it broken
3. do not ignore already broken weak rich deps (partially reverts the change)
4. change the behavior on dynamically depending on the dnf command used
(discouraged)
(Go see the linked comment for details.)
Please let us know what you think is best or if there is a better solution.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok