The package installs, imports, and satisfies the dependency of python-aiodns-3.0.0.

Once I replace the build with 0.67.0, this will require FEDORA-2022-3402dfbec3.

Just as a heads-up: this caused python-hdmf and python-pynwb to fail to install in F35, since both packages were upper-bounding the numpy version. It looks like I will be able to fix these two packages by simply removing the upper bounds.

Thanks for doing the update! Everything looks good. I linked the RHBZ bug from release monitoring so it can be auto-closed.

Since the big grpc/abseil-cpp update didn’t quite make it in before the Beta Freeze, you’ll need to rebuild this in F37 after it lands, or rebuild it into the side tag f37-build-side-57002 and I can include the rebuild in that update. That resets the 7-day clock, but I just reset it to include the latest grpc patch release anyway. Sorry about that!

Fixed.

Disabled autopush because this is missing rapidyaml. I’ll re-enable it after I add the build.

An upstream bug was reported in 2.0.7. This update should not go stable until it is updated to 2.0.8, which was just released.

An upstream bug was reported in 2.0.7. This update should not go stable until it is updated to 2.0.8, which was just released.

Technically, the embree bug now references 3.13.4, and this update includes only 3.13.3. See: https://src.fedoraproject.org/rpms/embree/pull-request/1

The update installs, and Blender starts.

Thanks for your testing!

Updated with a new build; see comments in FEDORA-2022-afbc5a5a95.

Updated with a new build to fix the “*” symlink regression mentioned above, and to fix the self-reported version number.

Thanks! I’ll patch the version number in the source code.

I’m not sure what to do about the trailing BUILD (here “2”). It’s really designed to count upstream binary release builds, I think. It’s exposed to plugins but I’m not sure if any use it. Still, that keeps me from wanting to stuff the entire RPM “release” string in there, e.g., 1.fc36, lest some plugin expect it to be a decimal representation. Maybe I’ll just use the RPM packages numeric pkgrel field.

I also discovered that I introduced a regression in which broken symlinks named * could be created by the launcher script in ~/.imagej/luts and ~/.imagej/plugins. That was relatively harmless, but I’ll update this with a fix for that, as well.

Feel free to add qalculate-qt-4.2.0-1.fc36 to this update.

I had to manually update my F35 workstation with the corresponding pyproject-rpm-macros update in order to be able to do anything, even just fedpkg build, with a spec file that uses the new -w option. I guess that isn’t surprising.

Once I did that, this worked beautifully with python-hatchling in F37 and F36. I can fully test it on F35 once the update for that release moves from pending to testing.

This is great!

Works to run the async tests for python-aiosignal.

Replaced the usd build in this update with one that contains the fix for fix for CVE-2022-28041. Changed update type from bugfix to security.

Thanks for testing!