From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1M35Ds-00056m-Dq for garchives@archives.gentoo.org; Sun, 10 May 2009 09:21:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D0C88E023C; Sun, 10 May 2009 09:21:25 +0000 (UTC) Received: from mail-ew0-f165.google.com (mail-ew0-f165.google.com [209.85.219.165]) by pigeon.gentoo.org (Postfix) with ESMTP id 905BAE023C for ; Sun, 10 May 2009 09:21:25 +0000 (UTC) Received: by ewy9 with SMTP id 9so2776869ewy.34 for ; Sun, 10 May 2009 02:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=itOvq9w6XHcYk2mYqvvXmg3kFZHCBamEJvK9Doktuos=; b=JoumiXQgMaqUD1Gp5cFvhMtOqmL2yXJnhGrXNaPjl0SJUtzVc1Vh5ywGY6IKTjGIs/ P1Morby348Wi0hu+G/fvwralJpR+Z9nGJVs0SfKJXhbhb5J1+ZxLyXMzUJIGF/95kah+ A/Sc6/PUzcA8vp+CJbGz/404CUn54uzLTAQ3M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=e97yVayweqXFSZo1/TQNSvIc39tGekRJYeDI+ruBeDRc6lN5MOQm7rMmbQvYn/8OHQ Mppgj3jdpwSTcY1H1r997+mB3jJljVjDuZTDz5bTFS/qhk0K3ad7RKKoylP68ciAaJ3B v/5mJ4PRGc7MTernQ8RJpfc0P5/8B97T0aRrc= Received: by 10.210.105.8 with SMTP id d8mr7155869ebc.70.1241947284533; Sun, 10 May 2009 02:21:24 -0700 (PDT) Received: from ?192.168.0.2? (5ad0d224.bb.sky.com [90.208.210.36]) by mx.google.com with ESMTPS id 5sm5359299eyh.40.2009.05.10.02.21.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 10 May 2009 02:21:22 -0700 (PDT) From: David Leverton To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] `paludis --info' is not like `emerge --info' Date: Sun, 10 May 2009 10:21:20 +0100 User-Agent: KMail/1.9.9 References: <20090218232212.5452b86d@epia.jer-c2.orkz.net> <20090509211459.GC4903@dodo.hsd1.nj.comcast.net> <8b4c83ad0905092023n61f4933jd844ad2f0681203d@mail.gmail.com> In-Reply-To: <8b4c83ad0905092023n61f4933jd844ad2f0681203d@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905101021.20505.levertond@googlemail.com> X-Archives-Salt: 4c3001ef-7060-48c9-82f1-9731bdd9e85a X-Archives-Hash: 6188f7dbb1ab4b04bc42fdcbbae93b4d On Sunday 10 May 2009 04:23:25 Nirbheek Chauhan wrote: > 1. It was a paludis bug, of course paludis --info came in handy (are > you trying to jest? ;p) It's most likely not a Paludis bug; do you really think that no-one's ever tried to compile Qt4 on amd64 with Paludis until now? I'm guessing a misconfiguration, but we'll have to wait for the real paludis --info output (NOT emerge --info, because that doesn't say anything about the Paludis configuration) to be sure. > 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 It's useful and relevant if and only if it contains information that helps diagnose the problem. In the likely event that it's a misconfiguration, that applies to paludis --info, but probably not emerge --info, unless he made the same mistake with both. > 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 If anything, that's a point in favour of tanderson's argument. If the --info the user had posted had been right, then both the paludis and emerge output are equally useful, because they both indicate that it isn't an amd64 system at all. On the other hand, if it turns out that on the correct system, Paludis is misconfigured and Portage isn't, then only paludis --info will help.