Git-Url: http://git.frugalware.org/gitweb/gitweb.cgi?p=frugalware-current.git;a=commitdiff;h=489abdf357e43f8adcc9f46ad2ca1080cec0c08e
commit 489abdf357e43f8adcc9f46ad2ca1080cec0c08e Author: Miklos Vajna <[EMAIL PROTECTED]> Date: Mon Jan 21 00:14:46 2008 +0100 docs/develfaq: added how do i repair a corrupted fdb diff --git a/docs/develfaq.txt b/docs/develfaq.txt index bb12e2a..2087f5e 100644 --- a/docs/develfaq.txt +++ b/docs/develfaq.txt @@ -187,3 +187,17 @@ custom commands, then you always have to use them. * If your change affects only the FrugalBuild (like an up2date fix) then you should not, just push your change. * If your change affects only the fdb (like options=(\'force\') or replaces()) then you should repoman cl after the push but no incrementing is needed * In any other case: you should do so. + +== How do I repair a corrupted package database? + +Restore a backup from the `/pub/other/fdb-snapshot` directory, and check what +its version (the `.version` file in the tarball). + +Then run: + +---- +$ for i in `git log --pretty=oneline 94a41e0..|sed 's/^[^ ]* \([^ ]*\).*/\1/'\ + |sed 's/-[^-]*-[^-]*-[^-]*$//'`; do ls ../source/*/$i &>/dev/null \ + || continue; updatesync upd frugalware-current.fdb \ + ../source/*/$i/FrugalBuild; done +---- _______________________________________________ Frugalware-git mailing list [email protected] http://frugalware.org/mailman/listinfo/frugalware-git
