Your message dated Mon, 09 Mar 2026 18:39:59 +0000
with message-id <[email protected]>
and subject line Bug#1129765: fixed in g10k 0.9.10-2
has caused the Debian Bug report #1129765,
regarding g10k has a minimum run time of one second
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.)
--
1129765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129765
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: g10k
Version: 0.9.10-2
Severity: normal
This might seem like a trivial concern, but we fire up a bunch of g10k
commands in our test suite, and it's kind of slow! I know that g10k is
actually *really* fast in terms of what it does, but I'm now faced
with a hard one-second-per-run limit that I can't get rid of
otherwise.
A good reproducer is just calling `-help`:
```
> time g10k --help 2>/dev/null
________________________________________________________
Executed in 1.01 secs fish external
usr time 0.64 millis 642.00 micros 0.00 millis
sys time 11.93 millis 139.00 micros 11.79 millis
```
That's a whole second doing essentially ... well, nothing: the total
user/sys time there is a couple miliseconds at most.
This seems to be a locking issue similar to the upstream issue #230.
The way `-help` looks, it does seem like something is spinning while
threads complete. This, of course, also applies to an empty
`-puppetfile` run:
```
> /bin/time g10k -puppetfile
Synced ./Puppetfile with 0 git repositories and 0 Forge modules in 0.0s with
git (0.0s sync, I/O 0.0s) and Forge (0.0s query+download, I/O 0.0s) using 50
resolve and 20 extract workers
0.00user 0.00system 0:01.01elapsed 1%CPU (0avgtext+0avgdata 31288maxresident)k
0inputs+0outputs (0major+1913minor)pagefaults 0swaps
```
I understand this might not be a priority, but it seems to me there's
something off here. `-maxworker` doesn't help.
This was originally filed upstream as:
https://github.com/xorpaul/g10k/issues/249
But I found out this is actually an issue with the Debian build
system. I can't reproduce the issue when building the source code with
a plain `go build`.
-- System Information:
Debian Release: 13.3
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'),
(1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.73+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages g10k depends on:
ii git 1:2.47.3-0+deb13u1
ii libc6 2.41-12+deb13u1
g10k recommends no packages.
g10k suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: g10k
Source-Version: 0.9.10-2
Done: Antoine Beaupré <[email protected]>
We believe that the bug you reported is fixed in the latest version of
g10k, 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.
Antoine Beaupré <[email protected]> (supplier of updated g10k 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, 09 Mar 2026 10:03:35 -0400
Source: g10k
Architecture: source
Version: 0.9.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team <[email protected]>
Changed-By: Antoine Beaupré <[email protected]>
Closes: 1129765
Changes:
g10k (0.9.10-2) unstable; urgency=medium
.
* remove -race flag to fix extra 1s runtime (Closes: #1129765)
Checksums-Sha1:
a92759f66c3be398bf37259885b0fdb9a9ab8e06 1868 g10k_0.9.10-2.dsc
4b46ebb1f777b36c4f894af11ea3521cea0ca870 7984 g10k_0.9.10-2.debian.tar.xz
969cbff530d4c76dba97805f7ed8241cc6ec01ed 6667 g10k_0.9.10-2_amd64.buildinfo
Checksums-Sha256:
56d3ce1cdf043af9d44e02684abc8d51e5727738e7dfc01ac01c69819ad67525 1868
g10k_0.9.10-2.dsc
c87f567f2674475bbc55c63d67bf7068cec384215b045af24f22b40a47906fa8 7984
g10k_0.9.10-2.debian.tar.xz
c84429eee295af64d2a9e13c3f2888d3ca3ef90a215d79ef33ca4274ffddad48 6667
g10k_0.9.10-2_amd64.buildinfo
Files:
a11555e78c51507eb5d56112bef7fe56 1868 devel optional g10k_0.9.10-2.dsc
ccdd6d83c2defe217a7d4219ed8753ef 7984 devel optional
g10k_0.9.10-2.debian.tar.xz
39bb0c67523a3ebda57ef67244d05c6e 6667 devel optional
g10k_0.9.10-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQS7ts1MmNdOE1inUqYCKTpvpOU0cwUCaa8KbQAKCRACKTpvpOU0
c1gUAP42r9yeL1ylPJwNUAA7cE3RZ0z8yHaEjOko7hbtqiE4iQEAog8sMwW+iWku
+nf68Oxz7hAAO4Q8u76ICgLzgLRjOQs=
=7csw
-----END PGP SIGNATURE-----
pgp5qHf3zFIFA.pgp
Description: PGP signature
--- End Message ---
