I've been trying the COSMIC store and it looks like it killed my apt somehow. Apt says that there is a version mismatch between some libc6 packages, but I checked with dpkg and it all looks correct.

Apt says that I've a newer version of some packages but that is not true. Is there any way to fix this?

EDIT: Fixed formatting

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 11 months ago (1 child)

My best guess is that the Debian Unstable repository doesn't have all the libc6 packages updated to the same version. I might just have to wait and see what happens

  • source
  • hideshow 1 child comment
  • [–] 3 points 11 months ago

    Looks like that might have changed, libc-gconv-modules-extra has an i386 package for 2.42-5 added at like midnight UTC+1. Given the sources only update every 6 hours, might be you found an unlucky update in between?

    Struggled to find a time for the release, but the changelog has one, unsure how true to package-available time that is:

    glibc (2.42-5) unstable; urgency=medium
    
      [ Martin Bagge ]
      * Update Swedish debconf translation.  Closes: #1121991.
    
      [ Aurelien Jarno ]
      * debian/control.in/main: change libc-gconv-modules-extra to Multi-Arch:
        same as it contains libraries.
      * debian/libc6.symbols.i386, debian/libc6-i386.symbols.{amd64,x32}: force
        the minimum libc6 version to >= 2.42, to ensure GLIBC_ABI_GNU_TLS is
        available, given symbols in .gnu.version_r section are currently not
        handled by dpkg-shlibdeps.
    
     -- Aurelien Jarno <aurel32@debian.org>  Sat, 06 Dec 2025 23:02:46 +0100
    
    glibc (2.42-4) unstable; urgency=medium
    
      * Upload to unstable.
    
     -- Aurelien Jarno <aurel32@debian.org>  Wed, 03 Dec 2025 23:03:48 +0100
    
  • source
  • parent