An 11/30/06, cwaeth Albert Shih <[EMAIL PROTECTED]>:
 Le 30/11/2006  13:04:33+0000, Chris a écrit
> Try "man pkgdb". Specifically "pkgdb -F".


     The pkgdb command is a tool to create or update the system package data-
     base which is used by the portupgrade(1) tool suite.  It maintains a hash
     that maps an installed file to a package name, a hash that maps a package
     to an origin, and a list of installed packages.

It's not my database is corrupt, but really my


for example

[EMAIL PROTECTED] /var/db/pkg]# ls -l firefox-2.0_2,1/
total 28
-rw-r--r--  1 root  wheel     52 12 nov 02:27 +COMMENT
-rw-r--r--  1 root  wheel    765 12 nov 02:27 +DEINSTALL
-rw-r--r--  1 root  wheel    345 12 nov 02:27 +DESC
-rw-r--r--  1 root  wheel   1119 12 nov 02:27 +DISPLAY
-rw-r--r--  1 root  wheel   1165 12 nov 02:27 +INSTALL
-r--r--r--  1 root  wheel  15305 12 nov 02:27 +MTREE_DIRS
-rw-r--r--  1 root  wheel     32 28 nov 23:37 +REQUIRED_BY
[EMAIL PROTECTED] /var/db/pkg]#

I don't have +CONTENT file....

Anyone can help me ?

The only cure I can think of is to reinstall the affected
packages/ports, since these (or those) are the files that
tell all (any) of the intended management tools what
actually is installed and where.

As an aside, backing up your /var/db/pkg will save you a
bit of trouble should something go wrong with the disk,
however in the event of a mangled upgrade it likely will
not, since the backup will not match what is on disk any-
more (or more to the point the backup will not match
what is needed for what was mangled by the mangler).

Probably still ought to take the backups with every updating.

A simple tar -jcf /backup/file/name.tar.bz2 /var/db/pkg/
for 301 packages took about 90 seconds and consumes
2.9M of disk space.  Not a lot of overhead there.  Excluding
/var/db/pkg/pkgdb.db (which would be rebuilt anyway) would
probably cut those figures in half.

_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to