Your message dated Sat, 4 Mar 2023 20:44:20 +0100 with message-id <916d165a-5cd2-121c-72f0-e969674dc9e6@debian.org> and subject line Re: Bug#992213: release-notes: Release notes should mention lxc issues with cgroups change has caused the Debian Bug report #992213, regarding release-notes: Release notes should mention lxc issues with cgroups change to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 992213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992213 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: release-notes: Release notes should mention lxc issues with cgroups change
- From: Mike Hommey <mh+reportbug@glandium.org>
- Date: Mon, 16 Aug 2021 06:08:18 +0900
- Message-id: <162906169850.13680.5103341323766568328.reportbug@goemon>
Package: release-notes Severity: important The release notes has a section about the issues with openstack, but there are also problems with lxc. I'm not sure what the proper workaround is, but setting `lxc.mount.auto = cgroup:mixed:force` fixed it for me. Mike
--- End Message ---
--- Begin Message ---
- To: 992213-done@bugs.debian.org, Mike Hommey <mh@glandium.org>
- Subject: Re: Bug#992213: release-notes: Release notes should mention lxc issues with cgroups change
- From: Paul Gevers <elbrus@debian.org>
- Date: Sat, 4 Mar 2023 20:44:20 +0100
- Message-id: <916d165a-5cd2-121c-72f0-e969674dc9e6@debian.org>
- In-reply-to: <02a2527c-58b9-7320-7cd8-fa76d7219494@debian.org>
- References: <162906169850.13680.5103341323766568328.reportbug@goemon> <d04531f9-09bb-7f3e-e70f-6485974d0dc2@debian.org> <9e2a09c2-f143-6e56-1ee3-25ebb26a37bb@debian.org> <20210821211114.jetwn2xnpkgzwizo@glandium.org> <7d770dfc-d687-965c-ed0e-ad6b5430d792@debian.org> <20210821212333.t647b2nojrzkekve@glandium.org> <162906169850.13680.5103341323766568328.reportbug@goemon> <a11e18b6-dd9b-444e-d280-d9e19d20f839@debian.org> <02a2527c-58b9-7320-7cd8-fa76d7219494@debian.org> <02a2527c-58b9-7320-7cd8-fa76d7219494@debian.org>
Hi, On Thu, 23 Sep 2021 15:57:16 +0200 Paul Gevers <elbrus@debian.org> wrote:> That doesn't make an awful good release-notes report. Have you filed the > bug somewhere (e.g. against the lxc package). I think that's probably > the better course of action than to try to figure it out with the > release notes editors. Did you do anything with this? Without more information, this bug isn't really actionable.Closing as I don't believe we can do anything with the information so far. PaulAttachment: OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---