Re: Broken: devel/py-jaraco.envs in pkgsrc-current on NetBSD 10.0/x86_64

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Sun, Mar 16, 2025 at 09:41:04PM +0000, Taylor R Campbell wrote:
> > Date: Sun, 16 Mar 2025 22:34:34 +0100
> > From: Thomas Klausner <wiz%NetBSD.org@localhost>
> > 
> > On Sun, Mar 16, 2025 at 09:26:19PM +0000, Taylor R Campbell wrote:
> > > The builds of py310-jaracon.envs, py311-jaracon.envs,
> > > py312-jaracon.envs, and py313-jaracon.envs from devel/py-jaraco.envs
> > > are newly broken in pkgsrc-current on NetBSD 10.0/x86_64 since the
> > > last build from the same series.  Build failures:
> > > 
> > > http://shadow.netbsd.org/pub/pkgsrc/packages/reports/HEAD/NetBSD-10.0-x86_64/20250315.1129/py310-jaraco.envs-2.6.0nb1/install.log
> > > http://shadow.netbsd.org/pub/pkgsrc/packages/reports/HEAD/NetBSD-10.0-x86_64/20250315.1129/py311-jaraco.envs-2.6.0nb1/install.log
> > > http://shadow.netbsd.org/pub/pkgsrc/packages/reports/HEAD/NetBSD-10.0-x86_64/20250315.1129/py312-jaraco.envs-2.6.0nb1/install.log
> > > http://shadow.netbsd.org/pub/pkgsrc/packages/reports/HEAD/NetBSD-10.0-x86_64/20250315.1129/py313-jaraco.envs-2.6.0nb1/install.log
> > 
> > Wasn't this rather something that was depending on a package that was
> > fixed in this bulk build compared to the previous one?
> 
> Between
> 
> https://mail-index.netbsd.org/pkgsrc-bulk/2025/03/08/msg026568.html
> and
> https://mail-index.netbsd.org/pkgsrc-bulk/2025/03/16/msg026576.html
> 
> the status of these four packages changed from `done' to `failed'. 
> 
> There were some other py-jaraco.* packages that changed from `failed'
> to `done', like py-jaraco.collections, py-jaraco.test, and
> py-jaraco.vcs.  But py-jaraco.envs is a new failure.
> 
> The typo in the message `py310-jaracon.envs' was my human mistake
> demonstrating the `semi' part of `semiautomatically generated', but
> the actual detection of the transition from `done' to `failed' was
> purely automated by the bulkdiff script and appears to be correct.
> 
> $ awk '/^PKGNAME=py.*-jaraco.envs-/ { show = 1; print; next } /^PKGNAME=/ { show = 0 } show && /^BUILD_STATUS/ { print }' <old
> PKGNAME=py312-jaraco.envs-2.6.0nb1
> BUILD_STATUS=done
> PKGNAME=py313-jaraco.envs-2.6.0nb1
> BUILD_STATUS=done
> PKGNAME=py310-jaraco.envs-2.6.0nb1
> BUILD_STATUS=done
> PKGNAME=py311-jaraco.envs-2.6.0nb1
> BUILD_STATUS=done
> $ awk '/^PKGNAME=py.*-jaraco.envs-/ { show = 1; print; next } /^PKGNAME=/ { show = 0 } show && /^BUILD_STATUS/ { print }' <new
> PKGNAME=py312-jaraco.envs-2.6.0nb1
> BUILD_STATUS=failed
> PKGNAME=py313-jaraco.envs-2.6.0nb1
> BUILD_STATUS=failed
> PKGNAME=py310-jaraco.envs-2.6.0nb1
> BUILD_STATUS=failed
> PKGNAME=py311-jaraco.envs-2.6.0nb1
> BUILD_STATUS=failed

Interesting. I can't make sense of this, since it should have been
broken by the py-setuptools update to 75.8.2, long before that.

Anyway, I think I've fixed it now.
 Thomas