13

I'm using Ubuntu 20.04 focal fossa.

I'm trying to install a package that depends on libc6=<2.33 or above. However, focal repositories only have version 2.31, which is causing dependency troubles:

Depends: libc6 (>= 2.34) but 2.31-0ubuntu9.2 is to be installed

Is there any way I can install libc6 2.34 or above on Ubuntu 20.04 focal?

$ apt-cache policy libc6
  Installed: 2.31-0ubuntu9.2
  Candidate: 2.31-0ubuntu9.2
  Version table:
 *** 2.31-0ubuntu9.2 500
        500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     2.31-0ubuntu9 500
        500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 

Thanks!

Error404
  • 7,440
  • 10
    It's a good technical question for advanced explorers! Most folks who discover this question should keep in mind that the whole point of an LTS release is that the software doesn't change. Once you start changing basic elements deep in the stack, it's not really LTS anymore...regardless of the label. Most folks who want to run newer software should try a tested, stable 6-month release of Ubuntu instead of frankensteining an older LTS release. – user535733 Jan 28 '22 at 17:44
  • I would not do it if I was you. libc is a library touching so many core packages. I would upgrade your system to 22.04 See also https://askubuntu.com/questions/1379732/dpkg-regarding-libc6-2-34-wont-install-because-itd-break-locales-2-34-and "install a package" what package? Because I would assume there is also a 20.04 version of that package. You could install virtualbox, 22.04 in that and that package in that system as a workaround – Rinzwind Jul 02 '22 at 15:42
  • and another one https://askubuntu.com/questions/1143268/how-to-install-a-libc6-version-2-29 with the advice to not do it. Please be accurate and name the package. Maybe there is a snap version :) – Rinzwind Jul 02 '22 at 15:47
  • Are you SERIOUS to leave the vulnerable libc 2.31 with the system just for whatsoever about LTS release? It IS even worse to make a comment here, man. – Y.Z Sep 14 '22 at 16:49
  • 1
    @Rinzwind It should be totally fine to install libc to a different path, and then use patchelf to adjust the executable that won't run. Is there no way to install another libc with the alternate system in Ubuntu? – jpaugh Dec 26 '23 at 18:56
  • @Y.Z Note the distro suffix -0ubuntu9.2. glibc point releases won't stay completely still after release. It is a very common practice for packagers to backport fixes, including security fixes, from later versions or even the git master, so the security concerns simply do not exist with an up-to-date system. – mcendu Feb 05 '24 at 03:19

0 Answers0