Your message dated Fri, 15 May 2026 05:49:41 +0000
with message-id <[email protected]>
and subject line Bug#1136706: fixed in libequihash 1.0.10-3
has caused the Debian Bug report #1136706,
regarding libequihash0: Pre-Depends hardcodes obsolete libsodium version
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 [email protected]
immediately.)


-- 
1136706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136706
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libequihash0
Version: 1.0.10-2
Severity: serious
Tags: forky sid

Package: libequihash0
Depends: libc6 (>= 2.14), libgcc-s1 (>= 3.0), libsodium26 (>= 0.6.0), 
libstdc++6 (>= 5)
Pre-Depends: build-essential, libsodium23 (>= 1.0.18)


As far as I can see, using Pre-Depends is already a bug that
has to be fixed - I'd guess these were only by accident pasted
under Pre-Depends instead of Depends in debian/control, and the
manual listing was just a workaround for what was in 1.0.2-1
properly fixed with ${shlibs:Depends}:
https://salsa.debian.org/debian/libequihash/-/commit/0e06748b4cfe3d43e8fe47c96609dab42590c47d

--- End Message ---
--- Begin Message ---
Source: libequihash
Source-Version: 1.0.10-3
Done: Joost van Baal-Ilić <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libequihash, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Joost van Baal-Ilić <[email protected]> (supplier of updated libequihash 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 15 May 2026 07:24:55 +0200
Source: libequihash
Architecture: source
Version: 1.0.10-3
Distribution: unstable
Urgency: low
Maintainer: Joost van Baal-Ilić <[email protected]>
Changed-By: Joost van Baal-Ilić <[email protected]>
Closes: 1136706
Changes:
 libequihash (1.0.10-3) unstable; urgency=low
 .
   * d/control: drop "Rules-Requires-Root: no": default as of dpkg-dev 1.22.13.
   * d/control: drop "Pre-Depends: ${misc:Pre-Depends}, build-essential,
     libsodium23 (>= 1.0.18)" from libequihash0, thanks Adrian Bunk.
     Closes: #1136706
   * d/patches/{makefile.patch,series}: added: honor CPPFLAGS and LDFLAGS,
     fixing Debian blhc error 'missing -D_FORTIFY_SOURCE=2'.
Checksums-Sha1:
 76384047ce986dc4b8bb0fe7d14b9fb8d94f443a 2074 libequihash_1.0.10-3.dsc
 4dc1d0186ad7ba0d294f718b72e29b37053bfb93 4768 
libequihash_1.0.10-3.debian.tar.xz
 e578466082ec6352068bc442b472d7e3101d2d00 5675 
libequihash_1.0.10-3_source.buildinfo
Checksums-Sha256:
 652a5f938d5d1a1fcf5b3c8b3bb1192f7f32d53eefd56aa218401b380fab8d3d 2074 
libequihash_1.0.10-3.dsc
 14d9db231ac3c1e99f3f645db1bc56d8356a2c3ffa1447b96bdaac1e7e94dffe 4768 
libequihash_1.0.10-3.debian.tar.xz
 4033b4ac38ecbe7a0b4782c742bc4614cc37ca03c0e26231a739ea5ccc22b504 5675 
libequihash_1.0.10-3_source.buildinfo
Files:
 6fa0f93822a9755d022072737654b121 2074 utils optional libequihash_1.0.10-3.dsc
 efc208cace5f4c6313a767d5cf067786 4768 utils optional 
libequihash_1.0.10-3.debian.tar.xz
 23ecca431ec46f93fdaf83f7aca869da 5675 utils optional 
libequihash_1.0.10-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkqrZAbIbS8eaR6AwVPGmYxdIZxMFAmoGsNgACgkQVPGmYxdI
ZxNiNRAAlgjlP3BcHZg5zF+8YV1JFox8eZdhVKsl5wRT7kOjDwNAf13U4XGULPo2
cbSEletPTtWnmesh+5QV9+t7zpgbAz/zFjkmKHIIWsR79EnPhp0OS3d702c4agC+
vjk2W40pBQLjW362jojnv37WR8asawVKZPgODcxRzW2nAMqZvTSTOm3kMWun1FOS
0AABGMuni7nXvqa38dmILOVwaANnJoD3Ic0vJ0bkspUN4NqEr0+BYykBt48htCwx
imCO1eKoyXTZDxNSA0ITL/GQENaRf7IQ19RTbbnWaEeblhTiFTqbKX23VRgZYUhc
O20lo99Q4Ak2qtn34l1fR0cSb32hPJ4F+y+yGrkRWx5smPS3sLj+XbLGOHnqiy+3
3/TvQSXIjZZgBGCK2UGCCWx95akAq55HZbRVKTuzLmjOL34MSVOdEpM3BvqBmHYw
wKRhlmZCRaniICldg5mf1Nrq55C3Onzps06etEbsomsHYWBSCYdslpBc3OeWfFld
Aup4/bRxaAuHB8LekvMrowe6u/B4i9SrcDj1TS+96hB5q4cX8IUw65E6p1MGykAC
kohNHQjTU+fX8+QuqJ8o8FQCKU0r+Z+I/ZcgVQDN5Oz5KYMJAj7Jy+QmlpcaedVB
X1WXTQyM9d/L2tDKMBf13iJMydBiqA6J5h4+rqfG3DWncY3ALhs=
=wq5N
-----END PGP SIGNATURE-----

Attachment: pgpa7YIReUkFl.pgp
Description: PGP signature


--- End Message ---

Reply via email to