[Bug 213806] www/mitmproxy is broken request upgrading to 0.17

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Oct 26 13:12:33 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213806

            Bug ID: 213806
           Summary: www/mitmproxy is broken request upgrading to 0.17
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs at FreeBSD.org
          Reporter: p5B2E9A8F at t-online.de
                CC: gaod at hychen.org
                CC: gaod at hychen.org
             Flags: maintainer-feedback?(gaod at hychen.org)

# mitmproxy
Traceback (most recent call last):
  File "/usr/local/bin/mitmproxy", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
2991, in <module>
    @_call_aside
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
2977, in _call_aside
    f(*args, **kwargs)
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
3004, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
664, in _build_master
    return cls._build_from_requirements(__requires__)
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
677, in _build_from_requirements
    dists = ws.resolve(reqs, Environment())
  File "/usr/local/lib/python2.7/site-packages/pkg_resources/__init__.py", line
856, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'lxml==3.4.4' distribution was not
found and is required by mitmproxy

This problem is fixed in mitmproxy version 0.17
for reference see https://trac.macports.org/ticket/51562

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list