Date: Wed, 31 Dec 2008 10:42:00 +0100 From: "Simon L. Nielsen" <simon@FreeBSD.org> To: Max Laier <max@love2party.net> Cc: freebsd-current@freebsd.org, cperciva@freebsd.org Subject: Re: portsnap corrupted Message-ID: <20081231094159.GA964@zaphod.nitro.dk> In-Reply-To: <200812302213.07155.max@love2party.net> References: <200812301616.11132.max@love2party.net> <20081230203340.GB933@zaphod.nitro.dk> <200812302213.07155.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2008.12.30 22:13:06 +0100, Max Laier wrote: > On Tuesday 30 December 2008 21:33:41 Simon L. Nielsen wrote: > > On 2008.12.30 16:16:10 +0100, Max Laier wrote: > > > long story short: a clean "portsnap fetch && portsnap extract" doesn't > > > extract all ports that should be there according to cvsweb and others. > > > > > > I noticed via x11/listres, but there are plenty others - see attached > > > (grep -v -1 ^/ > porterror). > > > > Hey, > > > > I just tried using -d and -p to portsnap to fetch a new dir and > > everything worked fine. Do you have log from portsnap fetch? > > attached - done just now in an empty directory. I also did a "portsnap fetch" > on the normal db to the same point in time and diffed the two directories - > they are the same. Strange - which FreeBSD version are you using? (I tested on 8-CURRENT i386 from yesterday.) > If you like I can tar it up for you and put it somewhere for analysis. Yes please. Just dump it on freefall etc. -- Simon L. Nielsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081231094159.GA964>