klibc 2.0.13-2ubuntu1 source package in Ubuntu

Changelog

klibc (2.0.13-2ubuntu1) noble; urgency=medium

  [ Klaus Frank ]
  * d/i/h/klibc-utils: Fix compatibility issue with busybox and improve verbose debug output.
    (Closes: #1055694) (LP: #2046336)

 -- Florent 'Skia' Jacquet <email address hidden>  Fri, 15 Dec 2023 16:08:42 +0100

Upload details

Uploaded by:
Skia
Sponsored by:
Paride Legovini
Uploaded to:
Noble
Original maintainer:
Ubuntu Developers
Architectures:
linux-any
Section:
libs
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
klibc_2.0.13.orig.tar.xz 461.6 KiB d673a294f742d59368222ff5c38462d81098c55063799de6fb8a7ba3d4af0436
klibc_2.0.13-2ubuntu1.debian.tar.xz 19.9 KiB 70f3924bee04a5661ea93b54d18814a4ceda922ce6490a7f6cf03a1897c5b93e
klibc_2.0.13-2ubuntu1.dsc 1.9 KiB 51b645d1d8df5cd266f500b8569cefd81d60ff19504037a2af03136ac578f389

View changes file

Binary packages built by this source

klibc-utils: small utilities built with klibc for early boot

 This package contains a collection of programs that are linked
 against klibc. These duplicate some of the functionality of a
 regular Linux toolset, but are typically much smaller than their
 full-function counterparts. They are intended for inclusion in
 initramfs images and embedded systems.

klibc-utils-dbgsym: debug symbols for klibc-utils
libklibc: minimal libc subset for use with initramfs

 klibc is intended to be a minimalistic libc subset for use with
 initramfs. It is deliberately written for small size, minimal
 entanglement, and portability, not speed. It is definitely a work in
 progress, and a lot of things are still missing.

libklibc-dbgsym: debug symbols for libklibc
libklibc-dev: kernel headers used during the build of klibc

 This package contains the set of kernel headers that were required to
 build klibc and the utilities that ship with it. This may or may
 not be a complete enough set to build other programs that link against
 klibc. If in doubt, use real kernel headers instead.