Re: closed bugs, open comments?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



Aaron Griffin wrote:
On Wed, Feb 18, 2009 at 3:03 PM, Baho Utot <baho-utot@xxxxxxxxxxxxxxx> wrote:
Grigorios Bouzakis wrote:
On Tue, Feb 17, 2009 at 04:46:19PM -0500, Baho Utot wrote:

Nicolas Bigaouette wrote:

I totally second that. It is really frustrating as a bug reporting user
to
end the discussion like this.
It really looks like a "shut-up and stop annoying us" thing...

I know it did not gave me the motivation to open other bugs.

I don't see why the discussion should be closed when the bug is. As
Damjan
said, some useful information can still be provided even if the bug is
closed.


2009/2/16 Damjan Georgievski <gdamjan@xxxxxxxxx>


Which is why I don't submit bug reports anymore.

Instead of +1'ing this could you provide examples instead?

No not really, as I am done with this and I am not going to argue with
anyone about this.

It's just that I came looking for help and got slammed one too many times.

Now I either go the the news groups for help or fix it my self.  If I don't
get a solution then I skip the package and move on.

Out of curiosity - how many people here also believe that the bug
tracker is for help? I am honestly interested, as this could be the
source of confusion here - the above is actually the way things SHOULD
work - forums, newsgroups, mailing lists, etc should be used for help;
the bug tracker should be used for bugs or "actionable items"

I know the bug tracker is for bugs and not help, when I used to file bug reports I did so because some thing didn't work (for example compiling a package under the current arch gcc version). Yes maybe I didn't fully understand the issue. You can look at your favorite package klibc* :), ( klibc-udev to be exact) which I did file. (remember we found a flea in pacman/makepkg using makeworld with the --log flag).

Although I did not file a bug report for this here is an example

I had opensp that I found a solution for and tried to get my patch applied and the response (The way I saw it maybe not as it was intended) was go adopt the package followed by a piss off. Well the package was in extra I couldn't adopt it and I can not fix it in any way. I the problem still exists with opensp. My intention was to simply get it fixed, all that needed to be done was for someone who has access to update the PKGBUILD and add the patch which I received from comp.os.linux.misc and it will build. I did file a upstream bug report.

Also:

Had the bug report for the klibc* I filed just be tossed as in this is not a bug, the makeworld --log flea would not have been found. I think that bug reports can be closed too quickly, maybe because the one who closes the report doesn't fully understand why the report was filed ( We are all not good english speakers ).

My suggestion would be to create an arch news group where issues using/building etc can be discussed. It could then be searched and one could read the thread and it may/could fix ones issue/problem. It also could promote discussion leading to solutions for bugs/issues/problems as well as one more source of help for less experienced users.

--
Tayo'y Mga Pinoy



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux