Bug 1838402

Summary:	Cannot install python3-pysnmp from EPEL 8
Product:	[Fedora] Fedora EPEL	Reporter:	Rogue Blue <darren.reed>
Component:	pysnmp	Assignee:	Fabian Affolter <mail>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel8	CC:	aurelien, mail, xavier
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-09-28 18:21:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1888579
Bug Blocks:

Description Rogue Blue 2020-05-21 05:08:48 UTC

Description of problem:
install of python3-pysnmp fails

Version-Release number of selected component (if applicable): 4.4.12-1.el8


How reproducible: Every time.


Steps to Reproduce:
1.yum install python3-pysnmp

Actual results:
Last metadata expiration check: 0:01:39 ago on Thu 21 May 2020 02:52:29 PM AEST.
Error:
 Problem: conflicting requests
  - nothing provides python3.6dist(pysmi) needed by python3-pysnmp-4.4.12-1.el8.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Expected results:


Additional info:

Comment 1 Avram Lubkin 2020-05-29 11:08:54 UTC

How does this relate to python3-pyasn1?

Comment 2 Rogue Blue 2020-05-29 11:54:06 UTC

1) There is no dedicated component for "python3-pysnmp" even thought it is a 1st class RPM
2) python3-pysnmp is a python interface to SNMP. SNMP is all ASN.1 encoded messages sent over the network
3) python3-pyasn1 is a prerequisite for python3-pysnmp.

Comment 3 Avram Lubkin 2020-05-29 12:02:35 UTC

Component names map to repo names, not package names. They are usually close, but not guaranteed. The srpm names also map to repo names, so you can usually find the correct component by running rpm -qi and looking at the "Source RPM" field. I updated the component, so hopefully this should get visibility by the right maintainers.

Comment 4 Fabian Affolter 2024-09-28 18:21:48 UTC

As https://bugzilla.redhat.com/show_bug.cgi?id=1888579 was, I guess that we are fine. At least there were no more complains.