<?xml version="1.0" encoding="UTF-8"?>
<otherdata xmlns="http://linux.duke.edu/metadata/other" packages="37">
<package pkgid="fce69a98ad6fed6a97ea7753151b6c08d1527ad67f48217a0f742a93ab240b86" name="hdf5-1_8" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="c0a9f5d35036326b0ce91c12468392031028688d92464d513b72c47e6e147a42" name="hdf5-1_8" arch="src">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="8342580ec15e0ea9129a986035168b2978fc9dce7e444d5978ad6beaff604b17" name="hdf5-1_8" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="5f844f074818fb76a1e7017925c65fee4c370f98227cdce920b08a5b98bc5ebc" name="hdf5-1_8-devel" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="f9d9bcb185d0778fdcd29f90f9985ae9be72192c718a0a281b3fa9e7b6a01da5" name="hdf5-1_8-devel" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="ad30634ef7f06d3952ce9081e7de571bc8b8dc25c396cc4ebdc901d9cd63d630" name="hdf5-1_8-devel-data" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="e015752ada25454548187b2b532a7151987a393d7d69dd0cc5a9619f323adfc7" name="hdf5-1_8-devel-data" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="b80a5b5d6ddb6ef88f76497716d67e251daa7607f1c1cd6d158cb2e3f582d480" name="hdf5-1_8-devel-static" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="766c0f3f83093383e6487acb726d208155d6707ce101bc9a47b7d8ddb378fa2c" name="hdf5-1_8-devel-static" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="d9f32c1fca17a87ecbd3d27fca1e4806d09c2a8eae6702a9c6a36b46f8882c25" name="hdf5-1_8-examples" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="e00ffba745d8e0b8b24cdb949386a0f37d4e0a2ca77aaf0e5af3b4d2219ce965" name="hdf5-1_8-examples" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="bddc88616c36bf172f4fb45e5438c448ed31782a58318323f8daac17ee0ce929" name="hdf5-1_8-openmpi" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="7c13b675acbc466feb9fb500f84efcd665a500e9aeb63b2cd771c5d1fa2a0407" name="hdf5-1_8-openmpi" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="4c2fb6a8a69b2d4bf557ffd4820ecf208af73f1ea0f5f2c5b71bdd099b56afbd" name="hdf5-1_8-openmpi-devel" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="dc265047bd07bdab31ee6bf7307ab7af272353e9087abe63d5e6460b1b31fa6e" name="hdf5-1_8-openmpi-devel" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="a070e880efc7fcfbc2c640abbce18bc973e07b7819b1deff1e60a91f8167fa49" name="hdf5-1_8-openmpi-devel-static" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="e25ac9ec300327f407321ca67ba973474994ca623a0bfc76a0f6f985c2e37979" name="hdf5-1_8-openmpi-devel-static" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="12026e3901ced9950c0d307842e0e2c00adc1e28e758d02d4bd0db205858fbc3" name="libhdf5-10" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="6d003e42ce0056586411d9c943f9438fd25c7d3ddde9a8220a59a2bc847fa2fd" name="libhdf5-10" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="7dd0654806db61e60c8827886addd553004af252da14ef0e81cd2004d6a49f85" name="libhdf5-10-openmpi" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="07a64010caecf05498c54021a901b75b69254019ba1b5a5a363595a3d10eb5dc" name="libhdf5-10-openmpi" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="1baf8d18b0d8a3efbc962eeb36ce2bfc6c86b08ac19fe69cce106e1a926fe9f0" name="libhdf5_cpp11" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="1b773877f098531aa276a8875c4d4fec380f90175cda84b7953d34896b0c5b6c" name="libhdf5_cpp11" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="27b762c284f92e9f99aa5c067df56a7128075034ba0f0d54de34e57911faf8d2" name="libhdf5_fortran10" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="91f0e345658283af9bad390b2d6cdcafe1f2a415eac87f3507ad22e182fc8154" name="libhdf5_fortran10" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="dd30037de956dc56c40984d8aba92f6725a8eacb12abaf74253e8755ef062222" name="libhdf5_fortran10-openmpi" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="a564b5b32f631aa9602472f7e4a24bd7f66f053a5b313345cc429f8b1991f932" name="libhdf5_fortran10-openmpi" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="b5cd9aa3f16d40f2128cc0f1c5cf2df69efe8edac52e9e542c4f56dbe078cbdb" name="libhdf5_hl10" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="bb4bfc587b21aab7128ba6a0a46cbfc07b1656cf56b8782d19702548c140b2c6" name="libhdf5_hl10" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="48edf67b575edce755b784e10287aaf0b9f5318a531eb5f133e12332383471d3" name="libhdf5_hl10-openmpi" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="f7fb2c3f167c390031b5bd92fdad5a8c13c6482672a870228275ad99c92e94dc" name="libhdf5_hl10-openmpi" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="ade248813c869724603131b40f92b69480b89fcd0b1133fab37d79dcd8417163" name="libhdf5_hl_cpp11" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="13914dee6a632114c25a37f0222d139d55e7ab8af73c51b2462122224bd10eed" name="libhdf5_hl_cpp11" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="d9581219dd2f17f1496c351995372b6b1988ded297583d2b624251281f351bb7" name="libhdf5hl_fortran10" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="7b5c6f607f2337c5719ab305a75d8cf527c06f24f5c6035c319706b81d0e18f1" name="libhdf5hl_fortran10" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="8b1b4a5650805d39bb324980619ad72e0b7f1fa76382a9a61d7d12c582bbb900" name="libhdf5hl_fortran10-openmpi" arch="i586">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
<package pkgid="5ee4805f1757995292aac549a2bd5752412263808de64f702eaa6e346fd20d6b" name="libhdf5hl_fortran10-openmpi" arch="x86_64">
  <version epoch="0" ver="1.8.16" rel="29.11"/>
  <changelog author="pgajdos@suse.com" date="1403524800">- updated to 1.8.13:
  - Added an H5free_memory API call. This should be used to free memory
    that has been allocated by HDF5 API calls. H5Tget_member_name and
    H5Pget_class_name are two examples. The main motivation for this call
    is Windows, where it is common for application code and the HDF5 Library
    to be using different C run-time libraries (CRT). Using the new call
    ensures that the same CRT handles both the allocation and free. This
    new function can also be useful in any case where the library uses a
    different memory manager than the application, such as when a debug
    memory manager is in use or when the HDF5 Library is wrapped for use
    in a managed language like Python or Java. Fixes HDFFV-7710, 8519,
    and 8851. (DER - 2014/04/11)
  - The Core VFD (aka Memory VFD) can now be configured to track dirty
    regions in the file and only write out the changed regions on
    flush/close. Additionally, a "page aggregation" size can be set that
    will aggregate small writes into larger writes. For example, setting
    a 1 MiB page aggregation size will logically partition the the
    in-memory file into 1 MiB pages that will be written out in their
    entirety if even a single byte is dirtied. The feature is controlled
    via the new H5Pset/get_core_write_tracking() API call. A new
    "core_paged" target has been added to the check-vfd target in
    test/Makefile.am that exercises the feature over all HDF5 VFD-aware
    tests. (DER - 2014/04/12)
  - see http://www.hdfgroup.org/ftp/HDF5/current/src/hdf5-1.8.13-RELEASE.txt
    for more
