Hello.
fmt 10.0.x update will include a soversion bump from .9 to .10. It has both API and ABI changes.
Changelog: https://github.com/fmtlib/fmt/releases/tag/10.0.0
The list of affected packages in Rawhide:
0ad OpenImageIO bear cachelib cantera ceph dnf5 dolphin-emu domoticz easyeffects easyrpg-player fb303 fbthrift fizz fmidi folly freeopcua gerbera giada gnuradio gr-funcube libsemigroups libsonata luxcorerender mcrouter mkvtoolnix nheko proxygen rstudio sdrpp spdlog vcpkg wangle watchman waybar zswap-cli
I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week.
On 23/05/2023 12:22, Vitaly Zaitsev wrote:
I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week.
Many packages are not yet ready for fmt 10. Spdlog for example:
- https://github.com/gabime/spdlog/issues/2614 - https://github.com/gabime/spdlog/issues/2767 - https://github.com/gabime/spdlog/issues/2782
On 23/05/2023 12:22, Vitaly Zaitsev wrote:
I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week.
Koji is now broken in this side tag (f39-build-side-69392):
Error: Problem 1: package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data = 4.16.1-2.fc39, but none of the providers can be installed - package dnf-data-4.16.1-2.fc39.noarch from build requires /etc/dnf/dnf.conf, but none of the providers can be installed - conflicting requests - nothing provides libfmt.so.9()(64bit) needed by libdnf5-5.0.14-1.fc39.ppc64le from build Problem 2: package python3-dnf-plugins-core-4.4.1-3.fc39.noarch from build requires python3-dnf >= 4.11.0, but none of the providers can be installed - package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data = 4.16.1-2.fc39, but none of the providers can be installed - package dnf-plugins-core-4.4.1-3.fc39.noarch from build requires python3-dnf-plugins-core = 4.4.1-3.fc39, but none of the providers can be installed - package dnf-data-4.16.1-2.fc39.noarch from build requires /etc/dnf/dnf.conf, but none of the providers can be installed - conflicting requests - nothing provides libfmt.so.9()(64bit) needed by libdnf5-5.0.14-1.fc39.ppc64le from build (try to add '--skip-broken' to skip uninstallable packages)
How I can fix that?
On Wednesday, 28 June 2023 at 08:32, Vitaly Zaitsev via devel wrote:
On 23/05/2023 12:22, Vitaly Zaitsev wrote:
I will use my proven-packager rights to rebuild all dependent packages in a separate side tag next week.
Koji is now broken in this side tag (f39-build-side-69392):
Error: Problem 1: package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data = 4.16.1-2.fc39, but none of the providers can be installed
- package dnf-data-4.16.1-2.fc39.noarch from build requires
/etc/dnf/dnf.conf, but none of the providers can be installed
- conflicting requests
- nothing provides libfmt.so.9()(64bit) needed by
libdnf5-5.0.14-1.fc39.ppc64le from build Problem 2: package python3-dnf-plugins-core-4.4.1-3.fc39.noarch from build requires python3-dnf >= 4.11.0, but none of the providers can be installed
- package python3-dnf-4.16.1-2.fc39.noarch from build requires dnf-data =
4.16.1-2.fc39, but none of the providers can be installed
- package dnf-plugins-core-4.4.1-3.fc39.noarch from build requires
python3-dnf-plugins-core = 4.4.1-3.fc39, but none of the providers can be installed
- package dnf-data-4.16.1-2.fc39.noarch from build requires
/etc/dnf/dnf.conf, but none of the providers can be installed
- conflicting requests
- nothing provides libfmt.so.9()(64bit) needed by
libdnf5-5.0.14-1.fc39.ppc64le from build (try to add '--skip-broken' to skip uninstallable packages)
How I can fix that?
If dnf requires fmt, then you have to submit a compat fmt package first so that dnf remains installable. I'd try untaggin the new fmt from that side tag to fix this.
Regards, Dominik
On 28/06/2023 08:32, Vitaly Zaitsev wrote:
How I can fix that?
Steps how to fix such issues for historical purposes:
1. Create a new side tag. 2. Introduce compatibility fmt9 package. 3. Build fmt9 compatibility package. 4. Build fmt 10. 5. Rebuild dnf5 against fmt 10. 6. Untag fmt9 from this side tag. 7. Retire fmt9 compatibility package.
On Wed, 28 Jun 2023 at 04:20, Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
On 28/06/2023 08:32, Vitaly Zaitsev wrote:
How I can fix that?
Steps how to fix such issues for historical purposes:
- Create a new side tag.
- Introduce compatibility fmt9 package.
- Build fmt9 compatibility package.
- Build fmt 10.
- Rebuild dnf5 against fmt 10.
- Untag fmt9 from this side tag.
- Retire fmt9 compatibility package.
Thanks for documenting this for other people to find in the future.
You could bootstrap dnf for the rebuild
https://src.fedoraproject.org/rpms/dnf/blob/rawhide/f/dnf.spec#_298
Results: 37 builds succeeded, 19 failed.
FTBFS:
0ad arbor CuraEngine bout++ cachelib contour-terminal dnf5 dolphin-emu easyrpg-player folly freeopcua gerbera gnuradio luxcorerender mangohud nheko wasmedge watchman waybar
Please fix your packages and use f39-build-side-69394 side tag: fedpkg build --target f39-build-side-69394
On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
Results: 37 builds succeeded, 19 failed.
gnuradio
Issue filed upstream: https://github.com/gnuradio/gnuradio/issues/6735
Also, not all the maintainers may review the devel list as closely. In the past when I've had a lot of affected packages I wrote a simple bash script that took the package names and output the <package>- maintainers@fedoraproject.org email so I could copy and paste it into my email client.
Not quite the way I did it but ChatGPT came up with this: ``` #!/bin/bash
# Specify the input file containing package names (one per line) input_file="package_names.txt"
# Initialize an empty string to store the email addresses email_addresses=""
# Read each package name from the input file while IFS= read -r package_name; do # Construct the email address and append it to the string email_address="${package_name}-maintainers@fedoraproject.org" email_addresses+="${email_address};" done < "$input_file"
# Remove the trailing semicolon, if any email_addresses=${email_addresses%;}
# Print the final email addresses string echo "$email_addresses" ```
Thanks, Richard
On Wed, Jun 28, 2023 at 6:37 AM Richard Shaw hobbes1069@gmail.com wrote:
On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
Results: 37 builds succeeded, 19 failed.
gnuradio
Issue filed upstream: https://github.com/gnuradio/gnuradio/issues/6735
I'm currently at work but if a proven packager wants to try the solution proposed in the above that would be helpful.
Thanks, Richard
Richard Shaw wrote on 2023/06/28 23:40:
On Wed, Jun 28, 2023 at 6:37 AM Richard Shaw hobbes1069@gmail.com wrote:
On Wed, Jun 28, 2023 at 6:12 AM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
Results: 37 builds succeeded, 19 failed.
gnuradio
Issue filed upstream: https://github.com/gnuradio/gnuradio/issues/6735
I'm currently at work but if a proven packager wants to try the solution proposed in the above that would be helpful.
Thanks, Richard
Fixed (build ongoing) https://koji.fedoraproject.org/koji/buildinfo?buildID=2223120
So with fmt10, it seems fmt::format no longer accepts (unscoped) enum by default, just casting into int fixes the issue.
dolphin-emu can perhaps be fixed similarly, ref: https://github.com/dolphin-emu/dolphin/commit/cc5640245cf4316f9bafcb11141d88... If someone can apply the above change, I will appreciate it (because now I want to take a rest)
Mamoru
On Wed, Jun 28, 2023 at 1:12 PM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
Results: 37 builds succeeded, 19 failed.
FTBFS:
0ad arbor CuraEngine bout++ cachelib contour-terminal dnf5 dolphin-emu easyrpg-player folly freeopcua gerbera gnuradio luxcorerender mangohud nheko wasmedge watchman waybar
Please fix your packages and use f39-build-side-69394 side tag: fedpkg build --target f39-build-side-69394
Since you already have the compat package, I would suggest merging the side tag as is. The compat package makes it possible for the package maintainers to switch over at their own pace when they have time to deal with this.
Also, please file FTBFS bugs against packages that failed to build.
On 28/06/2023 14:10, Kalev Lember wrote:
Since you already have the compat package, I would suggest merging the side tag as is.
I'm waiting for dnf5: https://github.com/rpm-software-management/dnf5/issues/675 https://bugzilla.redhat.com/show_bug.cgi?id=2218180
I fixed some packages with trivial issues. Now only 16 packages could not be built from sources.
Also I want to untag fmt9 compat package before merging side tag. It was introduced only to fix issues with dnf5 in Koji.
On 6/28/23 04:10, Vitaly Zaitsev via devel wrote:
Results: 37 builds succeeded, 19 failed.
FTBFS:
waybar
Known regression in fmt. Please, apply https://github.com/fmtlib/fmt/pull/3430.
On 28/06/2023 15:00, Aleksei Bavshin wrote:
Known regression in fmt. Please, apply https://github.com/fmtlib/fmt/pull/3430.
Thanks for the information. The fix has been ported to fmt-10.0.0-2.fc39.
waybar is now fixed.
FTBFS: easyrpg-player
Upstream has already updated the program to work with fmt10, so I just applied the relevant commit to the Fedora package.
Submitted and rebuilt: https://koji.fedoraproject.org/koji/taskinfo?taskID=102705429
A.FI.
FTBFS: contour-terminal
Applying the related upstream commit as the patch, the rebuild succeeded.
Ref: https://koji.fedoraproject.org/koji/taskinfo?taskID=102707247
FTBFS:
0ad arbor CuraEngine bout++ cachelib dolphin-emu folly freeopcua gerbera luxcorerender mangohud wasmedge watchman
I think I will merge this side tag without fmt9 compatibility package tomorrow.
On Wed, Jun 28, 2023 at 8:03 PM Vitaly Zaitsev via devel < devel@lists.fedoraproject.org> wrote:
FTBFS:
0ad arbor CuraEngine bout++ cachelib dolphin-emu folly freeopcua gerbera luxcorerender mangohud wasmedge watchman
I fixed 0ad from that list and built it in the side tag.
I think I will merge this side tag without fmt9 compatibility package tomorrow.
Why? Now that you've already done all the work of adding the compatibility package, why drop it and break all of the unbuilt packages in rawhide? I don't think any of the packages from the list are release blocking, but it just seems antisocial for rawhide users to break packages they might be using, especially if it's no extra work for you at this point.
Another thing that comes in my mind is that there is the ongoing python rebuild in f39-python and your rebuilt package set probably intersects with it. Would be good to let Miro know what packages they need to rebuild again once your fmt tag is merged.
On 28/06/2023 23:39, Kalev Lember wrote:
Why? Now that you've already done all the work of adding the compatibility package, why drop it and break all of the unbuilt packages in rawhide? I don't think any of the packages from the list are release blocking, but it just seems antisocial for rawhide users to break packages they might be using, especially if it's no extra work for you at this point.
At least one maintainer emailed me that they want to use fmt9-devel instead of fixing FTBFS. Sorry, but I can't allow that.
Another possible solution - rebuild fmt9 without -devel subpackage to prevent its usage for building new packages.
Another thing that comes in my mind is that there is the ongoing python rebuild in f39-python and your rebuilt package set probably intersects with it.
Yes. All packages with Python bindings (dnf5 for example).
Would be good to let Miro know what packages they need to rebuild again once your fmt tag is merged.
Another reason to untag it is to make sure all packages are built against fmt 10.
Also FTI RHBZ tickets will be generated automatically.
Dne 28. 06. 23 v 23:39 Kalev Lember napsal(a):
On Wed, Jun 28, 2023 at 8:03 PM Vitaly Zaitsev via devel devel@lists.fedoraproject.org wrote:
FTBFS: 0ad arbor CuraEngine bout++ cachelib dolphin-emu folly freeopcua gerbera luxcorerender mangohud wasmedge watchman
I fixed 0ad from that list and built it in the side tag.
I think I will merge this side tag without fmt9 compatibility package tomorrow.
Why? Now that you've already done all the work of adding the compatibility package, why drop it and break all of the unbuilt packages in rawhide? I don't think any of the packages from the list are release blocking, but it just seems antisocial for rawhide users to break packages they might be using, especially if it's no extra work for you at this point.
This don't necessarily breaks Rawhide users. It just won't let them update some packages. The only question is if the packages gets fixed eventually.
Vít
Another thing that comes in my mind is that there is the ongoing python rebuild in f39-python and your rebuilt package set probably intersects with it. Would be good to let Miro know what packages they need to rebuild again once your fmt tag is merged.
-- Kalev
devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-leave@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue
The side tag has been merged: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e8e736635
FTBFS (final):
arbor (not related to fmt, some tests failed on s390x) CuraEngine bout++ cachelib dolphin-emu folly mangohud (not related to fmt) wasmedge watchman
FTI issues will be generated automatically after the next Rawhide compose.
Maintainers of these packages can build fixed versions to Rawhide directly without using any side tags.
Vitaly,
On Friday, 30 June 2023 at 07:42, Vitaly Zaitsev via devel wrote:
The side tag has been merged: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e8e736635
FTBFS (final):
arbor (not related to fmt, some tests failed on s390x) CuraEngine bout++ cachelib dolphin-emu folly mangohud (not related to fmt) wasmedge watchman
FTI issues will be generated automatically after the next Rawhide compose.
Maintainers of these packages can build fixed versions to Rawhide directly without using any side tags.
That is not excellent. Since you had the fmt9 package done, you could've just added it to Fedora without review (compat packages of existing ones don't need one). The above packages would then get FTBFS bugs filled, but would still be installable. You could've even orphaned the fmt9 compat package immediately, which would have give maintainers who depend on it 6 weeks to react and either pick it up or fix their packages to build with newer fmt. As it is, you're forcing the above maintainers to scramble to fix their packages at the beginning of summer holiday season.
Regards, Dominik
On 30/06/2023 10:01, Dominik 'Rathann' Mierzejewski wrote:
As it is, you're forcing the above maintainers to scramble to fix their packages at the beginning of summer holiday season.
Announced: 23.05.2023. Rebuild started: 27.06.2023. FTBFS packages announced: 28.06.2023. Side tag merged: 30.06.2023.
On Friday, 30 June 2023 at 12:37, Vitaly Zaitsev via devel wrote:
On 30/06/2023 10:01, Dominik 'Rathann' Mierzejewski wrote:
As it is, you're forcing the above maintainers to scramble to fix their packages at the beginning of summer holiday season.
Announced: 23.05.2023. Rebuild started: 27.06.2023. FTBFS packages announced: 28.06.2023. Side tag merged: 30.06.2023.
That's a reasonable timeline, except not everyone reads the devel mailing list so they might have found out only today that there's something they need to do. I would've done a rebuild in COPR before announcing and doing it in Fedora and contacted maintainers of FTBFS packages directly at the same time. You wouldn't have been pressed for time to merge the side tag quickly, then. It's very easy to automate, too. See the great talk by Karolina Surma at DevConf 2023: https://devconfcz2023.sched.com/event/1MYlI/fedora-package-update-assess-its...
Regards, Dominik
On Fri, Jun 30, 2023 at 07:42:39AM +0200, Vitaly Zaitsev via devel wrote:
The side tag has been merged: https://bodhi.fedoraproject.org/updates/FEDORA-2023-4e8e736635
FTBFS (final):
arbor (not related to fmt, some tests failed on s390x) CuraEngine bout++ cachelib dolphin-emu folly mangohud (not related to fmt) wasmedge watchman
Going to fix folly, cachelib and watchman
Best regards,