FS#71299 - [ngrep] does not use pcre due to configure bug

Attached to Project: Community Packages
Opened by loqs (loqs) - Saturday, 19 June 2021, 16:58 GMT
Last edited by Jelle van der Waa (jelly) - Sunday, 03 September 2023, 16:08 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The configure test would always fail due to [1] preventing pcre from being detected and using a bundled regex library instead.
Tested with [2].

Additional info:
* ngrep 1.47-2
[1] https://github.com/jpr5/ngrep/commit/b8b1e9751e1d074af0dd77c2554c1b25fd8f7abe
[2] PKGBUILD.diff

Steps to reproduce:
ldd /usr/bin/ngrep | grep pcre
produces no output
   PKGBUILD.diff (0.6 KiB)
This task depends upon

Closed by  Jelle van der Waa (jelly)
Sunday, 03 September 2023, 16:08 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.47-4
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.
Comment by loqs (loqs) - Tuesday, 08 August 2023, 22:25 GMT
Updated PKGBUILD.diff for change to sha256sums and switch to git.
   PKGBUILD.diff (0.6 KiB)
Comment by loqs (loqs) - Thursday, 31 August 2023, 19:03 GMT
Two alternative solutions as pcre is EOL [1]
Use glibc's regex [2].
Use pcre2 [3]. The upstream PR [4] has not been merged. There have been no upstream commits since January 2019 [5].

[1] https://pcre.org/
[2] PKGBUILD.diff.1
[3] PKGBUILD.diff.2
[4] https://github.com/jpr5/ngrep/pull/27
[5] https://github.com/jpr5/ngrep/commit/2a9603bc67dface9606a658da45e1f5c65170444
   PKGBUILD.diff.1 (0.9 KiB)
   PKGBUILD.diff.2 (10.5 KiB)

Loading...