| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This reverts commit 4f89d3629b22255963da3705e4222c71045da58a.
The bugscript uses yesno which is documented to require bash in
/usr/share/doc/reportbug/README.developers.gz.
Closes: #1007121
|
| |
|
|
|
|
|
|
|
| |
Without documentation these options will see much less use.
Fixes: commit 1d9e29c9e2a5591b42a99a721b901fc003ed9149
Suggested-by: kibi on #debian-devel
|
| |
|
|
|
|
|
| |
With apt-key going away, people need to manage key files, rather
than keys, so they need to know if any keys are in the legacy keyring.
|
|\
| |
| |
| |
| | |
bugscript: switch to POSIX shell, quoting, other improvements
See merge request apt-team/apt!225
|
| |
| |
| |
| |
| |
| | |
This means Debian is one step closer to removing bash from essential.
See-also: https://salsa.debian.org/debian/grow-your-ideas/-/issues/20#note_296809
|
| |
| |
| |
| |
| |
| | |
Otherwise slashes in filenames could be interpreted as newlines etc.
Also makes it portable to shells that don't support `echo -e`.
|
| |
| |
| |
| |
| |
| |
| | |
The file names could contain spaces and without quoting, the
files would not be found and included in the bug reports.
Suggested-by: shellcheck
|
| |
| |
| |
| |
| | |
Otherwise the options won't be applied when running the script
directly from a sh command instead of via the shebang.
|
| |
| |
| |
| |
| |
| | |
See-also: https://bugs.debian.org/169495
Fixed-in: reportbug 2.10
Fixed-on: 2002-12-23
|
|/
|
|
|
|
|
| |
This directory is intended to provide an alternative to
/usr/share/keyrings for placing keys used with signed-by.
Gbp-Dch: full
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
`which` has been deprecated in debianutils 5.0+. The recommended
replacement, `command -v`, is mandated by Debian policy these days, in
addition to being required by POSIX and its predecessor specs at least
since 1994.
Not found commands cause no output from `command -v` per POSIX, so
remove the redundant 2>&1's while at it.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If the system tells us that a core dump was created we should try to
display the contained info as that system might not be easily available
when we see the error (like C-I or autopkgtest).
Gbp-Dch: Ignore
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We use a Breaks for the binary package instead of adding
a versioned depends, as Breaks will cause apt solver to upgrade dpkg,
while depends would make apt try to remove apt as first choice.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This reverts commit d96c9a0280bffcfb0f4a319e003e9af60c6cfaf1.
It is not correct for master.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for Phased-Update-Percentage by pinning
upgrades that are not to be installed down to 1.
The output of policy has been changed to add the level of
phasing, and documentation has been improved to document
how phased updates work.
The patch detects if it is running in a chroot, and if so, always
includes phased updates, restoring classic apt behavior to avoid
behavioral changes on buildd chroots.
Various options are added to control this all:
* APT::Get::{Always,Never}-Include-Phased-Updates and their legacy
update-manager equivalents to always or never include phased updates
* APT::Machine-ID can be set to a UUID string to have all machines in a
fleet phase the same
* Dir::Etc::Machine-ID is weird in that it's default is sort of like
../machine-id, but not really, as ../machine-id would look up
$PWD/../machine-id and not relative to Dir::Etc; but it allows you to
override the path to machine-id (as opposed to the value)
* Dir::Bin::ischroot is the path to the ischroot(1) binary which is used
to detect whether we are running in a chroot.
|
|
|
|
|
| |
Kernels clutter /boot and /boot is small size, so we need to take
extra care to remove kernels when possible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our kernel autoremoval helper script protects the currently booted
kernel, but it only runs whenever we install or remove a kernel,
causing it to protect the kernel that was booted at that point in time,
which is not necessarily the same kernel as the one that is running
right now.
Reimplement the logic in C++ such that we can calculate it at run-time:
Provide a function to produce a regular expression that matches all
kernels that need protecting, and by changing the default root set
function in the DepCache to make use of that expression.
Note that the code groups the kernels by versions as before, and then
marks all kernel packages with the same version.
This optimized version inserts a virtual package $kernel into the cache
when building it to avoid having to iterate over all packages in the
cache to find the installed ones, significantly improving performance at
a minor cost when building the cache.
LP: #1615381
|
| |
|
| |
|