Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
Hi, On Fri, 13 Jun 2014 11:22:03 +0200 Emilio Pozuelo Monfort po...@debian.org wrote: On 12/06/14 21:51, Gilles Filippini wrote: nmu hdf5_1.8.8-9 . amd64 i386 kfreebsd-amd64 kfreebsd-i386 . stable . -m Rebuild with current gfortran in wheezy (closes: #739261) Hoping to get it right this time :/ Scheduled. This still needs to be accepted by the SRMs for the next point release. I fail to see any move on this side. Is there anything I could do to have this binNMU accepted into stable? Thanks in advance, _g. signature.asc Description: OpenPGP digital signature
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
[resending because of a previously malformed address] Hi, On Fri, 13 Jun 2014 11:22:03 +0200 Emilio Pozuelo Monfort po...@debian.org wrote: On 12/06/14 21:51, Gilles Filippini wrote: nmu hdf5_1.8.8-9 . amd64 i386 kfreebsd-amd64 kfreebsd-i386 . stable . -m Rebuild with current gfortran in wheezy (closes: #739261) Hoping to get it right this time :/ Scheduled. This still needs to be accepted by the SRMs for the next point release. I fail to see any move on this side. Is there anything I could do to have this binNMU accepted into stable? Thanks in advance, _g. signature.asc Description: OpenPGP digital signature
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
On Thu, 2014-09-04 at 23:26 +0200, Gilles Filippini wrote: [resending because of a previously malformed address] Hi, On Fri, 13 Jun 2014 11:22:03 +0200 Emilio Pozuelo Monfort po...@debian.org wrote: On 12/06/14 21:51, Gilles Filippini wrote: nmu hdf5_1.8.8-9 . amd64 i386 kfreebsd-amd64 kfreebsd-i386 . stable . -m Rebuild with current gfortran in wheezy (closes: #739261) Hoping to get it right this time :/ Scheduled. This still needs to be accepted by the SRMs for the next point release. I fail to see any move on this side. Then your vision is faulty. Is there anything I could do to have this binNMU accepted into stable? Travel back to July this year, when the update was released. See https://www.debian.org/News/2014/20140712 and libhdf5-7 | 1.8.8-9 | stable | armel, armhf, ia64, mips, mipsel, powerpc, s390, s390x, sparc libhdf5-7 |1.8.8-9+b1 | stable | amd64, i386, kfreebsd-amd64, kfreebsd-i386 Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
On 12/06/14 21:51, Gilles Filippini wrote: fixed 739261 hdf5/1.8.12+docs-1.1 thanks Emilio Pozuelo Monfort a écrit , Le 12/06/2014 20:11: On 04/06/14 01:17, Gilles Filippini wrote: Hi, Frank Loeffler a écrit , Le 03/06/2014 21:01: Being hit by this myself now, I am a bit surprised by the reaction can wait a little longer, for an issue that clearly breaks the Fortran interface and seems to be easily fixable. But this aside - is there a plan to get this into _any_ of the future point releases of stable? I have no plan but getting the binNMU #740561 processed. And it all depends on the good will of the release team. You've requested a binnmu for stable on ALL architectures. Before scheduling that, I'd like to clarify some things: Is this bug affecting testing/unstable? If not, please mark it as fixed as appropriate in #739261. This bug doesn't affect testing nor unstable. Marking it fixed for the related version. Is this bug really affecting all architectures? From what I can see, gfortran in wheezy is 4.6 everywhere except on amd64, i386, kfreebsd-amd64 and kfreebsd-i386: gfortran | 4:4.6.3-8 | stable | armel, armhf, ia64, mips, mipsel, powerpc, s390, s390x, sparc gfortran | 4:4.7.2-1 | stable | amd64, i386, kfreebsd-amd64, kfreebsd-i386 And hdf5 1.8.8-9 was built against 4.6 everywhere, from what I can see on: https://buildd.debian.org/status/logs.php?pkg=hdf5ver=1.8.8-9suite=sid So do we need the binnmu everywhere, or only on those architectures where the default gfortran was bumped to 4.7, i.e. on amd64, i386, kfreebsd-amd64 and kfreebsd-i386? My mistake: I took for granted that gfortran was upgraded to 4.7 on all architectures. nmu hdf5_1.8.8-9 . amd64 i386 kfreebsd-amd64 kfreebsd-i386 . stable . -m Rebuild with current gfortran in wheezy (closes: #739261) Hoping to get it right this time :/ Scheduled. This still needs to be accepted by the SRMs for the next point release. Note that the closes: #739261 doesn't work for binnmus, so you'll have to close that manually. Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
On 04/06/14 01:17, Gilles Filippini wrote: Hi, Frank Loeffler a écrit , Le 03/06/2014 21:01: Being hit by this myself now, I am a bit surprised by the reaction can wait a little longer, for an issue that clearly breaks the Fortran interface and seems to be easily fixable. But this aside - is there a plan to get this into _any_ of the future point releases of stable? I have no plan but getting the binNMU #740561 processed. And it all depends on the good will of the release team. You've requested a binnmu for stable on ALL architectures. Before scheduling that, I'd like to clarify some things: Is this bug affecting testing/unstable? If not, please mark it as fixed as appropriate in #739261. Is this bug really affecting all architectures? From what I can see, gfortran in wheezy is 4.6 everywhere except on amd64, i386, kfreebsd-amd64 and kfreebsd-i386: gfortran | 4:4.6.3-8 | stable | armel, armhf, ia64, mips, mipsel, powerpc, s390, s390x, sparc gfortran | 4:4.7.2-1 | stable | amd64, i386, kfreebsd-amd64, kfreebsd-i386 And hdf5 1.8.8-9 was built against 4.6 everywhere, from what I can see on: https://buildd.debian.org/status/logs.php?pkg=hdf5ver=1.8.8-9suite=sid So do we need the binnmu everywhere, or only on those architectures where the default gfortran was bumped to 4.7, i.e. on amd64, i386, kfreebsd-amd64 and kfreebsd-i386? Regards, Emilio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
fixed 739261 hdf5/1.8.12+docs-1.1 thanks Emilio Pozuelo Monfort a écrit , Le 12/06/2014 20:11: On 04/06/14 01:17, Gilles Filippini wrote: Hi, Frank Loeffler a écrit , Le 03/06/2014 21:01: Being hit by this myself now, I am a bit surprised by the reaction can wait a little longer, for an issue that clearly breaks the Fortran interface and seems to be easily fixable. But this aside - is there a plan to get this into _any_ of the future point releases of stable? I have no plan but getting the binNMU #740561 processed. And it all depends on the good will of the release team. You've requested a binnmu for stable on ALL architectures. Before scheduling that, I'd like to clarify some things: Is this bug affecting testing/unstable? If not, please mark it as fixed as appropriate in #739261. This bug doesn't affect testing nor unstable. Marking it fixed for the related version. Is this bug really affecting all architectures? From what I can see, gfortran in wheezy is 4.6 everywhere except on amd64, i386, kfreebsd-amd64 and kfreebsd-i386: gfortran | 4:4.6.3-8 | stable | armel, armhf, ia64, mips, mipsel, powerpc, s390, s390x, sparc gfortran | 4:4.7.2-1 | stable | amd64, i386, kfreebsd-amd64, kfreebsd-i386 And hdf5 1.8.8-9 was built against 4.6 everywhere, from what I can see on: https://buildd.debian.org/status/logs.php?pkg=hdf5ver=1.8.8-9suite=sid So do we need the binnmu everywhere, or only on those architectures where the default gfortran was bumped to 4.7, i.e. on amd64, i386, kfreebsd-amd64 and kfreebsd-i386? My mistake: I took for granted that gfortran was upgraded to 4.7 on all architectures. nmu hdf5_1.8.8-9 . amd64 i386 kfreebsd-amd64 kfreebsd-i386 . stable . -m Rebuild with current gfortran in wheezy (closes: #739261) Hoping to get it right this time :/ _g. signature.asc Description: OpenPGP digital signature
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
Hi, Being hit by this myself now, I am a bit surprised by the reaction can wait a little longer, for an issue that clearly breaks the Fortran interface and seems to be easily fixable. But this aside - is there a plan to get this into _any_ of the future point releases of stable? Frank signature.asc Description: Digital signature
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
Hi, Frank Loeffler a écrit , Le 03/06/2014 21:01: Being hit by this myself now, I am a bit surprised by the reaction can wait a little longer, for an issue that clearly breaks the Fortran interface and seems to be easily fixable. But this aside - is there a plan to get this into _any_ of the future point releases of stable? I have no plan but getting the binNMU #740561 processed. And it all depends on the good will of the release team. Thanks, _g. signature.asc Description: OpenPGP digital signature
Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
Package: libhdf5-openmpi-dev Version: 1.8.8-9 Severity: normal The current version in wheezy was not built using the current version of gfortran in wheezy, and compilation fails: prompt h5fc h5_crtdat.f90 h5_crtdat.f90:26.6: USE HDF5 ! This module contains all necessary modules 1 Fatal Error: Wrong module version '6' (expected '9') for file 'hdf5.mod' -- The first line of /usr/include/hdf5.mod reads: GFORTRAN module version '6' created from ../../../../fortran/src/HDF5mpio.f90 on Thu Mar 8 11:40:49 2012 This is issue #630986 manifesting itself again, and a rebuild in a current wheezy environment is enough to solve this problem. It would be nice to see such a rebuilt in upcoming stable (wheezy) releases. Thanks Arne Nordmark -- System Information: Debian Release: 7.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libhdf5-openmpi-dev depends on: ii hdf5-helpers1.8.8-9 ii libhdf5-openmpi-7 1.8.8-9 ii libjpeg8-dev [libjpeg-dev] 8d-1 ii libopenmpi-dev 1.4.5-1 ii zlib1g-dev 1:1.2.7.dfsg-13 libhdf5-openmpi-dev recommends no packages. Versions of packages libhdf5-openmpi-dev suggests: pn libhdf5-doc none -- 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
