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

Bug#1106795: marked as done (libbg-dev: statically linked against glibc without a Built-Using: field)

Your message dated Fri, 30 May 2025 11:04:41 +0000
with message-id <E1uKxXV-009Sse-Cw@fasolo.debian.org>
and subject line Bug#1106795: fixed in bglibs 2.04+dfsg-8
has caused the Debian Bug report #1106795,
regarding libbg-dev: 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.)


-- 
1106795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106795
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libbg-dev
Version: 2.04+dfsg-4
Severity: serious
Justification: Policy 7.8

Dear maintainer,

The libbg-dev package provides /usr/bin/crc-gentab which is statically
linked against glibc.

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: bglibs
Source-Version: 2.04+dfsg-8
Done: Aurelien Jarno <aurel32@debian.org>

We believe that the bug you reported is fixed in the latest version of
bglibs, 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 1106795@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 bglibs 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 12:35:15 +0200
Source: bglibs
Architecture: source
Version: 2.04+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Aurelien Jarno <aurel32@debian.org>
Closes: 1106795
Changes:
 bglibs (2.04+dfsg-8) unstable; urgency=medium
 .
   * QA upload.
   * Generate Built-Using for glibc due to static linking (Closes: #1106795)
Checksums-Sha1:
 5671c68031bb5b7f0e0afee8ab22f0e61df51f10 1971 bglibs_2.04+dfsg-8.dsc
 71212d0f6219f033f485265ce7c28223a3a42828 33128 bglibs_2.04+dfsg-8.debian.tar.xz
 9238a9b934ff721e1c93eba266b2910c1575e3d0 5788 bglibs_2.04+dfsg-8_source.buildinfo
Checksums-Sha256:
 b7e0487eebfcbf2c8965b2e98ae001fa75e5a6995c1b9f022c66b59541c59ef5 1971 bglibs_2.04+dfsg-8.dsc
 178c07287e259a03fd772c1ae1728a6c297db7c19e94d233d1ed531fb712781d 33128 bglibs_2.04+dfsg-8.debian.tar.xz
 fb4fa51b9ec2b79a4590efcaef60de53d2dbfbea2d44897839f309306070625e 5788 bglibs_2.04+dfsg-8_source.buildinfo
Files:
 5fb01b9a7c43247d7f7ec0f08d79bedb 1971 devel optional bglibs_2.04+dfsg-8.dsc
 eaafc36215f40d05df08b0b210eaa8f9 33128 devel optional bglibs_2.04+dfsg-8.debian.tar.xz
 e2b7009a13b9e120e4953ad66ea25ce3 5788 devel optional bglibs_2.04+dfsg-8_source.buildinfo

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

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmg5ikUACgkQE4jA+Jno
M2vkxg/+J8XB7WGQ+byzg43zfKo0I4ixwbVdtKsVuMKWUHmguBx+K9Sb6gj60Npi
GFIyBLVuu3Le+YA0kkCT4tlb5eMNYfihpnEl8wyaHf5KlKYxnR3Zq4Iv8Iv3sJjM
kmoh88yxbN8NgmA1U9sBlEBlpFJU0IIgXYEt3uRU81n0HLnW/BCiCqDy+32KSUuG
xXGIL4YwqX3V7ymqwC3p45V1OZgTCs8OEW5bdp+RXvmFWOmg5v3oI2ibbwwLltkr
7ayR8SCBpd2cPpGmTf9NnlRpRcXWiusljWKG4KEEDkNBkWxgE+A5Kr4O5bKFFOq8
bdnfsOipwaOGg/rZ1mhjrD2RQOvIb+JX3iEG0Az3iJrK07TR6tTge+V41anECkrq
m3XnKXzq0a7HftjW6F2NPmo9RY9UDsV9jF+0GPEwzb8kPPriEkdqS3PX2kjlICVR
qMfg7PZPLnF7PwD0jN0h/SIwGgE3IzD8C8g1HaiL4GvJl4A/35CxKooYO5u+xqwB
xsm5VcHcGREbddGK4OOSoR4sW4aAg0solOqGt7dn7wpK42iW8qntHKwaS+JRedTV
Bl4K3YkEuHtVwaPV6wWjZzWiDyuieEvTcBPESSphC4l1QC507/XcWZaVaiHz63ku
A5UM06u0fIAXXk+d2CWQXeh85SzZ62D0kt0H8P58etVD1rNtOf0=
=ksSa
-----END PGP SIGNATURE-----

Attachment: pgpZt5oVmojUU.pgp
Description: PGP signature


--- End Message ---
Reply to: