Bug 2291961
| Summary: | F41FailsToInstall: python3-ufo2ft+cffsubr, python3-ufo2ft+compreffor, python3-ufo2ft | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fedora Fails To Install <fti-bugs> |
| Component: | python-ufo2ft | Assignee: | Benson Muite <benson_muite> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | benson_muite, kparal, ksurma, mhroncok |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedFreezeException | ||
| Fixed In Version: | python-ufo2ft-3.3.1-1.fc41 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-10-17 23:11:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 2315556 | ||
| Bug Blocks: | 2260877, 2244836, 2247868 | ||
|
Description
Fedora Fails To Install
2024-06-12 11:31:17 UTC
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. Some of the dependencies also need updating. This package has failed to build with Python 3.13 so far. Fedora 41 is already in the Beta Freeze phase. What's your plan going forward? Will the package be fixed in time for the Final Freeze of Fedora 41 (planned on Oct 15th 2024)? If you don't plan or can't fix the package before Fedora 41 goes into the Final Freeze phase, please retire the package. You can unretire it anytime during the Fedora 41 lifecycle - doing this now will simply ensure that we don't release Fedora with a broken package. Thank you! Need https://src.fedoraproject.org/rpms/python-fontMath/pull-request/1 merged for rawhide and f41 to proceed. It builds on f41 and f40 if python-fontMath is updated: https://copr.fedorainfracloud.org/coprs/fed500/python3-ufo2ft/build/8113632/ Could one of you proven packagers update python-fontMath? I see the build failed on rawhide. Would need to debug rawhide. Without updated fontMath, many tests fail on f41 and f40: https://koji.fedoraproject.org/koji/taskinfo?taskID=124520614 https://koji.fedoraproject.org/koji/taskinfo?taskID=124520649 Could you please build python-mutatormath in your copr, so we make sure the update does not break it? Build for python-mutatormath works: https://copr.fedorainfracloud.org/coprs/fed500/python3-ufo2ft/build/8114034/ PR is merged into rawhide and f41. I started a rawhide build: https://koji.fedoraproject.org/koji/taskinfo?taskID=124542225 For f41, you might want to build the package into your own side tag, so it is easier for you to create a joined update with ufo2ft. Let me know if you need help with that. > For f41, you might want to build the package into your own side tag...
I'm on it.
I built python-fontMath in f41-build-side-98192 but python-ufo2ft keeps failing there :/ It is ok to disable the failing test: https://github.com/googlefonts/ufo2ft/issues/877 Updating build and creating a sidetag. Build works in copr: https://copr.fedorainfracloud.org/coprs/fed500/python3-ufo2ft/build/8132846/ Created a sidetag: f41-build-side-98314 but not sure how to ensure that the last build of fontMath in the sidetag is used for the next build of ufo2ft You would do: koji tag f41-build-side-98314 python-fontMath-0.9.4-1.fc41 koji wait-repo f41-build-side-98314 --build=python-fontMath-0.9.4-1.fc41 However, since python-fontMath-0.9.4-1.fc41 is already available in f41-build-side-98192, I am building python-ufo2ft-3.3.1-1.fc41 now. FEDORA-2024-f4bcc30ba7 (python-fontMath-0.9.4-1.fc41 and python-ufo2ft-3.3.1-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-f4bcc30ba7 Thanks. Discussed at a blocker review meeting [1], agreed on the following: All six proposed FEs - 2291477 , 2291818 , 2275052 , 2291961 , 2301218 , 2283616 - are accepted as they are fails-to-install bugs and by precedent we accept these if there are no unusual factors involved, to keep the frozen tree as installable as possible [1] https://meetbot-raw.fedoraproject.org//meeting_matrix_fedoraproject-org/2024-10-14/ FEDORA-2024-f4bcc30ba7 has been pushed to the Fedora 41 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-f4bcc30ba7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-f4bcc30ba7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-f4bcc30ba7 (python-fontMath-0.9.4-1.fc41 and python-ufo2ft-3.3.1-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. |