Use dwz from rpm to compress debug info
an invention by rguenther
Updated almost 4 years ago. No love.

Use dwz (dwarf compressor) from rpms find-debuginfo.sh to reduce debuginfo package size. Aim for multi-file mode which would create a "base" debuginfo package that individual ones depend on (when multiple ones exist). -debuginfo package discovery is done by rpm itself while the extraction and compression is done from find-debuginfo.sh, this may complicate things a bit.

On the way fix inconsistencies in debuginfo package naming as created from rpm vs. baselibs (libgcc_s1-32bit-debuginfo vs. libz1-debuginfo-32bit).

Looking for hackers with the skills:

rpm baselibs

This project is part of:

Hack Week 15

Activity

  • almost 8 years ago: rguenther added keyword "baselibs" to this project.
  • almost 8 years ago: rguenther added keyword "rpm" to this project.
  • almost 8 years ago: rguenther started this project.
  • almost 8 years ago: rguenther originated this project.


    • Comments

    • rguenther
      almost 8 years ago by rguenther | Reply

      So the project is "finished", results should find their way into Tumbleweed / SLE-13. Updated rpm and dwz packages are in home:rguenther:hw15. To enable dwz use you currently have to adjust your projectconf:

      Support: dwz Macros: %finddebuginfodwzopts --run-dwz

      Results show a reduction in installed debuginfo size of up to 50% (glibc-debuginfo). For packages with not many binaries and libraries and which use C do not expect wonders (patchutils shows no changes, likewise telnet).

      Some packages expose issues in the current setup, like gcc6 builds multilibs and thus has a mix of 32bit and 64bit packages which means DWZs multi-file mode fails. kernel-default has bogus DWARF according to DWZ and thus it gives up (needs to be investigated).

      I did not yet try many packages but only the set in home:rguenther:hw15.

    • rguenther
      almost 5 years ago by rguenther | Reply

      This was finished.

    Similar Projects

    Switch software-o-o to parse repomd data by hennevogel

    Currently software.opensuse.org search is using the OBS binary search for everything, even for packages inside the openSUSE distributions. Let's switch this to use repomd data from download.opensuse.org

    A CLI for Harvester by mohamed.belgaied

    [comment]: # Harvester does not officially come with a CLI tool, the user is supposed to interact with Harvester mostly through the UI [comment]: # Though it is theoretically possible to use kubectl to interact with Harvester, the manipulation of Kubevirt YAML objects is absolutely not user friendly. [comment]: # Inspired by tools like multipass from Canonical to easily and rapidly create one of multiple VMs, I began the development of Harvester CLI. Currently, it works but Harvester CLI needs some love to be up-to-date with Harvester v1.0.2 and needs some bug fixes and improvements as well.

    Project Description

    Harvester CLI is a command line interface tool written in Go, designed to simplify interfacing with a Harvester cluster as a user. It is especially useful for testing purposes as you can easily and rapidly create VMs in Harvester by providing a simple command such as: harvester vm create my-vm --count 5 to create 5 VMs named my-vm-01 to my-vm-05.

    asciicast

    Harvester CLI is functional but needs a number of improvements: up-to-date functionality with Harvester v1.0.2 (some minor issues right now), modifying the default behaviour to create an opensuse VM instead of an ubuntu VM, solve some bugs, etc.

    Github Repo for Harvester CLI: https://github.com/belgaied2/harvester-cli

    Done in previous Hackweeks

    • Create a Github actions pipeline to automatically integrate Harvester CLI to Homebrew repositories: DONE
    • Automatically package Harvester CLI for OpenSUSE / Redhat RPMs or DEBs: DONE

    Goal for this Hackweek

    The goal for this Hackweek is to bring Harvester CLI up-to-speed with latest Harvester versions (v1.3.X and v1.4.X), and improve the code quality as well as implement some simple features and bug fixes.

    Some nice additions might be: * Improve handling of namespaced objects * Add features, such as network management or Load Balancer creation ? * Add more unit tests and, why not, e2e tests * Improve CI * Improve the overall code quality * Test the program and create issues for it

    Issue list is here: https://github.com/belgaied2/harvester-cli/issues

    Resources

    The project is written in Go, and using client-go the Kubernetes Go Client libraries to communicate with the Harvester API (which is Kubernetes in fact). Welcome contributions are:

    • Testing it and creating issues
    • Documentation
    • Go code improvement

    What you might learn

    Harvester CLI might be interesting to you if you want to learn more about:

    • GitHub Actions
    • Harvester as a SUSE Product
    • Go programming language
    • Kubernetes API