I use a computer at home, and one while I am traveling. Both have the same collection of songs (500+ GB) After a trip abroad, I would synch up my home computer to the laptop, and when traveling, I would synch up the laptop to the home system. All my settings and data are transferred between the machines. They have exactly the same directory structure and contents, but Amarok insists on rescanning the entire collection whenever I change computers. I suspect that this is because of the HDD ID changing from it's point of view. Is there a way that I can avoid it rescanning the entire collection? This takes many hours to complete for each user on the system. Reproducible: Always Steps to Reproduce: 1. rsync entire computer 1 with computer 2 2. open amarok 3. collection now shows empty, (0 tracks) and needs re-scanning Actual Results: Amarok forgets the path to where the collection is. Expected Results: Amarok should remember where the collection is, and not need a re-scan just because the disk that the collection is on changed ID I am aware that this is not the usual use case, but I would very much like an option where I can tell Amarok to ignore disk ID's
Just for clarification: what exact arguments do you use for rsync? I don't think the hard disk ID is to blame, but that rsync is probably changing the track IDs, as all tracks have individual IDs in the database.
The command used is rsync -av --delete This ensures that the files are identical, even down to all the attributes. Just to be clear, the /data directory where the music resides, and the /home directory are duplicated, but not / Thanks for the quick response. -Evert-
Thank you for the fast feedback.
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!