| 1 |
(First, I don't care how the autoconf.in->autoconf.ac migration is |
| 2 |
handled at a code level. This isn't about that. I'd appreciate if that |
| 3 |
were largely handled in a separate thread. This (I think) is about |
| 4 |
policy around bug reporting.) |
| 5 |
|
| 6 |
Timeline: |
| 7 |
|
| 8 |
1) *Bug 426262* <https://bugs.gentoo.org/show_bug.cgi?id=426262> was filed |
| 9 |
2) SpanKY <mailto:vapier@g.o> |
| 10 |
committedhttp://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166 |
| 11 |
, and marked #426262 RESOLVED/FIXED, with the intent of flushing out |
| 12 |
configure.in use cases. |
| 13 |
<http://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166> |
| 14 |
3) I hit SpanKY's eqawarn, and filed #530478. |
| 15 |
4) Jer marked #530478 as a dupe of #426262, which was still marked #426262. |
| 16 |
5) Being the only one who's apparently filed anything following this |
| 17 |
eqawarn, I kicked off an emerge -e @world to trawl for more use cases on |
| 18 |
my system. (I'd rather not have my system break when autotools is |
| 19 |
eventually upgraded.) |
| 20 |
|
| 21 |
(then there's a spat between Justin Lecher and Jer, but that's not |
| 22 |
relevant yet.) |
| 23 |
|
| 24 |
I'm confused about two things. |
| 25 |
|
| 26 |
First, if something is supposed to have attention paid to it (which I |
| 27 |
take to be the purpose of the eqawarn), I don't see how it makes sense |
| 28 |
for bug reports responding to the eqawarn to be marked as duplicate of a |
| 29 |
bug that's in the RESOLVED/FIXED state; who's going to pay attention to |
| 30 |
that, in the general case? (In this case, Justin saw it, unmarked the |
| 31 |
dupe, set up a tracker for the issue and marked my bug as a blocker for |
| 32 |
that.) |
| 33 |
|
| 34 |
Second, having my bug report marked as a dupe of one already in the |
| 35 |
RESOLVED/FIXED state tells me that my bug report was a waste of time. |
| 36 |
Reading the content of #426262 suggests to me that any further filings |
| 37 |
will also be marked as duplicates of the RESOLVED/FIXED bug, and thus |
| 38 |
also wastes of time. I don't mind burning a few CPU cycles if it's |
| 39 |
useful, but if it's just going to waste time, there's obviously no |
| 40 |
point, and I should kill the emerge I started. |
| 41 |
|
| 42 |
So...could I get some clarification here? I don't get the dupe-marking |
| 43 |
pattern, and I don't know whether or not I should kill off my emerge -e. |
| 44 |
<http://sources.gentoo.org/eclass/autotools.eclass?r1=1.165&r2=1.166> |
Archives