Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with library directory operations #12933

Closed
ronso0 opened this issue Mar 7, 2024 · 1 comment
Closed

Issue with library directory operations #12933

ronso0 opened this issue Mar 7, 2024 · 1 comment

Comments

@ronso0
Copy link
Member

ronso0 commented Mar 7, 2024

This is a meta issue collecting some issues with regular (expectable) directory operations as well as cross-OS library migration (I tested Windows <--> Linux, currently neither direction works).

  1. Can not remove missing directory (e.g. unmounted drives)
    Fixed by (fix) relink directory / migrate Linux/macOS <--> Windows #12878

  2. Can not add a new directory if one of the current directories is missing because it is tested whether the new dir is a child of one the current dirs.
    -> this is hard to fix (or rather it's easy to fix by reverting from mixxx::FileInfo back to QString, but that is obviously suboptimal)
    Well, fixed by (fix) Library: allow adding new dirs while we have missing watched dir(s) #12937

  3. Relinking music directories set on a Linux machine to Windows paths or vice versa is not working, it just fails silently, see Relink music Directory from Linux to Windows fails #12715 (probably also the other way around)
    Fixed by (fix) relink directory / migrate Linux/macOS <--> Windows #12878

  4. Starting on Linux with Windows music paths causes debug assertion hits (presumably during cover art lookup, relevant only for debug builds

@ronso0 ronso0 added the bug label Mar 7, 2024
@ronso0 ronso0 changed the title Library migration Linux -> Windows not working at all Issue with library directory operations Mar 7, 2024
@ronso0
Copy link
Member Author

ronso0 commented Aug 6, 2024

Closing this now that 1 -3 have been fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant