Skip to content
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

Closed
wants to merge 3 commits into from
Closed

Conversation

@vbgl
Copy link
Contributor

vbgl commented May 5, 2020

Port of #85184 to 20.03. cc/ @jtojnar

Motivation for this change

Inkscape 0.92.4 depends on python 2

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
@jtojnar
Copy link
Contributor

jtojnar commented May 5, 2020

I am not sure this is okay to backport. The update was minor only in version scheme. cc @worldofpeace

@vbgl
Copy link
Contributor Author

vbgl commented May 12, 2020

How to know if this is OK to backport?

@jtojnar
Copy link
Contributor

jtojnar commented May 13, 2020

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.

jtojnar added 3 commits Apr 13, 2020
The unpackPhase override was only needed when the download server mangled the file extension:

#23652
(cherry picked from commit 38e316d)
Also order the build inputs alphabetically and switch to pname+version.

(cherry picked from commit eff936e)
@vbgl vbgl force-pushed the vbgl:inkscape-0.92.5 branch from b5557d1 to 2a46312 May 13, 2020
@vbgl
Copy link
Contributor Author

vbgl commented May 13, 2020

Thanks for the clarification.

@worldofpeace
Copy link
Member

worldofpeace commented Jun 18, 2020

I agree with @jtojnar this isn't suitable for backport, and just because in 20.03 we didn't axe python3 just yet.

@vbgl vbgl closed this Jun 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

4 participants
You can’t perform that action at this time.