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

frama-c: 21.0 (Scandium) → 21.1 (Scandium) #91810

Merged
merged 1 commit into from Jul 1, 2020
Merged

frama-c: 21.0 (Scandium) → 21.1 (Scandium) #91810

merged 1 commit into from Jul 1, 2020

Conversation

vbgl
Copy link
Contributor

@vbgl vbgl commented Jun 30, 2020

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.

@ofborg ofborg bot requested review from thoughtpolice and amiddelk June 30, 2020 07:32
@vbgl vbgl changed the title framac: 20.0 (Calcium) → 21.1 (Scandium) framac: 21.0 (Scandium) → 21.1 (Scandium) Jun 30, 2020
@vbgl
Copy link
Contributor Author

vbgl commented Jun 30, 2020

@GrahamcOfBorg build framac

@vbgl vbgl changed the title framac: 21.0 (Scandium) → 21.1 (Scandium) frama-c: 21.0 (Scandium) → 21.1 (Scandium) Jun 30, 2020
@bjornfor bjornfor merged commit 18094db into NixOS:master Jul 1, 2020
@vbgl vbgl deleted the frama-c-21.1 branch July 2, 2020 05:12
@yrashk
Copy link
Contributor

yrashk commented Jul 30, 2020

I have just discovered that Frama-C 21+ in nixpkgs has WP plugin disabled because nixpkg's why3 is too old. Configure process didn't fail but simply disabled WP upon discovering why3's version.

I've addressed this in #94258

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

@thoughtpolice thoughtpolice Awaiting requested review from thoughtpolice

@amiddelk amiddelk Awaiting requested review from amiddelk

Assignees
No one assigned
Labels
8.has: package (update) 10.rebuild-darwin: 1-10 10.rebuild-darwin: 1 10.rebuild-linux: 1-10 10.rebuild-linux: 1
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@vbgl @yrashk @bjornfor