Evaluate consequences of importing large amounts of packages into reprepro
Try it, see how it behaves, including:
- importing 1k to 2k source packages into a reprepro APT suite
- operations documented on https://tails.boum.org/contribute/APT_repository/, especially merging
The information we need is:
- information about the hardware and system load it was tested on
- how much time each operation takes
- how much peak memory each operation takes
- disk space used after each operation
For the set of packages to import, as a first approximation, use the
*.packages file found at https://tails.boum.org/torrents/files/. These
are binary packages, so a first step would be to convert this list to
the corresponding list of source packages, based on the APT sources
(plus corresponding deb-src lines) configured in Tails. Note that this
part of the work can very well be done in very hackish ways to start
with (baby steps!), but a nicer solution will have to be found later
(#6297 (closed)).
People are doing that, e.g. to maintain local mirrors:
http://vincent.bernat.im/en/blog/2014-local-apt-repositories.html
After the initial evaluation, we’ll want to keep an eye on resources usage and performance in production-like settings.
Blueprint: https://tails.boum.org/blueprint/freezable_APT_repository/
Parent Task: #9487 (closed)
Related issues
- Blocks #6303 (closed)
Original created by @intrigeri on 6295 (Redmine)