Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ Your package (libzypp) Fails To Install in Fedora 40: can't install libzypp: - nothing provides libboost_thread.so.1.81.0()(64bit) needed by libzypp-17.31.8-2.fc39.x86_64 If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem. If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks. P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock: $ mock -r fedora-40-x86_64 --config-opts mirrored=False install libzypp P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages Thanks!
This wasn't rebuilt for the new boost because the package FTBFS in rawhide. libzypp-17.31.8/zypp-curl/proxyinfo/proxyinfolibproxy.h:18:10: fatal error: proxy.h: No such file or directory Also a missing header for PATH_MAX: /builddir/build/BUILD/libzypp-17.31.8/zypp-core/Pathname.cc: In member function ‘zypp::filesystem::Pathname zypp::filesystem::Pathname::realpath() const’: /builddir/build/BUILD/libzypp-17.31.8/zypp-core/Pathname.cc:247:21: error: ‘PATH_MAX’ was not declared in this scope 247 | char buff[PATH_MAX + 2]; | ^~~~~~~~ It should include <limits.h> to get that.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 7+ weeks. This is the first reminder (step 3) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 40 development cycle. Changing version to 40.
Hello, Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/ This package fails to install and maintainers are advised to take one of the following actions: - Fix this bug and close this bugzilla once the update makes it to the repository. (The same script that posted this comment will eventually close this bugzilla when the fixed package reaches the repository, so you don't have to worry about it.) or - Move this bug to ASSIGNED if you plan on fixing this, but simply haven't done so yet. or - Orphan the package if you no longer plan to maintain it. If you do not take one of these actions, the process at https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs will continue. This package may be orphaned in 4+ weeks. This is the second reminder (step 4) from the policy. Don't hesitate to ask for help on https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/ if you are unsure how to fix this bug.
Working on it, also have bug upstream about it: https://github.com/openSUSE/libzypp/issues/522
FEDORA-2024-c09d825437 (libzypp-17.31.32-1.fc40 and zypper-1.14.68-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-c09d825437
Proposed as a Freeze Exception for 40-beta by Fedora user ngompa using the blocker tracking app because: Fixes FTIs and FTBFS for Zypp stack.
FEDORA-2024-c09d825437 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-c09d825437` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-c09d825437 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Discussed during the 2024-03-04 blocker review meeting: [0] The decision to classify this bug as an "AcceptedFreezeException (Beta)" was made as FTI issues can interfere with upgrades, so straightforward FTI fixes are typically accepted. [0] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-04/f40-blocker-review.2024-03-04-17.00.log.txt
FEDORA-2024-c09d825437 (libzypp-17.31.32-1.fc40 and zypper-1.14.68-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.