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

Re: libexpat1: missing Pre-Depends on libc6 (>= 2.38) causes error during python3-cryptography upgrade (?)



Hi Niels,

On Sun, Jul 13, 2025 at 9:37 PM Niels Thykier <niels@thykier.net> wrote:
> As short context, Lucas found a case where the upgrade can break with:
>
> > /usr/bin/python3: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /lib/x86_64-linux-gnu/libexpat.so.1)
[...]
> My recommendation is to:
>
>   1) Patch `libexpat1` to use `Pre-Depends: ${shlibs:Depends}`. It only
>      has a single dependency on amd64 (libc), so it should be safe and be
>      a work around
[...]
>    --> Do we agree with this proposal for moving forward for Trixie?
 I say let's go on this path, Trixie release is very close. Proposed
patch is attached.

Cheers,
Laszlo/GCS
diff -Nru expat-2.7.1/debian/changelog expat-2.7.1/debian/changelog
--- expat-2.7.1/debian/changelog	2025-03-27 18:56:41.000000000 +0000
+++ expat-2.7.1/debian/changelog	2025-07-14 08:05:27.000000000 +0000
@@ -1,3 +1,10 @@
+expat (2.7.1-2) unstable; urgency=medium
+
+  * Move libc6 dependency to pre-dependency on libexpat1 to prevent
+    dist-upgrade errors with python packages (closes: #1108934).
+
+ -- Laszlo Boszormenyi (GCS) <gcs@debian.org>  Mon, 14 Jul 2025 08:05:27 +0000
+
 expat (2.7.1-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru expat-2.7.1/debian/control expat-2.7.1/debian/control
--- expat-2.7.1/debian/control	2024-09-04 18:33:01.000000000 +0000
+++ expat-2.7.1/debian/control	2025-07-14 08:05:27.000000000 +0000
@@ -27,9 +27,9 @@
 Package: libexpat1
 Section: libs
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends}
 Multi-Arch: same
-Pre-Depends: ${misc:Pre-Depends}
+Pre-Depends: ${shlibs:Depends}, ${misc:Pre-Depends}
 Description: XML parsing C library - runtime library
  This package contains the runtime, shared library of expat, the C
  library for parsing XML. Expat is a stream-oriented parser in

Reply to: