abrt not working in current Rawhide?

Neil Horman nhorman at redhat.com
Thu Jan 28 15:21:42 UTC 2010


On Thu, Jan 28, 2010 at 03:38:27PM +0100, Jiri Moskovcak wrote:
> On 01/28/2010 03:25 PM, Neil Horman wrote:
> >On Thu, Jan 28, 2010 at 01:17:08PM +0100, Jiri Moskovcak wrote:
> >>On 01/28/2010 01:02 PM, Neil Horman wrote:
> >>>On Thu, Jan 28, 2010 at 10:55:47AM +0100, Jiri Moskovcak wrote:
> >>>>On 01/28/2010 02:03 AM, Neil Horman wrote:
> >>>>>On Wed, Jan 27, 2010 at 10:46:33PM +0100, Jiri Moskovcak wrote:
> >>>>>>Unfortunately it doesn't because of this:
> >>>>>>https://bugzilla.redhat.com/show_bug.cgi?id=557386
> >>>>>>
> >>>>>>Jirka
> >>>>>>
> >>>>>Bear in mind, Abrt could have fixed this any time in the past few weeks, they've
> >>>>>just chosen not to.  Jiri, you and I agreed that you would pursue a user space
> >>>>>correction for this that I laid out for you if I proposed a kernel space
> >>>>>solution. I can't help but notice you seem to have tossed that asside.
> >>>>>Neil
> >>>>>
> >>>>
> >>>>Yes, I decided not to implement it, because I discussed the proposed
> >>>>solution with few other engineers and nobody likes it and the
> >>>>security/selinux guys wouldn't like it also. Please don't take me wrong,
> >>>>the solution you've proposed is just a few lines of code, so it's not a
> >>>>big problem to write it, but it's just a temporary workaround and would
> >>>>require changing the selinux policy and to make it work fine. We can
> >>>>take a vote and if there is enough people to support it then I' write
> >>>>it, but I don't writing something to /proc/<pid>/ is a good idea.
> >>>>
> >>>>Jirka
> >>>
> >>>Well, thanks for comming to a conclusion about this without bothering to bring
> >>>it back up with me, thats fantastic.  The bottom line is, you saw that I was
> >>>willing to try do what you wanted me to do, and concluded that you didn't need
> >>>to do what I had asked you to do.  Thats a lousy way to behave.
> >>>Neil
> >>>
> >>
> >>I'm sorry that you feel that way, but what would it change anyway? I
> >>already told you my concerns about that on irc, yes I said I'll
> >>implement it, but before that I went to discuss it with some of my
> >>colleagues and no-one likes it for the same reasons I already told
> >>you,
> >>so what would be the point of repeating the same if I already knew
> >>your opinion?
> >>
> >Because you told me you would, on irc we discussed it, you told me your
> >concerns, I told you my thoughts on it, and we agreed that it was worth
> >implementing.  The fact that your collegues there agreed with you doesn't give
> >you leave to conclude that this is my problem to fix, and just disregard what
> >you said you would do.  If it did, I would just assert that some
> >co-workers here agree with my opinion and stop working on any solution you asked
> >me to.  I have half a mind to do exactly that.
> >
> >
> 
> C'mon do we really need to make this into a fight? The reason why I
> didn't implement it is that it would be temporary anyway and thus
> doesn't worth the work, because it's not just that 10 lines of code
> on ABRT side, it gets more people from different teams involved, so
> that's why I decided not to do it. Yes, I should told you that and
> I'm really sorry I didn't.
> 
Apparently we have different recollections of what we discussed.
Neil



More information about the devel mailing list