diff options
| author |  Christian Hesse <mail@eworm.de> | 2024-03-04 09:02:56 +0100 |
|---|---|---|
| committer | Christian Hesse <mail@eworm.de> | 2024-03-04 09:06:25 +0100 |
| commit | 8370784a9be4900b9cda82d42e1fa5fdcaee368b (patch) | |
| tree | b4090b318a656f51df541448c009027b7778c1af | |
| parent | 8edad204b9e309647ae07bda23966c2724016573 (diff) | |
| download | pacredir-8370784a9be4900b9cda82d42e1fa5fdcaee368b.tar.gz pacredir-8370784a9be4900b9cda82d42e1fa5fdcaee368b.tar.zst | |
README: issue solved!
Though the release is pacman 6.1.0...
| -rw-r--r-- | README.md | 14 |
1 files changed, 0 insertions, 14 deletions
@@ -76,20 +76,6 @@ Please note that `pacredir` redirects to the most recent database file found on the local network if it is not too old (currently 24 hours). To make sure you really do have the latest files run `pacman -Syu` *twice*. -Current caveat --------------- - -With `pacman`'s latest major release `6.x` it now supports a -*server error limit*: Three download errors from a server results in the -server being skipped for the remainder of this transaction. -However `pacredir` sends a "*404 - not found*" response if the file is not -available in local network - and is skipped after just three misses. - -The upcoming `pacman` version `7.x` does -[add cache server support](https://gitlab.archlinux.org/pacman/pacman/-/merge_requests/98) -and resolves the situation. You should use `pacman` with that feature -backported. - Security -------- |