Jason Tackaberry wrote: > On Wed, 2006-04-19 at 11:14 +0200, Dirk Meyer wrote: >> Besides the bug in the error message, why can't beacon find the media? >> The media support (different root dirs on different media like cd) is >> not integrated yet and you should always find the media (normal hd). > > I honestly couldn't tell you why. I hope that's a rhetorical > question. :)
Yes, just thinking loud to hope you get an idea... > sqlite> select name,id from objects_dir where id in (13,8,9); > tv|8 > |9 > buffy|13 > > Indeed, 9 is empty. Why, I have no idea. But it looks like beacon has > added a phantom parent in there: > > / -> home -> tack -> tv -> (EMPTY) -> buffy ... like this one. > > I'll see if I can figure out why when I get home. Unless you have any > ideas. But the directory structure under /home/tack/tv is quite > straightforward, with no symlinks at all. > > Ah, but note, if I delete ~/.beacon and run: > > BEACON_MONITOR=/home/tack/tv beacon --start > > Then the query that before failed now works fine. So there's something > about my having previously attempted to index /data/movies that is > causing this problem. Possibly due to the failure indexing /data/movies > it has left some cruft in the tables that is confusing matters. If so, > aside from the original bug, that's a bug too. :) It should work now (also with your softlinks) >> Not lots of bugs, but small stuff that doesn't match my testing cases >> like your softlinks for example. > > I'm sure there are stranger configurations than mine. :) Yes, I guess. Like softlinks pointing to nothing. Dischi -- "I get to go to lots of overseas places, like Canada." - Britney Spears
pgprVOHf8XXYS.pgp
Description: PGP signature
