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.

Sign up for GitHub

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

Jump to bottom

kdevelop, kdev-php, kdev-python: 5.3.1 -> 5.3.3 [backport] #65032

Merged
merged 2 commits into from Jul 23, 2019
Merged

kdevelop, kdev-php, kdev-python: 5.3.1 -> 5.3.3 [backport] #65032

merged 2 commits into from Jul 23, 2019

Conversation

aanderse
Copy link
Member

Motivation for this change

Backport of #65012.
Looks like I missed the backport on last update.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • 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 nix-review --run "nix-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.

@aanderse aanderse added the 8.has: port to stable A PR already has a backport to the stable release. label Jul 18, 2019
@aanderse aanderse merged commit 3147750 into NixOS:release-19.03 Jul 23, 2019
@aanderse aanderse deleted the kdevelop branch July 23, 2019 01:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
8.has: port to stable A PR already has a backport to the stable release. 10.rebuild-darwin: 0 10.rebuild-linux: 1-10
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@aanderse