Date: Sat, 29 Oct 2005 09:10:17 -0500 From: Eric F Crist <ecrist@secure-computing.net> To: John DeStefano <john.destefano@gmail.com> Cc: "Michael C. Shultz" <ringworm01@gmail.com>, freebsd-questions@freebsd.org Subject: Re: portupgrade stale dependencies Message-ID: <19A2A3C1-0592-46BB-BA29-6476DD300FEF@secure-computing.net> In-Reply-To: <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com> References: <f2160e0d0510151746n28cdbb25s2150337c0c6f7cfc@mail.gmail.com> <6FB767AE-D4D7-4C38-90C0-726D48AF5654@secure-computing.net> <f2160e0d0510281731u268c1f75y82ec93a0ed08ad40@mail.gmail.com> <200510281922.16495.ringworm01@gmail.com> <f2160e0d0510281951s541d3d9ft808d36b023fa9661@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I ended up deinstalling that apache installation (which I was not keen > on doing), and installing the apache20 port (which was the same > version (2.0.55) as the apache2 port <?>), and, thankfully, it's > working fine. I'm also now able to run both 'pkgdb -F'and 'portsdb > -Uu' without ANY errors (except for a few 'Duplicate INDEX entry' > warnings). > > Needless to say, this process wasn't much fun. What can I do to keep > this from happening again? What can/can't I safely include in cron to > automate database and index maintenance? > > Thanks to all. What I do for critical system ports is a manual upgrade. I have never trusted any of the port management tools. I suggest you pay attention to bugtracker and some other sites. When you see a compelling reason to upgrade, do it manually. The process I use is what I described in an earlier post: #cd /usr/ports/port-to-upgrade && make deinstall #make install #<restart whatever port I just upgraded> HTH ----- Eric F Crist Secure Computing Networks http://www.secure-computing.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19A2A3C1-0592-46BB-BA29-6476DD300FEF>