--On June 8, 2014 at 11:38:37 AM -0400 Kevin Phair <phair.ke...@gmail.com>
wrote:
On 6/8/14, 11:20 AM, Paul Schmehl wrote:
--On June 7, 2014 at 11:16:04 PM +0200 olli hauer <oha...@gmx.de> wrote:
Do you see which port is looping?
Perhaps a port was moved / renamed / removed and portmaster therfore is
looping around
Sadly I cannot help more since I used all the years tinderbox /
poudriere
to build packages.
I've been working on this for two days now, so the parameters have
changed a bit. But here's an example of what prompted my question:
This is the result of portmaster -ad
===>>> All >> (18)
[[stuff]]
===>>> Proceed? y/n [y] n
This is the result of pkg upgrade -n
# pkg upgrade -n
Updating repository catalogue
Upgrades have been requested for the following 150 packages:
[[different stuff]]
The upgrade will require 426 MB more space
373 MB to be downloaded
Clearly portmaster and pkg upgrade disagree on what work needs to be
done.
Do you have non-default port options configured? I believe the packages
are all created with the default options, so that if you've installed
everything from ports, and some of those ports with non-default options,
your dependencies when upgrading with portmaster could end up looking
different than when upgrading with pkg.
Yes, I do have a few ports with none-default options. The problem is,
they're critical ports (like apache22).
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson
"There are some ideas so wrong that only a very
intelligent person could believe in them." George Orwell
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
