Sorry - that was a typo. Typing 'bugzilla' must have made me think back to my earlier problem with mozlla :-/
It was actually 'realplayer' that I searched on, and which produced the five matches when I selected the 'bugs' link.... I just tried it again, and all it gives me are ID's 6720, 79555, 86511, 87118 and 89045.. This is the URL that the link invokes: http://bugs.gentoo.org/buglist.cgi?query_format=&short_desc_type=allwords&short_desc=realplayer&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED It looks like the problem was that checking for known problems this way doesn't find but reports with a RESOLVED status, and in this case RESOLVED is a little misleading in that a simple 'emerge --update' wont fix it without manual intervention according to the instructions in the problem entry. Moral of the story seems to be to search for ALL bugs from the mozilla page rather than relying on the bugs link in the package database. Regards, DigbyT On Wed, Apr 20, 2005 at 12:18:04AM +0100, Neil Bothwick wrote: > On Tue, 19 Apr 2005 22:56:21 +0100, Digby Tarvin wrote: > > > I did check the bugzilla (by searching for mozilla in the package > > database and then invoking the 'bugs' link) but none of the > > five items listed seemed to refer to 10.0.3.. > > Why 'mozilla' when the error was with RealPlayer? Searching for > RealPlayer brings it up, bug no. 87198. > > > -- > Neil Bothwick > > "Bother" said Pooh when C4 postponed B5 -- Digby R. S. Tarvin [EMAIL PROTECTED] http://www.digbyt.com -- [email protected] mailing list
