Projects

7 project(s) on this page

Metapackage	In AIX Open Source Packages	Spread	Newest	Outdated	Ignored
aalib∗	1.4.0	35	1.4rc516 1.4_rc53 1.4~rc5 1.4.r5 1.2		1.4.0_5 1.4.0.5 1.4.05 1.43 1.4.0-rc52 1.4.0rc5 1.4p5
cgrep∗	8.15	4	6.6.272	6.6.25 6.6.17
dnrd	2.20.4 2.20.3	5	2.20.34
elvis	2.2f	11	2.2.05 2.2_04 2.2		20170815
hexdump∗	20130926 20130412	3	1.8		1003.1-2008
mupdf	2009_09_03_cvs	35	1.14.019	1.13.016 1.12.08 1.117 1.10a4 1.10 1.10~a 1.9a 1.9 1.82 1.7a 1.72 1.62 1.52 1.42 1.32 1.2 1.12 1.0 0.92 0.8 0.7 0.6	20181125.b5053c4c 1.14.0.20181105
smake	1.3.2	11	1.3	1.2.59 1.2a49

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).