Comments

750 Comments

Is this a release or a post-release snapshot? The commit message / changelog entry suggest the former, while the version string suggests the latter.

Fixes "rpmdev-bumpspec --new", should also fix the-new-hotness patch / scratch builld creation.

I don't know what caused this issue, but I got hundreds of lines of scriptlet errors when upgrading to kernel-devel from this update:

Installing       : kernel-devel-5.16.8-200.fc35.x86_64                  13/27 
  Running scriptlet: kernel-devel-5.16.8-200.fc35.x86_64                  13/27 
hardlink: cannot link ./Documentation/kbuild/Kconfig.recursion-issue-01 to /usr/src/kernels/5.16.5-200.fc35.x86_64/./Documentation/kbuild/Kconfig.recursion-issue-01.hardlink-temporary: File exists
hardlink: cannot link ./Documentation/kbuild/Kconfig.select-break to /usr/src/kernels/5.16.5-200.fc35.x86_64/./Documentation/kbuild/Kconfig.select-break.hardlink-temporary: File exists
hardlink: cannot link ./Documentation/userspace-api/media/Makefile to /usr/src/kernels/5.16.5-200.fc35.x86_64/./Documentation/userspace-api/media/Makefile.hardlink-temporary: File exists

(and thousands more lines like these)

Looks like they reference the wrong kernel version (5.16.5, should be 5.16.8?)

Full log from the failed scriptlet here: https://gist.github.com/decathorpe/55a821a98b6cc39a1c1fca7cede78325

Prepared and built tons of updates with this today, worked like a charm. The new argcomplete-based bash completions are also very nice :+1:

Works fine. Default and performance regression tests also pass on all my systems:

  • Ryzen 5800X on ASUS ROG X570-E with NVidia GTX 1070 running 510.47.03 RPMFusion drivers
  • dell XPS 13 9370 (Intel Core i7 8550U / UHD Graphics 620)

Though it seems tmpfs is noticably slower with any 5.16 kernel ... or maybe I'm imagining things.

Works fine. Default and performance regression tests also pass on all my systems:

  • Ryzen 5800X on ASUS ROG X570-E with NVidia GTX 1070 running RPMFusion drivers
  • dell XPS 13 9370 (Intel Core i7 8550U / UHD Graphics 620)

This is suffering the same broken dependency problem as the rawhide update: https://bugzilla.redhat.com/show_bug.cgi?id=2047225

You will probably need to disable CUDA support in these packages.

This is suffering the same broken dependency problem as the rawhide update: https://bugzilla.redhat.com/show_bug.cgi?id=2047225

You will probably need to disable CUDA support in these packages.

python3-azure-cli-core from this update is not installable due to this unsatisfied dependency: "(python3.10dist(humanfriendly) >= 10 with python3.10dist(humanfriendly) < 11)"

It doesn't really matter. Only "security" updates are handled slightly differently.

This update has been in testing for three weeks (and in f34-stable for two weeks), and nobody else seems to have hit this problem. I'll push it to stable (since I'll build 1.18.6 tomorrow anyway).

The version string for this update is very weird and non-standard. The update text suggests that this should in fact be libtpms-0.9.2-1.fc35, but the actual version string suggests it is a pre-release git snapshot of 0.9.2, with an additional ".0" suffix that I don't know what it should signify. The packaging also suggests that you're using plain git archives, but then I wonder why you're not using standard download URLs for git archives from GitHub.

Dropping support for architectures in stable branches is a no-go. 600+ MBs of new dependencies too.

Dropping support for architectures in stable branches is a no-go. 600+ MBs of new dependencies too.

Works fine. Default and performance regression tests also pass on all my systems:

  • Ryzen 5800X on ASUS ROG X570-E with NVidia GTX 1070 running RPMFusion drivers
  • dell XPS 13 9370 (Intel Core i7 8550U / UHD Graphics 620)

That's the only distantly-related change I see between this version and the last, but it should not pre-set any GUI authentication for you, if you already had syncthing set up before. This also didn't happen on any of my machines ... but I'll let this update sit in updates-testing for now, maybe somebody else has this problem too.

Are you sure that this is caused by this update, and not by some peculiarity of your local configuration? I tested this update on three different machines (two desktops, one headless server), and it didn't cause any issues.