Trevor Gamblin 3bb2dd3414
hdf5: fix shasum, downloadfilename
Fixes: #1023

Upstream seems to have regenerated the archive, as the checksum no
longer matches the one specified in the recipe:

|WARNING: hdf5-2.0.0-r0 do_fetch: Checksum failure encountered with download of https://support.hdfgroup.org/releases/hdf5/v2_0/v2_0_0/downloads/hdf5-2.0.0.tar.gz - will attempt other sources if available
|WARNING: hdf5-2.0.0-r0 do_fetch: Checksum mismatch for local file /buildcache/downloads/hdf5-2.0.0.tar.gz
|Cleaning and trying again.
|WARNING: hdf5-2.0.0-r0 do_fetch: Renaming /buildcache/downloads/hdf5-2.0.0.tar.gz to /buildcache/downloads/hdf5-2.0.0.tar.gz_bad-checksum_a7a8f43e76e825ea22234bc735d5b184e880d305e33e4c9bb93a3912421c9973
|ERROR: hdf5-2.0.0-r0 do_fetch: Checksum failure fetching https://support.hdfgroup.org/releases/hdf5/v2_0/v2_0_0/downloads/hdf5-2.0.0.tar.gz
|ERROR: hdf5-2.0.0-r0 do_fetch: Bitbake Fetcher Error: ChecksumError('Checksum mismatch!\nFile: \'/buildcache/downloads/hdf5-2.0.0.tar.gz\' has sha256 checksum \'a7a8f43e76e825ea22234bc735d5b184e880d305e33e4c9bb93a3912421c9973\' when \'6e45a4213cb11bb5860)
|ERROR: Logfile of failure stored in: /home/tgamblin/workspace/yocto/openembedded-core/build/tmp/work/x86-64-v3-poky-linux/hdf5/2.0.0/temp/log.do_fetch.2054297

However, the tarballs look identical. Update the hash and be explicit
about downloadfilename to avoid any mirroring issues. A note has been
left that this measure can be removed with a future upgrade.

Signed-off-by: Trevor Gamblin <tgamblin@baylibre.com>
Reviewed-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit f0f02434c892769a307edc6728dd667f9c31a1d1)
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
2026-02-02 08:13:02 +05:30
..
2024-10-10 12:53:49 -07:00
2025-07-30 08:03:05 -07:00
2025-10-21 20:02:39 -07:00
2025-09-24 10:54:44 -07:00
2026-01-06 18:07:46 +05:30
2025-03-16 09:09:44 -07:00
2025-11-19 09:41:30 -08:00
2025-09-16 09:59:15 -07:00
2025-10-08 18:46:02 -07:00
2025-03-15 23:05:32 -07:00
2025-09-19 12:22:01 -07:00
2025-10-06 11:34:42 -07:00
2024-09-15 07:46:44 -07:00
2026-01-06 18:07:52 +05:30
2025-07-07 10:00:54 -07:00
2025-09-27 16:18:15 -07:00
2025-12-17 13:57:07 +05:30
2026-02-02 08:13:02 +05:30
2025-11-12 09:38:58 -08:00
2025-10-14 09:00:20 -07:00
2024-11-19 16:59:16 -08:00
2026-01-20 10:15:20 +05:30
2024-11-19 16:59:10 -08:00
2025-07-08 23:40:34 -07:00
2025-08-28 07:56:52 -07:00
2025-10-17 14:10:38 -07:00
2025-12-17 13:57:15 +05:30
2025-11-14 07:39:48 -08:00
2025-02-17 07:40:58 -08:00
2025-02-10 08:45:37 -08:00
2025-10-08 18:46:01 -07:00
2025-07-08 23:40:33 -07:00
2025-11-13 23:02:36 -08:00
2025-11-14 07:39:48 -08:00
2025-11-15 15:49:44 -08:00
2024-08-09 14:25:15 -07:00
2025-12-17 13:57:09 +05:30
2025-10-14 09:00:20 -07:00
2025-05-21 07:38:25 -07:00
2025-07-30 08:03:07 -07:00
2025-11-18 08:17:54 -08:00
2025-09-30 10:36:16 -07:00
2025-09-08 22:01:07 -07:00
2025-11-18 08:17:53 -08:00
2025-10-12 20:58:51 -07:00
2025-01-07 19:39:34 -08:00
2025-07-30 08:03:08 -07:00
2025-10-24 18:45:43 -07:00
2025-11-18 08:23:44 -08:00
2026-01-20 10:15:20 +05:30
2025-11-20 19:32:09 -08:00
2025-11-13 23:02:36 -08:00
2026-01-20 10:15:18 +05:30
2025-10-14 09:00:25 -07:00
2025-11-14 07:39:48 -08:00
2025-05-05 10:16:54 -07:00
2025-09-23 14:22:59 -07:00
2024-12-03 09:44:36 -08:00
2025-09-30 09:01:05 -07:00
2025-07-25 17:09:25 -07:00
2025-10-14 11:23:45 -07:00
2025-11-18 08:17:55 -08:00
2026-02-02 08:13:00 +05:30
2025-09-04 10:28:30 -07:00
2025-11-18 08:17:55 -08:00