FS#52482 - [beets] Missing deps on python-mutagen
Attached to Project:
Community Packages
Opened by Bruno Pagani (ArchangeGabriel) - Tuesday, 10 January 2017, 18:34 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 12 January 2017, 04:18 GMT
Opened by Bruno Pagani (ArchangeGabriel) - Tuesday, 10 January 2017, 18:34 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 12 January 2017, 04:18 GMT
|
Details
Without python-mutagen, any beets command results in:
Traceback (most recent call last): File "/usr/bin/beet", line 6, in <module> from pkg_resources import load_entry_point File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3019, in <module> @_call_aside File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3003, in _call_aside f(*args, **kwargs) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3032, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 655, in _build_master ws.require(__requires__) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 963, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python3.6/site-packages/pkg_resources/__init__.py", line 849, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'mutagen>=1.33' distribution was not found and is required by beets |
This task depends upon
Closed by Doug Newgard (Scimmia)
Thursday, 12 January 2017, 04:18 GMT
Reason for closing: Fixed
Additional comments about closing: beets 1.4.3-2
Thursday, 12 January 2017, 04:18 GMT
Reason for closing: Fixed
Additional comments about closing: beets 1.4.3-2
Interestingly, https://www.archlinux.org/packages/community/any/beets/ already lists `python-mutagen` as a dependency. However, `pacman -Si beets` does not.
EDIT: My bad. The website shows package version 1.4.3-2, but my pacman shows 1.4.3-1, which no amount of `pacman -Sy` or even `pacman -Syy` will change. I guess, it hasn't been replicated by my mirror yet? Don't know about the architecture specifics of pacman mirrors ;)
Just refresh & update. ;)
I guess this issue can be marked as fixed then.