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

mavproxy: 1.8.34 -> 1.8.36 #122791

Merged
merged 3 commits into from May 15, 2021
Merged

Conversation

lopsided98
Copy link
Contributor

Motivation for this change

Updates mavproxy to the latest version. I also corrected the licenses for both mavlink and pymavlink (which I had previously mistakenly thought was LGPLv3 only).

I tested loading a log file with MAVExplorer.py.

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.

The README states: "MAVProxy is released under the GNU General Public License v3
or later"
The license file doesn't specify that later versions can be used, but I missed
that it is stated in the README: "pymavlink is released under the GNU Lesser
General Public License v3 or later."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants