Bug 2346083 - Please branch and build netsniff-ng in epel10
Summary: Please branch and build netsniff-ng in epel10
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: netsniff-ng
Version: epel10
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2346084
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-02-17 09:22 UTC by Hangbin Liu
Modified: 2025-03-19 02:25 UTC (History)
3 users (show)

Fixed In Version: netsniff-ng-0.6.9-2.el10_1
Clone Of:
Environment:
Last Closed: 2025-03-19 02:25:20 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Hangbin Liu 2025-02-17 09:22:00 UTC 
Hi, would you please branch and build netsniff-ng in epel10. This tool(including mausezahn) is importent for networking tests.
Comment 1 Hangbin Liu 2025-02-17 09:23:37 UTC 
I saw there are some depends to build netsniff-ng which are also no in epel10 yet. Should I also open bugs for those components?
Comment 2 Hangbin Liu 2025-02-17 09:36:20 UTC 
I checked the list, looks we only need enable libcli on epel10.
Comment 3 Fedora Update System 2025-03-10 18:30:36 UTC 
FEDORA-EPEL-2025-f3340aba13 (netsniff-ng-0.6.9-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f3340aba13
Comment 4 Fedora Update System 2025-03-11 02:26:36 UTC 
FEDORA-EPEL-2025-f3340aba13 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f3340aba13

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 5 Fedora Update System 2025-03-19 02:25:20 UTC 
FEDORA-EPEL-2025-f3340aba13 (netsniff-ng-0.6.9-2.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.