On Wed, May 5, 2010 at 6:26 PM, Jeff Spaleta wrote:
> On Wed, May 5, 2010 at 2:12 PM, Orcan Ogetbil wrote:
>> An anonymous database is easy to ignore by packagers. I fear that that
>> might turn to something as useless as pulseaudio.
>
>
> The little jab at pulseaudio is extremely inappropriate and
On Wed, May 5, 2010 at 2:12 PM, Orcan Ogetbil wrote:
> An anonymous database is easy to ignore by packagers. I fear that that
> might turn to something as useless as pulseaudio.
The little jab at pulseaudio is extremely inappropriate and absolutely
non-constructive to the discussion at a hand. S
On Wed, May 5, 2010 at 6:02 PM, Jeff Spaleta wrote:
> On Wed, May 5, 2010 at 1:34 PM, Orcan Ogetbil wrote:
>> I understand. But please respect what others are thinking. I do see a
>> problem in abrt that it wastes my time.
>
> It's not possible for you to simply ignore the abrt bugs? I filter
> th
On Wed, May 5, 2010 at 1:34 PM, Orcan Ogetbil wrote:
> I understand. But please respect what others are thinking. I do see a
> problem in abrt that it wastes my time.
It's not possible for you to simply ignore the abrt bugs? I filter
the [abrt] ticket email into a separate folder for example so
On Wed, May 5, 2010 at 5:34 PM, Orcan Ogetbil wrote:
>
> I understand. But please respect what others are thinking. I do see a
> problem in abrt that it wastes my time.
To stem another abrt thread; see earlier one here:
http://www.redhat.com/archives/rhl-devel-list/2009-November/msg01487.html
Ba
On Wed, May 5, 2010 at 5:02 PM, Jeff Spaleta wrote:
> On Wed, May 5, 2010 at 12:47 PM, Orcan Ogetbil wrote:
>> Can we just disable abrt on Fedora until it figures how to file bugs
>> upstream? What is the procedure to propose this? Does this have to go
>> through FESCo?
>
> that's a bit drastic. I
On Wed, May 5, 2010 at 12:47 PM, Orcan Ogetbil wrote:
> Can we just disable abrt on Fedora until it figures how to file bugs
> upstream? What is the procedure to propose this? Does this have to go
> through FESCo?
that's a bit drastic. I don't want abrt disabled on my packages. I'm
willing to mak
On Tue, May 4, 2010 at 6:36 PM, Kevin Kofler wrote:
> Orcan Ogetbil wrote:
>> Hmm, this is what I did this a couple times, i.e. I forward the
>> backtrace to upstream without including any other information, since
>> the user does not provide any.
>>
>> What I receive from upstream is that they nee
On Tue, May 4, 2010 at 11:46 PM, Mathieu Bridon
wrote:
> On Wed, May 5, 2010 at 00:36, Kevin Kofler wrote:
>> Orcan Ogetbil wrote:
>>> Hmm, this is what I did this a couple times, i.e. I forward the
>>> backtrace to upstream without including any other information, since
>>> the user does not pro
Am Mittwoch, den 05.05.2010, 00:46 +0200 schrieb Mathieu Bridon:
> On Wed, May 5, 2010 at 00:36, Kevin Kofler wrote:
> > Orcan Ogetbil wrote:
> >> Hmm, this is what I did this a couple times, i.e. I forward the
> >> backtrace to upstream without including any other information, since
> >> the user
On Wed, May 5, 2010 at 00:36, Kevin Kofler wrote:
> Orcan Ogetbil wrote:
>> Hmm, this is what I did this a couple times, i.e. I forward the
>> backtrace to upstream without including any other information, since
>> the user does not provide any.
>>
>> What I receive from upstream is that they need
Orcan Ogetbil wrote:
> Hmm, this is what I did this a couple times, i.e. I forward the
> backtrace to upstream without including any other information, since
> the user does not provide any.
>
> What I receive from upstream is that they need more info. Then I go
> back to the user asking once more
On Tue, May 4, 2010 at 6:01 PM, Mat Booth wrote:
> On 4 May 2010 21:29, Orcan Ogetbil wrote:
>> On Fri, Apr 23, 2010 at 1:45 PM, Christoph Wickert wrote:
>>>
>>> Please, dear maintainers, take care of your ABRT reports and forward
>>> them if you cannot handle them yourselves!
>>>
>>
>> I want to d
On 4 May 2010 21:29, Orcan Ogetbil wrote:
> On Fri, Apr 23, 2010 at 1:45 PM, Christoph Wickert wrote:
>>
>> Please, dear maintainers, take care of your ABRT reports and forward
>> them if you cannot handle them yourselves!
>>
>
> I want to do this, but I need to verify first if the bug is packagin
On Fri, Apr 23, 2010 at 1:45 PM, Christoph Wickert wrote:
>
> Please, dear maintainers, take care of your ABRT reports and forward
> them if you cannot handle them yourselves!
>
I want to do this, but I need to verify first if the bug is packaging
related or upstream related.
However I get these
On Wed, 2010-04-28 at 00:04 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Right. There've been times where it hasn't done this properly and that's
> > when you used to get empty reports from abrt, but that's much less
> > likely to happy with current code; it's better at making sure the
>
Adam Williamson wrote:
> Right. There've been times where it hasn't done this properly and that's
> when you used to get empty reports from abrt, but that's much less
> likely to happy with current code; it's better at making sure the
> debuginfos get installed, and also complains a lot more before
On Mon, 2010-04-26 at 19:54 -0400, Matt McCutchen wrote:
> On Mon, 2010-04-26 at 10:11 -0800, Jeff Spaleta wrote:
> > On Sun, Apr 25, 2010 at 12:10 AM, Christoph Wickert
> > wrote:
> > > I'm upstreaming reports from 'lazy idiots' too and some of them get
> > > fixed. In fact the percentage of the
On Mon, 2010-04-26 at 10:11 -0800, Jeff Spaleta wrote:
> On Sun, Apr 25, 2010 at 12:10 AM, Christoph Wickert
> wrote:
> > I'm upstreaming reports from 'lazy idiots' too and some of them get
> > fixed. In fact the percentage of the ones that get fixed is not
> > different from the 'active' reporter
On Sun, Apr 25, 2010 at 12:10 AM, Christoph Wickert
wrote:
> I'm upstreaming reports from 'lazy idiots' too and some of them get
> fixed. In fact the percentage of the ones that get fixed is not
> different from the 'active' reporters cause usually the backtrace
> contains all necessary data for t
On Sunday 25 April 2010 10:33:13 Kevin Kofler wrote:
> Christoph Wickert wrote:
> > I'm upstreaming reports from 'lazy idiots' too and some of them get
> > fixed. In fact the percentage of the ones that get fixed is not
> > different from the 'active' reporters cause usually the backtrace
> > conta
Christoph Wickert wrote:
> I'm doing this for ~ 130 packages and it works for me.
Good for you. I have more important things to do than do triaging day and
night, sorry.
> Of course it is a some work, but it's easier for 20 downstream maintainers
> to deal with 10 reports each a week than for a
Christoph Wickert wrote:
> I'm upstreaming reports from 'lazy idiots' too and some of them get
> fixed. In fact the percentage of the ones that get fixed is not
> different from the 'active' reporters cause usually the backtrace
> contains all necessary data for the developer to fix the problem.
A
On 25/04/10 09:20, Christoph Wickert wrote:
--snipped--
>
> And obviously a checkbox doesn't help ether to separate the 'lazy
> idiots' from the active reporters. Q. E. D. ;)
Or perhaps the lazy maintainers?
--
Regards,
Frank Murphy
UTF_8 Encoded, Fedora 64 and 32
--
devel mailing list
dev
Am Sonntag, den 25.04.2010, 09:23 +0200 schrieb Kevin Kofler:
> Christoph Wickert wrote:
> > We have this nice ABRT tool now, so please let the bug reports our users
> > collect not be useless and forward them upstream cause that's where they
> > belong. We are not collecting these reports to let t
Am Sonntag, den 25.04.2010, 09:17 +0200 schrieb Kevin Kofler:
>
> ABRT bugs are usually filed by
> lazy idiots who have hit a "fix my software!" button and expect everything
> else to magically happen without them doing anything, so requests to
> upstream bugs are usually met with total silence
Christoph Wickert wrote:
> We have this nice ABRT tool now, so please let the bug reports our users
> collect not be useless and forward them upstream cause that's where they
> belong. We are not collecting these reports to let them rotten in our
> bugzilla and get them closed by the bugzappers. Th
Adam Williamson wrote:
> Not really. abrt reports are bug reports on crashing applications. The
> fact that they're automatically generated doesn't really matter a lot.
> Our policies should be as wide as practical, having special policies for
> some bugs just because they happen to have been gener
Thomas Spura wrote:
> Am Samstag, den 24.04.2010, 13:27 +0530 schrieb Rahul Sundaram:
>> There is a alternative. For some of my packages, I have asked upstream
>> to sign up for a Fedora account and apply to watch commits and bugs.
>> Since my packages are either patch free or I apply patches re
On 04/24/2010 10:47 PM, Thomas Spura wrote:
> That's true, but it sounded more like a 'solution' to the problem, and
> that's unfortunately not :(
> We should also find a solution for packages, where the maintainers
> didn't consider it as a option… Unfortunately this will be the case for
> the mos
Am Samstag, den 24.04.2010, 22:14 +0530 schrieb Rahul Sundaram:
> On 04/24/2010 09:49 PM, Thomas Spura wrote:
> > Am Samstag, den 24.04.2010, 13:27 +0530 schrieb Rahul Sundaram:
> >> There is a alternative. For some of my packages, I have asked upstream
> >> to sign up for a Fedora account and ap
On 04/24/2010 09:49 PM, Thomas Spura wrote:
> Am Samstag, den 24.04.2010, 13:27 +0530 schrieb Rahul Sundaram:
>> There is a alternative. For some of my packages, I have asked upstream
>> to sign up for a Fedora account and apply to watch commits and bugs.
>> Since my packages are either patch f
Am Samstag, den 24.04.2010, 13:27 +0530 schrieb Rahul Sundaram:
> On 04/24/2010 01:15 PM, Christoph Wickert wrote:
> >
> > * because without forwarding them the whole ABRT approach is
> > useless. We are gathering data but the reports are going to be
> > closed WONTFIX by the
On 04/24/2010 01:15 PM, Christoph Wickert wrote:
>
> * because without forwarding them the whole ABRT approach is
> useless. We are gathering data but the reports are going to be
> closed WONTFIX by the bugzappers if they are not forwarded in
> time.
>
There is a a
Am Freitag, den 23.04.2010, 22:09 +0100 schrieb Adam Williamson:
> On Fri, 2010-04-23 at 19:45 +0200, Christoph Wickert wrote:
>
> > P.S.: Now that we gather all these data, do we need a general policy for
> > it? Should the bugzappers take care of forwarding bugs?
>
> Not really. abrt reports ar
On Fri, 2010-04-23 at 19:45 +0200, Christoph Wickert wrote:
> P.S.: Now that we gather all these data, do we need a general policy for
> it? Should the bugzappers take care of forwarding bugs?
Not really. abrt reports are bug reports on crashing applications. The
fact that they're automatically g
Christoph Wickert wrote:
> When I receive a bug report I have a look at it and if it contains all
> necessary data, I forward it to upstream's bug tracker. Most of the time
> the developers are very thankful about the reports and especially the
> backtraces. Looking at the bugs I filed I see that n
A while back I was complaining about how the KDE SIG handles bug
reports. One could certainly argue that closing everything UPSTREAM
doesn't help to track bugs in Fedora, but on the other hand the bugs are
at least submitted to the original developers.
When I receive a bug report I have a look at
38 matches
Mail list logo
