| Interesting...I don't think this was my bug.
| It appears that Msg_Change was asked to change to message "-".
Something like that is quite possible, but perviously typing nonsense
in didn't cause tracebacks, and now it does, and the traceback came
Perviously this would have just caused red messages in the status
line complaining about my lousy typing.   That's probably what it
should keep on doing (the "red" part isn't important obviously..)

No, hits=-6.2 required=7.0
	tests=KNOWN_MAILING_LIST,NOSPAM_INC,SIGNATURE_SHORT_SPARSE,
	      SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_MOZILLA_UA,
	      X_ACCEPT_LANG
	version=2.40-cvs

No, hits=-7.2 required=7.0
	tests=IN_REP_TO,KNOWN_MAILING_LIST,QUOTED_EMAIL_TEXT,REFERENCES,
	      SPAM_PHRASE_00_01
	version=2.40-cvs

from mx1.example.com (mx1.example.com [66.187.233.31]) by egwn.net
    (8.11.6/8.11.6/EGWN) with ESMTP id g7N7oBJ30858 for
    <rpm-list@freshrpms.net>; Fri, 23 Aug 2002 09:50:11 +0200
from int-mx1.corp.example.com (int-mx1.corp.example.com
    [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id
    g7N7Zal24437 for <rpm-list@freshrpms.net>; Fri, 23 Aug 2002 03:35:36 -0400
from pobox.corp.example.com (pobox.corp.example.com
    [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id
    g7N7oAY14355 for <rpm-list@freshrpms.net>; Fri, 23 Aug 2002 03:50:10 -0400
from ckk.rdu.example.com (ckk.rdu.example.com [172.16.57.72]) by
    pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g7N7o9J22551 for
    <rpm-list@freshrpms.net>; Fri, 23 Aug 2002 03:50:10 -0400
No, hits=-9.6 required=7.0
	tests=EMAIL_ATTRIBUTION,IN_REP_TO,KNOWN_MAILING_LIST,
	      QUOTED_EMAIL_TEXT,REFERENCES,SIGNATURE_SHORT_SPARSE,
	      SPAM_PHRASE_01_02
	version=2.40-cvs

On Thu, 2002-08-22 at 19:10, Troy Engel wrote:
> Anyone have an idea what the heck RedHat did here, and why we're now
> trying to install a ton of crap I don't want?  (I'm hoping someone else
> has chased this down and could save me time... ;) )
I'm told that even our best people occasionally screw up. And QA had
tested the rpm on an "Everything" install. Expect a fixed version soon,
and QA procedures have been adjusted to catch this kind of braindamage
in the future. There is nothing really wrong with the binary inside the
rpm, so if you want to --nodeps for now it's ok.
--
Chris Kloiber
_______________________________________________
RPM-List mailing list <RPM-List@freshrpms.net>
http://lists.freshrpms.net/mailman/listinfo/rpm-list