[gentoo-dev] Bugs Bugs Bugs & Unstablity

[gentoo-dev] Bugs Bugs Bugs & Unstablity

[Doug Goldstein]

All I ever hear or read about is people complaining about bugs or 
stability issues or an ebuild problem. Granted I'm not complaining about 
this, this is good... we need to know this. But there is one thing 
missing... I go to http://bugs.gentoo.org and sort through the bugs and 
there are hardly any bug reports for the problems people say.

Here's a couple things I'd like to see our users do as far as bugs
1) Fill out bug reports @ http://bugs.gentoo.org
2) Provide us with all the necessary details... for example... if you 
just tell me that libfoo's latest ebuild doesn't compile for you. That 
is definetly not enough detail. Provide the FULL version including our 
ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see.
3) You NEED to tell us which version compiler you are using.
4) You need to tell us your USE flags and your CFLAGS
5) Provide us with a copy and paste of the exact error message.
6) Any other data you feel might be revelant.

If you do all that more bugs will be fixed and they will hopefully be 
fixed faster.

And if the person who sent me the patch against the latest version of 
pcmcia-cs over IRC in a /query while I was gone is here.... please fill 
out a bug report and lemme know what it fixes and include it. My battery 
on the laptop ran out while I was gone.

In conclusion, you need to submit your bugs and concerns in a reliable 
fashion so that they can be properly addressed... the only way to do 
that is to fill out a bug report.

-- 
Doug Goldstein
Developer (Laptops, WiFi, GCC-3.1)
Gentoo Linux                                http://www.gentoo.org/~cardoe/

Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity

[Stefano Peluchetti]

Doug Goldstein wrote:
> All I ever hear or read about is people complaining about bugs or 
> stability issues or an ebuild problem. Granted I'm not complaining about 
> this, this is good... we need to know this. But there is one thing 
> missing... I go to http://bugs.gentoo.org and sort through the bugs and 
> there are hardly any bug reports for the problems people say.
> 
> Here's a couple things I'd like to see our users do as far as bugs
> 1) Fill out bug reports @ http://bugs.gentoo.org
> 2) Provide us with all the necessary details... for example... if you 
> just tell me that libfoo's latest ebuild doesn't compile for you. That 
> is definetly not enough detail. Provide the FULL version including our 
> ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see.
> 3) You NEED to tell us which version compiler you are using.
> 4) You need to tell us your USE flags and your CFLAGS
> 5) Provide us with a copy and paste of the exact error message.
> 6) Any other data you feel might be revelant.
> 
> If you do all that more bugs will be fixed and they will hopefully be 
> fixed faster.
> 
> And if the person who sent me the patch against the latest version of 
> pcmcia-cs over IRC in a /query while I was gone is here.... please fill 
> out a bug report and lemme know what it fixes and include it. My battery 
> on the laptop ran out while I was gone.
> 
> In conclusion, you need to submit your bugs and concerns in a reliable 
> fashion so that they can be properly addressed... the only way to do 
> that is to fill out a bug report.
> 

I have already mentioned this, see my last reply to the previous thread.
Bye

Stefano Peluchetti

Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity

[Vitaly Kushneriuk]

On Wed, 2002-07-24 at 01:53, Doug Goldstein wrote:
> All I ever hear or read about is people complaining about bugs or 
> stability issues or an ebuild problem. Granted I'm not complaining about 
> this, this is good... we need to know this. But there is one thing 
> missing... I go to http://bugs.gentoo.org and sort through the bugs and 
> there are hardly any bug reports for the problems people say.
> 
> Here's a couple things I'd like to see our users do as far as bugs
> 1) Fill out bug reports @ http://bugs.gentoo.org
> 2) Provide us with all the necessary details... for example... if you 
> just tell me that libfoo's latest ebuild doesn't compile for you. That 
> is definetly not enough detail. Provide the FULL version including our 
> ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see.
> 3) You NEED to tell us which version compiler you are using.
> 4) You need to tell us your USE flags and your CFLAGS
> 5) Provide us with a copy and paste of the exact error message.
> 6) Any other data you feel might be revelant.
> 
> If you do all that more bugs will be fixed and they will hopefully be 
> fixed faster.
> 
> And if the person who sent me the patch against the latest version of 
> pcmcia-cs over IRC in a /query while I was gone is here.... please fill 
> out a bug report and lemme know what it fixes and include it. My battery 
> on the laptop ran out while I was gone.
> 
> In conclusion, you need to submit your bugs and concerns in a reliable 
> fashion so that they can be properly addressed... the only way to do 
> that is to fill out a bug report.
> 
> -- 
> Doug Goldstein
> Developer (Laptops, WiFi, GCC-3.1)
> Gentoo Linux                                http://www.gentoo.org/~cardoe/

