Closed GoogleCodeExporter closed 9 years ago
Is there a directory at "/home/x/Musique/__"?
Original comment by adrian.sampson
on 5 Nov 2012 at 6:04
Nope, no directory, no file.
Original comment by trash.xa...@gmail.com
on 5 Nov 2012 at 8:12
Strange. Can you include the verbose output for this case?
Original comment by adrian.sampson
on 5 Nov 2012 at 8:15
Here you go: http://pastebin.com/1KzbgtfP
Original comment by trash.xa...@gmail.com
on 5 Nov 2012 at 9:23
So weird -- beets is clearly under the impression that there's an album with
one track located at /home/x/Musique/__.
Do you also see this if you run "beet ls -ap"? Can you find the track by
running something like "beet ls -p albumartist::^$ album::^$"?
Original comment by adrian.sampson
on 5 Nov 2012 at 9:37
Yes, I see it:
beet ls -p albumartist::^$ album::^$
/home/x/Musique/__/00.mp3
beet ls -ap
/home/x/Musique/__
Maybe __/00.mp3 was a temporary file or something similar?
Original comment by trash.xa...@gmail.com
on 5 Nov 2012 at 11:54
Actually, this happens when a file sneaks into your library sans metadata.
I'm somehow totally failing to see how the import could proceed like this if
that file doesn't exist. Just to check, this command really emits an error?
$ ls -l /home/x/Musique/__/00.mp3
Original comment by adrian.sampson
on 5 Nov 2012 at 4:31
[deleted comment]
ls: impossible d'accéder à /home/x/Musique/__/00.mp3: Aucun fichier ou
dossier de ce type
Impossible to reach blabla...
Original comment by trash.xa...@gmail.com
on 5 Nov 2012 at 5:32
That's so strange. It looks like the file must have existed in the past but has
somehow been lost since. I really don't know how the DB entry got there in the
first place. You can clean it up by running something like:
$ beet rm albumartist::^$ album::^$
Original comment by adrian.sampson
on 5 Nov 2012 at 6:12
Original issue reported on code.google.com by
trash.xa...@gmail.com
on 4 Nov 2012 at 11:20