From owner-freebsd-stable Fri May 11 15: 8:16 2001 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (216-118-21-146.pdq.net [216.118.21.146]) by hub.freebsd.org (Postfix) with ESMTP id B4CA537B424 for ; Fri, 11 May 2001 15:08:11 -0700 (PDT) (envelope-from dwcjr@inethouston.net) Received: from dwcjr (DWCJR.inethouston.net [216.118.21.147]) by leviathan.inethouston.net (Postfix) with ESMTP id E1DFC10F40F; Fri, 11 May 2001 17:08:11 -0500 (CDT) Message-ID: <061901c0da66$8da39040$931576d8@inethouston.net> From: "David W. Chapman Jr." To: "Roelof Osinga" , "Rasputin" Cc: References: <3AF9F4E8.52A31C48@eboa.com> <20010510050737.A2285@xor.obsecurity.org> <3AFB3C14.A6FB45AA@eboa.com> <20010511094813.A20755@dogma.freebsd-uk.eu.org> <3AFC565D.AECE9C5F@eboa.com> Subject: Re: What gives? Date: Fri, 11 May 2001 17:05:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The most common thing I find is leftovers, like a Makefile.inc or a work directory, do a make clean on them, I periodically do a make clean in /usr/ports. I know there is probably a more efficient way to do it, but I just let it go for a while. You could also do it before you install somethings, just do a make clean install, because it also cleans the dependencies. ----- Original Message ----- From: "Roelof Osinga" To: "Rasputin" Cc: Sent: Friday, May 11, 2001 4:15 PM Subject: Re: What gives? > Rasputin wrote: > > > > >... > > > -rw-r--r-- 1 root wheel 1955761 May 10 00:30 gnome > > > -rw-r--r-- 1 root wheel 636835 May 10 02:46 kde2 > > > > Freaky - those two both work for me. > > > > > Sounds like your ports tree is shafted, because the ports work for others. > > Interesting suggestion. Never mind the obvious 'how could it have > been shafted?', but rather point out how one can verify the state > of ones port collection. Please :). > > Each tarball has an unique MD5 hash. Each port release has the distinfo > file with the MD5's it has been based upon. Hence each port can verify > if the tarball fetched is the right one. Alternatively it can check > if needed needed stuff like libs or execs are present. > > Yet how can a sysop check the correctness of the collection itself? > As well as supporting utilities, of course. Just wipe /usr/ports and > refetch the whole shebang? Coupled with a CVSup of the source, is it > advisable to also wipe the /usr/src tree? Or are there diagnostic tools? > > Would be nice since that would be a nice first step in the diagnostic > process. > > Roelof > > -- > _______________________________________________________________________ > eBOAź est. 1982 > http://eBOA.com/ tel. +31-58-2123014 > mailto:info@eBOA.com?subject=Information_request fax. +31-58-2160293 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message