Bug#1081888: [RFD] Update partman-auto/cap-ram default value to re-allow hibernation

[Pascal Hambourg]

Package: partman-auto
Version: 167
Tags: d-i

Dear maintainers,

The debconf setting partman-auto/cap-ram was introduced to deal with the
very special case of systems with more RAM than disk space with previous
recipes setting the minimum (and maximum in most cases) swap size to
100% of RAM size. On the other hand, the maximum swap size of 1GB caused
by its default value breaks hibernation in many cases.

partman-auto 167 provides updated recipes with new limits. Swap maximum
size is now the lower of 100% of RAM size or ~5% or disk space. This
should be enough to deal with the above special case while allowing
hibernation on systems with enough disk space.

But partman-auto/cap-ram still gets in the way. I believe it is time to
update its default value: either disable it completely, or raise it to a
value which does not prevent hibernation on the majority or systems,
e.g. 64GB. I hope a consensus can be reached.

[Holger Wansing]

I think with these new recipes in place, we should be able
to disable cap-ram completely by default.

Comments/objections?


Holger

[Holger Wansing]

Hi,

Post by Holger Wansing
I think with these new recipes in place, we should be able
to disable cap-ram completely by default.
Comments/objections?

I created a merge request for this:
https://salsa.debian.org/installer-team/partman-auto/-/merge_requests/20

Tests via the mini.iso built by salsa-CI have shown, that it works as expected
(swap can grow until the size of RAM now).

[Debian Bug Tracking System]

Your message dated Fri, 22 Nov 2024 14:45:03 +0100
with message-id <***@mailbox.org>
and subject line Re: #1081888 [RFD] Update partman-auto/cap-ram default value to re-allow hibernation
has caused the Debian Bug report #1081888,
regarding [RFD] Update partman-auto/cap-ram default value to re-allow hibernation
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 ***@bugs.debian.org
immediately.)