nv-codec-headers-12: 12.0.16.0 -> 12.1.14.0#260538
nv-codec-headers-12: 12.0.16.0 -> 12.1.14.0#260538r-ryantm wants to merge 1 commit intoNixOS:masterfrom
Conversation
|
@ofborg build jellyfin |
|
So, is there anything missing to merge this request? I could only build ffmpeg 6.1 with this update. |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: |
|
@ofborg build jellyfin-ffmpeg If you can somehow confirm this is still working, I'll merge. |
|
This appears to break the only dependent package, so this PR won't be merged any time soon. |
It seems that the jellyfin-ffmpeg is using ffmpeg 6.0, so that is the issue. We need to wait until they update to ffmpeg 6.1 to be able to proceed. |
|
Upstream agreed to update to ffmpeg 6.0.1, which has a fix for this. |
|
Thank you very much for bringing this upstream :). It looks like they've already made a release. Could you create a new PR against staging which updates ffmpeg, ffmpeg-jellyfin and incorporates this PR? |
|
Closing as it has been done here: #271905. |
Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/nv-codec-headers/versions.
meta.description for nv-codec-headers-12 is: FFmpeg version of headers for NVENC
meta.homepage for nv-codec-headers-12 is: https://git.videolan.org/?p=ffmpeg/nv-codec-headers.git
Updates performed
To inspect upstream changes
Impact
Checks done (click to expand)
passthru.tests, if any, passedRebuild report (if merged into master) (click to expand)
Instructions to test this update (click to expand)
Either download from Cachix:
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-userslist or you can usesudosince root is effectively trusted.Or, build yourself:
Or:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of
nixpkgs-reviewrun on x86_64-linux 12 packages failed to build:
1 package built:
Maintainer pings
cc @MP2E for testing.