Bug#1067118: marked as done (nmu: hdf5_1.10.10+repack-3.1)
Your message dated Wed, 27 Mar 2024 09:56:30 +0100
with message-id <ZgPfPrndzquLWgG0@ramacher.at>
and subject line Re: Bug#1067118: nmu: hdf5_1.10.10+repack-3.1
has caused the Debian Bug report #1067118,
regarding nmu: hdf5_1.10.10+repack-3.1
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.)
--
1067118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067118
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: SHA512
Hi,
During the ongoing 64 bit time_t transition it seems HDF5 should have been
triggered *after* curl. See #1065331.
As I understand it this should be fixed via the following binNMU request:
nmu hdf5_1.10.10+repack-3.1 . ANY . unstable . -m "binNMU to depend on libcurl4t64"
Thanks,
_g.
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAmX4o2YACgkQ7+hsbH/+
z4N+SQf/bgkEXassUkLIzCVBI5KnjM1uZXxp7tHgDsbPcx/Y769EZXUFSPLWaA3i
1E2ietil02tCgTa1njciUlsqPL6Din/vUbI7zX+Xjs1DfHVPleY56isPNfEQSVVE
qcmQekQvozFzrs5kxhbpkW7ZG9oiMujKclwjS72K3bSbWdORYzkWVkVA8njyEzfk
5ays8yOyzAq0VJ+vshWy7l0EqTkoX/qLsIsyVUHTf6A6Ii/p5Pr37/bB3x11EsGx
vF8fBHY6EvB77clpWVK6EmjiIMxZpZC0dr6wXS4BepOSAPkjoeUuec1KR/HHeFpQ
FPDFnxXVf++eO5U/c1Q3F8wCQ4YWCw==
=F5hi
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2024-03-18 21:26:23 +0100, Gilles Filippini wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
>
> Hi,
>
> During the ongoing 64 bit time_t transition it seems HDF5 should have been
> triggered *after* curl. See #1065331.
>
> As I understand it this should be fixed via the following binNMU request:
>
> nmu hdf5_1.10.10+repack-3.1 . ANY . unstable . -m "binNMU to depend on libcurl4t64"
-3.2 was uploaded in the meantime.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: