glibc and glibc-eac-bin are in conflict (Installed glibc-eac-bin for Insurgency Sandstorm) - eviltoast

Hello everybody! My brother plays Insurgency Sandstorm a lot and I wanted us to be able to play together, so I got it and after some messing about got it working on my system. One of the things I read in forum posts to do to get it to work on an Arch based system is to install glibc-eac-bin which has some patches to make certain games work (I hope I understood that correctly).

Today when I try to update my system I get the following message and it will not allow me to continue:

:: Starting full system upgrade...

resolving dependencies...

looking for conflicting packages...

:: glibc-2.40+r16+gaa533d58ff-1 and glibc-eac-bin-2.40-1 are in conflict. Remove glibc-eac-bin? [y/N]

I dont want to remove glibc, but i want the message to go away and to be able to proceed with my updates. Any suggestions on what I should do?

Thanks in advance

  • FrostyPolicy@suppo.fi
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    3 months ago

    I’d say wait a few days to see if glibc-eac-bin gets updated. Could the name refer to easy anti cheat perhaps? The glibc is the official library that comes with Linux distros.

    • Lucy :3@feddit.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Yes, glibc-eac is a special version of glibc which supports steams new linux EAC “app”, which is required for some/most eac games now, eg. Sea of thieves. I don’t have issues using just glibc-eac - which is obviously the self compiled version - as far as I know (I didn’t update in some days).

        • Lucy :3@feddit.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          3 months ago

          I believe so. According to the PKGBUILD of glibc-eac, it not only conflicts with glibc (the package) but also provides glibc (the dependency for other packages), which means it’s a drop-in replacement. Usually, the -bin version is exactly the same, just precompiled, so the same applies.

          Btw, I forgot there was a bin version and I painstakingly compiled it every time, thanks for reminding me :3

          Also: Don’t forget to install glibc-eac-locales. Gave me headaches when I forgot it.

          • promitheas@programming.devOP
            link
            fedilink
            arrow-up
            0
            ·
            3 months ago

            Ok so even though glibc is quite deeply integrated at the system level, its okay to replace it with the eac version(?). And what about the glibc-eac-locales? What are they for and why is it necessary to manually install them?

            Yea, I learned my lesson about -bin packages a while ago with electron or something related to it. When I tell you it was taking several hours to compile and I was getting worried because while I dont have a supercomputer its on the high-end for an average user… xD I immediately grabbed the bin package right after that update finished.

            • Lucy :3@feddit.org
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              3 months ago

              glibc-eac is basically glibc, except with a few patches applied. Like literally just one additional .patch file. You can see that on the AUR listing, there is an additional patch called reenable DT, and the PKGBUILD applies this patch implying it’s the only thing that needs to be changed. And indeed, the original PKGBUILD differs in just that one patch, afaik. They even have the same version number (as you can see with pacman -Q glibc-eac and pacman -Ss glibc). This means as long as the custom glibc-eac does not get out of sync too much, it’s fine, as other packages usually don’t rely on an exact version - it can’t be guaranteed that the most recent version of something is installed all the time anyway.
              As I see it, there’s glibc and glibc-locales. And for some reason you need to install glibc-eac-locales instead of just glibc-locales when using glibc-eac - I guess it’s because it’s a split package, which means multiple packages are built with the same source.
              On the same note, you’ll also need the 32 bit version for steam things - basically just use the AUR manager of your choosing, search for glibc-eac and install everything that has a just-glibc equivalent already installed.

              And on the topic of compiling: After installing LFS on a 14 yo Dell Latitude with Core 2 Duo (that thing could legally drink and fuck here in germany) I’m very patient and grateful for even my 5 2600 (6 cores). But it’s a nice experience to compile stuff on my E5-2680 (14 cores). And I’m looking forward to the 9 9950x (16 cores) :3