| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
UI changes for 2.9.2
See merge request apt-team/apt!343
|
| | |
| |
| |
| |
| |
| | |
This avoids awkward interactions with Installing dependencies and
Suggested packages appearing before it; despite being triggered by
it.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Add a new `note` field to `ShowList` which contains a line to
be displayed after the list itself. This allows `ShowList` to
render a self-contained list block.
|
| | |
| |
| |
| | |
We should pass this properly to the TagSection.write()
|
| | | |
|
| | |
| |
| |
| |
| | |
This allows these bits to be localized, improving user experience
for users in different languages.
|
| | |
| |
| |
| |
| | |
This draws a bit more attention, and improves readability vs
keeping the color for the entire message.
|
| | |
| |
| |
| | |
Yellow is a bit odd for notices.
|
| | |
| |
| |
| |
| | |
GTest has a lot of broken things with signed vs unsigned,
and double integer promotions, let's silence them.
|
| | |
| |
| |
| |
| |
| | |
This avoids us polluting the configuration for later tests, since
the test order apparently is not deterministic. We probably should
fix some common test case thingy instead.
|
| |\ \
| |/
|/|
| |
| | |
Add an "audit" error level
See merge request apt-team/apt!323
|
| | | |
|
| | |
| |
| |
| |
| | |
This option is recommended to be used by repository operators
for testing.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |/
|
|
|
| |
This will aggressively highlight out-of-compliance vs the best
practices.
|
| |\
| |
| |
| |
| | |
Introduce APT::Configuration::Color, --color option and documentation for color.
See merge request apt-team/apt!342
|
| | | |
|
| | |
| |
| |
| | |
This is somewhat pointless.
|
| | |
| |
| |
| | |
Wrap empty else in {} to avoid readability issues
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Closes: #1069118
|
| |
|
|
|
|
|
| |
Note by committer: Merged with latest pot and resolving 3 white space
fuzzies introduced by it
Closes: #1068943
|
| |
|
|
|
| |
While this is an interactive only change that doesn't break
parsing someone got unhappy.
|
| |
|
|
|
| |
This is easier to discover than APT::Color options and matches
best practices.
|
| | |
|
| |\
| |
| |
| |
| | |
UI improvements for 2.9.1
See merge request apt-team/apt!338
|
| | |
| |
| |
| |
| | |
This produces a much more appealing progress bar and it can even
show parts of the progress being done.
|
| | |
| |
| |
| |
| | |
This especially helps with the running out of space warnings to
be safe.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
dnf shows downgrades as green because the package comes from a remote
repository, but I think yellow is more indicative that they are
unsupported.
Ganneff asked for yellow for kept packages too, however I'm not
adding yellow there, as kept packages are more indicative of an
archive error, likely temporary, rather than an action item for
the user.
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This aligns the /boot message with the parent one, and also align
the formatting of the partially downloaded size message to add spaces
around /
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Calculate an estimate of 110% of the biggest initrd + system.map
as the additional space a kernel needs in /boot.
If /boot is a different file system than /usr, print the size of
the kernels + the additional space they will need separately;
otherwise include it in our /usr figure.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Also allow us to have utf-8 characters in xgettext, but msgcomm still
fails so ugh.
This avoids translations messing up the formatting a bit more, at
least, and makes apt build again
|
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Remove duplicate sentence in private-output.cc
See merge request apt-team/apt!339
|
| |/ |
|
| | |
|
| |\
| |
| |
| |
| | |
Introduce new output format for apt(8)
See merge request apt-team/apt!337
|
| | |
| |
| |
| |
| |
| | |
Instead of using Upgrades, Installs, and so on, just use
Upgrading, Installing, etc. This solves the problem of
not having a nice noun for "Not upgrading".
|
| | |
| |
| |
| |
| |
| | |
This makes things more useful in combination with the upgrade
command, but introduces a subtle change seen in the test suite
when you use the install command to upgrade packages.
|
| | |
| |
| |
| |
| |
| | |
Extract the code to show them into its own function and call
it in the old place for output version < 30, or after the
dependencies being installed for new output format.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The key talking points here are:
1. Instead of long sentences, we use short concise messages,
e.g. "The following NEW packages will be installed" becomes
"Installing".
2. Dependencies are only listed once. We removed the
"The following additional packages will be installed" section
in favor of splitting up the "Installing" section into
"Installing" and "Installing dependencies" (like dnf)
3. The order of the output is different:
1. Packages to be installed manually
2. Packages to be installed automatically
4. Weak dependencies of new packages not installed
3. Packages to be upgraded
4. Packages to be downgraded
5. Packages that have been kept back / are on hold
6. Removals
7. Essential removals
i.e. we logically show you the action that is being
done, followed by lists related to the action.
4. As requested by popey, we have colorful UI, with green for
packages being installed and red for packages being removed.
Caveats:
- The list of recommends and suggests has not been updated yet,
it should move to after the packages being installed (as they
are what triggers them)
This also introduces output format versioning, configured by the
APT::Output-Format option. The default value is 0, except for the
apt(8) binary where it is 30 - which enables the new style.
|