Yeah, I updated my f33 test box today, and ~80 new packages got pulled in, including some big ones (scala with 22M alone, plus four different variants of openblas for some reason, adding up to 20M, vtk at 17M, opencv itself with 10M ...)
While I like that my Java packages reach a broader audience (/sarcasm) this is probably going to explode the Workstation image size (and others) by at least 100M or so :(
Giving negative karma so this doesn't go to stable, 1.46.0-2.fc32 should supersede the build in this update.
For the record: 1.46.0 breaks compilation of doctests in release+LTO mode (which is the default for RPM builds).
Well, this update actually fixes the broken postun scriptlet, but upon upgrade, the broken one from the old package version is run (which is unfortunate, but can't really be fixed now ...)
Is this update supposed to go to stable now? It was opened three years ago, so maybe that's not even a good idea anymore.
Works fine, and regression and performance tests pass on all tested systems: - AMD ryzen 1700X / NVidia GTX 1070 w/ negativo17 drivers - dell XPS 13 9370 (2018) - libvirt/KVM based fedora 32 VMs
python3-molecule from this update is not installable:
Error: Problem: cannot install the best candidate for the job - nothing provides pre-commit needed by python3-molecule-3.0.2-6.fc30.noarch
Also, is this built from the master branch? Because the f30 branch doesn't have these changes ...