Hi Am 23.03.21 um 17:08 schrieb Santiago Ruano Rincón:
Dear Release Team, Could you please take a look at https://bugs.debian.org/959022 Would you agree to tag it bullseye-ignore, as pointed out by zigo here below (and proposed also by mbiebl on irc)?
Just to clarify: Ignoring the issue is not something I'd propose, but it is an available option. If we leave libgroup as-is, it means rdeps of libcgroup/cgroup-tools would have to disable cgroupv2 in systemd and boot with the cgroupv1 / the old hybrid setup if they want to use cgroup functionality in those rdeps.
They can do that via the systemd.unified_cgroup_hierarchy=false kernel command line parameter.
The old, hybrid cgroup setup is no longer actively used by systemd upstream and generally discouraged. I would consider such a setup as unsupported/semi-supported by systemd upstream.
So this should be used with care, especially considering that cgroupv1 support will deteriorate 3 years down the lane.
If this libcgroup bug is tagged bullseye-ignore, it should probably have a section in the release notes with a warning in that regards.
I appologize for this. Somehow this slipped through the cracks. I didn't really check that libcgroup had relevant rdeps.
Regards, Michael
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature