Summary: | net-analyzer/mbrowse-0.4.3-r1 : configure: error: SNMP checks failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Netmon project <netmon> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | axiator, chain, mlspamcb, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 506276 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 logs.tbz2 net-analyzer:mbrowse-0.4.3-r1:20190317-065425.log temp.tbz2 |
Description
Toralf Förster
2019-03-17 10:01:39 UTC
Created attachment 569448 [details]
emerge-info.txt
Created attachment 569450 [details]
emerge-history.txt
Created attachment 569452 [details]
environment
Created attachment 569454 [details]
etc.portage.tbz2
Created attachment 569456 [details]
logs.tbz2
Created attachment 569458 [details]
net-analyzer:mbrowse-0.4.3-r1:20190317-065425.log
Created attachment 569460 [details]
temp.tbz2
*** Bug 688028 has been marked as a duplicate of this bug. *** The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8fa1939e9863520bc28af945c9e0a1414ab4c2bb commit 8fa1939e9863520bc28af945c9e0a1414ab4c2bb Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-06-20 08:01:05 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-06-20 08:01:46 +0000 net-analyzer/mbrowse: Specify SNMP LIBDIR in configure call Package-Manager: Portage-2.3.67, Repoman-2.3.14 Bug: https://bugs.gentoo.org/680686 Signed-off-by: Jeroen Roovers <jer@gentoo.org> net-analyzer/mbrowse/mbrowse-0.4.3-r1.ebuild | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) Somehow this exact same problem just returned with the lastest SNMP update. Does anybody know more about it? I can provide logs, but it's exactly the same issue all over again. (In reply to Richard H. from comment #10) > Somehow this exact same problem just returned with the lastest SNMP update. > Does anybody know more about it? I can provide logs, but it's exactly the > same issue all over again. I think logs would help to figure out what component is outdated or what else is going on. |