On Sunday 30 January 2005 20:30, Duncan wrote: > Stefan Schweizer posted <[EMAIL PROTECTED]>, > > excerpted below, on Sun, 30 Jan 2005 09:15:55 +0100: > > On Sat, 29 Jan 2005 21:59:44 -0800, M. Edward (Ed) Borasky > > > > <[EMAIL PROTECTED]> wrote: > >> I see "QA Notices" fairly often in updates. I run mixed ~x86 and > >> non-~x86, though. Should I be reporting the non-~x86 ones as bugs?? > > > > You should even report the ~x86 QA Notices as bugs .. ~x86 means testing, > > we want feedback from the users. > > OK, this is a question that's been bothering me.. > > What about the "improper inheritance if eclass" or whatever errors I often > see during the unmerge of old packages after an update? When the question > last came up (in general, not on unmerging packages), the answer was the > system wasn't quite ready to handle the deluge of such errors just yet. > It was new to portage and in a version still hard masked at the time for > testing, IIRC. However, since then I've continued to see the QA Notice > message, but most of the time during an unmerge of an old package after an > update to a newer version. Thus, I've figured it's getting the old > packages out of the way and it's not worth reporting those QA Notices on > those old packages. Is that correct, or at least for someone generally > keeping up with ~arch (in my case ~amd64), should I be reporting those on > unmerges as well, now?
The reason it appears for old packages is that the information used for that check wasn't gathered at the time that the old packages were installed. As a general rule, notices can pretty much be ignored for unmerging. Any valid QA notice will appear upon any operation. Regards, Jason Stubbs -- [email protected] mailing list
