Bug 1242651 - [abrt] s3ql: __init__.py:839:resolve:pkg_resources.DistributionNotFound: The 'dugong>=3.4' distribution was not found and is required by s3ql
Summary: [abrt] s3ql: __init__.py:839:resolve:pkg_resources.DistributionNotFound: The ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: s3ql
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marcel Wysocki
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:42e1d213ebb1afdca218ca79c0f...
Depends On: 1127656
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-13 21:04 UTC by Sten Turpin
Modified: 2015-08-07 13:17 UTC (History)
2 users (show)

Fixed In Version: python3-dugong-3.5-1.fc21
Clone Of:
Environment:
Last Closed: 2015-08-07 12:54:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (2.97 KB, text/plain)
2015-07-13 21:04 UTC, Sten Turpin
no flags Details
File: environ (3.35 KB, text/plain)
2015-07-13 21:04 UTC, Sten Turpin
no flags Details

Description Sten Turpin 2015-07-13 21:04:42 UTC
Description of problem:
Updated to current s3ql on F22, attempted to unmount a mounted s3ql filesystem

Version-Release number of selected component:
s3ql-2.13-1.fc22

Additional info:
reporter:       libreport-2.6.0
cmdline:        /usr/bin/python3 /usr/bin/umount.s3ql /home/sten/.mnt/s3ql/sud0er-s3ql-rdiffbackup1
executable:     /usr/bin/umount.s3ql
kernel:         4.0.7-300.fc22.x86_64
runlevel:       N 5
type:           Python3
uid:            1000

Truncated backtrace:
__init__.py:839:resolve:pkg_resources.DistributionNotFound: The 'dugong>=3.4' distribution was not found and is required by s3ql

Traceback (most recent call last):
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 651, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 952, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 844, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (dugong 3.3 (/usr/lib/python3.4/site-packages), Requirement.parse('dugong>=3.4'), {'s3ql'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/umount.s3ql", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3084, in <module>
    @_call_aside
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3070, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 3097, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 653, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 666, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3.4/site-packages/pkg_resources/__init__.py", line 839, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'dugong>=3.4' distribution was not found and is required by s3ql

Local variables in innermost frame:
req: Requirement.parse('dugong>=3.4')
processed: {Requirement.parse('s3ql==2.13'): True, Requirement.parse('llfuse>=0.39'): True}
new_requirements: []
installer: None
ws: <pkg_resources.WorkingSet object at 0x7f46e2b86c50>
env: <pkg_resources.Environment object at 0x7f46e2b86da0>
best: {'dugong': None, 'llfuse': llfuse 0.40 (/usr/lib64/python3.4/site-packages), 's3ql': s3ql 2.13 (/usr/lib64/python3.4/site-packages)}
replace_conflicting: False
requirements: [Requirement.parse('defusedxml'), Requirement.parse('requests'), Requirement.parse('pycrypto'), Requirement.parse('apsw>=3.7.0')]
required_by: defaultdict(<class 'set'>, {Requirement.parse('pycrypto'): {'s3ql'}, Requirement.parse('defusedxml'): {'s3ql'}, Requirement.parse('llfuse>=0.39'): {'s3ql'}, Requirement.parse('dugong>=3.4'): {'s3ql'}, Requirement.parse('apsw>=3.7.0'): {'s3ql'}, Requirement.parse('requests'): {'s3ql'}})
dist: None
requirers: {'s3ql'}
new_requirement: Requirement.parse('apsw>=3.7.0')
self: <pkg_resources.WorkingSet object at 0x7f46e2b86c50>
to_activate: [s3ql 2.13 (/usr/lib64/python3.4/site-packages), llfuse 0.40 (/usr/lib64/python3.4/site-packages)]

Comment 1 Sten Turpin 2015-07-13 21:04:48 UTC
Created attachment 1051512 [details]
File: backtrace

Comment 2 Sten Turpin 2015-07-13 21:04:49 UTC
Created attachment 1051513 [details]
File: environ

Comment 3 Fedora Update System 2015-07-22 14:39:33 UTC
python3-dugong-3.5-1.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/python3-dugong-3.5-1.fc21

Comment 4 Fedora Update System 2015-07-22 14:40:36 UTC
python3-dugong-3.5-1.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/python3-dugong-3.5-1.fc22

Comment 5 Fedora Update System 2015-07-29 01:42:47 UTC
Package python3-dugong-3.5-1.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing python3-dugong-3.5-1.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-11977/python3-dugong-3.5-1.fc21
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2015-08-07 12:54:02 UTC
python3-dugong-3.5-1.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-08-07 13:17:51 UTC
python3-dugong-3.5-1.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


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