vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 752db4b27121a522278383dea41911e3122cc705
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Jun 10 03:50:07 2026 +0000
Suppress ShellCheck SC2250 in `debcraft improve`
The SC2250 rule flags every unbraced variable reference as a style
issue, which produces excessive noise and hiding real ShellCheck issues.
Suppress this as low value and distracting:
SC2250 (style): Prefer putting braces around variable references even when not strictly required.
commit a19cdea9986318eaee8433ac7b402e604ae01571
Author: Otto Kekäläinen <otto@debian.org>
Date: Sun Jun 7 21:12:08 2026 +0800
Silence extra `mkdir` message
The extra white `mkdir` line when running a build for a new package for
the first time seemed stray and unnecessary, so silence it:
± debcraft build
Running in directory /home/otto/debian/go-team/golang-github-launchdarkly-go-ntlmssp that has Debian package sources for 'golang-github-launchdarkly-go-ntlmssp'
Use 'podman' container image 'debcraft-golang-github-launchdarkly-go-ntlmssp-debian-sid' for package 'golang-github-launchdarkly-go-ntlmssp'
DEBCRAFT WARNING: Unable to find any git tags, which are needed to identify previous release and compare build artifacts with it. Run 'git fetch --tags' to ensu
Building container 'debcraft-golang-github-launchdarkly-go-ntlmssp-debian-sid' in '/home/otto/.cache/debcraft/debcraft-container-golang-github-launchdarkly-go-nt
.0.2.1'
mkdir: created directory '/home/otto/.cache/debcraft/debcraft-container-golang-github-launchdarkly-go-ntlmssp'
STEP 1/36: FROM debian:sid
STEP 2/36: ARG HOST_ARCH
--> Using cache 7de4720a91673db29bb4022f7bc89b6dd463598dec22f3f3c73265b6769eab62
--> 7de4720a9167
STEP 3/36: ARG SOURCE_DATE_EPOCH
--> Using cache f492408c1c884914747073861caca91fd7d6839f0abe812a5770b53e2218c20b
commit ebd7ad4b879d644e35c159761972a902344edd55
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed Jun 3 09:54:21 2026 +0000
Forward global git identity into containers for commit operations
Commands like `debcraft improve` and `debcraft update` run `git commit`
inside containers, which cannot see the host's global git config. If
the repository lacked a local identity, commits would fail or use
incorrect metadata.
Add `ensure_git_identity()` to check for local configuration first.
If none exists but a global identity is available, export the standard
`GIT_AUTHOR_*` and `GIT_COMMITTER_*` environment variables so they are
forwarded into the container runtime. If neither is configured, print
a clear error message and exit.
This avoids forcing users to set `--local` git config solely to
satisfy containerized workflows. Most users would however get their
repos by running `gbp clone` that does set git name and email locally
on automatically, so the majority of users wouldn't need this extra
check.
commit 1d280c6ac052a8bba1ea89fb60f9f212de939c6a
Author: Otto Kekäläinen <otto@debian.org>
Date: Wed May 27 09:20:15 2026 +0000
Prevent GPG signing inside debcraft improve container
Containers have no GPG keys available, so Git must not try to sign
commits. Set the GIT_CONFIG_* environment variables via ENV directives
so all entrypoints inherit this policy automatically. This avoids
duplicating exports across individual scripts and keeps the
configuration in one location.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/debcraft.png){kind=link}