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 783735d14817ef4dfa1a76cbf499383ba6ab336e
Author: Otto Kekäläinen <otto@debian.org>
Date: Sun Nov 17 17:11:19 2024 -0800
Add support for building on Debian Stretch
Debian 9.0 was initially released on June 17th, 2017.
Security updates have been discontinued as of July 6th, 2020.
It is however still supported by the Debian (E)LTS initiative, so include
support for it in Debcraft.
See https://wiki.debian.org/LTS and https://wiki.debian.org/LTS/Extended,
where the latter states that Stretch updates will be provided until 2027.
commit c054e695a0ec08bc1cb2fba7eea5ec3b91b1c206
Author: Otto Kekäläinen <otto@debian.org>
Date: Sun Nov 17 13:13:35 2024 -0800
Refactor Containerfile to be available for even older Debian releases
Similar to 00d6747d, now also make diffoscope-minimal an optional
dependency that is installed only if available in the target distro
release.
commit c74141bbfd5e292ccc9646948b76377e67c1691e
Author: Otto Kekäläinen <otto@debian.org>
Date: Tue Nov 12 11:33:40 2024 -0800
Sort blhc.log to make comparisons between build practical
commit ec28b8f21fdf36c39efb101b34c2d1325b77258f
Author: Otto Kekäläinen <otto@debian.org>
Date: Sat Nov 9 19:20:39 2024 -0800
Export pristine-tar based on upstream version, not newness
Instead of listing all available signature files and selecting the newest,
select the one that matches the expected upstream version. This fixes the
bug where release directories ended up having two tarballs (newest by
Debcraft, and the correct one by git-buildpackage).
commit 1e8369f0f1cda2e9d7a855f32615e0560efac21c
Author: Otto Kekäläinen <otto@debian.org>
Date: Sat Nov 2 09:05:58 2024 -0700
Add 'plucky' as the new default Ubuntu development release
commit cdb5f82902600fa06aee0881f76b13679f08d02b
Author: Otto Kekäläinen <otto@debian.org>
Date: Sat Sep 14 15:16:36 2024 -0700
Always run `apt-get update` before installing packages in containers
If the apt-cache is not recent, the `apt-get install` commands will fail
on 404 errors. Updating the cache does not take long if a previous layer
already pulled it, so best to always run it just to be sure.
Also indent RUN commands neatly with the apt-get parameters indented one
more level to show are part of the same command.