While repology tries its best in matching packages across different repositories, this is quite a complex task:
Packages of a single software project may be named differently in some repositories (for instance, libagg vs. agg, dungeoncrawl vs. dungeon-crawl, fonts-linuxlibertine vs. fonts-ttf-linuxlibertine vs. linux-libertine-fonts vs. linuxlibertine-fonts-ttf).
There may be multiple unrelated software projects with a same name (for instance, clementine is both X11 window manager and a media player).
Some packages may use incorrect versions (for instance, picking "next" version number which was not released yet when packaging a git snapshot, or using dates and commit hashes instead of version numbers).
Repology uses a set of manually edited rules to resolve these cases. You may submit a change to the ruleset directly or use this form to suggest an improvement to the ruleset. Please only use this for problems which may be fixed by the ruleset (which are basically problems listed above).
Current reports (1)
Created 8 months ago,
The project needs some version(s) to be marked as ignored
Comment: Selected here `Needs version ignore` because it has to do with "version", but in fact the version is ignored wrongly.
Solus is reporting correctly the version at 18.104.22.1686. See here: https://github.com/bjaraujo/Bombermaaan/tags
This is a continuatin of bombermaaan hosted in sourceforge.
Repology reply: This has nothing to do with bombermaaan, all new versions from solus are ignored because of too many incorrect versions.