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

Bug#1106801: marked as done (integrit: statically linked against glibc without a Built-Using: field)

Your message dated Fri, 30 May 2025 09:51:03 +0000
with message-id <E1uKwOF-009IOg-Aa@fasolo.debian.org>
and subject line Bug#1106801: fixed in integrit 4.1-7
has caused the Debian Bug report #1106801,
regarding integrit: statically linked against glibc without a Built-Using: field
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.)


-- 
1106801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106801
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: integrit
Version: 4.1-3
Severity: serious
Justification: Policy 7.8

Dear maintainer,

The integrit packages provides the following files, which are statically
linked against glibc:
/usr/sbin/integrit
/usr/sbin/i-viewdb
/usr/bin/i-ls

glibc is mostly is mostly licensed under the LGPL, which requires that
the full source code of the incorporating binary package be made
available. According to Debian Policy §7.8 [1] such a binary package
MUST list the glibc source package (and possibly others) in the
Built-Using: field.

Regards
Aurelien

[1] https://www.debian.org/doc/debian-policy/ch-relationships.html#additional-source-packages-used-to-build-the-binary-built-using

--- End Message ---
--- Begin Message --- 
Source: integrit
Source-Version: 4.1-7
Done: Aurelien Jarno <aurel32@debian.org>

We believe that the bug you reported is fixed in the latest version of
integrit, 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 1106801@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno <aurel32@debian.org> (supplier of updated integrit 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 ftpmaster@ftp-master.debian.org)


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

Format: 1.8
Date: Fri, 30 May 2025 11:22:02 +0200
Source: integrit
Architecture: source
Version: 4.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 1106801
Changes:
 integrit (4.1-7) unstable; urgency=medium
 .
   * QA upload.
   * Generate Built-Using for glibc due to static linking (Closes: #1106801)
Checksums-Sha1:
 a3215c4d84dc43a48eb2dbc167a33bfd603faf78 1826 integrit_4.1-7.dsc
 e4d95b54f98473c73c05c15325f7b5e2fc0a6054 9812 integrit_4.1-7.debian.tar.xz
 dadf17c167b1880c644cbdc726293cf21a1e2c9a 5816 integrit_4.1-7_source.buildinfo
Checksums-Sha256:
 85f4cff21ae0c855d452bae34f5a241d0e5baf84f2382e4a7aa21149d2485c99 1826 integrit_4.1-7.dsc
 9560d9c739b981b1740ee81451c5c83ad33bf6f3b71b7bd23edd5ea837dfd302 9812 integrit_4.1-7.debian.tar.xz
 3b8db79c10f9eabe4016f4236e4e9c7bd3849bf685447c2df21de30e8d60cec4 5816 integrit_4.1-7_source.buildinfo
Files:
 4aa6e6bd375fbee500cafab861a41a2f 1826 admin optional integrit_4.1-7.dsc
 0c69dc1294ea2c96ce8b7caf24561c37 9812 admin optional integrit_4.1-7.debian.tar.xz
 b4c7c714f9df0e932b86f5e7db32e93c 5816 admin optional integrit_4.1-7_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmg5es0ACgkQE4jA+Jno
M2s/AA//diPuID8qCgx1bRI4vopSYq3kMlymhTQk6X5Ui7bfe/PWn6ZIL0qIMwLv
UXZcEd0vVtUqIU/TMV+MvEAGWAiBCvXslPYViEoeCwnBFd5+G8jSjVyDzqeSHiiS
GZPpH3FGwuH3d7Bcuye2Z27M0ZPBx6Ub8tpSiZ74V+1r2c8dz6VRurHxpbhoMmqQ
moNUMuZEnJ1Yxn2mssmc6mkueHyDMWg7bmM2Q2klmSGUANDe5dus4P8REhcnIzck
jxoqfTAFLC6Yf5uVFswaRKO0MsuF8OGh2dSqpjvBedBXfT/1bKVMDwKgpUjCUxmU
jhm1YTb0kXyaiQq4ZYORmPu42tVxE+ejxp1FNYZ3/zYwyAXRbd63OusgreXPka2N
q/vVJYsDBv6p8vjg4bz6MuScVlR8IIdIqZzi8KCOsLFcTVu2B9iaBT1vKzqgPejs
baQx1JGbHrUkaLdMdYKZOsP+qznDJmxBf1SLmImSAmxChpKVkyUfrZavJSRuUCEs
gqizB7JQyjQVia2UExaZ4H+LRPScmThO016bmSiUwLdMq8dYmmieOV63+pmKPP1O
Fwjgz05G8wICYPIFVoIKhD96ZLqc1m47wcR1BXIBVTB+0dclBgIDfUKat2A2j1cJ
CRX9kCaDZO9lBo44/GsgZqgNKZU78wu62U1cdgEKfMYeXdkI/eo=
=BeIy
-----END PGP SIGNATURE-----

Attachment: pgpUYz6NkQ8ir.pgp
Description: PGP signature


--- End Message ---
Reply to: