Problem installing libc6_2.28-10_i386.deb while doing an apt-get dist-upgrade

Forum Forums Official Releases antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” Problem installing libc6_2.28-10_i386.deb while doing an apt-get dist-upgrade

  • This topic has 3 replies, 3 voices, and was last updated May 11-9:56 pm by anticapitalista.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #59262
    Member
    model99

      I have a frugal install of antiX 19.3

      The following text is from trying to do a sudo apt-get –fix-broken install
      after having the same error message appear when I did a sudo apt-get dist-upgrade.

      $ sudo apt-get --fix-broken install
      [sudo] password for demo: 
      Reading package lists... Done
      Building dependency tree       
      Reading state information... Done
      Correcting dependencies... Done
      The following packages were automatically installed and are no longer required:
        libexo-1-0 liblua5.2-0 libvulkan1
      Use 'sudo apt autoremove' to remove them.
      The following additional packages will be installed:
        libc6:i386
      Suggested packages:
        glibc-doc:i386 locales:i386
      Recommended packages:
        libidn2-0:i386
      The following NEW packages will be installed:
        libc6:i386
      0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
      2 not fully installed or removed.
      Need to get 0 B/2,743 kB of archives.
      After this operation, 11.8 MB of additional disk space will be used.
      Do you want to continue? [Y/n] y
      Preconfiguring packages ...
      (Reading database ... 207973 files and directories currently installed.)
      Preparing to unpack .../libc6_2.28-10_i386.deb ...
      ERROR: Your kernel version indicates a revision number
      of 255 or greater.  Glibc has a number of built in
      assumptions that this revision number is less than 255.
      If you\'ve built your own kernel, please make sure that any
      custom version numbers are appended to the upstream
      kernel number with a dash or some other delimiter.
      
      dpkg: error processing archive /var/cache/apt/archives/libc6_2.28-10_i386.deb (--unpack):
       new libc6:i386 package pre-installation script subprocess returned error exit status 1
      Errors were encountered while processing:
       /var/cache/apt/archives/libc6_2.28-10_i386.deb
      E: Sub-process /usr/bin/dpkg returned an error code (1)

      Here is information about my computer:

      System:
        Host: antix1 Kernel: 4.9.264-antix.1-amd64-smp x86_64 bits: 64 
        Desktop: IceWM 2.3.4 
        Distro: antiX-19.3_x64-full Manolis Glezos 15 October 2020 
      Machine:
        Type: Laptop System: HP product: HP Notebook v: Type1ProductConfigId 
        serial: <root required> 
        Mobo: HP model: 81EB v: 61.38 serial: <root required> UEFI: Insyde v: F.21 
        date: 10/27/2016 
      Battery:
        ID-1: BAT1 charge: 30.4 Wh condition: 30.4/31.1 Wh (98%) 
      CPU:
        Dual Core: Intel Core i3-6100U type: MT MCP speed: 700 MHz 
        min/max: 400/2300 MHz 
      Graphics:
        Device-1: Intel HD Graphics 520 driver: i915 v: kernel 
        Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa 
        resolution: 1366x768~60Hz 
        OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) 
        v: 4.5 Mesa 18.3.6 
      Network:
        Device-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet 
        driver: r8169 
        Device-2: Intel Wireless 3165 driver: iwlwifi 
      Drives:
        Local Storage: total: 931.51 GiB used: 10.14 GiB (1.1%) 
      Info:
        Processes: 146 Uptime: 12m Memory: 7.76 GiB used: 515.0 MiB (6.5%) 
        Shell: bash inxi: 3.0.36 
      
      
      #59264
      Member
      Xecure
        Helpful
        Up
        0
        ::

        This is a problem already reported in the forum.
        The recommendation is to install the latest 4.9.0-264 kernel using the package installer, reboot and select the kernel from the grub advanced boot menu.
        When inside the system, check it is the correct kernel 4.9.0-264
        uname .r
        fix packages again. After this, REMOVE ALL 4.9.XXX kernels except for the 4.9.0-XXX one. This is important so that it automatically boots into this kernel in the future.

        antiX Live system enthusiast.
        General Live Boot Parameters for antiX.

        #59273
        Member
        model99
          Helpful
          Up
          0
          ::

          As stated in my original post this is a frugal install and from my computer information
          you can see kernel 4.9.0-264 is already installed and boots into that kernel.

          But I did take your advice to remove any older kernels from the frugal install.

          From Synaptics history log:

          Completely removed the following packages:
          linux-image-4.9.235-antix.1-amd64-smp
          
          Removed the following packages:
          codecs-antix
          libgcc1:i386
          
          Completely removed the following packages:
          linux-image-4.9.261-antix.1-amd64-smp

          After that I did another “sudo apt-get –fix-broken install” and it was clean.

          That is a first for me in 15+ years using Linux that I had to remove a Linux kernel
          to solve a dependency problem.

          #59274
          Forum Admin
          anticapitalista
            Helpful
            Up
            0
            ::

            It maybe a first for you, but the issue was documented.

            https://antixlinux.com/new-builds-of-4-4-and-4-9-kernels/

            Philosophers have interpreted the world in many ways; the point is to change it.

            antiX with runit - leaner and meaner.

          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.