The thing that would help would be steps to reproduce, from scratch, starting 
with an empty database and an empty beets configuration.




Adrian
> On Nov 16, 2017, at 11:45 AM, Bearcat Şándor <[email protected]> wrote:
> 
> This happens with *almost* every move operation. 
> 
> What would you need from me to help? A stack trace, my database? 
> 
> -- 
> Bearcat M. Şándor
> Feline Soul Systems LLC
> Voice: 872.CAT.SOUL (872.228.7685)
> Fax: 406.235.7070
> 
>> On Nov 15, 2017 19:57, "Adrian Sampson" <[email protected]> wrote:
>> Hmm; it’s hard to say without being able to reproduce the state of your 
>> library from scratch. Somehow, beets previously thought the file was at 
>> `cover.1.jpg`. Then, the file got renamed to `cover.jpg`, but the path in 
>> beets’s database still points to the old name. We’d need to do some more 
>> digging to understand how that happened.
>> 
>>> On Nov 15, 2017, at 5:05 PM, Bearcat Şándor <[email protected]> wrote:
>>> 
>>> This is a long-standing issue that i'm having.  I have a cover.jpg in each 
>>> directory. When beets moves the file into a new directory it seems to 
>>> rename it as cover.1.jpg and then it can't find that file and craps out.  
>>> If it does manage to move the file it still renames all graphics in my 
>>> artwork directory as disk.1.jpg where the original was disk.jpg.  When it 
>>> does crap out, i end up with the files half moved, beets half updated and a 
>>> very confused system. I then have to move the files back to the original 
>>> directory.  Why is it trying to move the graphics before the music files 
>>> are updated anyway?
>>> 
>>> Here's an example:
>>> 
>>> moonwind@jaguarundi 2016-clearview % ls                                     
>>>                                 14:47:37  
>>> 01-01-drama_for_life.wv   01-04-once_upon_a_playground_rainy.wv  
>>> 01-07-center_stage.wv   01-10-moonlight_kissed.wv  
>>> 01-02-the_game.wv         01-05-children_of_the_sun.wv           
>>> 01-08-the_labyrinth.wv  cover.jpg                  
>>> 01-03-the_child_in_me.wv  01-06-shadow_play.wv                   
>>> 01-09-crystalline.wv                               
>>> moonwind@jaguarundi 2016-clearview % beet update ./                         
>>>                                 14:47:41  
>>> Poets of the Fall - 2016 - Clearview - The Child in Me - 3:51               
>>>                                         
>>>   encoder:  -> WavPack 5.1.0                                                
>>>                                         
>>>   bitrate: 940kbps -> 932kbps                                               
>>>                                           
>>> Poets of the Fall - 2016 - Clearview - Once Upon a Playground Rainy - 3:36  
>>>                                           
>>>   rg_track_gain: -7.3 -> -7.3                                               
>>>                                         
>>>   encoder:  -> WavPack 5.1.0                                                
>>>                                         
>>>   bitrate: 926kbps -> 912kbps                                               
>>>                                           
>>> Error: No such file or directory while moving 
>>> /home/hometheater/audio/poets_of_the_fall/2016-clearview/cover.jpg to 
>>> /home/hometheater/audio/poets_of_the_fall/2016-clearview_[]/cover.1.jpg  
>>> 
>>> 
>>> (in this case the text between the brackets is supposed to be the 
>>> catalognumber but it's missing from this listing for some reason. That's 
>>> not beet's problem)
>>> 
>>> Why is it looking for files that have a .1. appended to the basename? Why 
>>> isn't it just moving cover.jpg to the new target directory. The directory 
>>> doesn't exist, so there is no need to append the .1 to prevent a duplicate. 
>>> Even if there were a duplicate i should have the option of an overwrite.
>>> 
>>> Is this because i have 
>>> 
>>> import:
>>>     move: yes
>>>     incremental: yes
>>> 
>>> 
>>> in my config?
>>> 
>>> My full config is here (with passwords masked out): 
>>> https://gist.github.com/bearcatsandor/680ddabbf23543e7e39f71536bee4738  
>>> 
>>> Thank you!
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "beets" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "beets" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beets-users/2oOPyv9pef0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected].
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "beets" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"beets" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to