[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#740561: marked as done (nmu: hdf5_1.8.8-9)

Your message dated Fri, 13 Jun 2014 11:22:03 +0200
with message-id <539AC2BB.10707@debian.org>
and subject line Re: Bug#739261: libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
has caused the Debian Bug report #740561,
regarding nmu: hdf5_1.8.8-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
740561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740561
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

nmu hdf5_1.8.8-9 . ALL . stable . -m "Rebuild with current gfortran in wheezy (closes: #739261)"

Hi,

Since I fail to see any move related to #739266 [1] I'd like to have
#739261 [2] taken care of anyway.

[1] wheezy-pu: package hdf5/1.8.8-9+deb7u1
    <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739266>
[2] libhdf5-openmpi-dev: Version in stable (wheezy) does not work with gfortran from stable
    <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739261>

Many thanks in advance,

_g.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJTE6jhAAoJEO/obGx//s+DDt0H/3FETCDbpgWDpKYPTxH8Fap7
sqS9YxfosTmcgXBnotnfoZBckP6E6Ke0c/A1FOCQsMLQE+MihFaKt+gc0ZrXHLIK
qgCJU8g68wKIOryT9r4GqwsuZ/ui9fGuO3TbSIfFy2ohX4dGLmWnYF8vzkLcGRP9
lkn/QgJUfAbEvK6GC3tvDrej861h/Qj9NuXd+bjQqvX1s/Wo/yvW6LxMIK+/x/1D
ImQNiSuVWRaQhTcATaMxCl6w/FpSL0R7Wtu5ueAimG9XE6oJvvoaVofmUQVs9gRL
Ph0ezV/HL84LbJC2mvdsB4foG2dvxGzhFlqpM2iH7+idBw6KzkB/P+BK/XNXseA=
=ePEV
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message --- 
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=hdf5&ver=1.8.8-9&suite=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

--- End Message ---
Reply to: