Date: Tue, 15 Mar 2005 22:28:11 +0000 (UTC) From: Adam Weinberger <adamw@FreeBSD.org> To: doc-committers@FreeBSD.org, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: www/en/gnome gnome_upgrade.sh Message-ID: <200503152228.j2FMSBxI007892@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
adamw 2005-03-15 22:28:11 UTC FreeBSD doc repository Modified files: en/gnome gnome_upgrade.sh Log: There have been a number of upgrade failure reports, and most of them seem to stem from external dependencies not getting updated. (Here, external dependencies are ports which do NOT depend upon glib20.) I'm suspecting that the cause of this is inconsistent package databases. Inconsistent pkgdbs will cause portupgrade(1) to silently fail, but portinstall and pkg_delete will still work just fine. (I really wish gnu had agreed to make pkgdb(1) return meaningful error codes -- or any error codes at all!) So, instead of running pkgdb -F, we're now running pkgdb -fu. This will hopefully rebuild the entire database from scratch, and leave us with a consistent database every time. And just in case, we follow it with a pkgdb -F for good measure. Additionally, I've changed the script's version number to be a bit more legible, and thus a bit more meaningful. Also, there is now a -v option which prints some basic version/revision information. I'd like to thank Alexandre Vasconcelos's horribly inconsistent package database for inspiring the pkgdb change ;;) Revision Changes Path 1.20 +30 -8 www/en/gnome/gnome_upgrade.sh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503152228.j2FMSBxI007892>