View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0017408||CentOS-8||net-snmp||public||2020-05-27 17:06||2020-10-07 15:47|
|Summary||0017408: Missing net-snmp-perl package in any repo although it's included in the net-snmp SRPM|
|Description||The net-snmp-perl isn't in any of the CentOS 8 repositories, although if one gets the SRPM from http://vault.centos.org/8.1.1911/BaseOS/Source/SPackages/net-snmp-5.8-12.el8_1.src.rpm and rebuilds it, the package is generated.|
Note: *please* do not confuse net-snmp-perl with perl-Net-SNMP, they are *not* the same thing. There are several scripts (mainly 3rd party nagios plugins) that require the former, hence this is being an issue when trying to migrate monitoring servers to CentOS 8.
This problem didn't occur in previous CentOS releases.
It's being included in the build as can be seen for instance in https://koji.mbox.centos.org/koji/buildinfo?buildID=6424
Is there any reason why net-snmp-perl isn't on the repos? (I've looked for more info but without success on finding any)
Or is it really a bug (like missing tagging somewhere and it's not published), and if so can it be fixed so the missing package is published?
|Steps To Reproduce||Try to install and fails:|
# dnf install --refresh net-snmp-perl
Failed to set locale, defaulting to C.UTF-8
CentOS-8 - AppStream 21 kB/s | 4.3 kB 00:00
CentOS-8 - Base 20 kB/s | 3.9 kB 00:00
CentOS-8 - Extras 8.0 kB/s | 1.5 kB 00:00
CentOS-8 - PowerTools 12 kB/s | 4.3 kB 00:00
CentOS-8 - Plus 2.5 MB/s | 1.1 MB 00:00
No match for argument: net-snmp-perl
Error: Unable to find a match: net-snmp-perl
|Tags||8.1.1911, 8.2.2004, bug, net-snmp, net-snmp-perl|
New net-snmp release came out, problem still persists, even worse because src package is currently nowhere to be found so one can't build the missing net-snmp-package.
Any news on this? Or is there any valid reason for the (already produced package when the build is made) not to be published in the CentOS repos that I'm missing?
This is quite frustrating...
And it's extremely odd that no one else is having issues, as it is extremely odd that no one cared to reply to this issue. Is there so many little sys admins out there that need net.-snmp-perl or just don't bother to update their Centos 8 systems? Or is still everyone using CentOS 7 (even though 8 came out almost 1 year ago already) and using CentOS 8 in production is just a crass mistake?
To anyone interested, found the SRPM here: http://vault.centos.org/8.2.2004/BaseOS/Source/SPackages/net-snmp-5.8-14.el8_2.1.src.rpm
Just rebuilt it and confirm that it still produces thenet-snmp-perl-5.8-14 rpm with no problems, but that rpm still isn't published on the CentOS 8 repositories (hence the bug report, which seems to be a deployment issue on the CentOS 8 build system). So, is there any hope that is fixed for this and future releases?
This also affects me - and probably everyone else who tries to use CentOS8 as a monitoring platform.
Can please someone look into and address this?
It's quite cumbersome do have to manually track and build and publish a rpm every time a new version is released.
As the reporter said, this did not happen on previous CentOS releases so this should be look at as a regression.
First off .. all packages built for CentOS Linux 8 come from git. If we built it, you can get the src from here:
and using the get_sources,sh and / or into_srpm.sh scripts from here:
Also .. the latest SRPM should be here:
The next step is to see if that package is in RHEL 8.2 .. if it is not, it will also not be in CentOS. Being produced but excluded from RHEL will also mean exclded from CentOS for CentOS Linux 8.
If you look here:
It is not in RHEL-8.
From comments here, it should be in RHEL-8.3, so it should be in CentOS-8.3:
It is currently available in CentOS Stream here:
This should work fine on CentOS 8.2 if you download it and install it, or you could move to stream if that is more appropriate.
Many thanks guys for the enlightenment. Let's hope RedHat doesn't mess up in RHEL 8.3 then :)
Hopefully they won't publish any newer net-snmp releases until then, but we'll use the mentioned workarounds in the meanwhile.
Perhaps this can be marked as solved? (I'm not finding any option to do it)
|2020-05-27 17:06||araujorm||New Issue|
|2020-05-27 17:06||araujorm||Tag Attached: net-snmp-perl|
|2020-09-16 09:59||araujorm||Note Added: 0037699|
|2020-09-16 13:16||araujorm||Note Added: 0037700|
|2020-09-16 13:16||araujorm||Tag Attached: net-snmp|
|2020-09-16 13:17||araujorm||Tag Attached: bug|
|2020-09-16 13:18||araujorm||Tag Attached: 8.1.1911|
|2020-09-16 13:18||araujorm||Tag Attached: 8.2.2004|
|2020-10-01 14:54||mindo||Note Added: 0037768|
|2020-10-06 19:18||JohnnyHughes||Note Added: 0037788|
|2020-10-06 19:20||JohnnyHughes||Note Edited: 0037788|
|2020-10-06 19:23||JohnnyHughes||Note Added: 0037789|
|2020-10-07 15:16||rcgreenw||Note Added: 0037794|
|2020-10-07 15:47||araujorm||Note Added: 0037796|