On 2025-03-01 06:24 +0100, Guillem Jover wrote:
> Package: libc6
> Version: 2.41-2
> Severity: serious
>
> Hi!
>
> It looks like at least libc6:amd64 and libc6:i386 contain different
> content for /usr/share/lintian/overrides/libc6, which makes them fail
> to co-install. During an upgrade I just got this.
>
> ,---
> Unpacking libc6:i386 (2.41-2) over (2.40-7) ...
> dpkg: error processing archive
> /var/cache/apt/archives/libc6_2.41-2_i386.deb (--unpack):
> trying to overwrite shared '/usr/share/lintian/overrides/libc6', which is
> diffearent from other instances of package libc6:i386
> `---
>
> The diff for the files is:
>
> ,---
> --- libc-amd64/usr/share/lintian/overrides/libc6 2025-02-28
> 18:57:42.000000000 +0100
> +++ libc-i386/usr/share/lintian/overrides/libc6 2025-02-28
> 18:57:42.000000000 +0100
> @@ -7,7 +7,6 @@
>
> # A linker script is used instead of a symlink (see debian-policy
> bug#1095039)
> lacks-unversioned-link-to-shared-library * [*/libc.so.*]
> -lacks-unversioned-link-to-shared-library * [*/libm.so.*]
>
> # These are empty libraries shipped for backward compatibilities
> lacks-unversioned-link-to-shared-library * [*/libdl.so.*]
> `---
I worked around it by using dpkg's --force-overwrite option, but ran
into another problem with the libc6-dev override. Here is the diff for
/usr/share/lintian/overrides/libc6-dev in libc6-dev:amd64 and
libc6-dev:i386:
--- libc-amd64/usr/share/lintian/overrides/libc6-dev 2025-02-28 18:57:42.000000000 +0100
+++ libc-i386/usr/share/lintian/overrides/libc6-dev 2025-02-28 18:57:42.000000000 +0100
@@ -14,5 +14,4 @@
no-code-sections [*/libutil.a]
# Lintian false positive (see bug#994716)
-unpack-message-for-deb-data ar failed for */libm.a
unpack-message-for-deb-data ar failed for */libmcheck.a
Cheers,
Sven
