Closed gramster closed 6 years ago
Interesting! It looks like there are two problems:
update
doesn't currently know how to clean up art files when they're deleted. See #2419, #2036, and https://github.com/beetbox/beets/issues/2768#issuecomment-361624969, for example.samefile
). However, that check fails if the file doesn't exist. We should probably add an extra check for path equality (just p1 == p2
) to avoid weird situations like this.Does that sound right? If so, we can quickly fix the second thing, at least.
I think it would be obviously good to fix both things :-) A quick fix of thing 2 would be a good start.
If I turn off art files in the config will beets at least just ignore them? That may be a way to at least get past this and eventually I can use Picard or something to fix the art files.
BTW I had a similar error-out when doing a merge:
Error: No such file or directory while moving /volume1/music/beet/Paul A. Schwartz/Aria 2_ New Horizon/cover.1.jpg to /volume1/music/beet/Paul A. Schwartz/Aria 2_ New Horizon/cover.1.jpg
Very annoying when these things cause beets to exit, because resuming imports doesn't seem to work well and I have to redo a lot of work.
Cool; I pushed a quick fix for the equal-path problem.
If you're interested in the broader problem of file errors that abort operations, please take a look at a few related issues—this has been discussed in some detail (and we could definitely use some help sorting it out).
I still have this exact issue on the latest source build.
The same issue here. I have had it since I started using beets, and it is definitely still there in the last version.
Problem
I'm trying to run "beet update" but it fails, apparently while trying to move a non-existent file onto itself.
Setup
My configuration (output of
beet config
) is: