Skip to content

flatbuffer: 2.0.0 -> 2.0.6#170185

Closed
Lunarequest wants to merge 1 commit intoNixOS:masterfrom
Lunarequest:flatbuffers
Closed

flatbuffer: 2.0.0 -> 2.0.6#170185
Lunarequest wants to merge 1 commit intoNixOS:masterfrom
Lunarequest:flatbuffers

Conversation

@Lunarequest
Copy link
Contributor

@Lunarequest Lunarequest commented Apr 25, 2022

Description of changes

update flatbuffers to 2.0.6: https://github.com/google/flatbuffers/releases/tag/v2.0.6

Things done
  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 22.05 Release Notes (or backporting 21.11 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
    • (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes
  • Fits CONTRIBUTING.md.

@ofborg ofborg bot requested a review from teh April 25, 2022 03:31
@ofborg ofborg bot added 10.rebuild-darwin: 101-500 This PR causes between 101 and 500 packages to rebuild on Darwin. 10.rebuild-linux: 101-500 This PR causes between 101 and 500 packages to rebuild on Linux. labels Apr 25, 2022
@vobloeb
Copy link
Contributor

vobloeb commented Jun 1, 2022

Is it ok just to disable failing tests without investigations why do they fail?

@Lunarequest
Copy link
Contributor Author

Is it ok just to disable failing tests without investigations why do they fail?

they fail in upstreams ci as well.

@Lassulus Lassulus added the 2.status: merge conflict This PR has merge conflicts with the target branch label Jun 24, 2022
@smancill smancill mentioned this pull request Jul 26, 2022
13 tasks
@SuperSandro2000
Copy link
Member

superseded by PR linked in the activity log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge conflict This PR has merge conflicts with the target branch 10.rebuild-darwin: 101-500 This PR causes between 101 and 500 packages to rebuild on Darwin. 10.rebuild-linux: 101-500 This PR causes between 101 and 500 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants