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

hyperscan: 5.4 -> 5.4.1 #221028

Closed
wants to merge 0 commits into from
Closed

hyperscan: 5.4 -> 5.4.1 #221028

wants to merge 0 commits into from

Conversation

tbaggaley
Copy link
Contributor

@tbaggaley tbaggaley commented Mar 13, 2023

Description of changes

Upgrades Intel Hyperscan library from 5.4 to 5.4.1.

Changelog

Adds patch from commit intel/hyperscan@0bf86a7 to fix a bug introduced by release 5.4.1 regarding checking validity of scratch space buffers (present only on master). See intel/hyperscan#350.

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.05 Release Notes (or backporting 22.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
  • Fits CONTRIBUTING.md.

@NickCao
Copy link
Member

NickCao commented Apr 24, 2023

The patch is now in 5.4.2: https://github.com/intel/hyperscan/releases/tag/v5.4.2

Copy link
Contributor

@drupol drupol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello,

I would like to proceed with this PR and I see that version 5.4.2 is out.

Do you mind updating your pr ?

@tbaggaley
Copy link
Contributor Author

Thanks @NickCao @drupol - I've upgraded to 5.4.2 in #236604. Could you take a look at merging that one?

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.

3 participants