On Sun, Jan 30, 2005 at 05:32:45PM +0100, Benjamin Mesing wrote: > Hello, > > > I have a possible clue: maybe this is some interaction with package > > installation. I had the problem happen again, and it was while I was > > doing an apt-get dist-upgrade (specifically, while it was doing all > > the installs). > Thanks, I was able to reproduce the bug now doing an "apt-get update" Yea! > while fideling around with the searches. Afterwards the apt-search was > broken in packagesearch. Now that I know what is wrong, I only have to > find a solution :-o. But this is not that easy because I have to > recognize external changes on the apt database. Perhaps this bug really > is something for the won't fix section. I will think about it. Rather than trying to deal with changes, you could just put a lock on the database. I assume there's some standard way to do so. That is ugly, considering it's read only, but at least it would fix the problem.
Probably some other apt-based tool has a way to deal with this, though, since it's graphical, packagesearch is likely to be longer lived than most apt tools. > > Thanks again for your report and your patience in hunting down the > problem. You're welcome. Ross -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
