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
[20.03] inkscape: 0.92.4 → 0.92.5 #86952
Conversation
I am not sure this is okay to backport. The update was minor only in version scheme. cc @worldofpeace |
How to know if this is OK to backport? |
I think this is partly matter of opinion. We are not as strict as e.g. Ubuntu, for example we sometimes allow not-so-minor updates in leaf packages when they are broken (e.g. depend on an online service that changed API), but if the old it might be not worth the risk backporting – it might break users or even other packages. Thankfully, I do not think this release includes the new CLI api that broke everything (#68930) but it still switched from Python 2 to Python 3. As such, it might be potentially breaking for users that have extra Inkscape extensions installed. For that reason, I think it is unsuitable for backporting into a stable release. But maybe you can convince a release manager that the breakage is unlikely and the benefits are super neat. |
The unpackPhase override was only needed when the download server mangled the file extension: NixOS#23652 (cherry picked from commit 38e316d)
Also order the build inputs alphabetically and switch to pname+version. (cherry picked from commit eff936e)
https://gitlab.com/inkscape/inkscape/-/tags/INKSCAPE_0_92_5 (cherry picked from commit a48d86e)
Thanks for the clarification. |
I agree with @jtojnar this isn't suitable for backport, and just because in 20.03 we didn't axe python3 just yet. |
Port of #85184 to 20.03. cc/ @jtojnar
Motivation for this change
Inkscape 0.92.4 depends on python 2
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)