Rebuilding /var/db/pkg
I committed a crime! While upgrading the ports under the newly installed RELENG_7 (beta4) with portupgrade -arRk I **deleted ** the directory /var/db/pkg. Is there any way to rebuild it from scratch? Ciao Vittorio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
vittorio wrote: I committed a crime! While upgrading the ports under the newly installed RELENG_7 (beta4) with portupgrade -arRk I **deleted ** the directory /var/db/pkg. Is there any way to rebuild it from scratch? Ciao Vittorio Nope, that was the only copy. Kris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
Kris Kennaway writes: I committed a crime! While upgrading the ports under the newly installed RELENG_7 (beta4) with portupgrade -arRk I **deleted** the directory /var/db/pkg. Is there any way to rebuild it from scratch? Nope, that was the only copy. Assuming there are no backups, he will have to rebuild from scratch. I see two approaches: I) Find complex leaf programs, like FireFox or OpenOffice. Build the port; this will drag in all the dependencies. II) a) Look in /usr/ports/distfiles, where all the distribution tarballs live. b) Prune the resulting list, so you're only trying to build one of any given port. c) Map the tarball name to the port. A discussion of how to do this happened within the last year on either questions@ or ports@, and may contain usable scripts. d) Lay in a good supply of your favorite caffeinated beverage, and set to work. In either case, design and implement a backup method. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
On Thursday 25 May 2006 19:03, John Nielsen wrote: Quoting Robert Huff [EMAIL PROTECTED]: Robertsen A. Riehle writes: Say that the /var/db/pkg directory had been recursively erased off of a workstation that had ~300 packages on it. And, let's hypothetically say that this workstation's ports tree was up to date as of yesterday. Is there any hope of rectifying this or is this workstation is a static ports state forever??? 1) Is there no back-up? 2) Unless you clear it regularly, look in Also if you act before the weekly(?) periodic script rebuilds the locate database, you could use the output of locate /var/db/pkg to help you determine what was there. This is really good idea except the locate database was already updated. /usr/ports/distfiles. On my system, I'd also check pkgtools.conf. Start with things with a lot of dependencies (OpenOffice, Mozilla, KDE/gnome, Java, Emacs, etc.) and reinstall by hand. It appears that this is really the only way to solve the problem. Except, if there is nothing in /var/db/pkg, make install does nothing. So, I tried pkg_add -r gcc41 and the following result revealed a more substantial problem. su-2.05b# pkg_add -r gcc41 (Before I compile all of KDE and find out that it didn't work, I decided to try something small...) Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/gcc41.tbz... /var: write failed, filesystem is full info/gcc41/gccint.info: Write error: No space left on device Done. ^C /var: write failed, filesystem is full Signal 2 received, cleaning up.. But su-2.05b# df -h /var Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s2d248M183M 45M80%/var Surely, a gcc package doesn't take up 45M. What is going on here? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
Robertsen A. Riehle writes: Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/gcc41.tbz... /var: write failed, filesystem is full info/gcc41/gccint.info: Write error: No space left on device Done. ^C /var: write failed, filesystem is full Signal 2 received, cleaning up.. But su-2.05b# df -h /var Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s2d248M183M 45M80%/var Surely, a gcc package doesn't take up 45M. Objection - fact not in evidence. I don't _know_ how much room gcc takes ... but if someone told me 45 megabytes I wouldn't disagree. Followup questions: 1) what is the output of du /var | sort -nr | head -n 40? 2) does lsof show any open files you don't recognize, or or have no reason to be open? Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Rebuilding /var/db/pkg
Say that the /var/db/pkg directory had been recursively erased off of a workstation that had ~300 packages on it. And, let's hypothetically say that this workstation's ports tree was up to date as of yesterday. Is there any hope of rectifying this or is this workstation is a static ports state forever??? wab ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
On Thu, May 25, 2006 at 05:55:55PM -0500, Robertsen A. Riehle wrote: Say that the /var/db/pkg directory had been recursively erased off of a workstation that had ~300 packages on it. And, let's hypothetically say that this workstation's ports tree was up to date as of yesterday. Is there any hope of rectifying this or is this workstation is a static ports state forever??? There is not (unless you go through by hand and figure out what was installed), this is why backups are necessary. Kris pgpw2GLSnsJS8.pgp Description: PGP signature
Rebuilding /var/db/pkg
Robertsen A. Riehle writes: Say that the /var/db/pkg directory had been recursively erased off of a workstation that had ~300 packages on it. And, let's hypothetically say that this workstation's ports tree was up to date as of yesterday. Is there any hope of rectifying this or is this workstation is a static ports state forever??? 1) Is there no back-up? 2) Unless you clear it regularly, look in /usr/ports/distfiles. On my system, I'd also check pkgtools.conf. Start with things with a lot of dependencies (OpenOffice, Mozilla, KDE/gnome, Java, Emacs, etc.) and reinstall by hand. Robert Huff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Rebuilding /var/db/pkg
Quoting Robert Huff [EMAIL PROTECTED]: Robertsen A. Riehle writes: Say that the /var/db/pkg directory had been recursively erased off of a workstation that had ~300 packages on it. And, let's hypothetically say that this workstation's ports tree was up to date as of yesterday. Is there any hope of rectifying this or is this workstation is a static ports state forever??? 1) Is there no back-up? 2) Unless you clear it regularly, look in /usr/ports/distfiles. On my system, I'd also check pkgtools.conf. Start with things with a lot of dependencies (OpenOffice, Mozilla, KDE/gnome, Java, Emacs, etc.) and reinstall by hand. Also if you act before the weekly(?) periodic script rebuilds the locate database, you could use the output of locate /var/db/pkg to help you determine what was there. JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
