-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
obs-studio: 28.0.3 -> 28.1.2, plugins fixes #200639
Conversation
d1c7f36
to
f79ef25
Compare
Co-authored-by: Raphael Robatsch <raphael-git@tapesoftware.net>
There is no release with OBS 28 support yet.
f79ef25
to
a9dacbb
Compare
Possible overlooked casualty: Anyone using v27 on unstable had support for obs-websocket yesterday but doesn't today. pkgs/applications/video/obs-studio/plugins/obs-websocket.nix The plugin was removed (due to inclusion in v28) before the late decision to keep v27 around, and didn't get restored. Not sure how big a concern but seems kind to leave in place in some form for people using it. Edit: On second glance it looks like plugins are doing a hard cutover in general so maybe this doesn't matter. Anyone using much of anything on v27 will need to pull from a previous version of nixpkgs either way. |
Also still missing: 22.11 release notes for the major version bump and plugin breakage, as previously noted by raphaelr. |
@raphaelr any plans to submit these patches upstream? |
I'm planning to send an upstream PR with Provide-runtime-plugin-destination-as-relative-path.patch once it's had a few days on master, since it's fixing general-case breakage for anyone building with a custom install prefix. |
Cool Personally I'm thinking about obs-multi-rtmp (the one I package). I'm happy to take the patch and submit a PR, with permission, but it feels better the author submit it :) |
That was exactly what I was thinking when preparing this PR. I think we'll just remove v27 because maintaining plugins for both version is just too much. |
I disagree, we are bumping packages all the time without mentioning it in the changelog. The commonly used plugins are working. obs-hyperion is probably not used by anyone and thus marked as broken. No need for release notes IMHO. |
See discussion #194578 here, I don't need both but some need 27 until their plugins are compatible with 28 as far as I understood? (possibly irrelevant because of #200639 (comment)) |
Okay, deferring to you on this one. For the record, at the very least the obs-websocket plugin removal is a breaking change for anyone referencing it in 22.05. Easily remedied, but breaks working configs. It broke mine. Your call on it meriting a mention or not. Cheers! |
The plugins we have packaged and are not marked as broken are working. And that's the only thing we should care about. If we keep 27 we need to have two versions of most plugins which is insanity. People still using v27 should just use 22.05. 😏 If I read correctly no one stepped up in the other PR that they've packaged obs-plugins themselves. |
Fair point. I've removed |
31e7f29
to
2ba52d9
Compare
As there are currently some plugins broken on master since I merged #194578 prematurely, I'd like to merge this as soon as possible. Any other comments on the immediate changes here? |
2ba52d9
to
96edebd
Compare
Not in a place to runtime test the impacted plugins but builds are green and a simple obs runtime test looks good to me. Result of 1 package marked as broken and skipped:
2 packages blacklisted:
10 packages built:
|
I've tested the plugins and their basic functionality. Not sure if everything works but they are being loaded correctly, can be configured and do stuff. ;) If you encounter issues please mention me in a follow-up PR or issue and we'll get that fixed ASAP. |
@06kellyjac Feel free to upstream that patch, as it is right now though I doubt that this patch will work on non-Nix systems, their CMakeLists.txt contains too many |
Description of changes
Merging #194578 caused more issues than I initially anticipated. Upgrades obs-studio and fixes all plugins except obs-hyperion which is not yet compatible.
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes