1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1105006: flag uuid_time64 as glibc-only symbol

    From Helmut Grohne@21:1/5 to All on Fri May 9 22:40:02 2025
    Source: util-linux
    Version: 2.41-4
    Tags: patch
    User: helmutg@debian.org
    Usertags: rebootstrap

    Hi Chris,

    I got a symbol failure for util-linux on musl-linux-any. If you look at
    the source, you'll notice that uuid_time64 is a glibc-only symbol
    guarded by __GLIBC__. Please drop it from non-glibc architectures such
    as musl-linux-any. I'm attaching a patch for your convenience. I do not
    see a reason to include it in trixie, but I also do not see much risk in including it.

    Helmut

    diff --minimal -Nru util-linux-2.41/debian/changelog util-linux-2.41/debian/changelog
    --- util-linux-2.41/debian/changelog 2025-04-09 23:08:54.000000000 +0200
    +++ util-linux-2.41/debian/changelog 2025-05-09 16:13:46.000000000 +0200
    @@ -1,3 +1,10 @@
    +util-linux (2.41-4.1) UNRELEASED; urgency=medium
    +
    + * Non-maintainer upload.
    + * Update libuuid symbols for musl. (Closes: #-1)
    +
    + -- Helmut Grohne <helmut@subdivi.de> Fri, 09 May 2025 16:13:46 +0200
    +
    util-linux (2.41-4) unstable; urgency=medium

    * Pick patches from upstream v2.41-stable branch.
    diff --minimal -Nru util-linux-2.41/debian/libuuid1.symbols util-linux-2.41/debian/libuuid1.symbols
    --- util-linux-2.41/debian/libuuid1.symbols 2025-04-09 23:08:54.000000000 +0200
    +++ util-linux-2.41/debian/libuuid1.symbols 2025-05-09 16:13:44.000000000 +0200
    @@ -26,7 +26,7 @@
    uuid_parse@UUID_1.0 2.16
    uuid_parse_range@UUID_2.36 2.36
    uuid_time@UUID_1.0 2.16
    - uuid_time64@UUID_2.40 2.40
    + (arch=gnu-any-any)uuid_time64@UUID_2.40 2.40
    uuid_type@UUID_1.0 2.16
    uuid_unparse@UUID_1.0 2.16
    uuid_unparse_lower@UUID_1.0 2.1
  • From Chris Hofstaedtler@21:1/5 to All on Fri May 9 23:40:02 2025
    * Helmut Grohne <helmut@subdivi.de> [250509 22:39]:
    I got a symbol failure for util-linux on musl-linux-any. If you look at
    the source, you'll notice that uuid_time64 is a glibc-only symbol
    guarded by __GLIBC__. Please drop it from non-glibc architectures such
    as musl-linux-any.

    I can certainly do that, but I do wonder if that hides a t64 problem
    on !glibc archs.

    Best,
    Chris

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Helmut Grohne@21:1/5 to Chris Hofstaedtler on Sat May 10 09:40:01 2025
    Hi Chris,

    On Fri, May 09, 2025 at 11:31:20PM +0200, Chris Hofstaedtler wrote:
    I can certainly do that, but I do wonder if that hides a t64 problem on !glibc archs.

    At least for musl, there was a flag-day transition. Refer to https://musl.libc.org/time64.html for details. As a result, it now
    redirects time-aware functions to changed names and rebuilds pick those
    up automatically. In effect, this is very much similar to how Debian did
    the time64 switch. My understanding is that musl is fine as a result. I
    do not reason about other C libraries and none of them is in a state
    nearly as close as musl to support being a Debian libc.

    Helmut

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)