Skip to Content.
Sympa Menu

sm-grimoire - Re: [SM-Grimoire] Gurus Bugzilla

sm-grimoire AT lists.ibiblio.org

Subject: Discussion of Spells and Grimoire items

List archive

Chronological Thread  
  • From: "Sergey A. Lipnevich" <sergey AT optimaltec.com>
  • To: Hamish Greig <hgreig AT bigpond.net.au>
  • Cc: sm-grimoire AT lists.ibiblio.org
  • Subject: Re: [SM-Grimoire] Gurus Bugzilla
  • Date: Mon, 01 Dec 2003 23:11:32 -0500

Hamish Greig wrote:

On Mon, 1 Dec 2003 08:28, Sergey A. Lipnevich wrote:

We may want to enable Keywords feature in Bugzilla and mark those issues
with a keywords so that they're easy to find. What do you think?


This is probably a good idea.
[short version]
A lot of the bugs I read I can tell the error just from experience(simple depends, gcc related errors and such) so the summary is also the necessary bugfix. What should I use as a keyword then ? FIXME ? FOUND ? POOPY ?

Please, not the last one. Let's keep it a safe place for kids. All of the bugs are "fixme", "found" doesn't make sense I think. How about "bite-size" or "quickfix"?

[longer version]
for all three prometheus machines I am running, I check bugzilla atleast once a day and look through the errors and reassign them to the right section.

That's great work BTW, thank you!

Often I recognise duplicates and I then mark them as such AND close them (to avoid hassle later). eg. sorcery using make -k on the makefile it generates (so trying to cast kdelibs and kdenetwork the same qt-x11 error will show up) or same bug different host.

Cool.

Normally I look through the bug, find the error and use that error in the summary. Occasionally the actual error isn't listed in the bug and I must download, unzip and read the castlog.bz2.

I hate attachments that make you download and open them. But isn't that correct that a huge part of the Prometheus output is pasted into the initial bug description?

Probably 70% of the time the summary is the fix also.
Guru's *can* close bugs (with good reason) if they see them as invalid after reassigning, but you must tell me (so I can add that spell to the ignore list) or the same bug will keep being reported.

OK. I'd volunteer for reviewing the bugs submitted via Prometheus, is there an easy way to filter out the new ones?

Guru's can reassign bugs if they feel it is more relevant to another section or to sorcery itself or even an ISO issue.

OK.

I am cc-ed on all prometheus bugs so if a bugfix needs integrating from test into stable just note that in the bug when ready.

OK.

Please don't become upset if I assign the same (a duplicate) bug to you or your section twice. Today (after two days away over the weekend) I have around 150 bugs to peruse from prometheus. Because there are so many I might miss some duplicates or even assign them to the wrong section ( ie focus on the wrong error). Some are not bugs but local machine errors (I haven't fully stabilised my cluster distcc/ccache problems yet).
Apologies in advance.

I'm sure nobody would mind. Care to assign a random share of bugs to sergey AT sourcemage.org without looking at them?

If you get assigned a bug that has "file not recognized: File truncated
collect2: ld returned 1 exit status" that is actually an error from my distcc/ccache/nfs/openmosix setup and you should not try to fix it :)

We'll have to fix you :-).

any questions/ flames/ masonic rituals ?

Can't think of any :-).

Hamish
ps some help scanning bugs, summarising them and reassigning them would be helpful, just leave the games grimoire bugs for me, they are very low priority.

Hit me.





Archive powered by MHonArc 2.6.24.

Top of Page