| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Closes: #1007128
|
|
|
|
|
|
|
|
|
| |
This reverts commit 4f89d3629b22255963da3705e4222c71045da58a.
The bugscript uses yesno which is documented to require bash in
/usr/share/doc/reportbug/README.developers.gz.
Closes: #1007121
|
|
|
|
| |
Closes: #1005781
|
| |
|
|\
| |
| |
| |
| | |
gpgv: Fix legacy fallback on unavailable keys
See merge request apt-team/apt!228
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change the logic to use "Valid" instead of "Good" to determine
whether we need to fallback and if fallback was successful. That
means that if you have an expired key in trusted.gpg.d, and a
non-expired in trusted.gpg, verification will now fail directly
with the expired key in trusted.gpg.d and not try to fallback.
Likewise, if the key in trusted.gpg is expired, this will now
also be reported correctly again, instead of producing an error
message that the key could not be found.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If a repository is signed with multiple keys, apt 2.4.0 would
ignore the fallback result if some keys were still missing,
causing signature verification to fail.
Rework the logic such that when checking if fallback was "succesful",
missing keys are ignored - it only matters if we managed to verify
one key now, whether good or bad.
Likewise, simplify the logic when to do the fallback:
If there was a bad signature in trusted.gpg.d, do NOT fallback at all
- this is a minor security issue, as a key in trusted.gpg.d could
fail silently with a bad signature, and then a key in trusted.gpg
might allow the signature to succeed (as trusted.gpg.d key is then
missing).
Only fallback if we are missing a good signature, and there are
keys we have not yet checked.
|
|\ \
| |/
|/|
| |
| | |
Document the APT::Periodic interval suffixes and "always" value
See merge request apt-team/apt!227
|
|/
|
|
|
|
|
| |
Without documentation these options will see much less use.
Fixes: commit 1d9e29c9e2a5591b42a99a721b901fc003ed9149
Suggested-by: kibi on #debian-devel
|
| |
|
|\
| |
| |
| |
| | |
Warn if the legacy trusted.gpg keyring is used for verification
See merge request apt-team/apt!209
|
| |
| |
| |
| |
| | |
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.
|
|/ |
|
|\
| |
| |
| |
| | |
Readme: Default branch is now main
See merge request apt-team/apt!226
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
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
|
|\ \
| | |
| | |
| | |
| | | |
Don’t bash-complete package names before the command word
See merge request apt-team/apt!221
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, package names would get suggested at the cursor position `_`
for a command line like this:
```
~# apt _ install git vim
```
|
| | |
| | |
| | |
| | |
| | |
| | | |
$words[0] contains the first word on the command-line, the name of the
program: apt. Also, the last word already typed on the command-line
might be the command, don’t ignore it.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Add bash-completion for autopurge and reinstall (closes: #930295)
See merge request apt-team/apt!214
|
| | | |
| | | |
| | | |
| | | | |
Closes: #930295
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
8ebb95805 missed some places to really bash-complete the autopurge command.
Partially closes #930295
|
| | | |
| | | |
| | | |
| | | | |
[jak@ Also document /etc/apt/keyrings]
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | | |
This directory is intended to provide an alternative to
/usr/share/keyrings for placing keys used with signed-by.
Gbp-Dch: full
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Allow --solver apt to work on apt satisfy
See merge request apt-team/apt!224
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Our EDSP code is confused by the spaces in the package name, so we adopt
a naming scheme similar to build-dep here instead of trying to teach
EDSP to somehow encode the spaces as that is probably even more
confusing for onlookers than this invalid package name is.
Reported-By: Johannes Schauer Marin Rodrigues on IRC
|
| | |
| | |
| | |
| | | |
Closes: #1004931
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The -q flag isn't quiet – it means quick – so ar happily prints an
"ar: creating test.deb" which is harmless, but also pointless and it
is the only testcase who produces output.
Gbp-Dch: Ignore
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Pinning and its display was reworked years ago, but the test and
especially the comment never got the memo.
References: a91aae406112df1d8fe16d00212333a20210f674
Gbp-Dch: Ignore
|
| | |
| | |
| | |
| | |
| | |
| | | |
I have no idea what I was thinking 12 years ago.
Gbp-Dch: Ignore
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
GNU parallel diverts moreutils implementation away. As we us moreutils
features just installing parallel breaks the test runner hence. We have
this already for another naming scheme, so fixing this is easy enough.
Gbp-Dch: Ignore
|
|/ |
|
|\
| |
| |
| |
| | |
Small tweaks for bash-completion after `apt install`
See merge request apt-team/apt!216
|
| |
| |
| |
| |
| | |
Following a practice from upstream bash-completion. See for example
https://github.com/scop/bash-completion/commit/b807460140aa6dda09eb2af2ecf3afa1971c84c4
|
| |
| |
| |
| |
| |
| |
| | |
argument to `apt install`
This will start by suggesting ./ and ../ which are both fine path
segments for `apt install` to handle later.
|
| |
| |
| |
| |
| | |
Should provide a tiny speed-up when someone already started typing
either one in the current argument.
|
| |
| |
| |
| |
| |
| | |
At the time the bash-completion runs, the ~ (or even ~user) is not yet
expanded to /home/user, so it did not match the existing comparison with
`/*`.
|
|\ \
| | |
| | |
| | |
| | | |
bash-completion: Don’t misidentify short options as commands to `apt`
See merge request apt-team/apt!211
|
| | |
| | |
| | |
| | |
| | |
| | | |
Previously the comparison would match `-s` with `edit-sources`, `-d`
with `build-dep` etc. and the real commands would not get suggested
after some of the short options.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
Bash-completion of .dsc filenames for `apt build-dep` (closes: #985899)
See merge request apt-team/apt!215
|
|/ /
| |
| |
| | |
Closes: #985899
|
|\ \
| | |
| | |
| | |
| | | |
Fix "was already not hold" message grammar
See merge request apt-team/apt!213
|
|/ / |
|
|\ \
| |/
|/|
| |
| | |
Add a --full mode to apt show
See merge request apt-team/apt!212
|