Re: [beets] cover1.jpg not found and halting updates and imports

Sat, 03 Dec 2016 08:29:25 -0800 

Sorry about that; I’ve not had time to do a full reproduction.

In the mean time, the best thing you can do to help is probably to do a 
step-by-step investigation yourself and post it on GitHub. Something like this:
1. Strip your config down to the bare essentials to make sure nothing else is 
interfering.
2. Start from a temporary empty library database and music directory.
3. Run (and record!) all the commands you need to reproduce the problem from 
scratch.
4. Note the `ls -R` output that shows when offending files show up and 
disappear, and when the error message eventually appear.

Does that sound doable?

Adrian


> On Dec 2, 2016, at 7:05 PM, Bearcat Şándor <[email protected]> wrote:
> 
> I'm just wondering if there is something i can do to help this along. My 
> collection tagging is almost at a stand-still.   Here's a gist with my 
> configuration 
> <https://gist.github.com/bearcatsandor/6ee35b7b751edfb52064ff0c582afb77> in 
> it, in case that helps. I've replaced all usernames, passwords and keys with 
> "xxxxxx".  A reliable way to reproduce it is to import a directory with a 
> cover.jpg that is less than 1000px wide.
> 
> Thank you
> 
> On Wednesday, November 16, 2016 at 6:51:41 PM UTC-7, Bearcat Şándor wrote:
> Often when i do an update or import a directory i get the following error:
> 
> No such file or directory while moving 
> /home/hometheater/audio/bon_jovi/1986-slippery_when_wet/cover.1.jpg to 
> /home/hometheater/audio/bon_jovi/1986-slippery_when_wet/cover.1.jpg
> 
> When i look at the directory, indeed there is no cover1.jpg.  This seems to 
> be coming from the fetchart plugin which renames the fetched cover to 
> cover1.[extention] if there is a cover already present in the directory.  
> However, that 'cover1' must be stored in the db somewhere if it's being 
> complained about and doesn't exist in the directory in question.
> 
> 
> -- 
> 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] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <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