While updating the overlay for EESSI/2023.06 we ran into several issues raised by the pkgcheck GHA:
ebuilds for archspec v0.1.1 and v0.1.2 did not specify any available Python version, while it might have been possible to update them, we decided to remove them entirely (these are quite outdated and not used anymore)
other ebuilds for archspec and reframe were updated similarly (adding more recent Python versions) and also removing conflicting variable settings DISTUTILS_USE_SETUPTOOLS=pyproject.toml
plus the test failed with a message
FAILURE RESULTS
/opt/hostedtoolcache/Python/3.11.3/x64/bin/pkgcheck replay --color y /home/runner/failures.json
profiles
UnknownCategoryDirs: unknown category dir: etc
::error::pkgcheck failed with exit code 1
somehow pkgcheck seems to pickup/scan the directory etc and the test fails because etc is not a known category such as sys-apps or dev-util
we opted to let pkgcheck only analyse the currently present categories dev-util, sys-apps, sys-cluster and sys-fabric by adding arguments with the following two lines
While this may be ok as a work around, we should try to find a better way to run pkgcheck, e.g., by determining the list of categories to be checked automatically.
While updating the overlay for EESSI/2023.06 we ran into several issues raised by the
pkgcheckGHA:DISTUTILS_USE_SETUPTOOLS=pyproject.tomlpkgcheckseems to pickup/scan the directoryetcand the test fails becauseetcis not a known category such assys-appsordev-utilpkgcheckonly analyse the currently present categoriesdev-util,sys-apps,sys-clusterandsys-fabricby adding arguments with the following two linesWhile this may be ok as a work around, we should try to find a better way to run
pkgcheck, e.g., by determining the list of categories to be checked automatically.