| Age | Commit message (Collapse) | Author |
|---|
|
These status fields belong to the current item, move them there. This
prepares us for eventually having multiple current items.
|
|
Github-Fixes: #89
|
|
Queues for processes like rred are not created by hostname but we
spawn at most CPU*2 queues to place items in. The problem is that we
then proceeded to limit it to at most 10 queues (via QueueHost::Limit)
again at the end of the method so that all items (after the first 10
queues are busy) are forcibly placed into a generic catch-all instance
which is bad because we don't keep all CPUs we have available busy and
worse we end up sheduling the most work to a single one while random
distribution was intended.
|
|
warning: but ‘pkgTagFilePrivate::FileChunk::FileChunk(bool, size_t)’
does not throw; perhaps it should be declared ‘noexcept’ [-Wnoexcept]
Reported-By: gcc-9
Gbp-Dch: Ignore
|
|
warning: moving a local object in a return statement prevents copy
elision [-Wpessimizing-move]
Reported-By: gcc-9
Gbp-Dch: Ignore
|
|
Test from the fix for the regression in trusty for LP #1821308.
|
|
Closes: #926614
|
|
Prevent the translations to become fuzzy due to the simple
copy-editing done recently on the english "translation".
References: 30e6fad9ad892a21d271fa93319f7a3ee23da134
Gbp-Dch: Ignore
|
|
The value as shown in the NEWS file (not in the code) has a typo in
which just a "/" and ":" are swapped.
Closes: #917986
|
|
The package is an empty dummy by now, but even before it could have made
sense as described in the bugreport and due to external requirements it
might stick around a while still.
References: afe3cd6ef1b157a07d05bbf70283e4f175813438
Closes: #905141
|
|
Perform minor copy-editing on the docs
See merge request apt-team/apt!58
|
|
Add PkgConfig on the apt-pkg and apt-inst libraries
See merge request apt-team/apt!20
|
|
Tighten dependencies from apt and apt-utils on libs
See merge request apt-team/apt!56
|
|
|
|
Make apt pull in at least the same version of libapt-pkg,
and apt-utils at least the same version of libapt-inst,
so that upgrading only apt also upgrades the libraries.
|
|
Fix vendor/getinfo on Ubuntu derivatives
See merge request apt-team/apt!55
|
|
If your dpkg-vendor configuration in base-files is an Ubuntu derivative,
but not exactly Ubuntu, and not an exact match for anything in vendor/,
we want to use vendor/ubuntu.
Previously we used whatever $DISTRO happened to be at the end of the
"for" loop above, but that's undesirable: even if we assume that find(1)
returns results in alphabetical order (which is not guaranteed), we
wouldn't want to return a non-Ubuntu result if a future apt version
happens to have a vendor that sorts later than vendor/ubuntu, for
example vendor/zombieos or something.
Closes: #924662
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
find(1) works in readdir() order, which isn't guaranteed to be sorted.
If the current vendor is not an exact match for any subdirectory in
vendor/, and is somehow a derivative of more than one of them, we should
at least produce a deterministic answer.
Closes: #924662
Signed-off-by: Simon McVittie <smcv@collabora.com>
|
|
|
|
|
|
This command allows merging translations from another branch. This
is to be used strictly downwards, that is, translations should be
merged from newest to oldest branch, without skipping any active
branch, to ensure the best result.
For example, consider branches 1 and 2 have the strings "a" and "b"
to translate, but master only has the strings "a" and "c". Now, 2
has more translations for "b" than 1. By merging master into 2, and
2 into 1, 1 also gets any translations for "b" from 2.
|
|
Closes: #439121
|
|
apt Debian release 1.8.0
|
|
|
|
The missing auth.conf.d directory was an oversight, it should
be there.
LP: #1818996
|
|
Closes: #923834
|
|
Closes: #923728
|
|
Bad accident. Accidents happen.
|
|
[l10n] Update Italian translation
See merge request apt-team/apt!53
|
|
Add explicit message for unsupported binary signature
See merge request apt-team/apt!52
|
|
Signed-off-by: Milo Casagrande <milo@milo.name>
|
|
Verifying the content of Release.gpg made us fail on binary signatures
which were never officially supported (apt-secure manpage only documents
only the generation of ASCII armored), but silently accepted by gpgv as
we passed it on unchecked before.
The binary format is complex and is itself split into old and new
formats so adding support for this would not only add lots of code but
also a good opportunity for bugs and dubious benefit.
Reporting this issue explicitly should help repository creators figure
out the problem faster than the default NODATA message hinting at
captive portals.
Given that the binary format has no file magic or any other clear and
simple indication that this is a detached signature we guess based on
the first two bits only – and by that only supporting the "old" binary
format which seems to be the only one generated by gnupg in this case.
References: e2965b0b6bdd68ffcad0e06d11755412a7e16e50
Closes: #921685
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Please use the standard C++ variants instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This keeps the members in the class, but makes them private. We
want to migrate to libgcrypt eventually, since we already use
libgcrypt through gpgv anyway.
|
