Comments
music
That’s probably the safer choice, unless there’s some reason to really want the update in F40. It might be OK to proceed if a more thorough impact check shows nothing else is broken.
I’ve backported the python-meson-python patch either way.
Just a heads-up that this update caused python-meson-python to FTBFS in Rawhide, although I was able to patch it easily.
I plan to backport that patch to F40 to accommodate this update.
I performed a very basic check. The application starts. I can navigate the tour. I can type into the interactive console and open Python scripts.
If the ABI break is not addressed, why build this for F40 and break all the dependent packages? See https://bugzilla.redhat.com/show_bug.cgi?id=2261766#c5.
Works for me, and fixes a GCC optimization bug involving signed zeros that was responsible for https://github.com/shibatch/sleef/issues/439: FEDORA-2024-d50f7ba432
This update has been unpushed.
Replaced by FEDORA-2024-acd629e509.
Tested by manual download and installation of RPMs since this is not yet in updates-testing.
I confirmed that a trivial crate library package (rust2rpm drop-tracker) has the same spec file except for the rust2rpm version comment.
I confirmed that rust2rpm -p b3sum correctly flags the missing license file in the crate, and that I can proceed using rust2rpm -p --ignore-missing-license-files b3sum. Furthermore, I was able to write a rust2rpm.toml that almost eliminates hand-editing the generated spec file, including generating and installing a man page with help2man and patching in the missing license file from upstream. All I had to do by hand was replace # FIXME: no license files detected with %license LICENSE, and paste in the output of %cargo_license_summary in the right place.
This is a really exciting update!
Both the regression I reported on the 0.6.2 update and https://github.com/fedora-infra/rpmautospec/issues/71 / https://github.com/fedora-infra/rpmautospec/issues/80 appear to be fixed in 0.6.3. Thanks!
$ fedpkg co cramjam-cli
$ cd cramjam-cli
$ fedpkg mockbuild -- --dnf
Downloading cramjam_cli-0.1.1.tar.gz
######################################################################## 100.0%
Could not execute mockbuild: Couldn’t parse spec file cramjam-cli.spec:
Spec file is missing.
The above works fine with 0.6.1.
There appears to be a regression with rpmautospec packages in Koji that started yesterday. I don’t know what version of rpmautospec is running there, and I don’t know if it’s associated with an rpmautospec update or something else, so I’m not giving negative karma – but I am leaving this comment as a heads-up.
Superseded by FEDORA-2023-427f7d3cbb.
This update has been unpushed.
The new build should have identical contents, but it was built with the test suite enabled.
One user did report problems in the Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2240134#c10
This seems to work fine for me on a GNOME/Wayland session, using either the Wayland or the non-Wayland launcher.
The
oxipngexecutable worked in a “smoke test” in an EPEL9-next chroot. The upstream-generated man page was properly formatted. The rust-oxipng+image-devel-9.1.1-1.el9.next.noarch.rpm and rust-oxipng+sanity-checks-devel-9.1.1-1.el9.next.noarch.rpm metapackages fail to install, but nothing depends on them; I will fix them by temporarily hiding the features in a follow-up update.