From owner-freebsd-ports@freebsd.org Wed Dec 11 07:08:24 2019 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9BCDE1CF132 for ; Wed, 11 Dec 2019 07:08:24 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ultimatedns.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 47Xp1M42Bwz3HFK; Wed, 11 Dec 2019 07:08:22 +0000 (UTC) (envelope-from portmaster@BSDforge.com) Received: from udns.ultimatedns.net (localhost [IPv6:0:0:0:0:0:0:0:1]) by udns.ultimatedns.net (8.15.2/8.15.2) with ESMTPS id xBB78Z9i087411 (version=TLSv1.2 cipher=DHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Tue, 10 Dec 2019 23:08:42 -0800 (PST) (envelope-from portmaster@BSDforge.com) X-Mailer: Cypht MIME-Version: 1.0 Cc: freebsd-ports In-Reply-To: From: Chris Reply-To: portmaster@BSDforge.com To: Jan Beich Subject: Re: python support appears broken in the ports trree Date: Tue, 10 Dec 2019 23:08:42 -0800 Message-Id: <4cf4b4e599fe40d9b61705064ebfa9e2@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 47Xp1M42Bwz3HFK X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of portmaster@BSDforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=portmaster@BSDforge.com X-Spamd-Result: default: False [-1.10 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[portmaster@BSDforge.com]; XM_UA_NO_VERSION(0.01)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-0.92)[-0.925,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[BSDforge.com]; REPLYTO_ADDR_EQ_FROM(0.00)[]; AUTH_NA(1.00)[]; IP_SCORE(-0.11)[ip: (-1.05), ipnet: 24.113.0.0/16(-0.52), asn: 11404(1.08), country: US(-0.05)]; TO_DN_ALL(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-0.98)[-0.977,0]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2019 07:08:24 -0000 On Wed, 11 Dec 2019 06:21:29 +0100 Jan Beich jbeich@FreeBSD=2Eorg said > Chris writes: >=20 > > I struggled all day yesterday with various ports barfing with similar > > python messages=2E So today I blew everything off the disk, and started > > from scratch=2E Which only repeats what happened yesterday=2E Is python > > multiplicity no longer available? Or? >=20 > See bug 233723 or bug 237795=2E Build each port separately instead of relyi= ng > on dependecy chaining should work=2E For best experience use poudriere=2E Thank you very much for the insight, Jan! Near as I can figure from the two bugs, I'm going to need to fix Mk/python=2Emk That should be a fun project=2E :P Thanks again! --Chris