Skip to content

ngrep: update to 1.49.0. - #60942

Closed
FabioLeitao wants to merge 1 commit into
void-linux:masterfrom
FabioLeitao:ngrep-1.49.0
Closed

FabioLeitao wants to merge 1 commit into
void-linux:masterfrom
FabioLeitao:ngrep-1.49.0

Conversation

@FabioLeitao

@FabioLeitao FabioLeitao commented Jun 6, 2026

Copy link
Copy Markdown
Contributor

Testing the changes - build and install

  • I've built this PR locally.
  • I've tested the changes and everything works as expected (pending reviewer build test on CI)

Summary of changes:

  • Update ngrep from 1.47 → 1.49.0
  • Adopt orphaned package (maintainer was Orphaned <orphan@voidlinux.org>)
  • PCRE1 → PCRE2 migration: upstream dropped --enable-pcre (PCRE1) in 1.49.0; regex backend is now PCRE2 via --enable-pcre2 (or GNU regex by default). This PR enables PCRE2 to preserve the regex capability the old package provided.
    • makedepends: pcre-develpcre2-devel
    • configure_args: removed --enable-pcre EXTRA_LIBS=-lpcre; added --enable-pcre2
  • Tag scheme change: upstream changed tag format from V1_47 (uppercase, underscores) to v1.49.0 (lowercase, semver); updated distfiles URL accordingly
  • --with-pcap-includes fix: configure.ac changed BASE_PCAP_H from pcap.h to pcap/pcap.h in 1.49.0; the old /usr/include/pcap path would have caused CI failure (could not find a complete set of pcap headers). Native build now uses configure's default search (finds /usr/include); cross-build points to $XBPS_CROSS_BASE/usr/include.

Built and installed on Void Linux x86_64 (musl); ngrep -VV1.49.0, libpcap version 1.10.6.

@Duncaen Duncaen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please do not adopt the package yet.

@FabioLeitao

Copy link
Copy Markdown
Contributor Author

Understood, thank you. Removed the adoption — will focus on establishing track record first. Less is more here.

@FabioLeitao

FabioLeitao commented Jul 12, 2026

Copy link
Copy Markdown
Contributor Author

Not quiet, I have used AI assistance as a research tool in my kit to gather similar dangling easy issues that I knew how to handle and assist, not to co-author anything or to hallucinate, giving back to the community specifically in packages I do need and use a lot, mostly security adjacent... The solution it self was developed by me, built and tested locally, I had been myself audited by my AI Augmented Engineering agent with Human in the Loop (me) closely guarded by my ADRs, guidelines and guardrails, as far as vibe coding and hype as possible. Please check my personal repo/projects to understand my rigor and craft if you feel is necessary.

@FabioLeitao

Copy link
Copy Markdown
Contributor Author

Signed by @FabioLeitao - genuine humand report (HITL confirm), not an AI bot 2026-07-12 - ngrep - void-linux - void-packaged #60942

-----BEGIN SSH SIGNATURE-----
U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgHSwaWVCd3rALjtmwINNtVKRX3t
ucF7TfXNZFALyRo4EAAAAEZmlsZQAAAAAAAAAGc2hhNTEyAAAAUwAAAAtzc2gtZWQyNTUx
OQAAAEDo7VjZTyXIbgisnX5oEoXvFMeAwGFNeXmubGG/ssFJqtobOIQu8tYFDXeSACf/0Q
C3VAd24vQ7h1F6gzj1eDEJ
-----END SSH SIGNATURE-----

@FabioLeitao

Copy link
Copy Markdown
Contributor Author

Understood — thanks for the review. I’m happy to keep this scoped to just the version bump (ngrep 1.45 → 1.49.0) and drop the maintainer/adopt change; the update is useful on its own regardless of adoption. Would you prefer I resubmit as an update-only PR, or is there anything in the bump itself (distfiles/checksums, build) you’d like adjusted? No rush on the adoption — I mainly want the package current.

@Duncaen

Duncaen commented Jul 27, 2026

Copy link
Copy Markdown
Member

Was updated in #61336.

@Duncaen Duncaen closed this Jul 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants