portsnap corrupted
Guido Falsi
mad at madpilot.net
Wed Dec 31 09:29:03 UTC 2008
On Tue, Dec 30, 2008 at 10:13:06PM +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.
>
> If you like I can tar it up for you and put it somewhere for analysis.
I'm seeing the same problem on a test machine with 8-current here.
The problem is not showing up on 7.x though.
--
Guido Falsi <mad at madpilot.net>
More information about the freebsd-current
mailing list