Package Details: hdf5_18 1.8.21-1

Git Clone URL: (read-only, click to copy)
Package Base: hdf5_18
Description: General-purpose library and file format for storing scientific data (1.8 branch)
Upstream URL:
Licenses: custom
Submitter: arojas
Maintainer: tallero
Last Packager: flacks
Votes: 3
Popularity: 0.000000
First Submitted: 2017-05-26 17:46 (UTC)
Last Updated: 2018-07-31 01:03 (UTC)

Latest Comments

eleftg commented on 2018-07-31 00:52 (UTC)

This is the release announcement:

and this is the direct link to the archive:

I guess now everything is in order for an update. Next time, if a package is flagged out-of-date and you can't find the release announcement or the tarball, try googling or discussing it in the comments section, but please do not silently unflag it. Especially when there is a pending orphan request.

eleftg commented on 2018-07-31 00:09 (UTC)

1.8.21 was released on June 6. This package has been flagged out-of-date twice ever since and unflagged both times WITHOUT upgrading. Unless there is a legitimate reason to stick with 1.8.20 (in which case it should be explained and the package renamed to something like hdf5_1_8_20), I would suggest that you orphan the package.

carbolymer commented on 2018-01-21 22:37 (UTC)

The SHA512 hash in PKGBUILD is invalid. The correct one for hdf5-1.8.20.tar.gz is 326c0c85b5a5d68a916ce0cada353bea774369f9d3d0eb982b876197300f8ce5f91836d09ab01f24d67e8fc82ce25ab8bb07db26ac0f67c3a1d6b61347afb913

SpotlightKid commented on 2018-01-17 12:11 (UTC)

It's not about the type of the hash, but about there being one present in the PKGBUILD file at all. It's an integrity check that's there so that when upstream changes the distribution archive, you notice it when you use makepkg. I'm not sure whether I understand what the problem is? Just run "updpkgsums" when updating a PKGBUILD for a new release and you're done.

eleftg commented on 2018-01-12 12:13 (UTC)

It's a question I've also been fighting with for some time as the packager of hdf5_18-openmpi ...

I don't really see the point of providing my own sha512 checksums which are stronger than those provided by the official distributors but I keep doing it, in order to avoid questions such as yours :)

(you will only find md5 checksums in the official download folder)

SpotlightKid commented on 2018-01-11 18:28 (UTC)

Why was sha hash checking removed?

lemenjon commented on 2017-07-22 01:57 (UTC)

Minor version has incremented and 1.8.18 is no longer available: