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 5c046cf4f6d83cd6159cce5ef94739e7a1bd3b6f
Author: David Kalnischkies <david@kalnischkies.de>
Date: Mon Aug 8 09:38:40 2022 +0200
Don't reuse filename for in-tree builds of apt
A temporary filename is used as a workaround for bugs/missing features
in other software dealing with /dev/stdin, but nobody said I have to use
the exact same filename….
However in-tree builds are not generally recommended.
References:
https://salsa.debian.org/debian/sbuild/-/commit/aa4a4326d09969e809f336e1b75cbd7342a77529
https://salsa.debian.org/ci-team/autopkgtest/-/commit/fb0561efc41a117963fa3e31802db6b2664c7aa5
Regression-Of: 701a501fb1c84296d2003c0092e4308742079591
Reported-By: Lance Fredrickson <lancethepants@gmail.com>
commit dc25210d889ebbcdfe96bd814a355961e80bccb3
Author: David Kalnischkies <david@kalnischkies.de>
Date: Thu Jun 9 09:38:04 2022 +0200
Keep color disabled if APT::Color was set to false
Support for envvar NO_COLOR was added in 2.3.11, but with our own
options we can also be a tiny bit more sensible in not overriding
an explicit choice to disable colors.
References: 400a6895566b67d70bcde43dc8a1cc1c7121f87d
commit 7d10b39f7ad95f6ca3731fb58b1644018e8dea6b
Merge: 2d87af57e 5e4d241e2
Author: Julian Andres Klode <jak@debian.org>
Date: Sun Aug 7 12:45:17 2022 +0000
Merge branch 'doc-explain-apt-download-authenticity' into 'main'
doc: Explain that apt-get download ensures package authenticity
See merge request apt-team/apt!251
commit 5e4d241e273e32cfc72c80526e8951a767efaaeb
Author: Povilas Kanapickas <povilas@radix.lt>
Date: Sat Aug 6 15:43:46 2022 +0300
doc: Explain that apt-get download ensures package authenticity
The documentation currently does not specify whether `apt-get download`
verifies the authenticity of downloaded packages or not. The underlying
code does verify the authenticity of packages as usual and would fail if
the package signature is invalid. Therefore it makes sense to make this
guarantee explicit in the documentation, because without it
security-conscious users will likely want to recheck the signatures or
checksums manually which is not necessary in this case and just wastes
time.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/a/apt.png){kind=link}