From nobody Wed Oct 27 09:00:57 2021 X-Original-To: python@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4E6F2182A11C for <python@mlmmj.nyi.freebsd.org>; Wed, 27 Oct 2021 09:00:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HfN2f1QFLz3mXj for <python@FreeBSD.org>; Wed, 27 Oct 2021 09:00:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 122A351B7 for <python@FreeBSD.org>; Wed, 27 Oct 2021 09:00:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 19R90wkM002154 for <python@FreeBSD.org>; Wed, 27 Oct 2021 09:00:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 19R90wrf002153 for python@FreeBSD.org; Wed, 27 Oct 2021 09:00:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 259456] www/mitmproxy: 7.0.2 fails to run: pkg_resources.DistributionNotFound: The 'zstandard<0.16,>=0.11' distribution was not found Date: Wed, 27 Oct 2021 09:00:57 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: p5B2E9A8F@t-online.de X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: lwhsu@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: <bug-259456-21822-XGjGnSvXUF@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-259456-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-259456-21822@https.bugs.freebsd.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: FreeBSD-specific Python issues <freebsd-python.freebsd.org> List-Archive: https://lists.freebsd.org/archives/freebsd-python List-Help: <mailto:python+help@freebsd.org> List-Post: <mailto:python@freebsd.org> List-Subscribe: <mailto:python+subscribe@freebsd.org> List-Unsubscribe: <mailto:python+unsubscribe@freebsd.org> Sender: owner-freebsd-python@freebsd.org X-BeenThere: freebsd-python@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259456 --- Comment #3 from p5B2E9A8F@t-online.de --- At least to me it makes almost none sense pinning maximum versions of dependencies. This practice leads to frequently broken ports, which *must n= ot* be our primary goal in a dynamic environment of dependencies and using dependencies whenever possible. Our goal *should* be maintaining ports with the most little efforts possibl= e as we have already a huge workload. Pinning maximum versions makes sense if it is already known that a coming version of a dependency will break something. The fear that it might always= be possible is not a sufficient reason. At some places it has become a questionable practise instead. It *should not* need to be mentioned that repairing broken ports have prior= ity over delaying, waiting for something, or following policies that tend to mo= unt problems.=20=20 It is a known problem with Python apps running frequently in dependency failures. This has become to such a plague that it has become an almost gen= eral recommendation using virtual environments. There is a general need to discu= ss that development affecting the large number of FreeBSD-Python-ports having = to be maintained.=20 The www/privoxy port is a general example for breaking frequently and it ha= s a history being broken even for months. I'm *not* pointing to the port-mainta= iner here. It is a phenomenon that needs to be addressed in a more general way f= or maintaining the ports. --=20 You are receiving this mail because: You are on the CC list for the bug.=