Do you plan to push this update to testing? It's been stuck in "pending" for 4 days.

Do you plan to push this update to testing?

Do you plan to push this update to testing?

Works fine, default and performance regression test suites passed on both my systems.

Works fine so far. Also default and performance regression tests passed on both my systems.

Fixes upgrade path from f32, thanks!

Seems to work fine, default and performance tests pass on both my systems.

Seems to reliably crash during execution of "bomb-workers" in the benchmark.

Works for me

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).

Is any human being reading the comments on this update?

Please either waive the tests (if they're false positive failures) or unpush the update (if they're really broken).

Not sure if it was a good idea to push a major version update to stable fedora. It messes up my "database" for some reason, removing all old entries and re-inserting them with new IDs.

I was told to include this build with the libhandy1 0.90.0 update, and I can't do that if it's already part of another update.

This update has been unpushed.

This update has been unpushed.

Either this update should be pulled because of the broken tests, or they should be waived ... right now, it's just sitting there with lots of positive karma but stuck in testing because of failed gating tests.


Seems to work fine (linux/x86_64 guests on x86_64 via virt-manager).

Works fine.