Created attachment 599534 [details]
emerge --info output
Today I updated beets to the most recent version 1.4.9-r1. After the update the web server plugin is not available anymore:
$ beet web
** error loading plugin web:
Traceback (most recent call last):
File "/usr/lib64/python3.6/site-packages/beets/plugins.py", line 273, in load_plugins
namespace = __import__(modname, None, None)
ModuleNotFoundError: No module named 'beetsplug.web'
error: unknown command 'web'
I have the "webserver" flag set in my package.use file:
$ grep beets /etc/portage/package.use/settings
media-sound/beets chromaprint webserver
But despite the above the web plugin is not built:
Sorry, accidentally submitted before finishing the description.
From the build log:
>>> Preparing source in /var/tmp/portage/media-sound/beets-1.4.9-r1/work/beets-1.4.9 ...
* no webserver:
* removing web
(full build log attached)
The web plugin is not built likely because of the following part of profiles/base/package.use.mask:
# Andreas Sturmlechner <email@example.com> (2019-12-07)
# dev-python/flask-cors is PMASKED.
which was introduced by commit ff5418a7b5d.
I think dev-python/flask-cors is only necessary if someone wants to enable CORS in the beets web plugin (it's disabled by default). I'm using beets web plugin without flask-cors on a different machine (running Slackware64-14.2), and it works just fine. Perhaps masking the "webserver" USE flag just because there is a problem with flask-cors goes a bit too far?
Created attachment 599536 [details]
I have been working on this ebuild, I see the use flags was masqued in the profile, can we re enable it ?
I'm not invested in this package.
Maybe I wasn't clear sorry.
(In reply to Andreas Sturmlechner from comment #4)
> I'm not invested in this package.
Yes I understand but I try to upgrade the ebuild and cleanup the issues,
as this one could be solved by unmasking the USE flags in profile,
(masked by unless I am wrong).
My question is how can this flag be unmasked ?
If there's anything I can fix in the ebuild, I can do it.
The bug has been referenced in the following commit(s):
Author: Guillaume Seren <firstname.lastname@example.org>
AuthorDate: 2020-04-25 17:31:10 +0000
Commit: Joonas Niilola <email@example.com>
CommitDate: 2020-06-01 12:28:16 +0000
media-sound/beets: cleanup ebuild
Signed-off-by: Guillaume Seren <firstname.lastname@example.org>
Signed-off-by: Joonas Niilola <email@example.com>
media-sound/beets/beets-1.4.9-r1.ebuild | 179 +++++++++++++++++++-------------
1 file changed, 107 insertions(+), 72 deletions(-)
If it's fixed, please make a PR where you handle the profile masks and point it to close this bug with 'Closes:' tag.
I see this message was written before the commit c9ea4ce3a03267955c2823953eebc31961320670
I am preparing a cleanup commit that will close this bug
Also I will delete this mask in 'profiles/base/package.use.mask',
in my PR.
I have remove the PMASK and add a new usee flag for cors,
because it is disabled by default as stated in the doc see: