| 1 |
On Sun, May 10, 2009 at 2:44 AM, Thomas Anderson <gentoofan23@g.o> wrote: |
| 2 |
> Folks, I'd like to direct your attention to bug #269067. In this case, |
| 3 |
> had the bugwrangler(yngwin) asked for paludis --info the bug could have |
| 4 |
> been RESO INVALID without it getting to me. I wouldn't have wasted ~30 |
| 5 |
> minutes deciding that the user was being crazy. |
| 6 |
> |
| 7 |
> So yes, paludis --info can come in handy, and I found it useful in this |
| 8 |
> case. |
| 9 |
> |
| 10 |
|
| 11 |
1. It was a paludis bug, of course paludis --info came in handy (are |
| 12 |
you trying to jest? ;p) |
| 13 |
2. You found it useful because you knew the syntax, and where to look |
| 14 |
for what -- it is relevant to you. Not to everyone else |
| 15 |
3. Also, last comment on the bug: |
| 16 |
|
| 17 |
"The emerge --info and paludis --info I reported above are from the wrong |
| 18 |
machine. I'll update the results on Monday when I get back to the correct |
| 19 |
machine. It is a Xeon W5580 cpu which should be compiling as x86_64. I |
| 20 |
believe the bug is real. Sorry for the confusion." |
| 21 |
|
| 22 |
Oops? =p |
| 23 |
|
| 24 |
-- |
| 25 |
~Nirbheek Chauhan |
Archives