From owner-freebsd-ports@freebsd.org Fri May 14 01:35:28 2021 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 089AB63540F for ; Fri, 14 May 2021 01:35:28 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "www.zefox.com", Issuer "www.zefox.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FhB1B5gyVz4ZNv for ; Fri, 14 May 2021 01:35:26 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.16.1/8.15.2) with ESMTPS id 14E1ZJ5H047420 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for ; Thu, 13 May 2021 18:35:19 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.16.1/8.15.2/Submit) id 14E1ZIgf047419 for freebsd-ports@freebsd.org; Thu, 13 May 2021 18:35:18 -0700 (PDT) (envelope-from fbsd) Date: Thu, 13 May 2021 18:35:18 -0700 From: bob prohaska To: FreeBSD ports Subject: Python 37/38 conflict, was Re: Trubles compiling lxqt on RPi4 Message-ID: <20210514013518.GA46967@www.zefox.net> References: <515FCC01-19A2-463C-8416-85D0BF0B4845.ref@yahoo.com> <515FCC01-19A2-463C-8416-85D0BF0B4845@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <515FCC01-19A2-463C-8416-85D0BF0B4845@yahoo.com> X-Rspamd-Queue-Id: 4FhB1B5gyVz4ZNv X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of fbsd@www.zefox.net has no SPF policy when checking 50.1.20.27) smtp.mailfrom=fbsd@www.zefox.net X-Spamd-Result: default: False [-0.74 / 15.00]; RCVD_TLS_ALL(0.00)[]; ARC_NA(0.00)[]; WWW_DOT_DOMAIN(0.50)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RBL_DBL_DONT_QUERY_IPS(0.00)[50.1.20.27:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; DMARC_NA(0.00)[zefox.net]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; SPAMHAUS_ZRD(0.00)[50.1.20.27:from:127.0.2.255]; NEURAL_HAM_MEDIUM(-0.82)[-0.820]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.82)[-0.817]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7065, ipnet:50.1.16.0/20, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_WWW(0.50)[]; MAILMAN_DEST(0.00)[freebsd-ports] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 May 2021 01:35:28 -0000 On Thu, May 13, 2021 at 01:35:50PM -0700, Mark Millard wrote: > You have apparently chosen to build/update ports via a > technique that requires you to manage the dependencies, at > least some of the time. (Not that when is necessarily > obvious up front.) > You give me too much credit 8-) > Your environment is now based on a mix of python37 and > python 38 related materials. You are likely going to > need to rework/rebuild/reinstall things to avoid that. > > Hints may come from that UPDATING that I quoted but > things are more broken overall than what UPDATING is > intended to cover. You might end up needing to > uninstall a bunch of stuff until python is unused > (or only one python is used) and then follow the > notes if you have only python37 use and want to > get to python38. Finally rebuild/reinstall what > was uninstalled, based on python38 as a context. > Trying to deinstall both python37 and python38 didn't suffice. Python38's reinstall fails with the same conflict. Deleting the offending file doesn't help If other things need to be deinstalled it's not clear what they might be. > Due to how I build/install ports, I've not had to deal > with ending up with the mix so I'm not familiar with > the details for recovering from a messy mix. > Would use of poudriere help with this sort of problem? It isn't trivial to configure, but this sort of difficulty has been growing ever worse. I didn't want to deal with the complexity and overhead, but maybe it's time. Many thanks for patient counsel! bob prohaska