| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| | |
apt Debian release 1.8.0~alpha3.1
|
| | |
|
|/
|
|
| |
Not needed since quite some time.
|
| |
|
|
|
|
|
|
|
|
|
| |
This avoids a lot of problems from local installations of
scripting languages and other stuff in /usr/local for which
maintainer scripts are not prepared.
[v3: Inherit PATH during tests, check overrides work]
[v2: Add testing]
|
|
|
|
|
|
|
| |
.UTF-8 sets stdio encoding to UTF-8 which may be ASCII on the system making
unattended-upgrades crash.
LP: #1806076
|
|
|
|
|
|
|
|
| |
No user visible change expect for some years old changelog entries,
so we don't really need to add a new one for this…
Reported-By: codespell
Gbp-Dch: Ignore
|
|
|
|
|
|
|
| |
The << 0.8.11 was stronger than necessary, and breaks Ubuntu,
which is unable to build aptitude 0.8.11 atm (the test suite
fails since 0.8.10 in C++17 mode, only works in C++14, but
0.8.11 uses C++17 constructs).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gcc 8 broke the ABI again. After they decided to switch mangling of ABI tags in return values from:
U URI::operator std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >[abi:cxx11]()
to:
U URI::operator std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >()
in gcc 7, they now removed the legacy symbol in gcc 8, causing us to break our ABI in turn
for that one operator. We need more responsible gcc developers.
Closes: #911090
|
|
|
|
|
|
|
| |
This gives more protection for people where kernel metapackages
are accidentally removed.
LP: #1787460
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
No user-visible change as it effects mostly code comments and
not a single error message, manpage or similar.
Reported-By: codespell & spellintian
Gbp-Dch: Ignore
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Installer packages need us to be online, or they are blocking
shutdowns in the worst case :(
LP: #1723761
|
|
|
|
| |
Closes: 892792
|
|
|
|
|
|
| |
The formatting is very basic and more should probably be done, but we at
least get the files out of the root directory which in case of the
various READMEs was confusing salsa which one display as (central) README.
|
|
|
|
|
| |
Reported-By: codespell & spellintian
Gbp-Dch: Ignore
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
pu/zstd
See merge request apt-team/apt!8
|
| |
| |
| |
| |
| |
| |
| | |
zstd is a compression algorithm developed by facebook. At level 19,
it is about 6% worse in size than xz -6, but decompression is multiple
times faster, saving about 40% install time, especially with eatmydata
on cloud instances.
|
| |
| |
| |
| |
| |
| | |
The override file already implements this, so we just adapt to reality.
Reported-By: lintian excessive-priority-for-library-package
|
| |
| |
| |
| | |
Whatever caused it, lets fix it.
|
| |
| |
| |
| |
| |
| | |
LP: #1732030
Closes: #890489
Fixes meefik/linuxdeploy#869
|
|/ |
|
| |
|
|
|
|
| |
LP: #1698159
|
|\
| |
| |
| |
| | |
Check that Date of Release file is not in the future
See merge request apt-team/apt!3
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
By restricting the Date field to be in the past, an attacker cannot
just create a repository from the future that would be accepted as
a valid update for a repository.
This check can be disabled by Acquire::Check-Date set to false. This
will also disable Check-Valid-Until and any future date related checking,
if any - the option means: "my computers date cannot be trusted."
Modify the tests to allow repositories to be up to 10 hours in the
future, so we can keep using hours there to simulate time changes.
|
|/
|
|
|
|
|
|
| |
This is an optional dependency for the test, but the skipping of the
test is very noisy and checking that an unchanged aptitude isn't
downright exploding with our libapt isn't a bad idea either.
Gbp-Dch: Ignore
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This has not been used for a while. It was added for apt-mark
in 7b4159cf2a4b7de10622c7e4e29247067358a3ab, but apt-mark has
been rewritten in C++ quite some time ago.
Closes: #887607
|
|
|
|
|
|
|
|
| |
If on_ac_power exits with 255 the script would fail at this point
because set -e was set, but it should continue, as 255 means the
power status could not be determined.
LP: #1742378
|
| |
|
|
|
|
|
| |
The mirror method is undocumented since 0.7.24, now with the
reimplementation it is high time to get something written about it.
|
|
|
|
|
|
| |
Same reasoning as with the previous commit for http with the added
benefit of moving the hard to discover and untranslated example config
into a manpage which could be translated.
|
|
|
|
|
|
| |
We had documentation for the http transport in our "catch-all" apt.conf
manpage, but it seems benefitial to document transports in their own
manpage instead of pushing them all into one.
|