For instance, I've had this problem with mod_fcgid and apache.If there is an upgrade of apache, then the compilation ends on a conflict between mod_fcgid and apache.
So we can conclude that this is a general ports collection's problem.
Usually, I noticed there are two main reasons for this: 1) A port change its name (eg tools-foobar becomes foobarutils).
Then it's obvious that the "tools-foobar" must be uninstalled before attempting the ports upgrade.
*** Error code 1 Stop in /usr/ports/print/texlive-scheme-full This situation is a bit confusing.
I don't know how to resolve the problem with texlive, there are so many dependencies... Is there any trick to bypass this kind of problem ?
Any option of make that could tell which files to keep, for instance ? Hello, First of all, I don't use portshaker, but I encountered the problem with files conflicting, several times.Usually I notice it when upgrading my whole ports collecion (which for me is portmaster -ad)..*** Error code 1 Stop in /usr/ports/print/texlive-bibtex.*** Error code 1 Stop in /usr/ports/print/texlive-scheme-full.Installing texlive-texlive-scripts-20130107...pkg: texlive-texlive-scripts-20130107 conflicts with texlive-core-20120628 (installs files into the same place).Problematic file: /usr/local/share/texmf/scripts/texlive/*** Error code 70 Stop in /usr/ports/print/texlive-texlive-scripts.