apt/apt-pkg/contrib, branch 2.9.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.22024-04-22T17:39:08ZAdd long-version message "Audit:" instead of "A:"2024-04-22T17:39:08ZJulian Andres Klodejulian.klode@canonical.com2024-04-22T17:39:08Zurn:sha1:cbb6f72b868cf7f50bd148479f7604f21964d239Merge branch 'ui-2.9.2' into 'main'2024-04-22T17:31:46ZJulian Andres Klodejak@debian.org2024-04-22T17:31:46Zurn:sha1:20ab001670226e92ca8a74f1e2308197111a8420
UI changes for 2.9.2
See merge request apt-team/apt!343i18n: Use Error:/Warning:/Notice: instead of E:/W:/N:2024-04-19T18:49:05ZJulian Andres Klodejulian.klode@canonical.com2024-04-15T14:51:32Zurn:sha1:dc3f3ec100f275e5a802e59fd160f75cd262845f
This allows these bits to be localized, improving user experience
for users in different languages.
Keep the entire error/warning/notice message bold2024-04-19T18:48:34ZJulian Andres Klodejulian.klode@canonical.com2024-04-15T14:49:43Zurn:sha1:4d54b35e7a0c073b293d26d075714bef17080d48
This draws a bit more attention, and improves readability vs
keeping the color for the entire message.
Add an "audit" error level2024-04-19T18:08:44ZJulian Andres Klodejulian.klode@canonical.com2024-01-23T17:32:32Zurn:sha1:b455ad0a6681be80134d31ca59c350332ab4fb73
This will aggressively highlight out-of-compliance vs the best
practices.
Render notices without (yellow) color, just in bold2024-04-19T17:21:36ZJulian Andres Klodejulian.klode@canonical.com2024-04-15T14:48:16Zurn:sha1:760d7d3aa5ac414f05e381e0984430544b1f42d9
Yellow is a bit odd for notices.
Only erase OpProgress lines in output version 3.02024-04-15T16:49:01ZJulian Andres Klodejulian.klode@canonical.com2024-04-15T16:48:14Zurn:sha1:fc35b4d7d95b2848db482021df4f4500ac142080
While this is an interactive only change that doesn't break
parsing someone got unhappy.
OpProgress: Erase lines when done2024-04-12T13:57:05ZJulian Andres Klodejulian.klode@canonical.com2024-04-12T10:00:45Zurn:sha1:8ddfeb2fb65dd45267d8f7abfc540d2b8cb73a5c
It's interesting to the user to see the progress when it happens,
but arguably once it's done it is just visual clutter, so let's
not write newlines, and when we are done, instead of appending
"Done", let's just empty the line.
This requires some effort to keep apt-cdrom happy which just writes
lines to stdout itself. Bad apt-cdrom. Maybe there is a better fix
for it, but this gets us going.
Handle EINTR in the static FileFd::Write overload2024-03-05T11:57:03ZDavid Kalnischkiesdavid@kalnischkies.de2024-03-04T14:50:44Zurn:sha1:1437dcbe489ee9bcd39000cfef30324ad0260b41
While the code claims to handle it by just continuing the loop, the
looping condition will actually cause a break from the loop failing the
interrupted writing. The non-static FileFd::Write (and ::Read) deal with
this by setting acceptable values for the loop condition as well – but
for more simplicity and consistency we can instead remove this extra loop
condition and perform the continue/break due to error handling more
explicitly.
Modernize standard library includes2024-02-20T12:49:04ZJulian Andres Klodejulian.klode@canonical.com2024-02-20T12:43:08Zurn:sha1:40a75722c43ae24cb9a99d6730a3b25b65819c49
This was automated with sed and git-clang-format, and then I had to
fix up the top of policy.cc by hand as git-clang-format accidentally
indented it by two spaces.