Your message dated Mon, 12 Oct 2026 16:06:57 +0000
with message-id <[email protected]>
and subject line Bug#1149922: fixed in guess-concurrency 0+20260512
has caused the Debian Bug report #1149922,
regarding guess-concurrency: Please consider using MemTotal instead of
MemAvailable for --require-mem
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 [email protected]
immediately.)
--
1149922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149922
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: guess-concurrency
Version: 0+20260511
Severity: normal
Control: affects -1 vtk9
Hi,
Thanks for providing guess-concurrency, it's a clear improvement over
the number of open-coded equivalents in many debian/rules file.
That said, I have observed that MemAvailable is sometimes significantly
lower than expected on some build daemons. I have tracked that to the
use of tmpfs as the build directory (which by the way is the default in
sbuild): until the data is flushed to the swap, the corresponding memory
amount disappears from MemAvailable. This causes the number of jobs to
be reduced for no real reason (the memory is still be available for
build), especially for packages with big sources.
Could you please consider using MemTotal instead? I think it represents
better the amount of memory a build daemon is able to use.
Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: guess-concurrency
Source-Version: 0+20260512
Done: Helmut Grohne <[email protected]>
We believe that the bug you reported is fixed in the latest version of
guess-concurrency, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Helmut Grohne <[email protected]> (supplier of updated guess-concurrency
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 12 Oct 2026 17:50:56 +0200
Source: guess-concurrency
Architecture: source
Version: 0+20260512
Distribution: unstable
Urgency: medium
Maintainer: Helmut Grohne <[email protected]>
Changed-By: Helmut Grohne <[email protected]>
Closes: 1149922
Changes:
guess-concurrency (0+20260512) unstable; urgency=medium
.
* Clarify how guess_python can return None
* Revamp --detect semantics
* Add a --debug option
* Change the estimation of available memory to consider tmpfs as
swappable (Closes: #1149922)
* Document downsides of using guess_concurrency in Debian
Checksums-Sha1:
f657b49c937e60a145033cfb2686ba621dffad11 1763 guess-concurrency_0+20260512.dsc
9b393c92b109144b70f1f5befe0bc6f456b65445 7028
guess-concurrency_0+20260512.tar.xz
Checksums-Sha256:
fdc6ac221961d170d54fcd3770c4530675b2dad151d7b3676e62f0dd5c3bf84a 1763
guess-concurrency_0+20260512.dsc
1d9dfa6544c7895403b322f857fab6002c287c4de44ca7a0b5de1918c9a0e58e 7028
guess-concurrency_0+20260512.tar.xz
Files:
0947760dd4e38f2479fd2c88141df5de 1763 devel optional
guess-concurrency_0+20260512.dsc
88b7363f25bd1aea098351985fccdbb6 7028 devel optional
guess-concurrency_0+20260512.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEETMLS2QqNFlTb+HOqLRqqzyREREIFAmrNAgMACgkQLRqqzyRE
REL0Eg//fJQt3q5ujkXW5SIlmWwuJLpQhuSAQ7icbRsztxXaMGnn8mdekTfkA+dv
AjxY/x37mhfS+M+VN0icz++Akyh2by9STv0DBvWJPngdFjneYL00B3mpoY++oTh9
WMvmvO70z9U+r5nGCeSjjaIDclx5IIx9gpNhMjcyHVJmzPeCGgP8h7FOFRElfLFJ
If+poR3wGnfdakE9Qa3Mh0xfZkbR0d3E/URUuceIGyT4C+n2/7y3vXFb7LjQ3BxX
itVnta9N8zDMnimCCoobXeSdiQckpTN0zsTX+zr4L/EJJoCdww1fsFXR1Yi0Bthq
aji3BXGN0O3OqU63K3aeJygAKxlGdhX/gnCIEo9h69KcqXimwZwLtyT2iBBV7xG0
N5Dh1G6AK1IUmUUMGBu7u//amYlgTjfU4d1SbtML4Zyezl6o0Wke3cJxI6mG0ZI2
WDY4tbE4kRq+DqFanxHQAkvhQzYsPcry29MOvCM2Ag3wB0uSNQN/vmVWfRgwEoRU
NTfj2BVO7VmmN/OlD+KL8HAzhDxAWxeHipJkHnlg9/ECQpRHyPoJm2RorkAknXrH
rPyVcmhCu8LmBHqFdEU+hVl07nlHXGCQ2c9nZYZE82Hxv+61KjNzbyo0SZBLqY/l
D3gjWoisWsyhhHz5iFuyJ8biWxFLn6bmG3XrKmtx6VAP5QFqeIM=
=ivCv
-----END PGP SIGNATURE-----
pgp4YJt2FS0is.pgp
Description: PGP signature
--- End Message ---
