| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | |
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
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.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We temporarily downgraded the errors to warnings to give the
launchpad PPAs time to be fixed, but warnings are not safe:
Untrusted keys could be hiding on your system, but just not
used at the moment. Hence revert this so we get the errors we
want.
This reverts commit 66998ed3d299bede651ad40368bdb270f5f5b0f9.
LP: #2060721
Gbp-Dch: full
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We don't store .diff_Index files anymore and so libapt cares even less
about these purposefully leftover files from the testcases than it did
previously. On a successful apt run they would just be deleted, but as
we are testing a failed run they are not touched at all.
Testing the file access bits then means we check with whatever umask
they were created which might very well be different to what apt decides
these files to have if it had touched them, so for this test we just
delete them. For the other case we set it completely wrong just in case,
but they will (hopefully) be non-existent anyhow as tested first.
References: afcdbcf895284efd76903b2b3ba5cc849059ce50
|
| |
|
|
|
|
| |
We remove the working directory from the found file names as these paths
could contain a lot of funny characters confusing the for loop like
spaces… we just readd it later in the actual calls to be safe.
|
| | |
|
| |
|
|
|
|
| |
to force upgrades in launchpad buildd chroots
Gbp-Dch: full
|
| |
|
|
| |
This reverts commit 9bb953fddae0246a4dcedddb769d75d3521e1f2f.
|
| |
|
|
|
|
|
| |
The TagFile parser will have already parsed further and can't go
back so it needs to reopen the file if compressed.
Closes: #1067440
|
| |\
| |
| |
| |
| | |
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>
|
| |\ \
| | |
| | |
| | |
| | | |
Update URI in documentation
See merge request apt-team/apt!335
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| | |/
| |
| |
| | |
Signed-off-by: Wesley Schwengle <wesleys@opperschaap.net>
|
| |\ \
| |/
|/|
| |
| | |
pkgTagFile::Jump: Use lookback buffer to rejump to current position
See merge request apt-team/apt!336
|
| |/
|
|
|
|
|
|
|
| |
If we get called twice with the same offset, our d->Start and d->iOffset
will already point at the offset for the next section. But since we have
the start of the last parsed section still in the buffer, just make sure
to always go back to the start first.
Closes: #1067440
|
| |
|
|
| |
Closes: #1065517
|
| |
|
|
| |
Closes: #1065513
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libapt has a NotEquals relation for version constraints in
dependencies, which is used internally e.g. in the MultiArch
implementation, but this relation is not supported by Debian
policy and as such can not be used in packages.
Our parser here is extremely accepting, even unknown relations are
parsed as Equals relation – but the version that must match will be a
rather strange one…
For our own testcases and e.g. on the command line with 'satisfy' it
can make sense to have != available… and what strange things apt does
parsing unsupported relations is not really much of a concern. Real
packages will not have such relations anyhow as we are (mostly) just
a consumer, not a producer of packages and index files.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |\
| |
| |
| |
| | |
Support building without gnutls
See merge request apt-team/apt!333
|
| |/
|
|
|
|
|
|
|
| |
Once in a generation, it may be necessary to bootstrap apt in an
environment where gnutls is not yet available. This makes gnutls
support in apt optional.
You may also want a configure flag to force gnutls to be required from
outside the buildsystem (e.g. debian/rules).
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Assert >=2048-bit RSA keys, Ed25519, Ed448, and some improvements to diagnostic reporting
See merge request apt-team/apt!322
|
| | |
| |
| |
| |
| | |
This will only issue warnings instead of errors while we continue
cleaning up our repositories.
|
| | |
| |
| |
| | |
This allows us to render public key algorithms as weak as well.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Do not require versioned dpkg-dev on CI
See merge request apt-team/apt!332
|
| |/ /
| |
| |
| |
| | |
Annotate the Build-Depends with a <!pkg.apt.ci> profile and use
that in prepare-release when doing build-dep.
|
| |\ \
| | |
| | |
| | | |
Import 2.7.12+nmu1
|
| | |/
| |
| |
| |
| |
| |
| | |
apt (2.7.12+nmu1) unstable; urgency=medium
.
* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition. Closes: #1061896
|