ffmpeg spack package build fails due to a checksum error

Summary

The ebrains-spack-builds build will fail due to a sub-package build error with ffmpeg@6.0 or ffmpeg@6.1.1.

Summary	Spack package build failure
Package info	ffmpeg@@6.0/ffmpeg@6.1.1
System	Local installation: Ubuntu
Related	NA

Steps to reproduce the issue

Follow the steps below to reproduce the error:

1. Clone the source repository:

   git clone https://gitlab.ebrains.eu/ri/tech-hub/platform/esd/ebrains-spack-builds.git

2. Clone Spack:

   git clone --depth 1 -c advice.detachedHead=false -c feature.manyFiles=true --branch v0.22.0 https://github.com/spack/spack

3. Source Spack:

   source spack/share/spack/setup-env.sh

4. Add the Spack repository:

   spack repo add ebrains-spack-builds

5. Set the system name:

   export SYSTEMNAME=ebrainslab

6. Modify <checkout-dir>/ebrains-spack-builds/spack.yaml to include only ffmpeg@6.0 or ffmpeg@6.1.1 in the spec section.
7. Modify <checkout-dir>/ebrains-spack-builds/site-config/ebrainslab/packages.yaml to remove all py-* packages.
8. Remove <checkout-dir>/ebrains-spack-builds/site-config/ebrainslab/spack.yaml.
9. Start the build:

   spack -d --env ebrains-spack-builds -j8 install --fresh

10. The build of ffmpeg will fail with the errors described in the section below.

The full error log is attached.install_log_2025-02-05-12-17-53.txt

Error message

Error message

spack.fetch_strategy.ChecksumError: sha256 checksum failed for /tmp/jmurugan/spack-stage/spack-stage-patch-416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53/f01fdedb69e4accb1d1555106d8f682ff1f1ddc7
    Expected 416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53 but got 673813d13f5c37b75ff5bcb56790ccd6b16962fdb9bddcbbeeead979d47d31b3. File size = 8260 bytes. Contents = b"From: Frank Plow...atting('float',\n"
==> [2025-02-05-12:26:53.284867] Flagging ffmpeg-6.0-5zwyfidvcwvjyzh6svmwwf52pgdoeiqd as failed: ChecksumError: sha256 checksum failed for /tmp/jmurugan/spack-stage/spack-stage-patch-416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53/f01fdedb69e4accb1d1555106d8f682ff1f1ddc7
    Expected 416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53 but got 673813d13f5c37b75ff5bcb56790ccd6b16962fdb9bddcbbeeead979d47d31b3. File size = 8260 bytes. Contents = b"From: Frank Plow...atting('float',\n"
==> [2025-02-05-12:26:53.290439] Creating ConfigScope env:/home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds:ebrainslab for '/home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds/site-config/ebrainslab'
==> [2025-02-05-12:26:53.290486] Reading config from file /home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds/site-config/ebrainslab/config.yaml
==> [2025-02-05-12:26:53.291156] Reading config from file /home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds/spack.yaml
==> [2025-02-05-12:26:53.294351] Deactivated environment '/home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds'
==> [2025-02-05-12:26:53.297189] Using environment '/home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds'
==> [2025-02-05-12:26:53.299641] '/usr/bin/git' '-C' '/home/jmurugan/esd_tests/ffmpeg_tests/spack' 'rev-parse' 'HEAD'
==> [2025-02-05-12:26:53.304784] View at /home/jmurugan/esd_tests/ffmpeg_tests/ebrains-spack-builds/.spack-env/view does not need regeneration.
==> [2025-02-05-12:26:53.304851] ChildError: ChecksumError: sha256 checksum failed for /tmp/jmurugan/spack-stage/spack-stage-patch-416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53/f01fdedb69e4accb1d1555106d8f682ff1f1ddc7
    Expected 416751f41cfbf086c28b4bbf01ace4c08e5651e59911dca6240292bb1b5c6b53 but got 673813d13f5c37b75ff5bcb56790ccd6b16962fdb9bddcbbeeead979d47d31b3. File size = 8260 bytes. Contents = b"From: Frank Plow...atting('float',\n"

Information on your system

GCC version: gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0

Spack: v0.22.0

Operating system:

• Description: Ubuntu 24.04.1 LTS
• Release: 24.04
• Codename: noble

Additional information

This appears to be a known issue in the Spack community: spack/spack#44773. If the build explicitly uses an older version of Spack (v0.21.1), it will succeed.

Although we have not yet upgraded to the latest Spack version, this issue will need to be resolved in the future when we transition to a newer Spack release.

@elmath @emuller @adrianciu We attempted to use Spack version v0.22.0 in VBT, and this issue appears to be newly introduced. Just for your information!

changed the description

That looks like a "didn't cleanup the spack config folders after switching to a new spack version"? Did you clean your caches, user folders, etc?

Has been solved with https://github.com/spack/spack/pull/45574, in Spack v0.23.0.

So it's backporting of this https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/ffmpeg/package.py#L133-L138 to our spack version.

yes, after (actually if, I'm hoping to go directly to v0.23.0) we update to Spack v0.22.*

@elmath Are we certain that this issue has been resolved in Spack v0.23.0? The same problem was previously reported for this specific version in the Spack community: spack/spack#44773.

This issue was not reported for spack v0.23.0, but for the develop HEAD at the time, 0.23.0.dev0 (c283526). The PR I mentioned above was merged later.

@elmath Ahh yes, you are right, thanks for the Information!

Isn't the fix just in there: https://github.com/spack/spack/commit/72e3f10d5b93d83027c003c7757591d0e8cc8325