Projects

1 project(s) on this page

Project	Selected	Spr	Newest	Outdated	Ignored
libsearpc∗	3.3.0+really3.3+git20250303.6f06843	22	3.3.04 3.33	3.2.1-1+really3.2+git20220902.15f6f0b 3.2.0.20211008 3.2.0-7-g50ff08b 3.2.0.1 3.2.010 3.2_latest 3.1.02 3.1 3.0.8 3.0.2 3.0.latest 1.5.3	3.3-20241031 3.3-20230626 3.3.0.20250303 3.3.0.20230527 3.3.0.20220902 3.3.0.20220902 3.3.0+really3.3+git20250303.6f06843 3.3.0+really3.3+git20250122.255d5de 3.3.0+really3.3+git20240425.4ccd198 3.3.0+really3.3+git20230527.783141f 3.3.0pl20221111

Legend:

• Spread means how many repository families (e.g. all Debian versions as well as Ubuntu and other derivatives make 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 the 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.