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 for problems which may be fixed by the ruleset (which are basically problems listed above).
Current reports (1)
Created more than a year ago,
The project needs some version(s) to be marked as ignored
Comment: ignore choclately and scoop, they are using bogus versions numbers.
They are using 1.34.0-1 but the latest release per github (at the time of this writing) is "1.34.0".
Those 2 must be using a hash of something-post release or something like that.
Repology reply: Chocolatey is always ignored, so in this case the problem is Scoop. It uses build number present in windows downloads (https://github.com/aria2/aria2/releases), so it's even somewhat legitimate. I'm adding rule to remote the build number.