Bug 2301768 - rust-ripgrep: FTBFS in EPEL 9 NEXT
Summary: rust-ripgrep: FTBFS in EPEL 9 NEXT
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: rust-ripgrep
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabio Valentini
QA Contact:
URL: https://koschei.fedoraproject.org/pac...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-30 18:38 UTC by Josh Stone
Modified: 2024-08-30 13:23 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-08-30 13:22:32 UTC
Type: Bug
Embargoed:
jistone: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github BurntSushi rust-pcre2 issues 42 0 None open `MatchData::find`'s `EMPTY` may still be dangling 2024-07-30 18:45:35 UTC
Red Hat Issue Tracker FC-1268 0 None None None 2024-07-30 21:13:32 UTC
Red Hat Issue Tracker FC-1269 0 None None None 2024-08-30 13:23:11 UTC

Description Josh Stone 2024-07-30 18:38:57 UTC
Description of problem:
Package rust-ripgrep fails to build from source in EPEL 9 NEXT.

Version-Release number of selected component (if applicable):
14.1.0-3.el9

Steps to Reproduce:
koji build --scratch epel9-next rust-ripgrep-14.1.0-3.el9.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/rust-ripgrep

Comment 1 Josh Stone 2024-07-30 18:43:13 UTC
I found that since Rust 1.79 (https://github.com/rust-lang/rust/pull/123936), there's an EMPTY constant in rust-pcre2 that's now a dangling pointer, even though it was trying to avoid that: https://github.com/BurntSushi/rust-pcre2/issues/42

But even still, the underlying pcre2 shouldn't be reading that pointer at all when the length is 0. The same `rg` test binary does work when copied to Fedora, which has newer pcre2, so I'm guessing there was also some fix there since RHEL 9's pcre2 10.40.

Comment 2 Fabio Valentini 2024-08-30 13:22:32 UTC
Worked around by the updated pcre2 bindings.


Note You need to log in before you can comment on or make changes to this bug.