Hello community, here is the log from the commit of package dmtcp for openSUSE:Factory checked in at 2015-07-28 11:43:17 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/dmtcp (Old) and /work/SRC/openSUSE:Factory/.dmtcp.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "dmtcp" Changes: -------- --- /work/SRC/openSUSE:Factory/dmtcp/dmtcp.changes 2015-03-25 21:32:50.000000000 +0100 +++ /work/SRC/openSUSE:Factory/.dmtcp.new/dmtcp.changes 2015-07-28 11:43:39.000000000 +0200 @@ -1,0 +2,37 @@ +Wed Jul 15 13:41:40 UTC 2015 - [email protected] + +- Removed includes.patch and dmtcp-glibc-2.21.patch from patch list. +- Updated to upstream release 2.4.0. + * Release notes: + Several important changes and enhancements were added: +- dmtcp_launch/restart/command/coordinator now take the flags + -h, -p, --coord-host/port and environment variables + DMTCP_COORD_HOST/PORT. The older --host, --port, DMTCP_HOST/PORT + are now deprecated. +- Newer versions of MATLAB (matlab-2013 and later) were using additional + Linux features. All recent versions of matlab are again supported. +- Intensive testing done for integration of MPI/SLURM + for the following MPI dialects: Intel MPI/MVAPICH-2/MPICH-2/Open MPI. + See plugin/batch-queue/job_examples/ for SLURM/DMTCP submission scripts. + Preliminary support for some other resource managers also provided, + especially including ibrun. + - Open MPI version 1.8 _with_ InfiniBand is not yet supported. + This is due to the OMPI use of UD (unreliable datagrams) for InfiniBand. + Support is planned for the near future. Earlier OMPI versions continue + to work with IB. We do not currently know of a config in OMPI-1.8 to + avoid IB/UD (to use only IB/CM). Such a workaround would let DMTCP work. +- Added support for newest Linux kernels: split of [vdso] + into [vdso] and [vvar]; To see if this affects you, do: + cat /proc/self/maps | grep '\[vvar]' +- Support for glibc version 2.21 added. To see if this affects you, do: + ls -l /lib*/libc.so.6 /lib/*/libc.so.6 +- The environment variable DMTCP_GDB_ATTACH_ON_RESTART was added. Setting + this permanently is a security risk. But on a temporary basis, + it can enable easier debugging of restarted processes: + DMTCP_GDB_ATTACH_ON_RESTART=1 dmtcp_restart ckpt_a.out_*.dmtcp & + gdb a.out `pgrep -n a.out` +- Enhancements added for newer 32-bit ARM (armv7) CPUs +- Experimental support is now provided for 64-bit ARM (armv8) +- Bug fixes + +------------------------------------------------------------------- Old: ---- dmtcp-2.3.1.tar.gz dmtcp-glibc-2.21.patch includes.patch New: ---- dmtcp-2.4.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ dmtcp.spec ++++++ --- /var/tmp/diff_new_pack.ITL4fq/_old 2015-07-28 11:43:40.000000000 +0200 +++ /var/tmp/diff_new_pack.ITL4fq/_new 2015-07-28 11:43:40.000000000 +0200 @@ -18,15 +18,13 @@ Name: dmtcp -Version: 2.3.1 +Version: 2.4.0 Release: 0 Summary: Checkpoint/Restart functionality for Linux processes License: LGPL-3.0+ Group: System/Packages Url: http://dmtcp.sourceforge.net Source0: %{name}-%{version}.tar.gz -Patch1: includes.patch -Patch2: dmtcp-glibc-2.21.patch BuildRoot: %{_tmppath}/%{name}-%{version}-build BuildRequires: gcc BuildRequires: gcc-c++ @@ -65,8 +63,6 @@ %prep %setup -q -%patch1 -p1 -%patch2 -p1 sed -i -e 's,enable_option_checking=fatal,enable_option_checking=no,' configure %build ++++++ dmtcp-2.3.1.tar.gz -> dmtcp-2.4.0.tar.gz ++++++ ++++ 33903 lines of diff (skipped)