Writing  report wizard that will collect needed information and submit
it to the bugzilla might help ;-).

Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity

[Kim Nielsen]

On Wed, 2002-07-24 at 00:53, Doug Goldstein wrote:
> 
> Here's a couple things I'd like to see our users do as far as bugs
> 1) Fill out bug reports @ http://bugs.gentoo.org
> 2) Provide us with all the necessary details... for example... if you 
> just tell me that libfoo's latest ebuild doesn't compile for you. That 
> is definetly not enough detail. Provide the FULL version including our 
> ebuild revision, such as libfoo-1.0.1-r1.ebuild is what we'd like to see.
> 3) You NEED to tell us which version compiler you are using.
> 4) You need to tell us your USE flags and your CFLAGS
> 5) Provide us with a copy and paste of the exact error message.
> 6) Any other data you feel might be revelant.
> 

Excuse me for sounding a bit grumpy .. but every time I add something
new in bugzilla its stays in bugzilla and no one is using or looking at
it (I submitted a bugfix to the gentoo security guide more than one
month ago). This is how it works with documentation.

So problems are resolved in the same tempo as with documentation, I can
understand why someone with problems compiling a package prefers to mail
it to the list instead of filling out a bug report.

/Kim

Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity

[Jean-Michel Smith]

On Wednesday 24 July 2002 03:13 am, Kim Nielsen wrote:

> Excuse me for sounding a bit grumpy .. but every time I add something
> new in bugzilla its stays in bugzilla and no one is using or looking at
> it (I submitted a bugfix to the gentoo security guide more than one
> month ago). This is how it works with documentation.
>
> So problems are resolved in the same tempo as with documentation, I can
> understand why someone with problems compiling a package prefers to mail
> it to the list instead of filling out a bug report.

I've submitted two bug reports (that I recall).

One was fixed and resolved very quickly, the other is being worked on (and I 
periodically receive email detailing the work).  The one that hasn't been 
resolved yet is a really difficult one (OmniORB's f*cked up installation 
procedure, which having tried to fix myself and failed I can understand the 
delay on ... working with those .mk scripts is a pain to the nth degree), but 
even it is being worked on.

Both of the bugs in question were not critical to the overall functionality of 
the gentoo system ... they were for ebuilds I happen to want to use, that 
were (or in the case of omniORB, still are) broken.  Critical bugs get fixed 
much faster.

It may take a couple or three weeks, but the bug reports do get read, 
assigned, and fixed.  Of course, if the reports are just sent to the list and 
complained about, but never filed with bugzilla, it is entirely possible 
they'll never get fixed.  The developers have made it plain on more than one 
occasion that the mailing lists and forums are in general a bad place to be 
filing bug reports.

Jean.

Re: [gentoo-dev] Bugs Bugs Bugs & Unstablity

[Paul de Vrieze]

On Wednesday 24 July 2002 13:47, Jean-Michel Smith wrote:
> It may take a couple or three weeks, but the bug reports do get read,
> assigned, and fixed.  Of course, if the reports are just sent to the list
> and complained about, but never filed with bugzilla, it is entirely
> possible they'll never get fixed.  The developers have made it plain on
> more than one occasion that the mailing lists and forums are in general a
> bad place to be filing bug reports.
>

I submitted enough bug reports, and they the fixing time tends to vary. The 
main reason for slow fixes is either "there is no known solution" (just a 
difficult bug), "the bug report sucks" (what the hell goes wrong, the ebuild 
is not good enough and needs a lot of work), "upstream is slow" (well, we 
cannot fix it, but are waiting for upstream). Ebuild patches are generally 
processed fast, especially if you describe what your patch does and why. This 
is to a degree also true for program patches.

In short, the more you do, the faster you will get a result.

Paul

-- 
Paul de Vrieze
Junior Researcher
Mail: pauldv@cs.kun.nl
Homepage: http://www.devrieze.net