Bug 432926 – net-analyzer/net-snmp-5.7.2_rc1 should not be requiring pciutils

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description SpanKY 2012-08-27 04:35:52 UTC]

net-snmp works just fine on systems w/out pci, and all the code in net-snmp is conditional upon pci being available, so hard depending on the package is wrong

[Comment 1 Diego Elio Pettenò (RETIRED) 2012-08-27 04:40:51 UTC]

If you have a patch that'll help — otherwise it'll have to wait till tomorrow and I'll make it USE-conditional.

[Comment 2 SpanKY 2012-08-27 04:48:50 UTC]

i didn't write a patch for configure, but it should be easy to utilize the autoconf cache variables ala (untested):
  export ac_cv_header_pci_pci_h=$(usex pci)
  export netsnmp_cv_func_pci_lookup_name_LMIBLIBS=$(usex pci)

[Comment 3 Diego Elio Pettenò (RETIRED) 2012-08-27 05:07:45 UTC]

Yes I meant a patch to the ebuild. Will do that tomorrow, no problem.

[Comment 4 Diego Elio Pettenò (RETIRED) 2012-08-27 15:29:53 UTC]

Fixed in 5.7.2_rc1-r1 (since some arches already marked -r0 stable).

[Comment 5 SpanKY 2012-08-27 20:47:45 UTC]

thanks, latest one seems to work nicely

[Comment 6 Jeroen Roovers (RETIRED) 2012-09-24 11:00:29 UTC]

*** Bug 436078 has been marked as a duplicate of this bug. ***

[Comment 7 Luca Lesinigo 2012-10-08 13:52:25 UTC]

I don't know if this bug should be reopened or a new one filed or nothing at all, but please note that with the recent removal of net-analyzer/net-snmp-5.7.2_rc1-r1 the stable version once again is 5.7.2_rc1 thus bringing back the problem on PCI-less systems, after an emerge -u world the snmpd service isn't able to start.

[Comment 8 Diego Elio Pettenò (RETIRED) 2012-10-08 14:49:11 UTC]

Doesn't have to be reopened. -r1 was never stable to begin with, if you used package.accept_keywords just fix it on your side.

[Comment 9 Diego Elio Pettenò (RETIRED) 2012-10-24 17:44:49 UTC]

*** Bug 439534 has been marked as a duplicate of this bug. ***

[Comment 10 edoceo 2012-10-25 20:43:17 UTC]

This doesn't appear to be fixed.

I've recently synced, /usr/portage/net-analyzer/net-snmp/net-snmp-5.7.2_rc1.ebuild

Is shown as stable:
KEYWORDS="alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86"

But it still forces usage of pciutils

COMMON="ssl? ( >=dev-libs/openssl-0.9.6d )
        tcpd? ( >=sys-apps/tcp-wrappers-7.6 )
        rpm? (
                app-arch/rpm
                dev-libs/popt
        )
        bzip2? ( app-arch/bzip2 )
        zlib? ( >=sys-libs/zlib-1.1.4 )
        elf? ( dev-libs/elfutils )
        python? ( dev-python/setuptools )
        sys-apps/pciutils
        lm_sensors? ( sys-apps/lm_sensors )"

[Comment 11 Sergey Popov 2012-10-26 06:47:24 UTC]

(In reply to comment #10)
> This doesn't appear to be fixed.
> 
> I've recently synced,
> /usr/portage/net-analyzer/net-snmp/net-snmp-5.7.2_rc1.ebuild

net-snmp-5.7.2 (release, not release candidate) is in tree since Oct 20. Does this reproduced with it?

[Comment 12 edoceo 2012-10-29 07:31:39 UTC]

If using just 5.7.2 (which is currently unstable) the PCI use flag is respected. Building with USE="-pci" succeeds and snmpd behaves as expected.  If security issues are fixed I'd really like it tagged stable.

[Comment 13 Sergey Popov 2012-10-29 07:45:12 UTC]

(In reply to comment #12)
> If security issues are fixed I'd really like it tagged stable.

Unfortunately, this version can not be stabilized yet and all security issues in our bugzilla are related to versions <5.7.2_rc1, so fast stabilization is not an option. Maybe optional USE="pci" can be applied to _rc1?

[Comment 14 Diego Elio Pettenò (RETIRED) 2012-10-29 16:19:39 UTC]

Nobody's going to touch the stable ebuild. For the few people needing the pciless version of this, just use ~arch version until this is marked stable (which is going to happen next month anyawy).