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

segger-jlink: 766 -> 792b #252137

Closed
wants to merge 1 commit into from
Closed

Conversation

MGlolenstine
Copy link
Member

Description of changes

Version bump.
Tested for flashing of a local project, which works.

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/)
  • 23.11 Release Notes (or backporting 23.05 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
  • Fits CONTRIBUTING.md.

@matthiasbeyer
Copy link
Contributor

Result of nixpkgs-review pr 252137 run on x86_64-linux 1

@MGlolenstine
Copy link
Member Author

I updated it to 792b, two versions newer than 792.
I thought b denoted a beta build, but it doesn't, as previous versions seem to go up to n.

@MGlolenstine MGlolenstine changed the title segger-jlink: 766 -> 792 segger-jlink: 766 -> 792b Aug 30, 2023
@matthiasbeyer
Copy link
Contributor

Result of nixpkgs-review pr 252137 run on x86_64-linux 1

@matthiasbeyer
Copy link
Contributor

I don't know why the review does not build the package... 🤔

@MGlolenstine
Copy link
Member Author

MGlolenstine commented Aug 30, 2023

That is weird, it was also reported in the previous PR #244637.
Could it be due to the license requirements?

@MatthewCroughan MatthewCroughan mentioned this pull request Sep 9, 2023
12 tasks
@pinpox
Copy link
Member

pinpox commented Oct 26, 2023

I think this is superseded by #255185

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

4 participants