Hello Ross,
> I forgot to mention that I hit clear search during my experiments. > However, it did follow having done some tag searches, so if they > were somehow sticking around it might explain the problem. If > they stuck around, that was not evident in the UI. This might be possible. I was never sure myself, but I think I might have stumbled about this behaviour already. Hmpf, I hate irreproducable bugs :-( I will try to figure out what might be wrong. > The first time I started up packagesearch and entered pdesk it > crashed. The second time, after doing a debtags update, it ran OK. > > Yet another probably unrelated issue in one bug report :) I sort of > remember the same pattern of an initial crash on my first system. Thanks this is fixed with the latest version 1.0.1. The plugin will disable itself properly now if the database is not found. > I think the errors indicate a major problem; for example there are > many messages "Removing tag devel not found in vocabulary". This is > odd, because "devel" shows in packagesearch's tags pain. However, > when I click on devel there are many missing packages. For example, I > see 3 zope packages in the packagesearch pain, but about 45 with a > "removing tag" message. The point with this is, that the tags are organized inside facets, i.e. we have a two level hierarchy now. And no packages should be tagged with facets directly. As this has changed against former version there are still a lot of packages which are tagged unappropriate (i.e. with a facet like devel). On a side note towards terminology: the top level hierachies are called facets, and the subitems are tags (see http://debtags.alioth.debian.org/ for more details) . > Should I report this to debtags? I think it is appropriate as it obviously confuses the users and Enrico should be aware of this. Besides he knows more about the internas than me. Greetings Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
