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 235d4ab12e72aeef4bbfc59de1d6d51cacdb2e66
Merge: 7010333 858a551
Author: Julian Andres Klode <jak@debian.org>
Date: Fri Apr 19 19:30:26 2024 +0000
Merge branch 'audit' into 'main'
Add an "audit" error level
See merge request apt-team/apt!323
commit 858a551b50ea3871748d9196896e54b361c3d545
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Tue Jan 23 19:01:34 2024 +0100
Add an audit message for missing InRelease files
commit 215b184d6a5774df10cabe12bde7d6b0fa3aff85
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Tue Jan 23 18:43:13 2024 +0100
Add an --audit option to switch on audit logging
This option is recommended to be used by repository operators
for testing.
commit 3cd6eacd1ab42e414f0d899a3f74fc60140f0e8a
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Tue Jan 23 18:37:42 2024 +0100
Change the default log level from debug to notice
We never used the debug level before, so we can do that. This
allows us to have the new audit level.
We did call DumpErrors() with DEBUG in two debug code paths,
so don't touch those.
debug
commit b455ad0a6681be80134d31ca59c350332ab4fb73
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Tue Jan 23 18:32:32 2024 +0100
Add an "audit" error level
This will aggressively highlight out-of-compliance vs the best
practices.
commit 70103339b017a42ea71a56c27c221a79ccc3116f
Merge: 633f6d6 28ec287
Author: Julian Andres Klode <jak@debian.org>
Date: Fri Apr 19 17:20:31 2024 +0000
Merge branch 'color-framework' into 'main'
Introduce APT::Configuration::Color, --color option and documentation for color.
See merge request apt-team/apt!342
commit 28ec28746d8633b9c4b67cd6d1b603a1da57f436
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 16:48:19 2024 +0200
apt.conf(5): Document the APT::Color scope
commit 58436fc3b7507d5c0f6fcf1a4a072c71961c42f2
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 16:20:43 2024 +0200
private-output: Remove check for output version for color
This is somewhat pointless.
commit be5289525a2a037881eaac48fbab26f864f72cd5
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 16:18:57 2024 +0200
Add a --color, --no-color option
Wrap empty else in {} to avoid readability issues
commit dc779ff0a33d9da8bc55390ee55ad73d31739e46
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 16:12:42 2024 +0200
Configure individual action colors using APT::Color::Action
commit e07450beb5a474ec3c099ff3eb329892b040d04c
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 16:05:08 2024 +0200
Use APT::Configuration::color to apply color to output
commit 58ee0fabc9028fcdf86faab3bb9c1db2b27e3644
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Fri Apr 19 15:57:23 2024 +0200
Add APT::Configuration::color helper to colorize things
commit 633f6d67a28b375cf1f225f14d3c926e618d46af
Author: David Kalnischkies <david@kalnischkies.de>
Date: Wed Apr 17 08:19:40 2024 +0000
Allow no spaces for the last dependency in ParseDepends, too
All other entries in a dependency line get substantial leeway about the
amount of spaces surrounding the entry itself and its individual parts,
but the very last entry was required to have a version constraint be
at least 4 chars long (excluding opening bracket and spaces following
it), so if the version is short and a single-char relation used a space
had to make up for it. This is a bit unfair in comparison to the other
entries who do not have such unreasonable demands, so we reduce our
demand to 3 chars or longer, which is satisfied by "=1)".
If it is a good idea to hate spaces that much remains unanswered by this
commit, but in practice most tools (re)writing the files we parse will
include spaces, so its only in files (or on the satisfy command line)
directly edited by users that we can encounter such a situation, which
is a relatively new development given this line came unchanged from
the introduction of this method in 1998.
LP: #2061834
commit e68a7ee54a5aba11d0fde3384cc90a20b1d184a0
Author: Boyuan Yang <byang@debian.org>
Date: Wed Apr 17 08:32:17 2024 +0000
Simplified Chinese program translation update
Closes: #1069118
commit 8cff6f076ea99f40f873f4150dd048b0e6f6cd9a
Author: Miroslav Kure <kurem@upcase.inf.upol.cz>
Date: Wed Apr 17 08:31:13 2024 +0000
Czech program translation update
Note by committer: Merged with latest pot and resolving 3 white space
fuzzies introduced by it
Closes: #1068943
commit fc35b4d7d95b2848db482021df4f4500ac142080
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Mon Apr 15 18:48:14 2024 +0200
Only erase OpProgress lines in output version 3.0
While this is an interactive only change that doesn't break
parsing someone got unhappy.
commit e52898659db4e34e7f50963f8331e83dedb9fc1b
Author: Julian Andres Klode <julian.klode@canonical.com>
Date: Mon Apr 15 13:40:49 2024 +0200
Also respect an APT_NO_COLOR variable
This is easier to discover than APT::Color options and matches
best practices.