public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] Duplicate bug reports, resolution status and Bug 426262
@ 2014-11-25 20:49 Michael Mol
  2014-11-29 14:51 ` Peter Stuge
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Mol @ 2014-11-25 20:49 UTC (permalink / raw
  To: gentoo-dev

(First, I don't care how the autoconf.in->autoconf.ac migration is
handled at a code level. This isn't about that. I'd appreciate if that
were largely handled in a separate thread. This (I think) is about
policy around bug reporting.)

Timeline:

1) *Bug 426262* <https://bugs.gentoo.org/show_bug.cgi?id=426262> was filed
2) SpanKY <mailto:vapier@gentoo.org>
committedhttp://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166
, and marked #426262 RESOLVED/FIXED, with the intent of flushing out
configure.in use cases.
<http://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166>
3) I hit SpanKY's eqawarn, and filed #530478.
4) Jer marked #530478 as a dupe of #426262, which was still marked #426262.
5) Being the only one who's apparently filed anything following this
eqawarn, I kicked off an emerge -e @world to trawl for more use cases on
my system. (I'd rather not have my system break when autotools is
eventually upgraded.)

(then there's a spat between Justin Lecher and Jer, but that's not
relevant yet.)

I'm confused about two things.

First, if something is supposed to have attention paid to it (which I
take to be the purpose of the eqawarn), I don't see how it makes sense
for bug reports responding to the eqawarn to be marked as duplicate of a
bug that's in the RESOLVED/FIXED state; who's going to pay attention to
that, in the general case? (In this case, Justin saw it, unmarked the
dupe, set up a tracker for the issue and marked my bug as a blocker for
that.)

Second, having my bug report marked as a dupe of one already in the
RESOLVED/FIXED state tells me that my bug report was a waste of time.
Reading the content of #426262 suggests to me that any further filings
will also be marked as duplicates of the RESOLVED/FIXED bug, and thus
also wastes of time. I don't mind burning a few CPU cycles if it's
useful, but if it's just going to waste time, there's obviously no
point, and I should kill the emerge I started.

So...could I get some clarification here? I don't get the dupe-marking
pattern, and I don't know whether or not I should kill off my emerge -e.
<http://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166>


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [gentoo-dev] Duplicate bug reports, resolution status and Bug 426262
  2014-11-25 20:49 [gentoo-dev] Duplicate bug reports, resolution status and Bug 426262 Michael Mol
@ 2014-11-29 14:51 ` Peter Stuge
  0 siblings, 0 replies; 2+ messages in thread
From: Peter Stuge @ 2014-11-29 14:51 UTC (permalink / raw
  To: gentoo-dev

Michael Mol wrote:
> 4) Jer marked #530478 as a dupe of #426262,

To me that looks bogus. #530478 is about app-office/dia while #426262
is about two eclasses.

Jeroen - please explain why you consider 530478 a duplicate of 426262?

I note that you did not do so in Bugzilla while marking the dupe, but
I think an explanation is very much warranted in this case.

I would have understood if you simply noted that 530478 was *related*
to 426262, but duplicate has a distinct and very different meaning. Right?

And please see if you can adopt a better tone. Your tone in

https://bugs.gentoo.org/show_bug.cgi?id=530478#c4

sounds quite nasty for no apparent reason. :\


//Peter


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-11-29 14:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-11-25 20:49 [gentoo-dev] Duplicate bug reports, resolution status and Bug 426262 Michael Mol
2014-11-29 14:51 ` Peter Stuge

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox