public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stefano Peluchetti <pelux@fastwebnet.it>
To: Gentoo-dev m-list <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] stable and unstable branches. (auto-bug reports???)
Date: Wed, 24 Jul 2002 11:28:57 +0200	[thread overview]
Message-ID: <3D3E7359.30400@fastwebnet.it> (raw)
In-Reply-To: 20020724001127.GC10394@athlon.dolly-llama.org

Ben Lutgens wrote:
> On Wed, Jul 24, 2002 at 12:12:45AM +0200, Stefano Peluchetti wrote:
> 
>>I know of this problem.
>>The thing that amazes me is that i very rarely find a bug report for the 
>>ebuild that doesn't work for me. I usaually commit the bugs i find but 
>>now it seems clear that some people does'nt do so.
>>I thing it could be a good idea at this point to introduce an automatic 
>>(user indipendent) bug report in portage, so that if ebuild compiling 
>>fails or some other errors arise, portage automagically submit a bug to 
>>the bug dabatabase of gentoo. That should speed up bugfixing (at lease 
>>for the majors bugs that prevent even building) and should' nt be that 
>>hard to implement in portage.
> 
> 
> People would go postal if gentoo was making network connections from thier
> boxen to our servers without thier knowledge. And rightly so. 
> 
> I'm in favor of an interactive bug report tool but bugzilla wouldn't
> facilitate that very well. Frankly I'd rather the users take a few mins to
> verify they have a bug, organize thier thoughts about it and then post.
> 
> And please, please, don't use bugzilla as a discussion board for your
> issues, work them out on the lists or forums untill you know it's a bug.
> 

Ok, but a simple message like:
"A problem arise with e-build xxx. Could i automaitcally submit a bug 
report for you? [Y/N]" should'nt do the work?
Also a little wizard that places needed information for bug report could 
be a different soluction.
But i think that this will make the work easier only for user who wants 
to spend their time submitting bugs. I may be wrong, but i thnink that a 
lot of gentoo user doesn't submit bug reports (as mantainer alway 
says!). And things won't change (i hope i'm wrong but....)
To me it didn't sound that bad to have an used indipendent suluction. 
Myabe an intermediate soluction? ( a spearate bug report database, where 
mantainer looks, and decide to submit a bug to the official database 
(it'  a real bug! :D )or discard it (the user is an idiot! :P ).
Thanks.

Stefano Pelux





  parent reply	other threads:[~2002-07-24  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 20:06 [gentoo-dev] stable and unstable branches Stefano Peluchetti
2002-07-23 20:21 ` Karl Trygve Kalleberg
2002-07-23 20:58   ` Terje Kvernes
2002-07-23 21:31 ` Christian Bartl
2002-07-23 22:12   ` [gentoo-dev] stable and unstable branches. (auto-bug reports???) Stefano Peluchetti
     [not found]     ` <20020724001127.GC10394@athlon.dolly-llama.org>
2002-07-24  9:28       ` Stefano Peluchetti [this message]
2002-07-24  4:32   ` [gentoo-dev] stable and unstable branches Christian Axelsson
2002-07-24  5:28     ` Chad M. Huneycutt
2002-07-24  8:50     ` Alexander Gretencord
2002-07-24 15:32   ` Fredrik Jagenheim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D3E7359.30400@fastwebnet.it \
    --to=pelux@fastwebnet.it \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox