File exists during link of paths using symlink mode about beets-alternatives

[wisp3rwind]

Hi! Your report is rather sparse in details on your setup, could you provide versions for beets and beets-alternatives? The full configuration file might also be useful.

Is it correct that the steps to reproduce are:

1. Modify some data (e.g. beet mod <query> parentwork=foobar)
2. beet alt update works

Maybe you could try whether such a small modification (using beet mod) of the metadata (which shouldn't have any other side effects) is sufficient to trigger the issue?

In any case, you could well be right that symlink mode isn't in perfect shape: It is covered by our testsuite, but at least I personally have never used it, and I think most posts on this issue tracker are also about the "external files" mode.

[aereaux]

Thanks for the quick response! Yeah, sorry, I wasn't entirely sure what all to include in the report.

Versions of packages:
beets-git 1.4.9.r1031.gcbc045f1-1
beets-alternatives 0.10.1-1.1

I noticed that I wasn't using the latest version of this package, which looks like it includes a fix for symlink problems like the ones I've been having. I'll try to see if that fixes it.

[wisp3rwind]

This might also be related to #49 if you removed those items from the library and then added them again (doing a re-import would probably have the same effect).

[aereaux]

Thanks, but I don't think it's that, I haven't removed items from my library in a long time.

[daviddavo]

I have the same problem, but I think it's because of my syncing setup. I think the easiest solution would be to add a --force or --replace option that replaces the file if it exists