Date: Sun, 19 Dec 2010 09:03:37 -0800 From: "Ron (Lists)" <rg.lists@rzweb.com> To: <freebsd-questions@freebsd.org> Subject: Portmaster recursion problem Message-ID: <e20a2fd2465d529ce801fa40a10b02ca@flabnapple.net>
next in thread | raw e-mail | index | archive | help
I recently switched from using portupgrade to portmaster and am having an odd problem upgrading. When I run 'portmaster apache' I get this recursion problem: ===>>> Port directory: /usr/ports/www/apache22 ===>>> Starting check for build dependencies ===>>> Gathering dependency list for www/apache22 from ports ===>>> Launching child to update devel/autoconf devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf >> perl-5.8.9_3 >> apache-2.2.17 >> devel/autoconf This just keeps going and going. I've tried upgrading other ports and they all do the same thing (with slightly different packages). What is very weird is the dependencies. For example, I run 'portmaster nano' and I get: ===>>> The following actions will be taken if you choose to proceed: Upgrade nano-2.2.5 to nano-2.2.6 Upgrade apache-2.2.17 to apache-2.2.17_1 Install devel/autoconf Upgrade autoconf-wrapper-20071109 to autoconf-wrapper-20101119 Upgrade perl-5.8.9_3 to perl-5.8.9_4 Install devel/libtool Upgrade openssl-1.0.0_2 to openssl-1.0.0_4 I'm not sure why nano is dependent on apache? This leads me to wonder is something is messed up in my dependencies, and if so, how do I fix it? I'd love to go back to using portupgrade, but it seems it is not longer maintained or functional (this reason I switched to portmaster). Thanks, Ron
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e20a2fd2465d529ce801fa40a10b02ca>