On Friday 28 October 2005 00:25, Andrew P. wrote:
> On 10/28/05, Michael C. Shultz <[EMAIL PROTECTED]> wrote:
> > On Thursday 27 October 2005 18:49, Eric F Crist wrote:
> > > On Oct 27, 2005, at 8:32 PM, John DeStefano wrote:
> > > > On 10/27/05, Andrew P. <[EMAIL PROTECTED]> wrote:
> > > >> On 10/27/05, John DeStefano <[EMAIL PROTECTED]> wrote:
> > > >>> After clearing out the ports, updating ports (with portsnap) and
> > > >>> source, and rebuilding the system and kernel... it seemed the
> > > >>> ultimate
> > > >>> problem was actually a dependency of the package to apache1.3.
> > > >>> After I
> > > >>> ran 'pkgdb -F' and "fixed" this dependency to point to apache2.1,
> > > >>> but
> > > >>> I still had trouble installing ports.
> > >
> > > At this point, what usually works for me is to:
> > >
> > > #cd /usr && rm -rf ./ports
> > >
> > > #mkdir ./ports && cvsup /root/ports-supfile
> > >
> > > The above will delete your ENTIRE ports tree, provided it's kept in /
> > > usr/ports and as long as you use cvsup (and your ports supfile is /
> > > root/ports-supfile as mine is). When a whole bunch of ports stop
> > > working, I find this is the easiest thing to do.
> > >
> > > The other thing I do is run a cron job every week that updates, via
> > > cvsup, the ports tree. About once a year I perform the above, mostly
> > > to clean out the crap. Re-downloading your entire ports tree will be
> > > quicker if you don't use the ports-all tag and actually define which
> > > port segments you are interested in. For example, there's no real
> > > reason to download all the x11/kde/gnome crap if you're doing this on
> > > a headless server that isn't going to serve X.
> > >
> > > HTH
> >
> > Replacing /usr/ports won't fix his problems, they reside in /var/db/pkg.
> > I may be a bit biased but I reaaly think John D. should try running
> > portmanager -u (ports/sysutils/portmanager). Stale dependencies is a non
> > issue for portmanager.
> >
> > -Mike
> >
>
> I don't think that stale dependencies are an issue for
> portupgrade as well, just add "-O" to the command-
> line.
From portupgrade's man page:
-O
--omit-check Omit sanity checks for dependencies. By default,
portupgrade checks if all the packages to upgrade
have consistent dependencies, though it takes
extra time to calculate dependencies. If you are
sure you have run ``pkgdb -F'' in advance, you can
specify this option to omit the sanity checks.
Seems to be a caveat to the -O command. What happens if pkgdb -F
isn't run first?
-Mike
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
