Date: Mon, 11 Jul 2011 12:41:46 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: FreeBSD-gnats-submit@freebsd.org Cc: ports@freebsd.org, dougb@freebsd.org Subject: ports-mgmt/portmaster: CONFLICTS trigger unterminated recursion-unto-self Message-ID: <E1QgDvu-0003i5-6P@apollo.emma.line.org>
next in thread | raw e-mail | index | archive | help
>Submitter-Id: current-users >Originator: Matthias Andree >Organization: FreeBSD >Confidential: no >Synopsis: ports-mgmt/portmaster: CONFLICTS trigger unterminated recursion-unto-self >Severity: serious >Priority: low >Category: ports >Class: sw-bug >Release: FreeBSD 8.2-STABLE amd64 >Environment: System: FreeBSD apollo.emma.line.org 8.2-STABLE FreeBSD 8.2-STABLE #6: Fri Jul 8 05:16:49 CEST 2011 toor@apollo.emma.line.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Hi Doug, portmaster cannot handle the recent www/p5-libwww update. It recurses unto itself as a dependency but never starts building. It's sufficient to run "portmaster p5-libwww" to trigger this. What I've figured is that the conflicts handling might be the culprit. Look: www/p5-libwww depends on net/p5-Net-HTTP >= 6. net/p5-Net-HTTP conflicts with www/p5-libwww-5*. portmaster evaluates this conflict, sees that p5-libwww-5* is installed, and decides "dependency for p5-Net-HTTP seems to be handled by p5-libwww." Suggestion: if the conflict is with a currently to-be-upgraded port, but not with the upgraded port any more, just ignore the conflicts marker. Alternative: if some port the current upgrade depends on gets upgraded and would then no longer be a conflict, let portmaster deinstall (in this case) libwww, build the dependency, then install the current port. >How-To-Repeat: >Fix:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1QgDvu-0003i5-6P>