-
-
Notifications
You must be signed in to change notification settings - Fork 17.5k
openimageio: 2.5.16.0 -> 3.0.5.0 #401089
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
openimageio: 2.5.16.0 -> 3.0.5.0 #401089
Conversation
bd11bdc to
edbd65f
Compare
amarshall
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! (Comments based on diffs only, have not yet done build testing)
I have a mild preference for the commits to be something like:
- openimageio: move to by-name
- openimageio: 2.5.16.0 -> 2.5.17.0, fix incorrect license
- openimageio: 2.5.17.0 -> 3.0.5.0; openimageio_2: init at 2.5.17.0
With all the necessary changes to dependents in that last one. This is to make bisecting easier—with the current commits in the PR the majority of commits have various drvs (presumably) failing to build.
- v2.5.17.0 was released on Nov 1, 2024, includes bug fixes - openimageio relicense their code under Apache 2.0 AcademySoftwareFoundation/OpenImageIO#3905 - remove unnecessary patch - remove `rec` and `with lib;`
|
@amarshall Thanks for your review! Bisecting makes sense to ensure that each commit builds successfully — I've updated the commits accordingly. There are still a few build failures that I'm working to address. Also, it looks like gpupad has been broken for a while. (#401129) |
|
SuperSandro2000
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
The tag seems to have changed |
Openimageio v3 was released in Nov 9, 2024. However, v3 introduces many breaking changes that some consumers are not yet ready for, and updating them would require complex changes. To address this, we’ve introduced openimageio_2 at version 2.5.17.0. This legacy package is expected to be removed once it is no longer used in nixpkgs.
|
@gador Thanks for your review! The tag itself wasn’t changed. However, a subtle mistake was made when I changed |
|
Openimageio v3 was released in Nov 9, 2024. This PR bumps openimageio from
2.5.16.0to3.0.5.0.However, v3 introduces many breaking changes that some consumers are not yet ready for, and updating them would require complex changes. To address this, we’ve introduced
openimageio_2at version2.5.17.0. This legacy package is expected to be removed once it is no longer used in nixpkgs.Also, openimageio has been relicensed under Apache-2.0
close #363100
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.