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

    • pewpew@feddit.itOP
      2·
      2 months ago

      What’s the output of apt —fix-broken install, like the big red error message suggests?

      You can see it in the post image. I’m using Debian Unstable

      • stupid_asshole69 [none/use name]@hexbear.netEnglish
        1·
        2 months ago

        Good looking out. I only saw the one inline with your post body.

        You’re on sid, using cosmic and have a read only root filesystem. Is there anything else out of the ordinary with your computer? You replied to another post that you removed additional repos from sources but did you get the ones in sources.d/?

        E: sources.list.d, not sources.d

        • pewpew@feddit.itOP
          1·
          2 months ago

          Correction: My filesystem is not read only. Dpkg can install .deb packages just fine

          My guess is that I tried to update packages in a specific time that there was a dependency issue in the Debian Unstable repository.

          Cosmic actually compiled and installed perfectly and the system still works and runs stable. It is a problem with Apt

  • pewpew@feddit.itOP
    3·
    2 months ago

    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

    • med@sh.itjust.worksEnglish
      3·
      2 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
  • nil@piefed.caEnglish
    3·
    2 months ago

    I suggest you install the stable version (since stability and predictability are the main features of Debian). If you need the latest packages go Arch (or any other rolling-release distro).

    • pewpew@feddit.itOP
      2·
      2 months ago

      I’ve been using Debian Unstable for about one year since I wanted Plasma 6 so bad. Even after Trixie came out I didn’t switch back to Stable because it runs good and gets frequent updates.

      The experience was actually quite smooth, better than what my friend has with Kubuntu, which for every distro update has a 50% chance of breaking

      • nil@piefed.caEnglish
        1·
        2 months ago

        I once tried to backport a package on Debian stable because I really wanted to run xwayland-satellite on Niri and I ended up breaking the system. I was using stable debian as-is since then, before switching to Arch.

    • pewpew@feddit.itOP
      1·
      2 months ago

      I regularly update using a macro in the terminal that just runs sudo apt update && sudo apt upgrade but this time I decided to install an update via the COSMIC store