Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1787688 - Unable to to run /usr/bin/pylint after dnf update, since astroid requires lazy_object_proxy 1.4.*
Summary: Unable to to run /usr/bin/pylint after dnf update, since astroid requires laz...
Keywords:
Status: CLOSED DUPLICATE of bug 1788084
Alias: None
Product: Fedora
Classification: Fedora
Component: pylint
Version: 31
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-04 07:40 UTC by Joachim Metz
Modified: 2020-01-06 16:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-01-06 16:08:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Joachim Metz 2020-01-04 07:40:00 UTC
Description of problem:

Unable to to run /usr/bin/pylint after dnf update, since astroid requires lazy_object_proxy 1.4.*

Version-Release number of selected component (if applicable):

Name         : pylint
Version      : 2.3.1
Release      : 2.fc31
Architecture : noarch
Size         : 186 k
Source       : pylint-2.3.1-2.fc31.src.rpm
Repository   : @System
From repo    : fedora

Name         : python3-astroid
Version      : 2.3.3
Release      : 2.gitace7b29.fc31
Architecture : noarch
Size         : 1.4 M
Source       : python-astroid-2.3.3-2.gitace7b29.fc31.src.rpm
Repository   : @System
From repo    : updates

Name         : python3-lazy-object-proxy
Version      : 1.3.1
Release      : 10.fc31
Architecture : x86_64
Size         : 93 k
Source       : python-lazy-object-proxy-1.3.1-10.fc31.src.rpm
Repository   : @System
From repo    : fedora


How reproducible:

Very

Steps to Reproduce:
1. dnf update
2. /usr/bin/pylint --version

Actual results:

Traceback see "Additional info" below

Expected results:

Pylint version

Additional info:

pylint --version
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 583, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 900, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 791, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (lazy-object-proxy 1.3.1 (/usr/lib64/python3.7/site-packages), Requirement.parse('lazy_object_proxy==1.4.*'), {'astroid'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/pylint", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3250, in <module>
    @_call_aside
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3234, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 3263, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 585, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 598, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 786, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'lazy_object_proxy==1.4.*' distribution was not found and is required by astroid

Comment 1 Gwyn Ciesla 2020-01-06 16:08:01 UTC

*** This bug has been marked as a duplicate of bug 1788084 ***


Note You need to log in before you can comment on or make changes to this bug.