Your message dated Tue, 29 Nov 2022 16:08:14 +0000
with message-id <[email protected]>
and subject line Bug#1025054: fixed in cryptsetup 2:2.6.0-2
has caused the Debian Bug report #1025054,
regarding libcryptsetup-dev: missing dependencies cause rdeps FTBFS (new
pkgconfig Requires.private)
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.)
--
1025054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025054
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libcryptsetup-dev
Version: 2:2.6.0-1
Severity: important
Hi,
cryptsetup's pkgconfig ini 4.6.0 includes new Requires.private, but
the corresponding dependencies were not added to libcryptsetup-dev, so
reverse deps are failing to build:
../meson.build:1308:8: ERROR: Dependency lookup for libcryptsetup with
method 'pkgconfig' failed: Could not generate cargs for libcryptsetup:
4857Package devmapper was not found in the pkg-config search path.
4858Perhaps you should add the directory containing `devmapper.pc'
4859to the PKG_CONFIG_PATH environment variable
4860Package 'devmapper', required by 'libcryptsetup', not found
4861Package 'libargon2', required by 'libcryptsetup', not found
In an ideal world dpkg would just understand pkg-config natively like
rpm does, and fill these in automatically, but alas we are where we
are. Please add:
libdevmapper-dev
libargon2-dev
uuid-dev
libjson-c-dev
libssl-dev
libblkid-dev
to libcryptsetup-dev's Depends field. Thanks!
Kind regards,
Luca Boccassi
--- End Message ---
--- Begin Message ---
Source: cryptsetup
Source-Version: 2:2.6.0-2
Done: Guilhem Moulin <[email protected]>
We believe that the bug you reported is fixed in the latest version of
cryptsetup, 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.
Guilhem Moulin <[email protected]> (supplier of updated cryptsetup 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: Tue, 29 Nov 2022 15:42:25 +0100
Source: cryptsetup
Architecture: source
Version: 2:2.6.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Cryptsetup Team
<[email protected]>
Changed-By: Guilhem Moulin <[email protected]>
Closes: 1025054
Changes:
cryptsetup (2:2.6.0-2) unstable; urgency=low
.
* libcryptsetup-dev: Add 'Depends: libargon2-dev, libblkid-dev,
libdevmapper-dev, libjson-c-dev, libssl-dev, uuid-dev' to account for
libcryptsetup.pc's Requires.private. Closes: #1025054.
Checksums-Sha1:
c24e75ed9c0934f6846f578409e4a4de463fd0c0 3610 cryptsetup_2.6.0-2.dsc
c3610f913b49964fa1998744b8c4eecbc93cc71e 153752
cryptsetup_2.6.0-2.debian.tar.xz
628682239c0a7e9b7a6bd668573072fee40ef402 11656
cryptsetup_2.6.0-2_amd64.buildinfo
Checksums-Sha256:
75c0c5ec07109ecd4eb7f4f1e45fe8239554a814a7d2424c2d742953c0d50bbe 3610
cryptsetup_2.6.0-2.dsc
63e7008fea4932b859064f9cee09c33210ea115c17f1e5c09575f91129487562 153752
cryptsetup_2.6.0-2.debian.tar.xz
3b0e056af99e709993537a102296b18d919d5e5099ef17c8d31bb5393eba7c05 11656
cryptsetup_2.6.0-2_amd64.buildinfo
Files:
02b5dc1fbae3128eec358d0114ac057b 3610 admin optional cryptsetup_2.6.0-2.dsc
39ed5febe1b954f404748016eeba48ef 153752 admin optional
cryptsetup_2.6.0-2.debian.tar.xz
9f42fb8de76c6059cfd285e017a959e7 11656 admin optional
cryptsetup_2.6.0-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmOGG+EACgkQ05pJnDwh
pVKF0hAAnncNc/FKL0u5RLOOkpLGG/i5kLgL8fL2snpXwfQy8XD1eq0P6oDWqy02
5+zeWxDWn3VYl1zI2wH3ECfz94MPGhyZmNgMfp/2MZlc44hPtOHueo/UsLDRlPog
WNUhFNY+tiQPRGJTNAESuusdvkNXUBqHucwEskwwxVENUcP1MOl9OLf7O5ZhQfQW
c6gaVMS1ztyp5Mt2KjX8vBOfLUUJBzMr3d2HOFzLtxNTJfT9RufDXx/Qda8nSW+b
0af3VEKoI5wjlziTk182bQ5L9yrFwXqsG3zHRPq48nOuW4vMwK3tVRdRZKIAFeKB
B+A2NVkIR1g0DsTMIj0C5EME82B8fJoHh0xKgmdpXmiPzhauaAV1UccytEBhGWDE
RaErObIrzzxMcwN2/9kT397gtgo/Ym3JDKIHwazcRrLbm3KoQV6ie65ULuaHwjTy
B0KKbnx0o2M+xlWDiPTmNQ030HRA1/nYIEaR0g+q8FuXdDK893GqNEOLeMs+8cnv
KaPUoA0cp2Fs3k/1joAKxjktU7i7YZAoUrKhdvIX/K6DL1r7gqnXB7yKP74TqelG
Z8f2EmpuDC7WYmZJMVTH1YVr5IK5QAihScvZhTjUh2nK9vNfCgnKTQQai5FVg8Re
LNkI86Y5Z5JOK5LyXEs7fQuqGRxutzhdYnJuuVkXBc76RDr73jE=
=f5xr
-----END PGP SIGNATURE-----
--- End Message ---
