Comments

739 Comments

You might want to delete the custom update name (where you - probably accidentally - entered your FAS username). If you leave that field empty, it defaults to the builds contained in the update.

You might want to delete the custom update name (where you - probably accidentally - entered your FAS username). If you leave that field empty, it defaults to the builds contained in the update.

karma

The -examples subpackage is not installable due to two problems:

  • the referenced -files subpackage doesn't exist
  • there's a typo in the dependency specification (missing % making the %{?_isa} macro inoperable)
karma

The -examples subpackage is not installable due to two problems:

  • the referenced -files subpackage doesn't exist
  • there's a typo in the dependency specification (missing % making the %{?_isa} macro inoperable)

Works fine, no problems encountered.

No issues encountered with epiphany etc.

Well, it's mostly true that "upgrade path" doesn't matter anymore (you're right that dist-upgrades do distro-sync - and downgrade - now by default).

In this case, this turned out to not be a problem, but in other cases, I found updates that were missing from f32 entirely (which is a problem, since package downgrades aren't exactly supported, and it's not good for f32 to be missing bugfixes and security updates).

But thanks for fixing it anyway :)

Nit-pick: With some unrelated changes in fedora 31 and 30, builds from this fedora 32 update now have a lower NVR than the builds from fedora 31 or 30.

When doing such "unrelated fixes" in older branches, it's recommended to append .1 to the Release (like 1%{?dist}.1, and then incrementing that postfix number) instead of incrementing the Release like normal. This preserves a correct upgrade path within and across releases.

This update breaks the upgrade path to fedora 32.

I see you've built the same version as in rawhide on f32, but it looks like you forgot to file a bodhi update for it. Please do that now, so it can land in stable before the final freeze.

This build is definitely also affected by JVM crashes, which I originally reported for rawhide:

https://bugzilla.redhat.com/show_bug.cgi?id=1813550

Very crashy, please do not push to stable :)

Works fine so far. Default and performance regression test suites also pass on both my systems:

  • amd Ryzen 1700X + NVidia GTX 1070 w/ negativo17 drivers
  • dell XPS 13 9370 (2018)

This update breaks the upgrade path from fedora 31 → fedora 32. This version has been built in koji, but no bodhi update for fedora 32 was created yet.

An update for fedora 32 has been created, retracting my issue about upgrade path :)

karma

This update breaks the upgrade path to fedora 32. libevdev-1.9.0-1.fc32 has been built in koji, but no bodhi update for it has been created.

This update breaks the upgrade path to fedora 32, since 3.1.3 has not been built and submitted for fedora 32 yet.

karma

Seems to work fine (cloning + building updates on rawhide + stable branches)

karma

python3-mayavi is not installable:

Error: Problem: cannot install the best candidate for the job - nothing provides python3.7dist(pyface) >= 6.1.1 needed by python3-mayavi-4.7.1-2.fc30.x86_64

This update breaks the upgrade path to fedora 32. Looks like 3.6.4 was built for f32, but no bodhi update was created.

karma

I don't know how it's possible that bigloo from this update is not compatible with bigloo-libs from this update, but "dnf install bigloo" fails. See also the dist.rpmdeplint failure in the test results. (this also affects rawhide, where this is already stable)

BZ#1807758 bigloo-4.3g is available
karma

Seems to work fine so far. Default and performance regression tests also passed on both my systems:

  • AMD ryzen 1700X + NVidia GTX 1070 w/ negativo17 drivers (440.64)
  • dell XPS 13 9370 (2018)