Metapackages

6 item(s) on this page

Metapackage	In Devuan Testing	Spread	Newest	Outdated	Ignored
connectagram	1.2.9	9	1.2.96	1.2.8 1.2.6 1.2.5 1.2.44 1.2.1 1.1.2 1.0.1 1.0.1maemo0
cutemaze	1.2.4	13	1.2.49	1.2.3 1.2.2 1.2.1 1.2.04 1.1.12 1.1.0
libircclient∗	1.9	18	1.105	1.98 1.86 1.72 1.62 1.3
libstrophe	0.9.2	14	0.9.212	0.9.15 0.8.8 0.8.6	273.cd92f69
linuxlogo∗	5.11	1	5.11
profanity∗	0.5.1	15	0.5.115	0.5.02 0.4.72 0.4.6 0.4.5 0.4.42 0.4.3 0.4.2 0.4.1 0.4.0 0.3.1 0.3.0 0.2.1 0.2.0 0.1.10 0.1.9 0.1.8 0.1.7	4737.d485588

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