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.
4 project(s) on this page
| Project |
Spread |
Newest |
Outdated |
Ignored |
|
btrfs-progs∗
|
28 |
4.20.215 |
4.20.18 4.20 4.19.13 4.19 4.17.14 4.16.13 4.15.14 4.14.1 4.142 4.12 4.11.1 4.10.22 4.9.16 4.9 4.7.3 4.5.3 4.5.1 4.4.13 4.4 4.1.2 3.19.1 3.18.2 3.16.22 3.12 0.202 0.20.rc1.20130917git194aa4a 0.20rc1 0.18 v4.5.3 |
9999 4420_4.19.1_r0_g167651ca scm |
|
btrfs-progs-static∗
|
1 |
4.20.2 |
|
|
|
btrfs-tools∗
|
1 |
4.4 |
3.17 3.12 0.19 |
|
|
btrfsprogs∗
|
1 |
4.20.1 |
4.19.1 4.15 4.5.3 |
|
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).