Metapackages

3 item(s) on this page

Metapackage	In Kali Linux Rolling	Spread	Newest	Outdated	Ignored
claws-mail∗	3.17.1	27	3.17.121	3.17.02 3.16.07 3.15.14 3.15.05 3.14.14 3.14.02 3.13.24 3.13.1 3.13.02 3.11.1 3.10.12 3.9.32 3.9.0 3.8.0 1.9.6	9999 3.17.0.r153.gf4607b4b6
claws-mail-themes∗	20140629	8	201406297	20131119 20120129 201102162
sylpheed∗	3.7.0	26	3.7.020 3.7	3.6.04 3.6 3.5.19 3.5.02 3.5.0rc2 3.5.0beta1.r3426 3.4.3 3.4.22 3.4.1 3.4.0beta7 3.3.0 3.2.0beta5 0.1.0alpha

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