- modified patches:
  * hdf5-LD_LIBRARY_PATH.patch</changelog>
  <changelog author="pgajdos@suse.com" date="1416398400">- updated to 1.8.14:
  * bugfix release, see RELEASE.txt</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1420804800">- fix typos in ChangeLog</changelog>
  <changelog author="pth@suse.de" date="1421150400">- Tag baselibs.conf as source.</changelog>
  <changelog author="dmueller@suse.com" date="1431345600">- update hdf5-non_void_return.patch for GCC 5.x</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437566400">- update to 1.8.15
  * New Features
    + Library
  - Added Memory Allocation Functions that Use the Library's Allocator
  - H5Pset_istore_k and H5Pset_sym_k added validation of "ik" to not
    exceed the max v1 btree entries (2 bytes) to these two routines.
  - Added Functions to Control the Value of H5PL_no_plugin_g without
    Using an Environment Variable
    + Parallel Library
  - Attached an attribute destroy callback to MPI_COMM_SELF that
    shuts down the HDF5 library when MPI_COMM_SELF is destroyed,
    in other words, on MPI_Finalize. This should fix several issues
    that users see when they forget to close HDF5 objects before
    + Fortran API
  - Added Global Variables. These new global variables are equivalent to
    the C definitions  without the '_F':
    o H5G_UDLINK_F
    o H5G_SAME_LOC_F
    o H5O_TYPE_UNKNOWN_F
    o H5O_TYPE_GROUP_F
    o H5O_TYPE_DATASET_F
    o H5O_NAMED_DATATYPE_F
    o H5O_TYPE_NTYPES_F
    + C++ API
  - New Wrappers for C Functions H5P[s/g]et_libver_bounds
  - New Wrappers to Get the Object Header's Version
  - New DataType Constructor
    + Support for New Platforms, Languages, and Compilers
  - Support for Linux 3.10.0-123.20.1.el7 added (LK - 2015/04/01)
  * Bug Fixes since HDF5-1.8.14
    + Library
  - Addition of Error Tracing Functionality to Several C API Calls
  - H5Rdereference Now Checks for HADDR_UNDEF or Uninitialized References
  - Fixed Bugs in H5Sextent_copy
    + Parallel Library
  - Fixed a Potential Memory Error
  - Parallel Test Problem Fixed
  - MPE Support
    + Tools
  - h5repack crashed on enumerated 8-bit type.
  - h52gif crashed non-8bit images.
  - perform/benchpar.c retired.
  - Source perform/ directory moved to tools/perform.
    + Fortran API
  - Fortran Fails with --enable-fortran2003 and Intel 15.x Compilers
  - h5tenum_insert_f Does Not Work with Default 8 Byte Integers
    (xlf compiler)
  - Some Fortran APIs Never Returned the Error State
  - Fixed h5pget_class_f
    + C++ API
  - Combined Two H5File::getObjCount Overloaded Methods
    The following two methods
    o ssize_t getObjCount(unsigned types) const;
    o ssize_t getObjCount() const;
    were combined into one:
    o ssize_t getObjCount(unsigned types = H5F_OBJ_ALL) const;
  - Many Warnings Were Removed
  - Functionality Deprecation
    The following two constructors of classes AbstractDs, IdComponent,
    H5Location, and H5Object are no longer appropriate after the data member
    "id" had been moved from IdComponent to the sub-classes in previous
    releases.
    o &lt;Classname&gt;(const hid_t h5_id);
    o &lt;Classname&gt;(const &lt;Classname&gt;&amp; original);
    The copy constructors were no-op and removed in 1.8.15.  The other
    constructors will be removed from 1.10 release, and then from 1.8.17
    if their removal does not cause any problems.
    + High-Level APIs:
  - Suppress Warnings from Flex/Bison-generated Code
  - Changed hdf5_hl.h to Include the HDF5 Main Library "hdf5.h"
  - H5PTcreate_fl Does Not Convert to Memory Datatype
  - Fix for H5LT Attribute Functions
    + Fortran High-Level APIs:
  - Internal Library Fix for Missing Argument Declaration
