Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 Jun 2007 13:05:14 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        Ade Lovett <ade@FreeBSD.org>
Cc:        ports@freebsd.org, Warner Losh <imp@harmony.bsdimp.com>, Kris Kennaway <kris@obsecurity.org>
Subject:   Re: Uggg!
Message-ID:  <20070601170514.GA54912@rot13.obsecurity.org>
In-Reply-To: <10723ADA-FD53-45F8-BDFA-DBD98CBC212E@FreeBSD.org>
References:  <200706010521.l515LE4N074880@harmony.bsdimp.com> <20070601085750.ang0g5aqp0kg8c8k@webmail.leidinger.net> <20070601083345.GA48323@rot13.obsecurity.org> <10723ADA-FD53-45F8-BDFA-DBD98CBC212E@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 01, 2007 at 02:15:48AM -0700, Ade Lovett wrote:
> 
> On Jun 01, 2007, at 01:33 , Kris Kennaway wrote:
> >Download the packages from the FTP site and either reinstall them or
> >extract the +CONTENTS.  This will work best if you don't have local
> >make.conf customizations, otherwise you will see variance.
> 
> Actually, this does bring up a meta-issue that ports, pkgsrc,  
> portage, all suffer from.
> 
> What happens when the metadata gets blown away (by accident, hardware  
> crash, flaming meteor from Mars, etc.)
> 
> Is there anything we can do to mitigate this?
> 
> Yes.  It's an open-ended question.  I also have no obvious solution.   
> But I do see the need for such.

I am not really sure there is a solution: unless the user has used a
precompiled "standard" package is not just representing data that is
cached from somewhere else and can be reconstructed, it is usually
unique to a particular build.  Even if they use a standard package it
may have changed in the meantime.

Best solution is to back up /var/db/pkg if it is in danger of deletion
by a wanton admin :)

Kris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070601170514.GA54912>