From nobody Tue Nov 02 11:51:20 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 8FFE51845B8D for ; Tue, 2 Nov 2021 11:51:20 +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 4Hk7XS3VNJz3Gm1 for ; Tue, 2 Nov 2021 11:51:20 +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 5819424271 for ; Tue, 2 Nov 2021 11:51:20 +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 1A2BpKaX085839 for ; Tue, 2 Nov 2021 11:51:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1A2BpKV9085838 for python@FreeBSD.org; Tue, 2 Nov 2021 11:51:20 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 259567] devel/py-jsonschema: Version returns 0.0.0, breaking net-im/py-matrix-synapse which runs a version check Date: Tue, 02 Nov 2021 11:51:20 +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, needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ports@skyforge.at X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bofh@freebsd.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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 List-Archive: https://lists.freebsd.org/archives/freebsd-python List-Help: List-Post: List-Subscribe: List-Unsubscribe: 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=3D259567 --- Comment #3 from Sascha Biberhofer --- I can confirm this on my system. Seems like something is weirdly wrong with= the version of the FreeBSD package and *only* the distributed package: * It appears as jsonschema=3D=3D0.0.0 in pip freeze too, suggesting that so= mething is wrong with the package metadata per se. * I quickly built and installed the package directly from ports, which does *not* result in such a broken package for me (i.e. both pip freeze and jsonschema --version report the correct version number). Similarly, install= ing the package directly via pip works fine too. * Building the package in poudriere however yields a package with version 0= .0.0 in pip which is consequently also reported back by the package It would appear that something goes wrong when building the package with poudriere, but I'm currently not sure what exactly goes wrong here and I'm a bit uncertain how to proceed. The way the package obtains the version appea= rs to have changed and relies on importlib's metadata.version() function, which *should* work, I suppose, but I'm not sure how that version is formed before the package is installed and would need to dig deeper into this to properly find the cause. In the meantime, should we patch synapse to remove the version check? It wo= uld be a hack and I'd prefer to resolve this issue right here, but it *should* = be fine for the time being to ensure things keep running moderately smoothly. --=20 You are receiving this mail because: You are on the CC list for the bug.=