From nobody Sat Dec 4 22:05:11 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 336E7189A668
for <python@mlmmj.nyi.freebsd.org>; Sat, 4 Dec 2021 22:05:11 +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 4J63dy6L0tz3sYK
for <python@FreeBSD.org>; Sat, 4 Dec 2021 22:05:10 +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 BA95340EB
for <python@FreeBSD.org>; Sat, 4 Dec 2021 22:05:10 +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 1B4M5AQg051406
for <python@FreeBSD.org>; Sat, 4 Dec 2021 22:05:10 GMT
(envelope-from bugzilla-noreply@freebsd.org)
Received: (from www@localhost)
by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1B4M5AY5051405
for python@FreeBSD.org; Sat, 4 Dec 2021 22:05:10 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 259981] devel/py-setuptools_scm: Fix incorrect *_DEPENDS,
causing devel/py-pyparsing (and others) Fails to configure: The
'packaging>=20.0' distribution was not found
Date: Sat, 04 Dec 2021 22:05:11 +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: needs-patch, regression
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: se@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Resolution:
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: kai@FreeBSD.org
X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback+
X-Bugzilla-Changed-Fields:
Message-ID: <bug-259981-21822-EYVD7KGW5e@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-259981-21822@https.bugs.freebsd.org/bugzilla/>
References: <bug-259981-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
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org;
s=dkim; t=1638655510;
h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
to:to:cc:mime-version:mime-version:content-type:content-type:
content-transfer-encoding:content-transfer-encoding:
in-reply-to:in-reply-to:references:references;
bh=sbkZ5rXwvSdMCXKpZXUiAN+zWaXDSOmawFdNFuJHVOM=;
b=IW6PxDzON0js8obrrlVtyTkfCFvdv1+mP/bNxg6I/RgGjjODZwri3aEiQiolAolxsKKNpl
G6hW3gU6adjMz4modgboz819gqVQi/yftQgEoiI9RdEdx2pb5pejKapIp9d9NkyxUXTpGh
xipLBPdDl0Zk8LFcGs9+xeZEYmCkZsMMrMg28PAT21UIkb0PpVgGQQSuA300OerYgtCM/u
FKCB9+TZF+yxbkReLh247Dn3TxMTLikBKXgmvRN9TYDvE70sdESmJj4BD9sx4kr+sLn0hg
zyaT3d/XUBU/CDN/ilQyXKTat/Pj+dOZfBI2mLZ5TG1TC7FfKUYzB2E3wmqW4g==
ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1638655510; a=rsa-sha256; cv=none;
b=GEMhAGbeBJhXpP86OAf3Tk8ve6Rlux3yahFtAQspnNhUgWqlP/dxxBAG0w44rMu1Y3S+7Y
czd16LGy5dA1qtWMcX1DZG77mWJdrgyjAK4PXEI5Xs8rLrQ0XMkBOeJOr/wGHydhQzKsIV
c7y7YG467wGcicLT3yEjaJN0GGqqCbpBKbjNBHZ74fzuVirD+8VsHZQDcBwxMVtFpk6Nww
4mU8uispaUoVBogEfdk/deyyEPNpp9Nb5wM0sZQ2iP+3SsZoZD75ZREH/hRS5uWW4vWewt
1WrC8Sjl/s8hPS0s3tNhC8FoHNQU+ZO5782HmMJ5XE+HrQ3qkkR7O7saVnu9bQ==
ARC-Authentication-Results: i=1;
mx1.freebsd.org;
none
X-ThisMailContainsUnwantedMimeParts: N
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259981
--- Comment #6 from Stefan E=C3=9Fer <se@FreeBSD.org> ---
I can confirm that py-setuptools_scm installed prevents building of other
Python ports, if py-packaging or py-pyparsing are not available.
But I do not see any issue when updating these ports with portmaster.
I have tested all permutations of port names in the following command:
# portmaster devel/py-pyparsing devel/py-packaging devel/py-setuptools_scm
And in all cases the re-installation succeeded (as would have a port upgrad=
e):
=3D=3D=3D>>> The following actions were performed:
Re-installation of py38-pyparsing-3.0.6
Re-installation of py38-packaging-21.3
Re-installation of py38-setuptools_scm-6.3.2
The dependency checks performed by portmaster are somewhat different from t=
hose
performed by a plain make, since portmaster plans all updates before starti=
ng
the first one.
But the updates are then performed in the same way as by a plain "make all
deinstall install" in the port directory.
Portmaster considers RUN_DEPENDS to actually mean that, i.e. a dependency t=
hat
has to be provided to run the program built by the port. This is different =
from
a plain "make", since that performs builds and installations of RUN_TIME
dependencies before starting the "stage" phase.
But this difference is irrelevant for this PR.
A solution to this issue might be to treat a missing py-pyparsing or
py-packaging in the same way as if py-setuptools_scm was not installed.
The huge majority of Python ports does not depend on py-setuptools_scm -
specifically py-packaging and py-pyparsing do not depend on it. (Of more th=
an
7000 devel/py-* ports less than 70 directly depend on py-setuptools_scm.)
But if py-setuptools_scm *is* installed, a missing py-pyparsing oder
py-packages does suddenly become a configure dependency, since
py-setuptools_scm is (unnecessarily) invoked, but fails due to the missing
run-time dependency.
Thus, a missing py-pyparsing or py-packaging should not cause py-setuptools=
_scm
to fail in such a way, that setup.py is stopped. For ports that do not dire=
ctly
depend on py-setuptools_scm, such a failure should be ignored.
--=20
You are receiving this mail because:
You are on the CC list for the bug.=