I have to admit that I did very poor testing in d7307d8 and didn't
notice that the "badfiles" plugin relies on mp3val (thanks to @devhell
for packaging in 6e1ef13) and flac to be actually useful.
We now patch in the store locations of these binaries and make
"badfiles" an optional dependency (though enabled by default).
Now, I have tested "beet bad" on my whole music collection and it worked
fine (well, it has found errors... but that's what it is for).
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
We have a mirror:// URL for sourceforge stuff so we can still retreive
the source tarball even if downloads.sourceforge.net is down.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This adds mp3val, which in turn is needed for the beets "badfiles"
plugin.
Thanks a lot to @devhell for packaging.
Built and tested locally by myself as well.
Unfortunately I lost the exact failure, but it was something starting
with 'No rule to make target: ...', which suggests missing dependencies
between generated source files.
Introduces a new plugin called "badfiles", which helps to scan for
corruption within the music collection. I've added this to
pluginsWithoutDeps and sorted the list.
Full upstream changelog can be found here:
https://github.com/sampsyo/beets/releases/tag/v1.3.15
This fixes#10376 via sampsyo/beets@225ba28.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Regression introduced by b21fd5d066.
The initialScript is only executed whenever there is a .first-startup in
the dataDir, so silently dropping the file essentially breaks
initialScript functionality.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
command : 076a2ad -> 91ca5ec
cache : new
exponential-backoff: new
extractor : new
open-golang : new
pretty-words : new
meddler : new
Update drive and bump/add dependencies
Now we always enable large file support, as it should be cheap enough,
and avoids also problems on some filesystems #10181.
The minimal build disables (almost) all options, so it was building
without large file support. However, in musl the `off_t` is *always*
64-bit, which lead to problems, now detected during build time.
