| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change makes it a bit easier to quickly grasp the changes
about to be performed by apt.
It displays package lists in a columnar format by default,
similar to what `ls` produces for files.
A new long option `--no-list-columns` and an associated
`APT::Get::List-Columns` config setting control the behavior.
Usage example, with 60 column wide terminal:
```
$ sudo apt upgrade |
Reading package lists... Done |
Building dependency tree... Done |
Reading state information... Done |
Calculating upgrade... Done |
The following packages were automatically installed and are |
no longer required: |
libappindicator1 libindicator7 |
libdbusmenu-gtk4 linux-image-5.14.0-4-amd64 |
Use 'sudo apt autoremove' to remove them. |
The following packages have been kept back: |
criu linux-headers-amd64 nvidia-settings |
libxnvctrl0 nvidia-modprobe xwayland |
0 upgraded, 0 newly installed, 0 to remove and 6 not upgrade|
d. |
```
The effect becomes more pronounced with more packages (e.g. when
doing a dist-upgrade).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The Graphviz change adapted only the msgstrs in the po files, which
fuzzied all translations the moment the msgids were updated by the
merge while forgetting fr.po and pl.po and in the VCG change the
msgstr in the ja.po was missed.
This commit "just" unfuzzies the strings (and fixes the missed ones)
so the translators don't have to as intended in the commits.
References: ae5c291b0c76b22c939679ccf35e3eb94131e586
edf1025e691e94cdde305bc2d15484fc7ee6db1c
|
| | |
|
| |\
| |
| |
| |
| | |
Update documentation for apt-get upgrade with pkg arg
See merge request apt-team/apt!334
|
| | |
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |
| |
| |
| |
| |
| | |
Closes: #1065831
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |
| |
| |
| |
| |
| | |
Closes: #1065831
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |/
|
|
| |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |
|
|
| |
Closes: #1065517
|
| |
|
|
|
|
|
|
|
| |
The option was removed in 2016 along with the code surrounding it, as
the special build-deps specific solver was replaced with reusing our
generic solver(s). As such, the normal debug options for these apply
here nowadays instead of requiring another one to be set as well.
References: a249b3e6fd798935a02b769149c9791a6fa6ef16
|
| | |
|
| |\
| |
| |
| |
| | |
Assert >=2048-bit RSA keys, Ed25519, Ed448, and some improvements to diagnostic reporting
See merge request apt-team/apt!322
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The assertion can be overriden using apt::key::assert-pubkey-algo,
the default is the most opinionated one.
This will inform the user during apt-cdrom add as we do not
pass --quiet to user, so adjust test case.
Add a simple test case for it to test-method-gpgv.
LP: #2055193
|
| |/
|
|
|
|
|
|
| |
The man page uses examples/configure-index.gz for the configure-index
file, but this isn't a .gz file. Remove the .gz so users can find the
correct file.
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |
|
|
|
| |
I also unfuzzied the translation strings for the 23.10->24.04
apt-key deprecation change.
|
| |
|
|
|
| |
While it was initially on the road map for 24.04 it got replaced
with the disable 1024R keys feature.
|
| |\
| |
| |
| |
| | |
apt.8: summarise remaining verbs (Closes: #827785)
See merge request apt-team/apt!315
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following were undocumented
// package stuff
{"auto-remove", &DoInstall, nullptr},
{"autopurge",&DoInstall, nullptr},
// system wide stuff
// misc
{"moo", &DoMoo, nullptr},
// for compat with muscle memory
{"dist-upgrade", &DoDistUpgrade, nullptr},
{"showsrc",&ShowSrcPackage, nullptr},
{"depends",&Depends, nullptr},
{"rdepends",&RDepends, nullptr},
{"policy",&Policy, nullptr},
{"build-dep", &DoBuildDep,nullptr},
{"clean", &DoClean, nullptr},
{"distclean", &DoDistClean, nullptr},
{"dist-clean", &DoDistClean, nullptr},
{"autoclean", &DoAutoClean, nullptr},
{"auto-clean", &DoAutoClean, nullptr},
{"source", &DoSource, nullptr},
{"download", &DoDownload, nullptr},
{"changelog", &DoChangelog, nullptr},
{"info", &ShowPackage, nullptr},
And there's good reason for some of it, but I unironically didn't know
where apt changelog lived. It's unsearchable.
So the following are now simple links with no paragraphs:
// query
// package stuff
// system wide stuff
// misc
// for compat with muscle memory
{"showsrc",&ShowSrcPackage, nullptr},
{"depends",&Depends, nullptr},
{"rdepends",&RDepends, nullptr},
{"policy",&Policy, nullptr},
{"build-dep", &DoBuildDep,nullptr},
{"clean", &DoClean, nullptr},
{"distclean", &DoDistClean, nullptr},
{"autoclean", &DoAutoClean, nullptr},
{"source", &DoSource, nullptr},
{"download", &DoDownload, nullptr},
{"changelog", &DoChangelog, nullptr},
|
| |\ \
| | |
| | |
| | |
| | | |
Document 'dist-clean'
See merge request apt-team/apt!317
|
| | | |
| | |
| | |
| | | |
cf. https://salsa.debian.org/apt-team/apt/-/merge_requests/312#note_453588
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Configure the amount of kernels to keep
See merge request apt-team/apt!324
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit adds documentation for: APT::Protect-Kernels,
APT::NeverAutoRemove::*, APT::VersionedKernelPackages.
This is to inform users about the newly introduced
NeverAutoRemove::KernelCount feature.
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This commit introduces the following configuration for keeping a
configurable amount of kernels: APT::NeverAutoRemove::KernelCount
The logic dictates that the running kernel and the latest kernel are not
autoremoved. In case the running kernel is the latest kernel, the
previous kernel is kept. Any count lower than two is therefore
disregarded. This is in line with the previous behavior.
The default is therefore similar to:
APT::NeverAutoRemove::KernelCount 2;
This will be ignored and we will still keep two:
APT::NeverAutoRemove::KernelCount 1;
This will keep 3 kernels (including the runnig, and most recent)
APT::NeverAutoRemove::KernelCount 3;
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | | | | |
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | | |
This selects all packages that are being kept back due to phasing
on your system.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The -a flag exists for apt-cache (--all-versions) and -a=arch is
actually an (also documented) option to set host architecture – as the
apt-get manpage documents further below setting a host arch makes sense
only for those commands that actually need one set like source and
build-dep, so other commands keep refusing the option as unsupported as
they should be.
So this commit does indeed just remove a single character from
documentation with no other practical effect.
See: #1061148
|
| | | | |
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| | |
This reverts commit 86e6eace1d50527b5a2396290acd1db819b13e26, reversing
changes made to 6e43eef9ca8250eb561f2c9af2f4890d674f3911.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Usually this method will return the package in the most preferred
architecture (e.g. native) as that is usually what the user talks about
and also information wise for our internal usage the most dense.
Early on in parsing Packages files through it can happen that we
encounter stanzas about packages in architectures we are not even
configured to know about – we have to collect them anyhow as we might be
requested to show info about them or they could be in the status file
and we can't ignore stanzas in the status file… trouble is that this
method used to not return anything if only such an architecture was
present if we later discover other architectures which causes Provides
and Conflicts which are added lazily on discovery of an architecture
to not be added correctly.
The result is like in the testcase that apt could be instructed to
install a package without respecting its negative dependencies, which is
bad even if its discovered by dpkg and refused. It does only happen with
unknown architectures through which mostly happens if you are unlucky
(amd64 users tend to be very lucky as that sorts early) and use
flat-style repositories containing multiple architectures.
Reported-By: Tianyu Chen (billchenchina) on IRC
|
| | |
|
| |\
| |
| |
| |
| | |
Update fr.po (add a missing dot)
See merge request apt-team/apt!306
|
| | | |
|
| | |
| |
| |
| | |
Thanks: jwilk for suggestion
|
| | |
| |
| |
| | |
Translation template reordering carnage :D
|
| | |
| |
| |
| | |
Closes: #1051731
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
Closes: #1051723
|
