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

uhdm, surelog 1.83 -> 1.84-unstable-2024-11-07 #354369

Closed

Conversation

hzeller
Copy link
Contributor

@hzeller hzeller commented Nov 8, 2024

Update both, UHDM and Surelog (that are somewhat version-locked) to 1.84 and their respective latest unstable upstream git hashes.

Two separate commits.

Replaces #332963

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • 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/)
  • 24.11 Release Notes (or backporting 23.11 and 24.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.

Add a 👍 reaction to pull requests you find important.

@hzeller hzeller mentioned this pull request Nov 8, 2024
13 tasks
@hzeller
Copy link
Contributor Author

hzeller commented Nov 8, 2024

Also adding myself as maintainer as discussed in #311846 (comment)

@hzeller
Copy link
Contributor Author

hzeller commented Nov 8, 2024

It is unclear to me what the ofborg-eval issue is in the CI.

@ofborg build

@wegank wegank added the 2.status: merge conflict This PR has merge conflicts with the target branch label Nov 10, 2024
@hzeller
Copy link
Contributor Author

hzeller commented Nov 10, 2024

Looks like this PR got caught in the middle of projects being moved to pkgs/by-name/ hence the merge conflict.
Will open a separate one.

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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants