Your message dated Sat, 19 Jul 2025 07:23:52 +0000
with message-id <[email protected]>
and subject line Re: snapd: statically linked against glibc without a
Built-Using: field
has caused the Debian Bug report #1106808,
regarding snapd: 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 [email protected]
immediately.)
--
1106808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106808
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: snapd
Version: 2.57.6-1
Severity: serious
Justification: Policy 7.8
Dear maintainer,
The snapd package provides the following files which are statically
linked against glibc:
/usr/lib/snapd/snap-update-ns
/usr/lib/snapd/snap-gdbserver-shim
/usr/lib/snapd/snap-gdb-shim
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: snapd
Source-Version: 2.68.3-3
Done: Zygmunt Bazyli Krynicki <[email protected]>
This was fixed with the upload of src:snapd 2.68.3-3, but there wasn't
a Closes stanza in the changelog to automatically close this bug.
https://tracker.debian.org/news/1650947/accepted-snapd-2683-3-source-into-unstable/
signature.asc
Description: This is a digitally signed message part
--- End Message ---
