On 01 Nov 2016, at 19:57 , Rainer Müller <rai...@macports.org> wrote:
> On 2016-11-01 19:50, Clemens Lang wrote: >> On Tue, Nov 01, 2016 at 07:09:48PM +0100, Marko Käning wrote: >>> how can I convince rev-upgrade to actually rebuild broken ports if >>> 'revupgrade_mode' is set to ‘report' in macports.conf? >> >> You can specifically rebuild them manually using port -nf upgrade $port. > > Never use the global force option -f with upgrade, but instead: > > sudo port -n upgrade --force $port > > The local --force was specifically added to only force the upgrade, but > do not apply force to any other phase. In case of variant mismatches, > the global 'port -f' will continue although the state in the work/ > directory is inconsistent. In case of activation conflicts, the global > 'port -f' will blindly overwrite existing files. Jeez, thanks, guys, for the pointers! I haven’t thought about that an individual upgrade would do the job just fine. But here I see that even that isn’t that easy... This should be in the wiki, man page and our Guide! Marko _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
