Related projects are determined by recursively matching package homepage URLs. Note that this list may be incomplete as Repology may not be able to get homepage URLs from some repositories.
3 project(s) on this page
Project |
Spr |
Newest |
Outdated |
Ignored |
Rank |
duplicity∗
|
30 |
0.8.183 |
0.8.177 0.8.168 0.8.153 0.8.136 0.8.12.16122 0.8.122 0.8.11.1612 0.8.11.1596 0.8.09 0.8.08 0.8.03 0.7.195 0.7.18.27 0.7.18.1 0.7.176 0.7.16 0.7.153 0.7.142 0.7.13.12 0.7.124 0.7.113 0.7.10 0.7.07.1 0.7.062 0.6.262 0.6.242 0.6.23 0.6.22 0.6.18 |
930 0.8.17.dev29 |
100.0 |
duplicity-dev∗
|
1 |
0.8.18 |
|
|
95.85 |
python:duplicity∗
|
1 |
0.8.18 |
|
|
85.85 |
Legend:
- Spread means how many repository families (e.g. all Debian versions are a single family) contain this package.
- newest#repos - newest known version. The number shows how many repository families have this version.
- devel - newest known devel (or unstable) version. There may be both devel and newest versions for a given package.
- unique - package is only present in a single repository family, there are no other sources to compare it against, so although it's latest version known to repology, is not really reliable.
- outdated - outdated version which requires updating.
- legacy - outdated version when a newer version is present. This is assumed to be legacy version preserved for e.g. compatibility.
- rolling - package is fetched from always latest snapshot or VCS master/trunk, so it is always latest and is not a subject for comparison.
- noscheme - the project does not have official versioning scheme, so versions used in repositories which are basically random.
- incorrect - version is known to be incorrect (e.g. version not officially released yet, or lacking alpha/beta/rc qualifier).
- untrusted - this source is known to likely supply incorrect versions, so is ignored proactively.
- ignored - version is ignored and excluded from comparison for some other reason (e.g. snapshots).
- vulnerable▲ - version is potentially vulnerable as there are related CVEs.