Weird! This is definitely not normal. Any chance something has gone wrong with the beets installation? You can try `pip uninstall`ing beets and installing it again. Also, this seems *very* unlikely, but maybe try temporarily removing your custom `pluginpath` setting?
Adrian > On Jan 28, 2018, at 7:07 AM, Jonathan Thomas <[email protected]> > wrote: > > Installed a new Ubuntu server and installed beets with pip. Setup my config - > https://gist.github.com/jonathanthomas83/9486d94e236d8bb44867664213ddb276 > > And when doing a reimport (beet import -A collection) to setup a new library, > I get the following (same output on 'beet config -p' too): > > beet config -p > ** plugin importadded not found > ** plugin mbsync not found > ** plugin mbcollection not found > ** plugin zero not found > /home/jonathan/.config/beets/config.yaml > > Any ideas what's going on? I never have to do anything with plugins usually, > after an install, they just work! :-/ > > Many thanks, > Jonathan > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