- Build in thread-safe mode to allow parallel reads
  * These are only unsupported to avoid confusing casual users.
    The fotran and C++ libraries don't support thread-safe mode,
    while the C library does.  So you have to explicitly allow
    building the thread-safe C library and the non-thread-safe C++
    and fortran libraries in order to make sure only people who
    have done their research do so.  Since users are going to be
    accessing this through other programs, this doesn't matter.
- Build fortran 2003 libraries
- Rebase hdf5-non_void_return.patch
- Remove irrelevant hdf5-configure-long-double.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437652800">- Fix baselibs.conf</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998400">- Use explicit library requirements to avoid ambiguities.
  Without this, packages that depend on hdf5 won't know which
  library to use.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1437998401">- Update subpackage groups
- Make subpackage summaries and descriptions more consistent
- Provide rpm macros for version identification
- Spec file cleanups</changelog>
  <changelog author="badshah400@gmail.com" date="1439467200">- Add hdf5-cpp-compilation-errors.patch: Reverts a change from
  v1.8.15 to H5api_adpt.h that caused compilation errors for C++
  HDF5 applications; patch taken from upstream svn.</changelog>
  <changelog author="toddrme2178@gmail.com" date="1440158400">- Currently the regular, openmpi, and mpivachi2 versions of the
  library packages all provide the exact same libraries.  So any
  package built against the -devel package will end up with an
  "unresolvable" build error because there are multiple versions
  of the library it can use. To avoid this, I have added generic
  provides for the library package so packages can depend on the
  version they really need, avoiding these build issues.</changelog>
  <changelog author="sweet_f_a@gmx.de" date="1453982400">- update to 1.8.16, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.16/src/hdf5-1.8.16-RELEASE.txt
- rebase hdf5-ldouble-ppc64le.patch
- remove hdf5-cpp-compilation-errors.patch
- prepare independent so versions and add TODO</changelog>
  <changelog author="olaf@aepfle.de" date="1457352000">- Remove timestamps from binaries
  hdf5-buildcompare.patch</changelog>
  <changelog author="toddrme2178@gmail.com" date="1458302400">- Split libraries into C, C++, and Fortran versions to comply with
  openSUSE library packaging policies.
  Fixes BNC#971602
- Make Fortran builds required.
- Manually set so numbers.  The autodetected ones weren't matching
  the real ones.</changelog>
  <changelog author="normand@linux.vnet.ibm.com" date="1460721600">- add hdf5-mpi.patch same as fedora commit id
  78ddcff82b10fd80eafb7b2dc5e4ce2bb9ecbe3c
  should avoid transient hung of t_pflush1 test</changelog>
  <changelog author="toddrme2178@gmail.com" date="1464004800">- update to 1.8.17, changes documented here:
  https://www.hdfgroup.org/ftp/HDF5/releases/hdf5-1.8.17/src/hdf5-1.8.17-RELEASE.txt</changelog>
  <changelog author="adrian@suse.de" date="1518004800">- branch 1.8 version as hdf5-1_8 package to allow parallel build
- needed for med-tools (and therefore for FreeCAD), because 1.10
  has incompatible data exchange format</changelog>
  <changelog author="adrian@suse.de" date="1523448000">- update to version 1.8.20
  https://support.hdfgroup.org/HDF5/doc1.8/</changelog>
  <changelog author="wagner-thomas@gmx.at" date="1530532800">- revert to 1.8.16 to be compatible with RadServ from Inras</changelog>
  <changelog author="adrian@suse.de" date="1533729600">- add provides of standard package names</changelog>
</package>
</otherdata>