This project will let you mirror a Linux distribution's repository/repositories (or BSD, etc.).
Features:
* Logging
* RSync or FTP supported (RSync mirrors require rsync to be installed and in the $PATH environment variable) (HTTP/HTTPS cannot and will not be supported as there's no real way to do it reliably and efficiently.)
* Locking - prevent a specific distribution from syncing if it is currently being synced but allow other distributions to sync
* Customizable rsync arguments
* Changing of directory/file ownership per-distribution
* Mount-checking per-distribution - a distribution will be skipped if its designated mountpoint is not mounted
* Synchronization checks - timestamp files can be read and written and are used to determine if a sync should take place or not
** TODO: customizable "staleness" of repos (e.g. sync if timestamp X is older than timestamp Y on server)
Configuration/Deployment:
See example.config.xml for details on a configuration file, as it's extensively commented and won't be covered in this README.
You can also run reposync -h (or reposync --help) to see all supported options.
You may take special interest in repomirror/utils/find_fastest_upstream/ scripts as they're pre-written to find the fastest (in theory) upstream you can use. Currently only Arch Linux and CentOS have scripts written, but I'll gladly try to add other distros if you open a feature request (see below). You can run -h/--help to see the supported options (there aren't many).
Bugs/Feature Requests:
Please use my tracker at https://bugs.square-r00t.net/index.php?project=14 or, if you prefer to not create an account, simply email me at bts(at)square-r00t[dot]net.
Sources:
This project can be found at/cloned from:
* https://git.square-r00t.net/RepoMirror
* git://git.square-r00t.net/repomirror.git
And has a mirrored repository on GitHub (Issues/Wiki/etc. disabled) at:
* https://github.com/johnnybubonic/repomirror
It can also be found on PyPi at:
* https://pypi.org/project/repomirror/
Metadata
Release files for repomirror 1.0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| repomirror-1.0.4.tar.gz | 14.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| repomirror-1.0.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.4 kB
Release files / repomirror-1.0.4.tar.gz
| Download URL | repomirror-1.0.4.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2765e97376344bcff6d0211fb54d4a801144e9306c98845ed8a048fb02a2b126
|
|
BLAKE2b-256 checksum How to use checksums |
0e21bb5dc0b0741b2b802c1d588a079862cf73baf76d16d56e7750e3d9e30ea5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Release files / repomirror-1.0.4-py3-none-any.whl
| Download URL | repomirror-1.0.4-py3-none-any.whl |
|---|---|
| Size | 28.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4bc14f8aea4cfa5752b39db6c6472fc0e16a286f9c4139359d1c5ceb2ec36d70
|
|
BLAKE2b-256 checksum How to use checksums |
b5aadfcc941cfedccf219f0fd19df1aa5038a27e2328b21247aa516192856128
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/47.3.1 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.3
|
Security for repomirror 1.0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.