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