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 (3)
Created more than a year ago,
20210715.151551.e7ad03a is current version,
Created 2 years ago,
Comment: "20210124.204813.840499f" is seen as incorrect/ignored, though it exactly matches how upstream version things now: https://github.com/wez/atomicparsley/releases
Confusingly, `--version` can make the last component show as 0: "20210124.204813.0"
Created 4 years ago,
The project needs some version(s) to be marked as ignored