Bug 274095 - net/ntopng: Version mismatch between ntop-ntopng and ntop-ntopng-dist distfiles
Summary: net/ntopng: Version mismatch between ntop-ntopng and ntop-ntopng-dist distfiles
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Guido Falsi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-26 03:51 UTC by Doug White
Modified: 2023-09-26 10:01 UTC (History)
0 users

See Also:
madpilot: maintainer-feedback+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Doug White 2023-09-26 03:51:38 UTC 
The ntopng port is pulling the ntop-ntopng-dist distfile from the wrong branch. This breaks the Flows -> Analysis table and all charts in the web UI. 

ntop-ntopng-dist should be coming from the 5.6-stable branch in that repository. The current short commit hash is e7a0d8b.
Comment 1 Guido Falsi freebsd_committer freebsd_triage 2023-09-26 07:23:09 UTC 
Hi!

Thanks for reporting this.

Most probably I got distracted in the last update and grabbed the wrong commit.

Going to fix this shortly.
Comment 2 commit-hook freebsd_committer freebsd_triage 2023-09-26 10:01:17 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=2a3ecf3e019da5b366a85a4002319a6be6a8476f

commit 2a3ecf3e019da5b366a85a4002319a6be6a8476f
Author:     Guido Falsi <madpilot@FreeBSD.org>
AuthorDate: 2023-09-26 09:59:25 +0000
Commit:     Guido Falsi <madpilot@FreeBSD.org>
CommitDate: 2023-09-26 09:59:25 +0000

    net/ntopng: Update, use correct distribution file

    PR:             274095

 net/ntopng/Makefile |  6 +++---
 net/ntopng/distinfo | 10 +++++-----
 2 files changed, 8 insertions(+), 8 deletions(-)
Comment 3 Guido Falsi freebsd_committer freebsd_triage 2023-09-26 10:01:57 UTC 
Committed update, including pointing to the correct upstream revision.

Thanks again for reporting the issue!