cover1.jpg not found and halting updates and imports

[Bearcat Şándor]

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.

[Adrian Sampson]

Yes, beets keeps track of your files, including images. So if you delete an image file, beets might get confused.

--
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 beets-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Bearcat Şándor]

Well, first off it's looking at a backup file. What's odd is that even if i rename cover.jpg to cover.1.jpg it then complains renames it back to cover.jpg and complains "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

" again.

Is there a better way to approach this or is it a bug?

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/fyEvIfJAcdI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beets-users...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Bearcat M. Şándor, CEO
Feline Soul Systems LLC
Voice: 872.CAT.SOUL (872.228.7685)
Fax: 406.235.7070

[Adrian Sampson]

That’s odd. It’s sort of hard to see exactly what’s going on without knowing how beets got into this state—is there something we can do to reproduce the behavior from scratch?

[Bearcat Şándor]

Sure.  If you enable the fetchart plugin with these options

fetchart:

    auto: true

    google_key: AIzaSyDxkosmJMLvt6bAJIy_VkwcM01E_A-AqRg    

    google_search: false 

    cautious: false

    cover_names: cover front back art album folder

    minwidth: 1000

    sources: filesystem fanarttv coverart itunes amazon albumart wikipedia google

    fanarttv_key: 73a82af81e9eecf2acd6461a2861b5cd

    store_source: yes

Find a cover for an album that is less than 1000px wide and put it in the album's directory with a filename of cover.jpg.  If you run fetchart on those tracks and it finds art, you'll see the new cover with a name of cover.1.jpg.  Then when you re-import the album you should get the error, even if you change the file names.

Thanks for the help!!  If you want me to post a directory wherein this happens i can do that, but if so i'd prefer to send you the link privately so as to avoid 'illegal file sharing'.

[Raf Czlonka]

On Thu, Nov 17, 2016 at 04:40:23AM GMT, Bearcat Şándor wrote:
> Sure. If you enable the fetchart plugin with these options
>
> fetchart:
> auto: true
> google_key: AIzaSyDxkosmJMLvt6bAJIy_VkwcM01E_A-AqRg

> [...]
> google
> fanarttv_key: 73a82af81e9eecf2acd6461a2861b5cd

Hi,

I strongly suggest you get new keys straight away and don't include
any next time you're sending your config:^)

Cheers,

Raf

[Adrian Sampson]

Sure! A directory I can run this on would be super helpful. (Please feel free to email me directly.)

[Bearcat Şándor]

Aw crap! Thanks Raf. That's what i get for posting when i'm sick.

[Bearcat Şándor]

Sent.

[Bearcat Şándor]

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 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

[Adrian Sampson]

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

[Bearcat Şándor]

Well, at this point i think it's only a problem i'm having.  I can say that doing an additional  fetchart on the offending directory fixes the problem.

On Wednesday, November 16, 2016 at 6:51:41 PM UTC-7, Bearcat Şándor wrote:

[Boris Prüßmann]

No, I was having the exact same issue yesterday. I had changed the title of an album and wanted beets to make the proper moves. For some weird reason, after moving the cover.jpg to the new destination, it complained afterwards that it could not find cover.jpg (old location) to move it to cover.1.jpg (new location).

[Adrian Sampson]

OK! That list of steps to nail down the problem and file a complete GitHub issue would still be really helpful. Here’s a copy ’n paste:

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 appears.