[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#832629: marked as done (CONFIG_CGROUPS=n appears to have been broken in updates)



Your message dated Sat, 16 Oct 2021 05:07:23 -0700 (PDT)
with message-id <616ac07b.1c69fb81.340e8.2728@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #832629,
regarding CONFIG_CGROUPS=n appears to have been broken in updates
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.)


-- 
832629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832629
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: important

Unfortunately I cannot finger the exact version where it happened, but it
appears one of the updates to linux-source-3.16 *broke* builds where
CONFIG_CGROUPS was left unset.  While this may be an unusual
configuration, it certainly *was* working.

I thought updates were supposed to be confined to *security* issues, the
better to avoid breaking other confirmed to work setups.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         EHeM+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

--- End Message ---
--- Begin Message ---
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---

Reply to: