ports-mgmt/portmaster: CONFLICTS trigger unterminated
recursion-unto-self
Matthias Andree
mandree at FreeBSD.org
Mon Jul 11 14:41:26 UTC 2011
>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 at 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:
More information about the freebsd-ports
mailing list