[pacman-dev] [PATCH v2] Swap alpm_db_update() implementation to multiplexed version
anatol.pomozov at gmail.com
Mon May 11 17:45:57 UTC 2020
On Mon, May 11, 2020 at 7:51 AM <guillaume at manjaro.org> wrote:
> Hi Allan, Hi Anatol,
> I was looking to this new multiplexed implementation and I found some
> 1) This implementation can lead to download databases from different
> servers, I think it can't be a problem if they are not synced
Database files are downloaded independently. There is no any grouping
where did each file come from. It is true both for current (multiplexed) and for
the previous (sequential) downloader implementation.
Thus there was and is always a possibility that databases can
come from different mirrors e.g. in case of a flaky server.
> 2) Differents download payloads are created for databases and its
> signature files, this can this time lead to download the database and
> its signature from differents server, I'm sure it's not wanted.
> 3) Because signature files have their own download payloads, if the
> signature is missing on a the first server (e.g. database signature is
> optional), all next servers will be tried and all will give the same
> I really wanted to suggest a patch but I didn't find a easy way
> (understand a small patch) to fix it and I would like your opinion on
> point 1) first.
More information about the pacman-dev