Still no traceback for ports conflicts during "pkg upgrade"
zaphod at berentweb.com
Sun Dec 29 21:25:22 UTC 2013
I am getting several ports conflicts when doing a "pkg upgrade". The most
obvious example is lang/gcc vs lang/gcc46:
pkg: WARNING: locally installed gcc-4.6.4 conflicts on
with: - gcc46-4.6.4_1,1
As I had requested previously, "There needs to be an -x (exclude) flag or
better yet a traceback method for pkg upgrade" so that one can trace the
port causing the issue. lang/gcc46 is not the only port causing such
I admit that one of the possible causes could be that I marcusmerge the
gnome3 ports. However, this does not make my request any less sensible,
since there will probably be many other development branches in the future.
View this message in context: http://freebsd.1045724.n5.nabble.com/Still-no-traceback-for-ports-conflicts-during-pkg-upgrade-tp5872335.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
More information about the freebsd-ports