Bug#753001: Bug #753001: openmpi: New upstream version 1.8 available
Alastair, now that you took over maintainership and started fixing bugs in unstable, will you update OpenMPI to 1.8 soon? Michael
Bug#753001: [Pkg-openmpi-maintainers] Bug#753001: Bug#753001: openmpi: New upstream version 1.8 available
Hello, we can still work during the freeze. It is one of the reason experimental is for. Anyway, if you want to help, please subscribe to the group on alioth (it is down for me now). You will be able to commit in the repo. As there is no active maintainer, I don't think the delay is an issue... And I am usually fast to upload (even if I am going in Holidays for a little while). Sylvestre Le 18/06/2015 17:11, M Milligan a écrit : Now that the stable release is past, I'm happy to work on openmpi again. During the freeze it seemed counterproductive to do so, since I don't have upload powers and thus anything I did would introduce delays with sponsored uploads etc. --- Michael Milligan, Ph.D. | Supercomputing Institute Scientific Computing Consultant | University of Minnesota Application Software Manager| milli...@umn.edu www.msi.umn.edu/users/milligan | Phone: 612-624-8857 On 2015-06-18 09:59, Sylvestre Ledru wrote: Le 18/06/2015 16:52, Nico Schlömer a écrit : Package: libopenmpi-dev Version: 1.6.5-9.2 Followup-For: Bug #753001 Is anyone still on this? AFAIK, No, unfortunately. There is no active maintainer on openmpi. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
Package: libopenmpi-dev Version: 1.6.5-9.2 Followup-For: Bug #753001 Is anyone still on this? -- System Information: Debian Release: jessie/sid APT prefers vivid-updates APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), (100, 'vivid-backports') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.19.0-18-generic (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenmpi-dev depends on: ii libc6 2.21-0ubuntu4 ii libhwloc-dev1.10.0-3 ii libibverbs-dev 1.1.8-1ubuntu1 ii libopenmpi1.6 1.6.5-9.2 ii openmpi-common 1.6.5-9.2 libopenmpi-dev recommends no packages. libopenmpi-dev suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: [Pkg-openmpi-maintainers] Bug#753001: openmpi: New upstream version 1.8 available
Le 18/06/2015 16:52, Nico Schlömer a écrit : Package: libopenmpi-dev Version: 1.6.5-9.2 Followup-For: Bug #753001 Is anyone still on this? AFAIK, No, unfortunately. There is no active maintainer on openmpi. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: [Pkg-openmpi-maintainers] Bug#753001: Bug#753001: openmpi: New upstream version 1.8 available
Now that the stable release is past, I'm happy to work on openmpi again. During the freeze it seemed counterproductive to do so, since I don't have upload powers and thus anything I did would introduce delays with sponsored uploads etc. --- Michael Milligan, Ph.D. | Supercomputing Institute Scientific Computing Consultant | University of Minnesota Application Software Manager| milli...@umn.edu www.msi.umn.edu/users/milligan | Phone: 612-624-8857 On 2015-06-18 09:59, Sylvestre Ledru wrote: Le 18/06/2015 16:52, Nico Schlömer a écrit : Package: libopenmpi-dev Version: 1.6.5-9.2 Followup-For: Bug #753001 Is anyone still on this? AFAIK, No, unfortunately. There is no active maintainer on openmpi. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
Version 1.8.2 is out, which brings a good list of bug fixes. http://www.open-mpi.org/community/lists/announce/2014/08/0063.php In the changelog, this line : - Close many memory leaks to achieve valgrind-clean operation suggests bug #732160 may be addressed. How large an effort would it be to update openmpi from the 1.6 to the 1.8 series ? Ghis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
On 11/09/2014 10:45, Ghislain Vaillant wrote: Version 1.8.2 is out, which brings a good list of bug fixes. http://www.open-mpi.org/community/lists/announce/2014/08/0063.php Yeh, professionally, I left the scientific world for Mozilla. So, my interest for scientific packages decreased. Sorry about that. In the changelog, this line : - Close many memory leaks to achieve valgrind-clean operation suggests bug #732160 may be addressed. How large an effort would it be to update openmpi from the 1.6 to the 1.8 series ? Usually, upstream is great to keep our work easy. However, it is likely that this version of OpenMPI requires an SO bump (and therefor requires a transition). Such transition is going to be important to be done before Jessie. However, we could prepare everything in experimental. If you are interested, I would be happy to sponsor such work. Cheers, Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
On 11/09/14 10:04, Sylvestre Ledru wrote: On 11/09/2014 10:45, Ghislain Vaillant wrote: Version 1.8.2 is out, which brings a good list of bug fixes. http://www.open-mpi.org/community/lists/announce/2014/08/0063.php Yeh, professionally, I left the scientific world for Mozilla. So, my interest for scientific packages decreased. Sorry about that. No problem, we all have lives too. In the changelog, this line : - Close many memory leaks to achieve valgrind-clean operation suggests bug #732160 may be addressed. How large an effort would it be to update openmpi from the 1.6 to the 1.8 series ? Usually, upstream is great to keep our work easy. That is good news. However, it is likely that this version of OpenMPI requires an SO bump (and therefor requires a transition). I am not surprised. Such transition is going to be important to be done before Jessie. However, we could prepare everything in experimental. If you are interested, I would be happy to sponsor such work. I would be keen on giving it a go, however I am not too sure about where to start once the latest source are imported. FYI, I did a merge with 1.8.2 and tried a build with pbuilder, which unsurprisingly failed. Cheers, Ghis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
On 11/09/2014 19:18, Ghislain Vaillant wrote: Such transition is going to be important to be done before Jessie. However, we could prepare everything in experimental. If you are interested, I would be happy to sponsor such work. I would be keen on giving it a go, however I am not too sure about where to start once the latest source are imported. FYI, I did a merge with 1.8.2 and tried a build with pbuilder, which unsurprisingly failed. pbuilder takes too long to prepare everything. You should have a local instance of the source and try to fix one problem after the other. What is the failure ? S -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
pbuilder takes too long to prepare everything. You should have a local instance of the source and try to fix one problem after the other. You're probably right. I did not realize how long the build is taking. What is the failure ? Seems to be failing on the make check target for ompi/debuggers. I have pasted a copy of my stdout below: Making check in debuggers make[3]: Entering directory '/tmp/buildd/openmpi-1.8.2/ompi/debuggers' make predefined_gap_test dlopen_test make[4]: Entering directory '/tmp/buildd/openmpi-1.8.2/ompi/debuggers' gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../opal/include -I../../orte/include -I../../ompi/include -I../../oshmem/include -I../../opal/mca/hwloc/hwloc172/hwloc/include/private/autogen -I../../opal/mca/hwloc/hwloc172/hwloc/include/hwloc/autogen -I../.. -D_FORTIFY_SOURCE=2 -I/usr//include -I/tmp/buildd/openmpi-1.8.2/opal/mca/event/libevent2021/libevent -I/tmp/buildd/openmpi-1.8.2/opal/mca/event/libevent2021/libevent/include -DNDEBUG -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -pthread -g -c -o predefined_gap_test.o predefined_gap_test.c /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -DNDEBUG -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -pthread -g -Wl,-z,relro -L/usr//lib -o predefined_gap_test predefined_gap_test.o ../../ompi/libmpi.la -lrt -lm -lutil -lhwloc -lltdl libtool: link: gcc -std=gnu99 -DNDEBUG -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -pthread -g -Wl,-z -Wl,relro -o .libs/predefined_gap_test predefined_gap_test.o -L/usr//lib ../../ompi/.libs/libmpi.so -lrt -lm -lutil -lhwloc /usr/lib/x86_64-linux-gnu/libltdl.so -pthread -Wl,-rpath -Wl,/usr/lib/openmpi/lib gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I../../opal/include -I../../orte/include -I../../ompi/include -I../../oshmem/include -I../../opal/mca/hwloc/hwloc172/hwloc/include/private/autogen -I../../opal/mca/hwloc/hwloc172/hwloc/include/hwloc/autogen -I../../opal/libltdl -I../.. -D_FORTIFY_SOURCE=2 -I/usr//include -I/tmp/buildd/openmpi-1.8.2/opal/mca/event/libevent2021/libevent -I/tmp/buildd/openmpi-1.8.2/opal/mca/event/libevent2021/libevent/include -DNDEBUG -fstack-protector-strong -Wformat -Werror=format-security -fno-strict-aliasing -pthread -g -c -o dlopen_test-dlopen_test.o `test -f 'dlopen_test.c' || echo './'`dlopen_test.c make[4]: *** No rule to make target '../../opal/libltdl/libltdlc.la', needed by 'dlopen_test'. Stop. make[4]: Leaving directory '/tmp/buildd/openmpi-1.8.2/ompi/debuggers' Makefile:2259: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 make[3]: Leaving directory '/tmp/buildd/openmpi-1.8.2/ompi/debuggers' Makefile:3147: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory '/tmp/buildd/openmpi-1.8.2/ompi' Makefile:1709: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/tmp/buildd/openmpi-1.8.2' dh_auto_test: make -j1 check returned exit code 2 debian/rules:32: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package W: no hooks of type C found -- ignoring I: unmounting /var/cache/pbuilder/deps filesystem I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem - Cleaning COW directory forking: rm -rf /var/cache/pbuilder/build/sid-amd64//cow.20838 Ghis -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753001: openmpi: New upstream version 1.8 available
Package: openmpi Version: 1.6.5-8 Severity: wishlist Dear Maintainer, Version 1.8 (and, more recently 1.8.1) of OpenMPI has been released this year: http://www.open-mpi.org/community/lists/announce/2014/03/0061.php http://www.open-mpi.org/community/lists/announce/2014/04/0062.php Michael -- System Information: Debian Release: 7.5 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=POSIX, LC_CTYPE=de_DE.ISO-8859-15@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
