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 8b75945f5987468601d40372ce4bb2adc6bfbd61
Author: Otto Kekäläinen <otto@debian.org>
Date: Mon Feb 17 21:33:03 2025 -0800
Apply patches with Quilt when dpkg-source is skipped (Closes: #11, #13)
Normally dpkg-source applies the patches when creating a source package.
Running a build on the directory that was used to create the source
package will have the patches applied, or running a build on a directory
that was extracted from a source package will have the patches applied.
However, when we run binary-only builds, or autopkgtest directly on the
Debian source repository, no patches are applied, and git needs to run
explicitly.
Make the Quilt run conditional on if a series file exists. If it does
not, the package either has no packages, or the git branch has the
patches already applied (e.g. when building a `gbp pq` branch directly).
commit 626c31268d5ae372c142929f29755b272d3acbd5
Author: Otto Kekäläinen <otto@debian.org>
Date: Mon Feb 17 21:33:03 2025 -0800
Pass $DPKG_BUILDPACKAGE_ARGS also to non-git builds
In f5b41281 the default `debcraft build` was changed to do a full build,
including sources. Passing `$DPKG_BUILDPACKAGE_ARGS` to the non-git
build was omitted, so add it now.
Also emit more specific information about what build parameters are
used.
commit 608159a2f55d78d28059b828bfc0f66e5045b120
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Apr 15 20:25:14 2025 +0300
Extend tests to build Galera skipping sources
commit 55e300de55370962ddaa81611dd0c549616a55d9
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Thu Apr 24 01:53:58 2025 -0400
Add explanation for setting explicit parameter
commit 97a4ae01adf153523b9906ece948de0aed67e96d
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Thu Apr 24 01:53:17 2025 -0400
Move logging of options to after setting default
commit d012b29e39244a9d81dc700c771f241d966c6927
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Wed Apr 23 18:45:46 2025 -0400
Apply default environment variables on cross build
When performing a cross build, some actions cannot be performed, such as
executing the resulting artifacts utilizing a foreign architecture. This
means that most auto tests fail to run. Also, some packages may need
special configurations when being cross built. The `nocheck` option
prevents the check command from running, which is usually used to run
tests. The `nocheck` and `cross` profiles can be used by packages to
control which dependencies and build processes to use when cross
building and when building without running the check command.
This lines up with how sbuild adds these environment variables when
cross building is dectected, including not overwriting the variables
when they are already set.
commit d71c77102cf6789ffbd1a2b139741c0882e0975a
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Tue Apr 22 19:07:17 2025 -0400
Update install-local target
When using the install-local target defined in the Makefile, if
`~/.local/bin` or `~/.local/share/bash-completion/completions`
directory does not exist, the target fails. Adding a couple `mkdir`
commands at the beginning of the target ensures they exist when running
the target.
commit 7327ca9dbdb60235aebf1bc1c45d9429ab4b8a24
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Tue Apr 22 19:06:49 2025 -0400
Update usage and bash completion
commit 01a32870a34a768f74e2f535c7abb6b88b1c83b6
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Tue Apr 22 17:10:15 2025 -0400
Pass HOST_ARCH to build container
By mapping the `HOST_ARCH` environment variable when running the build
container, the build process can use it to set up a cross build. It
does this by adding `--host-arch $HOST_ARCH` to the
`DPKG_BUILDPACKAGE_ARGS` variable.
commit de26128e2b908105635a15e20d1353d1a483702e
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Mon Apr 21 21:11:10 2025 -0400
Update build container image to support host arch
This update adds the option `--host-architecture` which sets the
variable `HOST_ARCH`. This value is used in the container name in order
to distinguish it from containers using other host architectures, as
well as the default container which uses the build architecture as the
host architecture. The host architecture is also passed to the build
process such that the host architecture is set up as a foreign
architecture, and that the host build dependencies use the host
architecture when resolving and installing build dependencies.
commit 2b3d1afb7a8748d6fc074f74af21ab40b889c304
Author: TheJayMann <736769+TheJayMann@users.noreply.github.com>
Date: Tue Apr 15 15:11:03 2025 -0400
Use git rev-parse to retrieve commit id
When using debcraft within a git repository, it is possible that `git
log -n 1 --oneline` can output more than one line, such as when the
configuration value `log.showsignature` is set to show GPG signatures
in the git log. Because of this, the attempt to assign the `COMMIT_ID`
variable using the command `git -C "$PWD/.git" log -n 1 --oneline | cut
-d ' ' -f 1` results in `COMMIT_ID` being multiple lines. This causes
problems when it is used as part of the file name used for the image id
file when building the container.
Using the command `git rev-parse --short HEAD` produces the same commit
id as `git log -n 1 --oneline`, and will only contain a single line of
output. Also, it will only output the commit id itself, thus it does not
need to be piped to the `cut` command to get rid of the extra
unnecessary information.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/debcraft.png){kind=link}