We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The recent Prefix bootstrap script added a "stable-only packages" mode (see https://gitweb.gentoo.org/repo/proj/prefix.git/commit/scripts/bootstrap-prefix.sh?id=92e83b4212ec23c1ea9d6013343462b85011a6bd), but only for amd64 (x86_64).
amd64
x86_64
This could easily lead to different package versions being installed for x86_64 vs aarch64 and ppc64le.
aarch64
ppc64le
That's already the case though, depending on when the compat layer is built.
So, we should check in CI that the same set of packages (and package versions) is installed in each of the compat/linux subdirectories.
compat/linux
The text was updated successfully, but these errors were encountered:
disable 'stable mode' in Gentoo Prefix bootstrap script, since it's o…
8c7c544
…nly used forr x86_64 (cfr. EESSI#131)
7c87d65
…nly used for x86_64 (cfr. EESSI#131)
This CI can generate a list of the installed packages by running something like the following on all supported architectures (using qemu):
qemu
cd /cvmfs/pilot.eessi-hpc.org/2021.12/compat/linux/$(uname -m)/var/db/pkg && ls -d */* | sort
or
qlist -ICv
Then it can do a diff of the outputs, and use our yaml set definition (https://github.com/EESSI/gentoo-overlay/blob/main/scripts/eessi_sets.yml) to ignore certain architecture-specific packages.
Sorry, something went wrong.
No branches or pull requests
The recent Prefix bootstrap script added a "stable-only packages" mode (see https://gitweb.gentoo.org/repo/proj/prefix.git/commit/scripts/bootstrap-prefix.sh?id=92e83b4212ec23c1ea9d6013343462b85011a6bd), but only for
amd64
(x86_64
).This could easily lead to different package versions being installed for
x86_64
vsaarch64
andppc64le
.That's already the case though, depending on when the compat layer is built.
So, we should check in CI that the same set of packages (and package versions) is installed in each of the
compat/linux
subdirectories.The text was updated successfully, but these errors were encountered: