* Package name    : golang-github-opencontainers-cgroups
  Version         : 0.0.4-1
  Upstream Author : Open Container Initiative
* URL             : https://github.com/opencontainers/cgroups
* License         : Apache-2.0
  Programming Lang: Go
  Description     : Go library for managing Linux control groups (cgroups) - source

This library provides a native Go implementation for managing and interacting
with Linux control groups (cgroups), specifically for the unified hierarchy
(cgroups v2) and the legacy hierarchy (cgroups v1). It is a core dependency for
container runtimes and other utilities that require fine-grained resource
management of processes (e.g., CPU, memory, I/O, and pids).

Key features include:

 • A clean and idiomatic Go API for creating, managing, and destroying cgroups.                                                           • Full support for both cgroups v1 and v2.
 • Loading and parsing existing cgroup configurations from the system.
 • Comprehensive management of all standard controllers (subsystems) such as cpu, cpuset, memory, io, pids, and rdma.
 • Statistics and metrics retrieval from cgroups.

This package contains the source code needed to build packages that use this
library. It is a fundamental component of the Open Containers Initiative (OCI)
ecosystem and is used by projects like containerd and runc.

Hey,

I'm currently looking into packaging opencontainers/cgroups (cf.
https://bugs.debian.org/1111929), which requires a newer version of
cilium/ebpf. I notice that our version 0.11 is quite old, last updated over
a year ago, and the latest version is 0.19. I've chosen 0.17.3 anyway,
because that version is what is referenced by runc 1.3 and
opencontainers/cgroups, to minimize risk.

However, as it turns out, the newer version 0.17.3 not only introduces a
few more dependencies, but also some API Changes. You can see those
breakages in debusine at
https://debusine.debian.net/debian/developers/work-request/147825/

I've also cleaned up the packaging and made it "lintian clean". I'm going
to upload 0.17.3 to experimental and file bugs against the affected
packages.

Let me know if you have any questions or concerns with this approach. Help,
as always, much appreciated.

Reinhard Tartler <siretart@gmail.com> writes:

Could you describe a step-by-step process of how you did this?
Presumably this builds all reverse build dependencies with the proposed
new package?  The debusine documentation seems good, but I've not been
able to figure out how to do anything useful with it so far.

Btw, +1 on your upload.

/Simon